idnits 2.17.1 draft-ietf-ccamp-lmp-mib-02.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 61 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 (May 2002) is 8016 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 418, but not defined == Unused Reference: 'GMPLS' is defined on line 3758, but no explicit reference was found in the text == Unused Reference: 'BUNDLE' is defined on line 3767, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 3777, but no explicit reference was found in the text == Unused Reference: 'IANAFamily' is defined on line 3782, 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: November 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 May 2002 17 Link Management Protocol Management Information Base 19 draft-ietf-ccamp-lmp-mib-02.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. lmpTeLinkPerfTable ........................................... 7 57 7.7. lmpDataBearingLinkTable ...................................... 7 58 7.8. lmpDataBearingLinkPerfTable .................................. 7 59 8. Example of LMP Control Channel Interface Setup ............... 7 60 9. Application of the Interfaces Group to LMP ................... 10 61 9.1. Support of the LMP Layer by ifTable .......................... 10 62 10. Link Management Protocol MIB Definitions ..................... 12 63 11. Security Considerations ...................................... 78 64 12. Acknowledgments .............................................. 79 65 13. References ................................................... 79 66 14. Authors' Addresses ........................................... 82 67 15. Full Copyright Statement ..................................... 82 69 1. Abstract 71 This memo defines an experimental portion of the Management Informa- 72 tion Base (MIB) for use with network management protocols in the 73 Internet community. In particular, it describes managed objects for 74 modeling the Link Management Protocol (LMP) [LMP]. 76 2. Introduction 78 Current work is underway in the IETF to specify a suite of protocols 79 to be used as a common control plane and a separate common measure- 80 ment plane. The Link Management Protocol, which primary purpose is to 81 manage traffic engineering (TE) links, is one of the key components 82 of this standardization activity. Primary goals of LMP are the 83 maintenance of the control channel connectivity, correlation of link 84 properties, verification of data-bearing links and detection and iso- 85 lation of link faults. 87 We describe in this document a MIB that can be used to manage LMP 88 implementations. This MIB covers both configuration and performance 89 monitoring aspects of LMP. 91 Comments should be made directly to the ccamp mailing list at 92 ccamp@ops.ietf.org. 94 This memo does not, in its draft form, specify a standard for the 95 Internet community. 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in RFC 2119, reference 100 [BCP14]. 102 3. Terminology 104 This document uses terminology from the document describing the Link 105 Management Protocol [LMP]. An "LMP adjacency" is formed between two 106 nodes that support the same capabilities, and LMP messages are 107 exchanged between the node pair over control channels that form this 108 adjacency. Several control channels can be active at the same time. 109 With the exception of messages related to control channel management, 110 any time a LMP message needs to be transferred to a neighbor node, it 111 can be sent on any of the active control channels. The control chan- 112 nels can also be used to exchange MPLS control plane information or 113 routing information. 115 LMP is designed to support aggregation of one or more data-bearing 116 links into a traffic-engineering (TE) link. The data-bearing links 117 can be either component links or ports depending on their multiplex- 118 ing capability (see [LMP] for distinction between port and component 119 link). 121 Each TE link is associated with an LMP adjacency, and one or more 122 control channels are used to exchange LMP messages for a particular 123 adjacency. In turn, control channels are used to manage the TE links 124 associated with the LMP adjacency. 126 4. The SNMP Management Framework 128 The SNMP Management Framework presently consists of five major com- 129 ponents: 131 - An overall architecture, described in RFC 2571 [RFC2571]. 133 - Mechanisms for describing and naming objects and events for the 134 purpose of management. The first version of this Structure of 135 Management Information (SMI) is called SMIv1 and described in 136 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 137 1215 [RFC1215]. The second version, called SMIv2, is described 138 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 139 STD 58, RFC 2580 [RFC2580]. 141 - Message protocols for transferring management information. The 142 first version of the SNMP message protocol is called SNMPv1 and 143 described in STD 15, RFC 1157 [RFC1157]. A second version of 144 the SNMP message protocol, which is not an Internet standards 145 track protocol, is called SNMPv2c and described in RFC 1901 146 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 147 message protocol is called SNMPv3 and described in RFC 1906 148 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 150 - Protocol operations for accessing management information. The 151 first set of protocol operations and associated PDU formats is 152 described in STD 15, RFC 1157 [RFC1157]. A second set of 153 protocol operations and associated PDU formats is described in 154 RFC 1905 [RFC1905]. 156 - A set of fundamental applications described in RFC 2573 157 [RFC2573] and the view-based access control mechanism described 158 in RFC 2575 [RFC2575]. 160 A more detailed introduction to the current SNMP Management Framework 161 can be found in RFC 2570 [RFC2570]. 163 Managed objects are accessed via a virtual information store, termed 164 the Management Information Base or MIB. Objects in the MIB are 165 defined using the mechanisms defined in the SMI. 167 This memo specifies a MIB module that is compliant to the SMIv2. A 168 MIB conforming to the SMIv1 can be produced through the appropriate 169 translations. The resulting translated MIB must be semantically 170 equivalent, except where objects or events are omitted because no 171 translation is possible (use of Counter64). Some machine readable 172 information in SMIv2 will be converted into textual descriptions in 173 SMIv1 during the translation process. However, this loss of machine 174 readable information is not considered to change the semantics of the 175 MIB. 177 5. Feature Checklist 179 The Link Management protocol MIB (LMP-MIB) is designed to satisfy the 180 following requirements and constraints: 182 - The MIB supports the enabling and disabling of LMP capability 183 on LMP capable interfaces of a photonic switch, optical 184 cross-connect or router. 186 - The MIB is used provide information about LMP adjacencies. 188 - Support is provided for configuration of the keep alive and 189 link verification parameters. 191 - The MIB is used to express the mapping between local and remote 192 TE links, as well as local and remote interface identifiers for 193 port or component link. 195 - Performance counters are provided for measuring LMP 196 performance on a per-control channel basis. Performance counters 197 are also provided for measuring LMP performance on the data- 198 bearing links. 200 Note that the LMP MIB goes hand-in-hand with the Link Bundling MIB 201 [BUNDLE-MIB]. The TE link table, which is used to associate data- 202 bearing links to TE links, is defined in the Link Bundling MIB. The 203 TE link table in the LMP MIB contains TE link information specific to 204 LMP. 206 6. Outline 208 Configuring LMP through an optical device involves the following 209 steps: 211 - Enabling LMP on LMP capable interfaces through control channel 212 configuration. 214 - Optionally specifying link verification parameters. 216 - Configuring the data-bearing links and associating them to the 217 appropriate TE link (this association is stored in the 218 ifStackTable of the Interfaces Group MIB). 220 TE links are managed by the control channels that run between the 221 same pair of nodes (LMP adjacency). 223 6.1. Summary of LMP MIB 225 The MIB objects for performing these actions consist of the following 226 tables: 228 - The remote node table (lmpNbrTable) is used to identify the pair 229 of nodes that exchange LMP messages over control channels. 231 - The control channel table (lmpControlChannelTable) is used 232 for enabling the LMP protocol on LMP-capable interfaces. 234 - The control channel performance table 235 (lmpControlChannelPerfTable) is used for collecting 236 LMP performance counts on a per-control channel basis. 238 - The TE link table (lmpTeLinkTable) is used for 239 specifying LMP information associated with TE links. 241 - The link verification table (lmpLinkVerificationTable) is used for 242 configuring the LMP link verification parameters of TE links. 244 - The TE link performance table (lmpTeLinkPerfTable) is used for 245 collecting LMP performance counts on a per-TE link basis. 247 - The data-bearing link table (lmpDataBearingLinkTable) is used to 248 specify the data-bearing links that are associated with TE links. 250 - The data-bearing link performance table 251 (lmpDataBearingLinkPerfTable) is used for collecting LMP 252 performance counts on data-bearing links. 254 These tables are described in the subsequent sections. 256 7. Brief Description of MIB Objects 258 Sections 7.1-7.3 describe objects pertaining to LMP-capable inter- 259 faces. Section 7.4 to 7.7 describes objects for specifying TE links 260 and data-bearing links. The MIB objects were derived from the LMP 261 document [LMP]. 263 7.1. lmpNbrTable 265 This table identifies the pairs of nodes on which LMP is enabled. 267 7.2. lmpControlChannelTable 269 This table represents the interfaces that are LMP capable (i.e. capa- 270 ble of transmitting LMP messages). A photonic switch, optical cross- 271 connect, or router creates an entry in this table for every LMP capa- 272 ble interface on that device. 274 7.3. lmpControlChannelPerfTable 276 This table contains the objects to measure the LMP performance of LMP 277 capable interfaces and is an AUGMENT to the lmpControlChannelTable. 279 7.4. lmpTeLinkTable 281 This table represents the TE link information specific to LMP. 283 7.5. lmpLinkVerificationTable 285 This table augments the lmpTeLinkTable and represents the link verif- 286 ication parameters associated with the TE links. 288 7.6. lmpTeLinkPerfTable 290 This table contains the objects to measure the LMP performance of LMP 291 capable interfaces and is an AUGMENT to the lmpTeLinkTable. 293 7.7. lmpDataBearingLinkTable 295 The data-bearing link table enumerates the data-bearing links that 296 are associated with each TE link. 298 7.8. lmpDataBearingLinkPerfTable 300 This table augments the lmpDataBearingLinkTable. It contains the 301 objects to measure the LMP performance of data-bearing links. 303 8. Example of LMP Control Channel Setup 305 In this section we provide a brief example of using the MIB 306 objects described in section 10 to set up an LMP control channel. 307 While this example is not meant to illustrate every nuance of the 308 MIB, it is intended as an aid to understanding some of the key 309 concepts. It is meant to be read after going through the MIB itself. 311 Suppose that one would like to form an LMP adjacency between two 312 nodes using two control channels. Suppose also that there are 313 three data-bearing links. We also assume that the data-bearing 314 links are ports (lambdas). We also assume that the link 315 verification procedure is not enabled. The following example 316 illustrates which rows and corresponding objects might be created 317 to accomplish this. 319 First, LMP must be enabled between the pair of nodes. 321 In lmpNbrTable: 323 { 324 lmpNbrNodeId = 'c0010101'H, -- 192.1.1.1 325 lmpNbrRetransmitInterval = 10, 326 lmpNbrRetransmitTimeoutInterval = 0, 327 lmpNbrAdminStatus = up(1), 328 lmpNbrRowStatus = createAndGo(4) 329 } 331 Then, the control channels must be set up. These are created in 332 the lmpControlChannelTable. 334 In lmpControlChannelTable: 335 { 336 lmpCcId = 1, 337 lmpCcUnderlyingIfIndex = 1, 338 lmCcIsIf = false(1), 339 lmpCcAuthentication = false(1), 340 lmpCcConfigRetransmitInterval = 10, 341 lmpCcHelloInterval = 15, 342 lmpCcHelloIntervalMin = 15, 343 lmpCcHelloIntervalMax = 1000, 344 lmpCcHelloDeadInterval = 45, 345 lmpCcHelloDeadIntervalMin = 45, 346 lmpCcHelloDeadIntervalMax = 1000, 347 lmpCcAdminStatus = up(1), 348 lmpCcRowStatus = createAndGo(4) 349 } 351 { 352 lmpCcId = 2, 353 lmpCcUnderlyingIfIndex = 2, 354 lmCcIsIf = false(1), 355 lmpCcAuthentication = false(1), 356 lmpCcConfigRetransmitInterval = 10, 357 lmpCcHelloInterval = 15, 358 lmpCcHelloIntervalMin = 15, 359 lmpCcHelloIntervalMax = 1000, 360 lmpCcHelloDeadInterval = 45, 361 lmpCcHelloDeadIntervalMin = 45, 362 lmpCcHelloDeadIntervalMax = 1000, 363 lmpCcAdminStatus = up(1), 364 lmpCcRowStatus = createAndGo(4) 365 } 367 Next, the three data-bearing links are created. For each data- 368 bearing link, an ifEntry with the same ifIndex needs to be created 369 beforehand. 371 In lmpDataBearingLinkTable: 372 { 373 ifIndex = 41, 374 lmpDataBearingLinkNumberingType = unnumbered(1), 375 lmpDataBearingLinkRemoteIfId = 47, 376 lmpDataBearingLinkRowStatus = createAndGo(4) 377 } 379 { 380 ifIndex = 43, 381 lmpDataBearingLinkNumberingType = unnumbered(1), 382 lmpDataBearingLinkRemoteIfId = 42, 383 lmpDataBearingLinkRowStatus = createAndGo(4) 384 } 386 { 387 ifIndex = 44, 388 lmpDataBearingLinkNumberingType = unnumbered(1), 389 lmpDataBearingLinkRemoteIfId = 48, 390 lmpDataBearingLinkRowStatus = createAndGo(4) 391 } 393 Note that the data-bearing link type (lmpDataBearingLinkType) does 394 not need to be provisioned as it is automatically populated by the 395 node. The definition of the protection role (primary or 396 secondary) for the data-bearing links is stored in the 397 dataBearingChannelTable of the Link Bundling MIB [BUNDLE-MIB]. 399 Then, a TE link is created as an ifEntry with ifType teLink in 400 the ifTable. 402 Once the TE link is created in the ifTable, a TE link entry 403 is created in the LMP MIB to specify TE link information specific 404 to LMP. 406 In lmpTeLinkTable: 407 { 408 ifIndex = 20, 409 lmpTeLinkVerification = true(2), 410 lmpTeLinkFaultManagement = true(2), 411 lmpTeLinkDwdm = false(1), 412 lmpTeLinkBitRate = 100000, 413 lmpTeLinkWavelength = 0, 414 lmpTeLinkRowStatus = createAndGo(4) 415 } 417 The association between the data-bearing links and the TE links is 418 stored in the ifStackTable [IF-MIB]. 420 In parallel with the entry created in the lmpTeLinkTable, an entry 421 may be created in the teLinkTable of Link Bundling MIB 422 [BUNDLE-MIB]. 424 9. Application of the Interfaces Group to LMP 426 The Interfaces Group [IFMIB] defines generic managed objects for 427 managing interfaces. This memo contains the media-specific 428 extensions to the Interfaces Group for managing LMP control channels 429 that are modeled as interfaces. If the control channel as defined in 430 the lmpControlChannelTable is modeled as an ifEntry, then the 431 following definition applies. An lmpControlChannelTable entry is 432 designated as being represented as an Interfaces MIB ifEntry if the 433 lmpControlChannelEntry object lmpCcIsIf is set to true (2). In this 434 case, the control channel SHOULD be modeled as an ifEntry and 435 provide appropriate interface stacking as defined below. 437 This memo assumes the interpretation of the Interfaces Group to be 438 in accordance with [IFMIB] which states that the interfaces table 439 (ifTable) contains information on the managed resource's 440 interfaces and that each sub-layer below the internetwork layer of 441 a network interface is considered an interface. Since the LMP 442 interface only carries control traffic, it is considered to be below 443 the internetwork layer. Thus, the LMP interface may be represented 444 as an entry in the ifTable. The inter-relation of entries in the 445 ifTable is defined by Interfaces Stack Group defined in [IFMIB]. 447 When LMP control channels are modeled as interfaces, the interface 448 stack table must appear as follows for the LMP control channel 449 interfaces: 451 +----------------------------------------+ 452 | LMP-interface ifType = lmp(TBD) + 453 +----------------------------------------+ 454 | Underlying Layer... + 455 +----------------------------------------+ 457 In the above diagram, "Underlying Layer..." refers to the ifIndex 458 of any interface type over which the LMP interface will transmit 459 its traffic. Note that if the underlying layer provides multiple 460 access to its media (i.e.: Ethernet), then it is possible to stack 461 multiple LMP interfaces on top of this interface in parallel. 463 9.1. Support of the LMP Layer by ifTable 465 Some specific interpretations of ifTable for the LMP layer 466 follow. 468 Object Use for the LMP layer 470 ifIndex Each LMP interface may be represented by an ifEntry. 472 ifDescr Description of the LMP interface. 474 ifType The value that is allocated for LMP is TBD. 475 This number will be assigned by the IANA. 477 ifSpeed The total bandwidth in bits per second for use by 478 the LMP layer. 480 ifPhysAddress Unused. 482 ifAdminStatus This variable indicates the administrator's intent 483 as to whether LMP should be enabled, disabled, or 484 running in some diagnostic testing mode on this 485 interface. Also see [IFMIB]. 487 ifOperStatus This value reflects the actual or operational 488 status of LMP on this interface. 490 ifLastChange See [IFMIB]. 492 ifInOctets The number of received octets over the interface, 493 i.e., the number of octets received as LMP 494 packets. 496 ifOutOctets The number of transmitted octets over the 497 interface, i.e., the number of octets transmitted 498 as LMP packets. 500 ifInErrors The number of LMP packets dropped due to 501 uncorrectable errors. 503 ifInUnknownProtos 504 The number of received packets discarded during 505 packet header validation, including packets with 506 unrecognized label values. 508 ifOutErrors See [IFMIB]. 510 ifName Textual name (unique on this system) of the 511 interface or an octet string of zero length. 513 ifLinkUpDownTrapEnable 514 Default is disabled (2). 516 ifConnectorPresent 517 Set to false (2). 519 ifHighSpeed See [IFMIB]. 521 ifHCInOctets The 64-bit version of ifInOctets; supported if 522 required by the compliance statements in [IFMIB]. 524 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 525 required by the compliance statements in [IFMIB]. 527 ifAlias The non-volatile 'alias' name for the interface as 528 specified by a network manager. 530 ifCounterDiscontinuityTime 531 See [IFMIB]. 533 10. LMP MIB Definitions 535 LMP-MIB DEFINITIONS ::= BEGIN 537 IMPORTS 538 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 539 experimental, Unsigned32, Counter32, TimeTicks 540 FROM SNMPv2-SMI 542 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 543 FROM SNMPv2-CONF 545 TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, 546 TimeStamp 547 FROM SNMPv2-TC 549 InterfaceIndexOrZero, ifIndex 550 FROM IF-MIB 552 InetAddressType, InetAddress 553 FROM INET-ADDRESS-MIB 555 teLinkRemoteIpAddr, teLinkIncomingIfId 556 FROM LINK-BUNDLING-MIB; 558 lmpMIB MODULE-IDENTITY 559 LAST-UPDATED "200205291200Z" -- 29 May 2002 12:00:00 EST 560 ORGANIZATION "Common Control and Measurement Protocols (CCAMP) 561 Working Group" 562 CONTACT-INFO 563 " Martin Dubuc 564 Postal: Meriton Networks 565 3026 Solandt Road 566 Kanata, ON, CANADA K2K 2A5 567 Tel: +1-613-270-9279 x253 568 Email: martin.dubuc@meriton.com 570 Sudheer Dharanikota 571 Postal: Nayna Networks, Inc. 572 157 Topaz Street 573 Milipitas, CA 95035 574 Tel: +1-408-956-8000 x357 575 Email: sudheer@nayna.com 577 Thomas D. Nadeau 578 Postal: Cisco Systems, Inc. 579 300 Apollo Drive 580 Chelmsford, MA 01824 581 Tel: +1-978-244-3051 582 Email: tnadeau@cisco.com 584 Jonathan P. Lang 585 Postal: Calient Networks, Inc. 586 25 Castilian Drive 587 Goleta, CA 93117 588 Email: jplang@calient.net 590 Evan McGinnis 591 Postal: Calient Networks, Inc. 592 5853 Rue Ferrari 593 San Jose, CA 95138 594 Email: evan@calient.net" 596 DESCRIPTION 597 "This MIB contains managed object definitions for the 598 Link Management Protocol (LMP) as 599 defined in: Lang, J., Mitra, K., Drake, J., Kompella, K., 600 Rekhter, Y., Berger, L., Saha, D., 601 Basak, D., Sandick, H., Zinin, A., and 602 Rajagopalan, B., Link Management Protocol, 603 Internet Draft , 604 March 2002." 606 -- Revision history. 607 REVISION 608 "200205291200Z" -- 29 May 2002 12:00:00 EST 609 DESCRIPTION 610 "Addresses Last Call comments. 611 - Fixed syntax problems reported by SMICng and smilint. 612 - Added lmpRemoteCcIpAddrType and lmpRemoteCcIpAddr. 613 - Added lmpTeLinkPerfTable. 614 - Added lmpDataBearingLinkIpAddr. 615 - Added lmpTeLinkNotDegraded notification." 616 REVISION 617 "200202261200Z" -- 26 February 2002 12:00:00 EST 618 DESCRIPTION 619 "- Used latest MIB boiler plate. 620 - Added lmpFullModuleCompliance conformance statement. 621 - Replaced IpAddress with InetAddress. 622 - Added lmpOperStatus. 623 - Added lmpCcHelloIntervalNegotiated and 624 lmpCcHelloDeadIntervalNegotiated. 625 - Converted all 64-bit counters to 32-bit counters. 626 - Added counters for all LMP message types. 627 - Added counters to monitor data-bearing link tests. 628 - Reintroduced lmpNbrRetransmitTimeout. 629 - Added lmpDataBearingLinkNumberingType and 630 lmpDataBearingLinkRemoteIpAddress. 631 - Split data-bearing link operational status into active and 632 passive operational status. 633 - Updated description of all row status and storage type objects. 634 - Updated references." 635 REVISION 636 "200110211200Z" -- 21 October 2001 12:00:00 EST 637 DESCRIPTION 638 "- Minor syntax fixes. 639 - Added lmpCcId. Changed type of lmpRemoteCcId. 640 - Updated lmpTeLinkEncodingType. 641 - Removed lmpRemoteTeLinkType and lmpRemoteTeLinkId (their 642 content can be derived from LINK-BUNDLING-MIB). 643 - Added lmpCcLastChange, lmpCcCounterDiscontinuityTime and 644 lmpDataBearingLinkCounterDiscontinuityTime. 645 - Moved lmpTeLinkBitRate and lmpTeLinkWavelength to 646 lmpLinkVerificationTable. 647 - Updated lmpDataBearingLinkOperStatus. 648 - Modified performance counters to account for changes in 649 channel status message types. 650 - Changed indices for lmpTeLinkPropertyMismatch and 651 lmpDataBearingLinkPropertyMismatch notifications. 652 - Renamed lmpNbrLinkSumRetransmitInterval. Removed 653 lmpNbrRetransmitTimeout. 654 - Added lmpCcUnderlyingIfId, lmpCcIsIf and lmpCcSetupRole." 655 REVISION 656 "200105221200Z" -- 22 May 2001 12:00:00 EST 657 DESCRIPTION 658 "Updates based on IETF-50 feedback. Aligned with 659 upcoming version of LMP draft." 660 REVISION 661 "200102221200Z" -- 22 February 2001 12:00:00 EST 662 DESCRIPTION 663 "Updates based on MPLS mailing list feedback." 664 REVISION 665 "200101261200Z" -- 26 January 2001 12:00:00 EST 666 DESCRIPTION 667 "Initial draft version." 668 ::= { experimental 113 } 670 -- Textual Conventions 672 LmpInterval ::= TEXTUAL-CONVENTION 673 DISPLAY-HINT "d" 674 STATUS current 675 DESCRIPTION 676 "The interval delay in milliseconds." 677 SYNTAX Unsigned32 (1..65535) 679 LmpRetransmitInterval ::= TEXTUAL-CONVENTION 680 DISPLAY-HINT "d" 681 STATUS current 682 DESCRIPTION 683 "The retransmission interval delay in milliseconds." 684 SYNTAX Unsigned32 (1..4294967295) 686 -- Top level components of this MIB 688 -- Notifications 689 lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 } 690 -- Tables, Scalars 691 lmpObjects OBJECT IDENTIFIER ::= { lmpMIB 1 } 692 -- Conformance 693 lmpConformance OBJECT IDENTIFIER ::= { lmpMIB 2 } 695 lmpAdminStatus OBJECT-TYPE 696 SYNTAX INTEGER { up(1), down(2) } 697 MAX-ACCESS read-write 698 STATUS current 699 DESCRIPTION 700 "The desired operational status of LMP on the node." 702 DEFVAL { up } 703 ::= { lmpObjects 1 } 705 lmpOperStatus OBJECT-TYPE 706 SYNTAX INTEGER { up(1), down(2) } 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "The actual operational status of LMP on the node." 711 ::= { lmpObjects 2 } 713 -- LMP Neighbor Table 715 lmpNbrTable OBJECT-TYPE 716 SYNTAX SEQUENCE OF LmpNbrEntry 717 MAX-ACCESS not-accessible 718 STATUS current 719 DESCRIPTION 720 "This table specifies the neighbor node(s) to which control channels 721 may be established." 722 ::= { lmpObjects 3 } 724 lmpNbrEntry OBJECT-TYPE 725 SYNTAX LmpNbrEntry 726 MAX-ACCESS not-accessible 727 STATUS current 728 DESCRIPTION 729 "An entry in this table is created by a LMP-enabled device for 730 every pair of nodes that can establish control channels." 731 INDEX { lmpNbrNodeId } 732 ::= { lmpNbrTable 1 } 734 LmpNbrEntry ::= SEQUENCE { 735 lmpNbrNodeId InetAddress, 736 lmpNbrRetransmitInterval LmpRetransmitInterval, 737 lmpNbrRetransmitTimeout Unsigned32, 738 lmpNbrAdminStatus INTEGER, 739 lmpNbrOperStatus INTEGER, 740 lmpNbrRowStatus RowStatus, 741 lmpNbrStorageType StorageType 742 } 744 lmpNbrNodeId OBJECT-TYPE 745 SYNTAX InetAddress (SIZE(4)) 746 MAX-ACCESS not-accessible 747 STATUS current 748 DESCRIPTION 749 "This is a unique index for an entry in the LmpNbrTable. 750 This value represents the remote Node ID. The Node ID 751 address type must be IPv4." 752 ::= { lmpNbrEntry 1 } 754 lmpNbrRetransmitInterval OBJECT-TYPE 755 SYNTAX LmpRetransmitInterval 756 MAX-ACCESS read-create 757 STATUS current 758 DESCRIPTION 759 "This object specifies the interval that is used for the 760 retransmission of LinkSummary, BeginVerify, EndVerify, 761 TestStatusSuccess, TestStatusFailure, ChannelStatus and 762 ChannelStatusRequest messages." 763 REFERENCE 764 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 765 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 766 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 767 B. Rajagopalan, March 2002." 768 ::= { lmpNbrEntry 2 } 770 lmpNbrRetransmitTimeout OBJECT-TYPE 771 SYNTAX Unsigned32 772 MAX-ACCESS read-create 773 STATUS current 774 DESCRIPTION 775 "This object specifies the LinkSummary, BeginVerify, EndVerify, 776 TestStatusSuccess, TestStatusFailure, ChannelStatus and 777 ChannelStatusRequest retransmission timeout period. If the specified 778 timeout expires and the message has not yet been acknowledged, 779 a node can stop retransmitting the message. A value of 0 is used 780 to indicate that a node should never stop retransmission." 781 REFERENCE 782 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 783 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 784 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 785 B. Rajagopalan, March 2002." 786 DEFVAL { 0 } 787 ::= { lmpNbrEntry 7 } 789 lmpNbrAdminStatus OBJECT-TYPE 790 SYNTAX INTEGER { up(1), down(2) } 791 MAX-ACCESS read-create 792 STATUS current 793 DESCRIPTION 794 "The desired operational status of LMP to this remote node." 795 ::= { lmpNbrEntry 3 } 797 lmpNbrOperStatus OBJECT-TYPE 798 SYNTAX INTEGER { up(1), down(2) } 799 MAX-ACCESS read-only 800 STATUS current 801 DESCRIPTION 802 "The actual operational status of LMP to this remote node." 803 ::= { lmpNbrEntry 4 } 805 lmpNbrRowStatus OBJECT-TYPE 806 SYNTAX RowStatus 807 MAX-ACCESS read-create 808 STATUS current 809 DESCRIPTION 810 "This variable is used to create, modify, and/or 811 delete a row in this table. All read-create objects 812 can only be changed when lmpNbrRowStatus is active." 813 ::= { lmpNbrEntry 5 } 815 lmpNbrStorageType OBJECT-TYPE 816 SYNTAX StorageType 817 MAX-ACCESS read-create 818 STATUS current 819 DESCRIPTION 820 "The storage type for this conceptual row in the 821 lmpNbrTable. Conceptual rows having the value 822 'permanent' need not allow write-access to any 823 columnar object in the row." 824 ::= { lmpNbrEntry 6 } 826 -- End of lmpNbrTable 828 lmpCcHelloIntervalDefault OBJECT-TYPE 829 SYNTAX LmpInterval 830 MAX-ACCESS read-write 831 STATUS current 832 DESCRIPTION 833 "This object specifies the default value for the HelloInterval 834 parameter used in the Hello protocol keep-alive phase. It 835 indicates how frequently LMP Hello messages will be sent. It 836 is used a the default value for lmpCcHelloInterval." 837 REFERENCE 838 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 839 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 840 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 841 B. Rajagopalan, March 2002." 842 ::= { lmpObjects 4 } 844 lmpCcHelloIntervalDefaultMin OBJECT-TYPE 845 SYNTAX LmpInterval 846 MAX-ACCESS read-write 847 STATUS current 848 DESCRIPTION 849 "This object specifies the default minimum value for the 850 HelloInterval parameter. It is used as a default value 851 for lmpCcHelloIntervalMin." 852 ::= { lmpObjects 5 } 854 lmpCcHelloIntervalDefaultMax OBJECT-TYPE 855 SYNTAX LmpInterval 856 MAX-ACCESS read-write 857 STATUS current 858 DESCRIPTION 859 "This object specifies the default maximum value for the 860 HelloInterval parameter. It is used as a default value 861 for lmpCcHelloIntervalMax." 862 ::= { lmpObjects 6 } 864 lmpCcHelloDeadIntervalDefault OBJECT-TYPE 865 SYNTAX LmpInterval 866 MAX-ACCESS read-write 867 STATUS current 868 DESCRIPTION 869 "This object specifies the default HelloDeadInterval parameter to 870 use in the Hello protocol keep-alive phase. It indicates how long 871 a device should wait before declaring the control channel dead. 872 The HelloDeadInterval parameter should be at least three times the 873 value of HelloInterval. It is used as a default value for 874 lmpCcHelloDeadInterval." 875 REFERENCE 876 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 877 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 878 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 879 B. Rajagopalan, March 2002." 880 ::= { lmpObjects 7 } 882 lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE 883 SYNTAX LmpInterval 884 MAX-ACCESS read-write 885 STATUS current 886 DESCRIPTION 887 "This object specifies the default minimum value for the 888 HelloDeadInterval parameter. It is used as a default value 889 for lmpCcHelloDeadIntervalMin." 890 ::= { lmpObjects 8 } 892 lmpCcHelloDeadIntervalDefaultMax OBJECT-TYPE 893 SYNTAX LmpInterval 894 MAX-ACCESS read-write 895 STATUS current 896 DESCRIPTION 897 "This object specifies the default maximum value for the 898 HelloDeadInterval parameter. It is used as a default value 899 for lmpCcHelloDeadIntervalMax." 900 ::= { lmpObjects 9 } 902 -- LMP Control Channel Table 904 lmpControlChannelTable OBJECT-TYPE 905 SYNTAX SEQUENCE OF LmpControlChannelEntry 906 MAX-ACCESS not-accessible 907 STATUS current 908 DESCRIPTION 909 "This table specifies LMP control channel information." 910 ::= { lmpObjects 10 } 912 lmpControlChannelEntry OBJECT-TYPE 913 SYNTAX LmpControlChannelEntry 914 MAX-ACCESS not-accessible 915 STATUS current 916 DESCRIPTION 917 "An entry in this table is created by a LMP-enabled device for 918 every control channel. Whenever a new entry is created with lmpCcIsIf 919 set to true(2), then a corresponding entry is created in ifTable as 920 well (see RFC 2863)." 921 INDEX { lmpCcId } 922 ::= { lmpControlChannelTable 1 } 924 LmpControlChannelEntry ::= SEQUENCE { 925 lmpCcId Unsigned32, 926 lmpCcUnderlyingIfIndex InterfaceIndexOrZero, 927 lmpCcIsIf TruthValue, 928 lmpCcNbrNodeId InetAddress, 929 lmpRemoteCcId Unsigned32, 930 lmpRemoteCcIpAddrType InetAddressType, 931 lmpRemoteCcIpAddr InetAddress, 932 lmpCcSetupRole INTEGER, 933 lmpCcAuthentication TruthValue, 934 lmpCcConfigRetransmitInterval LmpRetransmitInterval, 935 lmpCcConfigRetransmitTimeout Unsigned32, 936 lmpCcHelloInterval LmpInterval, 937 lmpCcHelloIntervalMin LmpInterval, 938 lmpCcHelloIntervalMax LmpInterval, 939 lmpCcHelloIntervalNegotiated LmpInterval, 940 lmpCcHelloDeadInterval LmpInterval, 941 lmpCcHelloDeadIntervalMin LmpInterval, 942 lmpCcHelloDeadIntervalMax LmpInterval, 943 lmpCcHelloDeadIntervalNegotiated LmpInterval, 944 lmpCcLastChange TimeTicks, 945 lmpCcAdminStatus INTEGER, 946 lmpCcOperStatus INTEGER, 947 lmpCcRowStatus RowStatus, 948 lmpCcStorageType StorageType 949 } 951 lmpCcId OBJECT-TYPE 952 SYNTAX Unsigned32 953 MAX-ACCESS not-accessible 954 STATUS current 955 DESCRIPTION 956 "This value represents the local control channel identifier." 957 ::= { lmpControlChannelEntry 1 } 959 lmpCcUnderlyingIfIndex OBJECT-TYPE 960 SYNTAX InterfaceIndexOrZero 961 MAX-ACCESS read-create 962 STATUS current 963 DESCRIPTION 964 "This value represents the underlying interface index, i.e. the 965 interface index of the interface over which the LMP interface 966 will transmit its traffic. If set to 0, then the control channel 967 is not associated with any underlying interface. If the control 968 channel is not associated with an underlying interface, the control 969 channel's operational status must not be up(1), nor should the 970 control channel forward or receive traffic." 971 ::= { lmpControlChannelEntry 2 } 973 lmpCcIsIf OBJECT-TYPE 974 SYNTAX TruthValue 975 MAX-ACCESS read-create 976 STATUS current 977 DESCRIPTION 978 "Denotes whether or not this control channel corresponds to 979 an interface represented in the interfaces group table." 980 ::= { lmpControlChannelEntry 3 } 982 lmpCcNbrNodeId OBJECT-TYPE 983 SYNTAX InetAddress (SIZE(4)) 984 MAX-ACCESS read-create 985 STATUS current 986 DESCRIPTION 987 "This is the Node ID of the control channel remote node. 988 This value is either configured or gets created by the node 989 when a Config message is received or when an outgoing Config 990 message is acknowledged by the remote node. The Node ID 991 address type must be IPv4." 992 ::= { lmpControlChannelEntry 4 } 994 lmpRemoteCcId OBJECT-TYPE 995 SYNTAX Unsigned32 996 MAX-ACCESS read-only 997 STATUS current 998 DESCRIPTION 999 "This value represents the remote control channel identifier. It is 1000 determined during the negotiation phase. A value 1001 of zero means that the remote control channel identifier has not 1002 yet been learnt." 1003 ::= { lmpControlChannelEntry 5 } 1005 lmpRemoteCcIpAddrType OBJECT-TYPE 1006 SYNTAX InetAddressType 1007 MAX-ACCESS read-create 1008 STATUS current 1009 DESCRIPTION 1010 "This value represents the remote control channel IP address type. 1011 In point-to-point configuration, this value can be set to 1012 unknown(0)." 1013 ::= { lmpControlChannelEntry 6 } 1015 lmpRemoteCcIpAddr OBJECT-TYPE 1016 SYNTAX InetAddress 1017 MAX-ACCESS read-create 1018 STATUS current 1019 DESCRIPTION 1020 "This value represents the remote control channel IP address for 1021 non point-to-point configuration. For point-to-point configuration, 1022 this value can be set to null." 1023 ::= { lmpControlChannelEntry 7 } 1025 lmpCcSetupRole OBJECT-TYPE 1026 SYNTAX INTEGER { active(1), passive(2) } 1027 MAX-ACCESS read-create 1028 STATUS current 1029 DESCRIPTION 1030 "The role that this node should take during establishment of this 1031 control channel. An active node will initiate establishment. A 1032 passive node will wait for the remote node to initiate. A pair 1033 of nodes that both take the passive role will never establish 1034 communications." 1036 DEFVAL { active } 1037 ::= { lmpControlChannelEntry 8 } 1039 lmpCcAuthentication OBJECT-TYPE 1040 SYNTAX TruthValue 1041 MAX-ACCESS read-create 1042 STATUS current 1043 DESCRIPTION 1044 "This object indicates whether the control channel should use 1045 authentication." 1046 REFERENCE 1047 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 1048 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1049 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1050 B. Rajagopalan, March 2002." 1051 ::= { lmpControlChannelEntry 9 } 1053 lmpCcConfigRetransmitInterval OBJECT-TYPE 1054 SYNTAX LmpRetransmitInterval 1055 MAX-ACCESS read-create 1056 STATUS current 1057 DESCRIPTION 1058 "This object specifies the interval that is used for the 1059 retransmission of Config messages during the parameter 1060 negotiation phase." 1061 REFERENCE 1062 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 1063 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1064 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1065 B. Rajagopalan, March 2002." 1066 ::= { lmpControlChannelEntry 10 } 1068 lmpCcConfigRetransmitTimeout OBJECT-TYPE 1069 SYNTAX Unsigned32 1070 MAX-ACCESS read-create 1071 STATUS current 1072 DESCRIPTION 1073 "This object specifies the Config retransmission timeout 1074 period. If the specified timeout expires and no Config, 1075 ConfigAck or ConfigNack message has been received, a node 1076 can stop retransmitting Config messages on the control 1077 channel. A value of 0 is used to indicate that a node should 1078 never stop retransmission. This parameter (if non-zero) 1079 should be greater than lmpCcConfigRetransmitInterval." 1080 REFERENCE 1081 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 1082 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1083 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1084 B. Rajagopalan, March 2002." 1085 DEFVAL { 0 } 1086 ::= { lmpControlChannelEntry 11 } 1088 lmpCcHelloInterval OBJECT-TYPE 1089 SYNTAX LmpInterval 1090 MAX-ACCESS read-create 1091 STATUS current 1092 DESCRIPTION 1093 "This object specifies the value of the HelloInterval 1094 parameter. The default value for this object should be 1095 set to lmpCcHelloIntervalDefault." 1096 ::= { lmpControlChannelEntry 12 } 1098 lmpCcHelloIntervalMin OBJECT-TYPE 1099 SYNTAX LmpInterval 1100 MAX-ACCESS read-create 1101 STATUS current 1102 DESCRIPTION 1103 "This object specifies the minimum value for the 1104 HelloInterval parameter. The default value for this 1105 object should be set to lmpCcHelloIntervalMinDefault." 1106 ::= { lmpControlChannelEntry 13 } 1108 lmpCcHelloIntervalMax OBJECT-TYPE 1109 SYNTAX LmpInterval 1110 MAX-ACCESS read-create 1111 STATUS current 1112 DESCRIPTION 1113 "This object specifies the maximum value for the 1114 HelloInterval parameter. The default value for this 1115 object should be set to lmpCcHelloIntervalMaxDefault." 1116 ::= { lmpControlChannelEntry 14 } 1118 lmpCcHelloIntervalNegotiated OBJECT-TYPE 1119 SYNTAX LmpInterval 1120 MAX-ACCESS read-only 1121 STATUS current 1122 DESCRIPTION 1123 "Once the control channel is active, this object represents 1124 the negotiated HelloInterval value." 1125 ::= { lmpControlChannelEntry 15 } 1127 lmpCcHelloDeadInterval OBJECT-TYPE 1128 SYNTAX LmpInterval 1129 MAX-ACCESS read-create 1130 STATUS current 1131 DESCRIPTION 1132 "This object specifies the value of the HelloDeadInterval 1133 parameter. The default value for this object should be 1134 set to lmpCcHelloDeadIntervalDefault." 1135 ::= { lmpControlChannelEntry 16 } 1137 lmpCcHelloDeadIntervalMin OBJECT-TYPE 1138 SYNTAX LmpInterval 1139 MAX-ACCESS read-create 1140 STATUS current 1141 DESCRIPTION 1142 "This object specifies the minimum value for the 1143 HelloDeadInterval parameter. The default value for this 1144 object should be set to lmpCcHelloDeadIntervalMinDefault." 1145 ::= { lmpControlChannelEntry 17 } 1147 lmpCcHelloDeadIntervalMax OBJECT-TYPE 1148 SYNTAX LmpInterval 1149 MAX-ACCESS read-create 1150 STATUS current 1151 DESCRIPTION 1152 "This object specifies the maximum value for the 1153 HelloDeadInterval parameter. The default value for this 1154 object should be set to lmpCcHelloIntervalMaxDefault." 1155 ::= { lmpControlChannelEntry 18 } 1157 lmpCcHelloDeadIntervalNegotiated OBJECT-TYPE 1158 SYNTAX LmpInterval 1159 MAX-ACCESS read-only 1160 STATUS current 1161 DESCRIPTION 1162 "Once the control channel is active, this object represents 1163 the negotiated HelloDeadInterval value." 1164 ::= { lmpControlChannelEntry 19 } 1166 lmpCcLastChange OBJECT-TYPE 1167 SYNTAX TimeTicks 1168 MAX-ACCESS read-only 1169 STATUS current 1170 DESCRIPTION 1171 "The value of sysUpTime at the time the control channel entered 1172 its current operational state. If the current state was 1173 entered prior to the last re-initialization of the local 1174 network management subsystem, then this object contains a 1175 zero value." 1176 ::= { lmpControlChannelEntry 20 } 1178 lmpCcAdminStatus OBJECT-TYPE 1179 SYNTAX INTEGER { up(1), down(2) } 1180 MAX-ACCESS read-create 1181 STATUS current 1182 DESCRIPTION 1183 "The desired operational status of this control channel." 1184 ::= { lmpControlChannelEntry 21 } 1186 lmpCcOperStatus OBJECT-TYPE 1187 SYNTAX INTEGER { 1188 up(1), 1189 down(2), 1190 configSnd(3), 1191 configRcv(4), 1192 active(5), 1193 goingDown(6) 1194 } 1195 MAX-ACCESS read-only 1196 STATUS current 1197 DESCRIPTION 1198 "The actual operational status of this control channel 1199 interface." 1200 ::= { lmpControlChannelEntry 22 } 1202 lmpCcRowStatus OBJECT-TYPE 1203 SYNTAX RowStatus 1204 MAX-ACCESS read-create 1205 STATUS current 1206 DESCRIPTION 1207 "This variable is used to create, modify, and/or 1208 delete a row in this table. All read-create objects 1209 can only be changed when lmpCcRowStatus is active." 1210 ::= { lmpControlChannelEntry 23 } 1212 lmpCcStorageType OBJECT-TYPE 1213 SYNTAX StorageType 1214 MAX-ACCESS read-create 1215 STATUS current 1216 DESCRIPTION 1217 "The storage type for this conceptual row in the 1218 lmpControlChannelTable. Conceptual rows having the value 1219 'permanent' need not allow write-access to any 1220 columnar object in the row." 1221 ::= { lmpControlChannelEntry 24 } 1223 -- End of lmpControlChannelTable 1225 -- LMP Control Channel Performance Table 1226 lmpControlChannelPerfTable OBJECT-TYPE 1227 SYNTAX SEQUENCE OF LmpControlChannelPerfEntry 1228 MAX-ACCESS not-accessible 1229 STATUS current 1230 DESCRIPTION 1231 "This table specifies LMP control channel performance counters." 1232 ::= { lmpObjects 11 } 1234 lmpControlChannelPerfEntry OBJECT-TYPE 1235 SYNTAX LmpControlChannelPerfEntry 1236 MAX-ACCESS not-accessible 1237 STATUS current 1238 DESCRIPTION 1239 "An entry in this table is created by a LMP-enabled device for 1240 every control channel." 1241 AUGMENTS { lmpControlChannelEntry } 1242 ::= { lmpControlChannelPerfTable 1 } 1244 LmpControlChannelPerfEntry ::= SEQUENCE { 1245 lmpCcInOctets Counter32, 1246 lmpCcInDiscards Counter32, 1247 lmpCcInErrors Counter32, 1248 lmpCcOutOctets Counter32, 1249 lmpCcOutDiscards Counter32, 1250 lmpCcOutErrors Counter32, 1251 lmpCcConfigReceived Counter32, 1252 lmpCcConfigSent Counter32, 1253 lmpCcConfigRetransmit Counter32, 1254 lmpCcConfigAckReceived Counter32, 1255 lmpCcConfigAckSent Counter32, 1256 lmpCcConfigNackReceived Counter32, 1257 lmpCcConfigNackSent Counter32, 1258 lmpCcHelloReceived Counter32, 1259 lmpCcHelloSent Counter32, 1260 lmpCcBeginVerifyReceived Counter32, 1261 lmpCcBeginVerifySent Counter32, 1262 lmpCcBeginVerifyRetransmit Counter32, 1263 lmpCcBeginVerifyAckReceived Counter32, 1264 lmpCcBeginVerifyAckSent Counter32, 1265 lmpCcBeginVerifyNackReceived Counter32, 1266 lmpCcBeginVerifyNackSent Counter32, 1267 lmpCcEndVerifyReceived Counter32, 1268 lmpCcEndVerifySent Counter32, 1269 lmpCcEndVerifyRetransmit Counter32, 1270 lmpCcEndVerifyAckReceived Counter32, 1271 lmpCcEndVerifyAckSent Counter32, 1272 lmpCcTestStatusSuccessReceived Counter32, 1273 lmpCcTestStatusSuccessSent Counter32, 1274 lmpCcTestStatusSuccessRetransmit Counter32, 1275 lmpCcTestStatusFailureReceived Counter32, 1276 lmpCcTestStatusFailureSent Counter32, 1277 lmpCcTestStatusFailureRetransmit Counter32, 1278 lmpCcTestStatusAckReceived Counter32, 1279 lmpCcTestStatusAckSent Counter32, 1280 lmpCcLinkSummaryReceived Counter32, 1281 lmpCcLinkSummarySent Counter32, 1282 lmpCcLinkSummaryRetransmit Counter32, 1283 lmpCcLinkSummaryAckReceived Counter32, 1284 lmpCcLinkSummaryAckSent Counter32, 1285 lmpCcLinkSummaryNackReceived Counter32, 1286 lmpCcLinkSummaryNackSent Counter32, 1287 lmpCcChannelStatusReceived Counter32, 1288 lmpCcChannelStatusSent Counter32, 1289 lmpCcChannelStatusRetransmit Counter32, 1290 lmpCcChannelStatusAckReceived Counter32, 1291 lmpCcChannelStatusAckSent Counter32, 1292 lmpCcChannelStatusRequestReceived Counter32, 1293 lmpCcChannelStatusRequestSent Counter32, 1294 lmpCcChannelStatusRequestRetransmit Counter32, 1295 lmpCcChannelStatusResponseSent Counter32, 1296 lmpCcChannelStatusResponseReceived Counter32, 1297 lmpCcCounterDiscontinuityTime TimeStamp 1298 } 1300 lmpCcInOctets OBJECT-TYPE 1301 SYNTAX Counter32 1302 MAX-ACCESS read-only 1303 STATUS current 1304 DESCRIPTION 1305 "The total number of LMP message octets received on the 1306 control channel." 1307 ::= { lmpControlChannelPerfEntry 1 } 1309 lmpCcInDiscards OBJECT-TYPE 1310 SYNTAX Counter32 1311 MAX-ACCESS read-only 1312 STATUS current 1313 DESCRIPTION 1314 "The number of inbound packets which were chosen to be 1315 discarded even though no errors had been detected. One 1316 possible reason for discarding such a packet could be to 1317 free up buffer space." 1318 ::= { lmpControlChannelPerfEntry 2 } 1320 lmpCcInErrors OBJECT-TYPE 1321 SYNTAX Counter32 1322 MAX-ACCESS read-only 1323 STATUS current 1324 DESCRIPTION 1325 "The number of inbound packets that contained errors 1326 preventing them from being processed by LMP." 1327 ::= { lmpControlChannelPerfEntry 3 } 1329 lmpCcOutOctets OBJECT-TYPE 1330 SYNTAX Counter32 1331 MAX-ACCESS read-only 1332 STATUS current 1333 DESCRIPTION 1334 "The total number of LMP message octets transmitted out of 1335 the control channel." 1336 ::= { lmpControlChannelPerfEntry 4 } 1338 lmpCcOutDiscards OBJECT-TYPE 1339 SYNTAX Counter32 1340 MAX-ACCESS read-only 1341 STATUS current 1342 DESCRIPTION 1343 "The number of outbound packets which were chosen to be 1344 discarded even though no errors had been detected to prevent 1345 their being transmitted. One possible reason for discarding 1346 such a packet could be to free up buffer space." 1347 ::= { lmpControlChannelPerfEntry 5 } 1349 lmpCcOutErrors OBJECT-TYPE 1350 SYNTAX Counter32 1351 MAX-ACCESS read-only 1352 STATUS current 1353 DESCRIPTION 1354 "The number of outbound packets that could not be 1355 transmitted because of errors." 1356 ::= { lmpControlChannelPerfEntry 6 } 1358 lmpCcConfigReceived OBJECT-TYPE 1359 SYNTAX Counter32 1360 MAX-ACCESS read-only 1361 STATUS current 1362 DESCRIPTION 1363 "This object counts the number of Config messages that have 1364 been received on this control channel." 1365 ::= { lmpControlChannelPerfEntry 7 } 1367 lmpCcConfigSent OBJECT-TYPE 1368 SYNTAX Counter32 1369 MAX-ACCESS read-only 1370 STATUS current 1371 DESCRIPTION 1372 "This object counts the number of Config messages that have 1373 been sent on this control channel." 1374 ::= { lmpControlChannelPerfEntry 8 } 1376 lmpCcConfigRetransmit OBJECT-TYPE 1377 SYNTAX Counter32 1378 MAX-ACCESS read-only 1379 STATUS current 1380 DESCRIPTION 1381 "This object counts the number of Config messages that 1382 have been retransmitted over this control channel." 1383 ::= { lmpControlChannelPerfEntry 9 } 1385 lmpCcConfigAckReceived OBJECT-TYPE 1386 SYNTAX Counter32 1387 MAX-ACCESS read-only 1388 STATUS current 1389 DESCRIPTION 1390 "This object counts the number of ConfigAck messages that have 1391 been received on this control channel." 1392 ::= { lmpControlChannelPerfEntry 10 } 1394 lmpCcConfigAckSent OBJECT-TYPE 1395 SYNTAX Counter32 1396 MAX-ACCESS read-only 1397 STATUS current 1398 DESCRIPTION 1399 "This object counts the number of ConfigAck messages that have 1400 been sent on this control channel." 1401 ::= { lmpControlChannelPerfEntry 11 } 1403 lmpCcConfigNackReceived OBJECT-TYPE 1404 SYNTAX Counter32 1405 MAX-ACCESS read-only 1406 STATUS current 1407 DESCRIPTION 1408 "This object counts the number of ConfigNack messages that have 1409 been received on this control channel." 1410 ::= { lmpControlChannelPerfEntry 12 } 1412 lmpCcConfigNackSent OBJECT-TYPE 1413 SYNTAX Counter32 1414 MAX-ACCESS read-only 1415 STATUS current 1416 DESCRIPTION 1417 "This object counts the number of ConfigNack messages that have 1418 been sent on this control channel." 1419 ::= { lmpControlChannelPerfEntry 13 } 1421 lmpCcHelloReceived OBJECT-TYPE 1422 SYNTAX Counter32 1423 MAX-ACCESS read-only 1424 STATUS current 1425 DESCRIPTION 1426 "This object counts the number of Hello messages that have 1427 been received on this control channel." 1428 ::= { lmpControlChannelPerfEntry 14 } 1430 lmpCcHelloSent OBJECT-TYPE 1431 SYNTAX Counter32 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "This object counts the number of Hello messages that have 1436 been sent on this control channel." 1437 ::= { lmpControlChannelPerfEntry 15 } 1439 lmpCcBeginVerifyReceived OBJECT-TYPE 1440 SYNTAX Counter32 1441 MAX-ACCESS read-only 1442 STATUS current 1443 DESCRIPTION 1444 "This object counts the number of BeginVerify messages that have 1445 been received on this control channel." 1446 ::= { lmpControlChannelPerfEntry 16 } 1448 lmpCcBeginVerifySent OBJECT-TYPE 1449 SYNTAX Counter32 1450 MAX-ACCESS read-only 1451 STATUS current 1452 DESCRIPTION 1453 "This object counts the number of BeginVerify messages that have 1454 been sent on this control channel." 1455 ::= { lmpControlChannelPerfEntry 17 } 1457 lmpCcBeginVerifyRetransmit OBJECT-TYPE 1458 SYNTAX Counter32 1459 MAX-ACCESS read-only 1460 STATUS current 1461 DESCRIPTION 1462 "This object counts the number of BeginVerify messages that 1463 have been retransmitted over this control channel." 1464 ::= { lmpControlChannelPerfEntry 18 } 1466 lmpCcBeginVerifyAckReceived OBJECT-TYPE 1467 SYNTAX Counter32 1468 MAX-ACCESS read-only 1469 STATUS current 1470 DESCRIPTION 1471 "This object counts the number of BeginVerifyAck messages that have 1472 been received on this control channel." 1473 ::= { lmpControlChannelPerfEntry 19 } 1475 lmpCcBeginVerifyAckSent OBJECT-TYPE 1476 SYNTAX Counter32 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "This object counts the number of BeginVerifyAck messages that have 1481 been sent on this control channel." 1482 ::= { lmpControlChannelPerfEntry 20 } 1484 lmpCcBeginVerifyNackReceived OBJECT-TYPE 1485 SYNTAX Counter32 1486 MAX-ACCESS read-only 1487 STATUS current 1488 DESCRIPTION 1489 "This object counts the number of BeginVerifyNack messages that have 1490 been received on this control channel." 1491 ::= { lmpControlChannelPerfEntry 21 } 1493 lmpCcBeginVerifyNackSent OBJECT-TYPE 1494 SYNTAX Counter32 1495 MAX-ACCESS read-only 1496 STATUS current 1497 DESCRIPTION 1498 "This object counts the number of BeginVerifyNack messages that have 1499 been sent on this control channel." 1500 ::= { lmpControlChannelPerfEntry 22 } 1502 lmpCcEndVerifyReceived OBJECT-TYPE 1503 SYNTAX Counter32 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "This object counts the number of EndVerify messages that have 1508 been received on this control channel." 1509 ::= { lmpControlChannelPerfEntry 23 } 1511 lmpCcEndVerifySent OBJECT-TYPE 1512 SYNTAX Counter32 1513 MAX-ACCESS read-only 1514 STATUS current 1515 DESCRIPTION 1516 "This object counts the number of EndVerify messages that have 1517 been sent on this control channel." 1518 ::= { lmpControlChannelPerfEntry 24 } 1520 lmpCcEndVerifyRetransmit OBJECT-TYPE 1521 SYNTAX Counter32 1522 MAX-ACCESS read-only 1523 STATUS current 1524 DESCRIPTION 1525 "This object counts the number of EndVerify messages that 1526 have been retransmitted over this control channel." 1527 ::= { lmpControlChannelPerfEntry 25 } 1529 lmpCcEndVerifyAckReceived OBJECT-TYPE 1530 SYNTAX Counter32 1531 MAX-ACCESS read-only 1532 STATUS current 1533 DESCRIPTION 1534 "This object counts the number of EndVerifyAck messages that have 1535 been received on this control channel." 1536 ::= { lmpControlChannelPerfEntry 26 } 1538 lmpCcEndVerifyAckSent OBJECT-TYPE 1539 SYNTAX Counter32 1540 MAX-ACCESS read-only 1541 STATUS current 1542 DESCRIPTION 1543 "This object counts the number of EndVerifyAck messages that have 1544 been sent on this control channel." 1545 ::= { lmpControlChannelPerfEntry 27 } 1547 lmpCcTestStatusSuccessReceived OBJECT-TYPE 1548 SYNTAX Counter32 1549 MAX-ACCESS read-only 1550 STATUS current 1551 DESCRIPTION 1552 "This object counts the number of TestStatusSuccess messages that have 1553 been received on this control channel." 1554 ::= { lmpControlChannelPerfEntry 28 } 1556 lmpCcTestStatusSuccessSent OBJECT-TYPE 1557 SYNTAX Counter32 1558 MAX-ACCESS read-only 1559 STATUS current 1560 DESCRIPTION 1561 "This object counts the number of TestStatusSuccess messages that have 1562 been sent on this control channel." 1563 ::= { lmpControlChannelPerfEntry 29 } 1565 lmpCcTestStatusSuccessRetransmit OBJECT-TYPE 1566 SYNTAX Counter32 1567 MAX-ACCESS read-only 1568 STATUS current 1569 DESCRIPTION 1570 "This object counts the number of TestStatusSuccess messages that 1571 have been retransmitted over this control channel." 1572 ::= { lmpControlChannelPerfEntry 30 } 1574 lmpCcTestStatusFailureReceived OBJECT-TYPE 1575 SYNTAX Counter32 1576 MAX-ACCESS read-only 1577 STATUS current 1578 DESCRIPTION 1579 "This object counts the number of TestStatusFailure messages that have 1580 been received on this control channel." 1581 ::= { lmpControlChannelPerfEntry 31 } 1583 lmpCcTestStatusFailureSent OBJECT-TYPE 1584 SYNTAX Counter32 1585 MAX-ACCESS read-only 1586 STATUS current 1587 DESCRIPTION 1588 "This object counts the number of TestStatusFailure messages that have 1589 been sent on this control channel." 1590 ::= { lmpControlChannelPerfEntry 32 } 1592 lmpCcTestStatusFailureRetransmit OBJECT-TYPE 1593 SYNTAX Counter32 1594 MAX-ACCESS read-only 1595 STATUS current 1596 DESCRIPTION 1597 "This object counts the number of TestStatusFailure messages that 1598 have been retransmitted over this control channel." 1599 ::= { lmpControlChannelPerfEntry 33 } 1601 lmpCcTestStatusAckReceived OBJECT-TYPE 1602 SYNTAX Counter32 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "This object counts the number of TestStatusAck messages that have 1607 been received on this control channel." 1608 ::= { lmpControlChannelPerfEntry 34 } 1610 lmpCcTestStatusAckSent OBJECT-TYPE 1611 SYNTAX Counter32 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "This object counts the number of TestStatusAck messages that have 1616 been sent on this control channel." 1617 ::= { lmpControlChannelPerfEntry 35 } 1619 lmpCcLinkSummaryReceived OBJECT-TYPE 1620 SYNTAX Counter32 1621 MAX-ACCESS read-only 1622 STATUS current 1623 DESCRIPTION 1624 "This object counts the number of LinkSummary messages that have 1625 been received on this control channel." 1626 ::= { lmpControlChannelPerfEntry 36 } 1628 lmpCcLinkSummarySent OBJECT-TYPE 1629 SYNTAX Counter32 1630 MAX-ACCESS read-only 1631 STATUS current 1632 DESCRIPTION 1633 "This object counts the number of LinkSummary messages that have 1634 been sent on this control channel." 1635 ::= { lmpControlChannelPerfEntry 37 } 1637 lmpCcLinkSummaryRetransmit OBJECT-TYPE 1638 SYNTAX Counter32 1639 MAX-ACCESS read-only 1640 STATUS current 1641 DESCRIPTION 1642 "This object counts the number of LinkSummary messages that 1643 have been retransmitted over this control channel." 1644 ::= { lmpControlChannelPerfEntry 38 } 1646 lmpCcLinkSummaryAckReceived OBJECT-TYPE 1647 SYNTAX Counter32 1648 MAX-ACCESS read-only 1649 STATUS current 1650 DESCRIPTION 1651 "This object counts the number of LinkSummaryAck messages that have 1652 been received on this control channel." 1653 ::= { lmpControlChannelPerfEntry 39 } 1655 lmpCcLinkSummaryAckSent OBJECT-TYPE 1656 SYNTAX Counter32 1657 MAX-ACCESS read-only 1658 STATUS current 1659 DESCRIPTION 1660 "This object counts the number of LinkSummaryAck messages that have 1661 been sent on this control channel." 1662 ::= { lmpControlChannelPerfEntry 40 } 1664 lmpCcLinkSummaryNackReceived OBJECT-TYPE 1665 SYNTAX Counter32 1666 MAX-ACCESS read-only 1667 STATUS current 1668 DESCRIPTION 1669 "This object counts the number of LinkSummaryNack messages that have 1670 been received on this control channel." 1671 ::= { lmpControlChannelPerfEntry 41 } 1673 lmpCcLinkSummaryNackSent OBJECT-TYPE 1674 SYNTAX Counter32 1675 MAX-ACCESS read-only 1676 STATUS current 1677 DESCRIPTION 1678 "This object counts the number of LinkSummaryNack messages that have 1679 been sent on this control channel." 1680 ::= { lmpControlChannelPerfEntry 42 } 1682 lmpCcChannelStatusReceived 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 received on this control channel." 1689 ::= { lmpControlChannelPerfEntry 43 } 1691 lmpCcChannelStatusSent OBJECT-TYPE 1692 SYNTAX Counter32 1693 MAX-ACCESS read-only 1694 STATUS current 1695 DESCRIPTION 1696 "This object counts the number of ChannelStatus messages that have 1697 been sent on this control channel." 1698 ::= { lmpControlChannelPerfEntry 44 } 1700 lmpCcChannelStatusRetransmit OBJECT-TYPE 1701 SYNTAX Counter32 1702 MAX-ACCESS read-only 1703 STATUS current 1704 DESCRIPTION 1705 "This object counts the number of ChannelStatus messages that have 1706 been retransmitted on this control channel." 1707 ::= { lmpControlChannelPerfEntry 45 } 1709 lmpCcChannelStatusAckReceived OBJECT-TYPE 1710 SYNTAX Counter32 1711 MAX-ACCESS read-only 1712 STATUS current 1713 DESCRIPTION 1714 "This object counts the number of ChannelStatusAck messages that have 1715 been received on this control channel." 1716 ::= { lmpControlChannelPerfEntry 46 } 1718 lmpCcChannelStatusAckSent OBJECT-TYPE 1719 SYNTAX Counter32 1720 MAX-ACCESS read-only 1721 STATUS current 1722 DESCRIPTION 1723 "This object counts the number of ChannelStatus messages that have 1724 been sent on this control channel." 1725 ::= { lmpControlChannelPerfEntry 47 } 1727 lmpCcChannelStatusRequestReceived OBJECT-TYPE 1728 SYNTAX Counter32 1729 MAX-ACCESS read-only 1730 STATUS current 1731 DESCRIPTION 1732 "This object counts the number of ChannelStatusRequest messages that 1733 have been received on this control channel." 1734 ::= { lmpControlChannelPerfEntry 48 } 1736 lmpCcChannelStatusRequestSent OBJECT-TYPE 1737 SYNTAX Counter32 1738 MAX-ACCESS read-only 1739 STATUS current 1740 DESCRIPTION 1741 "This object counts the number of ChannelStatusRequest messages that 1742 have been sent on this control channel." 1743 ::= { lmpControlChannelPerfEntry 49 } 1745 lmpCcChannelStatusRequestRetransmit OBJECT-TYPE 1746 SYNTAX Counter32 1747 MAX-ACCESS read-only 1748 STATUS current 1749 DESCRIPTION 1750 "This object counts the number of ChannelStatusRequest messages that 1751 have been retransmitted on this control channel." 1752 ::= { lmpControlChannelPerfEntry 50 } 1754 lmpCcChannelStatusResponseReceived OBJECT-TYPE 1755 SYNTAX Counter32 1756 MAX-ACCESS read-only 1757 STATUS current 1758 DESCRIPTION 1759 "This object counts the number of ChannelStatusResponse messages that 1760 have been received on this control channel." 1761 ::= { lmpControlChannelPerfEntry 51 } 1763 lmpCcChannelStatusResponseSent OBJECT-TYPE 1764 SYNTAX Counter32 1765 MAX-ACCESS read-only 1766 STATUS current 1767 DESCRIPTION 1768 "This object counts the number of ChannelStatusResponse messages that 1769 have been sent on this control channel." 1770 ::= { lmpControlChannelPerfEntry 52 } 1772 lmpCcCounterDiscontinuityTime OBJECT-TYPE 1773 SYNTAX TimeStamp 1774 MAX-ACCESS read-only 1775 STATUS current 1776 DESCRIPTION 1777 "The value of sysUpTime on the most recent occasion at which 1778 any one or more of this control channel's counters suffered a 1779 discontinuity. The relevant counters are the specific 1780 instances associated with this control channel of any Counter32 1781 object contained in the lmpControlChannelPerfTable. If 1782 no such discontinuities have occurred since the last re- 1783 initialization of the local management subsystem, then this 1784 object contains a zero value." 1785 ::= { lmpControlChannelPerfEntry 53 } 1787 -- End of lmpControlChannelPerfTable 1789 -- LMP TE Link Table 1791 lmpTeLinkTable OBJECT-TYPE 1792 SYNTAX SEQUENCE OF LmpTeLinkEntry 1793 MAX-ACCESS not-accessible 1794 STATUS current 1795 DESCRIPTION 1796 "This table contains a collection of TE link." 1797 ::= { lmpObjects 12 } 1799 lmpTeLinkEntry OBJECT-TYPE 1800 SYNTAX LmpTeLinkEntry 1801 MAX-ACCESS not-accessible 1802 STATUS current 1803 DESCRIPTION 1804 "An entry in this table exists for each ifEntry with an 1805 ifType of teLink(TBD), i.e. for every TE link. An ifEntry 1806 with an ifIndex must exist before the corresponding 1807 teLinkEntry is created. If a TE link entry in the ifTable is 1808 destroyed, then so is the corresponding entry in the 1809 teLinkTable. The administrative status value is controlled 1810 from the ifEntry. Setting the administrative status to 1811 testing prompts LMP to start link verification on the TE link. 1812 Information about the TE link that is not LMP specific is also 1813 contained in teLinkTable [BUNDLE-MIB]." 1814 INDEX { ifIndex } 1815 ::= { lmpTeLinkTable 1 } 1817 LmpTeLinkEntry ::= SEQUENCE { 1818 lmpTeLinkNbrNodeId InetAddress, 1819 lmpTeLinkVerification TruthValue, 1820 lmpTeLinkFaultManagement TruthValue, 1821 lmpTeLinkDwdm TruthValue, 1822 lmpTeLinkOperStatus INTEGER, 1823 lmpTeLinkRowStatus RowStatus, 1824 lmpTeLinkStorageType StorageType 1825 } 1827 lmpTeLinkNbrNodeId OBJECT-TYPE 1828 SYNTAX InetAddress (SIZE(4)) 1829 MAX-ACCESS read-create 1830 STATUS current 1831 DESCRIPTION 1832 "This is the Node ID of the TE link remote node. This value 1833 may be learned during control channel parameter negotiation 1834 phase (in the Config message). Node ID address type must 1835 be IPv4." 1836 ::= { lmpTeLinkEntry 1 } 1838 lmpTeLinkVerification OBJECT-TYPE 1839 SYNTAX TruthValue 1840 MAX-ACCESS read-create 1841 STATUS current 1842 DESCRIPTION 1843 "This object indicates if the extended LMP link verification 1844 procedure is enabled for this TE link." 1845 REFERENCE 1846 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 1847 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1848 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1849 B. Rajagopalan, March 2002." 1850 ::= { lmpTeLinkEntry 2 } 1852 lmpTeLinkFaultManagement OBJECT-TYPE 1853 SYNTAX TruthValue 1854 MAX-ACCESS read-create 1855 STATUS current 1856 DESCRIPTION 1857 "This object indicates if the extended LMP fault management 1858 procedure is enabled on this TE link." 1859 REFERENCE 1860 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 1861 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1862 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1863 B. Rajagopalan, March 2002." 1864 ::= { lmpTeLinkEntry 3 } 1866 lmpTeLinkDwdm OBJECT-TYPE 1867 SYNTAX TruthValue 1868 MAX-ACCESS read-create 1869 STATUS current 1870 DESCRIPTION 1871 "This object indicates if the extended LMP DWDM procedure 1872 is enabled on this TE link." 1873 REFERENCE 1874 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 1875 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1876 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1877 B. Rajagopalan, March 2002." 1878 ::= { lmpTeLinkEntry 4 } 1880 lmpTeLinkOperStatus OBJECT-TYPE 1881 SYNTAX INTEGER { up(1), down(2), testing(3), init(4), degraded(5) } 1882 MAX-ACCESS read-only 1883 STATUS current 1884 DESCRIPTION 1885 "The actual operational status of this TE link. The status 1886 is set to testing when the TE link is performing link 1887 verification. A degraded state indicates that there are 1888 no active control channel between the pair of nodes that 1889 form the endpoints of the TE link, but yet at least one 1890 data-bearing links on the TE link is allocated." 1891 ::= { lmpTeLinkEntry 5 } 1893 lmpTeLinkRowStatus OBJECT-TYPE 1894 SYNTAX RowStatus 1895 MAX-ACCESS read-create 1896 STATUS current 1897 DESCRIPTION 1898 "This variable is used to create, modify, and/or 1899 delete a row in this table. All read-create objects 1900 can only be changed when lmpTeLinkRowStatus is active." 1901 ::= { lmpTeLinkEntry 6 } 1903 lmpTeLinkStorageType OBJECT-TYPE 1904 SYNTAX StorageType 1905 MAX-ACCESS read-create 1906 STATUS current 1907 DESCRIPTION 1908 "The storage type for this conceptual row in the 1909 lmpTeLinkTable. Conceptual rows having the value 1910 'permanent' need not allow write-access to any 1911 columnar object in the row." 1912 ::= { lmpTeLinkEntry 7 } 1914 -- End of lmpTeLinkTable 1916 lmpLinkVerificationInterval OBJECT-TYPE 1917 SYNTAX Unsigned32 1918 MAX-ACCESS read-write 1919 STATUS current 1920 DESCRIPTION 1921 "This object indicates how often the link verification procedure 1922 is executed. The interval is in milliseconds." 1923 ::= { lmpObjects 13 } 1925 -- LMP Link Verification Table 1927 lmpLinkVerificationTable OBJECT-TYPE 1928 SYNTAX SEQUENCE OF LmpLinkVerificationEntry 1929 MAX-ACCESS not-accessible 1930 STATUS current 1931 DESCRIPTION 1932 "This table specifies TE link information associated with the 1933 LMP verification procedure." 1934 ::= { lmpObjects 14 } 1936 lmpLinkVerificationEntry OBJECT-TYPE 1937 SYNTAX LmpLinkVerificationEntry 1938 MAX-ACCESS not-accessible 1939 STATUS current 1940 DESCRIPTION 1941 "An entry in this table is created by a LMP-enabled device for 1942 every TE link that supports the LMP verification 1943 procedure." 1944 AUGMENTS { lmpTeLinkEntry } 1945 ::= { lmpLinkVerificationTable 1 } 1947 LmpLinkVerificationEntry ::= SEQUENCE { 1948 lmpVerifyInterval LmpInterval, 1949 lmpVerifyDeadInterval LmpInterval, 1950 lmpVerifyTransportMechanism BITS, 1951 lmpVerifyAllLinks INTEGER, 1952 lmpTeLinkBitRate Unsigned32, 1953 lmpTeLinkWavelength Unsigned32 1954 } 1956 lmpVerifyInterval OBJECT-TYPE 1957 SYNTAX LmpInterval 1958 MAX-ACCESS read-create 1959 STATUS current 1960 DESCRIPTION 1961 "This object specifies the VerifyInterval parameter used 1962 in the LMP link verification process. It indicates the interval 1963 at which the Test messages are sent." 1964 REFERENCE 1965 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 1966 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1967 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1968 B. Rajagopalan, March 2002." 1969 ::= { lmpLinkVerificationEntry 1 } 1971 lmpVerifyDeadInterval OBJECT-TYPE 1972 SYNTAX LmpInterval 1973 MAX-ACCESS read-create 1974 STATUS current 1975 DESCRIPTION 1976 "This object specifies the VerifyDeadInterval parameter used 1977 in the verification of the physical connectivity of data-bearing 1978 links. It specifies the observation period used to detect a Test 1979 message at the remote node." 1980 REFERENCE 1981 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 1982 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1983 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1984 B. Rajagopalan, March 2002." 1985 ::= { lmpLinkVerificationEntry 2 } 1987 lmpVerifyTransportMechanism OBJECT-TYPE 1988 SYNTAX BITS { 1989 -- SONET/SDH encoding type: 1990 j016OverheadBytes(0), 1991 j064OverheadBytes(1), 1992 dccSectionOverheadBytes(2), 1993 dccLineOverheadBytes(3), 1994 pos(4), 1995 j0Trace(5) 1996 -- GigE encoding type: TBD 1997 -- 10GigE encoding type: TBD 1998 } 1999 MAX-ACCESS read-create 2000 STATUS current 2001 DESCRIPTION 2002 "This defines the transport mechanism for the Test messages. The 2003 scope of this bit mask is restricted to each link encoding 2004 type. The local node will set the bits corresponding to the 2005 various mechanisms it can support for transmitting LMP Test 2006 messages. The receiver chooses the appropriate mechanism in the 2007 BeginVerifyAck message." 2008 REFERENCE 2009 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 2010 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 2011 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 2012 B. Rajagopalan, March 2002." 2013 ::= { lmpLinkVerificationEntry 3 } 2015 lmpVerifyAllLinks OBJECT-TYPE 2016 SYNTAX INTEGER { verifyAllLinks(1), verifyNewLinks(2) } 2017 MAX-ACCESS read-create 2018 STATUS current 2019 DESCRIPTION 2020 "This object indicates whether the verification process checks 2021 all entities or only the new entities that have been added to 2022 this TE link." 2023 ::= { lmpLinkVerificationEntry 4 } 2025 lmpTeLinkBitRate OBJECT-TYPE 2026 SYNTAX Unsigned32 2027 MAX-ACCESS read-create 2028 STATUS current 2029 DESCRIPTION 2030 "This is the bit rate at which the Test messages will be 2031 transmitted and is expressed in bytes per second." 2032 REFERENCE 2033 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 2034 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 2035 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 2036 B. Rajagopalan, March 2002." 2037 ::= { lmpLinkVerificationEntry 5 } 2039 lmpTeLinkWavelength OBJECT-TYPE 2040 SYNTAX Unsigned32 2041 MAX-ACCESS read-create 2042 STATUS current 2043 DESCRIPTION 2044 "This value corresponds to the wavelength at 2045 which the Test messages will be transmitted over and is 2046 measured in nanometers (nm). If each data-bearing link 2047 corresponds to a separate wavelength, than this value should be 2048 set to 0." 2049 REFERENCE 2050 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 2051 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 2052 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 2053 B. Rajagopalan, March 2002." 2054 ::= { lmpLinkVerificationEntry 6 } 2056 -- End of lmpLinkVerificationTable 2058 -- LMP TE Link Performance Table 2060 lmpTeLinkPerfTable OBJECT-TYPE 2061 SYNTAX SEQUENCE OF LmpTeLinkPerfEntry 2062 MAX-ACCESS not-accessible 2063 STATUS current 2064 DESCRIPTION 2065 "This table specifies LMP TE link performance counters." 2066 ::= { lmpObjects 15 } 2068 lmpTeLinkPerfEntry OBJECT-TYPE 2069 SYNTAX LmpTeLinkPerfEntry 2070 MAX-ACCESS not-accessible 2071 STATUS current 2072 DESCRIPTION 2073 "An entry in this table is created by a LMP-enabled device for 2074 every TE link." 2075 AUGMENTS { lmpTeLinkEntry } 2076 ::= { lmpTeLinkPerfTable 1 } 2078 LmpTeLinkPerfEntry ::= SEQUENCE { 2079 lmpTeLinkInOctets Counter32, 2080 lmpTeLinkOutOctets Counter32, 2081 lmpTeLinkBeginVerifyReceived Counter32, 2082 lmpTeLinkBeginVerifySent Counter32, 2083 lmpTeLinkBeginVerifyRetransmit Counter32, 2084 lmpTeLinkBeginVerifyAckReceived Counter32, 2085 lmpTeLinkBeginVerifyAckSent Counter32, 2086 lmpTeLinkBeginVerifyNackReceived Counter32, 2087 lmpTeLinkBeginVerifyNackSent Counter32, 2088 lmpTeLinkEndVerifyReceived Counter32, 2089 lmpTeLinkEndVerifySent Counter32, 2090 lmpTeLinkEndVerifyRetransmit Counter32, 2091 lmpTeLinkEndVerifyAckReceived Counter32, 2092 lmpTeLinkEndVerifyAckSent Counter32, 2093 lmpTeLinkTestStatusSuccessReceived Counter32, 2094 lmpTeLinkTestStatusSuccessSent Counter32, 2095 lmpTeLinkTestStatusSuccessRetransmit Counter32, 2096 lmpTeLinkTestStatusFailureReceived Counter32, 2097 lmpTeLinkTestStatusFailureSent Counter32, 2098 lmpTeLinkTestStatusFailureRetransmit Counter32, 2099 lmpTeLinkTestStatusAckReceived Counter32, 2100 lmpTeLinkTestStatusAckSent Counter32, 2101 lmpTeLinkSummaryReceived Counter32, 2102 lmpTeLinkSummarySent Counter32, 2103 lmpTeLinkSummaryRetransmit Counter32, 2104 lmpTeLinkSummaryAckReceived Counter32, 2105 lmpTeLinkSummaryAckSent Counter32, 2106 lmpTeLinkSummaryNackReceived Counter32, 2107 lmpTeLinkSummaryNackSent Counter32, 2108 lmpTeLinkChannelStatusReceived Counter32, 2109 lmpTeLinkChannelStatusSent Counter32, 2110 lmpTeLinkChannelStatusRetransmit Counter32, 2111 lmpTeLinkChannelStatusAckReceived Counter32, 2112 lmpTeLinkChannelStatusAckSent Counter32, 2113 lmpTeLinkChannelStatusRequestReceived Counter32, 2114 lmpTeLinkChannelStatusRequestSent Counter32, 2115 lmpTeLinkChannelStatusRequestRetransmit Counter32, 2116 lmpTeLinkChannelStatusResponseSent Counter32, 2117 lmpTeLinkChannelStatusResponseReceived Counter32, 2118 lmpTeLinkCounterDiscontinuityTime TimeStamp 2119 } 2121 lmpTeLinkInOctets OBJECT-TYPE 2122 SYNTAX Counter32 2123 MAX-ACCESS read-only 2124 STATUS current 2125 DESCRIPTION 2126 "The total number of LMP message octets received for 2127 this TE link." 2128 ::= { lmpTeLinkPerfEntry 1 } 2130 lmpTeLinkOutOctets OBJECT-TYPE 2131 SYNTAX Counter32 2132 MAX-ACCESS read-only 2133 STATUS current 2134 DESCRIPTION 2135 "The total number of LMP message octets transmitted out 2136 for this TE link." 2137 ::= { lmpTeLinkPerfEntry 2 } 2139 lmpTeLinkBeginVerifyReceived OBJECT-TYPE 2140 SYNTAX Counter32 2141 MAX-ACCESS read-only 2142 STATUS current 2143 DESCRIPTION 2144 "This object counts the number of BeginVerify messages that have 2145 been received for this TE link." 2146 ::= { lmpTeLinkPerfEntry 3 } 2148 lmpTeLinkBeginVerifySent OBJECT-TYPE 2149 SYNTAX Counter32 2150 MAX-ACCESS read-only 2151 STATUS current 2152 DESCRIPTION 2153 "This object counts the number of BeginVerify messages that have 2154 been sent for this TE link." 2155 ::= { lmpTeLinkPerfEntry 4 } 2157 lmpTeLinkBeginVerifyRetransmit OBJECT-TYPE 2158 SYNTAX Counter32 2159 MAX-ACCESS read-only 2160 STATUS current 2161 DESCRIPTION 2162 "This object counts the number of BeginVerify messages that 2163 have been retransmitted for this TE link." 2164 ::= { lmpTeLinkPerfEntry 5 } 2166 lmpTeLinkBeginVerifyAckReceived OBJECT-TYPE 2167 SYNTAX Counter32 2168 MAX-ACCESS read-only 2169 STATUS current 2170 DESCRIPTION 2171 "This object counts the number of BeginVerifyAck messages that have 2172 been received for this TE link." 2173 ::= { lmpTeLinkPerfEntry 6 } 2175 lmpTeLinkBeginVerifyAckSent OBJECT-TYPE 2176 SYNTAX Counter32 2177 MAX-ACCESS read-only 2178 STATUS current 2179 DESCRIPTION 2180 "This object counts the number of BeginVerifyAck messages that have 2181 been sent for this TE link." 2183 ::= { lmpTeLinkPerfEntry 7 } 2185 lmpTeLinkBeginVerifyNackReceived OBJECT-TYPE 2186 SYNTAX Counter32 2187 MAX-ACCESS read-only 2188 STATUS current 2189 DESCRIPTION 2190 "This object counts the number of BeginVerifyNack messages that have 2191 been received for this TE link." 2192 ::= { lmpTeLinkPerfEntry 8 } 2194 lmpTeLinkBeginVerifyNackSent OBJECT-TYPE 2195 SYNTAX Counter32 2196 MAX-ACCESS read-only 2197 STATUS current 2198 DESCRIPTION 2199 "This object counts the number of BeginVerifyNack messages that have 2200 been sent for this TE link." 2201 ::= { lmpTeLinkPerfEntry 9 } 2203 lmpTeLinkEndVerifyReceived OBJECT-TYPE 2204 SYNTAX Counter32 2205 MAX-ACCESS read-only 2206 STATUS current 2207 DESCRIPTION 2208 "This object counts the number of EndVerify messages that have 2209 been received for this TE link." 2210 ::= { lmpTeLinkPerfEntry 10 } 2212 lmpTeLinkEndVerifySent OBJECT-TYPE 2213 SYNTAX Counter32 2214 MAX-ACCESS read-only 2215 STATUS current 2216 DESCRIPTION 2217 "This object counts the number of EndVerify messages that have 2218 been sent for this TE link." 2219 ::= { lmpTeLinkPerfEntry 11 } 2221 lmpTeLinkEndVerifyRetransmit OBJECT-TYPE 2222 SYNTAX Counter32 2223 MAX-ACCESS read-only 2224 STATUS current 2225 DESCRIPTION 2226 "This object counts the number of EndVerify messages that 2227 have been retransmitted over this control channel." 2228 ::= { lmpTeLinkPerfEntry 12 } 2230 lmpTeLinkEndVerifyAckReceived OBJECT-TYPE 2231 SYNTAX Counter32 2232 MAX-ACCESS read-only 2233 STATUS current 2234 DESCRIPTION 2235 "This object counts the number of EndVerifyAck messages that have 2236 been received for this TE link." 2237 ::= { lmpTeLinkPerfEntry 13 } 2239 lmpTeLinkEndVerifyAckSent OBJECT-TYPE 2240 SYNTAX Counter32 2241 MAX-ACCESS read-only 2242 STATUS current 2243 DESCRIPTION 2244 "This object counts the number of EndVerifyAck messages that have 2245 been sent for this TE link." 2246 ::= { lmpTeLinkPerfEntry 14 } 2248 lmpTeLinkTestStatusSuccessReceived OBJECT-TYPE 2249 SYNTAX Counter32 2250 MAX-ACCESS read-only 2251 STATUS current 2252 DESCRIPTION 2253 "This object counts the number of TestStatusSuccess messages that have 2254 been received for this TE link." 2255 ::= { lmpTeLinkPerfEntry 15 } 2257 lmpTeLinkTestStatusSuccessSent OBJECT-TYPE 2258 SYNTAX Counter32 2259 MAX-ACCESS read-only 2260 STATUS current 2261 DESCRIPTION 2262 "This object counts the number of TestStatusSuccess messages that have 2263 been sent for this TE link." 2264 ::= { lmpTeLinkPerfEntry 16 } 2266 lmpTeLinkTestStatusSuccessRetransmit OBJECT-TYPE 2267 SYNTAX Counter32 2268 MAX-ACCESS read-only 2269 STATUS current 2270 DESCRIPTION 2271 "This object counts the number of TestStatusSuccess messages that 2272 have been retransmitted for this TE link." 2273 ::= { lmpTeLinkPerfEntry 17 } 2275 lmpTeLinkTestStatusFailureReceived OBJECT-TYPE 2276 SYNTAX Counter32 2277 MAX-ACCESS read-only 2278 STATUS current 2279 DESCRIPTION 2280 "This object counts the number of TestStatusFailure messages that have 2281 been received for this TE link." 2282 ::= { lmpTeLinkPerfEntry 18 } 2284 lmpTeLinkTestStatusFailureSent OBJECT-TYPE 2285 SYNTAX Counter32 2286 MAX-ACCESS read-only 2287 STATUS current 2288 DESCRIPTION 2289 "This object counts the number of TestStatusFailure messages that have 2290 been sent for this TE link." 2291 ::= { lmpTeLinkPerfEntry 19 } 2293 lmpTeLinkTestStatusFailureRetransmit OBJECT-TYPE 2294 SYNTAX Counter32 2295 MAX-ACCESS read-only 2296 STATUS current 2297 DESCRIPTION 2298 "This object counts the number of TestStatusFailure messages that 2299 have been retransmitted on this TE link." 2300 ::= { lmpTeLinkPerfEntry 20 } 2302 lmpTeLinkTestStatusAckReceived OBJECT-TYPE 2303 SYNTAX Counter32 2304 MAX-ACCESS read-only 2305 STATUS current 2306 DESCRIPTION 2307 "This object counts the number of TestStatusAck messages that have 2308 been received for this TE link." 2309 ::= { lmpTeLinkPerfEntry 21 } 2311 lmpTeLinkTestStatusAckSent OBJECT-TYPE 2312 SYNTAX Counter32 2313 MAX-ACCESS read-only 2314 STATUS current 2315 DESCRIPTION 2316 "This object counts the number of TestStatusAck messages that have 2317 been sent for this TE link." 2318 ::= { lmpTeLinkPerfEntry 22 } 2320 lmpTeLinkSummaryReceived OBJECT-TYPE 2321 SYNTAX Counter32 2322 MAX-ACCESS read-only 2323 STATUS current 2324 DESCRIPTION 2325 "This object counts the number of LinkSummary messages that have 2326 been received for this TE link." 2328 ::= { lmpTeLinkPerfEntry 23 } 2330 lmpTeLinkSummarySent OBJECT-TYPE 2331 SYNTAX Counter32 2332 MAX-ACCESS read-only 2333 STATUS current 2334 DESCRIPTION 2335 "This object counts the number of LinkSummary messages that have 2336 been sent for this TE link." 2337 ::= { lmpTeLinkPerfEntry 24 } 2339 lmpTeLinkSummaryRetransmit OBJECT-TYPE 2340 SYNTAX Counter32 2341 MAX-ACCESS read-only 2342 STATUS current 2343 DESCRIPTION 2344 "This object counts the number of LinkSummary messages that 2345 have been retransmitted over this control channel." 2346 ::= { lmpTeLinkPerfEntry 25 } 2348 lmpTeLinkSummaryAckReceived OBJECT-TYPE 2349 SYNTAX Counter32 2350 MAX-ACCESS read-only 2351 STATUS current 2352 DESCRIPTION 2353 "This object counts the number of LinkSummaryAck messages that have 2354 been received for this TE link." 2355 ::= { lmpTeLinkPerfEntry 26 } 2357 lmpTeLinkSummaryAckSent OBJECT-TYPE 2358 SYNTAX Counter32 2359 MAX-ACCESS read-only 2360 STATUS current 2361 DESCRIPTION 2362 "This object counts the number of LinkSummaryAck messages that have 2363 been sent for this TE link." 2364 ::= { lmpTeLinkPerfEntry 27 } 2366 lmpTeLinkSummaryNackReceived OBJECT-TYPE 2367 SYNTAX Counter32 2368 MAX-ACCESS read-only 2369 STATUS current 2370 DESCRIPTION 2371 "This object counts the number of LinkSummaryNack messages that have 2372 been received for this TE link." 2373 ::= { lmpTeLinkPerfEntry 28 } 2375 lmpTeLinkSummaryNackSent OBJECT-TYPE 2376 SYNTAX Counter32 2377 MAX-ACCESS read-only 2378 STATUS current 2379 DESCRIPTION 2380 "This object counts the number of LinkSummaryNack messages that have 2381 been sent for this TE link." 2382 ::= { lmpTeLinkPerfEntry 29 } 2384 lmpTeLinkChannelStatusReceived OBJECT-TYPE 2385 SYNTAX Counter32 2386 MAX-ACCESS read-only 2387 STATUS current 2388 DESCRIPTION 2389 "This object counts the number of ChannelStatus messages that have 2390 been received for this TE link." 2391 ::= { lmpTeLinkPerfEntry 30 } 2393 lmpTeLinkChannelStatusSent OBJECT-TYPE 2394 SYNTAX Counter32 2395 MAX-ACCESS read-only 2396 STATUS current 2397 DESCRIPTION 2398 "This object counts the number of ChannelStatus messages that have 2399 been sent for this TE link." 2400 ::= { lmpTeLinkPerfEntry 31 } 2402 lmpTeLinkChannelStatusRetransmit OBJECT-TYPE 2403 SYNTAX Counter32 2404 MAX-ACCESS read-only 2405 STATUS current 2406 DESCRIPTION 2407 "This object counts the number of ChannelStatus messages that have 2408 been retransmitted for this TE link." 2409 ::= { lmpTeLinkPerfEntry 32 } 2411 lmpTeLinkChannelStatusAckReceived OBJECT-TYPE 2412 SYNTAX Counter32 2413 MAX-ACCESS read-only 2414 STATUS current 2415 DESCRIPTION 2416 "This object counts the number of ChannelStatusAck messages that have 2417 been received for this TE link." 2418 ::= { lmpTeLinkPerfEntry 33 } 2420 lmpTeLinkChannelStatusAckSent OBJECT-TYPE 2421 SYNTAX Counter32 2422 MAX-ACCESS read-only 2423 STATUS current 2424 DESCRIPTION 2425 "This object counts the number of ChannelStatus messages that have 2426 been sent for this TE link." 2427 ::= { lmpTeLinkPerfEntry 34 } 2429 lmpTeLinkChannelStatusRequestReceived OBJECT-TYPE 2430 SYNTAX Counter32 2431 MAX-ACCESS read-only 2432 STATUS current 2433 DESCRIPTION 2434 "This object counts the number of ChannelStatusRequest messages that 2435 have been received for this TE link." 2436 ::= { lmpTeLinkPerfEntry 35 } 2438 lmpTeLinkChannelStatusRequestSent OBJECT-TYPE 2439 SYNTAX Counter32 2440 MAX-ACCESS read-only 2441 STATUS current 2442 DESCRIPTION 2443 "This object counts the number of ChannelStatusRequest messages that 2444 have been sent for this TE link." 2445 ::= { lmpTeLinkPerfEntry 36 } 2447 lmpTeLinkChannelStatusRequestRetransmit OBJECT-TYPE 2448 SYNTAX Counter32 2449 MAX-ACCESS read-only 2450 STATUS current 2451 DESCRIPTION 2452 "This object counts the number of ChannelStatusRequest messages that 2453 have been retransmitted for this TE link." 2454 ::= { lmpTeLinkPerfEntry 37 } 2456 lmpTeLinkChannelStatusResponseReceived OBJECT-TYPE 2457 SYNTAX Counter32 2458 MAX-ACCESS read-only 2459 STATUS current 2460 DESCRIPTION 2461 "This object counts the number of ChannelStatusResponse messages that 2462 have been received for this TE link." 2463 ::= { lmpTeLinkPerfEntry 38 } 2465 lmpTeLinkChannelStatusResponseSent OBJECT-TYPE 2466 SYNTAX Counter32 2467 MAX-ACCESS read-only 2468 STATUS current 2469 DESCRIPTION 2470 "This object counts the number of ChannelStatusResponse messages that 2471 have been sent for this TE link." 2473 ::= { lmpTeLinkPerfEntry 39 } 2475 lmpTeLinkCounterDiscontinuityTime OBJECT-TYPE 2476 SYNTAX TimeStamp 2477 MAX-ACCESS read-only 2478 STATUS current 2479 DESCRIPTION 2480 "The value of sysUpTime on the most recent occasion at which 2481 any one or more of this TE link's counters suffered a 2482 discontinuity. The relevant counters are the specific 2483 instances associated with this TE link of any Counter32 2484 object contained in the lmpTeLinkPerfTable. If 2485 no such discontinuities have occurred since the last re- 2486 initialization of the local management subsystem, then this 2487 object contains a zero value." 2488 ::= { lmpTeLinkPerfEntry 40 } 2490 -- End of lmpTeLinkPerfTable 2492 -- LMP Data Bearing Link Table 2494 lmpDataBearingLinkTable OBJECT-TYPE 2495 SYNTAX SEQUENCE OF LmpDataBearingLinkEntry 2496 MAX-ACCESS not-accessible 2497 STATUS current 2498 DESCRIPTION 2499 "This table specifies the data-bearing links managed by the 2500 LMP." 2501 ::= { lmpObjects 16 } 2503 lmpDataBearingLinkEntry OBJECT-TYPE 2504 SYNTAX LmpDataBearingLinkEntry 2505 MAX-ACCESS not-accessible 2506 STATUS current 2507 DESCRIPTION 2508 "An entry in this table exists for each ifEntry that represents 2509 a data-bearing link. An ifEntry with an ifIndex must exist 2510 before the corresponding lmpDataBearingLinkEntry is created. 2511 If an entry representing the data-bearing link is destroyed in 2512 the ifTable, then so is the corresponding entry in the 2513 lmpDataBearingLinkTable. The administrative status value is 2514 controlled from the ifEntry. The index to this table also 2515 used to get information in the dataBearingChannelTable 2516 [BUNDLE-MIB]." 2517 INDEX { ifIndex } 2518 ::= { lmpDataBearingLinkTable 1 } 2520 LmpDataBearingLinkEntry ::= SEQUENCE { 2521 lmpDataBearingLinkType INTEGER, 2522 lmpDataBearingLinkIpAddrType InetAddressType, 2523 lmpDataBearingLinkIpAddr InetAddress, 2524 lmpDataBearingLinkRemoteIpAddress InetAddress, 2525 lmpDataBearingLinkRemoteIfId InterfaceIndexOrZero, 2526 lmpDataBearingLinkEncodingType INTEGER, 2527 lmpDataBearingLinkActiveOperStatus INTEGER, 2528 lmpDataBearingLinkPassiveOperStatus INTEGER, 2529 lmpDataBearingLinkRowStatus RowStatus, 2530 lmpDataBearingLinkStorageType StorageType 2531 } 2533 lmpDataBearingLinkType OBJECT-TYPE 2534 SYNTAX INTEGER { 2535 port(1), 2536 componentLink(2) 2537 } 2538 MAX-ACCESS read-only 2539 STATUS current 2540 DESCRIPTION 2541 "This attribute specifies whether this data-bearing link is 2542 a port or a component link. Component link are multiplex 2543 capable whereas, ports are not multiplex capable." 2544 REFERENCE 2545 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 2546 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 2547 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 2548 B. Rajagopalan, March 2002." 2549 ::= { lmpDataBearingLinkEntry 1 } 2551 lmpDataBearingLinkIpAddrType OBJECT-TYPE 2552 SYNTAX InetAddressType 2553 MAX-ACCESS read-create 2554 STATUS current 2555 DESCRIPTION 2556 "This attribute specifies the data-bearing link IP address 2557 type. If the data-bearing link is unnumbered, the address 2558 type must be set to unknown(0)." 2559 ::= { lmpDataBearingLinkEntry 2 } 2561 lmpDataBearingLinkIpAddr OBJECT-TYPE 2562 SYNTAX InetAddress 2563 MAX-ACCESS read-create 2564 STATUS current 2565 DESCRIPTION 2566 "IP address of the data-bearing link. This 2567 If the data-bearing link is unnumbered, then the 2568 IP address must be null." 2569 ::= { lmpDataBearingLinkEntry 3 } 2571 lmpDataBearingLinkRemoteIpAddress OBJECT-TYPE 2572 SYNTAX InetAddress 2573 MAX-ACCESS read-create 2574 STATUS current 2575 DESCRIPTION 2576 "IP address of the remote end point. This 2577 information is either configured manually or is 2578 communicated by the remote node during the link verification 2579 procedure. If the data-bearing link is unnumbered, then the 2580 remote IP address must be null." 2581 ::= { lmpDataBearingLinkEntry 4 } 2583 lmpDataBearingLinkRemoteIfId OBJECT-TYPE 2584 SYNTAX InterfaceIndexOrZero 2585 MAX-ACCESS read-create 2586 STATUS current 2587 DESCRIPTION 2588 "Interface identifier of the remote end point. This 2589 information is either configured manually or is 2590 communicated by the remote node during the link verification 2591 procedure." 2592 ::= { lmpDataBearingLinkEntry 5 } 2594 lmpDataBearingLinkEncodingType OBJECT-TYPE 2595 SYNTAX INTEGER { 2596 packet(1), 2597 ethernet(2), 2598 ansiEtsiPdh(3), 2599 sdhItuSonetAnsi(5), 2600 digitalWrapper(7), 2601 lambda(8), 2602 fiber(9), 2603 fiberChannel(11) 2604 } 2605 MAX-ACCESS read-create 2606 STATUS current 2607 DESCRIPTION 2608 "The encoding type of the data-bearing link." 2609 REFERENCE 2610 "draft-ietf-mpls-generalized-signaling-08.txt - Generalized 2611 MPLS Signaling Functional Description, P. Ashwood-Smith, 2612 A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan, 2613 E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha, 2614 V. Sharma, G. Swallow, Z. Tang, April 2002." 2615 ::= { lmpDataBearingLinkEntry 6 } 2617 lmpDataBearingLinkActiveOperStatus OBJECT-TYPE 2618 SYNTAX INTEGER { 2619 upAlloc(1), 2620 upFree(2), 2621 down(3), 2622 testing(4) } 2623 MAX-ACCESS read-only 2624 STATUS current 2625 DESCRIPTION 2626 "The actual operational status of this data-bearing link 2627 (active FSM)." 2628 REFERENCE 2629 "draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), 2630 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 2631 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 2632 B. Rajagopalan, March 2002." 2633 ::= { lmpDataBearingLinkEntry 7 } 2635 lmpDataBearingLinkPassiveOperStatus OBJECT-TYPE 2636 SYNTAX INTEGER { 2637 upAlloc(1), 2638 upFree(2), 2639 down(3), 2640 psvTst(4) } 2641 MAX-ACCESS read-only 2642 STATUS current 2643 DESCRIPTION 2644 "The actual operational status of this data-bearing link 2645 (passive FSM)." 2646 REFERENCE 2647 "draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), 2648 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 2649 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 2650 B. Rajagopalan, March 2002." 2651 ::= { lmpDataBearingLinkEntry 8 } 2653 lmpDataBearingLinkRowStatus OBJECT-TYPE 2654 SYNTAX RowStatus 2655 MAX-ACCESS read-create 2656 STATUS current 2657 DESCRIPTION 2658 "This variable is used to create, modify, and/or 2659 delete a row in this table. All read-create objects 2660 can only be changed when lmpDataBearingLinkRowStatus is active." 2661 ::= { lmpDataBearingLinkEntry 9 } 2663 lmpDataBearingLinkStorageType OBJECT-TYPE 2664 SYNTAX StorageType 2665 MAX-ACCESS read-create 2666 STATUS current 2667 DESCRIPTION 2668 "The storage type for this conceptual row in the 2669 lmpDataBearingLinkTable. Conceptual rows having the value 2670 'permanent' need not allow write-access to any 2671 columnar object in the row." 2672 ::= { lmpDataBearingLinkEntry 10 } 2674 -- End of lmpDataBearingLinkTable 2676 -- LMP Data Bearing Link Performance Table 2678 lmpDataBearingLinkPerfTable OBJECT-TYPE 2679 SYNTAX SEQUENCE OF LmpDataBearingLinkPerfEntry 2680 MAX-ACCESS not-accessible 2681 STATUS current 2682 DESCRIPTION 2683 "This table specifies the data-bearing links LMP performance 2684 counters." 2685 ::= { lmpObjects 17 } 2687 lmpDataBearingLinkPerfEntry OBJECT-TYPE 2688 SYNTAX LmpDataBearingLinkPerfEntry 2689 MAX-ACCESS not-accessible 2690 STATUS current 2691 DESCRIPTION 2692 "An entry in this table contains information about 2693 the LMP performance counters for the data-bearing links." 2694 AUGMENTS { lmpDataBearingLinkEntry } 2695 ::= { lmpDataBearingLinkPerfTable 1 } 2697 LmpDataBearingLinkPerfEntry ::= SEQUENCE { 2698 lmpDataBearingLinkTestReceived Counter32, 2699 lmpDataBearingLinkTestSent Counter32, 2700 lmpDataBearingLinkActiveTestSuccess Counter32, 2701 lmpDataBearingLinkActiveTestFailure Counter32, 2702 lmpDataBearingLinkPassiveTestSuccess Counter32, 2703 lmpDataBearingLinkPassiveTestFailure Counter32, 2704 lmpDataBearingLinkCounterDiscontinuityTime TimeStamp 2705 } 2707 lmpDataBearingLinkTestReceived OBJECT-TYPE 2708 SYNTAX Counter32 2709 MAX-ACCESS read-only 2710 STATUS current 2711 DESCRIPTION 2712 "This object counts the number of Test messages that have 2713 been received on this data-bearing link." 2714 ::= { lmpDataBearingLinkPerfEntry 1 } 2716 lmpDataBearingLinkTestSent OBJECT-TYPE 2717 SYNTAX Counter32 2718 MAX-ACCESS read-only 2719 STATUS current 2720 DESCRIPTION 2721 "This object counts the number of Test messages that have 2722 been sent on this data-bearing link." 2723 ::= { lmpDataBearingLinkPerfEntry 2 } 2725 lmpDataBearingLinkActiveTestSuccess OBJECT-TYPE 2726 SYNTAX Counter32 2727 MAX-ACCESS read-only 2728 STATUS current 2729 DESCRIPTION 2730 "This object counts the number of data-bearing link test 2731 that were successful on the active side of this data- 2732 bearing link." 2733 ::= { lmpDataBearingLinkPerfEntry 3 } 2735 lmpDataBearingLinkActiveTestFailure OBJECT-TYPE 2736 SYNTAX Counter32 2737 MAX-ACCESS read-only 2738 STATUS current 2739 DESCRIPTION 2740 "This object counts the number of data-bearing link test 2741 that failed on the active side of this data-bearing link." 2742 ::= { lmpDataBearingLinkPerfEntry 4 } 2744 lmpDataBearingLinkPassiveTestSuccess OBJECT-TYPE 2745 SYNTAX Counter32 2746 MAX-ACCESS read-only 2747 STATUS current 2748 DESCRIPTION 2749 "This object counts the number of data-bearing link test 2750 that were successful on the passive side of this data- 2751 bearing link." 2752 ::= { lmpDataBearingLinkPerfEntry 5 } 2754 lmpDataBearingLinkPassiveTestFailure OBJECT-TYPE 2755 SYNTAX Counter32 2756 MAX-ACCESS read-only 2757 STATUS current 2758 DESCRIPTION 2759 "This object counts the number of data-bearing link test 2760 that failed on the passive side of this data-bearing link." 2761 ::= { lmpDataBearingLinkPerfEntry 6 } 2763 lmpDataBearingLinkCounterDiscontinuityTime OBJECT-TYPE 2764 SYNTAX TimeStamp 2765 MAX-ACCESS read-only 2766 STATUS current 2767 DESCRIPTION 2768 "The value of sysUpTime on the most recent occasion at which 2769 any one or more of this data-bearing link's counters suffered a 2770 discontinuity. The relevant counters are the specific 2771 instances associated with this data-bearing link of any Counter32 2772 object contained in the lmpDataBearingLinkPerfTable. If 2773 no such discontinuities have occurred since the last re- 2774 initialization of the local management subsystem, then this 2775 object contains a zero value." 2776 ::= { lmpDataBearingLinkPerfEntry 7 } 2778 -- End of lmpDataBearingLinkPerfTable 2780 -- Notification Configuration 2782 lmpLinkPropertyMismatchNotifEnable OBJECT-TYPE 2783 SYNTAX TruthValue 2784 MAX-ACCESS read-write 2785 STATUS current 2786 DESCRIPTION 2787 "If this object is true, then it enables the 2788 generation of lmpTeLinkPropertyMismatch 2789 and lmpDataBearingLinkPropertyMismatch notifications, 2790 otherwise these notifications are not emitted." 2791 DEFVAL { false } 2792 ::= { lmpObjects 18 } 2794 lmpUnprotectedNotifEnable OBJECT-TYPE 2795 SYNTAX TruthValue 2796 MAX-ACCESS read-write 2797 STATUS current 2798 DESCRIPTION 2799 "If this object is true, then it enables the 2800 generation of lmpUnprotected notifications, 2801 otherwise these notifications are not emitted." 2802 DEFVAL { false } 2803 ::= { lmpObjects 19 } 2805 lmpCcUpDownNotifEnable OBJECT-TYPE 2806 SYNTAX TruthValue 2807 MAX-ACCESS read-write 2808 STATUS current 2809 DESCRIPTION 2810 "If this object is true, then it enables the generation of 2811 lmpControlChannelUp and lmpControlChannelDown notifications, 2812 otherwise these notifications are not emitted." 2813 DEFVAL { false } 2814 ::= { lmpObjects 20 } 2816 lmpTeLinkNotifEnable OBJECT-TYPE 2817 SYNTAX TruthValue 2818 MAX-ACCESS read-write 2819 STATUS current 2820 DESCRIPTION 2821 "If this object is true, then it enables the 2822 generation of lmpTeLinkDegraded and lmpTeLinkNotDegraded 2823 notifications, otherwise these notifications are not emitted." 2824 DEFVAL { false } 2825 ::= { lmpObjects 21 } 2827 lmpDataBearingLinkNotifEnable OBJECT-TYPE 2828 SYNTAX TruthValue 2829 MAX-ACCESS read-write 2830 STATUS current 2831 DESCRIPTION 2832 "If this object is true, then it enables the 2833 generation of lmpDataBearingLinkVerificationFailure 2834 notification, otherwise these notifications are not emitted." 2835 DEFVAL { false } 2836 ::= { lmpObjects 22 } 2838 -- Notifications 2840 -- Link Property Mismatch Notifications 2842 lmpTeLinkPropertyMismatch NOTIFICATION-TYPE 2843 OBJECTS { teLinkRemoteIpAddr, 2844 teLinkIncomingIfId } 2845 STATUS current 2846 DESCRIPTION 2847 "This notification is generated when a TE link property 2848 mismatch is detected on the node. The received remote TE link 2849 id of the misconfigured TE link is represented by either 2850 teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether 2851 the TE link is numbered or unnumbered. This notification should 2852 not be sent unless lmpLinkPropertyMismatchNotifEnable is 2853 true." 2855 ::= { lmpNotifications 1 } 2857 lmpDataBearingLinkPropertyMismatch NOTIFICATION-TYPE 2858 OBJECTS { ifIndex, 2859 lmpDataBearingLinkRemoteIfId } 2860 STATUS current 2861 DESCRIPTION 2862 "This notification is generated when a data-bearing link 2863 property mismatch is detected on the node. ifIndex 2864 is the interface index of the TE link. The remote entity 2865 interface id is the remote entity interface id received in the 2866 LinkSummary message. This notification should 2867 not be sent unless lmpLinkPropertyMismatchNotifEnable is 2868 true." 2869 ::= { lmpNotifications 2 } 2871 -- Neighbor Notification 2873 lmpUnprotected NOTIFICATION-TYPE 2874 OBJECTS { lmpCcNbrNodeId } 2875 STATUS current 2876 DESCRIPTION 2877 "This notification is generated when there are more than one 2878 control channels between LMP neighbors and the last redundant 2879 control channel has failed. If the remaining operational control 2880 channel fails, then there will be no more control channels 2881 between the pair of nodes and all the TE links between the pair 2882 of nodes will go to degraded state. This notification should not 2883 be sent unless lmpUnprotectedNotifEnable is set to true." 2884 ::= { lmpNotifications 3 } 2886 -- Control Channel Notifications 2888 lmpControlChannelUp NOTIFICATION-TYPE 2889 OBJECTS { lmpCcAdminStatus, lmpCcOperStatus } 2890 STATUS current 2891 DESCRIPTION 2892 "This notification is generated when a control 2893 channel transitions to the up operational state. This 2894 notification should not be sent unless lmpCcUpDownNotifEnable 2895 is true." 2896 ::= { lmpNotifications 4 } 2898 lmpControlChannelDown NOTIFICATION-TYPE 2899 OBJECTS { lmpCcAdminStatus, lmpCcOperStatus } 2900 STATUS current 2901 DESCRIPTION 2902 "This notification is generated when a control 2903 channel transitions out of the up operational state. This 2904 notification should not be sent unless lmpCcUpDownNotifEnable 2905 is true." 2906 ::= { lmpNotifications 5 } 2908 -- TE Link Notification 2910 lmpTeLinkDegraded NOTIFICATION-TYPE 2911 OBJECTS { ifIndex } 2912 STATUS current 2913 DESCRIPTION 2914 "This notification is generated when a lmpTeLinkOperStatus 2915 object for a TE link enters the degraded state. This 2916 notification should not be sent unless lmpTeLinkNotifEnable 2917 is true." 2918 ::= { lmpNotifications 6 } 2920 lmpTeLinkNotDegraded NOTIFICATION-TYPE 2921 OBJECTS { ifIndex } 2922 STATUS current 2923 DESCRIPTION 2924 "This notification is generated when a lmpTeLinkOperStatus 2925 object for a TE link leaves the degraded state. This 2926 notification should not be sent unless lmpTeLinkNotifEnable 2927 is true." 2928 ::= { lmpNotifications 7 } 2930 -- Data-bearing Link Notification 2932 lmpDataBearingLinkVerificationFailure NOTIFICATION-TYPE 2933 OBJECTS { ifIndex } 2934 STATUS current 2935 DESCRIPTION 2936 "This notification is generated when a data-bearing 2937 link verification fails. This notification should not be sent 2938 unless lmpDataBearingLinkNotifEnable is true." 2939 ::= { lmpNotifications 8 } 2941 -- End of notifications 2943 -- Module compliance 2945 lmpGroups 2946 OBJECT IDENTIFIER ::= { lmpConformance 1 } 2948 lmpCompliances 2949 OBJECT IDENTIFIER ::= { lmpConformance 2 } 2951 lmpFullModuleCompliance MODULE-COMPLIANCE 2952 STATUS current 2953 DESCRIPTION 2954 "Compliance statement for agents that support the 2955 configuration and monitoring of LMP MIB." 2956 MODULE -- this module 2958 -- The mandatory groups have to be implemented 2959 -- by all LMP-enabled devices. However, they may all be supported 2960 -- as read-only objects in the case where manual 2961 -- configuration is unsupported. 2963 MANDATORY-GROUPS { lmpNodeGroup, 2964 lmpControlChannelGroup, 2965 lmpLinkPropertyCorrelationGroup, 2966 lmpPerfGroup, 2967 lmpTeLinkGroup, 2968 lmpDataBearingLinkGroup } 2970 GROUP lmpControlChannelIsNotInterfaceGroup 2971 DESCRIPTION 2972 "This group is mandatory for devices which support 2973 control channels that are not interfaces, in addition to 2974 lmpControlChannelGroup. The following constraints apply: 2975 lmpCcIsIf must at least be read-only returning false(1)." 2977 GROUP lmpControlChannelIsInterfaceGroup 2978 DESCRIPTION 2979 "This group is mandatory for devices which support 2980 control channels that are interfaces, in addition to 2981 lmpControlChannelGroup. The following constraints apply: 2982 lmpCcIsIf must at least be read-only returning true(2)." 2984 GROUP lmpLinkVerificationGroup 2985 DESCRIPTION 2986 "This group is mandatory for devices which support 2987 the link verification procedure." 2989 GROUP lmpNotificationGroup 2990 DESCRIPTION 2991 "This group is optional." 2993 -- lmpNbrTable 2995 OBJECT lmpNbrRowStatus 2996 SYNTAX INTEGER { active(1), notInService(2), 2997 createAndGo(4), destroy(6) } 2998 MIN-ACCESS read-only 2999 DESCRIPTION 3000 "The notReady(3) and createAndWait(5) states need 3001 not be supported." 3003 OBJECT lmpNbrStorageType 3004 SYNTAX INTEGER { other(1) } 3005 MIN-ACCESS read-only 3006 DESCRIPTION 3007 "Only other(1) needs to be supported." 3009 -- lmpControlChannelTable 3011 OBJECT lmpRemoteCcIpAddrType 3012 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 3013 MIN-ACCESS read-only 3014 DESCRIPTION 3015 "The dns(16) adress type needs not be supported. For 3016 point-to-point configuration, this object MIN-ACCESS 3017 is read-create." 3019 OBJECT lmpRemoteCcIpAddr 3020 SYNTAX InetAddress (SIZE(0|4|16)) 3021 MIN-ACCESS read-only 3022 DESCRIPTION 3023 "The size of the IP address depends on the address type. 3024 For point-to-point configuration, this object MIN-ACCESS is 3025 read-create." 3027 OBJECT lmpCcRowStatus 3028 SYNTAX INTEGER { active(1), notInService(2), 3029 createAndGo(4), destroy(6) } 3030 MIN-ACCESS read-only 3031 DESCRIPTION 3032 "The notReady(3) and createAndWait(5) states need 3033 not be supported." 3035 OBJECT lmpCcOperStatus 3036 SYNTAX INTEGER { up(1), down(2) } 3037 DESCRIPTION 3038 "A value of active(3), configuring(4), goingDown(5) 3039 need not be supported." 3041 OBJECT lmpCcStorageType 3042 SYNTAX INTEGER { other(1) } 3043 MIN-ACCESS read-only 3044 DESCRIPTION 3045 "Only other(1) needs to be supported." 3047 -- lmpTeLinkTable 3049 OBJECT lmpTeLinkOperStatus 3050 SYNTAX INTEGER { up(1), down(2), degraded(4) } 3051 DESCRIPTION 3052 "The testing(3) state need not be supported." 3054 OBJECT lmpTeLinkRowStatus 3055 SYNTAX INTEGER { active(1), notInService(2), 3056 createAndGo(4), destroy(6) } 3057 MIN-ACCESS read-only 3058 DESCRIPTION 3059 "The notReady(3) and createAndWait(5) states need 3060 not be supported." 3062 OBJECT lmpTeLinkStorageType 3063 SYNTAX INTEGER { other(1) } 3064 MIN-ACCESS read-only 3065 DESCRIPTION 3066 "Only other(1) needs to be supported." 3068 -- lmpDataBearingLinkTable 3070 OBJECT lmpDataBearingLinkActiveOperStatus 3071 SYNTAX INTEGER { up(1), down(2), degraded(4) } 3072 DESCRIPTION 3073 "A value of testing(3) need not be supported." 3075 OBJECT lmpDataBearingLinkPassiveOperStatus 3076 SYNTAX INTEGER { up(1), down(2), degraded(4) } 3077 DESCRIPTION 3078 "A value of testing(3) need not be supported." 3080 OBJECT lmpDataBearingLinkRowStatus 3081 SYNTAX INTEGER { active(1), notInService(2), 3082 createAndGo(4), destroy(6) } 3083 MIN-ACCESS read-only 3084 DESCRIPTION 3085 "The notReady(3) and createAndWait(5) states need 3086 not be supported." 3088 OBJECT lmpDataBearingLinkStorageType 3089 SYNTAX INTEGER { other(1) } 3090 MIN-ACCESS read-only 3091 DESCRIPTION 3092 "Only other(1) needs to be supported." 3094 ::= { lmpCompliances 1 } 3096 lmpMonitoringModuleCompliance MODULE-COMPLIANCE 3097 STATUS current 3098 DESCRIPTION 3099 "Compliance statement for agents that support the 3100 monitoring of the LMP MIB." 3101 MODULE -- this module 3103 -- The mandatory groups have to be implemented 3104 -- by all LMP-enabled devices. However, they may all be supported 3105 -- as read-only objects in the case where manual 3106 -- configuration is unsupported. 3108 MANDATORY-GROUPS { lmpNodeGroup, 3109 lmpControlChannelGroup, 3110 lmpLinkPropertyCorrelationGroup, 3111 lmpPerfGroup, 3112 lmpTeLinkGroup, 3113 lmpDataBearingLinkGroup } 3115 GROUP lmpControlChannelIsNotInterfaceGroup 3116 DESCRIPTION 3117 "This group is mandatory for devices which support 3118 control channels that are not interfaces, in addition to 3119 lmpControlChannelGroup. The following constraints apply: 3120 lmpCcIsIf must at least be read-only returning false(1)." 3122 GROUP lmpControlChannelIsInterfaceGroup 3123 DESCRIPTION 3124 "This group is mandatory for devices which support 3125 control channels that are interfaces, in addition to 3126 lmpControlChannelGroup. The following constraints apply: 3127 lmpCcIsIf must at least be read-only returning true(2)." 3129 GROUP lmpLinkVerificationGroup 3130 DESCRIPTION 3131 "This group is mandatory for devices which support 3132 the link verification procedure." 3134 GROUP lmpNotificationGroup 3135 DESCRIPTION 3136 "This group is optional." 3138 -- Scalars 3140 OBJECT lmpAdminStatus 3141 MIN-ACCESS read-only 3142 DESCRIPTION 3143 "Write access is not required." 3145 OBJECT lmpLinkVerificationInterval 3146 MIN-ACCESS read-only 3147 DESCRIPTION 3148 "Write access is not required." 3150 OBJECT lmpCcHelloIntervalDefault 3151 MIN-ACCESS read-only 3152 DESCRIPTION 3153 "Write access is not required." 3155 OBJECT lmpCcHelloIntervalDefaultMin 3156 MIN-ACCESS read-only 3157 DESCRIPTION 3158 "Write access is not required." 3160 OBJECT lmpCcHelloIntervalDefaultMax 3161 MIN-ACCESS read-only 3162 DESCRIPTION 3163 "Write access is not required." 3165 OBJECT lmpCcHelloDeadIntervalDefault 3166 MIN-ACCESS read-only 3167 DESCRIPTION 3168 "Write access is not required." 3170 OBJECT lmpCcHelloDeadIntervalDefaultMin 3171 MIN-ACCESS read-only 3172 DESCRIPTION 3173 "Write access is not required." 3175 OBJECT lmpCcHelloDeadIntervalDefaultMax 3176 MIN-ACCESS read-only 3177 DESCRIPTION 3178 "Write access is not required." 3180 -- lmpNbrTable 3182 OBJECT lmpNbrRetransmitInterval 3183 MIN-ACCESS read-only 3184 DESCRIPTION 3185 "Write access is not required." 3187 OBJECT lmpNbrRetransmitTimeout 3188 MIN-ACCESS read-only 3189 DESCRIPTION 3190 "Write access is not required." 3192 OBJECT lmpNbrRowStatus 3193 SYNTAX INTEGER { active(1), notInService(2), 3194 createAndGo(4), destroy(6) } 3195 MIN-ACCESS read-only 3196 DESCRIPTION 3197 "The notReady(3) and createAndWait(5) states need 3198 not be supported." 3200 OBJECT lmpNbrStorageType 3201 SYNTAX INTEGER { other(1) } 3202 MIN-ACCESS read-only 3203 DESCRIPTION 3204 "Only other(1) needs to be supported." 3206 -- lmpControlChannelTable 3208 OBJECT lmpCcUnderlyingIfIndex 3209 MIN-ACCESS read-only 3210 DESCRIPTION 3211 "Write access is not required." 3213 OBJECT lmpCcIsIf 3214 MIN-ACCESS read-only 3215 DESCRIPTION 3216 "Write access is not required." 3218 OBJECT lmpCcNbrNodeId 3219 MIN-ACCESS read-only 3220 DESCRIPTION 3221 "Write access is not required." 3223 OBJECT lmpRemoteCcIpAddrType 3224 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 3225 MIN-ACCESS read-only 3226 DESCRIPTION 3227 "The dns(16) adress type needs not be supported." 3229 OBJECT lmpRemoteCcIpAddr 3230 SYNTAX InetAddress (SIZE(0|4|16)) 3231 MIN-ACCESS read-only 3232 DESCRIPTION 3233 "The size of the IP address depends on the address type." 3235 OBJECT lmpCcSetupRole 3236 MIN-ACCESS read-only 3237 DESCRIPTION 3238 "Write access is not required." 3240 OBJECT lmpCcAuthentication 3241 MIN-ACCESS read-only 3242 DESCRIPTION 3243 "Write access is not required." 3245 OBJECT lmpCcConfigRetransmitInterval 3246 MIN-ACCESS read-only 3247 DESCRIPTION 3248 "Write access is not required." 3250 OBJECT lmpCcConfigRetransmitTimeout 3251 MIN-ACCESS read-only 3252 DESCRIPTION 3253 "Write access is not required." 3255 OBJECT lmpCcHelloIntervalMin 3256 MIN-ACCESS read-only 3257 DESCRIPTION 3258 "Write access is not required." 3260 OBJECT lmpCcHelloIntervalMax 3261 MIN-ACCESS read-only 3262 DESCRIPTION 3263 "Write access is not required." 3265 OBJECT lmpCcHelloDeadIntervalMin 3266 MIN-ACCESS read-only 3267 DESCRIPTION 3268 "Write access is not required." 3270 OBJECT lmpCcHelloDeadIntervalMax 3271 MIN-ACCESS read-only 3272 DESCRIPTION 3273 "Write access is not required." 3275 OBJECT lmpCcRowStatus 3276 SYNTAX INTEGER { active(1), notInService(2), 3277 createAndGo(4), destroy(6) } 3278 MIN-ACCESS read-only 3279 DESCRIPTION 3280 "The notReady(3) and createAndWait(5) states need 3281 not be supported." 3283 OBJECT lmpCcOperStatus 3284 SYNTAX INTEGER { up(1), down(2) } 3285 MIN-ACCESS read-only 3286 DESCRIPTION 3287 "A value of active(3), configuring(4), goingDown(5) 3288 need not be supported." 3290 OBJECT lmpCcStorageType 3291 SYNTAX INTEGER { other(1) } 3292 MIN-ACCESS read-only 3293 DESCRIPTION 3294 "Only other(1) needs to be supported." 3296 -- lmpLinkVerificationTable 3298 OBJECT lmpVerifyInterval 3299 MIN-ACCESS read-only 3300 DESCRIPTION 3301 "Write access is not required." 3303 OBJECT lmpVerifyDeadInterval 3304 MIN-ACCESS read-only 3305 DESCRIPTION 3306 "Write access is not required." 3308 OBJECT lmpVerifyAllLinks 3309 MIN-ACCESS read-only 3310 DESCRIPTION 3311 "Write access is not required." 3313 -- lmpTeLinkTable 3315 OBJECT lmpTeLinkNbrNodeId 3316 MIN-ACCESS read-only 3317 DESCRIPTION 3318 "Write access is not required if the link verification 3319 procedure is enabled." 3321 OBJECT lmpTeLinkVerification 3322 MIN-ACCESS read-only 3323 DESCRIPTION 3324 "Write access is not required." 3326 OBJECT lmpTeLinkFaultManagement 3327 MIN-ACCESS read-only 3328 DESCRIPTION 3329 "Write access is not required." 3331 OBJECT lmpTeLinkDwdm 3332 MIN-ACCESS read-only 3333 DESCRIPTION 3334 "Write access is not required." 3336 OBJECT lmpTeLinkOperStatus 3337 SYNTAX INTEGER { up(1), down(2), degraded(4) } 3338 MIN-ACCESS read-only 3339 DESCRIPTION 3340 "The testing(3) state need not be supported." 3342 OBJECT lmpTeLinkRowStatus 3343 SYNTAX INTEGER { active(1), notInService(2), 3344 createAndGo(4), destroy(6) } 3345 MIN-ACCESS read-only 3346 DESCRIPTION 3347 "The notReady(3) and createAndWait(5) states need 3348 not be supported." 3350 OBJECT lmpTeLinkStorageType 3351 SYNTAX INTEGER { other(1) } 3352 MIN-ACCESS read-only 3353 DESCRIPTION 3354 "Only other(1) needs to be supported." 3356 -- lmpTeLinkVerificationTable 3358 OBJECT lmpTeLinkBitRate 3359 MIN-ACCESS read-only 3360 DESCRIPTION 3361 "Write access is not required." 3363 OBJECT lmpTeLinkWavelength 3364 MIN-ACCESS read-only 3365 DESCRIPTION 3366 "Write access is not required." 3368 -- lmpDataBearingLinkTable 3370 OBJECT lmpDataBearingLinkIpAddrType 3371 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 3372 MIN-ACCESS read-only 3373 DESCRIPTION 3374 "The dns(16) address type need not be supported. 3375 The ipv4(1) and ipv6(2) address types need not be 3376 supported if numbered links are not supported. The 3377 unknown(0) address type needs not be supported if 3378 unnumbered links are not supported." 3380 OBJECT lmpDataBearingLinkIpAddr 3381 SYNTAX InetAddress (SIZE(0|4|16)) 3382 MIN-ACCESS read-only 3383 DESCRIPTION 3384 "Size of data-bearing link IP address depends on type 3385 of data-bearing link. Data-bearing link IP address size 3386 is zero if link is unnumbered, four if link IP address is 3387 IPv4 and sixteen if link IP address is IPv6." 3389 OBJECT lmpDataBearingLinkRemoteIpAddress 3390 SYNTAX InetAddress (SIZE(0|4|16)) 3391 MIN-ACCESS read-only 3392 DESCRIPTION 3393 "Write access is not required if the link verification 3394 procedure is enabled." 3396 OBJECT lmpDataBearingLinkRemoteIfId 3397 MIN-ACCESS read-only 3398 DESCRIPTION 3399 "Write access is not required if the link verification 3400 procedure is enabled." 3402 OBJECT lmpDataBearingLinkEncodingType 3403 MIN-ACCESS read-only 3404 DESCRIPTION 3405 "Write access is not required." 3407 OBJECT lmpDataBearingLinkActiveOperStatus 3408 SYNTAX INTEGER { up(1), down(2), degraded(4) } 3409 MIN-ACCESS read-only 3410 DESCRIPTION 3411 "A value of testing(3) need not be supported." 3413 OBJECT lmpDataBearingLinkPassiveOperStatus 3414 SYNTAX INTEGER { up(1), down(2), degraded(4) } 3415 MIN-ACCESS read-only 3416 DESCRIPTION 3417 "A value of psvTst(3) need not be supported." 3419 OBJECT lmpDataBearingLinkRowStatus 3420 SYNTAX INTEGER { active(1), notInService(2), 3421 createAndGo(4), destroy(6) } 3422 MIN-ACCESS read-only 3423 DESCRIPTION 3424 "The notReady(3) and createAndWait(5) states need 3425 not be supported." 3427 OBJECT lmpDataBearingLinkStorageType 3428 SYNTAX INTEGER { other(1) } 3429 MIN-ACCESS read-only 3430 DESCRIPTION 3431 "Only other(1) needs to be supported." 3433 ::= { lmpCompliances 2 } 3435 -- Units of conformance 3437 lmpNodeGroup OBJECT-GROUP 3438 OBJECTS { lmpAdminStatus, 3439 lmpOperStatus, 3440 lmpNbrAdminStatus, 3441 lmpNbrOperStatus, 3442 lmpNbrRowStatus, 3443 lmpNbrStorageType, 3444 lmpUnprotectedNotifEnable 3445 } 3446 STATUS current 3447 DESCRIPTION 3448 "Collection of objects needed for LMP node configuration." 3449 ::= { lmpGroups 1 } 3451 lmpControlChannelGroup OBJECT-GROUP 3452 OBJECTS { 3453 lmpNbrRetransmitInterval, 3454 lmpNbrRetransmitTimeout, 3455 lmpNbrAdminStatus, 3456 lmpNbrOperStatus, 3457 lmpNbrRowStatus, 3458 lmpNbrStorageType, 3459 lmpCcHelloIntervalDefault, 3460 lmpCcHelloIntervalDefaultMin, 3461 lmpCcHelloIntervalDefaultMax, 3462 lmpCcHelloDeadIntervalDefault, 3463 lmpCcHelloDeadIntervalDefaultMin, 3464 lmpCcHelloDeadIntervalDefaultMax, 3465 lmpCcNbrNodeId, 3466 lmpRemoteCcId, 3467 lmpRemoteCcIpAddrType, 3468 lmpRemoteCcIpAddr, 3469 lmpCcSetupRole, 3470 lmpCcAuthentication, 3471 lmpCcConfigRetransmitInterval, 3472 lmpCcConfigRetransmitTimeout, 3473 lmpCcHelloInterval, 3474 lmpCcHelloIntervalMin, 3475 lmpCcHelloIntervalMax, 3476 lmpCcHelloIntervalNegotiated, 3477 lmpCcHelloDeadInterval, 3478 lmpCcHelloDeadIntervalMin, 3479 lmpCcHelloDeadIntervalMax, 3480 lmpCcHelloDeadIntervalNegotiated, 3481 lmpCcOperStatus, 3482 lmpCcRowStatus, 3483 lmpCcStorageType, 3484 lmpCcUpDownNotifEnable 3485 } 3486 STATUS current 3487 DESCRIPTION 3488 "Collection of objects needed for LMP interface 3489 configuration." 3490 ::= { lmpGroups 2 } 3492 lmpControlChannelIsInterfaceGroup OBJECT-GROUP 3493 OBJECTS { lmpCcIsIf } 3494 STATUS current 3495 DESCRIPTION 3496 "Objects needed to implement control channels that are 3497 interfaces." 3498 ::= { lmpGroups 3 } 3500 lmpControlChannelIsNotInterfaceGroup OBJECT-GROUP 3501 OBJECTS { 3502 lmpCcUnderlyingIfIndex, 3503 lmpCcIsIf, 3504 lmpCcLastChange, 3505 lmpCcAdminStatus 3506 } 3507 STATUS current 3508 DESCRIPTION 3509 "Objects needed to implement control channels that are not 3510 interfaces." 3511 ::= { lmpGroups 4 } 3513 lmpLinkPropertyCorrelationGroup OBJECT-GROUP 3514 OBJECTS { lmpLinkPropertyMismatchNotifEnable } 3515 STATUS current 3516 DESCRIPTION 3517 "Collection of objects needed to implement the link 3518 property correlation procedure." 3519 ::= { lmpGroups 5 } 3521 lmpLinkVerificationGroup OBJECT-GROUP 3522 OBJECTS { lmpLinkVerificationInterval, 3523 lmpVerifyInterval, 3524 lmpVerifyDeadInterval, 3525 lmpVerifyTransportMechanism, 3526 lmpVerifyAllLinks, 3527 lmpTeLinkBitRate, 3528 lmpTeLinkWavelength, 3529 lmpDataBearingLinkNotifEnable 3530 } 3532 STATUS current 3533 DESCRIPTION 3534 "Collection of objects needed to implement the link 3535 verification procedure." 3536 ::= { lmpGroups 6 } 3538 lmpPerfGroup OBJECT-GROUP 3539 OBJECTS { lmpCcInOctets, 3540 lmpCcInDiscards, 3541 lmpCcInErrors, 3542 lmpCcOutOctets, 3543 lmpCcOutDiscards, 3544 lmpCcOutErrors, 3545 lmpCcConfigReceived, 3546 lmpCcConfigSent, 3547 lmpCcConfigRetransmit, 3548 lmpCcConfigAckReceived, 3549 lmpCcConfigAckSent, 3550 lmpCcConfigNackSent, 3551 lmpCcConfigNackReceived, 3552 lmpCcHelloReceived, 3553 lmpCcHelloSent, 3554 lmpCcBeginVerifyReceived, 3555 lmpCcBeginVerifySent, 3556 lmpCcBeginVerifyRetransmit, 3557 lmpCcBeginVerifyAckReceived, 3558 lmpCcBeginVerifyAckSent, 3559 lmpCcBeginVerifyNackReceived, 3560 lmpCcBeginVerifyNackSent, 3561 lmpCcEndVerifyReceived, 3562 lmpCcEndVerifySent, 3563 lmpCcEndVerifyRetransmit, 3564 lmpCcEndVerifyAckReceived, 3565 lmpCcEndVerifyAckSent, 3566 lmpCcTestStatusSuccessReceived, 3567 lmpCcTestStatusSuccessSent, 3568 lmpCcTestStatusSuccessRetransmit, 3569 lmpCcTestStatusFailureReceived, 3570 lmpCcTestStatusFailureSent, 3571 lmpCcTestStatusFailureRetransmit, 3572 lmpCcTestStatusAckReceived, 3573 lmpCcTestStatusAckSent, 3574 lmpCcLinkSummaryReceived, 3575 lmpCcLinkSummarySent, 3576 lmpCcLinkSummaryRetransmit, 3577 lmpCcLinkSummaryAckReceived, 3578 lmpCcLinkSummaryAckSent, 3579 lmpCcLinkSummaryNackReceived, 3580 lmpCcLinkSummaryNackSent, 3581 lmpCcChannelStatusReceived, 3582 lmpCcChannelStatusSent, 3583 lmpCcChannelStatusRetransmit, 3584 lmpCcChannelStatusAckReceived, 3585 lmpCcChannelStatusAckSent, 3586 lmpCcChannelStatusRequestReceived, 3587 lmpCcChannelStatusRequestSent, 3588 lmpCcChannelStatusRequestRetransmit, 3589 lmpCcChannelStatusResponseReceived, 3590 lmpCcChannelStatusResponseSent, 3591 lmpCcCounterDiscontinuityTime, 3592 lmpTeLinkInOctets, 3593 lmpTeLinkOutOctets, 3594 lmpTeLinkBeginVerifyReceived, 3595 lmpTeLinkBeginVerifySent, 3596 lmpTeLinkBeginVerifyRetransmit, 3597 lmpTeLinkBeginVerifyAckReceived, 3598 lmpTeLinkBeginVerifyAckSent, 3599 lmpTeLinkBeginVerifyNackReceived, 3600 lmpTeLinkBeginVerifyNackSent, 3601 lmpTeLinkEndVerifyReceived, 3602 lmpTeLinkEndVerifySent, 3603 lmpTeLinkEndVerifyRetransmit, 3604 lmpTeLinkEndVerifyAckReceived, 3605 lmpTeLinkEndVerifyAckSent, 3606 lmpTeLinkTestStatusSuccessReceived, 3607 lmpTeLinkTestStatusSuccessSent, 3608 lmpTeLinkTestStatusSuccessRetransmit, 3609 lmpTeLinkTestStatusFailureReceived, 3610 lmpTeLinkTestStatusFailureSent, 3611 lmpTeLinkTestStatusFailureRetransmit, 3612 lmpTeLinkTestStatusAckReceived, 3613 lmpTeLinkTestStatusAckSent, 3614 lmpTeLinkSummaryReceived, 3615 lmpTeLinkSummarySent, 3616 lmpTeLinkSummaryRetransmit, 3617 lmpTeLinkSummaryAckReceived, 3618 lmpTeLinkSummaryAckSent, 3619 lmpTeLinkSummaryNackReceived, 3620 lmpTeLinkSummaryNackSent, 3621 lmpTeLinkChannelStatusReceived, 3622 lmpTeLinkChannelStatusSent, 3623 lmpTeLinkChannelStatusRetransmit, 3624 lmpTeLinkChannelStatusAckReceived, 3625 lmpTeLinkChannelStatusAckSent, 3626 lmpTeLinkChannelStatusRequestReceived, 3627 lmpTeLinkChannelStatusRequestSent, 3628 lmpTeLinkChannelStatusRequestRetransmit, 3629 lmpTeLinkChannelStatusResponseSent, 3630 lmpTeLinkChannelStatusResponseReceived, 3631 lmpTeLinkCounterDiscontinuityTime, 3632 lmpDataBearingLinkTestReceived, 3633 lmpDataBearingLinkTestSent, 3634 lmpDataBearingLinkActiveTestSuccess, 3635 lmpDataBearingLinkActiveTestFailure, 3636 lmpDataBearingLinkPassiveTestSuccess, 3637 lmpDataBearingLinkPassiveTestFailure, 3638 lmpDataBearingLinkCounterDiscontinuityTime 3639 } 3640 STATUS current 3641 DESCRIPTION 3642 "Collection of objects needed for providing performance 3643 information about LMP interfaces and data-bearing links." 3644 ::= { lmpGroups 7 } 3646 lmpTeLinkGroup OBJECT-GROUP 3647 OBJECTS { lmpTeLinkNbrNodeId, 3648 lmpTeLinkVerification, 3649 lmpTeLinkFaultManagement, 3650 lmpTeLinkDwdm, 3651 lmpTeLinkOperStatus, 3652 lmpTeLinkRowStatus, 3653 lmpTeLinkStorageType, 3654 lmpTeLinkNotifEnable 3655 } 3656 STATUS current 3657 DESCRIPTION 3658 "Collection of objects needed for TE link configuration." 3659 ::= { lmpGroups 8 } 3661 lmpDataBearingLinkGroup OBJECT-GROUP 3662 OBJECTS { lmpDataBearingLinkType, 3663 lmpDataBearingLinkIpAddrType, 3664 lmpDataBearingLinkIpAddr, 3665 lmpDataBearingLinkRemoteIpAddress, 3666 lmpDataBearingLinkRemoteIfId, 3667 lmpDataBearingLinkEncodingType, 3668 lmpDataBearingLinkActiveOperStatus, 3669 lmpDataBearingLinkPassiveOperStatus, 3670 lmpDataBearingLinkRowStatus, 3671 lmpDataBearingLinkStorageType 3672 } 3673 STATUS current 3674 DESCRIPTION 3675 "Collection of objects needed for data-bearing link 3676 configuration." 3677 ::= { lmpGroups 9 } 3679 lmpNotificationGroup NOTIFICATION-GROUP 3680 NOTIFICATIONS { lmpTeLinkPropertyMismatch, 3681 lmpDataBearingLinkPropertyMismatch, 3682 lmpUnprotected, 3683 lmpControlChannelUp, 3684 lmpControlChannelDown, 3685 lmpTeLinkDegraded, 3686 lmpTeLinkNotDegraded, 3687 lmpDataBearingLinkVerificationFailure } 3688 STATUS current 3689 DESCRIPTION 3690 "Set of notifications implemented in this module. 3691 None is mandatory." 3692 ::= { lmpGroups 10 } 3694 -- End of LMP-MIB 3695 END 3697 11. Security Considerations 3699 It is clear that this MIB is potentially useful for monitoring of LMP 3700 enabled devices. This MIB can also be used for configuration of cer- 3701 tain objects, and anything that can be configured can be incorrectly 3702 configured, with potentially disastrous results. 3704 At this writing, no security holes have been identified beyond those 3705 that SNMP Security [RFC2571] is itself intended to address. These 3706 relate to primarily controlled access to sensitive information and 3707 the ability to configure a device - or which might result from opera- 3708 tor error, which is beyond the scope of any security architecture. 3710 There are a number of management objects defined in this MIB which 3711 have a MAX-ACCESS clause of read-write and/or read-create. Such 3712 objects may be considered sensitive or vulnerable in some network 3713 environments. The support for SET operations in a non-secure environ- 3714 ment without proper protection can have a negative effect on network 3715 operations. The use of SNMP Version 3 is recommended over prior ver- 3716 sions, for configuration control, as its security model is improved. 3718 SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if 3719 the network itself is secure (for example by using IPSec [IPSEC]), 3720 there is no control as to who on the secure network is allowed to 3721 access and GET/SET (read/change/create/delete) the objects in this 3722 MIB. It is recommended that the implementers consider the security 3723 features as provided by the SNMPv3 framework. Specifically, the use 3724 of the User-based Security Model [RFC2574] and the View-based Access 3725 Control [RFC2575] is recommended. It is then a customer/user respon- 3726 sibility to ensure that the SNMP entity giving access to an instance 3727 of this MIB is properly configured to give access to the objects only 3728 to those principals (users) that have legitimate rights to indeed GET 3729 or SET (change/create/delete) them. 3731 There are a number of managed objects in this MIB that may contain 3732 information that may be sensitive from a business perspective, in 3733 that they can be used to derive the network topology, e.g. list of 3734 nodes and their IP address (lmpNbrTable) and list of data-bearing 3735 links (lmpDataBearingLinkTable). Allowing uncontrolled access to 3736 these objects could result in malicious and unwanted disruptions of 3737 network traffic, incorrect network configurations or theft of com- 3738 petitive business information. There are no objects that are particu- 3739 larly sensitive in their own right, such as passwords or monetary 3740 amounts. 3742 12. Acknowledgments 3744 The general structure of this draft has been modeled around draft- 3745 ietf-mpls-lsr-mib-06.txt. 3747 The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and 3748 George Wang. 3750 13. References 3752 [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., 3753 Rekhter, Y., Berger, L., Saha, S., Basak, D., 3754 Sandick, H., Zinin, A., and Rajagopalan, B., 3755 "Link Management Protocol", Internet Draft 3756 , March 2002. 3758 [GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L., 3759 Bernstein, G., Drake, J., Fan, Y., Kompella, K., 3760 Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., 3761 Saha, D., Sharma, V., Swallow, G., and Tang, Z., 3762 "Generalized MPLS Signaling Function Description", 3763 Internet Draft 3764 , 3765 April 2002. 3767 [BUNDLE] Kompella, K., Rekhter, Y., and Berger, L., 3768 "Link Bundling in MPLS Traffic Engineering", 3769 Internet Draft , 3770 May 2002. 3772 [BUNDLE-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J., 3773 "Link Bundling Management Information Base", 3774 Internet Draft , 3775 May 2002. 3777 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 3778 RFC 1700, October 1994. See also: 3779 http://www.isi.edu/in-notes/iana/assignments/smi- 3780 numbers 3782 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 3783 FAMILY NUMBERS, (http://www.isi.edu/in- 3784 notes/iana/assignements/address-family-numbers), 3785 for MIB see: 3786 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 3788 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 3789 Architecture for Describing SNMP Management 3790 Frameworks", RFC 2571, April 1999. 3792 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 3793 Identification of Management Information for TCP/IP- 3794 based Internets", STD 16, RFC 1155, May 1990. 3796 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 3797 STD 16, RFC 1212, March 1991. 3799 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 3800 the SNMP", RFC 1215, March 1991. 3802 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 3803 J., Rose, M., and S. Waldbusser, "Structure of 3804 Management Information Version 2 (SMIv2)", STD 58, 3805 RFC 2578, April 1999. 3807 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 3808 J., Rose, M., and S. Waldbusser, "Textual Conventions 3809 for SMIv2", STD 58, RFC 2579, April 1999. 3811 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 3812 J., Rose, M., and S. Waldbusser, "Conformance 3813 Statements for SMIv2", STD 58, RFC 2580, April 1999. 3815 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 3816 "Simple Network Management Protocol", STD 15, RFC 1157, 3817 May 1990. 3819 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3820 "Introduction to Community-based SNMPv2", RFC 1901, 3821 January 1996. 3823 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3824 "Transport Mappings for Version 2 of the Simple Network 3825 Management Protocol (SNMPv2)", RFC 1906, January 1996. 3827 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 3828 "Message Processing and Dispatching for the Simple 3829 Network Management Protocol (SNMP)", RFC 2572, April 3830 1999. 3832 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 3833 Model (USM) for version 3 of the Simple Network 3834 Management Protocol (SNMPv3)", RFC 2574, April 1999. 3836 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3837 "Protocol Operations for Version 2 of the Simple 3838 Network Management Protocol (SNMPv2)", RFC 1905, 3839 January 1996. 3841 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 3842 Applications", RFC 2573, April 1999. 3844 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 3845 Access Control Model (VACM) for the Simple Network 3846 Management Protocol (SNMP)", RFC 2575, April 1999. 3848 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 3849 "Introduction to Version 3 of the Internet-standard 3850 Network Management Framework", RFC 2570, April 1999. 3852 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 3853 for the Internet Protocol", RFC 2401, November 3854 1998. 3856 [IFMIB] McCloghrie, K., and Kastenholtz, F., "The Interfaces 3857 Group MIB", RFC 2863, June 2000. 3859 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 3860 Requirement Levels", BCP 14, RFC 2119, March 1997. 3862 14. Authors' Addresses 3864 Martin Dubuc Jonathan P. Lang 3865 Meriton Networks Calient Networks, Inc. 3866 3026 Solandt Road 25 Castilian Drive 3867 Kanata, ON, CANADA K2K 2A5 Goleta, CA 93117 3868 Phone: +1-613-270-9279 x253 Email: jplang@calient.net 3869 Email: martin.dubuc@meriton.com 3871 Sudheer Dharanikota Evan McGinnis 3872 Nayna Networks, Inc. Calient Networks, Inc. 3873 157 Topaz Street 5853 Rue Ferrari 3874 Milipitas, CA 95035 San Jose, CA 95138 3875 Phone: +1-408-956-8000 x357 Email: evan@calient.net 3876 Email: sudheer@nayna.com 3878 Thomas D. Nadeau 3879 Cisco Systems, Inc. 3880 300 Apollo Drive 3881 Chelmsford, MA 01824 3882 Phone: +1-978-244-3051 3883 Email: tnadeau@cisco.com 3885 15. Full Copyright Statement 3887 Copyright (C) The Internet Society (2001). All Rights Reserved. 3889 This document and translations of it may be copied and furnished to 3890 others, and derivative works that comment on or otherwise explain it 3891 or assist in its implementation may be prepared, copied, published 3892 and distributed, in whole or in part, without restriction of any 3893 kind, provided that the above copyright notice and this paragraph are 3894 included on all such copies and derivative works. However, this docu- 3895 ment itself may not be modified in any way, such as by removing the 3896 copyright notice or references to the Internet Society or other 3897 Internet organizations, except as needed for the purpose of develop- 3898 ing Internet standards in which case the procedures for copyrights 3899 defined in the Internet Standards process must be followed, or as 3900 required to translate it into languages other than English. 3902 The limited permissions granted above are perpetual and will not be 3903 revoked by the Internet Society or its successors or assigns. This 3904 document and the information contained herein is provided on an "AS 3905 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 3906 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 3907 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 3908 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 3909 OR FITNESS FOR A PARTICULAR PURPOSE.