idnits 2.17.1 draft-ietf-ccamp-lmp-mib-01.txt: ** The Abstract section seems to be numbered 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: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 41 instances of too long lines in the document, the longest one being 5 characters in excess of 72. ** The abstract seems to contain references ([LMP]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (February 2002) is 8099 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 412, but not defined == Unused Reference: 'GMPLS' is defined on line 3166, but no explicit reference was found in the text == Unused Reference: 'BUNDLE' is defined on line 3175, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 3185, but no explicit reference was found in the text == Unused Reference: 'IANAFamily' is defined on line 3190, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'LMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS' -- Possible downref: Non-RFC (?) normative reference: ref. 'BUNDLE' -- Possible downref: Non-RFC (?) normative reference: ref. 'BUNDLE-MIB' ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAFamily' ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC') (Obsoleted by RFC 4301) Summary: 21 errors (**), 0 flaws (~~), 7 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 Meriton Networks 4 Expires: August 2002 5 Sudheer Dharanikota 6 Nayna Networks 8 Thomas D. Nadeau 9 Cisco Systems 11 Jonathan P. Lang 12 Evan McGinnis 13 Calient Networks 15 February 2002 17 Link Management Protocol Management Information Base 19 draft-ietf-ccamp-lmp-mib-01.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 Table of Contents 43 1. Abstract ..................................................... 2 44 2. Introduction ................................................. 2 45 3. Terminology .................................................. 3 46 4. The SNMP Management Framework ................................ 3 47 5. Feature Checklist ............................................ 4 48 6. Outline ...................................................... 5 49 6.1. Summary of LMP MIB ........................................... 5 50 7. Brief Description of MIB Objects ............................. 6 51 7.1. lmpNbrTable .................................................. 6 52 7.2. lmpControlChannelTable ....................................... 6 53 7.3. lmpControlChannelPerfTable ................................... 6 54 7.4. lmpTeLinkTable ............................................... 7 55 7.5. lmpLinkVerificationTable ..................................... 7 56 7.6. lmpDataBearingLinkTable ...................................... 7 57 7.7. lmpDataBearingLinkPerfTable .................................. 7 58 8. Example of LMP Control Channel Interface Setup ............... 7 59 9. Application of the Interfaces Group to LMP ................... 9 60 9.1. Support of the LMP Layer by ifTable .......................... 10 61 10. Link Management Protocol MIB Definitions ..................... 12 62 11. Security Considerations ...................................... 66 63 12. Acknowledgments .............................................. 67 64 13. References ................................................... 67 65 14. Authors' Addresses ........................................... 69 66 15. Full Copyright Statement ..................................... 70 68 1. Abstract 70 This memo defines an experimental portion of the Management Informa- 71 tion Base (MIB) for use with network management protocols in the 72 Internet community. In particular, it describes managed objects for 73 modeling the Link Management Protocol (LMP) [LMP]. 75 2. Introduction 77 Current work is underway in the IETF to specify a suite of protocols 78 to be used as a common control plane and a separate common measure- 79 ment plane. The Link Management Protocol, which primary purpose is to 80 manage traffic engineering (TE) links, is one of the key components 81 of this standardization activity. Primary goals of LMP are the 82 maintenance of the control channel connectivity, correlation of link 83 properties, verification of data-bearing links and detection and iso- 84 lation of link faults. 86 We describe in this document a MIB that can be used to manage LMP 87 implementations. This MIB covers both configuration and performance 88 monitoring aspects of LMP. 90 Comments should be made directly to the ccamp mailing list at 91 ccamp@ops.ietf.org. 93 This memo does not, in its draft form, specify a standard for the 94 Internet community. 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 98 document are to be interpreted as described in RFC 2119, reference 99 [BCP14]. 101 3. Terminology 103 This document uses terminology from the document describing the Link 104 Management Protocol [LMP]. An "LMP adjacency" is formed between two 105 nodes that support the same capabilities, and LMP messages are 106 exchanged between the node pair over control channels that form this 107 adjacency. Several control channels can be active at the same time. 108 With the exception of messages related to control channel management, 109 any time a LMP message needs to be transferred to a neighbor node, it 110 can be sent on any of the active control channels. The control chan- 111 nels can also be used to exchange MPLS control plane information or 112 routing information. 114 LMP is designed to support aggregation of one or more data-bearing 115 links into a traffic-engineering (TE) link. The data-bearing links 116 can be either component links or ports depending on their multiplex- 117 ing capability (see [LMP] for distinction between port and component 118 link). 120 Each TE link is associated with an LMP adjacency, and one or more 121 control channels are used to exchange LMP messages for a particular 122 adjacency. In turn, control channels are used to manage the TE links 123 associated with the LMP adjacency. 125 4. The SNMP Management Framework 127 The SNMP Management Framework presently consists of five major com- 128 ponents: 130 - An overall architecture, described in RFC 2571 [RFC2571]. 132 Mechanisms for describing and naming objects and events for the 133 purpose of management. The first version of this Structure of 134 Management Information (SMI) is called SMIv1 and described in 135 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 136 1215 [RFC1215]. The second version, called SMIv2, is described 137 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 138 STD 58, RFC 2580 [RFC2580]. 140 - Message protocols for transferring management information. The 141 first version of the SNMP message protocol is called SNMPv1 and 142 described in STD 15, RFC 1157 [RFC1157]. A second version of 143 the SNMP message protocol, which is not an Internet standards 144 track protocol, is called SNMPv2c and described in RFC 1901 145 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 146 message protocol is called SNMPv3 and described in RFC 1906 147 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 149 - Protocol operations for accessing management information. The 150 first set of protocol operations and associated PDU formats is 151 described in STD 15, RFC 1157 [RFC1157]. A second set of 152 protocol operations and associated PDU formats is described in 153 RFC 1905 [RFC1905]. 155 - A set of fundamental applications described in RFC 2573 156 [RFC2573] and the view-based access control mechanism described 157 in RFC 2575 [RFC2575]. 159 A more detailed introduction to the current SNMP Management Framework 160 can be found in RFC 2570 [RFC2570]. 162 Managed objects are accessed via a virtual information store, termed 163 the Management Information Base or MIB. Objects in the MIB are 164 defined using the mechanisms defined in the SMI. 166 This memo specifies a MIB module that is compliant to the SMIv2. A 167 MIB conforming to the SMIv1 can be produced through the appropriate 168 translations. The resulting translated MIB must be semantically 169 equivalent, except where objects or events are omitted because no 170 translation is possible (use of Counter64). Some machine readable 171 information in SMIv2 will be converted into textual descriptions in 172 SMIv1 during the translation process. However, this loss of machine 173 readable information is not considered to change the semantics of the 174 MIB. 176 5. Feature Checklist 178 The Link Management protocol MIB (LMP-MIB) is designed to satisfy the 179 following requirements and constraints: 181 - The MIB supports the enabling and disabling of LMP capability 182 on LMP capable interfaces of a photonic switch, optical 183 cross-connect or router. 185 - The MIB is used provide information about LMP adjacencies. 187 - Support is provided for configuration of the keep alive and 188 link verification parameters. 190 - The MIB is used to express the mapping between local and remote 191 TE links, as well as local and remote interface identifiers for 192 port or component link. 194 - Performance counters are provided for measuring LMP 195 performance on a per-control channel basis. Performance counters 196 are also provided for measuring LMP performance on the data- 197 bearing links. 199 Note that the LMP MIB goes hand-in-hand with the Link Bundling MIB 200 [BUNDLE-MIB]. The TE link table, which is used to associate data- 201 bearing links to TE links, is defined in the Link Bundling MIB. The 202 TE link table in the LMP MIB contains TE link information specific to 203 LMP. 205 6. Outline 207 Configuring LMP through an optical device involves the following 208 steps: 210 - Enabling LMP on LMP capable interfaces through control channel 211 configuration. 213 - Optionally specifying link verification parameters. 215 - Configuring the data-bearing links and associating them to the 216 appropriate TE link (this association is stored in the 217 ifStackTable of the Interfaces Group MIB). 219 TE links are managed by the control channels that run between the 220 same pair of nodes (LMP adjacency). 222 6.1. Summary of LMP MIB 224 The MIB objects for performing these actions consist of the following 225 tables: 227 - The remote node table (lmpNbrTable) is used to identify the pair 228 of nodes that exchange LMP messages over control channels. 230 - The control channel table (lmpControlChannelTable) is used 231 for enabling the LMP protocol on LMP-capable interfaces. 233 - The control channel performance table 234 (lmpControlChannelPerfTable) is used for collecting 235 LMP performance counts on a per-control channel basis. 237 - The TE link table (lmpTeLinkTable) is used for 238 specifying LMP information associated with TE links. 240 - The link verification table (lmpLinkVerificationTable) is used for 241 configuring the LMP link verification parameters of TE links. 243 - The data-bearing link table (lmpDataBearingLinkTable) is used to 244 specify the data-bearing links that are associated with TE links. 246 - The data-bearing link performance table 247 (lmpDataBearingLinkPerfTable) is used for collecting LMP 248 performance counts on data-bearing links. 250 These tables are described in the subsequent sections. 252 7. Brief Description of MIB Objects 254 Sections 7.1-7.3 describe objects pertaining to LMP-capable inter- 255 faces. Section 7.4 to 7.7 describes objects for specifying TE links 256 and data-bearing links. The MIB objects were derived from the LMP 257 document [LMP]. 259 7.1. lmpNbrTable 261 This table identifies the pairs of nodes on which LMP is enabled. 263 7.2. lmpControlChannelTable 265 This table represents the interfaces that are LMP capable (i.e. capa- 266 ble of transmitting LMP messages). A photonic switch, optical cross- 267 connect, or router creates an entry in this table for every LMP capa- 268 ble interface on that device. 270 7.3. lmpControlChannelPerfTable 272 This table contains the objects to measure the LMP performance of LMP 273 capable interfaces and is an AUGMENT to the lmpControlChannelTable. 274 High capacity counters are provided for objects that are likely to 275 wrap around quickly. 277 7.4. lmpTeLinkTable 279 This table represents the TE link information specific to LMP. 281 7.5. lmpLinkVerificationTable 283 This table augments the lmpTeLinkTable and represents the link verif- 284 ication parameters associated with the TE links. 286 7.6. lmpDataBearingLinkTable 288 The data-bearing link table enumerates the data-bearing links that 289 are associated with each TE link. 291 7.7. lmpDataBearingLinkPerfTable 293 This table augments the lmpDataBearingLinkTable. It contains the 294 objects to measure the LMP performance of data-bearing links. 296 8. Example of LMP Control Channel Setup 298 In this section we provide a brief example of using the MIB 299 objects described in section 10 to set up an LMP control channel. 300 While this example is not meant to illustrate every nuance of the 301 MIB, it is intended as an aid to understanding some of the key 302 concepts. It is meant to be read after going through the MIB itself. 304 Suppose that one would like to form an LMP adjacency between two 305 nodes using two control channels. Suppose also that there are 306 three data-bearing links. We also assume that the data-bearing 307 links are ports (lambdas). We also assume that the link 308 verification procedure is not enabled. The following example 309 illustrates which rows and corresponding objects might be created 310 to accomplish this. 312 First, LMP must be enabled between the pair of nodes. 314 In lmpNbrTable: 315 { 316 lmpNbrNodeId = 'c0010101'H, -- 192.1.1.1 317 lmpNbrRetransmitInterval = 10, 318 lmpNbrRetransmitTimeoutInterval = 0, 319 lmpNbrAdminStatus = up(1), 320 lmpNbrRowStatus = createAndGo(4) 322 } 324 Then, the control channels must be set up. These are created in 325 the lmpControlChannelTable. 327 In lmpControlChannelTable: 328 { 329 lmpCcId = 1, 330 lmpCcUnderlyingIfIndex = 1, 331 lmCcIsIf = false(1), 332 lmpCcAuthentication = false(1), 333 lmpCcConfigRetransmitInterval = 10, 334 lmpCcHelloInterval = 15, 335 lmpCcHelloIntervalMin = 15, 336 lmpCcHelloIntervalMax = 1000, 337 lmpCcHelloDeadInterval = 45, 338 lmpCcHelloDeadIntervalMin = 45, 339 lmpCcHelloDeadIntervalMax = 1000, 340 lmpCcAdminStatus = up(1), 341 lmpCcRowStatus = createAndGo(4) 342 } 344 { 345 lmpCcId = 2, 346 lmpCcUnderlyingIfIndex = 2, 347 lmCcIsIf = false(1), 348 lmpCcAuthentication = false(1), 349 lmpCcConfigRetransmitInterval = 10, 350 lmpCcHelloInterval = 15, 351 lmpCcHelloIntervalMin = 15, 352 lmpCcHelloIntervalMax = 1000, 353 lmpCcHelloDeadInterval = 45, 354 lmpCcHelloDeadIntervalMin = 45, 355 lmpCcHelloDeadIntervalMax = 1000, 356 lmpCcAdminStatus = up(1), 357 lmpCcRowStatus = createAndGo(4) 358 } 360 Next, the three data-bearing links are created. For each data- 361 bearing link, an ifEntry with the same ifIndex needs to be created 362 beforehand. 364 In lmpDataBearingLinkTable: 365 { 366 ifIndex = 41, 367 lmpDataBearingLinkNumberingType = unnumbered(1), 368 lmpDataBearingLinkRemoteIfId = 47, 369 lmpDataBearingLinkRowStatus = createAndGo(4) 371 } 373 { 374 ifIndex = 43, 375 lmpDataBearingLinkNumberingType = unnumbered(1), 376 lmpDataBearingLinkRemoteIfId = 42, 377 lmpDataBearingLinkRowStatus = createAndGo(4) 378 } 380 { 381 ifIndex = 44, 382 lmpDataBearingLinkNumberingType = unnumbered(1), 383 lmpDataBearingLinkRemoteIfId = 48, 384 lmpDataBearingLinkRowStatus = createAndGo(4) 385 } 387 Note that the data-bearing link type (lmpDataBearingLinkType) does 388 not need to be provisioned as it is automatically populated by the 389 node. The definition of the protection role (primary or 390 secondary) for the data-bearing links is stored in the 391 dataBearingChannelTable of the Link Bundling MIB [BUNDLE-MIB]. 393 Then, a TE link is created as an ifEntry with ifType teLink in 394 the ifTable. 396 Once the TE link is created in the ifTable, a TE link entry 397 is created in the LMP MIB to specify TE link information specific 398 to LMP. 400 In lmpTeLinkTable: 401 { 402 ifIndex = 20, 403 lmpTeLinkVerification = true(2), 404 lmpTeLinkFaultManagement = true(2), 405 lmpTeLinkDwdm = false(1), 406 lmpTeLinkBitRate = 100000, 407 lmpTeLinkWavelength = 0, 408 lmpTeLinkRowStatus = createAndGo(4) 409 } 411 The association between the data-bearing links and the TE links is 412 stored in the ifStackTable [IF-MIB]. 414 In parallel with the entry created in the lmpTeLinkTable, an entry 415 may be created in the teLinkTable of Link Bundling MIB 416 [BUNDLE-MIB]. 418 9. Application of the Interfaces Group to LMP 420 The Interfaces Group [IFMIB] defines generic managed objects for 421 managing interfaces. This memo contains the media-specific 422 extensions to the Interfaces Group for managing LMP control channels 423 that are modeled as interfaces. If the control channel as defined in 424 the lmpControlChannelTable is modeled as an ifEntry, then the 425 following definition applies. An lmpControlChannelTable entry is 426 designated as being represented as an Interfaces MIB ifEntry if the 427 lmpControlChannelEntry object lmpCcIsIf is set to true (2). In this 428 case, the control channel SHOULD be modeled as an ifEntry and 429 provide appropriate interface stacking as defined below. 431 This memo assumes the interpretation of the Interfaces Group to be 432 in accordance with [IFMIB] which states that the interfaces table 433 (ifTable) contains information on the managed resource's 434 interfaces and that each sub-layer below the internetwork layer of 435 a network interface is considered an interface. Since the LMP 436 interface only carries control traffic, it is considered to be below 437 the internetwork layer. Thus, the LMP interface may be represented 438 as an entry in the ifTable. The inter-relation of entries in the 439 ifTable is defined by Interfaces Stack Group defined in [IFMIB]. 441 When LMP control channels are modeled as interfaces, the interface 442 stack table must appear as follows for the LMP control channel 443 interfaces: 445 +----------------------------------------+ 446 | LMP-interface ifType = lmp(TBD) + 447 +----------------------------------------+ 448 | Underlying Layer... + 449 +----------------------------------------+ 451 In the above diagram, "Underlying Layer..." refers to the ifIndex 452 of any interface type over which the LMP interface will transmit 453 its traffic. Note that if the underlying layer provides multiple 454 access to its media (i.e.: Ethernet), then it is possible to stack 455 multiple LMP interfaces on top of this interface in parallel. 457 9.1. Support of the LMP Layer by ifTable 459 Some specific interpretations of ifTable for the LMP layer 460 follow. 462 Object Use for the LMP layer 464 ifIndex Each LMP interface may be represented by an ifEntry. 466 ifDescr Description of the LMP interface. 468 ifType The value that is allocated for LMP is TBD. 469 This number will be assigned by the IANA. 471 ifSpeed The total bandwidth in bits per second for use by 472 the LMP layer. 474 ifPhysAddress Unused. 476 ifAdminStatus This variable indicates the administrator's intent 477 as to whether LMP should be enabled, disabled, or 478 running in some diagnostic testing mode on this 479 interface. Also see [IFMIB]. 481 ifOperStatus This value reflects the actual or operational 482 status of LMP on this interface. 484 ifLastChange See [IFMIB]. 486 ifInOctets The number of received octets over the interface, 487 i.e., the number of octets received as LMP 488 packets. 490 ifOutOctets The number of transmitted octets over the 491 interface, i.e., the number of octets transmitted 492 as LMP packets. 494 ifInErrors The number of LMP packets dropped due to 495 uncorrectable errors. 497 ifInUnknownProtos 498 The number of received packets discarded during 499 packet header validation, including packets with 500 unrecognized label values. 502 ifOutErrors See [IFMIB]. 504 ifName Textual name (unique on this system) of the 505 interface or an octet string of zero length. 507 ifLinkUpDownTrapEnable 508 Default is disabled (2). 510 ifConnectorPresent 511 Set to false (2). 513 ifHighSpeed See [IFMIB]. 515 ifHCInOctets The 64-bit version of ifInOctets; supported if 516 required by the compliance statements in [IFMIB]. 518 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 519 required by the compliance statements in [IFMIB]. 521 ifAlias The non-volatile 'alias' name for the interface as 522 specified by a network manager. 524 ifCounterDiscontinuityTime 525 See [IFMIB]. 527 10. LMP MIB Definitions 529 LMP-MIB DEFINITIONS ::= BEGIN 531 IMPORTS 532 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 533 experimental, Integer32, Unsigned32, Counter32, TimeTicks 534 FROM SNMPv2-SMI 536 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 537 FROM SNMPv2-CONF 539 TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, 540 RowPointer, TimeStamp 541 FROM SNMPv2-TC 543 InterfaceIndex, InterfaceIndexOrZero, ifIndex, ifStackHigherLayer 544 FROM IF-MIB 546 InetAddressType, InetAddress 547 FROM INET-ADDRESS-MIB 549 teLinkRemoteIpAddr, teLinkIncomingIfId 550 FROM LINK-BUNDLING-MIB; 552 lmpMIB MODULE-IDENTITY 553 LAST-UPDATED "200202261200Z" -- 26 February 2002 12:00:00 EST 554 ORGANIZATION "Common Control and Measurement Protocols (CCAMP) 555 Working Group" 556 CONTACT-INFO 557 " Martin Dubuc 558 Postal: Meriton Networks 559 3026 Solandt Road 560 Kanata, ON, CANADA K2K 2A5 561 Tel: +1-613-270-9279 x253 562 Email: martin.dubuc@meriton.com 564 Sudheer Dharanikota 565 Postal: Nayna Networks, Inc. 566 157 Topaz Street 567 Milipitas, CA 95035 568 Tel: +1-408-956-8000 x357 569 Email: sudheer@nayna.com 571 Thomas D. Nadeau 572 Postal: Cisco Systems, Inc. 573 300 Apollo Drive 574 Chelmsford, MA 01824 575 Tel: +1-978-244-3051 576 Email: tnadeau@cisco.com 578 Jonathan P. Lang 579 Postal: Calient Networks, Inc. 580 25 Castilian Drive 581 Goleta, CA 93117 582 Email: jplang@calient.net 584 Evan McGinnis 585 Postal: Calient Networks, Inc. 586 5853 Rue Ferrari 587 San Jose, CA 95138 588 Email: evan@calient.net" 590 DESCRIPTION 591 "This MIB contains managed object definitions for the 592 Link Management Protocol (LMP) as 593 defined in: Lang, J., Mitra, K., Drake, J., Kompella, K., 594 Rekhter, Y., Berger, L., Saha, D., 595 Basak, D., Sandick, H., Zinin, A., and 596 Rajagopalan, B., Link Management Protocol, 597 Internet Draft , 598 November 2001." 600 -- Revision history. 601 REVISION 602 "200202261200Z" -- 26 February 2002 12:00:00 EST 603 DESCRIPTION 604 "- Used latest MIB boiler plate. 605 - Added lmpFullModuleCompliance conformance statement. 606 - Replaced IpAddress with InetAddress. 607 - Added lmpOperStatus. 608 - Added lmpCcHelloIntervalNegotiated and 609 lmpCcHelloDeadIntervalNegotiated. 610 - Converted all 64-bit counters to 32-bit counters. 611 - Added counters for all LMP message types. 612 - Added counters to monitor data-bearing link tests. 613 - Reintroduced lmpNbrRetransmitTimeout. 614 - Added lmpDataBearingLinkNumberingType and 615 lmpDataBearingLinkRemoteIpAddress. 616 - Split data-bearing link operational status into active and 617 passive operational status. 618 - Updated description of all row status and storage type objects. 619 - Updated references." 620 REVISION 621 "200110211200Z" -- 21 October 2001 12:00:00 EST 622 DESCRIPTION 623 "- Minor syntax fixes. 624 - Added lmpCcId. Changed type of lmpRemoteCcId. 625 - Updated lmpTeLinkEncodingType. 626 - Removed lmpRemoteTeLinkType and lmpRemoteTeLinkId (their 627 content can be derived from LINK-BUNDLING-MIB). 628 - Added lmpCcLastChange, lmpCcCounterDiscontinuityTime and 629 lmpDataBearingLinkCounterDiscontinuityTime. 630 - Moved lmpTeLinkBitRate and lmpTeLinkWavelength to 631 lmpLinkVerificationTable. 632 - Updated lmpDataBearingLinkOperStatus. 633 - Modified performance counters to account for changes in 634 channel status message types. 635 - Changed indices for lmpTeLinkPropertyMismatch and 636 lmpDataBearingLinkPropertyMismatch notifications. 637 - Renamed lmpNbrLinkSumRetransmitInterval. Removed 638 lmpNbrRetransmitTimeout. 639 - Added lmpCcUnderlyingIfId, lmpCcIsIf and lmpCcSetupRole." 640 REVISION 641 "200105221200Z" -- 22 May 2001 12:00:00 EST 642 DESCRIPTION 643 "Updates based on IETF-50 feedback. Aligned with 644 upcoming version of LMP draft." 645 REVISION 646 "200102221200Z" -- 22 February 2001 12:00:00 EST 647 DESCRIPTION 648 "Updates based on MPLS mailing list feedback." 649 REVISION 650 "200101261200Z" -- 26 January 2001 12:00:00 EST 651 DESCRIPTION 652 "Initial draft version." 653 ::= { experimental 113 } 655 -- Textual Conventions 656 NodeID ::= TEXTUAL-CONVENTION 657 STATUS current 658 DESCRIPTION 659 "This value represents a Node ID." 660 SYNTAX InetAddress 662 LmpInterval ::= TEXTUAL-CONVENTION 663 DISPLAY-HINT "d" 664 STATUS current 665 DESCRIPTION 666 "The interval delay in milliseconds." 667 SYNTAX Unsigned32 (1..65535) 669 LmpRetransmitInterval ::= TEXTUAL-CONVENTION 670 DISPLAY-HINT "d" 671 STATUS current 672 DESCRIPTION 673 "The retransmission interval delay in milliseconds." 674 SYNTAX Unsigned32 (1..4294967295) 676 -- Top level components of this MIB 678 -- Notifications 679 lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 } 680 -- Tables, Scalars 681 lmpObjects OBJECT IDENTIFIER ::= { lmpMIB 1 } 682 -- Conformance 683 lmpConformance OBJECT IDENTIFIER ::= { lmpMIB 2 } 685 lmpAdminStatus OBJECT-TYPE 686 SYNTAX INTEGER { up(1), down(2) } 687 MAX-ACCESS read-write 688 STATUS current 689 DESCRIPTION 690 "The desired operational status of LMP on the node." 691 DEFVAL { up } 692 ::= { lmpObjects 1 } 694 lmpOperStatus OBJECT-TYPE 695 SYNTAX INTEGER { up(1), down(2) } 696 MAX-ACCESS read-only 697 STATUS current 698 DESCRIPTION 699 "The actual operational status of LMP on the node." 700 ::= { lmpObjects 2 } 702 -- LMP Neighbor Table 704 lmpNbrTable OBJECT-TYPE 705 SYNTAX SEQUENCE OF LmpNbrEntry 706 MAX-ACCESS not-accessible 707 STATUS current 708 DESCRIPTION 709 "This table specifies the neighbor node(s) to which control channels 710 may be established." 711 ::= { lmpObjects 3 } 713 lmpNbrEntry OBJECT-TYPE 714 SYNTAX LmpNbrEntry 715 MAX-ACCESS not-accessible 716 STATUS current 717 DESCRIPTION 718 "An entry in this table is created by a LMP-enabled device for 719 every pair of nodes that can establish control channels." 720 INDEX { lmpNbrNodeId } 721 ::= { lmpNbrTable 1 } 723 LmpNbrEntry ::= SEQUENCE { 724 lmpNbrNodeId NodeID, 725 lmpNbrRetransmitInterval LmpRetransmitInterval, 726 lmpNbrRetransmitTimeout Unsigned32, 727 lmpNbrAdminStatus INTEGER, 728 lmpNbrOperStatus INTEGER, 729 lmpNbrRowStatus RowStatus, 730 lmpNbrStorageType StorageType 731 } 733 lmpNbrNodeId OBJECT-TYPE 734 SYNTAX NodeID 735 MAX-ACCESS accessible-for-notify 736 STATUS current 737 DESCRIPTION 738 "This is a unique index for an entry in the LmpNbrTable. 739 This value represents the remote Node ID." 740 ::= { lmpNbrEntry 1 } 742 lmpNbrRetransmitInterval OBJECT-TYPE 743 SYNTAX LmpRetransmitInterval 744 MAX-ACCESS read-create 745 STATUS current 746 DESCRIPTION 747 "This object specifies the interval that is used for the 748 retransmission of LinkSummary, BeginVerify and EndVerify messages." 749 REFERENCE 750 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 751 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 752 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 753 B. Rajagopalan, November 2001." 754 ::= { lmpNbrEntry 2 } 756 lmpNbrRetransmitTimeout OBJECT-TYPE 757 SYNTAX Unsigned32 758 MAX-ACCESS read-create 759 STATUS current 760 DESCRIPTION 761 "This object specifies the LinkSummary, BeginVerify and EndVerify 762 retransmission timeout period. If the specified timeout expires 763 and the LinkSummary, BeginVerify and EndVerify message has not yet 764 been acknowledged with a LinkSummaryAck, BeginVerifyAck or 765 EndVerifyAck message, a node can stop retransmitting the LinkSummary, 766 BeginVerify or EndVerify messages. A value of 0 is used to indicate 767 that a node should never stop retransmission." 768 REFERENCE 769 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 770 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 771 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 772 B. Rajagopalan, November 2001." 773 DEFVAL { 0 } 774 ::= { lmpNbrEntry 7 } 776 lmpNbrAdminStatus OBJECT-TYPE 777 SYNTAX INTEGER { up(1), down(2) } 778 MAX-ACCESS read-create 779 STATUS current 780 DESCRIPTION 781 "The desired operational status of LMP to this remote node." 782 ::= { lmpNbrEntry 3 } 784 lmpNbrOperStatus OBJECT-TYPE 785 SYNTAX INTEGER { up(1), down(2) } 786 MAX-ACCESS read-only 787 STATUS current 788 DESCRIPTION 789 "The actual operational status of LMP to this remote node." 790 ::= { lmpNbrEntry 4 } 792 lmpNbrRowStatus OBJECT-TYPE 793 SYNTAX RowStatus 794 MAX-ACCESS read-create 795 STATUS current 796 DESCRIPTION 797 "This variable is used to create, modify, and/or 798 delete a row in this table. All read-create objects 799 can be changed when lmpNbrRowStatus is active." 800 ::= { lmpNbrEntry 5 } 802 lmpNbrStorageType OBJECT-TYPE 803 SYNTAX StorageType 804 MAX-ACCESS read-create 805 STATUS current 806 DESCRIPTION 807 "The storage type for this conceptual row in the 808 lmpNbrTable. Conceptual rows having the value 809 'permanent' need not allow write-access to any 810 columnar object in the row." 811 ::= { lmpNbrEntry 6 } 813 -- End of lmpNbrTable 815 lmpCcHelloIntervalDefault OBJECT-TYPE 816 SYNTAX LmpInterval 817 MAX-ACCESS read-write 818 STATUS current 819 DESCRIPTION 820 "This object specifies the default value for the HelloInterval 821 parameter used in the Hello protocol keep-alive phase. It 822 indicates how frequently LMP Hello messages will be sent. It 823 is used a the default value for lmpCcHelloInterval." 824 REFERENCE 825 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 826 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 827 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 828 B. Rajagopalan, November 2001." 829 ::= { lmpObjects 4 } 831 lmpCcHelloIntervalDefaultMin OBJECT-TYPE 832 SYNTAX LmpInterval 833 MAX-ACCESS read-write 834 STATUS current 835 DESCRIPTION 836 "This object specifies the default minimum value for the 837 HelloInterval parameter. It is used as a default value 838 for lmpCcHelloIntervalMin." 839 ::= { lmpObjects 5 } 841 lmpCcHelloIntervalDefaultMax OBJECT-TYPE 842 SYNTAX LmpInterval 843 MAX-ACCESS read-write 844 STATUS current 845 DESCRIPTION 846 "This object specifies the default maximum value for the 847 HelloInterval parameter. It is used as a default value 848 for lmpCcHelloIntervalMax." 849 ::= { lmpObjects 6 } 851 lmpCcHelloDeadIntervalDefault OBJECT-TYPE 852 SYNTAX LmpInterval 853 MAX-ACCESS read-write 854 STATUS current 855 DESCRIPTION 856 "This object specifies the default HelloDeadInterval parameter to 857 use in the Hello protocol keep-alive phase. It indicates how long 858 a device should wait before declaring the control channel dead. 859 The HelloDeadInterval parameter should be at least three times the 860 value of HelloInterval. It is used a a default value for 861 lmpCcHelloDeadInterval." 862 REFERENCE 863 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 864 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 865 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 866 B. Rajagopalan, November 2001." 867 ::= { lmpObjects 7 } 869 lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE 870 SYNTAX LmpInterval 871 MAX-ACCESS read-write 872 STATUS current 873 DESCRIPTION 874 "This object specifies the default minimum value for the 875 HelloDeadInterval parameter. It is used as a default value 876 for lmpCcHelloDeadIntervalMin." 877 ::= { lmpObjects 8 } 879 lmpCcHelloDeadIntervalDefaultMax OBJECT-TYPE 880 SYNTAX LmpInterval 881 MAX-ACCESS read-write 882 STATUS current 883 DESCRIPTION 884 "This object specifies the default maximum value for the 885 HelloDeadInterval parameter. It is used as a default value 886 for lmpCcHelloDeadIntervalMax." 887 ::= { lmpObjects 9 } 889 -- LMP Control Channel Table 891 lmpControlChannelTable OBJECT-TYPE 892 SYNTAX SEQUENCE OF LmpControlChannelEntry 893 MAX-ACCESS not-accessible 894 STATUS current 895 DESCRIPTION 896 "This table specifies LMP control channel information." 897 ::= { lmpObjects 10 } 899 lmpControlChannelEntry OBJECT-TYPE 900 SYNTAX LmpControlChannelEntry 901 MAX-ACCESS not-accessible 902 STATUS current 903 DESCRIPTION 904 "An entry in this table is created by a LMP-enabled device for 905 every control channel. Whenever a new entry is created with lmpCcIsIf 906 set to true(2), then a corresponding entry is created in ifTable as 907 well (see RFC 2863)." 908 INDEX { lmpCcId } 909 ::= { lmpControlChannelTable 1 } 911 LmpControlChannelEntry ::= SEQUENCE { 912 lmpCcId Unsigned32, 913 lmpCcUnderlyingIfIndex InterfaceIndexOrZero, 914 lmpCcIsIf TruthValue, 915 lmpCcNbrNodeId NodeID, 916 lmpRemoteCcId Unsigned32, 917 lmpCcSetupRole INTEGER, 918 lmpCcAuthentication TruthValue, 919 lmpCcConfigRetransmitInterval LmpRetransmitInterval, 920 lmpCcConfigRetransmitTimeout Unsigned32, 921 lmpCcHelloInterval LmpInterval, 922 lmpCcHelloIntervalMin LmpInterval, 923 lmpCcHelloIntervalMax LmpInterval, 924 lmpCcHelloIntervalNegotiated LmpInterval, 925 lmpCcHelloDeadInterval LmpInterval, 926 lmpCcHelloDeadIntervalMin LmpInterval, 927 lmpCcHelloDeadIntervalMax LmpInterval, 928 lmpCcHelloDeadIntervalNegotiated LmpInterval, 929 lmpCcLastChange TimeTicks, 930 lmpCcAdminStatus INTEGER, 931 lmpCcOperStatus INTEGER, 932 lmpCcRowStatus RowStatus, 933 lmpCcStorageType StorageType 934 } 936 lmpCcId OBJECT-TYPE 937 SYNTAX Unsigned32 938 MAX-ACCESS accessible-for-notify 939 STATUS current 940 DESCRIPTION 941 "This value represents the local control channel identifier." 942 ::= { lmpControlChannelEntry 1 } 944 lmpCcUnderlyingIfIndex OBJECT-TYPE 945 SYNTAX InterfaceIndexOrZero 946 MAX-ACCESS read-create 947 STATUS current 948 DESCRIPTION 949 "This value represents the underlying interface index, i.e. the 950 interface index of the interface over which the LMP interface 951 will transmit its traffic. If set to 0, then the control channel 952 is not associated with any underlying interface. If the control 953 channel is not associated with an underlying interface, the control 954 channel's operational status must not be up(1), nor should the 955 control channel forward or receive traffic." 956 ::= { lmpControlChannelEntry 2 } 958 lmpCcIsIf OBJECT-TYPE 959 SYNTAX TruthValue 960 MAX-ACCESS read-create 961 STATUS current 962 DESCRIPTION 963 "Denotes whether or not this control channel corresponds to 964 an interface represented in the interfaces group table." 965 ::= { lmpControlChannelEntry 3 } 967 lmpCcNbrNodeId OBJECT-TYPE 968 SYNTAX NodeID 969 MAX-ACCESS read-create 970 STATUS current 971 DESCRIPTION 972 "This is the Node ID of the control channel remote node. 973 This value is either configured or gets created by the node 974 when a Config message is received or when an outgoing Config 975 message is acknowledged by the remote node." 976 ::= { lmpControlChannelEntry 4 } 978 lmpRemoteCcId OBJECT-TYPE 979 SYNTAX Unsigned32 980 MAX-ACCESS read-only 981 STATUS current 982 DESCRIPTION 983 "This value represents the remote control channel identifier. It is 984 determined during the negotiation phase. A value 985 of zero means that the remote control channel identifier has not 986 yet been learnt." 987 ::= { lmpControlChannelEntry 5 } 989 lmpCcSetupRole OBJECT-TYPE 990 SYNTAX INTEGER { active(1), passive(2) } 991 MAX-ACCESS read-create 992 STATUS current 993 DESCRIPTION 994 "The role that this node should take during establishment of this 995 control channel. An active node will initiate establishment. A 996 passive node will wait for the remote node to initiate. A pair 997 of nodes that both take the passive role will never establish 998 communications." 999 DEFVAL { active } 1000 ::= { lmpControlChannelEntry 6 } 1002 lmpCcAuthentication OBJECT-TYPE 1003 SYNTAX TruthValue 1004 MAX-ACCESS read-create 1005 STATUS current 1006 DESCRIPTION 1007 "This object indicates whether the control channel should use 1008 authentication." 1009 REFERENCE 1010 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 1011 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1012 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1013 B. Rajagopalan, November 2001." 1014 ::= { lmpControlChannelEntry 7 } 1016 lmpCcConfigRetransmitInterval OBJECT-TYPE 1017 SYNTAX LmpRetransmitInterval 1018 MAX-ACCESS read-create 1019 STATUS current 1020 DESCRIPTION 1021 "This object specifies the interval that is used for the 1022 retransmission of Config messages during the parameter 1023 negotiation phase." 1024 REFERENCE 1025 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 1026 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1027 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1028 B. Rajagopalan, November 2001." 1029 ::= { lmpControlChannelEntry 8 } 1031 lmpCcConfigRetransmitTimeout OBJECT-TYPE 1032 SYNTAX Unsigned32 1033 MAX-ACCESS read-create 1034 STATUS current 1035 DESCRIPTION 1036 "This object specifies the Config retransmission timeout 1037 period. If the specified timeout expires and no Config, 1038 ConfigAck or ConfigNack message has been received, a node 1039 can stop retransmitting Config messages on the control 1040 channel. A value of 0 is used to indicate that a node should 1041 never stop retransmission. This parameter (if non-zero) 1042 should be greater than lmpCcConfigRetransmitInterval." 1043 REFERENCE 1044 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 1045 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1046 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1047 B. Rajagopalan, November 2001." 1048 DEFVAL { 0 } 1049 ::= { lmpControlChannelEntry 9 } 1051 lmpCcHelloInterval OBJECT-TYPE 1052 SYNTAX LmpInterval 1053 MAX-ACCESS read-create 1054 STATUS current 1055 DESCRIPTION 1056 "This object specifies the value of the HelloInterval 1057 parameter. The default value for this object should be 1058 set to lmpCcHelloIntervalDefault." 1059 ::= { lmpControlChannelEntry 10 } 1061 lmpCcHelloIntervalMin OBJECT-TYPE 1062 SYNTAX LmpInterval 1063 MAX-ACCESS read-create 1064 STATUS current 1065 DESCRIPTION 1066 "This object specifies the minimum value for the 1067 HelloInterval parameter. The default value for this 1068 object should be set to lmpCcHelloIntervalMinDefault." 1069 ::= { lmpControlChannelEntry 11 } 1071 lmpCcHelloIntervalMax OBJECT-TYPE 1072 SYNTAX LmpInterval 1073 MAX-ACCESS read-create 1074 STATUS current 1075 DESCRIPTION 1076 "This object specifies the maximum value for the 1077 HelloInterval parameter. The default value for this 1078 object should be set to lmpCcHelloIntervalMaxDefault." 1079 ::= { lmpControlChannelEntry 12 } 1081 lmpCcHelloIntervalNegotiated OBJECT-TYPE 1082 SYNTAX LmpInterval 1083 MAX-ACCESS read-only 1084 STATUS current 1085 DESCRIPTION 1086 "Once the control channel is active, this object represents 1087 the negotiated HelloInterval value." 1088 ::= { lmpControlChannelEntry 13 } 1090 lmpCcHelloDeadInterval OBJECT-TYPE 1091 SYNTAX LmpInterval 1092 MAX-ACCESS read-create 1093 STATUS current 1094 DESCRIPTION 1095 "This object specifies the value of the HelloDeadInterval 1096 parameter. The default value for this object should be 1097 set to lmpCcHelloDeadIntervalDefault." 1098 ::= { lmpControlChannelEntry 14 } 1100 lmpCcHelloDeadIntervalMin OBJECT-TYPE 1101 SYNTAX LmpInterval 1102 MAX-ACCESS read-create 1103 STATUS current 1104 DESCRIPTION 1105 "This object specifies the minimum value for the 1106 HelloDeadInterval parameter. The default value for this 1107 object should be set to lmpCcHelloDeadIntervalMinDefault." 1108 ::= { lmpControlChannelEntry 15 } 1110 lmpCcHelloDeadIntervalMax OBJECT-TYPE 1111 SYNTAX LmpInterval 1112 MAX-ACCESS read-create 1113 STATUS current 1114 DESCRIPTION 1115 "This object specifies the maximum value for the 1116 HelloDeadInterval parameter. The default value for this 1117 object should be set to lmpCcHelloIntervalMaxDefault." 1118 ::= { lmpControlChannelEntry 16 } 1120 lmpCcHelloDeadIntervalNegotiated OBJECT-TYPE 1121 SYNTAX LmpInterval 1122 MAX-ACCESS read-only 1123 STATUS current 1124 DESCRIPTION 1125 "Once the control channel is active, this object represents 1126 the negotiated HelloDeadInterval value." 1127 ::= { lmpControlChannelEntry 17 } 1129 lmpCcLastChange OBJECT-TYPE 1130 SYNTAX TimeTicks 1131 MAX-ACCESS read-only 1132 STATUS current 1133 DESCRIPTION 1134 "The value of sysUpTime at the time the control channel entered 1135 its current operational state. If the current state was 1136 entered prior to the last re-initialization of the local 1137 network management subsystem, then this object contains a 1138 zero value." 1139 ::= { lmpControlChannelEntry 18 } 1141 lmpCcAdminStatus OBJECT-TYPE 1142 SYNTAX INTEGER { up(1), down(2) } 1143 MAX-ACCESS read-create 1144 STATUS current 1145 DESCRIPTION 1146 "The desired operational status of this control channel." 1147 ::= { lmpControlChannelEntry 19 } 1149 lmpCcOperStatus OBJECT-TYPE 1150 SYNTAX INTEGER { 1151 up(1), 1152 down(2), 1153 configSnd(3), 1154 configRcv(4), 1155 active(5), 1156 goingDown(6) 1157 } 1158 MAX-ACCESS read-only 1159 STATUS current 1160 DESCRIPTION 1161 "The actual operational status of this control channel 1162 interface." 1163 ::= { lmpControlChannelEntry 20 } 1165 lmpCcRowStatus OBJECT-TYPE 1166 SYNTAX RowStatus 1167 MAX-ACCESS read-create 1168 STATUS current 1169 DESCRIPTION 1170 "This variable is used to create, modify, and/or 1171 delete a row in this table. All read-create objects 1172 can be changed when lmpCcRowStatus is active." 1173 ::= { lmpControlChannelEntry 21 } 1175 lmpCcStorageType OBJECT-TYPE 1176 SYNTAX StorageType 1177 MAX-ACCESS read-create 1178 STATUS current 1179 DESCRIPTION 1180 "The storage type for this conceptual row in the 1181 lmpControlChannelTable. Conceptual rows having the value 1182 'permanent' need not allow write-access to any 1183 columnar object in the row." 1184 ::= { lmpControlChannelEntry 22 } 1186 -- End of lmpControlChannelTable 1188 -- LMP Control Channel Performance Table 1190 lmpControlChannelPerfTable OBJECT-TYPE 1191 SYNTAX SEQUENCE OF LmpControlChannelPerfEntry 1192 MAX-ACCESS not-accessible 1193 STATUS current 1194 DESCRIPTION 1195 "This table specifies LMP control channel performance counters." 1196 ::= { lmpObjects 11 } 1198 lmpControlChannelPerfEntry OBJECT-TYPE 1199 SYNTAX LmpControlChannelPerfEntry 1200 MAX-ACCESS not-accessible 1201 STATUS current 1202 DESCRIPTION 1203 "An entry in this table is created by a LMP-enabled device for 1204 every control channel." 1205 AUGMENTS { lmpControlChannelEntry } 1206 ::= { lmpControlChannelPerfTable 1 } 1208 LmpControlChannelPerfEntry ::= SEQUENCE { 1209 lmpCcInOctets Counter32, 1210 lmpCcInDiscards Counter32, 1211 lmpCcInErrors Counter32, 1212 lmpCcOutOctets Counter32, 1213 lmpCcOutDiscards Counter32, 1214 lmpCcOutErrors Counter32, 1215 lmpCcConfigReceived Counter32, 1216 lmpCcConfigSent Counter32, 1217 lmpCcConfigRetransmit Counter32, 1218 lmpCcConfigAckReceived Counter32, 1219 lmpCcConfigAckSent Counter32, 1220 lmpCcConfigNackReceived Counter32, 1221 lmpCcConfigNackSent Counter32, 1222 lmpCcHelloReceived Counter32, 1223 lmpCcHelloSent Counter32, 1224 lmpCcBeginVerifyReceived Counter32, 1225 lmpCcBeginVerifySent Counter32, 1226 lmpCcBeginVerifyRetransmit Counter32, 1227 lmpCcBeginVerifyAckReceived Counter32, 1228 lmpCcBeginVerifyAckSent Counter32, 1229 lmpCcBeginVerifyNackReceived Counter32, 1230 lmpCcBeginVerifyNackSent Counter32, 1231 lmpCcEndVerifyReceived Counter32, 1232 lmpCcEndVerifySent Counter32, 1233 lmpCcEndVerifyRetransmit Counter32, 1234 lmpCcEndVerifyAckReceived Counter32, 1235 lmpCcEndVerifyAckSent Counter32, 1236 lmpCcTestStatusSuccessReceived Counter32, 1237 lmpCcTestStatusSuccessSent Counter32, 1238 lmpCcTestStatusSuccessRetransmit Counter32, 1239 lmpCcTestStatusFailureReceived Counter32, 1240 lmpCcTestStatusFailureSent Counter32, 1241 lmpCcTestStatusFailureRetransmit Counter32, 1242 lmpCcTestStatusAckReceived Counter32, 1243 lmpCcTestStatusAckSent Counter32, 1244 lmpCcLinkSummaryReceived Counter32, 1245 lmpCcLinkSummarySent Counter32, 1246 lmpCcLinkSummaryRetransmit Counter32, 1247 lmpCcLinkSummaryAckReceived Counter32, 1248 lmpCcLinkSummaryAckSent Counter32, 1249 lmpCcLinkSummaryNackReceived Counter32, 1250 lmpCcLinkSummaryNackSent Counter32, 1251 lmpCcChannelStatusReceived Counter32, 1252 lmpCcChannelStatusSent Counter32, 1253 lmpCcChannelStatusRetransmit Counter32, 1254 lmpCcChannelStatusAckReceived Counter32, 1255 lmpCcChannelStatusAckSent Counter32, 1256 lmpCcChannelStatusRequestReceived Counter32, 1257 lmpCcChannelStatusRequestSent Counter32, 1258 lmpCcChannelStatusRequestRetransmit Counter32, 1259 lmpCcChannelStatusResponseSent Counter32, 1260 lmpCcChannelStatusResponseReceived Counter32, 1261 lmpCcCounterDiscontinuityTime TimeStamp 1262 } 1264 lmpCcInOctets OBJECT-TYPE 1265 SYNTAX Counter32 1266 MAX-ACCESS read-only 1267 STATUS current 1268 DESCRIPTION 1269 "The total number of LMP message octets received on the 1270 control channel." 1271 ::= { lmpControlChannelPerfEntry 1 } 1273 lmpCcInDiscards OBJECT-TYPE 1274 SYNTAX Counter32 1275 MAX-ACCESS read-only 1276 STATUS current 1277 DESCRIPTION 1278 "The number of inbound packets which were chosen to be 1279 discarded even though no errors had been detected. One 1280 possible reason for discarding such a packet could be to 1281 free up buffer space." 1282 ::= { lmpControlChannelPerfEntry 2 } 1284 lmpCcInErrors OBJECT-TYPE 1285 SYNTAX Counter32 1286 MAX-ACCESS read-only 1287 STATUS current 1288 DESCRIPTION 1289 "The number of inbound packets that contained errors 1290 preventing them from being processed by LMP." 1291 ::= { lmpControlChannelPerfEntry 3 } 1293 lmpCcOutOctets OBJECT-TYPE 1294 SYNTAX Counter32 1295 MAX-ACCESS read-only 1296 STATUS current 1297 DESCRIPTION 1298 "The total number of LMP message octets transmitted out of 1299 the control channel." 1300 ::= { lmpControlChannelPerfEntry 4 } 1302 lmpCcOutDiscards OBJECT-TYPE 1303 SYNTAX Counter32 1304 MAX-ACCESS read-only 1305 STATUS current 1306 DESCRIPTION 1307 "The number of outbound packets which were chosen to be 1308 discarded even though no errors had been detected to prevent 1309 their being transmitted. One possible reason for discarding 1310 such a packet could be to free up buffer space." 1311 ::= { lmpControlChannelPerfEntry 5 } 1313 lmpCcOutErrors OBJECT-TYPE 1314 SYNTAX Counter32 1315 MAX-ACCESS read-only 1316 STATUS current 1317 DESCRIPTION 1318 "The number of outbound packets that could not be 1319 transmitted because of errors." 1320 ::= { lmpControlChannelPerfEntry 6 } 1322 lmpCcConfigReceived OBJECT-TYPE 1323 SYNTAX Counter32 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "This object counts the number of Config messages that have 1328 been received on this control channel." 1329 ::= { lmpControlChannelPerfEntry 7 } 1331 lmpCcConfigSent OBJECT-TYPE 1332 SYNTAX Counter32 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "This object counts the number of Config messages that have 1337 been sent on this control channel." 1338 ::= { lmpControlChannelPerfEntry 8 } 1340 lmpCcConfigRetransmit OBJECT-TYPE 1341 SYNTAX Counter32 1342 MAX-ACCESS read-only 1343 STATUS current 1344 DESCRIPTION 1345 "This object counts the number of Config messages that 1346 have been retransmitted over this control channel." 1347 ::= { lmpControlChannelPerfEntry 9 } 1349 lmpCcConfigAckReceived OBJECT-TYPE 1350 SYNTAX Counter32 1351 MAX-ACCESS read-only 1352 STATUS current 1353 DESCRIPTION 1354 "This object counts the number of ConfigAck messages that have 1355 been received on this control channel." 1356 ::= { lmpControlChannelPerfEntry 10 } 1358 lmpCcConfigAckSent OBJECT-TYPE 1359 SYNTAX Counter32 1360 MAX-ACCESS read-only 1361 STATUS current 1362 DESCRIPTION 1363 "This object counts the number of ConfigAck messages that have 1364 been sent on this control channel." 1365 ::= { lmpControlChannelPerfEntry 11 } 1367 lmpCcConfigNackReceived OBJECT-TYPE 1368 SYNTAX Counter32 1369 MAX-ACCESS read-only 1370 STATUS current 1371 DESCRIPTION 1372 "This object counts the number of ConfigNack messages that have 1373 been received on this control channel." 1374 ::= { lmpControlChannelPerfEntry 12 } 1376 lmpCcConfigNackSent OBJECT-TYPE 1377 SYNTAX Counter32 1378 MAX-ACCESS read-only 1379 STATUS current 1380 DESCRIPTION 1381 "This object counts the number of ConfigNack messages that have 1382 been sent on this control channel." 1383 ::= { lmpControlChannelPerfEntry 13 } 1385 lmpCcHelloReceived OBJECT-TYPE 1386 SYNTAX Counter32 1387 MAX-ACCESS read-only 1388 STATUS current 1389 DESCRIPTION 1390 "This object counts the number of Hello messages that have 1391 been received on this control channel." 1392 ::= { lmpControlChannelPerfEntry 14 } 1394 lmpCcHelloSent OBJECT-TYPE 1395 SYNTAX Counter32 1396 MAX-ACCESS read-only 1397 STATUS current 1398 DESCRIPTION 1399 "This object counts the number of Hello messages that have 1400 been sent on this control channel." 1401 ::= { lmpControlChannelPerfEntry 15 } 1403 lmpCcBeginVerifyReceived OBJECT-TYPE 1404 SYNTAX Counter32 1405 MAX-ACCESS read-only 1406 STATUS current 1407 DESCRIPTION 1408 "This object counts the number of BeginVerify messages that have 1409 been received on this control channel." 1410 ::= { lmpControlChannelPerfEntry 16 } 1412 lmpCcBeginVerifySent OBJECT-TYPE 1413 SYNTAX Counter32 1414 MAX-ACCESS read-only 1415 STATUS current 1416 DESCRIPTION 1417 "This object counts the number of BeginVerify messages that have 1418 been sent on this control channel." 1419 ::= { lmpControlChannelPerfEntry 17 } 1421 lmpCcBeginVerifyRetransmit OBJECT-TYPE 1422 SYNTAX Counter32 1423 MAX-ACCESS read-only 1424 STATUS current 1425 DESCRIPTION 1426 "This object counts the number of BeginVerify messages that 1427 have been retransmitted over this control channel." 1428 ::= { lmpControlChannelPerfEntry 18 } 1430 lmpCcBeginVerifyAckReceived OBJECT-TYPE 1431 SYNTAX Counter32 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "This object counts the number of BeginVerifyAck messages that have 1436 been received on this control channel." 1437 ::= { lmpControlChannelPerfEntry 19 } 1439 lmpCcBeginVerifyAckSent OBJECT-TYPE 1440 SYNTAX Counter32 1441 MAX-ACCESS read-only 1442 STATUS current 1443 DESCRIPTION 1444 "This object counts the number of BeginVerifyAck messages that have 1445 been sent on this control channel." 1446 ::= { lmpControlChannelPerfEntry 20 } 1448 lmpCcBeginVerifyNackReceived OBJECT-TYPE 1449 SYNTAX Counter32 1450 MAX-ACCESS read-only 1451 STATUS current 1452 DESCRIPTION 1453 "This object counts the number of BeginVerifyNack messages that have 1454 been received on this control channel." 1455 ::= { lmpControlChannelPerfEntry 21 } 1457 lmpCcBeginVerifyNackSent OBJECT-TYPE 1458 SYNTAX Counter32 1459 MAX-ACCESS read-only 1460 STATUS current 1461 DESCRIPTION 1462 "This object counts the number of BeginVerifyNack messages that have 1463 been sent on this control channel." 1464 ::= { lmpControlChannelPerfEntry 22 } 1466 lmpCcEndVerifyReceived OBJECT-TYPE 1467 SYNTAX Counter32 1468 MAX-ACCESS read-only 1469 STATUS current 1470 DESCRIPTION 1471 "This object counts the number of EndVerify messages that have 1472 been received on this control channel." 1473 ::= { lmpControlChannelPerfEntry 23 } 1475 lmpCcEndVerifySent OBJECT-TYPE 1476 SYNTAX Counter32 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "This object counts the number of EndVerify messages that have 1481 been sent on this control channel." 1482 ::= { lmpControlChannelPerfEntry 24 } 1484 lmpCcEndVerifyRetransmit OBJECT-TYPE 1485 SYNTAX Counter32 1486 MAX-ACCESS read-only 1487 STATUS current 1488 DESCRIPTION 1489 "This object counts the number of EndVerify messages that 1490 have been retransmitted over this control channel." 1491 ::= { lmpControlChannelPerfEntry 25 } 1493 lmpCcEndVerifyAckReceived OBJECT-TYPE 1494 SYNTAX Counter32 1495 MAX-ACCESS read-only 1496 STATUS current 1497 DESCRIPTION 1498 "This object counts the number of EndVerifyAck messages that have 1499 been received on this control channel." 1500 ::= { lmpControlChannelPerfEntry 26 } 1502 lmpCcEndVerifyAckSent OBJECT-TYPE 1503 SYNTAX Counter32 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "This object counts the number of EndVerifyAck messages that have 1508 been sent on this control channel." 1509 ::= { lmpControlChannelPerfEntry 27 } 1511 lmpCcTestStatusSuccessReceived OBJECT-TYPE 1512 SYNTAX Counter32 1513 MAX-ACCESS read-only 1514 STATUS current 1515 DESCRIPTION 1516 "This object counts the number of TestStatusSuccess messages that have 1517 been received on this control channel." 1518 ::= { lmpControlChannelPerfEntry 28 } 1520 lmpCcTestStatusSuccessSent OBJECT-TYPE 1521 SYNTAX Counter32 1522 MAX-ACCESS read-only 1523 STATUS current 1524 DESCRIPTION 1525 "This object counts the number of TestStatusSuccess messages that have 1526 been sent on this control channel." 1527 ::= { lmpControlChannelPerfEntry 29 } 1529 lmpCcTestStatusSuccessRetransmit OBJECT-TYPE 1530 SYNTAX Counter32 1531 MAX-ACCESS read-only 1532 STATUS current 1533 DESCRIPTION 1534 "This object counts the number of TestStatusSuccess messages that 1535 have been retransmitted over this control channel." 1536 ::= { lmpControlChannelPerfEntry 30 } 1538 lmpCcTestStatusFailureReceived OBJECT-TYPE 1539 SYNTAX Counter32 1540 MAX-ACCESS read-only 1541 STATUS current 1542 DESCRIPTION 1543 "This object counts the number of TestStatusFailure messages that have 1544 been received on this control channel." 1545 ::= { lmpControlChannelPerfEntry 31 } 1547 lmpCcTestStatusFailureSent OBJECT-TYPE 1548 SYNTAX Counter32 1549 MAX-ACCESS read-only 1550 STATUS current 1551 DESCRIPTION 1552 "This object counts the number of TestStatusFailure messages that have 1553 been sent on this control channel." 1554 ::= { lmpControlChannelPerfEntry 32 } 1556 lmpCcTestStatusFailureRetransmit OBJECT-TYPE 1557 SYNTAX Counter32 1558 MAX-ACCESS read-only 1559 STATUS current 1560 DESCRIPTION 1561 "This object counts the number of TestStatusFailure messages that 1562 have been retransmitted over this control channel." 1563 ::= { lmpControlChannelPerfEntry 33 } 1565 lmpCcTestStatusAckReceived OBJECT-TYPE 1566 SYNTAX Counter32 1567 MAX-ACCESS read-only 1568 STATUS current 1569 DESCRIPTION 1570 "This object counts the number of TestStatusAck messages that have 1571 been received on this control channel." 1572 ::= { lmpControlChannelPerfEntry 34 } 1574 lmpCcTestStatusAckSent OBJECT-TYPE 1575 SYNTAX Counter32 1576 MAX-ACCESS read-only 1577 STATUS current 1578 DESCRIPTION 1579 "This object counts the number of TestStatusAck messages that have 1580 been sent on this control channel." 1581 ::= { lmpControlChannelPerfEntry 35 } 1583 lmpCcLinkSummaryReceived OBJECT-TYPE 1584 SYNTAX Counter32 1585 MAX-ACCESS read-only 1586 STATUS current 1587 DESCRIPTION 1588 "This object counts the number of LinkSummary messages that have 1589 been received on this control channel." 1590 ::= { lmpControlChannelPerfEntry 36 } 1592 lmpCcLinkSummarySent OBJECT-TYPE 1593 SYNTAX Counter32 1594 MAX-ACCESS read-only 1595 STATUS current 1596 DESCRIPTION 1597 "This object counts the number of LinkSummary messages that have 1598 been sent on this control channel." 1599 ::= { lmpControlChannelPerfEntry 37 } 1601 lmpCcLinkSummaryRetransmit OBJECT-TYPE 1602 SYNTAX Counter32 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "This object counts the number of LinkSummary messages that 1607 have been retransmitted over this control channel." 1608 ::= { lmpControlChannelPerfEntry 38 } 1610 lmpCcLinkSummaryAckReceived OBJECT-TYPE 1611 SYNTAX Counter32 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "This object counts the number of LinkSummaryAck messages that have 1616 been received on this control channel." 1617 ::= { lmpControlChannelPerfEntry 39 } 1619 lmpCcLinkSummaryAckSent OBJECT-TYPE 1620 SYNTAX Counter32 1621 MAX-ACCESS read-only 1622 STATUS current 1623 DESCRIPTION 1624 "This object counts the number of LinkSummaryAck messages that have 1625 been sent on this control channel." 1626 ::= { lmpControlChannelPerfEntry 40 } 1628 lmpCcLinkSummaryNackReceived OBJECT-TYPE 1629 SYNTAX Counter32 1630 MAX-ACCESS read-only 1631 STATUS current 1632 DESCRIPTION 1633 "This object counts the number of LinkSummaryNack messages that have 1634 been received on this control channel." 1635 ::= { lmpControlChannelPerfEntry 41 } 1637 lmpCcLinkSummaryNackSent OBJECT-TYPE 1638 SYNTAX Counter32 1639 MAX-ACCESS read-only 1640 STATUS current 1641 DESCRIPTION 1642 "This object counts the number of LinkSummaryNack messages that have 1643 been sent on this control channel." 1644 ::= { lmpControlChannelPerfEntry 42 } 1646 lmpCcChannelStatusReceived OBJECT-TYPE 1647 SYNTAX Counter32 1648 MAX-ACCESS read-only 1649 STATUS current 1650 DESCRIPTION 1651 "This object counts the number of ChannelStatus messages that have 1652 been received on this control channel." 1653 ::= { lmpControlChannelPerfEntry 43 } 1655 lmpCcChannelStatusSent OBJECT-TYPE 1656 SYNTAX Counter32 1657 MAX-ACCESS read-only 1658 STATUS current 1659 DESCRIPTION 1660 "This object counts the number of ChannelStatus messages that have 1661 been sent on this control channel." 1662 ::= { lmpControlChannelPerfEntry 44 } 1664 lmpCcChannelStatusRetransmit OBJECT-TYPE 1665 SYNTAX Counter32 1666 MAX-ACCESS read-only 1667 STATUS current 1668 DESCRIPTION 1669 "This object counts the number of ChannelStatus messages that have 1670 been retransmitted on this control channel." 1671 ::= { lmpControlChannelPerfEntry 45 } 1673 lmpCcChannelStatusAckReceived OBJECT-TYPE 1674 SYNTAX Counter32 1675 MAX-ACCESS read-only 1676 STATUS current 1677 DESCRIPTION 1678 "This object counts the number of ChannelStatusAck messages that have 1679 been received on this control channel." 1680 ::= { lmpControlChannelPerfEntry 46 } 1682 lmpCcChannelStatusAckSent OBJECT-TYPE 1683 SYNTAX Counter32 1684 MAX-ACCESS read-only 1685 STATUS current 1686 DESCRIPTION 1687 "This object counts the number of ChannelStatus messages that have 1688 been sent on this control channel." 1689 ::= { lmpControlChannelPerfEntry 47 } 1691 lmpCcChannelStatusRequestReceived OBJECT-TYPE 1692 SYNTAX Counter32 1693 MAX-ACCESS read-only 1694 STATUS current 1695 DESCRIPTION 1696 "This object counts the number of ChannelStatusRequest messages that 1697 have been received on this control channel." 1698 ::= { lmpControlChannelPerfEntry 48 } 1700 lmpCcChannelStatusRequestSent OBJECT-TYPE 1701 SYNTAX Counter32 1702 MAX-ACCESS read-only 1703 STATUS current 1704 DESCRIPTION 1705 "This object counts the number of ChannelStatusRequest messages that 1706 have been sent on this control channel." 1707 ::= { lmpControlChannelPerfEntry 49 } 1709 lmpCcChannelStatusRequestRetransmit OBJECT-TYPE 1710 SYNTAX Counter32 1711 MAX-ACCESS read-only 1712 STATUS current 1713 DESCRIPTION 1714 "This object counts the number of ChannelStatusRequest messages that 1715 have been retransmitted on this control channel." 1716 ::= { lmpControlChannelPerfEntry 50 } 1718 lmpCcChannelStatusResponseReceived OBJECT-TYPE 1719 SYNTAX Counter32 1720 MAX-ACCESS read-only 1721 STATUS current 1722 DESCRIPTION 1723 "This object counts the number of ChannelStatusResponse messages that 1724 have been received on this control channel." 1725 ::= { lmpControlChannelPerfEntry 51 } 1727 lmpCcChannelStatusResponseSent OBJECT-TYPE 1728 SYNTAX Counter32 1729 MAX-ACCESS read-only 1730 STATUS current 1731 DESCRIPTION 1732 "This object counts the number of ChannelStatusResponse messages that 1733 have been sent on this control channel." 1734 ::= { lmpControlChannelPerfEntry 52 } 1736 lmpCcCounterDiscontinuityTime OBJECT-TYPE 1737 SYNTAX TimeStamp 1738 MAX-ACCESS read-only 1739 STATUS current 1740 DESCRIPTION 1741 "The value of sysUpTime on the most recent occasion at which 1742 any one or more of this control channel's counters suffered a 1743 discontinuity. The relevant counters are the specific 1744 instances associated with this control channel of any Counter32 or 1745 Counter64 object contained in the lmpControlChannelPerfTable. If 1746 no such discontinuities have occurred since the last re- 1747 initialization of the local management subsystem, then this 1748 object contains a zero value." 1749 ::= { lmpControlChannelPerfEntry 53 } 1751 -- End of lmpControlChannelPerfTable 1753 -- LMP TE Link Table 1755 lmpTeLinkTable OBJECT-TYPE 1756 SYNTAX SEQUENCE OF LmpTeLinkEntry 1757 MAX-ACCESS not-accessible 1758 STATUS current 1759 DESCRIPTION 1760 "This table contains a collection of TE link." 1761 ::= { lmpObjects 12 } 1763 lmpTeLinkEntry OBJECT-TYPE 1764 SYNTAX LmpTeLinkEntry 1765 MAX-ACCESS not-accessible 1766 STATUS current 1767 DESCRIPTION 1768 "An entry in this table exists for each ifEntry with an 1769 ifType of teLink(TBD), i.e. for every TE link. An ifEntry 1770 with an ifIndex must exist before the corresponding 1771 teLinkEntry is created. If a TE link entry in the ifTable is 1772 destroyed, then so is the corresponding entry in the 1773 teLinkTable. The administrative status value is controlled 1774 from the ifEntry. Setting the administrative status to 1775 testing prompts LMP to start link verification on the TE link. 1776 Information about the TE link that is not LMP specific is also 1777 contained in teLinkTable [BUNDLE-MIB]." 1778 INDEX { ifIndex } 1779 ::= { lmpTeLinkTable 1 } 1781 LmpTeLinkEntry ::= SEQUENCE { 1782 lmpTeLinkNbrNodeId NodeID, 1783 lmpTeLinkVerification TruthValue, 1784 lmpTeLinkFaultManagement TruthValue, 1785 lmpTeLinkDwdm TruthValue, 1786 lmpTeLinkOperStatus INTEGER, 1787 lmpTeLinkRowStatus RowStatus, 1788 lmpTeLinkStorageType StorageType 1789 } 1791 lmpTeLinkNbrNodeId OBJECT-TYPE 1792 SYNTAX NodeID 1793 MAX-ACCESS read-create 1794 STATUS current 1795 DESCRIPTION 1796 "This is the Node ID of the TE link remote node. This value 1797 may be learned during control channel parameter negotiation 1798 phase (in the Config message)." 1799 ::= { lmpTeLinkEntry 1 } 1801 lmpTeLinkVerification OBJECT-TYPE 1802 SYNTAX TruthValue 1803 MAX-ACCESS read-create 1804 STATUS current 1805 DESCRIPTION 1806 "This object indicates if the extended LMP link verification 1807 procedure is enabled for this TE link." 1808 REFERENCE 1809 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 1810 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1811 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1812 B. Rajagopalan, November 2001." 1813 ::= { lmpTeLinkEntry 2 } 1815 lmpTeLinkFaultManagement OBJECT-TYPE 1816 SYNTAX TruthValue 1817 MAX-ACCESS read-create 1818 STATUS current 1819 DESCRIPTION 1820 "This object indicates if the extended LMP fault management 1821 procedure is enabled on this TE link." 1822 REFERENCE 1823 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 1824 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1825 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1826 B. Rajagopalan, November 2001." 1827 ::= { lmpTeLinkEntry 3 } 1829 lmpTeLinkDwdm OBJECT-TYPE 1830 SYNTAX TruthValue 1831 MAX-ACCESS read-create 1832 STATUS current 1833 DESCRIPTION 1834 "This object indicates if the extended LMP DWDM procedure 1835 is enabled on this TE link." 1836 REFERENCE 1837 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 1838 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1839 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1840 B. Rajagopalan, November 2001." 1841 ::= { lmpTeLinkEntry 4 } 1843 lmpTeLinkOperStatus OBJECT-TYPE 1844 SYNTAX INTEGER { up(1), down(2), testing(3), init(4), degraded(5) } 1845 MAX-ACCESS read-only 1846 STATUS current 1847 DESCRIPTION 1848 "The actual operational status of this TE link. The status 1849 is set to testing when the TE link is performing link 1850 verification. A degraded state indicates that there are 1851 no active control channel between the pair of nodes that 1852 form the endpoints of the TE link, but yet at least one 1853 data-bearing links on the TE link is allocated." 1854 ::= { lmpTeLinkEntry 5 } 1856 lmpTeLinkRowStatus OBJECT-TYPE 1857 SYNTAX RowStatus 1858 MAX-ACCESS read-create 1859 STATUS current 1860 DESCRIPTION 1861 "This variable is used to create, modify, and/or 1862 delete a row in this table. All read-create objects 1863 can be changed when lmpTeLinkRowStatus is active." 1864 ::= { lmpTeLinkEntry 6 } 1866 lmpTeLinkStorageType OBJECT-TYPE 1867 SYNTAX StorageType 1868 MAX-ACCESS read-create 1869 STATUS current 1870 DESCRIPTION 1871 "The storage type for this conceptual row in the 1872 lmpTeLinkTable. Conceptual rows having the value 1873 'permanent' need not allow write-access to any 1874 columnar object in the row." 1875 ::= { lmpTeLinkEntry 7 } 1877 -- End of lmpTeLinkTable 1879 lmpLinkVerificationInterval OBJECT-TYPE 1880 SYNTAX Unsigned32 1881 MAX-ACCESS read-write 1882 STATUS current 1883 DESCRIPTION 1884 "This object indicates how often the link verification procedure 1885 is executed. The interval is in milliseconds." 1886 ::= { lmpObjects 13 } 1888 -- LMP Link Verification Table 1890 lmpLinkVerificationTable OBJECT-TYPE 1891 SYNTAX SEQUENCE OF LmpLinkVerificationEntry 1892 MAX-ACCESS not-accessible 1893 STATUS current 1894 DESCRIPTION 1895 "This table specifies TE link information associated with the 1896 LMP verification procedure." 1897 ::= { lmpObjects 14 } 1899 lmpLinkVerificationEntry OBJECT-TYPE 1900 SYNTAX LmpLinkVerificationEntry 1901 MAX-ACCESS not-accessible 1902 STATUS current 1903 DESCRIPTION 1904 "An entry in this table is created by a LMP-enabled device for 1905 every TE link that supports the LMP verification 1906 procedure." 1907 AUGMENTS { lmpTeLinkEntry } 1908 ::= { lmpLinkVerificationTable 1 } 1910 LmpLinkVerificationEntry ::= SEQUENCE { 1911 lmpVerifyInterval LmpInterval, 1912 lmpVerifyDeadInterval LmpInterval, 1913 lmpVerifyTransportMechanism BITS, 1914 lmpVerifyAllLinks INTEGER, 1915 lmpTeLinkBitRate Unsigned32, 1916 lmpTeLinkWavelength Unsigned32 1917 } 1919 lmpVerifyInterval OBJECT-TYPE 1920 SYNTAX LmpInterval 1921 MAX-ACCESS read-create 1922 STATUS current 1923 DESCRIPTION 1924 "This object specifies the VerifyInterval parameter used 1925 in the LMP link verification process. It indicates the interval 1926 at which the Test messages are sent." 1927 REFERENCE 1928 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 1929 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1930 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1931 B. Rajagopalan, November 2001." 1932 ::= { lmpLinkVerificationEntry 1 } 1934 lmpVerifyDeadInterval OBJECT-TYPE 1935 SYNTAX LmpInterval 1936 MAX-ACCESS read-create 1937 STATUS current 1938 DESCRIPTION 1939 "This object specifies the VerifyDeadInterval parameter used 1940 in the verification of the physical connectivity of data-bearing 1941 links. It specifies the observation period used to detect a Test 1942 message at the remote node." 1943 REFERENCE 1944 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 1945 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1946 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1947 B. Rajagopalan, November 2001." 1948 ::= { lmpLinkVerificationEntry 2 } 1950 lmpVerifyTransportMechanism OBJECT-TYPE 1951 SYNTAX BITS { 1952 -- SONET/SDH encoding type: 1953 j016OverheadBytes(1), 1954 j064OverheadBytes(2), 1955 dccSectionOverheadBytes(3), 1956 dccLineOverheadBytes(4), 1957 pos(5) 1958 -- GigE encoding type: TBD 1959 -- 10GigE encoding type: TBD 1960 } 1961 MAX-ACCESS read-create 1962 STATUS current 1963 DESCRIPTION 1964 "This defines the transport mechanism for the Test messages. The 1965 scope of this bit mask is restricted to each link encoding 1966 type. The local node will set the bits corresponding to the 1967 various mechanisms it can support for transmitting LMP Test 1968 messages. The receiver chooses the appropriate mechanism in the 1969 BeginVerifyAck message." 1970 REFERENCE 1971 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 1972 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1973 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1974 B. Rajagopalan, November 2001." 1975 ::= { lmpLinkVerificationEntry 3 } 1977 lmpVerifyAllLinks OBJECT-TYPE 1978 SYNTAX INTEGER { verifyAllLinks(1), verifyNewLinks(2) } 1979 MAX-ACCESS read-create 1980 STATUS current 1981 DESCRIPTION 1982 "This object indicates whether the verification process checks 1983 all entities or only the new entities that have been added to 1984 this TE link." 1985 ::= { lmpLinkVerificationEntry 4 } 1987 lmpTeLinkBitRate OBJECT-TYPE 1988 SYNTAX Unsigned32 1989 MAX-ACCESS read-create 1990 STATUS current 1991 DESCRIPTION 1992 "This is the bit rate at which the Test messages will be 1993 transmitted and is expressed in bytes per second." 1994 REFERENCE 1995 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 1996 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1997 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1998 B. Rajagopalan, November 2001." 1999 ::= { lmpLinkVerificationEntry 5 } 2001 lmpTeLinkWavelength OBJECT-TYPE 2002 SYNTAX Unsigned32 2003 MAX-ACCESS read-create 2004 STATUS current 2005 DESCRIPTION 2006 "This value corresponds to the wavelength at 2007 which the Test messages will be transmitted over and is 2008 measured in nanometers (nm). If each data-bearing link 2009 corresponds to a separate wavelength, than this value should be 2010 set to 0." 2011 REFERENCE 2012 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 2013 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 2014 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 2015 B. Rajagopalan, November 2001." 2016 ::= { lmpLinkVerificationEntry 6 } 2018 -- End of lmpLinkVerificationTable 2020 -- LMP Data Bearing Link Table 2022 lmpDataBearingLinkTable OBJECT-TYPE 2023 SYNTAX SEQUENCE OF LmpDataBearingLinkEntry 2024 MAX-ACCESS not-accessible 2025 STATUS current 2026 DESCRIPTION 2027 "This table specifies the data-bearing links managed by the 2028 LMP." 2029 ::= { lmpObjects 15 } 2031 lmpDataBearingLinkEntry OBJECT-TYPE 2032 SYNTAX LmpDataBearingLinkEntry 2033 MAX-ACCESS not-accessible 2034 STATUS current 2035 DESCRIPTION 2036 "An entry in this table exists for each ifEntry that represents 2037 a data-bearing link. An ifEntry with an ifIndex must exist 2038 before the corresponding lmpDataBearingLinkEntry is created. 2039 If an entry representing the data-bearing link is destroyed in 2040 the ifTable, then so is the corresponding entry in the 2041 lmpDataBearingLinkTable. The administrative status value is 2042 controlled from the ifEntry. The index to this table also 2043 used to get information in the dataBearingChannelTable 2044 [BUNDLE-MIB]." 2045 INDEX { ifIndex } 2046 ::= { lmpDataBearingLinkTable 1 } 2048 LmpDataBearingLinkEntry ::= SEQUENCE { 2049 lmpDataBearingLinkType INTEGER, 2050 lmpDataBearingLinkNumberingType INTEGER, 2051 lmpDataBearingLinkRemoteIfId InterfaceIndexOrZero, 2052 lmpDataBearingLinkRemoteIpAddress InetAddress, 2053 lmpDataBearingLinkEncodingType INTEGER, 2054 lmpDataBearingLinkActiveOperStatus INTEGER, 2055 lmpDataBearingLinkPassiveOperStatus INTEGER, 2056 lmpDataBearingLinkRowStatus RowStatus, 2057 lmpDataBearingLinkStorageType StorageType 2058 } 2060 lmpDataBearingLinkType OBJECT-TYPE 2061 SYNTAX INTEGER { 2062 port(1), 2063 componentLink(2) 2064 } 2065 MAX-ACCESS read-only 2066 STATUS current 2067 DESCRIPTION 2068 "This attribute specifies whether this data-bearing link is 2069 a port or a component link. Component link are multiplex 2070 capable whereas, ports are not multiplex capable." 2071 REFERENCE 2072 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 2073 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 2074 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 2075 B. Rajagopalan, November 2001." 2076 ::= { lmpDataBearingLinkEntry 1 } 2078 lmpDataBearingLinkNumberingType OBJECT-TYPE 2079 SYNTAX INTEGER { 2080 unnumbered(1), 2081 ipV4(2), 2082 ipV6(3) 2083 } 2084 MAX-ACCESS read-create 2085 STATUS current 2086 DESCRIPTION 2087 "This attribute specifies the data-bearing link numbering 2088 type." 2089 ::= { lmpDataBearingLinkEntry 2 } 2091 lmpDataBearingLinkRemoteIfId OBJECT-TYPE 2092 SYNTAX InterfaceIndexOrZero 2093 MAX-ACCESS read-create 2094 STATUS current 2095 DESCRIPTION 2096 "Interface identifier of the remote end point. This 2097 information is either configured manually or is 2098 communicated by the remote node during the link verification 2099 procedure." 2100 ::= { lmpDataBearingLinkEntry 3 } 2102 lmpDataBearingLinkRemoteIpAddress OBJECT-TYPE 2103 SYNTAX InetAddress 2104 MAX-ACCESS read-create 2105 STATUS current 2106 DESCRIPTION 2107 "IP address of the remote end point. This 2108 information is either configured manually or is 2109 communicated by the remote node during the link verification 2110 procedure." 2111 ::= { lmpDataBearingLinkEntry 4 } 2113 lmpDataBearingLinkEncodingType OBJECT-TYPE 2114 SYNTAX INTEGER { 2115 packet(1), 2116 ethernetV2Dix(2), 2117 ansiPdh(3), 2118 etsiPdh(4), 2119 sdhItuG707(5), 2120 sonetAnsiT1105(6), 2121 digitalWrapper(7), 2122 lambda(8), 2123 fiber(9), 2124 ethernet8023(10), 2125 fiberChannel(11) 2126 } 2127 MAX-ACCESS read-create 2128 STATUS current 2129 DESCRIPTION 2130 "The encoding type of the data-bearing link." 2131 REFERENCE 2132 "draft-ietf-mpls-generalized-signaling-07.txt - Generalized 2133 MPLS Signaling Functional Description, P. Ashwood-Smith, 2134 A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan, 2135 E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha, 2136 V. Sharma, G. Swallow, Z. Tang, November 2001." 2137 ::= { lmpDataBearingLinkEntry 5 } 2139 lmpDataBearingLinkActiveOperStatus OBJECT-TYPE 2140 SYNTAX INTEGER { 2141 upAlloc(1), 2142 upFree(2), 2143 down(3), 2144 testing(4) } 2145 MAX-ACCESS read-only 2146 STATUS current 2147 DESCRIPTION 2148 "The actual operational status of this data-bearing link 2149 (active FSM)." 2150 REFERENCE 2151 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 2152 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 2153 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 2154 B. Rajagopalan, November 2001." 2155 ::= { lmpDataBearingLinkEntry 6 } 2157 lmpDataBearingLinkPassiveOperStatus OBJECT-TYPE 2158 SYNTAX INTEGER { 2159 upAlloc(1), 2160 upFree(2), 2161 down(3), 2162 psvTst(4) } 2163 MAX-ACCESS read-only 2164 STATUS current 2165 DESCRIPTION 2166 "The actual operational status of this data-bearing link 2167 (passive FSM)." 2168 REFERENCE 2169 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 2170 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 2171 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 2172 B. Rajagopalan, November 2001." 2173 ::= { lmpDataBearingLinkEntry 7 } 2175 lmpDataBearingLinkRowStatus OBJECT-TYPE 2176 SYNTAX RowStatus 2177 MAX-ACCESS read-create 2178 STATUS current 2179 DESCRIPTION 2180 "This variable is used to create, modify, and/or 2181 delete a row in this table. All read-create objects 2182 can be changed when lmpDataBearingLinkRowStatus is active." 2183 ::= { lmpDataBearingLinkEntry 8 } 2185 lmpDataBearingLinkStorageType OBJECT-TYPE 2186 SYNTAX StorageType 2187 MAX-ACCESS read-create 2188 STATUS current 2189 DESCRIPTION 2190 "The storage type for this conceptual row in the 2191 lmpDataBearingLinkTable. Conceptual rows having the value 2192 'permanent' need not allow write-access to any 2193 columnar object in the row." 2194 ::= { lmpDataBearingLinkEntry 9 } 2196 -- End of lmpDataBearingLinkTable 2198 -- LMP Data Bearing Link Performance Table 2200 lmpDataBearingLinkPerfTable OBJECT-TYPE 2201 SYNTAX SEQUENCE OF LmpDataBearingLinkPerfEntry 2202 MAX-ACCESS not-accessible 2203 STATUS current 2204 DESCRIPTION 2205 "This table specifies the data-bearing links LMP performance 2206 counters." 2207 ::= { lmpObjects 16 } 2209 lmpDataBearingLinkPerfEntry OBJECT-TYPE 2210 SYNTAX LmpDataBearingLinkPerfEntry 2211 MAX-ACCESS not-accessible 2212 STATUS current 2213 DESCRIPTION 2214 "An entry in this table contains information about 2215 the LMP performance counters for the data-bearing links." 2216 AUGMENTS { lmpDataBearingLinkEntry } 2217 ::= { lmpDataBearingLinkPerfTable 1 } 2219 LmpDataBearingLinkPerfEntry ::= SEQUENCE { 2220 lmpDataBearingLinkTestReceived Counter32, 2221 lmpDataBearingLinkTestSent Counter32, 2222 lmpDataBearingLinkActiveTestSuccess Counter32, 2223 lmpDataBearingLinkActiveTestFailure Counter32, 2224 lmpDataBearingLinkPassiveTestSuccess Counter32, 2225 lmpDataBearingLinkPassiveTestFailure Counter32, 2226 lmpDataBearingLinkCounterDiscontinuityTime TimeStamp 2227 } 2229 lmpDataBearingLinkTestReceived OBJECT-TYPE 2230 SYNTAX Counter32 2231 MAX-ACCESS read-only 2232 STATUS current 2233 DESCRIPTION 2234 "This object counts the number of Test messages that have 2235 been received on this data-bearing link." 2236 ::= { lmpDataBearingLinkPerfEntry 1 } 2238 lmpDataBearingLinkTestSent OBJECT-TYPE 2239 SYNTAX Counter32 2240 MAX-ACCESS read-only 2241 STATUS current 2242 DESCRIPTION 2243 "This object counts the number of Test messages that have 2244 been sent on this data-bearing link." 2245 ::= { lmpDataBearingLinkPerfEntry 2 } 2247 lmpDataBearingLinkActiveTestSuccess OBJECT-TYPE 2248 SYNTAX Counter32 2249 MAX-ACCESS read-only 2250 STATUS current 2251 DESCRIPTION 2252 "This object counts the number of data-bearing link test 2253 that were successful on the active side of this data- 2254 bearing link." 2255 ::= { lmpDataBearingLinkPerfEntry 3 } 2257 lmpDataBearingLinkActiveTestFailure OBJECT-TYPE 2258 SYNTAX Counter32 2259 MAX-ACCESS read-only 2260 STATUS current 2261 DESCRIPTION 2262 "This object counts the number of data-bearing link test 2263 that failed on the active side of this data-bearing link." 2264 ::= { lmpDataBearingLinkPerfEntry 4 } 2266 lmpDataBearingLinkPassiveTestSuccess OBJECT-TYPE 2267 SYNTAX Counter32 2268 MAX-ACCESS read-only 2269 STATUS current 2270 DESCRIPTION 2271 "This object counts the number of data-bearing link test 2272 that were successful on the passive side of this data- 2273 bearing link." 2274 ::= { lmpDataBearingLinkPerfEntry 5 } 2276 lmpDataBearingLinkPassiveTestFailure OBJECT-TYPE 2277 SYNTAX Counter32 2278 MAX-ACCESS read-only 2279 STATUS current 2280 DESCRIPTION 2281 "This object counts the number of data-bearing link test 2282 that failed on the passive side of this data-bearing link." 2283 ::= { lmpDataBearingLinkPerfEntry 6 } 2285 lmpDataBearingLinkCounterDiscontinuityTime OBJECT-TYPE 2286 SYNTAX TimeStamp 2287 MAX-ACCESS read-only 2288 STATUS current 2289 DESCRIPTION 2290 "The value of sysUpTime on the most recent occasion at which 2291 any one or more of this data-bearing link's counters suffered a 2292 discontinuity. The relevant counters are the specific 2293 instances associated with this data-bearing link of any Counter32 or 2294 Counter64 object contained in the lmpDataBearingLinkPerfTable. If 2295 no such discontinuities have occurred since the last re- 2296 initialization of the local management subsystem, then this 2297 object contains a zero value." 2298 ::= { lmpDataBearingLinkPerfEntry 7 } 2300 -- End of lmpDataBearingLinkPerfTable 2302 -- Notification Configuration 2304 lmpLinkPropertyMismatchNotifEnable OBJECT-TYPE 2305 SYNTAX TruthValue 2306 MAX-ACCESS read-write 2307 STATUS current 2308 DESCRIPTION 2309 "If this object is true, then it enables the 2310 generation of lmpTeLinkPropertyMismatch 2311 and lmpDataBearingLinkPropertyMismatch notifications, 2312 otherwise these notifications are not emitted." 2313 DEFVAL { false } 2314 ::= { lmpObjects 17 } 2316 lmpUnprotectedNotifEnable OBJECT-TYPE 2317 SYNTAX TruthValue 2318 MAX-ACCESS read-write 2319 STATUS current 2320 DESCRIPTION 2321 "If this object is true, then it enables the 2322 generation of lmpUnprotected notifications, 2323 otherwise these notifications are not emitted." 2324 DEFVAL { false } 2325 ::= { lmpObjects 18 } 2327 lmpCcUpDownNotifEnable OBJECT-TYPE 2328 SYNTAX TruthValue 2329 MAX-ACCESS read-write 2330 STATUS current 2331 DESCRIPTION 2332 "If this object is true, then it enables the generation of 2333 lmpControlChannelUp and lmpControlChannelDown notifications, 2334 otherwise these notifications are not emitted." 2335 DEFVAL { false } 2336 ::= { lmpObjects 19 } 2338 lmpTeLinkNotifEnable OBJECT-TYPE 2339 SYNTAX TruthValue 2340 MAX-ACCESS read-write 2341 STATUS current 2342 DESCRIPTION 2343 "If this object is true, then it enables the 2344 generation of lmpTeLinkDegraded notification, 2345 otherwise these notifications are not emitted." 2346 DEFVAL { false } 2347 ::= { lmpObjects 20 } 2349 lmpDataBearingLinkNotifEnable OBJECT-TYPE 2350 SYNTAX TruthValue 2351 MAX-ACCESS read-write 2352 STATUS current 2353 DESCRIPTION 2354 "If this object is true, then it enables the 2355 generation of lmpDataBearingLinkVerificationFailure 2356 notification, otherwise these notifications are not emitted." 2357 DEFVAL { false } 2358 ::= { lmpObjects 21 } 2360 -- Notifications 2362 -- Link Property Mismatch Notifications 2364 lmpTeLinkPropertyMismatch NOTIFICATION-TYPE 2365 OBJECTS { teLinkRemoteIpAddr, 2366 teLinkIncomingIfId } 2367 STATUS current 2368 DESCRIPTION 2369 "This notification is generated when a TE link property 2370 mismatch is detected on the node. The received remote TE link 2371 id of the misconfigured TE link is represented by either 2372 teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether 2373 the TE link is numbered or unnumbered." 2374 ::= { lmpNotifications 1 } 2376 lmpDataBearingLinkPropertyMismatch NOTIFICATION-TYPE 2377 OBJECTS { ifStackHigherLayer, 2378 lmpDataBearingLinkRemoteIfId } 2379 STATUS current 2380 DESCRIPTION 2381 "This notification is generated when a data-bearing link 2382 property mismatch is detected on the node. ifStackHigherLayer 2383 is the interface index of the TE link. The remote entity 2384 interface id is the remote entity interface id received in the 2385 LinkSummary message." 2386 ::= { lmpNotifications 2 } 2388 -- Neighbor Notification 2390 lmpUnprotected NOTIFICATION-TYPE 2391 OBJECTS { lmpNbrNodeId } 2392 STATUS current 2393 DESCRIPTION 2394 "This notification is generated when all but one control channel 2395 is operational. If the only operational control channel fails, 2396 then there will be no more control channels between the pair of 2397 nodes and all the data-bearing links between the pair of nodes 2398 will go to degraded state." 2399 ::= { lmpNotifications 3 } 2401 -- Control Channel Notifications 2403 lmpControlChannelUp NOTIFICATION-TYPE 2404 OBJECTS { lmpCcId } 2405 STATUS current 2406 DESCRIPTION 2407 "This notification is generated when a control 2408 channel transitions to the up operational state." 2409 ::= { lmpNotifications 4 } 2411 lmpControlChannelDown NOTIFICATION-TYPE 2412 OBJECTS { lmpCcId } 2413 STATUS current 2414 DESCRIPTION 2415 "This notification is generated when a control 2416 channel transitions to the down operational state." 2417 ::= { lmpNotifications 5 } 2419 -- TE Link Notification 2421 lmpTeLinkDegraded NOTIFICATION-TYPE 2422 OBJECTS { ifIndex } 2423 STATUS current 2424 DESCRIPTION 2425 "This notification is generated when a lmpTeLinkOperStatus 2426 object for a TE link enters the degraded state." 2427 ::= { lmpNotifications 6 } 2429 -- Data-bearing Link Notification 2431 lmpDataBearingLinkVerificationFailure NOTIFICATION-TYPE 2432 OBJECTS { ifIndex } 2433 STATUS current 2434 DESCRIPTION 2435 "This notification is generated when a data-bearing 2436 link verification fails." 2437 ::= { lmpNotifications 7 } 2439 -- End of notifications 2441 -- Module compliance 2443 lmpGroups 2444 OBJECT IDENTIFIER ::= { lmpConformance 1 } 2446 lmpCompliances 2447 OBJECT IDENTIFIER ::= { lmpConformance 2 } 2449 lmpFullModuleCompliance MODULE-COMPLIANCE 2450 STATUS current 2451 DESCRIPTION 2452 "Compliance statement for agents that support the 2453 configuration and monitoring of LMP MIB." 2454 MODULE -- this module 2456 -- The mandatory groups have to be implemented 2457 -- by all LMP-enabled devices. However, they may all be supported 2458 -- as read-only objects in the case where manual 2459 -- configuration is unsupported. 2461 MANDATORY-GROUPS { lmpNodeGroup, 2462 lmpControlChannelGroup, 2463 lmpLinkPropertyCorrelationGroup, 2464 lmpPerfGroup, 2465 lmpTeLinkGroup, 2466 lmpDataBearingLinkGroup } 2468 GROUP lmpControlChannelIsNotInterfaceGroup 2469 DESCRIPTION 2470 "This group is mandatory for devices which support 2471 control channels that are not interfaces, in addition to 2472 lmpControlChannelGroup. The following constraints apply: 2473 lmpCcIsIf must at least be read-only returning false(1)." 2475 GROUP lmpControlChannelIsInterfaceGroup 2476 DESCRIPTION 2477 "This group is mandatory for devices which support 2478 control channels that are interfaces, in addition to 2479 lmpControlChannelGroup. The following constraints apply: 2480 lmpCcIsIf must at least be read-only returning true(2)." 2482 GROUP lmpLinkVerificationGroup 2483 DESCRIPTION 2484 "This group is mandatory for devices which support 2485 the link verification procedure." 2487 -- lmpNbrTable 2489 OBJECT lmpNbrRowStatus 2490 SYNTAX INTEGER { active(1), notInService(2), 2491 createAndGo(4), destroy(6) } 2492 MIN-ACCESS read-create 2493 DESCRIPTION 2494 "The notReady(3) and createAndWait(5) states need 2495 not be supported." 2497 OBJECT lmpNbrStorageType 2498 SYNTAX INTEGER { other(1) } 2499 MIN-ACCESS read-create 2500 DESCRIPTION 2501 "Only other(1) needs to be supported." 2503 -- lmpControlChannelTable 2505 OBJECT lmpCcRowStatus 2506 SYNTAX INTEGER { active(1), notInService(2), 2507 createAndGo(4), destroy(6) } 2508 MIN-ACCESS read-create 2509 DESCRIPTION 2510 "The notReady(3) and createAndWait(5) states need 2511 not be supported." 2513 OBJECT lmpCcOperStatus 2514 SYNTAX INTEGER { up(1), down(2) } 2515 MIN-ACCESS read-only 2516 DESCRIPTION 2517 "A value of active(3), configuring(4), goingDown(5) 2518 need not be supported." 2520 OBJECT lmpCcStorageType 2521 SYNTAX INTEGER { other(1) } 2522 MIN-ACCESS read-create 2523 DESCRIPTION 2524 "Only other(1) needs to be supported." 2526 -- lmpTeLinkTable 2528 OBJECT lmpTeLinkOperStatus 2529 SYNTAX INTEGER { up(1), down(2), degraded(4) } 2530 MIN-ACCESS read-only 2531 DESCRIPTION 2532 "The testing(3) state need not be supported." 2534 OBJECT lmpTeLinkRowStatus 2535 SYNTAX INTEGER { active(1), notInService(2), 2536 createAndGo(4), destroy(6) } 2537 MIN-ACCESS read-create 2538 DESCRIPTION 2539 "The notReady(3) and createAndWait(5) states need 2540 not be supported." 2542 OBJECT lmpTeLinkStorageType 2543 SYNTAX INTEGER { other(1) } 2544 MIN-ACCESS read-create 2545 DESCRIPTION 2546 "Only other(1) needs to be supported." 2548 -- lmpDataBearingLinkTable 2550 OBJECT lmpDataBearingLinkActiveOperStatus 2551 SYNTAX INTEGER { up(1), down(2), degraded(4) } 2552 MIN-ACCESS read-only 2553 DESCRIPTION 2554 "A value of testing(3) need not be supported." 2556 OBJECT lmpDataBearingLinkPassiveOperStatus 2557 SYNTAX INTEGER { up(1), down(2), degraded(4) } 2558 MIN-ACCESS read-only 2559 DESCRIPTION 2560 "A value of testing(3) need not be supported." 2562 OBJECT lmpDataBearingLinkRowStatus 2563 SYNTAX INTEGER { active(1), notInService(2), 2564 createAndGo(4), destroy(6) } 2565 MIN-ACCESS read-only 2566 DESCRIPTION 2567 "The notReady(3) and createAndWait(5) states need 2568 not be supported." 2570 OBJECT lmpDataBearingLinkStorageType 2571 SYNTAX INTEGER { other(1) } 2572 MIN-ACCESS read-create 2573 DESCRIPTION 2574 "Only other(1) needs to be supported." 2576 ::= { lmpCompliances 1 } 2578 lmpMonitoringModuleCompliance MODULE-COMPLIANCE 2579 STATUS current 2580 DESCRIPTION 2581 "Compliance statement for agents that support the 2582 monitoring of the LMP MIB." 2583 MODULE -- this module 2585 -- The mandatory groups have to be implemented 2586 -- by all LMP-enabled devices. However, they may all be supported 2587 -- as read-only objects in the case where manual 2588 -- configuration is unsupported. 2590 MANDATORY-GROUPS { lmpNodeGroup, 2591 lmpControlChannelGroup, 2592 lmpLinkPropertyCorrelationGroup, 2593 lmpPerfGroup, 2594 lmpTeLinkGroup, 2595 lmpDataBearingLinkGroup } 2597 GROUP lmpControlChannelIsNotInterfaceGroup 2598 DESCRIPTION 2599 "This group is mandatory for devices which support 2600 control channels that are not interfaces, in addition to 2601 lmpControlChannelGroup. The following constraints apply: 2602 lmpCcIsIf must at least be read-only returning false(1)." 2604 GROUP lmpControlChannelIsInterfaceGroup 2605 DESCRIPTION 2606 "This group is mandatory for devices which support 2607 control channels that are interfaces, in addition to 2608 lmpControlChannelGroup. The following constraints apply: 2609 lmpCcIsIf must at least be read-only returning true(2)." 2611 GROUP lmpLinkVerificationGroup 2612 DESCRIPTION 2613 "This group is mandatory for devices which support 2614 the link verification procedure." 2616 -- Scalars 2618 OBJECT lmpAdminStatus 2619 MIN-ACCESS read-only 2620 DESCRIPTION 2621 "Write access is not required." 2623 OBJECT lmpLinkVerificationInterval 2624 MIN-ACCESS read-only 2625 DESCRIPTION 2626 "Write access is not required." 2628 OBJECT lmpCcHelloIntervalDefault 2629 MIN-ACCESS read-only 2630 DESCRIPTION 2631 "Write access is not required." 2633 OBJECT lmpCcHelloIntervalDefaultMin 2634 MIN-ACCESS read-only 2635 DESCRIPTION 2636 "Write access is not required." 2638 OBJECT lmpCcHelloIntervalDefaultMax 2639 MIN-ACCESS read-only 2640 DESCRIPTION 2641 "Write access is not required." 2643 OBJECT lmpCcHelloDeadIntervalDefault 2644 MIN-ACCESS read-only 2645 DESCRIPTION 2646 "Write access is not required." 2648 OBJECT lmpCcHelloDeadIntervalDefaultMin 2649 MIN-ACCESS read-only 2650 DESCRIPTION 2651 "Write access is not required." 2653 OBJECT lmpCcHelloDeadIntervalDefaultMax 2654 MIN-ACCESS read-only 2655 DESCRIPTION 2656 "Write access is not required." 2658 -- lmpNbrTable 2660 OBJECT lmpNbrRetransmitInterval 2661 MIN-ACCESS read-only 2662 DESCRIPTION 2663 "Write access is not required." 2665 OBJECT lmpNbrRetransmitTimeout 2666 MIN-ACCESS read-only 2667 DESCRIPTION 2668 "Write access is not required." 2670 OBJECT lmpNbrRowStatus 2671 SYNTAX INTEGER { active(1), notInService(2), 2672 createAndGo(4), destroy(6) } 2673 MIN-ACCESS read-only 2674 DESCRIPTION 2675 "The notReady(3) and createAndWait(5) states need 2676 not be supported." 2678 OBJECT lmpNbrStorageType 2679 SYNTAX INTEGER { other(1) } 2680 MIN-ACCESS read-only 2681 DESCRIPTION 2682 "Only other(1) needs to be supported." 2684 -- lmpControlChannelTable 2686 OBJECT lmpCcUnderlyingIfIndex 2687 MIN-ACCESS read-only 2688 DESCRIPTION 2689 "Write access is not required." 2691 OBJECT lmpCcIsIf 2692 MIN-ACCESS read-only 2693 DESCRIPTION 2694 "Write access is not required." 2696 OBJECT lmpCcNbrNodeId 2697 MIN-ACCESS read-only 2698 DESCRIPTION 2699 "Write access is not required." 2701 OBJECT lmpCcSetupRole 2702 MIN-ACCESS read-only 2703 DESCRIPTION 2704 "Write access is not required." 2706 OBJECT lmpCcAuthentication 2707 MIN-ACCESS read-only 2708 DESCRIPTION 2709 "Write access is not required." 2711 OBJECT lmpCcConfigRetransmitInterval 2712 MIN-ACCESS read-only 2713 DESCRIPTION 2714 "Write access is not required." 2716 OBJECT lmpCcConfigRetransmitTimeout 2717 MIN-ACCESS read-only 2718 DESCRIPTION 2719 "Write access is not required." 2721 OBJECT lmpCcHelloIntervalMin 2722 MIN-ACCESS read-only 2723 DESCRIPTION 2724 "Write access is not required." 2726 OBJECT lmpCcHelloIntervalMax 2727 MIN-ACCESS read-only 2728 DESCRIPTION 2729 "Write access is not required." 2731 OBJECT lmpCcHelloDeadIntervalMin 2732 MIN-ACCESS read-only 2733 DESCRIPTION 2734 "Write access is not required." 2736 OBJECT lmpCcHelloDeadIntervalMax 2737 MIN-ACCESS read-only 2738 DESCRIPTION 2739 "Write access is not required." 2741 OBJECT lmpCcRowStatus 2742 SYNTAX INTEGER { active(1), notInService(2), 2743 createAndGo(4), destroy(6) } 2744 MIN-ACCESS read-only 2745 DESCRIPTION 2746 "The notReady(3) and createAndWait(5) states need 2747 not be supported." 2749 OBJECT lmpCcOperStatus 2750 SYNTAX INTEGER { up(1), down(2) } 2751 MIN-ACCESS read-only 2752 DESCRIPTION 2753 "A value of active(3), configuring(4), goingDown(5) 2754 need not be supported." 2756 OBJECT lmpCcStorageType 2757 SYNTAX INTEGER { other(1) } 2758 MIN-ACCESS read-only 2759 DESCRIPTION 2760 "Only other(1) needs to be supported." 2762 -- lmpLinkVerificationTable 2764 OBJECT lmpVerifyInterval 2765 MIN-ACCESS read-only 2766 DESCRIPTION 2767 "Write access is not required." 2769 OBJECT lmpVerifyDeadInterval 2770 MIN-ACCESS read-only 2771 DESCRIPTION 2772 "Write access is not required." 2774 OBJECT lmpVerifyAllLinks 2775 MIN-ACCESS read-only 2776 DESCRIPTION 2777 "Write access is not required." 2779 -- lmpTeLinkTable 2781 OBJECT lmpTeLinkNbrNodeId 2782 MIN-ACCESS read-only 2783 DESCRIPTION 2784 "Write access is not required if the link verification 2785 procedure is enabled." 2787 OBJECT lmpTeLinkVerification 2788 MIN-ACCESS read-only 2789 DESCRIPTION 2790 "Write access is not required." 2792 OBJECT lmpTeLinkFaultManagement 2793 MIN-ACCESS read-only 2794 DESCRIPTION 2795 "Write access is not required." 2797 OBJECT lmpTeLinkDwdm 2798 MIN-ACCESS read-only 2799 DESCRIPTION 2800 "Write access is not required." 2802 OBJECT lmpTeLinkOperStatus 2803 SYNTAX INTEGER { up(1), down(2), degraded(4) } 2804 MIN-ACCESS read-only 2805 DESCRIPTION 2806 "The testing(3) state need not be supported." 2808 OBJECT lmpTeLinkRowStatus 2809 SYNTAX INTEGER { active(1), notInService(2), 2810 createAndGo(4), destroy(6) } 2811 MIN-ACCESS read-only 2812 DESCRIPTION 2813 "The notReady(3) and createAndWait(5) states need 2814 not be supported." 2816 OBJECT lmpTeLinkStorageType 2817 SYNTAX INTEGER { other(1) } 2818 MIN-ACCESS read-only 2819 DESCRIPTION 2820 "Only other(1) needs to be supported." 2822 -- lmpTeLinkVerificationTable 2824 OBJECT lmpTeLinkBitRate 2825 MIN-ACCESS read-only 2826 DESCRIPTION 2827 "Write access is not required." 2829 OBJECT lmpTeLinkWavelength 2830 MIN-ACCESS read-only 2831 DESCRIPTION 2832 "Write access is not required." 2834 -- lmpDataBearingLinkTable 2836 OBJECT lmpDataBearingLinkNumberingType 2837 MIN-ACCESS read-only 2838 DESCRIPTION 2839 "Write access is not required if the link verification 2840 procedure is enabled." 2842 OBJECT lmpDataBearingLinkRemoteIfId 2843 MIN-ACCESS read-only 2844 DESCRIPTION 2845 "Write access is not required if the link verification 2846 procedure is enabled." 2848 OBJECT lmpDataBearingLinkRemoteIpAddress 2849 MIN-ACCESS read-only 2850 DESCRIPTION 2851 "Write access is not required if the link verification 2852 procedure is enabled." 2854 OBJECT lmpDataBearingLinkEncodingType 2855 MIN-ACCESS read-only 2856 DESCRIPTION 2857 "Write access is not required." 2859 OBJECT lmpDataBearingLinkActiveOperStatus 2860 SYNTAX INTEGER { up(1), down(2), degraded(4) } 2861 MIN-ACCESS read-only 2862 DESCRIPTION 2863 "A value of testing(3) need not be supported." 2865 OBJECT lmpDataBearingLinkPassiveOperStatus 2866 SYNTAX INTEGER { up(1), down(2), degraded(4) } 2867 MIN-ACCESS read-only 2868 DESCRIPTION 2869 "A value of psvTst(3) need not be supported." 2871 OBJECT lmpDataBearingLinkRowStatus 2872 SYNTAX INTEGER { active(1), notInService(2), 2873 createAndGo(4), destroy(6) } 2874 MIN-ACCESS read-only 2875 DESCRIPTION 2876 "The notReady(3) and createAndWait(5) states need 2877 not be supported." 2879 OBJECT lmpDataBearingLinkStorageType 2880 SYNTAX INTEGER { other(1) } 2881 MIN-ACCESS read-only 2882 DESCRIPTION 2883 "Only other(1) needs to be supported." 2885 ::= { lmpCompliances 2 } 2887 -- Units of conformance 2889 lmpNodeGroup OBJECT-GROUP 2890 OBJECTS { lmpAdminStatus, 2891 lmpOperStatus, 2892 lmpNbrAdminStatus, 2893 lmpNbrOperStatus, 2894 lmpNbrRowStatus, 2895 lmpNbrStorageType, 2896 lmpUnprotectedNotifEnable 2897 } 2898 STATUS current 2899 DESCRIPTION 2900 "Collection of objects needed for LMP node configuration." 2901 ::= { lmpGroups 1 } 2903 lmpControlChannelGroup OBJECT-GROUP 2904 OBJECTS { 2905 lmpNbrNodeId, 2906 lmpNbrRetransmitInterval, 2907 lmpNbrRetransmitTimeout, 2908 lmpNbrAdminStatus, 2909 lmpNbrOperStatus, 2910 lmpNbrRowStatus, 2911 lmpNbrStorageType, 2912 lmpCcHelloIntervalDefault, 2913 lmpCcHelloIntervalDefaultMin, 2914 lmpCcHelloIntervalDefaultMax, 2915 lmpCcHelloDeadIntervalDefault, 2916 lmpCcHelloDeadIntervalDefaultMin, 2917 lmpCcHelloDeadIntervalDefaultMax, 2918 lmpCcNbrNodeId, 2919 lmpCcId, 2920 lmpRemoteCcId, 2921 lmpCcSetupRole, 2922 lmpCcAuthentication, 2923 lmpCcConfigRetransmitInterval, 2924 lmpCcConfigRetransmitTimeout, 2925 lmpCcHelloInterval, 2926 lmpCcHelloIntervalMin, 2927 lmpCcHelloIntervalMax, 2928 lmpCcHelloIntervalNegotiated, 2929 lmpCcHelloDeadInterval, 2930 lmpCcHelloDeadIntervalMin, 2931 lmpCcHelloDeadIntervalMax, 2932 lmpCcHelloDeadIntervalNegotiated, 2933 lmpCcOperStatus, 2934 lmpCcRowStatus, 2935 lmpCcStorageType, 2936 lmpCcUpDownNotifEnable 2937 } 2938 STATUS current 2939 DESCRIPTION 2940 "Collection of objects needed for LMP interface 2941 configuration." 2942 ::= { lmpGroups 2 } 2944 lmpControlChannelIsInterfaceGroup OBJECT-GROUP 2945 OBJECTS { lmpCcIsIf } 2946 STATUS current 2947 DESCRIPTION 2948 "Objects needed to implement control channels that are 2949 interfaces." 2950 ::= { lmpGroups 3 } 2952 lmpControlChannelIsNotInterfaceGroup OBJECT-GROUP 2953 OBJECTS { 2954 lmpCcUnderlyingIfIndex, 2955 lmpCcIsIf, 2956 lmpCcLastChange, 2957 lmpCcAdminStatus 2958 } 2959 STATUS current 2960 DESCRIPTION 2961 "Objects needed to implement control channels that are not 2962 interfaces." 2963 ::= { lmpGroups 4 } 2965 lmpLinkPropertyCorrelationGroup OBJECT-GROUP 2966 OBJECTS { lmpLinkPropertyMismatchNotifEnable } 2967 STATUS current 2968 DESCRIPTION 2969 "Collection of objects needed to implement the link 2970 property correlation procedure." 2971 ::= { lmpGroups 5 } 2973 lmpLinkVerificationGroup OBJECT-GROUP 2974 OBJECTS { lmpLinkVerificationInterval, 2975 lmpVerifyInterval, 2976 lmpVerifyDeadInterval, 2977 lmpVerifyTransportMechanism, 2978 lmpVerifyAllLinks, 2979 lmpTeLinkBitRate, 2980 lmpTeLinkWavelength, 2981 lmpDataBearingLinkNotifEnable 2982 } 2983 STATUS current 2984 DESCRIPTION 2985 "Collection of objects needed to implement the link 2986 verification procedure." 2987 ::= { lmpGroups 6 } 2989 lmpPerfGroup OBJECT-GROUP 2990 OBJECTS { lmpCcInOctets, 2991 lmpCcInDiscards, 2992 lmpCcInErrors, 2993 lmpCcOutOctets, 2994 lmpCcOutDiscards, 2995 lmpCcOutErrors, 2996 lmpCcConfigReceived, 2997 lmpCcConfigSent, 2998 lmpCcConfigRetransmit, 2999 lmpCcConfigAckReceived, 3000 lmpCcConfigAckSent, 3001 lmpCcConfigNackSent, 3002 lmpCcConfigNackReceived, 3003 lmpCcHelloReceived, 3004 lmpCcHelloSent, 3005 lmpCcBeginVerifyReceived, 3006 lmpCcBeginVerifySent, 3007 lmpCcBeginVerifyReceived, 3008 lmpCcBeginVerifyAckReceived, 3009 lmpCcBeginVerifyAckSent, 3010 lmpCcBeginVerifyNackReceived, 3011 lmpCcBeginVerifyNackSent, 3012 lmpCcEndVerifyReceived, 3013 lmpCcEndVerifySent, 3014 lmpCcEndVerifyReceived, 3015 lmpCcEndVerifyAckReceived, 3016 lmpCcEndVerifyAckSent, 3017 lmpCcTestStatusSuccessReceived, 3018 lmpCcTestStatusSuccessSent, 3019 lmpCcTestStatusSuccessReceived, 3020 lmpCcTestStatusFailureReceived, 3021 lmpCcTestStatusFailureSent, 3022 lmpCcTestStatusFailureReceived, 3023 lmpCcLinkSummaryReceived, 3024 lmpCcLinkSummarySent, 3025 lmpCcLinkSummaryRetransmit, 3026 lmpCcLinkSummaryAckReceived, 3027 lmpCcLinkSummaryAckSent, 3028 lmpCcLinkSummaryNackReceived, 3029 lmpCcLinkSummaryNackSent, 3030 lmpCcChannelStatusReceived, 3031 lmpCcChannelStatusSent, 3032 lmpCcChannelStatusRetransmit, 3033 lmpCcChannelStatusAckReceived, 3034 lmpCcChannelStatusAckSent, 3035 lmpCcChannelStatusRequestReceived, 3036 lmpCcChannelStatusRequestSent, 3037 lmpCcChannelStatusRequestRetransmit, 3038 lmpCcChannelStatusResponseReceived, 3039 lmpCcChannelStatusResponseSent, 3040 lmpCcCounterDiscontinuityTime, 3041 lmpDataBearingLinkTestReceived, 3042 lmpDataBearingLinkTestSent, 3043 lmpDataBearingLinkActiveTestSuccess, 3044 lmpDataBearingLinkActiveTestFailure, 3045 lmpDataBearingLinkPassiveTestSuccess, 3046 lmpDataBearingLinkPassiveTestFailure, 3047 lmpDataBearingLinkCounterDiscontinuityTime 3048 } 3050 STATUS current 3051 DESCRIPTION 3052 "Collection of objects needed for providing performance 3053 information about LMP interfaces and data-bearing links." 3054 ::= { lmpGroups 7 } 3056 lmpTeLinkGroup OBJECT-GROUP 3057 OBJECTS { lmpTeLinkNbrNodeId, 3058 lmpTeLinkVerification, 3059 lmpTeLinkFaultManagement, 3060 lmpTeLinkDwdm, 3061 lmpTeLinkOperStatus, 3062 lmpTeLinkRowStatus, 3063 lmpTeLinkStorageType, 3064 lmpTeLinkNotifEnable 3065 } 3066 STATUS current 3067 DESCRIPTION 3068 "Collection of objects needed for TE link configuration." 3069 ::= { lmpGroups 8 } 3071 lmpDataBearingLinkGroup OBJECT-GROUP 3072 OBJECTS { lmpDataBearingLinkType, 3073 lmpDataBearingLinkNumberingType, 3074 lmpDataBearingLinkRemoteIfId, 3075 lmpDataBearingLinkRemoteIpAddress, 3076 lmpDataBearingLinkEncodingType, 3077 lmpDataBearingLinkActiveOperStatus, 3078 lmpDataBearingLinkPassiveOperStatus, 3079 lmpDataBearingLinkRowStatus, 3080 lmpDataBearingLinkStorageType 3081 } 3082 STATUS current 3083 DESCRIPTION 3084 "Collection of objects needed for data-bearing link 3085 configuration." 3086 ::= { lmpGroups 9 } 3088 lmpNotificationGroup NOTIFICATION-GROUP 3089 NOTIFICATIONS { lmpTeLinkPropertyMismatch, 3090 lmpDataBearingLinkPropertyMismatch, 3091 lmpUnprotected, 3092 lmpControlChannelUp, 3093 lmpControlChannelDown, 3094 lmpTeLinkDegraded, 3095 lmpDataBearingLinkVerificationFailure } 3096 STATUS current 3097 DESCRIPTION 3098 "Set of notifications implemented in this module. 3099 None is mandatory." 3100 ::= { lmpGroups 10 } 3102 -- End of LMP-MIB 3103 END 3105 11. Security Considerations 3107 It is clear that this MIB is potentially useful for monitoring of LMP 3108 enabled devices. This MIB can also be used for configuration of cer- 3109 tain objects, and anything that can be configured can be incorrectly 3110 configured, with potentially disastrous results. 3112 At this writing, no security holes have been identified beyond those 3113 that SNMP Security [RFC2571] is itself intended to address. These 3114 relate to primarily controlled access to sensitive information and 3115 the ability to configure a device - or which might result from opera- 3116 tor error, which is beyond the scope of any security architecture. 3118 There are a number of management objects defined in this MIB which 3119 have a MAX-ACCESS clause of read-write and/or read-create. Such 3120 objects may be considered sensitive or vulnerable in some network 3121 environments. The support for SET operations in a non-secure environ- 3122 ment without proper protection can have a negative effect on network 3123 operations. The use of SNMP Version 3 is recommended over prior ver- 3124 sions, for configuration control, as its security model is improved. 3126 SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if 3127 the network itself is secure (for example by using IPSec [IPSEC]), 3128 there is no control as to who on the secure network is allowed to 3129 access and GET/SET (read/change/create/delete) the objects in this 3130 MIB. It is recommended that the implementers consider the security 3131 features as provided by the SNMPv3 framework. Specifically, the use 3132 of the User-based Security Model [RFC2574] and the View-based Access 3133 Control [RFC2575] is recommended. It is then a customer/user respon- 3134 sibility to ensure that the SNMP entity giving access to an instance 3135 of this MIB is properly configured to give access to the objects only 3136 to those principals (users) that have legitimate rights to indeed GET 3137 or SET (change/create/delete) them. 3139 There are a number of managed objects in this MIB that may contain 3140 information that may be sensitive from a business perspective, in 3141 that they can be used to derive the network topology, e.g. list of 3142 nodes and their IP address (lmpNbrTable) and list of data-bearing 3143 links (lmpDataBearingLinkTable). Allowing uncontrolled access to 3144 these objects could result in malicious and unwanted disruptions of 3145 network traffic, incorrect network configurations or theft of com- 3146 petitive business information. There are no objects that are particu- 3147 larly sensitive in their own right, such as passwords or monetary 3148 amounts. 3150 12. Acknowledgments 3152 The general structure of this draft has been modeled around draft- 3153 ietf-mpls-lsr-mib-06.txt. 3155 The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and 3156 George Wang. 3158 13. References 3160 [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., 3161 Rekhter, Y., Berger, L., Saha, S., Basak, D., 3162 Sandick, H., Zinin, A., and Rajagopalan, B., 3163 "Link Management Protocol", Internet Draft 3164 , November 2001. 3166 [GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L., 3167 Bernstein, G., Drake, J., Fan, Y., Kompella, K., 3168 Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., 3169 Saha, D., Sharma, V., Swallow, G., and Tang, Z., 3170 "Generalized MPLS Signaling Function Description", 3171 Internet Draft 3172 , 3173 November 2001. 3175 [BUNDLE] Kompella, K., Rekhter, Y., and Berger, L., 3176 "Link Bundling in MPLS Traffic Engineering", 3177 Internet Draft , 3178 November 2001. 3180 [BUNDLE-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J., 3181 "Link Bundling Management Information Base", 3182 Internet Draft , 3183 January 2002. 3185 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 3186 RFC 1700, October 1994. See also: 3187 http://www.isi.edu/in-notes/iana/assignments/smi- 3188 numbers 3190 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 3191 FAMILY NUMBERS, (http://www.isi.edu/in- 3192 notes/iana/assignements/address-family-numbers), 3193 for MIB see: 3194 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 3196 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 3197 Architecture for Describing SNMP Management 3198 Frameworks", RFC 2571, April 1999. 3200 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 3201 Identification of Management Information for TCP/IP- 3202 based Internets", STD 16, RFC 1155, May 1990. 3204 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 3205 STD 16, RFC 1212, March 1991. 3207 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 3208 the SNMP", RFC 1215, March 1991. 3210 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 3211 J., Rose, M., and S. Waldbusser, "Structure of 3212 Management Information Version 2 (SMIv2)", STD 58, 3213 RFC 2578, April 1999. 3215 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 3216 J., Rose, M., and S. Waldbusser, "Textual Conventions 3217 for SMIv2", STD 58, RFC 2579, April 1999. 3219 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 3220 J., Rose, M., and S. Waldbusser, "Conformance 3221 Statements for SMIv2", STD 58, RFC 2580, April 1999. 3223 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 3224 "Simple Network Management Protocol", STD 15, RFC 1157, 3225 May 1990. 3227 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3228 "Introduction to Community-based SNMPv2", RFC 1901, 3229 January 1996. 3231 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3232 "Transport Mappings for Version 2 of the Simple Network 3233 Management Protocol (SNMPv2)", RFC 1906, January 1996. 3235 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 3236 "Message Processing and Dispatching for the Simple 3237 Network Management Protocol (SNMP)", RFC 2572, April 3238 1999. 3240 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 3241 Model (USM) for version 3 of the Simple Network 3242 Management Protocol (SNMPv3)", RFC 2574, April 1999. 3244 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3245 "Protocol Operations for Version 2 of the Simple 3246 Network Management Protocol (SNMPv2)", RFC 1905, 3247 January 1996. 3249 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 3250 Applications", RFC 2573, April 1999. 3252 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 3253 Access Control Model (VACM) for the Simple Network 3254 Management Protocol (SNMP)", RFC 2575, April 1999. 3256 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 3257 "Introduction to Version 3 of the Internet-standard 3258 Network Management Framework", RFC 2570, April 1999. 3260 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 3261 for the Internet Protocol", RFC 2401, November 3262 1998. 3264 [IFMIB] McCloghrie, K., and Kastenholtz, F., "The Interfaces 3265 Group MIB", RFC 2863, June 2000. 3267 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 3268 Requirement Levels", BCP 14, RFC 2119, March 1997. 3270 14. Authors' Addresses 3272 Martin Dubuc Jonathan P. Lang 3273 Meriton Networks Calient Networks, Inc. 3274 3026 Solandt Road 25 Castilian Drive 3275 Kanata, ON, CANADA K2K 2A5 Goleta, CA 93117 3276 Phone: +1-613-270-9279 x253 Email: jplang@calient.net 3277 Email: martin.dubuc@meriton.com 3279 Sudheer Dharanikota Evan McGinnis 3280 Nayna Networks, Inc. Calient Networks, Inc. 3281 157 Topaz Street 5853 Rue Ferrari 3282 Milipitas, CA 95035 San Jose, CA 95138 3283 Phone: +1-408-956-8000 x357 Email: evan@calient.net 3284 Email: sudheer@nayna.com 3285 Thomas D. Nadeau 3286 Cisco Systems, Inc. 3287 300 Apollo Drive 3288 Chelmsford, MA 01824 3289 Phone: +1-978-244-3051 3290 Email: tnadeau@cisco.com 3292 15. Full Copyright Statement 3294 Copyright (C) The Internet Society (2001). All Rights Reserved. 3296 This document and translations of it may be copied and furnished to 3297 others, and derivative works that comment on or otherwise explain it 3298 or assist in its implementation may be prepared, copied, published 3299 and distributed, in whole or in part, without restriction of any 3300 kind, provided that the above copyright notice and this paragraph are 3301 included on all such copies and derivative works. However, this docu- 3302 ment itself may not be modified in any way, such as by removing the 3303 copyright notice or references to the Internet Society or other 3304 Internet organizations, except as needed for the purpose of develop- 3305 ing Internet standards in which case the procedures for copyrights 3306 defined in the Internet Standards process must be followed, or as 3307 required to translate it into languages other than English. 3309 The limited permissions granted above are perpetual and will not be 3310 revoked by the Internet Society or its successors or assigns. This 3311 document and the information contained herein is provided on an "AS 3312 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 3313 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 3314 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 3315 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 3316 OR FITNESS FOR A PARTICULAR PURPOSE.