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