idnits 2.17.1 draft-ietf-ccamp-lmp-mib-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 2004) is 7157 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'IF-MIB' is mentioned on line 373, but not defined == Unused Reference: 'RFC2026' is defined on line 3799, but no explicit reference was found in the text == Unused Reference: 'RFC2914' is defined on line 3825, but no explicit reference was found in the text == Unused Reference: 'RFC3291' is defined on line 3828, but no explicit reference was found in the text == Unused Reference: 'RFC3667' is defined on line 3839, but no explicit reference was found in the text == Unused Reference: 'RFC3668' is defined on line 3842, but no explicit reference was found in the text == Unused Reference: 'BUNDLING' is defined on line 3874, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) ** Obsolete normative reference: RFC 3667 (Obsoleted by RFC 3978) ** Obsolete normative reference: RFC 3668 (Obsoleted by RFC 3979) -- Possible downref: Non-RFC (?) normative reference: ref. 'TELINK-MIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'LMP-WDM' -- Possible downref: Non-RFC (?) normative reference: ref. 'LMP-TEST' Summary: 5 errors (**), 0 flaws (~~), 8 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Martin Dubuc 3 Internet Draft 4 Category: Standards Track Sudheer Dharanikota 5 Expires: March 2005 6 Thomas D. Nadeau 7 Cisco Systems 9 Jonathan P. Lang 10 Rincon Networks 12 Evan McGinnis 13 Calient Networks 15 September 2004 17 Link Management Protocol Management Information Base 19 draft-ietf-ccamp-lmp-mib-10.txt 21 Status of this Memo 23 This document is an Internet-Draft and is in full conformance with 24 all provisions of Section 10 of RFC 2026. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF), its areas, and its working groups. Note that other 28 groups may also distribute working documents as Internet-Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts.txt. 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html. 41 Abstract 43 This memo defines a portion of the Management Information Base (MIB) 44 for use with network management protocols in the Internet community. 45 In particular, it describes managed objects for modeling the Link 46 Management Protocol (LMP). 48 Table of Contents 50 1. The Internet-Standard Management Framework . . . . . . . . . . . 2 51 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2 52 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 4. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . . 3 54 5. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 6. Brief Description of MIB Objects . . . . . . . . . . . . . . . . 4 56 6.1. lmpNbrTable . . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 6.2. lmpControlChannelTable . . . . . . . . . . . . . . . . . . . . 5 58 6.3. lmpControlChannelPerfTable . . . . . . . . . . . . . . . . . . 5 59 6.4. lmpTeLinkTable . . . . . . . . . . . . . . . . . . . . . . . . 5 60 6.5. lmpLinkVerificationTable . . . . . . . . . . . . . . . . . . . 5 61 6.6. lmpTeLinkPerfTable . . . . . . . . . . . . . . . . . . . . . . 5 62 6.7. lmpDataLinkTable . . . . . . . . . . . . . . . . . . . . . . . 5 63 6.8. lmpDataLinkPerfTable . . . . . . . . . . . . . . . . . . . . . 5 64 7. Example of LMP Control Channel Interface Setup . . . . . . . . . 5 65 8. Application of the Interfaces Group to LMP . . . . . . . . . . . 8 66 8.1. Support of the LMP Layer by ifTable . . . . . . . . . . . . . . 9 67 9. Link Management Protocol MIB Module Definitions . . . . . . . . . 11 68 10. Intellectual Property Considerations . . . . . . . . . . . . . . 78 69 11. Security Considerations . . . . . . . . . . . . . . . . . . . . 78 70 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 79 71 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 80 72 13.1 IANA Considerations for lmp ifType . . . . . . . . . . . . . . 80 73 13.2 IANA Considerations for LMP-MIB . . . . . . . . . . . . . . . . 80 74 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 75 14.1 Normative References . . . . . . . . . . . . . . . . . . . . . 80 76 14.2 Informative References . . . . . . . . . . . . . . . . . . . . 81 77 15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 82 78 16. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 82 80 1. The Internet-Standard Management Framework 82 For a detailed overview of the documents that describe the current 83 Internet-Standard Management Framework, please refer to section 7 of 84 RFC 3410 [RFC3410]. 86 Managed objects are accessed via a virtual information store, termed 87 the Management Information Base or MIB. MIB objects are generally 88 accessed through the Simple Network Management Protocol (SNMP). 89 Objects in the MIB are defined using the mechanisms defined in the 90 Structure of Management Information (SMI). This memo specifies a MIB 91 module that is compliant to the SMIv2, which is described in STD 58, 92 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 93 [RFC2580]. 95 2. Introduction 97 Current work is underway in the IETF to specify a suite of protocols 98 to be used as a common control plane and a separate common measure- 99 ment plane. Along with Generalized MPLS (GMPLS) [RFC3471], the Link 100 Management Protocol [LMP], which primary purpose is to manage traffic 101 engineering (TE) links, is one of the key components of this stan- 102 dardization activity. Primary goals of LMP are the maintenance of the 103 control channel connectivity, correlation of link properties, verifi- 104 cation of data-bearing links and detection and isolation of link 105 faults. 107 We describe in this document a MIB module that can be used to manage 108 LMP implementations. This MIB module covers both configuration and 109 performance monitoring aspects of LMP. 111 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 112 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 113 document are to be interpreted as described in RFC 2119, reference 114 [RFC2119]. 116 3. Terminology 118 This document uses terminology from the document describing the Link 119 Management Protocol [LMP]. An "LMP adjacency" is formed between two 120 nodes that support the same capabilities, and LMP messages are 121 exchanged between the node pair over control channels that form this 122 adjacency. Several control channels can be active at the same time. 123 With the exception of messages related to control channel management, 124 any time a LMP message needs to be transferred to a neighbor node, it 125 can be sent on any of the active control channels. The control 126 channels can also be used to exchange MPLS control plane information 127 or routing information. 129 LMP is designed to support aggregation of one or more data-bearing 130 links into a traffic-engineering (TE) link. The data-bearing links 131 can be either component links or ports depending on their 132 multiplexing capability (see [LMP] for distinction between port and 133 component link). 135 Each TE link is associated with an LMP adjacency, and one or more 136 control channels are used to exchange LMP messages for a particular 137 adjacency. In turn, control channels are used to manage the TE links 138 associated with the LMP adjacency. 140 4. Feature Checklist 142 The Link Management Protocol MIB module (LMP-MIB) is designed to 143 satisfy the following requirements and constraints: 145 - The MIB module supports the enabling and disabling of LMP 146 capability on LMP capable interfaces of a photonic switch, 147 optical cross-connect or router. 149 - The MIB module is used provide information about LMP adjacencies. 151 - Support is provided for configuration of the keep alive and 152 link verification parameters. 154 - The MIB module is used to express the mapping between local and 155 remote TE links, as well as local and remote interface identifiers 156 for port or component link. 158 - Performance counters are provided for measuring LMP 159 performance on a per-control channel basis. Performance counters 160 are also provided for measuring LMP performance on the data- 161 bearing links. 163 Note that the LMP MIB module goes hand-in-hand with the TE Link (TE- 164 LINK-STD-MIB) MIB module [TELINK-MIB]. The TE link table, which is 165 used to associate data-bearing links to TE links, is defined in the 166 TE Link MIB. The TE link table in the LMP MIB module contains TE link 167 information specific to LMP. 169 5. Outline 171 Configuring LMP through an optical device involves the following 172 steps: 174 - Enabling LMP on LMP capable interfaces through control channel 175 configuration. 177 - Optionally specifying link verification parameters. 179 - Configuring the data-bearing links and associating them to the 180 appropriate TE link (this association is stored in the 181 ifStackTable of the Interfaces Group MIB). 183 TE links are managed by the control channels that run between the 184 same pair of nodes (LMP adjacency). 186 6. Brief Description of MIB Objects 188 Sections 6.1-6.8 describe objects pertaining to LMP. The MIB objects 189 were derived from the LMP document [LMP]. 191 6.1. lmpNbrTable 193 The remote node table is used to identify the pair of nodes that 194 exchange LMP messages over control channels. 196 6.2. lmpControlChannelTable 198 The control channel table is used for enabling the LMP protocol on 199 LMP-capable interfaces. A photonic switch, optical cross-connect or 200 router creates an entry in this table for every LMP capable interface 201 in that device. 203 6.3. lmpControlChannelPerfTable 205 The control channel performance table is used for collecting LMP 206 performance counts on a per-control channel basis. Each entry in the 207 lmpControlChannelTable has a corresponding entry in the 208 lmpControlChannelPerfTable. 210 6.4. lmpTeLinkTable 212 The TE link table is used for specifying LMP information associated 213 with TE links. 215 6.5. lmpLinkVerificationTable 217 The link verification table is used for configuring the LMP link 218 verification parameters of TE links. For every TE link entry in the 219 lmpTeLinkTable that supports the link verification procedure, there 220 is a corresponding entry in the lmpLinkVerificationTable. 222 6.6. lmpTeLinkPerfTable 224 The TE link performance table is used for collecting LMP performance 225 counts on a per-TE link basis. Each entry in the lmpTeLinkTable has a 226 corresponding entry in the lmpTeLinkPerfTable. 228 6.7. lmpDataLinkTable 230 The data-bearing link table is used to specify the data-bearing links 231 that are associated with TE links. 233 6.8. lmpDataLinkPerfTable 235 The data-bearing link performance table is used for collecting LMP 236 performance counts on data-bearing links. 238 7. Example of LMP Control Channel Setup 240 In this section we provide a brief example of using the MIB 241 objects described in section 10 to set up an LMP control channel. 242 While this example is not meant to illustrate every nuance of the 243 MIB module, it is intended as an aid to understanding some of the 244 key concepts. It is meant to be read after going through the MIB 245 itself. 247 Suppose that one would like to form an LMP adjacency between two 248 nodes using two control channels. Suppose also that there are 249 three data-bearing links. We also assume that the data-bearing 250 links are ports (lambdas). We also assume that the link 251 verification procedure is not enabled. The following example 252 illustrates which rows and corresponding objects might be created 253 to accomplish this. 255 First, LMP must be enabled between the pair of nodes. 257 In lmpNbrTable: 258 { 259 lmpNbrNodeId = 'c0000201'H, -- 192.0.2.1 260 lmpNbrAdminStatus = up(1), 261 lmpNbrRowStatus = createAndGo(4), 262 lmpNbrStorageType = nonVolatile(3) 263 } 265 Then, the control channels must be set up. These are created in 266 the lmpControlChannelTable. 268 In lmpControlChannelTable: 269 { 270 lmpCcId = 1, 271 lmpCcUnderlyingIfIndex = 1, 272 lmpCcIsIf = false(1), 273 lmpCcAuthentication = false(1), 274 lmpCcHelloInterval = 15, 275 lmpCcHelloIntervalMin = 15, 276 lmpCcHelloIntervalMax = 1000, 277 lmpCcHelloDeadInterval = 45, 278 lmpCcHelloDeadIntervalMin = 45, 279 lmpCcHelloDeadIntervalMax = 1000, 280 lmpCcAdminStatus = up(1), 281 lmpCcRowStatus = createAndGo(4), 282 lmpCcStorageType = nonVolatile(3) 283 } 285 { 286 lmpCcId = 2, 287 lmpCcUnderlyingIfIndex = 2, 288 lmpCcIsIf = false(1), 289 lmpCcAuthentication = false(1), 290 lmpCcHelloInterval = 15, 291 lmpCcHelloIntervalMin = 15, 292 lmpCcHelloIntervalMax = 1000, 293 lmpCcHelloDeadInterval = 45, 294 lmpCcHelloDeadIntervalMin = 45, 295 lmpCcHelloDeadIntervalMax = 1000, 296 lmpCcAdminStatus = up(1), 297 lmpCcRowStatus = createAndGo(4), 298 lmpCcStorageType = nonVolatile(3) 299 } 301 Next, the three data-bearing links are created. For each data- 302 bearing link, an ifEntry with the same ifIndex needs to be created 303 beforehand. 305 In lmpDataLinkTable: 306 { 307 ifIndex = 41, 308 lmpDataLinkAddressType = unknown(0), 309 lmpDataLinkIpAddr = ''H, 310 lmpDataLinkRemoteIpAddress = ''H, 311 lmpDataLinkRemoteIfId = 47, 312 lmpDataLinkRowStatus = createAndGo(4), 313 lmpDataLinkStorageType = nonVolatile(3) 314 } 316 { 317 ifIndex = 43, 318 lmpDataLinkAddressType = unknown(0), 319 lmpDataLinkIpAddr = ''H, 320 lmpDataLinkRemoteIpAddress = ''H, 321 lmpDataLinkRemoteIfId = 42, 322 lmpDataLinkRowStatus = createAndGo(4), 323 lmpDataLinkStorageType = nonVolatile(3) 324 } 326 { 327 ifIndex = 44, 328 lmpDataLinkAddressType = unknown(0), 329 lmpDataLinkIpAddr = ''H, 330 lmpDataLinkRemoteIpAddress = ''H, 331 lmpDataLinkRemoteIfId = 48, 332 lmpDataLinkRowStatus = createAndGo(4), 333 lmpDataLinkStorageType = nonVolatile(3) 334 } 336 Note that the data-bearing link type (lmpDataLinkType) does 337 not need to be provisioned as it is automatically populated by the 338 node. The definition of the protection role (primary or 339 secondary) for the data-bearing links is stored in the 340 componentLinkTable of the TE Link MIB module [TELINK-MIB]. 342 Then, a TE link is created as an ifEntry with ifType teLink in 343 the ifTable. 345 Once the TE link is created in the ifTable, a TE link entry 346 is created in the LMP MIB module to specify TE link information 347 specific to LMP. 349 In lmpTeLinkTable: 350 { 351 ifIndex = 20, 352 lmpTeLinkVerification = true(2), 353 lmpTeLinkFaultManagement = true(2), 354 lmpTeLinkDwdm = false(1), 355 lmpTeLinkRowStatus = createAndGo(4), 356 lmpTeLinkStorageType = nonVolatile(3) 357 } 359 and in lmpLinkVerificationTable: 360 { 361 ifIndex = 20, 362 lmpLinkVerifyInterval = 100, 363 lmpLinkVerifyDeadInterval = 300, 364 lmpLinkVerifyTransportMechanism = j0Trace(3), 365 lmpLinkVerifyAllLinks = true(2), 366 lmpLinkVerifyTransmissionRate = 100000, 367 lmpLinkVerifyWavelength = 0, 368 lmpLinkVerifyRowStatus = createAndGo(4), 369 lmpLinkVerifyStorageType = nonVolatile(3) 370 } 372 The association between the data-bearing links and the TE links is 373 stored in the ifStackTable [IF-MIB]. 375 In parallel with the entry created in the lmpTeLinkTable, an entry 376 may be created in the teLinkTable of TE Link MIB module 377 [TELINK-MIB]. 379 8. Application of the Interfaces Group to LMP 381 The Interfaces Group [RFC2863] defines generic managed objects for 382 managing interfaces. This memo contains the media-specific 383 extensions to the Interfaces Group for managing LMP control channels 384 that are modeled as interfaces. If the control channel as defined in 385 the lmpControlChannelTable is modeled as an ifEntry, then the 386 following definition applies. An lmpControlChannelTable entry is 387 designated as being represented as an Interfaces MIB ifEntry if the 388 lmpControlChannelEntry object lmpCcIsIf is set to true (2). In this 389 case, the control channel SHOULD be modeled as an ifEntry and 390 provide appropriate interface stacking as defined below. 392 This memo assumes the interpretation of the Interfaces Group to be 393 in accordance with [RFC2863] which states that the interfaces table 394 (ifTable) contains information on the managed resource's 395 interfaces and that each sub-layer below the internetwork layer of 396 a network interface is considered an interface. Since the LMP 397 interface only carries control traffic, it is considered to be below 398 the internetwork layer. Thus, the LMP interface may be represented 399 as an entry in the ifTable. The inter-relation of entries in the 400 ifTable is defined by Interfaces Stack Group defined in [RFC2863]. 402 When LMP control channels are modeled as interfaces, the interface 403 stack table must appear as follows for the LMP control channel 404 interfaces: 406 +----------------------------------------+ 407 | LMP-interface ifType = lmp(TBD) + 408 +----------------------------------------+ 409 | Underlying Layer... + 410 +----------------------------------------+ 412 In the above diagram, "Underlying Layer..." refers to the ifIndex 413 of any interface type over which the LMP interface will transmit 414 its traffic. Note that if the underlying layer provides multiple 415 access to its media (i.e.: Ethernet), then it is possible to stack 416 multiple LMP interfaces on top of this interface in parallel. 418 Note that it is not a requirement that LMP control channels be 419 modeled as interfaces. It is acceptable that control channels 420 simply exist as logical connections between adjacent LMP-capable 421 nodes. In this case, lmpCcIsIf is set to false(2) and no 422 corresponding entry is made in the ifTable. 424 8.1. Support of the LMP Layer by ifTable 426 Some specific interpretations of ifTable for the LMP layer 427 follow. 429 Object Use for the LMP layer 431 ifIndex Each LMP interface may be represented by an ifEntry. 433 ifDescr Description of the LMP interface. 435 ifType The value that is allocated for LMP is TBD. 436 This number will be assigned by the IANA. 438 ifSpeed The total bandwidth in bits per second for use by 439 the LMP layer. 441 ifPhysAddress Unused. 443 ifAdminStatus This variable indicates the administrator's intent 444 as to whether LMP should be enabled, disabled, or 445 running in some diagnostic testing mode on this 446 interface. Also see [RFC2863]. 448 ifOperStatus This value reflects the actual or operational 449 status of LMP on this interface. 451 ifLastChange See [RFC2863]. 453 ifInOctets The number of received octets over the interface, 454 i.e., the number of octets received as LMP 455 packets. 457 ifOutOctets The number of transmitted octets over the 458 interface, i.e., the number of octets transmitted 459 as LMP packets. 461 ifInErrors The number of LMP packets dropped due to 462 uncorrectable errors. 464 ifInUnknownProtos 465 The number of received packets discarded during 466 packet header validation, including packets with 467 unrecognized label values. 469 ifOutErrors See [RFC2863]. 471 ifName Textual name (unique on this system) of the 472 interface or an octet string of zero length. 474 ifLinkUpDownTrapEnable 475 Default is disabled (2). 477 ifConnectorPresent 478 Set to false (2). 480 ifHighSpeed See [RFC2863]. 482 ifHCInOctets The 64-bit version of ifInOctets; supported if 483 required by the compliance statements in [RFC2863]. 485 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 486 required by the compliance statements in [RFC2863]. 488 ifAlias The non-volatile 'alias' name for the interface as 489 specified by a network manager. 491 ifCounterDiscontinuityTime 492 See [RFC2863]. 494 9. LMP MIB Module Definitions 496 LMP-MIB DEFINITIONS ::= BEGIN 498 IMPORTS 499 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 500 transmission, Unsigned32, Counter32, TimeTicks 501 FROM SNMPv2-SMI 503 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 504 FROM SNMPv2-CONF 506 TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, 507 TimeStamp 508 FROM SNMPv2-TC 510 InterfaceIndexOrZero, ifIndex 511 FROM IF-MIB 513 InetAddressType, InetAddress 514 FROM INET-ADDRESS-MIB 516 teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType 517 FROM TE-LINK-STD-MIB; 519 lmpMIB MODULE-IDENTITY 520 LAST-UPDATED "200409081200Z" -- 8 September 2004 12:00:00 EST 521 ORGANIZATION "Common Control and Measurement Protocols (CCAMP) 522 Working Group" 523 CONTACT-INFO 524 " Martin Dubuc 525 Email: dubuc.consulting@sympatico.ca 527 Sudheer Dharanikota 528 Email: sudheer@ieee.org 530 Thomas D. Nadeau 531 Email: tnadeau@cisco.com 533 Jonathan P. Lang 534 Email: jplang@ieee.org 536 Evan McGinnis 537 Email: evan@calient.net" 539 DESCRIPTION 540 "Copyright (C) 2004 The Internet Society. This version of 541 the MIB module is part of RFC XXXX; see the RFC itself 542 for full legal notices. 544 This MIB module contains managed object definitions for 545 the Link Management Protocol (LMP) as 546 defined in 'Link Management Protocol'." 548 -- Revision history. 549 REVISION 550 "200409081200Z" -- 8 September 2004 12:00:00 EST 551 DESCRIPTION 552 "Initial version published as RFC xxxx (to be assigned by RFC 553 Editor)" 554 ::= { transmission xxx } -- To be assigned by IANA. 555 -- Request to assign same number as LMP 556 -- ifType. 558 -- Textual Conventions 560 LmpInterval ::= TEXTUAL-CONVENTION 561 DISPLAY-HINT "d" 562 STATUS current 563 DESCRIPTION 564 "The interval delay in milliseconds." 565 SYNTAX Unsigned32 (1..65535) 567 LmpRetransmitInterval ::= TEXTUAL-CONVENTION 568 DISPLAY-HINT "d" 569 STATUS current 570 DESCRIPTION 571 "The retransmission interval delay in milliseconds." 572 SYNTAX Unsigned32 (1..4294967295) 574 LmpNodeId ::= TEXTUAL-CONVENTION 575 DISPLAY-HINT "1d.1d.1d.1d" 576 STATUS current 577 DESCRIPTION 578 "Represents a Node ID in network byte order. Node ID is an 579 address of type IPv4." 580 REFERENCE 581 "Section 1.1 of Link Management Protocol, RFC xxx" 582 -- RFC Editor to fill in RFC number that will be assigned to 583 -- [LMP] 584 SYNTAX OCTET STRING(SIZE(4)) 586 -- Top level components of this MIB 588 -- Notifications 589 lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 } 590 -- Tables, Scalars 591 lmpObjects OBJECT IDENTIFIER ::= { lmpMIB 1 } 592 -- Conformance 593 lmpConformance OBJECT IDENTIFIER ::= { lmpMIB 2 } 595 lmpAdminStatus OBJECT-TYPE 596 SYNTAX INTEGER { up(1), down(2) } 597 MAX-ACCESS read-write 598 STATUS current 599 DESCRIPTION 600 "The desired operational status of LMP on the node. 601 Implementations should save the value of this object in 602 persistent memory so that it survives restarts or reboot." 603 DEFVAL { up } 604 ::= { lmpObjects 1 } 606 lmpOperStatus OBJECT-TYPE 607 SYNTAX INTEGER { up(1), down(2) } 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION 611 "The actual operational status of LMP on the node." 612 ::= { lmpObjects 2 } 614 -- LMP Neighbor Table 616 lmpNbrTable OBJECT-TYPE 617 SYNTAX SEQUENCE OF LmpNbrEntry 618 MAX-ACCESS not-accessible 619 STATUS current 620 DESCRIPTION 621 "This table specifies the neighbor node(s) to which control 622 channels may be established." 623 ::= { lmpObjects 3 } 625 lmpNbrEntry OBJECT-TYPE 626 SYNTAX LmpNbrEntry 627 MAX-ACCESS not-accessible 628 STATUS current 629 DESCRIPTION 630 "An entry in this table is created by a LMP-enabled device for 631 every pair of nodes that can establish control channels." 632 INDEX { lmpNbrNodeId } 633 ::= { lmpNbrTable 1 } 635 LmpNbrEntry ::= SEQUENCE { 636 lmpNbrNodeId LmpNodeId, 637 lmpNbrRetransmitInterval LmpRetransmitInterval, 638 lmpNbrRetryLimit Unsigned32, 639 lmpNbrRetransmitDelta Unsigned32, 640 lmpNbrAdminStatus INTEGER, 641 lmpNbrOperStatus INTEGER, 642 lmpNbrRowStatus RowStatus, 643 lmpNbrStorageType StorageType 644 } 646 lmpNbrNodeId OBJECT-TYPE 647 SYNTAX LmpNodeId 648 MAX-ACCESS not-accessible 649 STATUS current 650 DESCRIPTION 651 "This is a unique index for an entry in the LmpNbrTable. 652 This value represents the remote Node ID." 653 ::= { lmpNbrEntry 1 } 655 lmpNbrRetransmitInterval OBJECT-TYPE 656 SYNTAX LmpRetransmitInterval 657 MAX-ACCESS read-create 658 STATUS current 659 DESCRIPTION 660 "This object specifies the initial retransmission interval that 661 is used for the retransmission of messages which require 662 acknowledgement. This object along with lmpNbrRetryLimit is 663 used to implement congestion handling mechanism as defined in 664 Section 10 of the Link Management Protocol specification, 665 which is based on RFC 2914." 666 REFERENCE 667 "Link Management Protocol, RFC xxx" 668 -- RFC Editor to fill in RFC number that will be assigned to 669 -- [LMP] 670 DEFVAL { 500 } 671 ::= { lmpNbrEntry 2 } 673 lmpNbrRetryLimit OBJECT-TYPE 674 SYNTAX Unsigned32 675 MAX-ACCESS read-create 676 STATUS current 677 DESCRIPTION 678 "This object specifies the maximum number of times a message 679 is transmitted without being acknowledged. A value of 0 is used 680 to indicate that a node should never stop retransmission. 681 This object along with lmpNbrRetransmitInterval is 682 used to implement congestion handling mechanism as defined in 683 Section 10 of the Link Management Protocol specification, 684 which is based on RFC 2914." 685 REFERENCE 686 "Link Management Protocol, RFC xxx" 687 -- RFC Editor to fill in RFC number that will be assigned to 688 -- [LMP] 689 DEFVAL { 3 } 690 ::= { lmpNbrEntry 3 } 692 lmpNbrRetransmitDelta OBJECT-TYPE 693 SYNTAX Unsigned32 694 MAX-ACCESS read-create 695 STATUS current 696 DESCRIPTION 697 "This object governs the speed with which the sender increases 698 the retransmission interval as explained in section 10 of the 699 Link Management Protocol specification, which is based on 700 RFC 2914. This value is a power used to express the 701 exponential backoff. The ratio of two succesive retransmission 702 intervals is (1 + Delta)." 703 REFERENCE 704 "Link Management Protocol, RFC xxx" 705 -- RFC Editor to fill in RFC number that will be assigned to 706 -- [LMP] 707 DEFVAL { 1 } 708 ::= { lmpNbrEntry 4 } 710 lmpNbrAdminStatus OBJECT-TYPE 711 SYNTAX INTEGER { up(1), down(2) } 712 MAX-ACCESS read-create 713 STATUS current 714 DESCRIPTION 715 "The desired operational status of LMP to this remote node." 716 ::= { lmpNbrEntry 5 } 718 lmpNbrOperStatus OBJECT-TYPE 719 SYNTAX INTEGER { up(1), down(2) } 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION 723 "The actual operational status of LMP to this remote node." 724 ::= { lmpNbrEntry 6 } 726 lmpNbrRowStatus OBJECT-TYPE 727 SYNTAX RowStatus 728 MAX-ACCESS read-create 729 STATUS current 730 DESCRIPTION 731 "This variable is used to create, modify, and/or 732 delete a row in this table. None of the writable objects 733 in a row can be changed if the status is active(1). 734 All read-create objects must have valid and consistent 735 values before the row can be activated." 736 ::= { lmpNbrEntry 7 } 738 lmpNbrStorageType OBJECT-TYPE 739 SYNTAX StorageType 740 MAX-ACCESS read-create 741 STATUS current 742 DESCRIPTION 743 "The storage type for this conceptual row in the 744 lmpNbrTable. Conceptual rows having the value 745 'permanent' need not allow write-access to any 746 columnar object in the row." 747 DEFVAL { nonVolatile } 748 ::= { lmpNbrEntry 8 } 750 -- End of lmpNbrTable 752 lmpCcHelloIntervalDefault OBJECT-TYPE 753 SYNTAX LmpInterval 754 MAX-ACCESS read-write 755 STATUS current 756 DESCRIPTION 757 "This object specifies the default value for the HelloInterval 758 parameter used in the Hello protocol keep-alive phase. It 759 indicates how frequently LMP Hello messages will be sent. It 760 is used a the default value for lmpCcHelloInterval. 761 Implementations should save the value of this object in 762 persistent memory so that it survives restarts or reboot." 763 REFERENCE 764 "Link Management Protocol, RFC xxx" 765 -- RFC Editor to fill in RFC number that will be assigned to 766 -- [LMP] 767 ::= { lmpObjects 4 } 769 lmpCcHelloIntervalDefaultMin OBJECT-TYPE 770 SYNTAX LmpInterval 771 MAX-ACCESS read-write 772 STATUS current 773 DESCRIPTION 774 "This object specifies the default minimum value for the 775 HelloInterval parameter. It is used as a default value 776 for lmpCcHelloIntervalMin. Implementations should save the 777 value of this object in persistent memory so that it survives 778 restarts or reboot." 779 ::= { lmpObjects 5 } 781 lmpCcHelloIntervalDefaultMax OBJECT-TYPE 782 SYNTAX LmpInterval 783 MAX-ACCESS read-write 784 STATUS current 785 DESCRIPTION 786 "This object specifies the default maximum value for the 787 HelloInterval parameter. It is used as a default value 788 for lmpCcHelloIntervalMax. Implementations should save the 789 value of this object in persistent memory so that it survives 790 restarts or reboot." 791 ::= { lmpObjects 6 } 793 lmpCcHelloDeadIntervalDefault OBJECT-TYPE 794 SYNTAX LmpInterval 795 MAX-ACCESS read-write 796 STATUS current 797 DESCRIPTION 798 "This object specifies the default HelloDeadInterval parameter 799 to use in the Hello protocol keep-alive phase. It indicates 800 how long a device should wait before declaring the control 801 channel dead. The HelloDeadInterval parameter should be at 802 least three times the value of HelloInterval. It is used as 803 a default value for lmpCcHelloDeadInterval. Implementations 804 should save the value of this object in persistent memory so 805 that it survives restarts or reboot." 806 REFERENCE 807 "Link Management Protocol, RFC xxx" 808 -- RFC Editor to fill in RFC number that will be assigned to 809 -- [LMP] 810 ::= { lmpObjects 7 } 812 lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE 813 SYNTAX LmpInterval 814 MAX-ACCESS read-write 815 STATUS current 816 DESCRIPTION 817 "This object specifies the default minimum value for the 818 HelloDeadInterval parameter. It is used as a default value 819 for lmpCcHelloDeadIntervalMin. Implementations should save 820 the value of this object in persistent memory so that it 821 survives restarts or reboot." 822 ::= { lmpObjects 8 } 824 lmpCcHelloDeadIntervalDefaultMax OBJECT-TYPE 825 SYNTAX LmpInterval 826 MAX-ACCESS read-write 827 STATUS current 828 DESCRIPTION 829 "This object specifies the default maximum value for the 830 HelloDeadInterval parameter. It is used as a default value 831 for lmpCcHelloDeadIntervalMax. Implementations should save the 832 value of this object in persistent memory so that it survives 833 restarts or reboot." 834 ::= { lmpObjects 9 } 836 -- LMP Control Channel Table 838 lmpControlChannelTable OBJECT-TYPE 839 SYNTAX SEQUENCE OF LmpControlChannelEntry 840 MAX-ACCESS not-accessible 841 STATUS current 842 DESCRIPTION 843 "This table specifies LMP control channel information." 844 ::= { lmpObjects 10 } 846 lmpControlChannelEntry OBJECT-TYPE 847 SYNTAX LmpControlChannelEntry 848 MAX-ACCESS not-accessible 849 STATUS current 850 DESCRIPTION 851 "An entry in this table is created by a LMP-enabled device for 852 every control channel. Whenever a new entry is created with 853 lmpCcIsIf set to true(2), then a corresponding entry is 854 created in ifTable as well (see RFC 2863)." 855 INDEX { lmpCcId } 856 ::= { lmpControlChannelTable 1 } 858 LmpControlChannelEntry ::= SEQUENCE { 859 lmpCcId Unsigned32, 860 lmpCcUnderlyingIfIndex InterfaceIndexOrZero, 861 lmpCcIsIf TruthValue, 862 lmpCcNbrNodeId LmpNodeId, 863 lmpCcRemoteId Unsigned32, 864 lmpCcRemoteAddressType InetAddressType, 865 lmpCcRemoteIpAddr InetAddress, 866 lmpCcSetupRole INTEGER, 867 lmpCcAuthentication TruthValue, 868 lmpCcHelloInterval LmpInterval, 869 lmpCcHelloIntervalMin LmpInterval, 870 lmpCcHelloIntervalMax LmpInterval, 871 lmpCcHelloIntervalNegotiated LmpInterval, 872 lmpCcHelloDeadInterval LmpInterval, 873 lmpCcHelloDeadIntervalMin LmpInterval, 874 lmpCcHelloDeadIntervalMax LmpInterval, 875 lmpCcHelloDeadIntervalNegotiated LmpInterval, 876 lmpCcLastChange TimeTicks, 877 lmpCcAdminStatus INTEGER, 878 lmpCcOperStatus INTEGER, 879 lmpCcRowStatus RowStatus, 880 lmpCcStorageType StorageType 881 } 883 lmpCcId OBJECT-TYPE 884 SYNTAX Unsigned32 (1..4294967295) 885 MAX-ACCESS not-accessible 886 STATUS current 887 DESCRIPTION 888 "This value represents the local control channel identifier. 889 The control channel identifier is a non-zero 32 bit number." 890 ::= { lmpControlChannelEntry 1 } 892 lmpCcUnderlyingIfIndex OBJECT-TYPE 893 SYNTAX InterfaceIndexOrZero 894 MAX-ACCESS read-create 895 STATUS current 896 DESCRIPTION 897 "If lmpCcIsIf is set to true(1), this object carries the 898 index into the ifTable of the entry that represents the 899 LMP interface over which LMP will transmit its traffic. 901 If this object is set to zero, but lmpCcIsIf is set to 902 true(1), the control channel is not currently associated 903 with any underlying interface and the control channel's 904 operational status must not be up(1), nor should the 905 control channel forward or receive traffic. 906 If lmpCcIsIf is set to false(2), this object should be set 907 to zero and should be ignored." 908 ::= { lmpControlChannelEntry 2 } 910 lmpCcIsIf OBJECT-TYPE 911 SYNTAX TruthValue 912 MAX-ACCESS read-create 913 STATUS current 914 DESCRIPTION 915 "In implementations where the control channels are modeled 916 as interfaces, the value of this object is true(1) and 917 this control channel is represented by an interface in 918 the interfaces group table as indicated by the value of 919 lmpCcUnderlyingIfIndex. If control channels are not 920 modeled as interfaces, the value of this object is 921 false(2) and there is no corresponding interface for 922 this control channel in the interfaces group table, 923 and the value of lmpCcUnderlyingIfIndex should be 924 ignored." 925 ::= { lmpControlChannelEntry 3 } 927 lmpCcNbrNodeId OBJECT-TYPE 928 SYNTAX LmpNodeId 929 MAX-ACCESS read-create 930 STATUS current 931 DESCRIPTION 932 "This is the Node ID of the control channel remote node. 933 This value is either configured or gets created by the node 934 when a Config message is received or when an outgoing Config 935 message is acknowledged by the remote node." 936 ::= { lmpControlChannelEntry 4 } 938 lmpCcRemoteId OBJECT-TYPE 939 SYNTAX Unsigned32 940 MAX-ACCESS read-only 941 STATUS current 942 DESCRIPTION 943 "This value represents the remote control channel identifier 944 (32 bit number). It is determined during the negotiation 945 phase. A value of zero means that the remote control channel 946 identifier has not yet been learnt." 947 ::= { lmpControlChannelEntry 5 } 949 lmpCcRemoteAddressType OBJECT-TYPE 950 SYNTAX InetAddressType 951 MAX-ACCESS read-create 952 STATUS current 953 DESCRIPTION 954 "This value represents the remote control channel IP address 955 type. In point-to-point configuration, this value can be set 956 to unknown(0)." 957 ::= { lmpControlChannelEntry 6 } 959 lmpCcRemoteIpAddr OBJECT-TYPE 960 SYNTAX InetAddress 961 MAX-ACCESS read-create 962 STATUS current 963 DESCRIPTION 964 "This value represents the remote control channel Internet 965 address for numbered control channel. The type of this 966 address is determined by lmpCcRemoteAddressType. 967 Control channel must be numbered on non point-to-point 968 configuration. For point-to-point configuration, the 969 remote control channel address can be of type unknown 970 in which case this object must be a zero length string. The 971 lmpCcRemoteId object then identifies the unnumbered 972 address." 973 ::= { lmpControlChannelEntry 7 } 975 lmpCcSetupRole OBJECT-TYPE 976 SYNTAX INTEGER { active(1), passive(2) } 977 MAX-ACCESS read-create 978 STATUS current 979 DESCRIPTION 980 "The role that this node should take during establishment 981 of this control channel. An active node will initiate 982 establishment. A passive node will wait for the remote node 983 to initiate. A pair of nodes that both take the passive role 984 will never establish communications." 985 DEFVAL { active } 986 ::= { lmpControlChannelEntry 8 } 988 lmpCcAuthentication OBJECT-TYPE 989 SYNTAX TruthValue 990 MAX-ACCESS read-create 991 STATUS current 992 DESCRIPTION 993 "This object indicates whether the control channel must use 994 authentication." 995 REFERENCE 996 "Link Management Protocol, RFC xxx" 997 -- RFC Editor to fill in RFC number that will be assigned to 998 -- [LMP] 999 ::= { lmpControlChannelEntry 9 } 1001 lmpCcHelloInterval OBJECT-TYPE 1002 SYNTAX LmpInterval 1003 MAX-ACCESS read-create 1004 STATUS current 1005 DESCRIPTION 1006 "This object specifies the value of the HelloInterval 1007 parameter. The default value for this object should be 1008 set to lmpCcHelloIntervalDefault." 1009 ::= { lmpControlChannelEntry 10 } 1011 lmpCcHelloIntervalMin OBJECT-TYPE 1012 SYNTAX LmpInterval 1013 MAX-ACCESS read-create 1014 STATUS current 1015 DESCRIPTION 1016 "This object specifies the minimum value for the 1017 HelloInterval parameter. The default value for this 1018 object should be set to lmpCcHelloIntervalMinDefault." 1019 ::= { lmpControlChannelEntry 11 } 1021 lmpCcHelloIntervalMax OBJECT-TYPE 1022 SYNTAX LmpInterval 1023 MAX-ACCESS read-create 1024 STATUS current 1025 DESCRIPTION 1026 "This object specifies the maximum value for the 1027 HelloInterval parameter. The default value for this 1028 object should be set to lmpCcHelloIntervalMaxDefault." 1029 ::= { lmpControlChannelEntry 12 } 1031 lmpCcHelloIntervalNegotiated OBJECT-TYPE 1032 SYNTAX LmpInterval 1033 MAX-ACCESS read-only 1034 STATUS current 1035 DESCRIPTION 1036 "Once the control channel is active, this object represents 1037 the negotiated HelloInterval value." 1038 ::= { lmpControlChannelEntry 13 } 1040 lmpCcHelloDeadInterval OBJECT-TYPE 1041 SYNTAX LmpInterval 1042 MAX-ACCESS read-create 1043 STATUS current 1044 DESCRIPTION 1045 "This object specifies the value of the HelloDeadInterval 1046 parameter. The default value for this object should be 1047 set to lmpCcHelloDeadIntervalDefault." 1048 ::= { lmpControlChannelEntry 14 } 1050 lmpCcHelloDeadIntervalMin OBJECT-TYPE 1051 SYNTAX LmpInterval 1052 MAX-ACCESS read-create 1053 STATUS current 1054 DESCRIPTION 1055 "This object specifies the minimum value for the 1056 HelloDeadInterval parameter. The default value for this 1057 object should be set to lmpCcHelloDeadIntervalMinDefault." 1058 ::= { lmpControlChannelEntry 15 } 1060 lmpCcHelloDeadIntervalMax OBJECT-TYPE 1061 SYNTAX LmpInterval 1062 MAX-ACCESS read-create 1063 STATUS current 1064 DESCRIPTION 1065 "This object specifies the maximum value for the 1066 HelloDeadInterval parameter. The default value for this 1067 object should be set to lmpCcHelloIntervalMaxDefault." 1068 ::= { lmpControlChannelEntry 16 } 1070 lmpCcHelloDeadIntervalNegotiated OBJECT-TYPE 1071 SYNTAX LmpInterval 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1075 "Once the control channel is active, this object represents 1076 the negotiated HelloDeadInterval value." 1077 ::= { lmpControlChannelEntry 17 } 1079 lmpCcLastChange OBJECT-TYPE 1080 SYNTAX TimeTicks 1081 MAX-ACCESS read-only 1082 STATUS current 1083 DESCRIPTION 1084 "The value of sysUpTime at the time the control channel entered 1085 its current operational state. If the current state was 1086 entered prior to the last re-initialization of the local 1087 network management subsystem, then this object contains a 1088 zero value." 1089 ::= { lmpControlChannelEntry 18 } 1091 lmpCcAdminStatus OBJECT-TYPE 1092 SYNTAX INTEGER { up(1), down(2) } 1093 MAX-ACCESS read-create 1094 STATUS current 1095 DESCRIPTION 1096 "The desired operational status of this control channel." 1097 ::= { lmpControlChannelEntry 19 } 1099 lmpCcOperStatus OBJECT-TYPE 1100 SYNTAX INTEGER { 1101 up(1), 1102 down(2), 1103 configSnd(3), 1104 configRcv(4), 1105 active(5), 1106 goingDown(6) 1107 } 1108 MAX-ACCESS read-only 1109 STATUS current 1110 DESCRIPTION 1111 "The actual operational status of this control channel." 1112 ::= { lmpControlChannelEntry 20 } 1114 lmpCcRowStatus OBJECT-TYPE 1115 SYNTAX RowStatus 1116 MAX-ACCESS read-create 1117 STATUS current 1118 DESCRIPTION 1119 "This variable is used to create, modify, and/or 1120 delete a row in this table. None of the writable objects 1121 in a row can be changed if the status is active(1). 1122 All read-create objects must have valid and consistent 1123 values before the row can be activated." 1124 ::= { lmpControlChannelEntry 21 } 1126 lmpCcStorageType OBJECT-TYPE 1127 SYNTAX StorageType 1128 MAX-ACCESS read-create 1129 STATUS current 1130 DESCRIPTION 1131 "The storage type for this conceptual row in the 1132 lmpControlChannelTable. Conceptual rows having the value 1133 'permanent' need not allow write-access to any 1134 columnar object in the row." 1135 DEFVAL { nonVolatile } 1136 ::= { lmpControlChannelEntry 22 } 1138 -- End of lmpControlChannelTable 1139 -- LMP Control Channel Performance Table 1141 lmpControlChannelPerfTable OBJECT-TYPE 1142 SYNTAX SEQUENCE OF LmpControlChannelPerfEntry 1143 MAX-ACCESS not-accessible 1144 STATUS current 1145 DESCRIPTION 1146 "This table specifies LMP control channel performance 1147 counters." 1148 ::= { lmpObjects 11 } 1150 lmpControlChannelPerfEntry OBJECT-TYPE 1151 SYNTAX LmpControlChannelPerfEntry 1152 MAX-ACCESS not-accessible 1153 STATUS current 1154 DESCRIPTION 1155 "An entry in this table is created by a LMP-enabled device for 1156 every control channel. lmpCcCounterDiscontinuityTime is used 1157 to indicate potential discontinuity for all counter objects 1158 in this table." 1159 INDEX { lmpCcId } 1160 ::= { lmpControlChannelPerfTable 1 } 1162 LmpControlChannelPerfEntry ::= SEQUENCE { 1163 lmpCcInOctets Counter32, 1164 lmpCcInDiscards Counter32, 1165 lmpCcInErrors Counter32, 1166 lmpCcOutOctets Counter32, 1167 lmpCcOutDiscards Counter32, 1168 lmpCcOutErrors Counter32, 1169 lmpCcConfigReceived Counter32, 1170 lmpCcConfigSent Counter32, 1171 lmpCcConfigRetransmit Counter32, 1172 lmpCcConfigAckReceived Counter32, 1173 lmpCcConfigAckSent Counter32, 1174 lmpCcConfigNackReceived Counter32, 1175 lmpCcConfigNackSent Counter32, 1176 lmpCcHelloReceived Counter32, 1177 lmpCcHelloSent Counter32, 1178 lmpCcBeginVerifyReceived Counter32, 1179 lmpCcBeginVerifySent Counter32, 1180 lmpCcBeginVerifyRetransmit Counter32, 1181 lmpCcBeginVerifyAckReceived Counter32, 1182 lmpCcBeginVerifyAckSent Counter32, 1183 lmpCcBeginVerifyNackReceived Counter32, 1184 lmpCcBeginVerifyNackSent Counter32, 1185 lmpCcEndVerifyReceived Counter32, 1186 lmpCcEndVerifySent Counter32, 1187 lmpCcEndVerifyRetransmit Counter32, 1188 lmpCcEndVerifyAckReceived Counter32, 1189 lmpCcEndVerifyAckSent Counter32, 1190 lmpCcTestStatusSuccessReceived Counter32, 1191 lmpCcTestStatusSuccessSent Counter32, 1192 lmpCcTestStatusSuccessRetransmit Counter32, 1193 lmpCcTestStatusFailureReceived Counter32, 1194 lmpCcTestStatusFailureSent Counter32, 1195 lmpCcTestStatusFailureRetransmit Counter32, 1196 lmpCcTestStatusAckReceived Counter32, 1197 lmpCcTestStatusAckSent Counter32, 1198 lmpCcLinkSummaryReceived Counter32, 1199 lmpCcLinkSummarySent Counter32, 1200 lmpCcLinkSummaryRetransmit Counter32, 1201 lmpCcLinkSummaryAckReceived Counter32, 1202 lmpCcLinkSummaryAckSent Counter32, 1203 lmpCcLinkSummaryNackReceived Counter32, 1204 lmpCcLinkSummaryNackSent Counter32, 1205 lmpCcChannelStatusReceived Counter32, 1206 lmpCcChannelStatusSent Counter32, 1207 lmpCcChannelStatusRetransmit Counter32, 1208 lmpCcChannelStatusAckReceived Counter32, 1209 lmpCcChannelStatusAckSent Counter32, 1210 lmpCcChannelStatusReqReceived Counter32, 1211 lmpCcChannelStatusReqSent Counter32, 1212 lmpCcChannelStatusReqRetransmit Counter32, 1213 lmpCcChannelStatusRspReceived Counter32, 1214 lmpCcChannelStatusRspSent Counter32, 1215 lmpCcCounterDiscontinuityTime TimeStamp 1216 } 1218 lmpCcInOctets OBJECT-TYPE 1219 SYNTAX Counter32 1220 MAX-ACCESS read-only 1221 STATUS current 1222 DESCRIPTION 1223 "The total number of LMP message octets received on the 1224 control channel." 1225 ::= { lmpControlChannelPerfEntry 1 } 1227 lmpCcInDiscards OBJECT-TYPE 1228 SYNTAX Counter32 1229 MAX-ACCESS read-only 1230 STATUS current 1231 DESCRIPTION 1232 "The number of inbound packets which were chosen to be 1233 discarded even though no errors had been detected. One 1234 possible reason for discarding such a packet could be to 1235 free up buffer space." 1236 ::= { lmpControlChannelPerfEntry 2 } 1238 lmpCcInErrors OBJECT-TYPE 1239 SYNTAX Counter32 1240 MAX-ACCESS read-only 1241 STATUS current 1242 DESCRIPTION 1243 "The number of inbound packets that contained errors 1244 preventing them from being processed by LMP." 1245 ::= { lmpControlChannelPerfEntry 3 } 1247 lmpCcOutOctets OBJECT-TYPE 1248 SYNTAX Counter32 1249 MAX-ACCESS read-only 1250 STATUS current 1251 DESCRIPTION 1252 "The total number of LMP message octets transmitted out of 1253 the control channel." 1254 ::= { lmpControlChannelPerfEntry 4 } 1256 lmpCcOutDiscards OBJECT-TYPE 1257 SYNTAX Counter32 1258 MAX-ACCESS read-only 1259 STATUS current 1260 DESCRIPTION 1261 "The number of outbound packets which were chosen to be 1262 discarded even though no errors had been detected to 1263 prevent their being transmitted. One possible reason 1264 for discarding such a packet could be to free up buffer 1265 space." 1266 ::= { lmpControlChannelPerfEntry 5 } 1268 lmpCcOutErrors OBJECT-TYPE 1269 SYNTAX Counter32 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "The number of outbound packets that could not be 1274 transmitted because of errors." 1275 ::= { lmpControlChannelPerfEntry 6 } 1277 lmpCcConfigReceived OBJECT-TYPE 1278 SYNTAX Counter32 1279 MAX-ACCESS read-only 1280 STATUS current 1281 DESCRIPTION 1282 "This object counts the number of Config messages that have 1283 been received on this control channel." 1284 ::= { lmpControlChannelPerfEntry 7 } 1286 lmpCcConfigSent OBJECT-TYPE 1287 SYNTAX Counter32 1288 MAX-ACCESS read-only 1289 STATUS current 1290 DESCRIPTION 1291 "This object counts the number of Config messages that have 1292 been sent on this control channel." 1293 ::= { lmpControlChannelPerfEntry 8 } 1295 lmpCcConfigRetransmit OBJECT-TYPE 1296 SYNTAX Counter32 1297 MAX-ACCESS read-only 1298 STATUS current 1299 DESCRIPTION 1300 "This object counts the number of Config messages that 1301 have been retransmitted over this control channel." 1302 ::= { lmpControlChannelPerfEntry 9 } 1304 lmpCcConfigAckReceived OBJECT-TYPE 1305 SYNTAX Counter32 1306 MAX-ACCESS read-only 1307 STATUS current 1308 DESCRIPTION 1309 "This object counts the number of ConfigAck messages that have 1310 been received on this control channel." 1311 ::= { lmpControlChannelPerfEntry 10 } 1313 lmpCcConfigAckSent OBJECT-TYPE 1314 SYNTAX Counter32 1315 MAX-ACCESS read-only 1316 STATUS current 1317 DESCRIPTION 1318 "This object counts the number of ConfigAck messages that have 1319 been sent on this control channel." 1320 ::= { lmpControlChannelPerfEntry 11 } 1322 lmpCcConfigNackReceived OBJECT-TYPE 1323 SYNTAX Counter32 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "This object counts the number of ConfigNack messages that have 1328 been received on this control channel." 1329 ::= { lmpControlChannelPerfEntry 12 } 1331 lmpCcConfigNackSent OBJECT-TYPE 1332 SYNTAX Counter32 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "This object counts the number of ConfigNack messages that have 1337 been sent on this control channel." 1338 ::= { lmpControlChannelPerfEntry 13 } 1340 lmpCcHelloReceived OBJECT-TYPE 1341 SYNTAX Counter32 1342 MAX-ACCESS read-only 1343 STATUS current 1344 DESCRIPTION 1345 "This object counts the number of Hello messages that have 1346 been received on this control channel." 1347 ::= { lmpControlChannelPerfEntry 14 } 1349 lmpCcHelloSent OBJECT-TYPE 1350 SYNTAX Counter32 1351 MAX-ACCESS read-only 1352 STATUS current 1353 DESCRIPTION 1354 "This object counts the number of Hello messages that have 1355 been sent on this control channel." 1356 ::= { lmpControlChannelPerfEntry 15 } 1358 lmpCcBeginVerifyReceived OBJECT-TYPE 1359 SYNTAX Counter32 1360 MAX-ACCESS read-only 1361 STATUS current 1362 DESCRIPTION 1363 "This object counts the number of BeginVerify messages that have 1364 been received on this control channel." 1365 ::= { lmpControlChannelPerfEntry 16 } 1367 lmpCcBeginVerifySent OBJECT-TYPE 1368 SYNTAX Counter32 1369 MAX-ACCESS read-only 1370 STATUS current 1371 DESCRIPTION 1372 "This object counts the number of BeginVerify messages that have 1373 been sent on this control channel." 1374 ::= { lmpControlChannelPerfEntry 17 } 1376 lmpCcBeginVerifyRetransmit OBJECT-TYPE 1377 SYNTAX Counter32 1378 MAX-ACCESS read-only 1379 STATUS current 1380 DESCRIPTION 1381 "This object counts the number of BeginVerify messages that 1382 have been retransmitted over this control channel." 1383 ::= { lmpControlChannelPerfEntry 18 } 1385 lmpCcBeginVerifyAckReceived OBJECT-TYPE 1386 SYNTAX Counter32 1387 MAX-ACCESS read-only 1388 STATUS current 1389 DESCRIPTION 1390 "This object counts the number of BeginVerifyAck messages that 1391 have been received on this control channel." 1392 ::= { lmpControlChannelPerfEntry 19 } 1394 lmpCcBeginVerifyAckSent OBJECT-TYPE 1395 SYNTAX Counter32 1396 MAX-ACCESS read-only 1397 STATUS current 1398 DESCRIPTION 1399 "This object counts the number of BeginVerifyAck messages that 1400 have been sent on this control channel." 1401 ::= { lmpControlChannelPerfEntry 20 } 1403 lmpCcBeginVerifyNackReceived OBJECT-TYPE 1404 SYNTAX Counter32 1405 MAX-ACCESS read-only 1406 STATUS current 1407 DESCRIPTION 1408 "This object counts the number of BeginVerifyNack messages that 1409 have been received on this control channel." 1410 ::= { lmpControlChannelPerfEntry 21 } 1412 lmpCcBeginVerifyNackSent OBJECT-TYPE 1413 SYNTAX Counter32 1414 MAX-ACCESS read-only 1415 STATUS current 1416 DESCRIPTION 1417 "This object counts the number of BeginVerifyNack messages that 1418 have been sent on this control channel." 1419 ::= { lmpControlChannelPerfEntry 22 } 1421 lmpCcEndVerifyReceived OBJECT-TYPE 1422 SYNTAX Counter32 1423 MAX-ACCESS read-only 1424 STATUS current 1425 DESCRIPTION 1426 "This object counts the number of EndVerify messages that have 1427 been received on this control channel." 1428 ::= { lmpControlChannelPerfEntry 23 } 1430 lmpCcEndVerifySent OBJECT-TYPE 1431 SYNTAX Counter32 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "This object counts the number of EndVerify messages that have 1436 been sent on this control channel." 1437 ::= { lmpControlChannelPerfEntry 24 } 1439 lmpCcEndVerifyRetransmit OBJECT-TYPE 1440 SYNTAX Counter32 1441 MAX-ACCESS read-only 1442 STATUS current 1443 DESCRIPTION 1444 "This object counts the number of EndVerify messages that 1445 have been retransmitted over this control channel." 1446 ::= { lmpControlChannelPerfEntry 25 } 1448 lmpCcEndVerifyAckReceived OBJECT-TYPE 1449 SYNTAX Counter32 1450 MAX-ACCESS read-only 1451 STATUS current 1452 DESCRIPTION 1453 "This object counts the number of EndVerifyAck messages that 1454 have been received on this control channel." 1455 ::= { lmpControlChannelPerfEntry 26 } 1457 lmpCcEndVerifyAckSent OBJECT-TYPE 1458 SYNTAX Counter32 1459 MAX-ACCESS read-only 1460 STATUS current 1461 DESCRIPTION 1462 "This object counts the number of EndVerifyAck messages that 1463 have been sent on this control channel." 1464 ::= { lmpControlChannelPerfEntry 27 } 1466 lmpCcTestStatusSuccessReceived OBJECT-TYPE 1467 SYNTAX Counter32 1468 MAX-ACCESS read-only 1469 STATUS current 1470 DESCRIPTION 1471 "This object counts the number of TestStatusSuccess messages 1472 that have been received on this control channel." 1473 ::= { lmpControlChannelPerfEntry 28 } 1475 lmpCcTestStatusSuccessSent OBJECT-TYPE 1476 SYNTAX Counter32 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "This object counts the number of TestStatusSuccess messages 1481 that have been sent on this control channel." 1482 ::= { lmpControlChannelPerfEntry 29 } 1484 lmpCcTestStatusSuccessRetransmit OBJECT-TYPE 1485 SYNTAX Counter32 1486 MAX-ACCESS read-only 1487 STATUS current 1488 DESCRIPTION 1489 "This object counts the number of TestStatusSuccess messages 1490 that have been retransmitted over this control channel." 1491 ::= { lmpControlChannelPerfEntry 30 } 1493 lmpCcTestStatusFailureReceived OBJECT-TYPE 1494 SYNTAX Counter32 1495 MAX-ACCESS read-only 1496 STATUS current 1497 DESCRIPTION 1498 "This object counts the number of TestStatusFailure messages 1499 that have been received on this control channel." 1500 ::= { lmpControlChannelPerfEntry 31 } 1502 lmpCcTestStatusFailureSent OBJECT-TYPE 1503 SYNTAX Counter32 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "This object counts the number of TestStatusFailure messages 1508 that have been sent on this control channel." 1509 ::= { lmpControlChannelPerfEntry 32 } 1511 lmpCcTestStatusFailureRetransmit OBJECT-TYPE 1512 SYNTAX Counter32 1513 MAX-ACCESS read-only 1514 STATUS current 1515 DESCRIPTION 1516 "This object counts the number of TestStatusFailure messages 1517 that have been retransmitted over this control channel." 1518 ::= { lmpControlChannelPerfEntry 33 } 1520 lmpCcTestStatusAckReceived OBJECT-TYPE 1521 SYNTAX Counter32 1522 MAX-ACCESS read-only 1523 STATUS current 1524 DESCRIPTION 1525 "This object counts the number of TestStatusAck messages 1526 that have been received on this control channel." 1527 ::= { lmpControlChannelPerfEntry 34 } 1529 lmpCcTestStatusAckSent OBJECT-TYPE 1530 SYNTAX Counter32 1531 MAX-ACCESS read-only 1532 STATUS current 1533 DESCRIPTION 1534 "This object counts the number of TestStatusAck messages 1535 that have been sent on this control channel." 1536 ::= { lmpControlChannelPerfEntry 35 } 1538 lmpCcLinkSummaryReceived OBJECT-TYPE 1539 SYNTAX Counter32 1540 MAX-ACCESS read-only 1541 STATUS current 1542 DESCRIPTION 1543 "This object counts the number of LinkSummary messages 1544 that have been received on this control channel." 1545 ::= { lmpControlChannelPerfEntry 36 } 1547 lmpCcLinkSummarySent OBJECT-TYPE 1548 SYNTAX Counter32 1549 MAX-ACCESS read-only 1550 STATUS current 1551 DESCRIPTION 1552 "This object counts the number of LinkSummary messages 1553 that have been sent on this control channel." 1554 ::= { lmpControlChannelPerfEntry 37 } 1556 lmpCcLinkSummaryRetransmit OBJECT-TYPE 1557 SYNTAX Counter32 1558 MAX-ACCESS read-only 1559 STATUS current 1560 DESCRIPTION 1561 "This object counts the number of LinkSummary messages that 1562 have been retransmitted over this control channel." 1563 ::= { lmpControlChannelPerfEntry 38 } 1565 lmpCcLinkSummaryAckReceived OBJECT-TYPE 1566 SYNTAX Counter32 1567 MAX-ACCESS read-only 1568 STATUS current 1569 DESCRIPTION 1570 "This object counts the number of LinkSummaryAck messages 1571 that have been received on this control channel." 1572 ::= { lmpControlChannelPerfEntry 39 } 1574 lmpCcLinkSummaryAckSent OBJECT-TYPE 1575 SYNTAX Counter32 1576 MAX-ACCESS read-only 1577 STATUS current 1578 DESCRIPTION 1579 "This object counts the number of LinkSummaryAck messages 1580 that have been sent on this control channel." 1581 ::= { lmpControlChannelPerfEntry 40 } 1583 lmpCcLinkSummaryNackReceived OBJECT-TYPE 1584 SYNTAX Counter32 1585 MAX-ACCESS read-only 1586 STATUS current 1587 DESCRIPTION 1588 "This object counts the number of LinkSummaryNack messages 1589 that have been received on this control channel." 1590 ::= { lmpControlChannelPerfEntry 41 } 1592 lmpCcLinkSummaryNackSent OBJECT-TYPE 1593 SYNTAX Counter32 1594 MAX-ACCESS read-only 1595 STATUS current 1596 DESCRIPTION 1597 "This object counts the number of LinkSummaryNack messages 1598 that have been sent on this control channel." 1599 ::= { lmpControlChannelPerfEntry 42 } 1601 lmpCcChannelStatusReceived OBJECT-TYPE 1602 SYNTAX Counter32 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "This object counts the number of ChannelStatus messages 1607 that have been received on this control channel." 1608 ::= { lmpControlChannelPerfEntry 43 } 1610 lmpCcChannelStatusSent OBJECT-TYPE 1611 SYNTAX Counter32 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "This object counts the number of ChannelStatus messages 1616 that have been sent on this control channel." 1617 ::= { lmpControlChannelPerfEntry 44 } 1619 lmpCcChannelStatusRetransmit OBJECT-TYPE 1620 SYNTAX Counter32 1621 MAX-ACCESS read-only 1622 STATUS current 1623 DESCRIPTION 1624 "This object counts the number of ChannelStatus messages 1625 that have been retransmitted on this control channel." 1626 ::= { lmpControlChannelPerfEntry 45 } 1628 lmpCcChannelStatusAckReceived OBJECT-TYPE 1629 SYNTAX Counter32 1630 MAX-ACCESS read-only 1631 STATUS current 1632 DESCRIPTION 1633 "This object counts the number of ChannelStatusAck messages 1634 that have been received on this control channel." 1635 ::= { lmpControlChannelPerfEntry 46 } 1637 lmpCcChannelStatusAckSent OBJECT-TYPE 1638 SYNTAX Counter32 1639 MAX-ACCESS read-only 1640 STATUS current 1641 DESCRIPTION 1642 "This object counts the number of ChannelStatus messages 1643 that have been sent on this control channel." 1644 ::= { lmpControlChannelPerfEntry 47 } 1646 lmpCcChannelStatusReqReceived OBJECT-TYPE 1647 SYNTAX Counter32 1648 MAX-ACCESS read-only 1649 STATUS current 1650 DESCRIPTION 1651 "This object counts the number of ChannelStatusRequest messages 1652 that have been received on this control channel." 1653 ::= { lmpControlChannelPerfEntry 48 } 1655 lmpCcChannelStatusReqSent OBJECT-TYPE 1656 SYNTAX Counter32 1657 MAX-ACCESS read-only 1658 STATUS current 1659 DESCRIPTION 1660 "This object counts the number of ChannelStatusRequest messages 1661 that have been sent on this control channel." 1662 ::= { lmpControlChannelPerfEntry 49 } 1664 lmpCcChannelStatusReqRetransmit OBJECT-TYPE 1665 SYNTAX Counter32 1666 MAX-ACCESS read-only 1667 STATUS current 1668 DESCRIPTION 1669 "This object counts the number of ChannelStatusRequest messages 1670 that have been retransmitted on this control channel." 1671 ::= { lmpControlChannelPerfEntry 50 } 1673 lmpCcChannelStatusRspReceived OBJECT-TYPE 1674 SYNTAX Counter32 1675 MAX-ACCESS read-only 1676 STATUS current 1677 DESCRIPTION 1678 "This object counts the number of ChannelStatusResponse messages 1679 that have been received on this control channel." 1680 ::= { lmpControlChannelPerfEntry 51 } 1682 lmpCcChannelStatusRspSent OBJECT-TYPE 1683 SYNTAX Counter32 1684 MAX-ACCESS read-only 1685 STATUS current 1686 DESCRIPTION 1687 "This object counts the number of ChannelStatusResponse messages 1688 that have been sent on this control channel." 1689 ::= { lmpControlChannelPerfEntry 52 } 1691 lmpCcCounterDiscontinuityTime OBJECT-TYPE 1692 SYNTAX TimeStamp 1693 MAX-ACCESS read-only 1694 STATUS current 1695 DESCRIPTION 1696 "The value of sysUpTime on the most recent occasion at which 1697 any one or more of this control channel's counters suffered a 1698 discontinuity. The relevant counters are the specific 1699 instances associated with this control channel of any 1700 Counter32 object contained in the lmpControlChannelPerfTable. 1701 If no such discontinuities have occurred since the last re- 1702 initialization of the local management subsystem, then this 1703 object contains a zero value." 1704 ::= { lmpControlChannelPerfEntry 53 } 1706 -- End of lmpControlChannelPerfTable 1708 -- LMP TE Link Table 1710 lmpTeLinkTable OBJECT-TYPE 1711 SYNTAX SEQUENCE OF LmpTeLinkEntry 1712 MAX-ACCESS not-accessible 1713 STATUS current 1714 DESCRIPTION 1715 "This table specifies the LMP specific TE link information. 1716 Overall TE link information is kept in three separate tables: 1717 ifTable, for interface specific information, lmpTeLinkTable 1718 for LMP specific information and teLinkTable for generic 1719 TE link information. ifIndex is the common index to all 1720 tables." 1721 ::= { lmpObjects 12 } 1723 lmpTeLinkEntry OBJECT-TYPE 1724 SYNTAX LmpTeLinkEntry 1725 MAX-ACCESS not-accessible 1726 STATUS current 1727 DESCRIPTION 1728 "An entry in this table exists for each ifEntry with an 1729 ifType of teLink(200) that is managed by LMP. An ifEntry with 1730 an ifIndex must exist before the corresponding lmpTeLinkEntry is 1731 created. If a TE link entry in the ifTable is destroyed, then so 1732 is the corresponding entry in the lmpTeLinkTable. The 1733 administrative status value is controlled from the ifEntry. 1734 Setting the administrative status to testing prompts LMP to 1735 start link verification on the TE link. Information about the TE 1736 link that is not LMP specific is contained in teLinkTable of the 1737 TE-LINK-STD-MIB MIB module." 1738 INDEX { ifIndex } 1739 ::= { lmpTeLinkTable 1 } 1741 LmpTeLinkEntry ::= SEQUENCE { 1742 lmpTeLinkNbrRemoteNodeId LmpNodeId, 1743 lmpTeLinkVerification TruthValue, 1744 lmpTeLinkFaultManagement TruthValue, 1745 lmpTeLinkDwdm TruthValue, 1746 lmpTeLinkOperStatus INTEGER, 1747 lmpTeLinkRowStatus RowStatus, 1748 lmpTeLinkStorageType StorageType 1749 } 1751 lmpTeLinkNbrRemoteNodeId OBJECT-TYPE 1752 SYNTAX LmpNodeId 1753 MAX-ACCESS read-create 1754 STATUS current 1755 DESCRIPTION 1756 "This is the Node ID of the TE link remote node. This value 1757 may be learned during control channel parameter negotiation 1758 phase (in the Config message). Node ID is an address which 1759 type must be IPv4." 1760 ::= { lmpTeLinkEntry 1 } 1762 lmpTeLinkVerification OBJECT-TYPE 1763 SYNTAX TruthValue 1764 MAX-ACCESS read-create 1765 STATUS current 1766 DESCRIPTION 1767 "This object indicates if the LMP link verification procedure 1768 is enabled for this TE link." 1769 REFERENCE 1770 "Link Management Protocol, RFC xxx" 1771 -- RFC Editor to fill in RFC number that will be assigned to 1772 -- [LMP] 1773 ::= { lmpTeLinkEntry 2 } 1775 lmpTeLinkFaultManagement OBJECT-TYPE 1776 SYNTAX TruthValue 1777 MAX-ACCESS read-create 1778 STATUS current 1779 DESCRIPTION 1780 "This object indicates if the LMP fault management procedure 1781 is enabled on this TE link." 1782 REFERENCE 1783 "Link Management Protocol, RFC xxx" 1784 -- RFC Editor to fill in RFC number that will be assigned to 1785 -- [LMP] 1786 ::= { lmpTeLinkEntry 3 } 1788 lmpTeLinkDwdm OBJECT-TYPE 1789 SYNTAX TruthValue 1790 MAX-ACCESS read-create 1791 STATUS current 1792 DESCRIPTION 1793 "This object indicates if the LMP DWDM procedure is enabled 1794 on this TE link." 1795 REFERENCE 1796 "Link Management Protocol (LMP) for Dense Wavelength Division 1797 Multiplexing (DWDM) Optical Line Systems, RFC xxx" 1798 -- RFC Editor to fill in RFC number that will be assigned to 1799 -- [LMP-WDM] 1800 ::= { lmpTeLinkEntry 4 } 1802 lmpTeLinkOperStatus OBJECT-TYPE 1803 SYNTAX INTEGER { 1804 up(1), down(2), testing(3), init(4), degraded(5) 1805 } 1806 MAX-ACCESS read-only 1807 STATUS current 1808 DESCRIPTION 1809 "The actual operational status of this TE link. The status 1810 is set to testing when the TE link is performing link 1811 verification. A degraded state indicates that there are 1812 no active control channel between the pair of nodes that 1813 form the endpoints of the TE link, but yet at least one 1814 data-bearing links on the TE link is allocated." 1815 ::= { lmpTeLinkEntry 5 } 1817 lmpTeLinkRowStatus OBJECT-TYPE 1818 SYNTAX RowStatus 1819 MAX-ACCESS read-create 1820 STATUS current 1821 DESCRIPTION 1822 "This variable is used to create, modify, and/or 1823 delete a row in this table. None of the writable objects 1824 in a row can be changed if the status is active(1). 1825 All read-create objects must have valid and consistent 1826 values before the row can be activated." 1827 ::= { lmpTeLinkEntry 6 } 1829 lmpTeLinkStorageType OBJECT-TYPE 1830 SYNTAX StorageType 1831 MAX-ACCESS read-create 1832 STATUS current 1833 DESCRIPTION 1834 "The storage type for this conceptual row in the 1835 lmpTeLinkTable. Conceptual rows having the value 1836 'permanent' need not allow write-access to any 1837 columnar object in the row." 1838 DEFVAL { nonVolatile } 1839 ::= { lmpTeLinkEntry 7 } 1841 -- End of lmpTeLinkTable 1843 lmpGlobalLinkVerificationInterval OBJECT-TYPE 1844 SYNTAX Unsigned32 1845 UNITS "milliseconds" 1846 MAX-ACCESS read-write 1847 STATUS current 1848 DESCRIPTION 1849 "This object indicates how often the link verification 1850 procedure is executed. The interval is in milliseconds. 1851 A value of 0 is used to indicate that the link 1852 verification procedure should not be executed. The 1853 interval specified in this object should be large enough 1854 to allow the verification procedure to be completed 1855 before the start of the next interval. 1856 Implementations should save the value of this object in 1857 persistent memory so that it survives restarts or reboot." 1858 ::= { lmpObjects 13 } 1860 -- LMP Link Verification Table 1862 lmpLinkVerificationTable OBJECT-TYPE 1863 SYNTAX SEQUENCE OF LmpLinkVerificationEntry 1864 MAX-ACCESS not-accessible 1865 STATUS current 1866 DESCRIPTION 1867 "This table specifies TE link information associated with the 1868 LMP verification procedure." 1869 ::= { lmpObjects 14 } 1871 lmpLinkVerificationEntry OBJECT-TYPE 1872 SYNTAX LmpLinkVerificationEntry 1873 MAX-ACCESS not-accessible 1874 STATUS current 1875 DESCRIPTION 1876 "An entry in this table is created by a LMP-enabled device for 1877 every TE link that supports the LMP verification 1878 procedure." 1879 INDEX { ifIndex } 1880 ::= { lmpLinkVerificationTable 1 } 1882 LmpLinkVerificationEntry ::= SEQUENCE { 1883 lmpLinkVerifyInterval LmpInterval, 1884 lmpLinkVerifyDeadInterval LmpInterval, 1885 lmpLinkVerifyTransportMechanism BITS, 1886 lmpLinkVerifyAllLinks TruthValue, 1887 lmpLinkVerifyTransmissionRate Unsigned32, 1888 lmpLinkVerifyWavelength Unsigned32, 1889 lmpLinkVerifyRowStatus RowStatus, 1890 lmpLinkVerifyStorageType StorageType 1891 } 1893 lmpLinkVerifyInterval OBJECT-TYPE 1894 SYNTAX LmpInterval 1895 MAX-ACCESS read-create 1896 STATUS current 1897 DESCRIPTION 1898 "This object specifies the VerifyInterval parameter used 1899 in the LMP link verification process. It indicates the 1900 interval at which the Test messages are sent." 1901 REFERENCE 1902 "Link Management Protocol, RFC xxx" 1903 -- RFC Editor to fill in RFC number that will be assigned to 1904 -- [LMP] 1905 ::= { lmpLinkVerificationEntry 1 } 1907 lmpLinkVerifyDeadInterval OBJECT-TYPE 1908 SYNTAX LmpInterval 1909 MAX-ACCESS read-create 1910 STATUS current 1911 DESCRIPTION 1912 "This object specifies the VerifyDeadInterval parameter used 1913 in the verification of the physical connectivity of data- 1914 bearing links. It specifies the observation period used to 1915 detect a Test message at the remote node." 1916 REFERENCE 1917 "Link Management Protocol, RFC xxx" 1918 -- RFC Editor to fill in RFC number that will be assigned to 1919 -- [LMP] 1920 ::= { lmpLinkVerificationEntry 2 } 1922 lmpLinkVerifyTransportMechanism OBJECT-TYPE 1923 SYNTAX BITS { 1924 -- All encoding types: 1925 payload(0), 1926 -- SONET/SDH encoding type: 1927 dccSectionOverheadBytes(1), 1928 dccLineOverheadBytes(2), 1929 j0Trace(3), 1930 j1Trace(4), 1931 j2Trace(5) 1932 } 1933 MAX-ACCESS read-create 1934 STATUS current 1935 DESCRIPTION 1936 "This defines the transport mechanism for the Test messages. The 1937 scope of this bit mask is restricted to each link encoding 1938 type. The local node will set the bits corresponding to the 1939 various mechanisms it can support for transmitting LMP Test 1940 messages. The receiver chooses the appropriate mechanism in the 1941 BeginVerifyAck message." 1942 REFERENCE 1943 "Link Management Protocol, RFC xxx and 1944 SONET/SDH Encoding for Link Management Protocol (LMP) 1945 Test Messages, RFC xxx" 1946 -- RFC Editor to fill in RFC number that will be assigned to 1947 -- [LMP] and [LMP-TEST] 1948 ::= { lmpLinkVerificationEntry 3 } 1950 lmpLinkVerifyAllLinks OBJECT-TYPE 1951 SYNTAX TruthValue 1952 MAX-ACCESS read-create 1953 STATUS current 1954 DESCRIPTION 1955 "A value of true(2) for this object indicates that the 1956 verification process checks all unallocated links, otherwise 1957 only the new ports or component links that have been added to 1958 this TE link are verified." 1959 ::= { lmpLinkVerificationEntry 4 } 1961 lmpLinkVerifyTransmissionRate OBJECT-TYPE 1962 SYNTAX Unsigned32 1963 UNITS "bytes per second" 1964 MAX-ACCESS read-create 1965 STATUS current 1966 DESCRIPTION 1967 "This is the transmission rate of the data link over which 1968 the Test messages will be transmitted and is expressed in 1969 bytes per second." 1970 REFERENCE 1971 "Link Management Protocol, RFC xxx" 1972 -- RFC Editor to fill in RFC number that will be assigned to 1973 -- [LMP] 1974 ::= { lmpLinkVerificationEntry 5 } 1976 lmpLinkVerifyWavelength OBJECT-TYPE 1977 SYNTAX Unsigned32 1978 UNITS "nanometers" 1979 MAX-ACCESS read-create 1980 STATUS current 1981 DESCRIPTION 1982 "This value corresponds to the wavelength at 1983 which the Test messages will be transmitted over and is 1984 measured in nanometers (nm). If each data-bearing link 1985 corresponds to a separate wavelength, than this value should 1986 be set to 0." 1987 REFERENCE 1988 "Link Management Protocol, RFC xxx" 1989 -- RFC Editor to fill in RFC number that will be assigned to 1990 -- [LMP] 1991 ::= { lmpLinkVerificationEntry 6 } 1993 lmpLinkVerifyRowStatus OBJECT-TYPE 1994 SYNTAX RowStatus 1995 MAX-ACCESS read-create 1996 STATUS current 1997 DESCRIPTION 1998 "This variable is used to create, modify, and/or 1999 delete a row in this table. None of the writable objects 2000 in a row can be changed if the status is active(1). 2001 All read-create objects must have valid and consistent 2002 values before the row can be activated." 2003 ::= { lmpLinkVerificationEntry 7 } 2005 lmpLinkVerifyStorageType OBJECT-TYPE 2006 SYNTAX StorageType 2007 MAX-ACCESS read-create 2008 STATUS current 2009 DESCRIPTION 2010 "The storage type for this conceptual row in the 2011 lmpLinkVerificationTable. Conceptual rows having the value 2012 'permanent' need not allow write-access to any 2013 columnar object in the row." 2014 DEFVAL { nonVolatile } 2015 ::= { lmpLinkVerificationEntry 8 } 2017 -- End of lmpLinkVerificationTable 2019 -- LMP TE Link Performance Table 2021 lmpTeLinkPerfTable OBJECT-TYPE 2022 SYNTAX SEQUENCE OF LmpTeLinkPerfEntry 2023 MAX-ACCESS not-accessible 2024 STATUS current 2025 DESCRIPTION 2026 "This table specifies LMP TE link performance counters." 2027 ::= { lmpObjects 15 } 2029 lmpTeLinkPerfEntry OBJECT-TYPE 2030 SYNTAX LmpTeLinkPerfEntry 2031 MAX-ACCESS not-accessible 2032 STATUS current 2033 DESCRIPTION 2034 "An entry in this table is created by a LMP-enabled device for 2035 every TE link. lmpTeCounterDiscontinuityTime is used 2036 to indicate potential discontinuity for all counter objects 2037 in this table." 2038 INDEX { ifIndex } 2039 ::= { lmpTeLinkPerfTable 1 } 2041 LmpTeLinkPerfEntry ::= SEQUENCE { 2042 lmpTeInOctets Counter32, 2043 lmpTeOutOctets Counter32, 2044 lmpTeBeginVerifyReceived Counter32, 2045 lmpTeBeginVerifySent Counter32, 2046 lmpTeBeginVerifyRetransmit Counter32, 2047 lmpTeBeginVerifyAckReceived Counter32, 2048 lmpTeBeginVerifyAckSent Counter32, 2049 lmpTeBeginVerifyNackReceived Counter32, 2050 lmpTeBeginVerifyNackSent Counter32, 2051 lmpTeEndVerifyReceived Counter32, 2052 lmpTeEndVerifySent Counter32, 2053 lmpTeEndVerifyRetransmit Counter32, 2054 lmpTeEndVerifyAckReceived Counter32, 2055 lmpTeEndVerifyAckSent Counter32, 2056 lmpTeTestStatusSuccessReceived Counter32, 2057 lmpTeTestStatusSuccessSent Counter32, 2058 lmpTeTestStatusSuccessRetransmit Counter32, 2059 lmpTeTestStatusFailureReceived Counter32, 2060 lmpTeTestStatusFailureSent Counter32, 2061 lmpTeTestStatusFailureRetransmit Counter32, 2062 lmpTeTestStatusAckReceived Counter32, 2063 lmpTeTestStatusAckSent Counter32, 2064 lmpTeLinkSummaryReceived Counter32, 2065 lmpTeLinkSummarySent Counter32, 2066 lmpTeLinkSummaryRetransmit Counter32, 2067 lmpTeLinkSummaryAckReceived Counter32, 2068 lmpTeLinkSummaryAckSent Counter32, 2069 lmpTeLinkSummaryNackReceived Counter32, 2070 lmpTeLinkSummaryNackSent Counter32, 2071 lmpTeChannelStatusReceived Counter32, 2072 lmpTeChannelStatusSent Counter32, 2073 lmpTeChannelStatusRetransmit Counter32, 2074 lmpTeChannelStatusAckReceived Counter32, 2075 lmpTeChannelStatusAckSent Counter32, 2076 lmpTeChannelStatusReqReceived Counter32, 2077 lmpTeChannelStatusReqSent Counter32, 2078 lmpTeChannelStatusReqRetransmit Counter32, 2079 lmpTeChannelStatusRspReceived Counter32, 2080 lmpTeChannelStatusRspSent Counter32, 2081 lmpTeCounterDiscontinuityTime TimeStamp 2082 } 2084 lmpTeInOctets OBJECT-TYPE 2085 SYNTAX Counter32 2086 MAX-ACCESS read-only 2087 STATUS current 2088 DESCRIPTION 2089 "The total number of LMP message octets received for 2090 this TE link." 2091 ::= { lmpTeLinkPerfEntry 1 } 2093 lmpTeOutOctets OBJECT-TYPE 2094 SYNTAX Counter32 2095 MAX-ACCESS read-only 2096 STATUS current 2097 DESCRIPTION 2098 "The total number of LMP message octets transmitted out 2099 for this TE link." 2100 ::= { lmpTeLinkPerfEntry 2 } 2102 lmpTeBeginVerifyReceived OBJECT-TYPE 2103 SYNTAX Counter32 2104 MAX-ACCESS read-only 2105 STATUS current 2106 DESCRIPTION 2107 "This object counts the number of BeginVerify messages that have 2108 been received for this TE link." 2109 ::= { lmpTeLinkPerfEntry 3 } 2111 lmpTeBeginVerifySent OBJECT-TYPE 2112 SYNTAX Counter32 2113 MAX-ACCESS read-only 2114 STATUS current 2115 DESCRIPTION 2116 "This object counts the number of BeginVerify messages that have 2117 been sent for this TE link." 2118 ::= { lmpTeLinkPerfEntry 4 } 2120 lmpTeBeginVerifyRetransmit OBJECT-TYPE 2121 SYNTAX Counter32 2122 MAX-ACCESS read-only 2123 STATUS current 2124 DESCRIPTION 2125 "This object counts the number of BeginVerify messages that 2126 have been retransmitted for this TE link." 2127 ::= { lmpTeLinkPerfEntry 5 } 2129 lmpTeBeginVerifyAckReceived OBJECT-TYPE 2130 SYNTAX Counter32 2131 MAX-ACCESS read-only 2132 STATUS current 2133 DESCRIPTION 2134 "This object counts the number of BeginVerifyAck messages that 2135 have been received for this TE link." 2136 ::= { lmpTeLinkPerfEntry 6 } 2138 lmpTeBeginVerifyAckSent OBJECT-TYPE 2139 SYNTAX Counter32 2140 MAX-ACCESS read-only 2141 STATUS current 2142 DESCRIPTION 2143 "This object counts the number of BeginVerifyAck messages that 2144 have been sent for this TE link." 2145 ::= { lmpTeLinkPerfEntry 7 } 2147 lmpTeBeginVerifyNackReceived OBJECT-TYPE 2148 SYNTAX Counter32 2149 MAX-ACCESS read-only 2150 STATUS current 2151 DESCRIPTION 2152 "This object counts the number of BeginVerifyNack messages that 2153 have been received for this TE link." 2154 ::= { lmpTeLinkPerfEntry 8 } 2156 lmpTeBeginVerifyNackSent OBJECT-TYPE 2157 SYNTAX Counter32 2158 MAX-ACCESS read-only 2159 STATUS current 2160 DESCRIPTION 2161 "This object counts the number of BeginVerifyNack messages that 2162 have been sent for this TE link." 2163 ::= { lmpTeLinkPerfEntry 9 } 2165 lmpTeEndVerifyReceived OBJECT-TYPE 2166 SYNTAX Counter32 2167 MAX-ACCESS read-only 2168 STATUS current 2169 DESCRIPTION 2170 "This object counts the number of EndVerify messages that have 2171 been received for this TE link." 2172 ::= { lmpTeLinkPerfEntry 10 } 2174 lmpTeEndVerifySent OBJECT-TYPE 2175 SYNTAX Counter32 2176 MAX-ACCESS read-only 2177 STATUS current 2178 DESCRIPTION 2179 "This object counts the number of EndVerify messages that have 2180 been sent for this TE link." 2181 ::= { lmpTeLinkPerfEntry 11 } 2183 lmpTeEndVerifyRetransmit OBJECT-TYPE 2184 SYNTAX Counter32 2185 MAX-ACCESS read-only 2186 STATUS current 2187 DESCRIPTION 2188 "This object counts the number of EndVerify messages that 2189 have been retransmitted over this control channel." 2190 ::= { lmpTeLinkPerfEntry 12 } 2192 lmpTeEndVerifyAckReceived OBJECT-TYPE 2193 SYNTAX Counter32 2194 MAX-ACCESS read-only 2195 STATUS current 2196 DESCRIPTION 2197 "This object counts the number of EndVerifyAck messages that 2198 have been received for this TE link." 2199 ::= { lmpTeLinkPerfEntry 13 } 2201 lmpTeEndVerifyAckSent OBJECT-TYPE 2202 SYNTAX Counter32 2203 MAX-ACCESS read-only 2204 STATUS current 2205 DESCRIPTION 2206 "This object counts the number of EndVerifyAck messages that 2207 have been sent for this TE link." 2208 ::= { lmpTeLinkPerfEntry 14 } 2210 lmpTeTestStatusSuccessReceived OBJECT-TYPE 2211 SYNTAX Counter32 2212 MAX-ACCESS read-only 2213 STATUS current 2214 DESCRIPTION 2215 "This object counts the number of TestStatusSuccess messages 2216 that have been received for this TE link." 2217 ::= { lmpTeLinkPerfEntry 15 } 2219 lmpTeTestStatusSuccessSent OBJECT-TYPE 2220 SYNTAX Counter32 2221 MAX-ACCESS read-only 2222 STATUS current 2223 DESCRIPTION 2224 "This object counts the number of TestStatusSuccess messages 2225 that have been sent for this TE link." 2226 ::= { lmpTeLinkPerfEntry 16 } 2228 lmpTeTestStatusSuccessRetransmit OBJECT-TYPE 2229 SYNTAX Counter32 2230 MAX-ACCESS read-only 2231 STATUS current 2232 DESCRIPTION 2233 "This object counts the number of TestStatusSuccess messages 2234 that have been retransmitted for this TE link." 2235 ::= { lmpTeLinkPerfEntry 17 } 2237 lmpTeTestStatusFailureReceived OBJECT-TYPE 2238 SYNTAX Counter32 2239 MAX-ACCESS read-only 2240 STATUS current 2241 DESCRIPTION 2242 "This object counts the number of TestStatusFailure messages 2243 that have been received for this TE link." 2244 ::= { lmpTeLinkPerfEntry 18 } 2246 lmpTeTestStatusFailureSent OBJECT-TYPE 2247 SYNTAX Counter32 2248 MAX-ACCESS read-only 2249 STATUS current 2250 DESCRIPTION 2251 "This object counts the number of TestStatusFailure messages 2252 that have been sent for this TE link." 2253 ::= { lmpTeLinkPerfEntry 19 } 2255 lmpTeTestStatusFailureRetransmit OBJECT-TYPE 2256 SYNTAX Counter32 2257 MAX-ACCESS read-only 2258 STATUS current 2259 DESCRIPTION 2260 "This object counts the number of TestStatusFailure messages 2261 that have been retransmitted on this TE link." 2262 ::= { lmpTeLinkPerfEntry 20 } 2264 lmpTeTestStatusAckReceived OBJECT-TYPE 2265 SYNTAX Counter32 2266 MAX-ACCESS read-only 2267 STATUS current 2268 DESCRIPTION 2269 "This object counts the number of TestStatusAck messages that 2270 have been received for this TE link." 2271 ::= { lmpTeLinkPerfEntry 21 } 2273 lmpTeTestStatusAckSent OBJECT-TYPE 2274 SYNTAX Counter32 2275 MAX-ACCESS read-only 2276 STATUS current 2277 DESCRIPTION 2278 "This object counts the number of TestStatusAck messages that 2279 have been sent for this TE link." 2280 ::= { lmpTeLinkPerfEntry 22 } 2282 lmpTeLinkSummaryReceived OBJECT-TYPE 2283 SYNTAX Counter32 2284 MAX-ACCESS read-only 2285 STATUS current 2286 DESCRIPTION 2287 "This object counts the number of LinkSummary messages that 2288 have been received for this TE link." 2289 ::= { lmpTeLinkPerfEntry 23 } 2291 lmpTeLinkSummarySent OBJECT-TYPE 2292 SYNTAX Counter32 2293 MAX-ACCESS read-only 2294 STATUS current 2295 DESCRIPTION 2296 "This object counts the number of LinkSummary messages that 2297 have been sent for this TE link." 2298 ::= { lmpTeLinkPerfEntry 24 } 2300 lmpTeLinkSummaryRetransmit OBJECT-TYPE 2301 SYNTAX Counter32 2302 MAX-ACCESS read-only 2303 STATUS current 2304 DESCRIPTION 2305 "This object counts the number of LinkSummary messages that 2306 have been retransmitted over this control channel." 2307 ::= { lmpTeLinkPerfEntry 25 } 2309 lmpTeLinkSummaryAckReceived OBJECT-TYPE 2310 SYNTAX Counter32 2311 MAX-ACCESS read-only 2312 STATUS current 2313 DESCRIPTION 2314 "This object counts the number of LinkSummaryAck messages that 2315 have been received for this TE link." 2316 ::= { lmpTeLinkPerfEntry 26 } 2318 lmpTeLinkSummaryAckSent OBJECT-TYPE 2319 SYNTAX Counter32 2320 MAX-ACCESS read-only 2321 STATUS current 2322 DESCRIPTION 2323 "This object counts the number of LinkSummaryAck messages that 2324 have been sent for this TE link." 2325 ::= { lmpTeLinkPerfEntry 27 } 2327 lmpTeLinkSummaryNackReceived OBJECT-TYPE 2328 SYNTAX Counter32 2329 MAX-ACCESS read-only 2330 STATUS current 2331 DESCRIPTION 2332 "This object counts the number of LinkSummaryNack messages that 2333 have been received for this TE link." 2334 ::= { lmpTeLinkPerfEntry 28 } 2336 lmpTeLinkSummaryNackSent OBJECT-TYPE 2337 SYNTAX Counter32 2338 MAX-ACCESS read-only 2339 STATUS current 2340 DESCRIPTION 2341 "This object counts the number of LinkSummaryNack messages that 2342 have been sent for this TE link." 2343 ::= { lmpTeLinkPerfEntry 29 } 2345 lmpTeChannelStatusReceived OBJECT-TYPE 2346 SYNTAX Counter32 2347 MAX-ACCESS read-only 2348 STATUS current 2349 DESCRIPTION 2350 "This object counts the number of ChannelStatus messages that 2351 have been received for this TE link." 2352 ::= { lmpTeLinkPerfEntry 30 } 2354 lmpTeChannelStatusSent OBJECT-TYPE 2355 SYNTAX Counter32 2356 MAX-ACCESS read-only 2357 STATUS current 2358 DESCRIPTION 2359 "This object counts the number of ChannelStatus messages that 2360 have been sent for this TE link." 2361 ::= { lmpTeLinkPerfEntry 31 } 2363 lmpTeChannelStatusRetransmit OBJECT-TYPE 2364 SYNTAX Counter32 2365 MAX-ACCESS read-only 2366 STATUS current 2367 DESCRIPTION 2368 "This object counts the number of ChannelStatus messages that 2369 have been retransmitted for this TE link." 2370 ::= { lmpTeLinkPerfEntry 32 } 2372 lmpTeChannelStatusAckReceived OBJECT-TYPE 2373 SYNTAX Counter32 2374 MAX-ACCESS read-only 2375 STATUS current 2376 DESCRIPTION 2377 "This object counts the number of ChannelStatusAck messages 2378 that have been received for this TE link." 2379 ::= { lmpTeLinkPerfEntry 33 } 2381 lmpTeChannelStatusAckSent OBJECT-TYPE 2382 SYNTAX Counter32 2383 MAX-ACCESS read-only 2384 STATUS current 2385 DESCRIPTION 2386 "This object counts the number of ChannelStatus messages 2387 that have been sent for this TE link." 2388 ::= { lmpTeLinkPerfEntry 34 } 2390 lmpTeChannelStatusReqReceived OBJECT-TYPE 2391 SYNTAX Counter32 2392 MAX-ACCESS read-only 2393 STATUS current 2394 DESCRIPTION 2395 "This object counts the number of ChannelStatusRequest messages 2396 that have been received for this TE link." 2397 ::= { lmpTeLinkPerfEntry 35 } 2399 lmpTeChannelStatusReqSent OBJECT-TYPE 2400 SYNTAX Counter32 2401 MAX-ACCESS read-only 2402 STATUS current 2403 DESCRIPTION 2404 "This object counts the number of ChannelStatusRequest messages 2405 that have been sent for this TE link." 2406 ::= { lmpTeLinkPerfEntry 36 } 2408 lmpTeChannelStatusReqRetransmit OBJECT-TYPE 2409 SYNTAX Counter32 2410 MAX-ACCESS read-only 2411 STATUS current 2412 DESCRIPTION 2413 "This object counts the number of ChannelStatusRequest messages 2414 that have been retransmitted for this TE link." 2415 ::= { lmpTeLinkPerfEntry 37 } 2417 lmpTeChannelStatusRspReceived OBJECT-TYPE 2418 SYNTAX Counter32 2419 MAX-ACCESS read-only 2420 STATUS current 2421 DESCRIPTION 2422 "This object counts the number of ChannelStatusResponse messages 2423 that have been received for this TE link." 2424 ::= { lmpTeLinkPerfEntry 38 } 2426 lmpTeChannelStatusRspSent OBJECT-TYPE 2427 SYNTAX Counter32 2428 MAX-ACCESS read-only 2429 STATUS current 2430 DESCRIPTION 2431 "This object counts the number of ChannelStatusResponse messages 2432 that have been sent for this TE link." 2433 ::= { lmpTeLinkPerfEntry 39 } 2435 lmpTeCounterDiscontinuityTime OBJECT-TYPE 2436 SYNTAX TimeStamp 2437 MAX-ACCESS read-only 2438 STATUS current 2439 DESCRIPTION 2440 "The value of sysUpTime on the most recent occasion at which 2441 any one or more of this TE link's counters suffered a 2442 discontinuity. The relevant counters are the specific 2443 instances associated with this TE link of any Counter32 2444 object contained in the lmpTeLinkPerfTable. If 2445 no such discontinuities have occurred since the last re- 2446 initialization of the local management subsystem, then this 2447 object contains a zero value." 2448 ::= { lmpTeLinkPerfEntry 40 } 2450 -- End of lmpTeLinkPerfTable 2452 -- LMP Data Link Table 2454 lmpDataLinkTable OBJECT-TYPE 2455 SYNTAX SEQUENCE OF LmpDataLinkEntry 2456 MAX-ACCESS not-accessible 2457 STATUS current 2458 DESCRIPTION 2459 "This table specifies the data-bearing links managed by the 2460 LMP." 2461 ::= { lmpObjects 16 } 2463 lmpDataLinkEntry OBJECT-TYPE 2464 SYNTAX LmpDataLinkEntry 2465 MAX-ACCESS not-accessible 2466 STATUS current 2467 DESCRIPTION 2468 "An entry in this table exists for each ifEntry that represents 2469 a data-bearing link. An ifEntry with an ifIndex must exist 2470 before the corresponding lmpDataLinkEntry is created. 2471 If an entry representing the data-bearing link is destroyed in 2472 the ifTable, then so is the corresponding entry in the 2473 lmpDataLinkTable. The administrative status value is 2474 controlled from the ifEntry. The index to this table also 2475 used to get information in the componentLinkTable 2476 of the TE-LINK-STD-MIB MIB module." 2477 INDEX { ifIndex } 2478 ::= { lmpDataLinkTable 1 } 2480 LmpDataLinkEntry ::= SEQUENCE { 2481 lmpDataLinkType INTEGER, 2482 lmpDataLinkAddressType InetAddressType, 2483 lmpDataLinkIpAddr InetAddress, 2484 lmpDataLinkRemoteIpAddress InetAddress, 2485 lmpDataLinkRemoteIfId InterfaceIndexOrZero, 2486 lmpDataLinkEncodingType TeLinkEncodingType, 2487 lmpDataLinkActiveOperStatus INTEGER, 2488 lmpDataLinkPassiveOperStatus INTEGER, 2489 lmpDataLinkRowStatus RowStatus, 2490 lmpDataLinkStorageType StorageType 2491 } 2493 lmpDataLinkType OBJECT-TYPE 2494 SYNTAX INTEGER { 2495 port(1), 2496 componentLink(2) 2497 } 2498 MAX-ACCESS read-only 2499 STATUS current 2500 DESCRIPTION 2501 "This attribute specifies whether this data-bearing link is 2502 a port or a component link. Component link are multiplex 2503 capable whereas, ports are not multiplex capable." 2504 REFERENCE 2505 "Link Management Protocol, RFC xxx" 2506 -- RFC Editor to fill in RFC number that will be assigned to 2507 -- [LMP] 2508 ::= { lmpDataLinkEntry 1 } 2510 lmpDataLinkAddressType OBJECT-TYPE 2511 SYNTAX InetAddressType 2512 MAX-ACCESS read-create 2513 STATUS current 2514 DESCRIPTION 2515 "This attribute specifies the data-bearing link IP address 2516 type. If the data-bearing link is unnumbered, the address 2517 type must be set to unknown(0)." 2518 ::= { lmpDataLinkEntry 2 } 2520 lmpDataLinkIpAddr OBJECT-TYPE 2521 SYNTAX InetAddress 2522 MAX-ACCESS read-create 2523 STATUS current 2524 DESCRIPTION 2525 "The local Internet address for numbered links. The type 2526 of this address is determined by the value of 2527 lmpDataLinkAddressType object. 2529 For IPv4 and IPv6 numbered links, this object represents 2530 the local IP address associated with the data-bearing 2531 link. For an unnumbered link, the local address is 2532 of type unknown and this object is set to the zero length 2533 string and the ifIndex object then identifies the 2534 unnumbered address." 2535 ::= { lmpDataLinkEntry 3 } 2537 lmpDataLinkRemoteIpAddress OBJECT-TYPE 2538 SYNTAX InetAddress 2539 MAX-ACCESS read-create 2540 STATUS current 2541 DESCRIPTION 2542 "The remote Internet address for numbered data-bearing links. 2543 The type of this address is determined by the 2544 lmpDataLinkAddressType object. 2546 For IPv4 and IPv6 numbered links, this object represents the 2547 remote IP address associated with the data-bearing link. For 2548 an unnumbered link, the remote address is of type unknown 2549 and this object is set to the zero length string and the 2550 lmpDataLinkRemoteIfId object then identifies the unnumbered 2551 address. 2553 This information is either configured manually or is 2554 communicated by the remote node during the link verification 2555 procedure." 2556 ::= { lmpDataLinkEntry 4 } 2558 lmpDataLinkRemoteIfId OBJECT-TYPE 2559 SYNTAX InterfaceIndexOrZero 2560 MAX-ACCESS read-create 2561 STATUS current 2562 DESCRIPTION 2563 "Interface identifier of the remote end point. This 2564 information is either configured manually or is 2565 communicated by the remote node during the link verification 2566 procedure." 2567 ::= { lmpDataLinkEntry 5 } 2569 lmpDataLinkEncodingType OBJECT-TYPE 2570 SYNTAX TeLinkEncodingType 2571 MAX-ACCESS read-create 2572 STATUS current 2573 DESCRIPTION 2574 "The encoding type of the data-bearing link." 2575 REFERENCE 2576 "Generalized MPLS Signaling Functional Description, RFC 3471" 2578 ::= { lmpDataLinkEntry 6 } 2580 lmpDataLinkActiveOperStatus OBJECT-TYPE 2581 SYNTAX INTEGER { 2582 upAlloc(1), 2583 upFree(2), 2584 down(3), 2585 testing(4) } 2586 MAX-ACCESS read-only 2587 STATUS current 2588 DESCRIPTION 2589 "The actual operational status of this data-bearing link 2590 (active FSM)." 2591 REFERENCE 2592 "Link Management Protocol, RFC xxx" 2593 -- RFC Editor to fill in RFC number that will be assigned to 2594 -- [LMP] 2595 ::= { lmpDataLinkEntry 7 } 2597 lmpDataLinkPassiveOperStatus OBJECT-TYPE 2598 SYNTAX INTEGER { 2599 upAlloc(1), 2600 upFree(2), 2601 down(3), 2602 psvTst(4) } 2603 MAX-ACCESS read-only 2604 STATUS current 2605 DESCRIPTION 2606 "The actual operational status of this data-bearing link 2607 (passive FSM)." 2608 REFERENCE 2609 "Link Management Protocol, RFC xxx" 2610 -- RFC Editor to fill in RFC number that will be assigned to 2611 -- [LMP] 2612 ::= { lmpDataLinkEntry 8 } 2614 lmpDataLinkRowStatus OBJECT-TYPE 2615 SYNTAX RowStatus 2616 MAX-ACCESS read-create 2617 STATUS current 2618 DESCRIPTION 2619 "This variable is used to create, modify, and/or 2620 delete a row in this table. None of the writable objects 2621 in a row can be changed if the status is active(1). 2622 All read-create objects must have valid and consistent 2623 values before the row can be activated." 2624 ::= { lmpDataLinkEntry 9 } 2626 lmpDataLinkStorageType OBJECT-TYPE 2627 SYNTAX StorageType 2628 MAX-ACCESS read-create 2629 STATUS current 2630 DESCRIPTION 2631 "The storage type for this conceptual row in the 2632 lmpDataLinkTable. Conceptual rows having the value 2633 'permanent' need not allow write-access to any 2634 columnar object in the row." 2635 DEFVAL { nonVolatile } 2636 ::= { lmpDataLinkEntry 10 } 2638 -- End of lmpDataLinkTable 2640 -- LMP Data Link Performance Table 2642 lmpDataLinkPerfTable OBJECT-TYPE 2643 SYNTAX SEQUENCE OF LmpDataLinkPerfEntry 2644 MAX-ACCESS not-accessible 2645 STATUS current 2646 DESCRIPTION 2647 "This table specifies the data-bearing links LMP performance 2648 counters." 2649 ::= { lmpObjects 17 } 2651 lmpDataLinkPerfEntry OBJECT-TYPE 2652 SYNTAX LmpDataLinkPerfEntry 2653 MAX-ACCESS not-accessible 2654 STATUS current 2655 DESCRIPTION 2656 "An entry in this table contains information about 2657 the LMP performance counters for the data-bearing links. 2658 lmpDataLinkDiscontinuityTime is used to indicate potential 2659 discontinuity for all counter objects in this table." 2660 INDEX { ifIndex } 2661 ::= { lmpDataLinkPerfTable 1 } 2663 LmpDataLinkPerfEntry ::= SEQUENCE { 2664 lmpDataLinkTestReceived Counter32, 2665 lmpDataLinkTestSent Counter32, 2666 lmpDataLinkActiveTestSuccess Counter32, 2667 lmpDataLinkActiveTestFailure Counter32, 2668 lmpDataLinkPassiveTestSuccess Counter32, 2669 lmpDataLinkPassiveTestFailure Counter32, 2670 lmpDataLinkDiscontinuityTime TimeStamp 2671 } 2672 lmpDataLinkTestReceived OBJECT-TYPE 2673 SYNTAX Counter32 2674 MAX-ACCESS read-only 2675 STATUS current 2676 DESCRIPTION 2677 "This object counts the number of Test messages that have 2678 been received on this data-bearing link." 2679 ::= { lmpDataLinkPerfEntry 1 } 2681 lmpDataLinkTestSent OBJECT-TYPE 2682 SYNTAX Counter32 2683 MAX-ACCESS read-only 2684 STATUS current 2685 DESCRIPTION 2686 "This object counts the number of Test messages that have 2687 been sent on this data-bearing link." 2688 ::= { lmpDataLinkPerfEntry 2 } 2690 lmpDataLinkActiveTestSuccess OBJECT-TYPE 2691 SYNTAX Counter32 2692 MAX-ACCESS read-only 2693 STATUS current 2694 DESCRIPTION 2695 "This object counts the number of data-bearing link test 2696 that were successful on the active side of this data- 2697 bearing link." 2698 ::= { lmpDataLinkPerfEntry 3 } 2700 lmpDataLinkActiveTestFailure OBJECT-TYPE 2701 SYNTAX Counter32 2702 MAX-ACCESS read-only 2703 STATUS current 2704 DESCRIPTION 2705 "This object counts the number of data-bearing link test 2706 that failed on the active side of this data-bearing link." 2707 ::= { lmpDataLinkPerfEntry 4 } 2709 lmpDataLinkPassiveTestSuccess OBJECT-TYPE 2710 SYNTAX Counter32 2711 MAX-ACCESS read-only 2712 STATUS current 2713 DESCRIPTION 2714 "This object counts the number of data-bearing link test 2715 that were successful on the passive side of this data- 2716 bearing link." 2717 ::= { lmpDataLinkPerfEntry 5 } 2719 lmpDataLinkPassiveTestFailure OBJECT-TYPE 2720 SYNTAX Counter32 2721 MAX-ACCESS read-only 2722 STATUS current 2723 DESCRIPTION 2724 "This object counts the number of data-bearing link test 2725 that failed on the passive side of this data-bearing link." 2726 ::= { lmpDataLinkPerfEntry 6 } 2728 lmpDataLinkDiscontinuityTime OBJECT-TYPE 2729 SYNTAX TimeStamp 2730 MAX-ACCESS read-only 2731 STATUS current 2732 DESCRIPTION 2733 "The value of sysUpTime on the most recent occasion at which 2734 any one or more of this data-bearing link's counters suffered 2735 a discontinuity. The relevant counters are the specific 2736 instances associated with this data-bearing link of any 2737 Counter32 object contained in the lmpDataLinkPerfTable. If 2738 no such discontinuities have occurred since the last re- 2739 initialization of the local management subsystem, then this 2740 object contains a zero value." 2741 ::= { lmpDataLinkPerfEntry 7 } 2743 -- End of lmpDataLinkPerfTable 2745 -- Notification Configuration 2747 lmpNotificationMaxRate OBJECT-TYPE 2748 SYNTAX Unsigned32 2749 MAX-ACCESS read-write 2750 STATUS current 2751 DESCRIPTION 2752 "The LMP notification rate depends on the size of the network, 2753 the type of links, the network configuration, the 2754 reliability of the network, etc. 2756 When designing this MIB, care has been taken to minimize the 2757 amount of notifications generated for LMP purposes. Wherever 2758 possible, notifications are state driven meaning the 2759 notification are only sent when the system changes state. 2760 The only notifications that are repeated and could cause a 2761 problem as far as congestion is concerned are the ones 2762 associated with data link verification. 2763 Without any considerations to handling of these 2764 notifications, a problem may arise if the number of data 2765 links is high. Since the data link verification notifications 2766 can happen only once per data link per link verification 2767 interval, the notification rate should be sustainable if one 2768 chooses an appropriate link verification interval for a given 2769 network configuration. For instance, a network of 100 nodes 2770 with 5 links of 128 wavelengths each and a link verification 2771 of 1 minute with no more than 10% of the links failed at any 2772 given time would have 1 notification per second sent from 2773 each node, or 100 notifications per second for the whole 2774 network. The rest of the notifications are negligeable 2775 compared to this number. 2777 To alleviate the congestion problem, the 2778 lmpNotificationMaxRate object can be used to implement a 2779 throttling mechanism. It is also possible to enable/disable 2780 certain type of notifications. 2782 This variable indicates the maximum number of 2783 notifications issued per minute. If events occur 2784 more rapidly, the implementation may simply fail to 2785 emit these notifications during that period, or may 2786 queue them until an appropriate time. A value of 0 2787 means no throttling is applied and events may be 2788 notified at the rate at which they occur. 2789 Implementations should save the value of this object in 2790 persistent memory so that it survives restarts or reboot." 2791 ::= { lmpObjects 18 } 2793 lmpLinkPropertyNotificationsEnabled OBJECT-TYPE 2794 SYNTAX TruthValue 2795 MAX-ACCESS read-write 2796 STATUS current 2797 DESCRIPTION 2798 "If this object is true, then it enables the 2799 generation of lmpTeLinkPropertyMismatch 2800 and lmpDataLinkPropertyMismatch notifications, 2801 otherwise these notifications are not emitted. 2802 Implementations should save the value of this object in 2803 persistent memory so that it survives restarts or reboot." 2804 DEFVAL { false } 2805 ::= { lmpObjects 19 } 2807 lmpUnprotectedNotificationsEnabled OBJECT-TYPE 2808 SYNTAX TruthValue 2809 MAX-ACCESS read-write 2810 STATUS current 2811 DESCRIPTION 2812 "If this object is true, then it enables the 2813 generation of lmpUnprotected notifications, 2814 otherwise these notifications are not emitted. 2816 Implementations should save the value of this object in 2817 persistent memory so that it survives restarts or reboot." 2818 DEFVAL { false } 2819 ::= { lmpObjects 20 } 2821 lmpCcUpDownNotificationsEnabled OBJECT-TYPE 2822 SYNTAX TruthValue 2823 MAX-ACCESS read-write 2824 STATUS current 2825 DESCRIPTION 2826 "If this object is true, then it enables the generation of 2827 lmpControlChannelUp and lmpControlChannelDown notifications, 2828 otherwise these notifications are not emitted. 2829 Implementations should save the value of this object in 2830 persistent memory so that it survives restarts or reboot." 2831 DEFVAL { false } 2832 ::= { lmpObjects 21 } 2834 lmpTeLinkNotificationsEnabled OBJECT-TYPE 2835 SYNTAX TruthValue 2836 MAX-ACCESS read-write 2837 STATUS current 2838 DESCRIPTION 2839 "If this object is true, then it enables the 2840 generation of lmpTeLinkDegraded and lmpTeLinkNotDegraded 2841 notifications, otherwise these notifications are not emitted. 2842 Implementations should save the value of this object in 2843 persistent memory so that it survives restarts or reboot." 2844 DEFVAL { false } 2845 ::= { lmpObjects 22 } 2847 lmpDataLinkNotificationsEnabled OBJECT-TYPE 2848 SYNTAX TruthValue 2849 MAX-ACCESS read-write 2850 STATUS current 2851 DESCRIPTION 2852 "If this object is true, then it enables the 2853 generation of lmpDataLinkVerificationFailure 2854 notification, otherwise these notifications are not emitted. 2855 Implementations should save the value of this object in 2856 persistent memory so that it survives restarts or reboot." 2857 DEFVAL { false } 2858 ::= { lmpObjects 23 } 2860 -- Notifications 2862 -- Link Property Mismatch Notifications 2863 lmpTeLinkPropertyMismatch NOTIFICATION-TYPE 2864 OBJECTS { teLinkRemoteIpAddr, 2865 teLinkIncomingIfId } 2866 STATUS current 2867 DESCRIPTION 2868 "This notification is generated when a TE link property 2869 mismatch is detected on the node. The received remote TE link 2870 id of the misconfigured TE link is represented by either 2871 teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether 2872 the TE link is numbered or unnumbered. This notification 2873 should not be sent unless lmpLinkPropertyNotificationsEnabled 2874 is true. It is recommended that this notification be reported 2875 only the first time a mismatch is detected. Otherwise, for a 2876 given TE link, this notification can occur no more than once 2877 per verification interval (lmpGlobalLinkVerificationInterval)." 2878 ::= { lmpNotifications 1 } 2880 lmpDataLinkPropertyMismatch NOTIFICATION-TYPE 2881 OBJECTS { lmpDataLinkType, lmpDataLinkRemoteIfId } 2882 STATUS current 2883 DESCRIPTION 2884 "This notification is generated when a data-bearing link 2885 property mismatch is detected on the node. lmpDataLinkType 2886 is used to identify the local identifiers associated with 2887 the data link (the data link interface index can be used 2888 to determine the TE link interface index as this 2889 relationship is captured in the interface stack table). 2890 The remote entity interface id is the remote entity 2891 interface id received in the LinkSummary message. 2892 This notification should not be sent unless 2893 lmpLinkPropertyNotificationsEnabled is true. It is 2894 recommended that this notification be reported only the 2895 first time a mismatch is detected. Otherwise, for a given 2896 data link, this notification can occur no more than once 2897 per verification interval (lmpGlobalLinkVerificationInterval)." 2898 ::= { lmpNotifications 2 } 2900 -- Neighbor Notification 2902 lmpUnprotected NOTIFICATION-TYPE 2903 OBJECTS { lmpCcNbrNodeId } 2904 STATUS current 2905 DESCRIPTION 2906 "This notification is generated when there are more than one 2907 control channels between LMP neighbors and the last redundant 2908 control channel has failed. If the remaining operational 2909 control channel fails, then there will be no more control 2910 channels between the pair of nodes and all the TE links 2911 between the pair of nodes will go to degraded state. This 2912 notification should not be sent unless 2913 lmpUnprotectedNotificationsEnabled is set to true." 2914 ::= { lmpNotifications 3 } 2916 -- Control Channel Notifications 2918 lmpControlChannelUp NOTIFICATION-TYPE 2919 OBJECTS { lmpCcAdminStatus, lmpCcOperStatus } 2920 STATUS current 2921 DESCRIPTION 2922 "This notification is generated when a control 2923 channel transitions to the up operational state. This 2924 notification should not be sent unless 2925 lmpCcUpDownNotificationsEnabled is true." 2926 ::= { lmpNotifications 4 } 2928 lmpControlChannelDown NOTIFICATION-TYPE 2929 OBJECTS { lmpCcAdminStatus, lmpCcOperStatus } 2930 STATUS current 2931 DESCRIPTION 2932 "This notification is generated when a control channel 2933 transitions out of the up operational state. This 2934 notification should not be sent unless 2935 lmpCcUpDownNotificationsEnabled is true." 2936 ::= { lmpNotifications 5 } 2938 -- TE Link Notification 2940 lmpTeLinkDegraded NOTIFICATION-TYPE 2941 OBJECTS { lmpTeLinkOperStatus } 2942 STATUS current 2943 DESCRIPTION 2944 "This notification is generated when a lmpTeLinkOperStatus 2945 object for a TE link enters the degraded state. This 2946 notification should not be sent unless 2947 lmpTeLinkNotificationsEnabled is true." 2948 ::= { lmpNotifications 6 } 2950 lmpTeLinkNotDegraded NOTIFICATION-TYPE 2951 OBJECTS { lmpTeLinkOperStatus } 2952 STATUS current 2953 DESCRIPTION 2954 "This notification is generated when a lmpTeLinkOperStatus 2955 object for a TE link leaves the degraded state. This 2956 notification should not be sent unless 2957 lmpTeLinkNotificationsEnabled is true." 2958 ::= { lmpNotifications 7 } 2960 -- Data-bearing Link Notification 2962 lmpDataLinkVerificationFailure NOTIFICATION-TYPE 2963 OBJECTS { lmpDataLinkActiveOperStatus, 2964 lmpDataLinkPassiveOperStatus } 2965 STATUS current 2966 DESCRIPTION 2967 "This notification is generated when a data-bearing 2968 link verification fails. This notification should not be sent 2969 unless lmpDataLinkNotificationsEnabled is true. For a given 2970 data link, this notification can occur no more than once per 2971 verification interval (lmpGlobalLinkVerificationInterval)." 2972 ::= { lmpNotifications 8 } 2974 -- End of notifications 2976 -- Module compliance 2978 lmpCompliances 2979 OBJECT IDENTIFIER ::= { lmpConformance 1 } 2981 lmpGroups 2982 OBJECT IDENTIFIER ::= { lmpConformance 2 } 2984 lmpModuleFullCompliance MODULE-COMPLIANCE 2985 STATUS current 2986 DESCRIPTION 2987 "Compliance statement for agents that support the 2988 configuration and monitoring of LMP MIB." 2989 MODULE -- this module 2991 MANDATORY-GROUPS { lmpNodeGroup, 2992 lmpControlChannelGroup, 2993 lmpLinkPropertyCorrelationGroup, 2994 lmpPerfGroup, 2995 lmpTeLinkGroup, 2996 lmpDataLinkGroup } 2998 GROUP lmpCcIsNotInterfaceGroup 2999 DESCRIPTION 3000 "This group is mandatory for devices which support 3001 control channels that are not interfaces, in addition to 3002 lmpControlChannelGroup. The following constraints apply: 3003 lmpCcIsIf must at least be read-only returning false(1)." 3005 GROUP lmpCcIsInterfaceGroup 3006 DESCRIPTION 3007 "This group is mandatory for devices which support 3008 control channels that are interfaces, in addition to 3009 lmpControlChannelGroup. The following constraints apply: 3010 lmpCcIsIf must at least be read-only returning true(2)." 3012 GROUP lmpLinkVerificationGroup 3013 DESCRIPTION 3014 "This group is mandatory for devices which support 3015 the link verification procedure." 3017 GROUP lmpNotificationGroup 3018 DESCRIPTION 3019 "This group is optional." 3021 -- lmpNbrTable 3023 OBJECT lmpNbrRowStatus 3024 SYNTAX RowStatus { active(1), notInService(2) } 3025 WRITE-SYNTAX RowStatus { active(1), notInService(2), 3026 createAndGo(4), destroy(6) } 3027 DESCRIPTION 3028 "Support for notReady(3) and createAndWait(5) is 3029 not required." 3031 -- lmpControlChannelTable 3033 OBJECT lmpCcRemoteAddressType 3034 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 3035 DESCRIPTION 3036 "Only ipv4(1) and ipv6(2) address types need to be 3037 supported for non point-to-point configurations." 3039 OBJECT lmpCcRemoteIpAddr 3040 SYNTAX InetAddress (SIZE(0|4|16)) 3041 DESCRIPTION 3042 "The size of the IP address depends on the address type." 3044 OBJECT lmpCcRowStatus 3045 SYNTAX RowStatus { active(1), notInService(2) } 3046 WRITE-SYNTAX RowStatus { active(1), notInService(2), 3047 createAndGo(4), destroy(6) } 3048 DESCRIPTION 3049 "Support for notReady(3) and createAndWait(5) is 3050 not required." 3052 OBJECT lmpCcOperStatus 3053 SYNTAX INTEGER { up(1), down(2) } 3054 DESCRIPTION 3055 "A value of configSnd(3), configRcv(4), active(5), 3056 goingDown(6) need not be supported." 3058 -- lmpTeLinkTable 3060 OBJECT lmpTeLinkOperStatus 3061 SYNTAX INTEGER { up(1), down(2), degraded(5) } 3062 DESCRIPTION 3063 "The testing(3) and init(4) state need not be supported." 3065 OBJECT lmpTeLinkRowStatus 3066 SYNTAX RowStatus { active(1), notInService(2) } 3067 WRITE-SYNTAX RowStatus { active(1), notInService(2), 3068 createAndGo(4), destroy(6) } 3069 DESCRIPTION 3070 "Support for notReady(3) and createAndWait(5) is 3071 not required." 3073 -- lmpDataLinkTable 3075 OBJECT lmpDataLinkActiveOperStatus 3076 SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) } 3077 DESCRIPTION 3078 "A value of testing(4) need not be supported." 3080 OBJECT lmpDataLinkPassiveOperStatus 3081 SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) } 3082 DESCRIPTION 3083 "A value of psvTst(4) need not be supported." 3085 OBJECT lmpDataLinkRowStatus 3086 SYNTAX RowStatus { active(1), notInService(2) } 3087 WRITE-SYNTAX RowStatus { active(1), notInService(2), 3088 createAndGo(4), destroy(6) } 3089 DESCRIPTION 3090 "Support for notReady(3) and createAndWait(5) is 3091 not required." 3093 ::= { lmpCompliances 1 } 3095 lmpModuleReadOnlyCompliance MODULE-COMPLIANCE 3096 STATUS current 3097 DESCRIPTION 3098 "Compliance statement for agents that support the 3099 monitoring of the LMP MIB." 3100 MODULE -- this module 3102 -- The mandatory groups have to be implemented 3103 -- by all LMP-enabled devices. However, they may all be supported 3104 -- as read-only objects in the case where manual 3105 -- configuration is not supported. 3107 MANDATORY-GROUPS { lmpNodeGroup, 3108 lmpControlChannelGroup, 3109 lmpLinkPropertyCorrelationGroup, 3110 lmpPerfGroup, 3111 lmpTeLinkGroup, 3112 lmpDataLinkGroup } 3114 GROUP lmpCcIsNotInterfaceGroup 3115 DESCRIPTION 3116 "This group is mandatory for devices which support 3117 control channels that are not interfaces, in addition to 3118 lmpControlChannelGroup. The following constraints apply: 3119 lmpCcIsIf must at least be read-only returning false(1)." 3121 GROUP lmpCcIsInterfaceGroup 3122 DESCRIPTION 3123 "This group is mandatory for devices which support 3124 control channels that are interfaces, in addition to 3125 lmpControlChannelGroup. The following constraints apply: 3126 lmpCcIsIf must at least be read-only returning true(2)." 3128 GROUP lmpLinkVerificationGroup 3129 DESCRIPTION 3130 "This group is mandatory for devices which support 3131 the link verification procedure." 3133 GROUP lmpNotificationGroup 3134 DESCRIPTION 3135 "This group is optional." 3137 -- Scalars 3139 OBJECT lmpAdminStatus 3140 MIN-ACCESS read-only 3141 DESCRIPTION 3142 "Write access is not required." 3144 OBJECT lmpGlobalLinkVerificationInterval 3145 MIN-ACCESS read-only 3146 DESCRIPTION 3147 "Write access is not required." 3149 OBJECT lmpCcHelloIntervalDefault 3150 MIN-ACCESS read-only 3151 DESCRIPTION 3152 "Write access is not required." 3154 OBJECT lmpCcHelloIntervalDefaultMin 3155 MIN-ACCESS read-only 3156 DESCRIPTION 3157 "Write access is not required." 3159 OBJECT lmpCcHelloIntervalDefaultMax 3160 MIN-ACCESS read-only 3161 DESCRIPTION 3162 "Write access is not required." 3164 OBJECT lmpCcHelloDeadIntervalDefault 3165 MIN-ACCESS read-only 3166 DESCRIPTION 3167 "Write access is not required." 3169 OBJECT lmpCcHelloDeadIntervalDefaultMin 3170 MIN-ACCESS read-only 3171 DESCRIPTION 3172 "Write access is not required." 3174 OBJECT lmpCcHelloDeadIntervalDefaultMax 3175 MIN-ACCESS read-only 3176 DESCRIPTION 3177 "Write access is not required." 3179 OBJECT lmpNotificationMaxRate 3180 MIN-ACCESS read-only 3181 DESCRIPTION 3182 "Write access is not required." 3184 -- lmpNbrTable 3186 OBJECT lmpNbrRetransmitInterval 3187 MIN-ACCESS read-only 3188 DESCRIPTION 3189 "Write access is not required." 3191 OBJECT lmpNbrRetryLimit 3192 MIN-ACCESS read-only 3193 DESCRIPTION 3194 "Write access is not required." 3196 OBJECT lmpNbrRetransmitDelta 3197 MIN-ACCESS read-only 3198 DESCRIPTION 3199 "Write access is not required." 3201 OBJECT lmpNbrRowStatus 3202 SYNTAX RowStatus { active(1) } 3203 MIN-ACCESS read-only 3204 DESCRIPTION 3205 "Write access is not required and active(1) is the 3206 only status that needs to be supported." 3208 OBJECT lmpNbrStorageType 3209 MIN-ACCESS read-only 3210 DESCRIPTION 3211 "Write access is not required." 3213 -- lmpControlChannelTable 3215 OBJECT lmpCcUnderlyingIfIndex 3216 MIN-ACCESS read-only 3217 DESCRIPTION 3218 "Write access is not required." 3220 OBJECT lmpCcIsIf 3221 MIN-ACCESS read-only 3222 DESCRIPTION 3223 "Write access is not required." 3225 OBJECT lmpCcNbrNodeId 3226 MIN-ACCESS read-only 3227 DESCRIPTION 3228 "Write access is not required." 3230 OBJECT lmpCcRemoteAddressType 3231 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 3232 MIN-ACCESS read-only 3233 DESCRIPTION 3234 "Only ipv4(1) and ipv6(2) address types need to be 3235 supported for non point-to-point configurations." 3237 OBJECT lmpCcRemoteIpAddr 3238 SYNTAX InetAddress (SIZE(0|4|16)) 3239 MIN-ACCESS read-only 3240 DESCRIPTION 3241 "The size of the IP address depends on the address type." 3243 OBJECT lmpCcSetupRole 3244 MIN-ACCESS read-only 3245 DESCRIPTION 3246 "Write access is not required." 3248 OBJECT lmpCcAuthentication 3249 MIN-ACCESS read-only 3250 DESCRIPTION 3251 "Write access is not required." 3253 OBJECT lmpCcHelloIntervalMin 3254 MIN-ACCESS read-only 3255 DESCRIPTION 3256 "Write access is not required." 3258 OBJECT lmpCcHelloIntervalMax 3259 MIN-ACCESS read-only 3260 DESCRIPTION 3261 "Write access is not required." 3263 OBJECT lmpCcHelloDeadIntervalMin 3264 MIN-ACCESS read-only 3265 DESCRIPTION 3266 "Write access is not required." 3268 OBJECT lmpCcHelloDeadIntervalMax 3269 MIN-ACCESS read-only 3270 DESCRIPTION 3271 "Write access is not required." 3273 OBJECT lmpCcRowStatus 3274 SYNTAX RowStatus { active(1) } 3275 MIN-ACCESS read-only 3276 DESCRIPTION 3277 "Write access is not required and active(1) is the 3278 only status that needs to be supported." 3280 OBJECT lmpCcOperStatus 3281 SYNTAX INTEGER { up(1), down(2) } 3282 DESCRIPTION 3283 "A value of configSnd(3), configRcv(4), active(5), 3284 goingDown(6) need not be supported." 3286 OBJECT lmpCcStorageType 3287 MIN-ACCESS read-only 3288 DESCRIPTION 3289 "Write access is not required." 3291 -- lmpLinkVerificationTable 3293 OBJECT lmpLinkVerifyInterval 3294 MIN-ACCESS read-only 3295 DESCRIPTION 3296 "Write access is not required." 3298 OBJECT lmpLinkVerifyDeadInterval 3299 MIN-ACCESS read-only 3300 DESCRIPTION 3301 "Write access is not required." 3303 OBJECT lmpLinkVerifyAllLinks 3304 MIN-ACCESS read-only 3305 DESCRIPTION 3306 "Write access is not required." 3308 -- lmpTeLinkTable 3310 OBJECT lmpTeLinkNbrRemoteNodeId 3311 MIN-ACCESS read-only 3312 DESCRIPTION 3313 "Write access is not required if the link verification 3314 procedure is enabled." 3316 OBJECT lmpTeLinkVerification 3317 MIN-ACCESS read-only 3318 DESCRIPTION 3319 "Write access is not required." 3321 OBJECT lmpTeLinkFaultManagement 3322 MIN-ACCESS read-only 3323 DESCRIPTION 3324 "Write access is not required." 3326 OBJECT lmpTeLinkDwdm 3327 MIN-ACCESS read-only 3328 DESCRIPTION 3329 "Write access is not required." 3331 OBJECT lmpTeLinkOperStatus 3332 SYNTAX INTEGER { up(1), down(2), degraded(5) } 3333 DESCRIPTION 3334 "The testing(3) and init(4) state need not be supported." 3336 OBJECT lmpTeLinkRowStatus 3337 SYNTAX RowStatus { active(1) } 3338 MIN-ACCESS read-only 3339 DESCRIPTION 3340 "Write access is not required and active(1) is the 3341 only status that needs to be supported." 3343 OBJECT lmpTeLinkStorageType 3344 MIN-ACCESS read-only 3345 DESCRIPTION 3346 "Write access is not required." 3348 -- lmpTeLinkVerificationTable 3350 OBJECT lmpLinkVerifyTransmissionRate 3351 MIN-ACCESS read-only 3352 DESCRIPTION 3353 "Write access is not required." 3355 OBJECT lmpLinkVerifyWavelength 3356 MIN-ACCESS read-only 3357 DESCRIPTION 3358 "Write access is not required." 3360 OBJECT lmpLinkVerifyRowStatus 3361 SYNTAX RowStatus { active(1) } 3362 MIN-ACCESS read-only 3363 DESCRIPTION 3364 "Write access is not required and active(1) is the 3365 only status that needs to be supported." 3367 OBJECT lmpLinkVerifyStorageType 3368 MIN-ACCESS read-only 3369 DESCRIPTION 3370 "Write access is not required." 3372 -- lmpDataLinkTable 3374 OBJECT lmpDataLinkAddressType 3375 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 3376 MIN-ACCESS read-only 3377 DESCRIPTION 3378 "Only ipv4(1) and ipv6(2) address types need to be 3379 supported for numbered links. For unnumbered links, the 3380 unknown(0) address type needs to be supported." 3382 OBJECT lmpDataLinkIpAddr 3383 SYNTAX InetAddress (SIZE(0|4|16)) 3384 MIN-ACCESS read-only 3385 DESCRIPTION 3386 "Size of data-bearing link IP address depends on type 3387 of data-bearing link. Data-bearing link IP address size 3388 is zero if link is unnumbered, four if link IP address is 3389 IPv4 and sixteen if link IP address is IPv6." 3391 OBJECT lmpDataLinkRemoteIpAddress 3392 SYNTAX InetAddress (SIZE(0|4|16)) 3393 MIN-ACCESS read-only 3394 DESCRIPTION 3395 "Write access is not required if the link verification 3396 procedure is enabled." 3398 OBJECT lmpDataLinkRemoteIfId 3399 MIN-ACCESS read-only 3400 DESCRIPTION 3401 "Write access is not required if the link verification 3402 procedure is enabled." 3404 OBJECT lmpDataLinkEncodingType 3405 MIN-ACCESS read-only 3406 DESCRIPTION 3407 "Write access is not required." 3409 OBJECT lmpDataLinkActiveOperStatus 3410 SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) } 3411 DESCRIPTION 3412 "A value of testing(4) need not be supported." 3414 OBJECT lmpDataLinkPassiveOperStatus 3415 SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) } 3416 DESCRIPTION 3417 "A value of psvTst(4) need not be supported." 3419 OBJECT lmpDataLinkRowStatus 3420 SYNTAX RowStatus { active(1) } 3421 MIN-ACCESS read-only 3422 DESCRIPTION 3423 "Write access is not required and active(1) is the 3424 only status that needs to be supported." 3426 OBJECT lmpDataLinkStorageType 3427 MIN-ACCESS read-only 3428 DESCRIPTION 3429 "Write access is not required." 3431 ::= { lmpCompliances 2 } 3433 -- Units of conformance 3435 lmpNodeGroup OBJECT-GROUP 3436 OBJECTS { lmpAdminStatus, 3437 lmpOperStatus, 3438 lmpNbrAdminStatus, 3439 lmpNbrOperStatus, 3440 lmpNbrRowStatus, 3441 lmpNbrStorageType, 3442 lmpUnprotectedNotificationsEnabled, 3443 lmpNotificationMaxRate 3444 } 3445 STATUS current 3446 DESCRIPTION 3447 "Collection of objects that represent LMP node 3448 configuration." 3449 ::= { lmpGroups 1 } 3451 lmpControlChannelGroup OBJECT-GROUP 3452 OBJECTS { 3453 lmpNbrRetransmitInterval, 3454 lmpNbrRetryLimit, 3455 lmpNbrRetransmitDelta, 3456 lmpNbrAdminStatus, 3457 lmpNbrOperStatus, 3458 lmpNbrRowStatus, 3459 lmpNbrStorageType, 3460 lmpCcHelloIntervalDefault, 3461 lmpCcHelloIntervalDefaultMin, 3462 lmpCcHelloIntervalDefaultMax, 3463 lmpCcHelloDeadIntervalDefault, 3464 lmpCcHelloDeadIntervalDefaultMin, 3465 lmpCcHelloDeadIntervalDefaultMax, 3466 lmpCcNbrNodeId, 3467 lmpCcRemoteId, 3468 lmpCcRemoteAddressType, 3469 lmpCcRemoteIpAddr, 3470 lmpCcSetupRole, 3471 lmpCcAuthentication, 3472 lmpCcHelloInterval, 3473 lmpCcHelloIntervalMin, 3474 lmpCcHelloIntervalMax, 3475 lmpCcHelloIntervalNegotiated, 3476 lmpCcHelloDeadInterval, 3477 lmpCcHelloDeadIntervalMin, 3478 lmpCcHelloDeadIntervalMax, 3479 lmpCcHelloDeadIntervalNegotiated, 3480 lmpCcOperStatus, 3481 lmpCcRowStatus, 3482 lmpCcStorageType, 3483 lmpCcUpDownNotificationsEnabled 3484 } 3485 STATUS current 3486 DESCRIPTION 3487 "Objects which can be used to configure LMP interface." 3489 ::= { lmpGroups 2 } 3491 lmpCcIsInterfaceGroup OBJECT-GROUP 3492 OBJECTS { lmpCcIsIf } 3493 STATUS current 3494 DESCRIPTION 3495 "Objects which can be used to configure control channels 3496 that are interfaces." 3497 ::= { lmpGroups 3 } 3499 lmpCcIsNotInterfaceGroup OBJECT-GROUP 3500 OBJECTS { lmpCcUnderlyingIfIndex, 3501 lmpCcIsIf, 3502 lmpCcLastChange, 3503 lmpCcAdminStatus 3504 } 3505 STATUS current 3506 DESCRIPTION 3507 "Objects which can be used to configure control channels 3508 that are not interfaces." 3509 ::= { lmpGroups 4 } 3511 lmpLinkPropertyCorrelationGroup OBJECT-GROUP 3512 OBJECTS { lmpLinkPropertyNotificationsEnabled } 3513 STATUS current 3514 DESCRIPTION 3515 "Collection of objects used to configure the link 3516 property correlation procedure." 3517 ::= { lmpGroups 5 } 3519 lmpLinkVerificationGroup OBJECT-GROUP 3520 OBJECTS { lmpGlobalLinkVerificationInterval, 3521 lmpLinkVerifyInterval, 3522 lmpLinkVerifyDeadInterval, 3523 lmpLinkVerifyTransportMechanism, 3524 lmpLinkVerifyAllLinks, 3525 lmpLinkVerifyTransmissionRate, 3526 lmpLinkVerifyWavelength, 3527 lmpLinkVerifyRowStatus, 3528 lmpLinkVerifyStorageType, 3529 lmpDataLinkNotificationsEnabled 3530 } 3531 STATUS current 3532 DESCRIPTION 3533 "Collection of objects that represent the link 3534 verification procedure configuration." 3535 ::= { lmpGroups 6 } 3537 lmpPerfGroup OBJECT-GROUP 3538 OBJECTS { lmpCcInOctets, 3539 lmpCcInDiscards, 3540 lmpCcInErrors, 3541 lmpCcOutOctets, 3542 lmpCcOutDiscards, 3543 lmpCcOutErrors, 3544 lmpCcConfigReceived, 3545 lmpCcConfigSent, 3546 lmpCcConfigRetransmit, 3547 lmpCcConfigAckReceived, 3548 lmpCcConfigAckSent, 3549 lmpCcConfigNackSent, 3550 lmpCcConfigNackReceived, 3551 lmpCcHelloReceived, 3552 lmpCcHelloSent, 3553 lmpCcBeginVerifyReceived, 3554 lmpCcBeginVerifySent, 3555 lmpCcBeginVerifyRetransmit, 3556 lmpCcBeginVerifyAckReceived, 3557 lmpCcBeginVerifyAckSent, 3558 lmpCcBeginVerifyNackReceived, 3559 lmpCcBeginVerifyNackSent, 3560 lmpCcEndVerifyReceived, 3561 lmpCcEndVerifySent, 3562 lmpCcEndVerifyRetransmit, 3563 lmpCcEndVerifyAckReceived, 3564 lmpCcEndVerifyAckSent, 3565 lmpCcTestStatusSuccessReceived, 3566 lmpCcTestStatusSuccessSent, 3567 lmpCcTestStatusSuccessRetransmit, 3568 lmpCcTestStatusFailureReceived, 3569 lmpCcTestStatusFailureSent, 3570 lmpCcTestStatusFailureRetransmit, 3571 lmpCcTestStatusAckReceived, 3572 lmpCcTestStatusAckSent, 3573 lmpCcLinkSummaryReceived, 3574 lmpCcLinkSummarySent, 3575 lmpCcLinkSummaryRetransmit, 3576 lmpCcLinkSummaryAckReceived, 3577 lmpCcLinkSummaryAckSent, 3578 lmpCcLinkSummaryNackReceived, 3579 lmpCcLinkSummaryNackSent, 3580 lmpCcChannelStatusReceived, 3581 lmpCcChannelStatusSent, 3582 lmpCcChannelStatusRetransmit, 3583 lmpCcChannelStatusAckReceived, 3584 lmpCcChannelStatusAckSent, 3585 lmpCcChannelStatusReqReceived, 3586 lmpCcChannelStatusReqSent, 3587 lmpCcChannelStatusReqRetransmit, 3588 lmpCcChannelStatusRspReceived, 3589 lmpCcChannelStatusRspSent, 3590 lmpCcCounterDiscontinuityTime, 3591 lmpTeInOctets, 3592 lmpTeOutOctets, 3593 lmpTeBeginVerifyReceived, 3594 lmpTeBeginVerifySent, 3595 lmpTeBeginVerifyRetransmit, 3596 lmpTeBeginVerifyAckReceived, 3597 lmpTeBeginVerifyAckSent, 3598 lmpTeBeginVerifyNackReceived, 3599 lmpTeBeginVerifyNackSent, 3600 lmpTeEndVerifyReceived, 3601 lmpTeEndVerifySent, 3602 lmpTeEndVerifyRetransmit, 3603 lmpTeEndVerifyAckReceived, 3604 lmpTeEndVerifyAckSent, 3605 lmpTeTestStatusSuccessReceived, 3606 lmpTeTestStatusSuccessSent, 3607 lmpTeTestStatusSuccessRetransmit, 3608 lmpTeTestStatusFailureReceived, 3609 lmpTeTestStatusFailureSent, 3610 lmpTeTestStatusFailureRetransmit, 3611 lmpTeTestStatusAckReceived, 3612 lmpTeTestStatusAckSent, 3613 lmpTeLinkSummaryReceived, 3614 lmpTeLinkSummarySent, 3615 lmpTeLinkSummaryRetransmit, 3616 lmpTeLinkSummaryAckReceived, 3617 lmpTeLinkSummaryAckSent, 3618 lmpTeLinkSummaryNackReceived, 3619 lmpTeLinkSummaryNackSent, 3620 lmpTeChannelStatusReceived, 3621 lmpTeChannelStatusSent, 3622 lmpTeChannelStatusRetransmit, 3623 lmpTeChannelStatusAckReceived, 3624 lmpTeChannelStatusAckSent, 3625 lmpTeChannelStatusReqReceived, 3626 lmpTeChannelStatusReqSent, 3627 lmpTeChannelStatusReqRetransmit, 3628 lmpTeChannelStatusRspSent, 3629 lmpTeChannelStatusRspReceived, 3630 lmpTeCounterDiscontinuityTime, 3631 lmpDataLinkTestReceived, 3632 lmpDataLinkTestSent, 3633 lmpDataLinkActiveTestSuccess, 3634 lmpDataLinkActiveTestFailure, 3635 lmpDataLinkPassiveTestSuccess, 3636 lmpDataLinkPassiveTestFailure, 3637 lmpDataLinkDiscontinuityTime 3638 } 3639 STATUS current 3640 DESCRIPTION 3641 "Collection of objects used to provide performance 3642 information about LMP interfaces and data-bearing links." 3643 ::= { lmpGroups 7 } 3645 lmpTeLinkGroup OBJECT-GROUP 3646 OBJECTS { lmpTeLinkNbrRemoteNodeId, 3647 lmpTeLinkVerification, 3648 lmpTeLinkFaultManagement, 3649 lmpTeLinkDwdm, 3650 lmpTeLinkOperStatus, 3651 lmpTeLinkRowStatus, 3652 lmpTeLinkStorageType, 3653 lmpTeLinkNotificationsEnabled 3654 } 3655 STATUS current 3656 DESCRIPTION 3657 "Objects which can be used to configure TE links." 3658 ::= { lmpGroups 8 } 3660 lmpDataLinkGroup OBJECT-GROUP 3661 OBJECTS { lmpDataLinkType, 3662 lmpDataLinkAddressType, 3663 lmpDataLinkIpAddr, 3664 lmpDataLinkRemoteIpAddress, 3665 lmpDataLinkRemoteIfId, 3666 lmpDataLinkEncodingType, 3667 lmpDataLinkActiveOperStatus, 3668 lmpDataLinkPassiveOperStatus, 3669 lmpDataLinkRowStatus, 3670 lmpDataLinkStorageType 3671 } 3672 STATUS current 3673 DESCRIPTION 3674 "Collection of objects that represent data-bearing link 3675 configuration." 3676 ::= { lmpGroups 9 } 3678 lmpNotificationGroup NOTIFICATION-GROUP 3679 NOTIFICATIONS { lmpTeLinkPropertyMismatch, 3680 lmpDataLinkPropertyMismatch, 3681 lmpUnprotected, 3682 lmpControlChannelUp, 3683 lmpControlChannelDown, 3684 lmpTeLinkDegraded, 3685 lmpTeLinkNotDegraded, 3686 lmpDataLinkVerificationFailure } 3687 STATUS current 3688 DESCRIPTION 3689 "Set of notifications defined in this module." 3690 ::= { lmpGroups 10 } 3692 -- End of LMP-MIB 3693 END 3695 10. Intellectual Property Considerations 3697 The IETF takes no position regarding the validity or scope of any 3698 intellectual property or other rights that might be claimed to 3699 pertain to the implementation or use of the technology described in 3700 this document or the extent to which any license under such rights 3701 might or might not be available; neither does it represent that it 3702 has made any effort to identify any such rights. Information on the 3703 IETF's procedures with respect to rights in standards-track and 3704 standards-related documentation can be found in BCP-11. Copies of 3705 claims of rights made available for publication and any assurances of 3706 licenses to be made available, or the result of an attempt made to 3707 obtain a general license or permission for the use of such 3708 proprietary rights by implementers or users of this specification can 3709 be obtained from the IETF Secretariat. 3711 The IETF invites any interested party to bring to its attention any 3712 copyrights, patents or patent applications, or other proprietary 3713 rights which may cover technology that may be required to practice 3714 this standard. Please address the information to the IETF Executive 3715 Director. 3717 By submitting this Internet Draft, we certify that any applicable 3718 patent or other IPR claims of which we are aware have been disclosed, 3719 and any of which we become aware will be disclosed, in accordance 3720 with RFC 3668. 3722 11. Security Considerations 3724 There are a number of management objects defined in this MIB module 3725 with a MAX-ACCESS clause of read-write and/or read-create. Such 3726 objects may be considered sensitive or vulnerable in some network 3727 environments. The support for SET operations in a non-secure 3728 environment without proper protection can have a negative effect on 3729 network operations. These are the tables and objects and their 3730 sensitivity/vulnerability: 3732 - Unauthorized changes to the lmpNbrTable, lmpControlChannelTable, 3733 lmpTeLinkTable and lmpDataLinkTable may disrupt allocation of 3734 resources in the network. 3736 Some of the readable objects in this MIB module (i.e., objects with a 3737 MAX-ACCESS other than not-accessible) may be considered sensitive or 3738 vulnerable in some network environments. It is thus important to 3739 control even GET and/or NOTIFY access to these objects and possibly 3740 to even encrypt the values of these objects when sending them over 3741 the network via SNMP. These are the tables and objects and their 3742 sensitivity/vulnerability: 3744 - The lmpNbrTable exposes network provider's node IP addresses. 3746 - lmpControlChannelTable exposes network provider's control 3747 network. 3749 - lmpDataLinkTable exposes network provider's data network. 3751 SNMP versions prior to SNMPv3 did not include adequate security. 3752 Even if the network itself is secure (for example by using IPSec), 3753 even then, there is no control as to who on the secure network is 3754 allowed to access and GET/SET (read/change/create/delete) the objects 3755 in this MIB module. 3757 It is RECOMMENDED that implementers consider the security features as 3758 provided by the SNMPv3 framework (see [RFC3410], section 8), 3759 including full support for the SNMPv3 cryptographic mechanisms (for 3760 authentication and privacy). 3762 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3763 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3764 enable cryptographic security. It is then a customer/operator 3765 responsibility to ensure that the SNMP entity giving access to an 3766 instance of this MIB module is properly configured to give access to 3767 the objects only to those principals (users) that have legitimate 3768 rights to indeed GET or SET (change/create/delete) them. 3770 12. Acknowledgments 3772 The general structure of this draft has been modeled around draft- 3773 ietf-mpls-lsr-mib-06.txt. 3775 The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and 3776 George Wang. 3778 13. IANA Considerations 3780 Each of the following "IANA Considerations" subsections requests IANA 3781 for a new assignment. New assignments can only be made via a 3782 Standards Action as specified in [RFC2434]. 3784 13.1. IANA Considerations for lmp ifType 3786 The IANA is requested to assign TBD ifType for LMP interfaces. 3788 13.2. IANA Considerations for LMP-MIB 3790 LMP-MIB should be rooted under the transmission subtree. The IANA is 3791 requested to assign { transmission TBD } to the LMP-MIB module 3792 specified in this document. The IANA is requested to use same number 3793 as the lmp ifType. 3795 14. References 3797 14.1. Normative References 3799 [RFC2026] Bradner, S., "The Internet Standards Process - 3800 Revision 3", RFC 2026, October 1996. 3802 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3803 Requirement Levels", BCP 14, RFC 2119, March 1997. 3805 [RFC2434] Narten, T., Alvestrand, H., "Guidelines for Writing 3806 an IANA Considerations Section in RFCs", RFC 2434, 3807 October 1998. 3809 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 3810 J., Rose, M., and S. Waldbusser, "Structure of 3811 Management Information Version 2 (SMIv2)", STD 58, 3812 RFC 2578, April 1999. 3814 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 3815 J., Rose, M., and S. Waldbusser, "Textual Conventions 3816 for SMIv2", STD 58, RFC 2579, April 1999. 3818 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 3819 J., Rose, M., and S. Waldbusser, "Conformance 3820 Statements for SMIv2", STD 58, RFC 2580, April 1999. 3822 [RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces 3823 Group MIB", RFC 2863, June 2000. 3825 [RFC2914] Floyd, S., "Congestion Control Principles", RFC 2914, 3826 September 2000. 3828 [RFC3291] Daniele, M., Haberman, B., Routhier, S., and 3829 Shoenwaelder, J., "Textual Conventions for Internet 3830 Network Addresses", RFC 3291, May 2002. 3832 [RFC3471] Ashwood-Smith, P., Banarjee, A., Berger, L., 3833 Bernstein, G., Drake, J., Fan, Y., Kompella, K., 3834 Lang, J., Mannie, E., Rajagopalan, B., Rekhter, Y., 3835 Saha, D., Sharma, V., Swallow, G., and Tang, B., 3836 "Generalized MPLS Signaling Functional Description", 3837 RFC 3471, January 2003. 3839 [RFC3667] Bradner, S., "IETF Rights in Contributions", 3840 RFC 3667, February 2004. 3842 [RFC3668] Bradner, S., "Intellectual Property Rights in IETF 3843 Technology", RFC 3668, February 2004. 3845 [TELINK-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J., 3846 "Traffic Engineering Link Management Information 3847 Base", Internet Draft 3848 , May 2004. 3850 [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., 3851 Rekhter, Y., Berger, L., Saha, S., Basak, D., 3852 Sandick, H., Zinin, A., Rajagopalan, B., and 3853 Ramamoorthi, S., "Link Management Protocol", 3854 Internet Draft , 3855 October 2003. 3857 [LMP-WDM] Fredette, A., Lang, J., "Link Management Protocol (LMP) 3858 for Dense Wavelength Division Multiplexing (DWDM) 3859 Optical Line Systems", Internet Draft 3860 , December 2003. 3862 [LMP-TEST] Lang, J., Papadimitriou, D., "SONET/SDH Encoding 3863 for Link Management (LMP) Test Messages", Internet 3864 Draft , 3865 December 2003. 3867 14.2. Informative References 3869 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 3870 "Introduction and Applicability Statements for 3871 Internet-Standard Management Framework", RFC 3410, 3872 December 2002. 3874 [BUNDLING] Kompella, K., Rekhter, Y., and Berger, L., 3875 "Link Bundling in MPLS Traffic Engineering", 3876 Internet Draft , 3877 July 2002. 3879 15. Authors' Addresses 3881 Martin Dubuc Jonathan P. Lang 3882 Email: dubuc.consulting@sympatico.ca Rincon Networks, Inc. 3883 110 El Paseo 3884 Santa Barbara, CA 93101 3885 Email: jplang@ieee.org 3887 Sudheer Dharanikota Evan McGinnis 3888 Email: sudheer@ieee.org Calient Networks, Inc. 3889 5853 Rue Ferrari 3890 San Jose, CA 95138 3891 Email: evan@calient.net 3893 Thomas D. Nadeau 3894 Cisco Systems, Inc. 3895 300 Apollo Drive 3896 Chelmsford, MA 01824 3897 Phone: +1-978-244-3051 3898 Email: tnadeau@cisco.com 3900 16. Full Copyright Statement 3902 Copyright (C) The Internet Society (2004). This document is subject 3903 to the rights, licenses and restrictions contained in BCP 78, and 3904 except as set forth therein, the authors retain all their rights. 3906 This document and translations of it may be copied and furnished to 3907 others, and derivative works that comment on or otherwise explain it 3908 or assist in its implementation may be prepared, copied, published 3909 and distributed, in whole or in part, without restriction of any 3910 kind, provided that the above copyright notice and this paragraph are 3911 included on all such copies and derivative works. However, this 3912 document itself may not be modified in any way, such as by removing 3913 the copyright notice or references to the Internet Society or other 3914 Internet organizations, except as needed for the purpose of 3915 developing Internet standards in which case the procedures for 3916 copyrights defined in the Internet Standards process must be 3917 followed, or as required to translate it into languages other than 3918 English. 3920 The limited permissions granted above are perpetual and will not be 3921 revoked by the Internet Society or its successors or assigns. This 3922 document and the information contained herein are provided on an "AS 3923 IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR 3924 IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 3925 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 3926 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 3927 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3928 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.