idnits 2.17.1 draft-ietf-ccamp-rfc4327bis-01.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 3899. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3910. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3917. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3923. ** 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? -- The abstract seems to indicate that this document obsoletes RFC4327, but the header doesn't have an 'Obsoletes:' line to match this. 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 (February 2006) is 6639 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 (==), 9 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 Obsoletes 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 February 2006 13 Link Management Protocol (LMP) Management Information Base (MIB) 15 draft-ietf-ccamp-rfc4327bis-01.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 and obsoletes 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. Changes from RFC 4327 to RFC XXXX .............................78 80 15. References ....................................................78 81 15.1. Normative References .....................................78 82 15.2. Informative References ...................................79 83 16. Authors' Addresses ............................................79 85 1. The Internet-Standard Management Framework 87 For a detailed overview of the documents that describe the current 88 Internet-Standard Management Framework, please refer to section 7 of 89 RFC 3410 [RFC3410]. 91 Managed objects are accessed via a virtual information store, termed 92 the Management Information Base or MIB. MIB objects are generally 93 accessed through the Simple Network Management Protocol (SNMP). 94 Objects in the MIB are defined using the mechanisms defined in the 95 Structure of Management Information (SMI). This memo specifies a MIB 96 module that is compliant to the SMIv2, which is described in STD 58, 97 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 98 [RFC2580]. 100 2. Introduction 102 Current work is under way in the IETF to specify a suite of protocols 103 to be used as a common control plane and a separate common 104 measurement plane. Generalized MPLS (GMPLS) [RFC3471] and the Link 105 Management Protocol [RFC4204] are key components of this 106 standardization activity. The primary purpose of LMP is to manage 107 traffic engineering (TE) links. Primary goals of LMP are the 108 maintenance of the control channel connectivity, correlation of link 109 properties, verification of data-bearing links, and detection and 110 isolation of link faults. 112 We describe in this document a MIB module that can be used to manage 113 LMP implementations. This MIB module covers both configuration and 114 performance monitoring aspects of LMP. 116 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 117 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 118 document are to be interpreted as described in RFC 2119 [RFC2119]. 120 3. Terminology 122 This document uses terminology from the document describing the Link 123 Management Protocol [RFC4204]. An "LMP adjacency" is formed between 124 two nodes that support the same capabilities, and LMP messages are 125 exchanged between the node pair over control channels that form this 126 adjacency. Several control channels can be active at the same time. 127 With the exception of messages related to control channel management, 128 anytime an LMP message needs to be transferred to a neighbor node, it 129 can be sent on any of the active control channels. The control 130 channels can also be used to exchange MPLS control plane information 131 or routing information. 133 LMP is designed to support aggregation of one or more data-bearing 134 links into a traffic-engineering (TE) link. The data-bearing links 135 can be either component links or ports depending on their 136 multiplexing capability (see [RFC4204] for distinction between port 137 and component link). 139 Each TE link is associated with an LMP adjacency, and one or more 140 control channels are used to exchange LMP messages for a particular 141 adjacency. In turn, control channels are used to manage the TE links 142 associated with the LMP adjacency. 144 4. Feature Checklist 146 The Link Management Protocol MIB module (LMP-MIB) is designed to 147 satisfy the following requirements and constraints: 149 - The MIB module supports the enabling and disabling of LMP 150 capability on LMP-capable interfaces of a photonic switch, optical 151 cross-connect, or router. 153 - The MIB module is used to provide information about LMP 154 adjacencies. 156 - Support is provided for configuration of the keep alive and link 157 verification parameters. 159 - The MIB module is used to express the mapping between local and 160 remote TE links, as well as local and remote interface identifiers 161 for port or component link. 163 - Performance counters are provided for measuring LMP performance on 164 a per-control channel basis. Performance counters are also 165 provided for measuring LMP performance on the data-bearing links. 167 Note that the LMP MIB module goes hand-in-hand with the TE Link 168 (TE-LINK-STD-MIB) MIB module [RFC4220]. The TE link table, which is 169 used to associate data-bearing links to TE links, is defined in the 170 TE Link MIB. The TE link table in the LMP MIB module contains TE 171 link information specific to LMP. 173 5. Outline 175 Configuring LMP through an optical device involves the following 176 steps: 178 - Enabling LMP on LMP-capable interfaces through control channel 179 configuration. 181 - Optionally specifying link verification parameters. 183 - Configuring the data-bearing links and associating them to the 184 appropriate TE link (this association is stored in the 185 ifStackTable of the Interfaces Group MIB). 187 TE links are managed by the control channels that run between the 188 same pair of nodes (LMP adjacency). 190 6. Brief Description of MIB Objects 192 Sections 6.1-6.8 describe objects pertaining to LMP. The MIB objects 193 were derived from the LMP document [RFC4204]. 195 6.1. lmpNbrTable 197 The remote node table is used to identify the pair of nodes that 198 exchange LMP messages over control channels. 200 6.2. lmpControlChannelTable 202 The control channel table is used for enabling the LMP protocol on 203 LMP-capable interfaces. A photonic switch, optical cross-connect, or 204 router creates an entry in this table for every LMP-capable interface 205 in that device. 207 6.3. lmpControlChannelPerfTable 209 The control channel performance table is used for collecting LMP 210 performance counts on a per-control channel basis. Each entry in the 211 lmpControlChannelTable has a corresponding entry in the 212 lmpControlChannelPerfTable. 214 6.4. lmpTeLinkTable 216 The TE link table is used for specifying LMP information associated 217 with TE links. 219 6.5. lmpLinkVerificationTable 221 The link verification table is used for configuring the LMP link 222 verification parameters of TE links. For every TE link entry in the 223 lmpTeLinkTable that supports the link verification procedure, there 224 is a corresponding entry in the lmpLinkVerificationTable. 226 6.6. lmpTeLinkPerfTable 228 The TE link performance table is used for collecting LMP performance 229 counts on a per-TE link basis. Each entry in the lmpTeLinkTable has 230 a corresponding entry in the lmpTeLinkPerfTable. 232 6.7. lmpDataLinkTable 234 The data-bearing link table is used to specify the data-bearing links 235 that are associated with TE links. 237 6.8. lmpDataLinkPerfTable 239 The data-bearing link performance table is used for collecting LMP 240 performance counts on data-bearing links. 242 7. Example of LMP Control Channel Setup 244 In this section, we provide a brief example of using the MIB 245 objects described in section 9 to set up an LMP control channel. 246 While this example is not meant to illustrate every nuance of the 247 MIB module, it is intended as an aid to understanding some of the 248 key concepts. It is meant to be read after going through the MIB 249 itself. 251 Suppose that one would like to form an LMP adjacency between two 252 nodes using two control channels. Suppose also that there are 253 three data-bearing links. We also assume that the data-bearing 254 links are ports (lambdas). We also assume that the link 255 verification procedure is not enabled. The following example 256 illustrates which rows and corresponding objects might be created 257 to accomplish this. 259 First, LMP must be enabled between the pair of nodes. 261 In lmpNbrTable: 262 { 263 lmpNbrNodeId = 'c0000201'H, -- 192.0.2.1 264 lmpNbrAdminStatus = up(1), 265 lmpNbrRowStatus = createAndGo(4), 266 lmpNbrStorageType = nonVolatile(3) 267 } 269 Then, the control channels must be set up. These are created in 270 the lmpControlChannelTable. 272 In lmpControlChannelTable: 273 { 274 lmpCcId = 1, 275 lmpCcUnderlyingIfIndex = 1, 276 lmpCcIsIf = false(2), 277 lmpCcAuthentication = false(2), 278 lmpCcHelloInterval = 15, 279 lmpCcHelloIntervalMin = 15, 280 lmpCcHelloIntervalMax = 1000, 281 lmpCcHelloDeadInterval = 45, 282 lmpCcHelloDeadIntervalMin = 45, 283 lmpCcHelloDeadIntervalMax = 1000, 284 lmpCcAdminStatus = up(1), 285 lmpCcRowStatus = createAndGo(4), 286 lmpCcStorageType = nonVolatile(3) 287 } 289 { 290 lmpCcId = 2, 291 lmpCcUnderlyingIfIndex = 2, 292 lmpCcIsIf = false(2), 293 lmpCcAuthentication = false(2), 294 lmpCcHelloInterval = 15, 295 lmpCcHelloIntervalMin = 15, 296 lmpCcHelloIntervalMax = 1000, 297 lmpCcHelloDeadInterval = 45, 298 lmpCcHelloDeadIntervalMin = 45, 299 lmpCcHelloDeadIntervalMax = 1000, 300 lmpCcAdminStatus = up(1), 301 lmpCcRowStatus = createAndGo(4), 302 lmpCcStorageType = nonVolatile(3) 303 } 305 Next, the three data-bearing links are created. For each data- 306 bearing link, an ifEntry with the same ifIndex needs to be created 307 beforehand. 309 In lmpDataLinkTable: 310 { 311 ifIndex = 41, 312 lmpDataLinkAddressType = unknown(0), 313 lmpDataLinkIpAddr = ''H, 314 lmpDataLinkRemoteIpAddress = ''H, 315 lmpDataLinkRemoteIfId = 47, 316 lmpDataLinkRowStatus = createAndGo(4), 317 lmpDataLinkStorageType = nonVolatile(3) 318 } 320 { 321 ifIndex = 43, 322 lmpDataLinkAddressType = unknown(0), 323 lmpDataLinkIpAddr = ''H, 324 lmpDataLinkRemoteIpAddress = ''H, 325 lmpDataLinkRemoteIfId = 42, 326 lmpDataLinkRowStatus = createAndGo(4), 327 lmpDataLinkStorageType = nonVolatile(3) 328 } 330 { 331 ifIndex = 44, 332 lmpDataLinkAddressType = unknown(0), 333 lmpDataLinkIpAddr = ''H, 334 lmpDataLinkRemoteIpAddress = ''H, 335 lmpDataLinkRemoteIfId = 48, 336 lmpDataLinkRowStatus = createAndGo(4), 337 lmpDataLinkStorageType = nonVolatile(3) 338 } 340 Note that the data-bearing link type (lmpDataLinkType) does 341 not need to be provisioned as it is automatically populated by the 342 node. The definition of the protection role (primary or 343 secondary) for the data-bearing links is stored in the 344 componentLinkTable of the TE Link MIB module [RFC4220]. 346 Then, a TE link is created as an ifEntry with ifType teLink in 347 the ifTable. 349 Once the TE link is created in the ifTable, a TE link entry 350 is created in the LMP MIB module to specify TE link information 351 specific to LMP. 353 In lmpTeLinkTable: 354 { 355 ifIndex = 20, 356 lmpTeLinkVerification = true(1), 357 lmpTeLinkFaultManagement = true(1), 358 lmpTeLinkDwdm = false(2), 359 lmpTeLinkRowStatus = createAndGo(4), 360 lmpTeLinkStorageType = nonVolatile(3) 361 } 363 and in lmpLinkVerificationTable: 364 { 365 ifIndex = 20, 366 lmpLinkVerifyInterval = 100, 367 lmpLinkVerifyDeadInterval = 300, 368 lmpLinkVerifyTransportMechanism = j0Trace(3), 369 lmpLinkVerifyAllLinks = true(1), 370 lmpLinkVerifyTransmissionRate = 100000, 371 lmpLinkVerifyWavelength = 0, 372 lmpLinkVerifyRowStatus = createAndGo(4), 373 lmpLinkVerifyStorageType = nonVolatile(3) 374 } 376 The association between the data-bearing links and the TE links is 377 stored in the ifStackTable [RFC2863]. 379 In parallel with the entry created in the lmpTeLinkTable, an entry 380 may be created in the teLinkTable of TE Link MIB module 381 [RFC4220]. 383 8. Application of the Interfaces Group to LMP 385 The Interfaces Group [RFC2863] defines generic managed objects for 386 managing interfaces. This memo contains the media-specific 387 extensions to the Interfaces Group for managing LMP control channels 388 that are modeled as interfaces. If the control channel as defined in 389 the lmpControlChannelTable is modeled as an ifEntry, then the 390 following definition applies. An lmpControlChannelTable entry is 391 designated as being represented as an Interfaces MIB ifEntry if the 392 lmpControlChannelEntry object lmpCcIsIf is set to true (1). In this 393 case, the control channel SHOULD be modeled as an ifEntry and 394 provide appropriate interface stacking as defined below. 396 This memo assumes the interpretation of the Interfaces Group to be 397 in accordance with [RFC2863], which states that the interfaces table 398 (ifTable) contains information on the managed resource's 399 interfaces and that each sub-layer below the internetwork layer of 400 a network interface is considered an interface. Since the LMP 401 interface only carries control traffic, it is considered to be below 402 the internetwork layer. Thus, the LMP interface may be represented 403 as an entry in the ifTable. The interrelation of entries in the 404 ifTable is defined by Interfaces Stack Group defined in [RFC2863]. 406 When LMP control channels are modeled as interfaces, the interface 407 stack table must appear as follows for the LMP control channel 408 interfaces: 410 +----------------------------------------+ 411 | LMP-interface ifType = lmp(227) + 412 +----------------------------------------+ 413 | Underlying Layer... + 414 +----------------------------------------+ 416 In the above diagram, "Underlying Layer..." refers to the ifIndex 417 of any interface type over which the LMP interface will transmit 418 its traffic. Note that if the underlying layer provides multiple 419 access to its media (i.e., Ethernet), then it is possible to stack 420 multiple LMP interfaces on top of this interface in parallel. 422 Note that it is not a requirement that LMP control channels be 423 modeled as interfaces. It is acceptable that control channels 424 simply exist as logical connections between adjacent LMP-capable 425 nodes. In this case, lmpCcIsIf is set to false(2) and no 426 corresponding entry is made in the ifTable. 428 8.1. Support of the LMP Layer by ifTable 430 Some specific interpretations of ifTable for the LMP layer 431 follow. 433 Object Use for the LMP layer. 435 ifIndex Each LMP interface may be represented by an ifEntry. 437 ifDescr Description of the LMP interface. 439 ifType The value that is allocated for LMP is 227. 440 This number has been assigned by the IANA. 442 ifSpeed The total bandwidth in bits per second for use by 443 the LMP layer. 445 ifPhysAddress Unused. 447 ifAdminStatus This variable indicates the administrator's intent 448 as to whether LMP should be enabled, disabled, or 449 running in some diagnostic testing mode on this 450 interface. Also see [RFC2863]. 452 ifOperStatus This value reflects the actual or operational 453 status of LMP on this interface. 455 ifLastChange See [RFC2863]. 457 ifInOctets The number of received octets over the interface, 458 i.e., the number of octets received as LMP 459 packets. 461 ifOutOctets The number of transmitted octets over the 462 interface, i.e., the number of octets transmitted 463 as LMP packets. 465 ifInErrors The number of LMP packets dropped due to 466 uncorrectable errors. 468 ifInUnknownProtos 469 The number of received packets discarded during 470 packet header validation, including packets with 471 unrecognized label values. 473 ifOutErrors See [RFC2863]. 475 ifName Textual name (unique on this system) of the 476 interface or an octet string of zero length. 478 ifLinkUpDownTrapEnable 479 Default is disabled (2). 481 ifConnectorPresent 482 Set to false (2). 484 ifHighSpeed See [RFC2863]. 486 ifHCInOctets The 64-bit version of ifInOctets; supported if 487 required by the compliance statements in [RFC2863]. 489 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 490 required by the compliance statements in [RFC2863]. 492 ifAlias The nonvolatile 'alias' name for the interface as 493 specified by a network manager. 495 ifCounterDiscontinuityTime 496 See [RFC2863]. 498 9. LMP MIB Module Definitions 500 This MIB module IMPORTs objects from [RFC2578], [RFC2579], [RFC2580], 501 [RFC2863], [RFC4001], and [RFC4220], and it has REFERENCE clauses to 502 [RFC4204], [RFC4207], [RFC4209], [RFC3471], and [RFC2914]. 504 LMP-MIB DEFINITIONS ::= BEGIN 506 IMPORTS 507 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 508 transmission, Unsigned32, Counter32, TimeTicks 509 FROM SNMPv2-SMI -- RFC 2578 511 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 512 FROM SNMPv2-CONF -- RFC 2580 514 TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, 515 TimeStamp 516 FROM SNMPv2-TC -- RFC 2579 518 InterfaceIndexOrZero, ifIndex 519 FROM IF-MIB -- RFC 2863 521 InetAddressType, InetAddress 522 FROM INET-ADDRESS-MIB -- RFC 4001 524 teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType 525 FROM TE-LINK-STD-MIB; -- RFC 4220 527 lmpMIB MODULE-IDENTITY 528 LAST-UPDATED "200602190000Z" -- 19 February 2006 529 ORGANIZATION "Common Control and Measurement Protocols (CCAMP) 530 Working Group" 531 CONTACT-INFO 532 " Martin Dubuc 533 Email: dubuc.consulting@sympatico.ca 535 Thomas D. Nadeau 536 Email: tnadeau@cisco.com 538 Jonathan P. Lang 539 Email: jplang@ieee.org 541 Evan McGinnis 542 Email: emcginnis@hammerheadsystems.com 544 Adrian Farrel 545 Email: adrian@olddog.co.uk" 547 DESCRIPTION 548 "Copyright (C) 2006 The Internet Society. This version of 549 the MIB module is part of RFC XXXX; see the RFC itself 550 for full legal notices. 551 -- RFC Editor. Please replace XXXX with new RFC number and remove 552 -- this note. 554 This MIB module contains managed object definitions for 555 the Link Management Protocol (LMP) as 556 defined in 'Link Management Protocol'." 558 -- Revision history. 559 REVISION 560 "200602190000Z" -- 19 February 2006 561 DESCRIPTION 562 "Revised version to: 563 - fix textual descriptions of TruthValue settings such that True 564 is always 1, and False is always 2. 565 - add punctuation to REFERENCE clauses. 567 This revision published as RFC XXXX" 568 -- RFC Editor. Please replace XXXX with new RFC number and remove 569 -- this note. 570 REVISION 571 "200601110000Z" -- 11 January 2006 572 DESCRIPTION 573 "Initial version published as RFC 4327" 574 ::= { transmission 227 } 576 -- Textual Conventions 578 LmpInterval ::= TEXTUAL-CONVENTION 579 DISPLAY-HINT "d" 580 STATUS current 581 DESCRIPTION 582 "The interval delay in milliseconds." 583 SYNTAX Unsigned32 (1..65535) 585 LmpRetransmitInterval ::= TEXTUAL-CONVENTION 586 DISPLAY-HINT "d" 587 STATUS current 588 DESCRIPTION 589 "The retransmission interval delay in milliseconds." 590 SYNTAX Unsigned32 (1..4294967295) 592 LmpNodeId ::= TEXTUAL-CONVENTION 593 DISPLAY-HINT "1d.1d.1d.1d" 594 STATUS current 595 DESCRIPTION 596 "Represents a Node ID in network byte order. Node ID is an 597 address of type IPv4." 598 REFERENCE 599 "Section 1.1 of Link Management Protocol, RFC 4204." 600 SYNTAX OCTET STRING(SIZE(4)) 602 -- Top level components of this MIB 604 -- Notifications 605 lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 } 606 -- Tables, Scalars 607 lmpObjects OBJECT IDENTIFIER ::= { lmpMIB 1 } 608 -- Conformance 609 lmpConformance OBJECT IDENTIFIER ::= { lmpMIB 2 } 611 lmpAdminStatus OBJECT-TYPE 612 SYNTAX INTEGER { up(1), down(2) } 613 MAX-ACCESS read-write 614 STATUS current 615 DESCRIPTION 616 "The desired operational status of LMP on the node. 617 Implementations should save the value of this object in 618 persistent memory so that it survives restarts or reboot." 619 DEFVAL { up } 620 ::= { lmpObjects 1 } 622 lmpOperStatus OBJECT-TYPE 623 SYNTAX INTEGER { up(1), down(2) } 624 MAX-ACCESS read-only 625 STATUS current 626 DESCRIPTION 627 "The actual operational status of LMP on the node." 628 ::= { lmpObjects 2 } 630 -- LMP Neighbor Table 632 lmpNbrTable OBJECT-TYPE 633 SYNTAX SEQUENCE OF LmpNbrEntry 634 MAX-ACCESS not-accessible 635 STATUS current 636 DESCRIPTION 637 "This table specifies the neighbor node(s) to which control 638 channels may be established." 639 ::= { lmpObjects 3 } 641 lmpNbrEntry OBJECT-TYPE 642 SYNTAX LmpNbrEntry 643 MAX-ACCESS not-accessible 644 STATUS current 645 DESCRIPTION 646 "An entry in this table is created by a LMP-enabled device for 647 every pair of nodes that can establish control channels." 648 INDEX { lmpNbrNodeId } 649 ::= { lmpNbrTable 1 } 651 LmpNbrEntry ::= SEQUENCE { 652 lmpNbrNodeId LmpNodeId, 653 lmpNbrRetransmitInterval LmpRetransmitInterval, 654 lmpNbrRetryLimit Unsigned32, 655 lmpNbrRetransmitDelta Unsigned32, 656 lmpNbrAdminStatus INTEGER, 657 lmpNbrOperStatus INTEGER, 658 lmpNbrRowStatus RowStatus, 659 lmpNbrStorageType StorageType 660 } 662 lmpNbrNodeId OBJECT-TYPE 663 SYNTAX LmpNodeId 664 MAX-ACCESS not-accessible 665 STATUS current 666 DESCRIPTION 667 "This is a unique index for an entry in the LmpNbrTable. 668 This value represents the remote Node ID." 669 ::= { lmpNbrEntry 1 } 671 lmpNbrRetransmitInterval OBJECT-TYPE 672 SYNTAX LmpRetransmitInterval 673 MAX-ACCESS read-create 674 STATUS current 675 DESCRIPTION 676 "This object specifies the initial retransmission interval that 677 is used for the retransmission of messages that require 678 acknowledgement. This object along with lmpNbrRetryLimit is 679 used to implement congestion-handling mechanism as defined in 680 Section 10 of the Link Management Protocol specification, 681 which is based on RFC 2914." 682 REFERENCE 683 "Link Management Protocol, RFC 4204. 685 Congestion Control Principles, RFC 2914." 686 DEFVAL { 500 } 687 ::= { lmpNbrEntry 2 } 689 lmpNbrRetryLimit OBJECT-TYPE 690 SYNTAX Unsigned32 691 MAX-ACCESS read-create 692 STATUS current 693 DESCRIPTION 694 "This object specifies the maximum number of times a message 695 is transmitted without being acknowledged. A value of 0 is used 696 to indicate that a node should never stop retransmission. 698 This object along with lmpNbrRetransmitInterval is 699 used to implement congestion-handling mechanism as defined in 700 Section 10 of the Link Management Protocol specification, 701 which is based on RFC 2914." 702 REFERENCE 703 "Link Management Protocol, RFC 4204. 704 Congestion Control Principles, RFC 2914." 705 DEFVAL { 3 } 706 ::= { lmpNbrEntry 3 } 708 lmpNbrRetransmitDelta OBJECT-TYPE 709 SYNTAX Unsigned32 710 MAX-ACCESS read-create 711 STATUS current 712 DESCRIPTION 713 "This object governs the speed with which the sender increases 714 the retransmission interval as explained in section 10 of the 715 Link Management Protocol specification, which is based on 716 RFC 2914. This value is a power used to express the 717 exponential backoff. The ratio of two successive retransmission 718 intervals is (1 + Delta)." 719 REFERENCE 720 "Link Management Protocol, RFC 4204. 721 Congestion Control Principles, RFC 2914." 722 DEFVAL { 1 } 723 ::= { lmpNbrEntry 4 } 725 lmpNbrAdminStatus OBJECT-TYPE 726 SYNTAX INTEGER { up(1), down(2) } 727 MAX-ACCESS read-create 728 STATUS current 729 DESCRIPTION 730 "The desired operational status of LMP to this remote node." 731 ::= { lmpNbrEntry 5 } 733 lmpNbrOperStatus OBJECT-TYPE 734 SYNTAX INTEGER { up(1), down(2) } 735 MAX-ACCESS read-only 736 STATUS current 737 DESCRIPTION 738 "The actual operational status of LMP to this remote node." 739 ::= { lmpNbrEntry 6 } 741 lmpNbrRowStatus OBJECT-TYPE 742 SYNTAX RowStatus 743 MAX-ACCESS read-create 744 STATUS current 745 DESCRIPTION 746 "This variable is used to create, modify, and/or 747 delete a row in this table. None of the writable objects 748 in a row can be changed if the status is active(1). 749 All read-create objects must have valid and consistent 750 values before the row can be activated." 751 ::= { lmpNbrEntry 7 } 753 lmpNbrStorageType OBJECT-TYPE 754 SYNTAX StorageType 755 MAX-ACCESS read-create 756 STATUS current 757 DESCRIPTION 758 "The storage type for this conceptual row in the 759 lmpNbrTable. Conceptual rows having the value 760 'permanent' need not allow write-access to any 761 columnar object in the row." 762 DEFVAL { nonVolatile } 763 ::= { lmpNbrEntry 8 } 765 -- End of lmpNbrTable 767 lmpCcHelloIntervalDefault OBJECT-TYPE 768 SYNTAX LmpInterval 769 MAX-ACCESS read-write 770 STATUS current 771 DESCRIPTION 772 "This object specifies the default value for the HelloInterval 773 parameter used in the Hello protocol keep-alive phase. It 774 indicates how frequently LMP Hello messages will be sent. It 775 is used a the default value for lmpCcHelloInterval. 776 Implementations should save the value of this object in 777 persistent memory so that it survives restarts or reboot." 778 REFERENCE 779 "Link Management Protocol, RFC 4204." 780 ::= { lmpObjects 4 } 782 lmpCcHelloIntervalDefaultMin OBJECT-TYPE 783 SYNTAX LmpInterval 784 MAX-ACCESS read-write 785 STATUS current 786 DESCRIPTION 787 "This object specifies the default minimum value for the 788 HelloInterval parameter. It is used as a default value 789 for lmpCcHelloIntervalMin. Implementations should save the 790 value of this object in persistent memory so that it survives 791 restarts or reboot." 792 ::= { lmpObjects 5 } 794 lmpCcHelloIntervalDefaultMax OBJECT-TYPE 795 SYNTAX LmpInterval 796 MAX-ACCESS read-write 797 STATUS current 798 DESCRIPTION 799 "This object specifies the default maximum value for the 800 HelloInterval parameter. It is used as a default value 801 for lmpCcHelloIntervalMax. Implementations should save the 802 value of this object in persistent memory so that it survives 803 restarts or reboot." 804 ::= { lmpObjects 6 } 806 lmpCcHelloDeadIntervalDefault OBJECT-TYPE 807 SYNTAX LmpInterval 808 MAX-ACCESS read-write 809 STATUS current 810 DESCRIPTION 811 "This object specifies the default HelloDeadInterval parameter 812 to use in the Hello protocol keep-alive phase. It indicates 813 how long a device should wait before declaring the control 814 channel dead. The HelloDeadInterval parameter should be at 815 least three times the value of HelloInterval. It is used as 816 a default value for lmpCcHelloDeadInterval. Implementations 817 should save the value of this object in persistent memory so 818 that it survives restarts or reboot." 819 REFERENCE 820 "Link Management Protocol, RFC 4204." 821 ::= { lmpObjects 7 } 823 lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE 824 SYNTAX LmpInterval 825 MAX-ACCESS read-write 826 STATUS current 827 DESCRIPTION 828 "This object specifies the default minimum value for the 829 HelloDeadInterval parameter. It is used as a default value 830 for lmpCcHelloDeadIntervalMin. Implementations should save 831 the value of this object in persistent memory so that it 832 survives restarts or reboot." 833 ::= { lmpObjects 8 } 835 lmpCcHelloDeadIntervalDefaultMax OBJECT-TYPE 836 SYNTAX LmpInterval 837 MAX-ACCESS read-write 838 STATUS current 839 DESCRIPTION 840 "This object specifies the default maximum value for the 841 HelloDeadInterval parameter. It is used as a default value 842 for lmpCcHelloDeadIntervalMax. Implementations should save the 843 value of this object in persistent memory so that it survives 844 restarts or reboot." 845 ::= { lmpObjects 9 } 847 -- LMP Control Channel Table 849 lmpControlChannelTable OBJECT-TYPE 850 SYNTAX SEQUENCE OF LmpControlChannelEntry 851 MAX-ACCESS not-accessible 852 STATUS current 853 DESCRIPTION 854 "This table specifies LMP control channel information." 855 ::= { lmpObjects 10 } 857 lmpControlChannelEntry OBJECT-TYPE 858 SYNTAX LmpControlChannelEntry 859 MAX-ACCESS not-accessible 860 STATUS current 861 DESCRIPTION 862 "An entry in this table is created by a LMP-enabled device for 863 every control channel. Whenever a new entry is created with 864 lmpCcIsIf set to true(1), then a corresponding entry is 865 created in ifTable as well (see RFC 2863)." 866 INDEX { lmpCcId } 867 ::= { lmpControlChannelTable 1 } 869 LmpControlChannelEntry ::= SEQUENCE { 870 lmpCcId Unsigned32, 871 lmpCcUnderlyingIfIndex InterfaceIndexOrZero, 872 lmpCcIsIf TruthValue, 873 lmpCcNbrNodeId LmpNodeId, 874 lmpCcRemoteId Unsigned32, 875 lmpCcRemoteAddressType InetAddressType, 876 lmpCcRemoteIpAddr InetAddress, 877 lmpCcSetupRole INTEGER, 878 lmpCcAuthentication TruthValue, 879 lmpCcHelloInterval LmpInterval, 880 lmpCcHelloIntervalMin LmpInterval, 881 lmpCcHelloIntervalMax LmpInterval, 882 lmpCcHelloIntervalNegotiated LmpInterval, 883 lmpCcHelloDeadInterval LmpInterval, 884 lmpCcHelloDeadIntervalMin LmpInterval, 885 lmpCcHelloDeadIntervalMax LmpInterval, 886 lmpCcHelloDeadIntervalNegotiated LmpInterval, 887 lmpCcLastChange TimeTicks, 888 lmpCcAdminStatus INTEGER, 889 lmpCcOperStatus INTEGER, 890 lmpCcRowStatus RowStatus, 891 lmpCcStorageType StorageType 892 } 893 lmpCcId OBJECT-TYPE 894 SYNTAX Unsigned32 (1..4294967295) 895 MAX-ACCESS not-accessible 896 STATUS current 897 DESCRIPTION 898 "This value represents the local control channel identifier. 899 The control channel identifier is a non-zero 32-bit number." 900 ::= { lmpControlChannelEntry 1 } 902 lmpCcUnderlyingIfIndex OBJECT-TYPE 903 SYNTAX InterfaceIndexOrZero 904 MAX-ACCESS read-create 905 STATUS current 906 DESCRIPTION 907 "If lmpCcIsIf is set to true(1), this object carries the 908 index into the ifTable of the entry that represents the 909 LMP interface over which LMP will transmit its traffic. 910 If this object is set to zero, but lmpCcIsIf is set to 911 true(1), the control channel is not currently associated 912 with any underlying interface and the control channel's 913 operational status must not be up(1), nor should the 914 control channel forward or receive traffic. 915 If lmpCcIsIf is set to false(2), this object should be set 916 to zero and should be ignored." 917 ::= { lmpControlChannelEntry 2 } 919 lmpCcIsIf OBJECT-TYPE 920 SYNTAX TruthValue 921 MAX-ACCESS read-create 922 STATUS current 923 DESCRIPTION 924 "In implementations where the control channels are modeled 925 as interfaces, the value of this object is true(1) and 926 this control channel is represented by an interface in 927 the interfaces group table as indicated by the value of 928 lmpCcUnderlyingIfIndex. If control channels are not 929 modeled as interfaces, the value of this object is 930 false(2) and there is no corresponding interface for 931 this control channel in the interfaces group table, 932 and the value of lmpCcUnderlyingIfIndex should be 933 ignored." 934 ::= { lmpControlChannelEntry 3 } 936 lmpCcNbrNodeId OBJECT-TYPE 937 SYNTAX LmpNodeId 938 MAX-ACCESS read-create 939 STATUS current 940 DESCRIPTION 941 "This is the Node ID of the control channel remote node. 942 This value either is configured or gets created by the node 943 when a Config message is received or when an outgoing Config 944 message is acknowledged by the remote node." 945 ::= { lmpControlChannelEntry 4 } 947 lmpCcRemoteId OBJECT-TYPE 948 SYNTAX Unsigned32 949 MAX-ACCESS read-only 950 STATUS current 951 DESCRIPTION 952 "This value represents the remote control channel identifier 953 (32-bit number). It is determined during the negotiation 954 phase. A value of zero means that the remote control channel 955 identifier has not yet been learnt." 956 ::= { lmpControlChannelEntry 5 } 958 lmpCcRemoteAddressType OBJECT-TYPE 959 SYNTAX InetAddressType 960 MAX-ACCESS read-create 961 STATUS current 962 DESCRIPTION 963 "This value represents the remote control channel IP address 964 type. In point-to-point configuration, this value can be set 965 to unknown(0)." 966 ::= { lmpControlChannelEntry 6 } 968 lmpCcRemoteIpAddr OBJECT-TYPE 969 SYNTAX InetAddress 970 MAX-ACCESS read-create 971 STATUS current 972 DESCRIPTION 973 "This value represents the remote control channel Internet 974 address for numbered control channel. The type of this 975 address is determined by lmpCcRemoteAddressType. 976 Control channel must be numbered on non-point-to-point 977 configuration. For point-to-point configuration, the 978 remote control channel address can be of type unknown 979 in which case this object must be a zero-length string. The 980 lmpCcRemoteId object then identifies the unnumbered 981 address." 982 ::= { lmpControlChannelEntry 7 } 984 lmpCcSetupRole OBJECT-TYPE 985 SYNTAX INTEGER { active(1), passive(2) } 986 MAX-ACCESS read-create 987 STATUS current 988 DESCRIPTION 989 "The role that this node should take during establishment 990 of this control channel. An active node will initiate 991 establishment. A passive node will wait for the remote node 992 to initiate. A pair of nodes that both take the passive role 993 will never establish communications." 994 DEFVAL { active } 995 ::= { lmpControlChannelEntry 8 } 997 lmpCcAuthentication OBJECT-TYPE 998 SYNTAX TruthValue 999 MAX-ACCESS read-create 1000 STATUS current 1001 DESCRIPTION 1002 "This object indicates whether the control channel must use 1003 authentication." 1004 REFERENCE 1005 "Link Management Protocol, RFC 4204." 1006 ::= { lmpControlChannelEntry 9 } 1008 lmpCcHelloInterval OBJECT-TYPE 1009 SYNTAX LmpInterval 1010 MAX-ACCESS read-create 1011 STATUS current 1012 DESCRIPTION 1013 "This object specifies the value of the HelloInterval 1014 parameter. The default value for this object should be 1015 set to lmpCcHelloIntervalDefault." 1016 ::= { lmpControlChannelEntry 10 } 1018 lmpCcHelloIntervalMin OBJECT-TYPE 1019 SYNTAX LmpInterval 1020 MAX-ACCESS read-create 1021 STATUS current 1022 DESCRIPTION 1023 "This object specifies the minimum value for the 1024 HelloInterval parameter. The default value for this 1025 object should be set to lmpCcHelloIntervalMinDefault." 1026 ::= { lmpControlChannelEntry 11 } 1028 lmpCcHelloIntervalMax OBJECT-TYPE 1029 SYNTAX LmpInterval 1030 MAX-ACCESS read-create 1031 STATUS current 1032 DESCRIPTION 1033 "This object specifies the maximum value for the 1034 HelloInterval parameter. The default value for this 1035 object should be set to lmpCcHelloIntervalMaxDefault." 1036 ::= { lmpControlChannelEntry 12 } 1038 lmpCcHelloIntervalNegotiated OBJECT-TYPE 1039 SYNTAX LmpInterval 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "Once the control channel is active, this object represents 1044 the negotiated HelloInterval value." 1045 ::= { lmpControlChannelEntry 13 } 1047 lmpCcHelloDeadInterval OBJECT-TYPE 1048 SYNTAX LmpInterval 1049 MAX-ACCESS read-create 1050 STATUS current 1051 DESCRIPTION 1052 "This object specifies the value of the HelloDeadInterval 1053 parameter. The default value for this object should be 1054 set to lmpCcHelloDeadIntervalDefault." 1055 ::= { lmpControlChannelEntry 14 } 1057 lmpCcHelloDeadIntervalMin OBJECT-TYPE 1058 SYNTAX LmpInterval 1059 MAX-ACCESS read-create 1060 STATUS current 1061 DESCRIPTION 1062 "This object specifies the minimum value for the 1063 HelloDeadInterval parameter. The default value for this 1064 object should be set to lmpCcHelloDeadIntervalMinDefault." 1065 ::= { lmpControlChannelEntry 15 } 1067 lmpCcHelloDeadIntervalMax OBJECT-TYPE 1068 SYNTAX LmpInterval 1069 MAX-ACCESS read-create 1070 STATUS current 1071 DESCRIPTION 1072 "This object specifies the maximum value for the 1073 HelloDeadInterval parameter. The default value for this 1074 object should be set to lmpCcHelloIntervalMaxDefault." 1075 ::= { lmpControlChannelEntry 16 } 1077 lmpCcHelloDeadIntervalNegotiated OBJECT-TYPE 1078 SYNTAX LmpInterval 1079 MAX-ACCESS read-only 1080 STATUS current 1081 DESCRIPTION 1082 "Once the control channel is active, this object represents 1083 the negotiated HelloDeadInterval value." 1084 ::= { lmpControlChannelEntry 17 } 1086 lmpCcLastChange OBJECT-TYPE 1087 SYNTAX TimeTicks 1088 MAX-ACCESS read-only 1089 STATUS current 1090 DESCRIPTION 1091 "The value of sysUpTime at the time the control channel entered 1092 its current operational state. If the current state was 1093 entered prior to the last re-initialization of the local 1094 network management subsystem, then this object contains a 1095 zero value." 1096 ::= { lmpControlChannelEntry 18 } 1098 lmpCcAdminStatus OBJECT-TYPE 1099 SYNTAX INTEGER { up(1), down(2) } 1100 MAX-ACCESS read-create 1101 STATUS current 1102 DESCRIPTION 1103 "The desired operational status of this control channel." 1104 ::= { lmpControlChannelEntry 19 } 1106 lmpCcOperStatus OBJECT-TYPE 1107 SYNTAX INTEGER { 1108 up(1), 1109 down(2), 1110 configSnd(3), 1111 configRcv(4), 1112 active(5), 1113 goingDown(6) 1114 } 1115 MAX-ACCESS read-only 1116 STATUS current 1117 DESCRIPTION 1118 "The actual operational status of this control channel." 1119 ::= { lmpControlChannelEntry 20 } 1121 lmpCcRowStatus OBJECT-TYPE 1122 SYNTAX RowStatus 1123 MAX-ACCESS read-create 1124 STATUS current 1125 DESCRIPTION 1126 "This variable is used to create, modify, and/or 1127 delete a row in this table. None of the writable objects 1128 in a row can be changed if the status is active(1). 1129 All read-create objects must have valid and consistent 1130 values before the row can be activated." 1131 ::= { lmpControlChannelEntry 21 } 1133 lmpCcStorageType OBJECT-TYPE 1134 SYNTAX StorageType 1135 MAX-ACCESS read-create 1136 STATUS current 1137 DESCRIPTION 1138 "The storage type for this conceptual row in the 1139 lmpControlChannelTable. Conceptual rows having the value 1140 'permanent' need not allow write-access to any 1141 columnar object in the row." 1143 DEFVAL { nonVolatile } 1144 ::= { lmpControlChannelEntry 22 } 1146 -- End of lmpControlChannelTable 1148 -- LMP Control Channel Performance Table 1150 lmpControlChannelPerfTable OBJECT-TYPE 1151 SYNTAX SEQUENCE OF LmpControlChannelPerfEntry 1152 MAX-ACCESS not-accessible 1153 STATUS current 1154 DESCRIPTION 1155 "This table specifies LMP control channel performance 1156 counters." 1157 ::= { lmpObjects 11 } 1159 lmpControlChannelPerfEntry OBJECT-TYPE 1160 SYNTAX LmpControlChannelPerfEntry 1161 MAX-ACCESS not-accessible 1162 STATUS current 1163 DESCRIPTION 1164 "An entry in this table is created by a LMP-enabled device for 1165 every control channel. lmpCcCounterDiscontinuityTime is used 1166 to indicate potential discontinuity for all counter objects 1167 in this table." 1168 INDEX { lmpCcId } 1169 ::= { lmpControlChannelPerfTable 1 } 1171 LmpControlChannelPerfEntry ::= SEQUENCE { 1172 lmpCcInOctets Counter32, 1173 lmpCcInDiscards Counter32, 1174 lmpCcInErrors Counter32, 1175 lmpCcOutOctets Counter32, 1176 lmpCcOutDiscards Counter32, 1177 lmpCcOutErrors Counter32, 1178 lmpCcConfigReceived Counter32, 1179 lmpCcConfigSent Counter32, 1180 lmpCcConfigRetransmit Counter32, 1181 lmpCcConfigAckReceived Counter32, 1182 lmpCcConfigAckSent Counter32, 1183 lmpCcConfigNackReceived Counter32, 1184 lmpCcConfigNackSent Counter32, 1185 lmpCcHelloReceived Counter32, 1186 lmpCcHelloSent Counter32, 1187 lmpCcBeginVerifyReceived Counter32, 1188 lmpCcBeginVerifySent Counter32, 1189 lmpCcBeginVerifyRetransmit Counter32, 1190 lmpCcBeginVerifyAckReceived Counter32, 1191 lmpCcBeginVerifyAckSent Counter32, 1192 lmpCcBeginVerifyNackReceived Counter32, 1193 lmpCcBeginVerifyNackSent Counter32, 1194 lmpCcEndVerifyReceived Counter32, 1195 lmpCcEndVerifySent Counter32, 1196 lmpCcEndVerifyRetransmit Counter32, 1197 lmpCcEndVerifyAckReceived Counter32, 1198 lmpCcEndVerifyAckSent Counter32, 1199 lmpCcTestStatusSuccessReceived Counter32, 1200 lmpCcTestStatusSuccessSent Counter32, 1201 lmpCcTestStatusSuccessRetransmit Counter32, 1202 lmpCcTestStatusFailureReceived Counter32, 1203 lmpCcTestStatusFailureSent Counter32, 1204 lmpCcTestStatusFailureRetransmit Counter32, 1205 lmpCcTestStatusAckReceived Counter32, 1206 lmpCcTestStatusAckSent Counter32, 1207 lmpCcLinkSummaryReceived Counter32, 1208 lmpCcLinkSummarySent Counter32, 1209 lmpCcLinkSummaryRetransmit Counter32, 1210 lmpCcLinkSummaryAckReceived Counter32, 1211 lmpCcLinkSummaryAckSent Counter32, 1212 lmpCcLinkSummaryNackReceived Counter32, 1213 lmpCcLinkSummaryNackSent Counter32, 1214 lmpCcChannelStatusReceived Counter32, 1215 lmpCcChannelStatusSent Counter32, 1216 lmpCcChannelStatusRetransmit Counter32, 1217 lmpCcChannelStatusAckReceived Counter32, 1218 lmpCcChannelStatusAckSent Counter32, 1219 lmpCcChannelStatusReqReceived Counter32, 1220 lmpCcChannelStatusReqSent Counter32, 1221 lmpCcChannelStatusReqRetransmit Counter32, 1222 lmpCcChannelStatusRspReceived Counter32, 1223 lmpCcChannelStatusRspSent Counter32, 1224 lmpCcCounterDiscontinuityTime TimeStamp 1225 } 1227 lmpCcInOctets OBJECT-TYPE 1228 SYNTAX Counter32 1229 MAX-ACCESS read-only 1230 STATUS current 1231 DESCRIPTION 1232 "The total number of LMP message octets received on the 1233 control channel." 1234 ::= { lmpControlChannelPerfEntry 1 } 1236 lmpCcInDiscards OBJECT-TYPE 1237 SYNTAX Counter32 1238 MAX-ACCESS read-only 1239 STATUS current 1240 DESCRIPTION 1241 "The number of inbound packets that were chosen to be 1242 discarded even though no errors had been detected. One 1243 possible reason for discarding such a packet could be to 1244 free up buffer space." 1245 ::= { lmpControlChannelPerfEntry 2 } 1247 lmpCcInErrors OBJECT-TYPE 1248 SYNTAX Counter32 1249 MAX-ACCESS read-only 1250 STATUS current 1251 DESCRIPTION 1252 "The number of inbound packets that contained errors 1253 preventing them from being processed by LMP." 1254 ::= { lmpControlChannelPerfEntry 3 } 1256 lmpCcOutOctets OBJECT-TYPE 1257 SYNTAX Counter32 1258 MAX-ACCESS read-only 1259 STATUS current 1260 DESCRIPTION 1261 "The total number of LMP message octets transmitted out of 1262 the control channel." 1263 ::= { lmpControlChannelPerfEntry 4 } 1265 lmpCcOutDiscards OBJECT-TYPE 1266 SYNTAX Counter32 1267 MAX-ACCESS read-only 1268 STATUS current 1269 DESCRIPTION 1270 "The number of outbound packets that were chosen to be 1271 discarded even though no errors had been detected to 1272 prevent their being transmitted. One possible reason 1273 for discarding such a packet could be to free up buffer 1274 space." 1275 ::= { lmpControlChannelPerfEntry 5 } 1277 lmpCcOutErrors OBJECT-TYPE 1278 SYNTAX Counter32 1279 MAX-ACCESS read-only 1280 STATUS current 1281 DESCRIPTION 1282 "The number of outbound packets that could not be 1283 transmitted because of errors." 1284 ::= { lmpControlChannelPerfEntry 6 } 1286 lmpCcConfigReceived OBJECT-TYPE 1287 SYNTAX Counter32 1288 MAX-ACCESS read-only 1289 STATUS current 1290 DESCRIPTION 1291 "This object counts the number of Config messages that have 1292 been received on this control channel." 1293 ::= { lmpControlChannelPerfEntry 7 } 1295 lmpCcConfigSent 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 sent on this control channel." 1302 ::= { lmpControlChannelPerfEntry 8 } 1304 lmpCcConfigRetransmit 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 1310 have been retransmitted over this control channel." 1311 ::= { lmpControlChannelPerfEntry 9 } 1313 lmpCcConfigAckReceived OBJECT-TYPE 1314 SYNTAX Counter32 1315 MAX-ACCESS read-only 1316 STATUS current 1317 DESCRIPTION 1318 "This object counts the number of ConfigAck messages that have 1319 been received on this control channel." 1320 ::= { lmpControlChannelPerfEntry 10 } 1322 lmpCcConfigAckSent 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 sent on this control channel." 1329 ::= { lmpControlChannelPerfEntry 11 } 1331 lmpCcConfigNackReceived OBJECT-TYPE 1332 SYNTAX Counter32 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "This object counts the number of ConfigNack messages that have 1337 been received on this control channel." 1338 ::= { lmpControlChannelPerfEntry 12 } 1340 lmpCcConfigNackSent 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 sent on this control channel." 1347 ::= { lmpControlChannelPerfEntry 13 } 1349 lmpCcHelloReceived OBJECT-TYPE 1350 SYNTAX Counter32 1351 MAX-ACCESS read-only 1352 STATUS current 1353 DESCRIPTION 1354 "This object counts the number of Hello messages that have 1355 been received on this control channel." 1356 ::= { lmpControlChannelPerfEntry 14 } 1358 lmpCcHelloSent 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 sent on this control channel." 1365 ::= { lmpControlChannelPerfEntry 15 } 1367 lmpCcBeginVerifyReceived OBJECT-TYPE 1368 SYNTAX Counter32 1369 MAX-ACCESS read-only 1370 STATUS current 1371 DESCRIPTION 1372 "This object counts the number of BeginVerify messages that have 1373 been received on this control channel." 1374 ::= { lmpControlChannelPerfEntry 16 } 1376 lmpCcBeginVerifySent 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 sent on this control channel." 1383 ::= { lmpControlChannelPerfEntry 17 } 1385 lmpCcBeginVerifyRetransmit 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 1391 have been retransmitted over this control channel." 1392 ::= { lmpControlChannelPerfEntry 18 } 1394 lmpCcBeginVerifyAckReceived OBJECT-TYPE 1395 SYNTAX Counter32 1396 MAX-ACCESS read-only 1397 STATUS current 1398 DESCRIPTION 1399 "This object counts the number of BeginVerifyAck messages that 1400 have been received on this control channel." 1401 ::= { lmpControlChannelPerfEntry 19 } 1403 lmpCcBeginVerifyAckSent 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 sent on this control channel." 1410 ::= { lmpControlChannelPerfEntry 20 } 1412 lmpCcBeginVerifyNackReceived OBJECT-TYPE 1413 SYNTAX Counter32 1414 MAX-ACCESS read-only 1415 STATUS current 1416 DESCRIPTION 1417 "This object counts the number of BeginVerifyNack messages that 1418 have been received on this control channel." 1419 ::= { lmpControlChannelPerfEntry 21 } 1421 lmpCcBeginVerifyNackSent 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 sent on this control channel." 1428 ::= { lmpControlChannelPerfEntry 22 } 1430 lmpCcEndVerifyReceived OBJECT-TYPE 1431 SYNTAX Counter32 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "This object counts the number of EndVerify messages that have 1436 been received on this control channel." 1437 ::= { lmpControlChannelPerfEntry 23 } 1439 lmpCcEndVerifySent 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 sent on this control channel." 1446 ::= { lmpControlChannelPerfEntry 24 } 1448 lmpCcEndVerifyRetransmit 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 1454 have been retransmitted over this control channel." 1455 ::= { lmpControlChannelPerfEntry 25 } 1457 lmpCcEndVerifyAckReceived OBJECT-TYPE 1458 SYNTAX Counter32 1459 MAX-ACCESS read-only 1460 STATUS current 1461 DESCRIPTION 1462 "This object counts the number of EndVerifyAck messages that 1463 have been received on this control channel." 1464 ::= { lmpControlChannelPerfEntry 26 } 1466 lmpCcEndVerifyAckSent 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 sent on this control channel." 1473 ::= { lmpControlChannelPerfEntry 27 } 1475 lmpCcTestStatusSuccessReceived OBJECT-TYPE 1476 SYNTAX Counter32 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "This object counts the number of TestStatusSuccess messages 1481 that have been received on this control channel." 1482 ::= { lmpControlChannelPerfEntry 28 } 1484 lmpCcTestStatusSuccessSent 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 sent on this control channel." 1491 ::= { lmpControlChannelPerfEntry 29 } 1493 lmpCcTestStatusSuccessRetransmit 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 retransmitted over this control channel." 1500 ::= { lmpControlChannelPerfEntry 30 } 1502 lmpCcTestStatusFailureReceived OBJECT-TYPE 1503 SYNTAX Counter32 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "This object counts the number of TestStatusFailure messages 1508 that have been received on this control channel." 1509 ::= { lmpControlChannelPerfEntry 31 } 1511 lmpCcTestStatusFailureSent 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 sent on this control channel." 1518 ::= { lmpControlChannelPerfEntry 32 } 1520 lmpCcTestStatusFailureRetransmit 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 retransmitted over this control channel." 1527 ::= { lmpControlChannelPerfEntry 33 } 1529 lmpCcTestStatusAckReceived OBJECT-TYPE 1530 SYNTAX Counter32 1531 MAX-ACCESS read-only 1532 STATUS current 1533 DESCRIPTION 1534 "This object counts the number of TestStatusAck messages 1535 that have been received on this control channel." 1536 ::= { lmpControlChannelPerfEntry 34 } 1538 lmpCcTestStatusAckSent 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 sent on this control channel." 1545 ::= { lmpControlChannelPerfEntry 35 } 1547 lmpCcLinkSummaryReceived OBJECT-TYPE 1548 SYNTAX Counter32 1549 MAX-ACCESS read-only 1550 STATUS current 1551 DESCRIPTION 1552 "This object counts the number of LinkSummary messages 1553 that have been received on this control channel." 1554 ::= { lmpControlChannelPerfEntry 36 } 1556 lmpCcLinkSummarySent 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 sent on this control channel." 1563 ::= { lmpControlChannelPerfEntry 37 } 1565 lmpCcLinkSummaryRetransmit OBJECT-TYPE 1566 SYNTAX Counter32 1567 MAX-ACCESS read-only 1568 STATUS current 1569 DESCRIPTION 1570 "This object counts the number of LinkSummary messages that 1571 have been retransmitted over this control channel." 1572 ::= { lmpControlChannelPerfEntry 38 } 1574 lmpCcLinkSummaryAckReceived OBJECT-TYPE 1575 SYNTAX Counter32 1576 MAX-ACCESS read-only 1577 STATUS current 1578 DESCRIPTION 1579 "This object counts the number of LinkSummaryAck messages 1580 that have been received on this control channel." 1581 ::= { lmpControlChannelPerfEntry 39 } 1583 lmpCcLinkSummaryAckSent 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 sent on this control channel." 1590 ::= { lmpControlChannelPerfEntry 40 } 1592 lmpCcLinkSummaryNackReceived OBJECT-TYPE 1593 SYNTAX Counter32 1594 MAX-ACCESS read-only 1595 STATUS current 1596 DESCRIPTION 1597 "This object counts the number of LinkSummaryNack messages 1598 that have been received on this control channel." 1599 ::= { lmpControlChannelPerfEntry 41 } 1601 lmpCcLinkSummaryNackSent 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 sent on this control channel." 1608 ::= { lmpControlChannelPerfEntry 42 } 1610 lmpCcChannelStatusReceived OBJECT-TYPE 1611 SYNTAX Counter32 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "This object counts the number of ChannelStatus messages 1616 that have been received on this control channel." 1617 ::= { lmpControlChannelPerfEntry 43 } 1619 lmpCcChannelStatusSent 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 sent on this control channel." 1626 ::= { lmpControlChannelPerfEntry 44 } 1628 lmpCcChannelStatusRetransmit 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 retransmitted on this control channel." 1635 ::= { lmpControlChannelPerfEntry 45 } 1637 lmpCcChannelStatusAckReceived OBJECT-TYPE 1638 SYNTAX Counter32 1639 MAX-ACCESS read-only 1640 STATUS current 1641 DESCRIPTION 1642 "This object counts the number of ChannelStatusAck messages 1643 that have been received on this control channel." 1644 ::= { lmpControlChannelPerfEntry 46 } 1646 lmpCcChannelStatusAckSent OBJECT-TYPE 1647 SYNTAX Counter32 1648 MAX-ACCESS read-only 1649 STATUS current 1650 DESCRIPTION 1651 "This object counts the number of ChannelStatus messages 1652 that have been sent on this control channel." 1653 ::= { lmpControlChannelPerfEntry 47 } 1655 lmpCcChannelStatusReqReceived OBJECT-TYPE 1656 SYNTAX Counter32 1657 MAX-ACCESS read-only 1658 STATUS current 1659 DESCRIPTION 1660 "This object counts the number of ChannelStatusRequest messages 1661 that have been received on this control channel." 1662 ::= { lmpControlChannelPerfEntry 48 } 1664 lmpCcChannelStatusReqSent 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 sent on this control channel." 1671 ::= { lmpControlChannelPerfEntry 49 } 1673 lmpCcChannelStatusReqRetransmit 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 retransmitted on this control channel." 1680 ::= { lmpControlChannelPerfEntry 50 } 1682 lmpCcChannelStatusRspReceived OBJECT-TYPE 1683 SYNTAX Counter32 1684 MAX-ACCESS read-only 1685 STATUS current 1686 DESCRIPTION 1687 "This object counts the number of ChannelStatusResponse messages 1688 that have been received on this control channel." 1689 ::= { lmpControlChannelPerfEntry 51 } 1691 lmpCcChannelStatusRspSent 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 sent on this control channel." 1698 ::= { lmpControlChannelPerfEntry 52 } 1700 lmpCcCounterDiscontinuityTime OBJECT-TYPE 1701 SYNTAX TimeStamp 1702 MAX-ACCESS read-only 1703 STATUS current 1704 DESCRIPTION 1705 "The value of sysUpTime on the most recent occasion at which 1706 any one or more of this control channel's counters suffered a 1707 discontinuity. The relevant counters are the specific 1708 instances associated with this control channel of any 1709 Counter32 object contained in the lmpControlChannelPerfTable. 1710 If no such discontinuities have occurred since the last re- 1711 initialization of the local management subsystem, then this 1712 object contains a zero value." 1713 ::= { lmpControlChannelPerfEntry 53 } 1715 -- End of lmpControlChannelPerfTable 1717 -- LMP TE Link Table 1719 lmpTeLinkTable OBJECT-TYPE 1720 SYNTAX SEQUENCE OF LmpTeLinkEntry 1721 MAX-ACCESS not-accessible 1722 STATUS current 1723 DESCRIPTION 1724 "This table specifies the LMP-specific TE link information. 1725 Overall TE link information is kept in three separate tables: 1726 ifTable for interface-specific information, lmpTeLinkTable 1727 for LMP specific information, and teLinkTable for generic 1728 TE link information. ifIndex is the common index to all 1729 tables." 1730 ::= { lmpObjects 12 } 1732 lmpTeLinkEntry OBJECT-TYPE 1733 SYNTAX LmpTeLinkEntry 1734 MAX-ACCESS not-accessible 1735 STATUS current 1736 DESCRIPTION 1737 "An entry in this table exists for each ifEntry with an 1738 ifType of teLink(200) that is managed by LMP. An ifEntry with 1739 an ifIndex must exist before the corresponding lmpTeLinkEntry is 1740 created. If a TE link entry in the ifTable is destroyed, then 1741 so is the corresponding entry in the lmpTeLinkTable. The 1742 administrative status value is controlled from the ifEntry. 1743 Setting the administrative status to testing prompts LMP to 1744 start link verification on the TE link. Information about the 1745 TE link that is not LMP specific is contained in teLinkTable of 1746 the TE-LINK-STD-MIB MIB module." 1747 INDEX { ifIndex } 1748 ::= { lmpTeLinkTable 1 } 1750 LmpTeLinkEntry ::= SEQUENCE { 1751 lmpTeLinkNbrRemoteNodeId LmpNodeId, 1752 lmpTeLinkVerification TruthValue, 1753 lmpTeLinkFaultManagement TruthValue, 1754 lmpTeLinkDwdm TruthValue, 1755 lmpTeLinkOperStatus INTEGER, 1756 lmpTeLinkRowStatus RowStatus, 1757 lmpTeLinkStorageType StorageType 1758 } 1760 lmpTeLinkNbrRemoteNodeId OBJECT-TYPE 1761 SYNTAX LmpNodeId 1762 MAX-ACCESS read-create 1763 STATUS current 1764 DESCRIPTION 1765 "This is the Node ID of the TE link remote node. This value 1766 may be learned during control channel parameter negotiation 1767 phase (in the Config message). Node ID is an address whose 1768 type must be IPv4." 1769 ::= { lmpTeLinkEntry 1 } 1771 lmpTeLinkVerification OBJECT-TYPE 1772 SYNTAX TruthValue 1773 MAX-ACCESS read-create 1774 STATUS current 1775 DESCRIPTION 1776 "This object indicates if the LMP link verification procedure 1777 is enabled for this TE link." 1778 REFERENCE 1779 "Link Management Protocol, RFC 4204." 1780 ::= { lmpTeLinkEntry 2 } 1782 lmpTeLinkFaultManagement OBJECT-TYPE 1783 SYNTAX TruthValue 1784 MAX-ACCESS read-create 1785 STATUS current 1786 DESCRIPTION 1787 "This object indicates if the LMP fault management procedure 1788 is enabled on this TE link." 1789 REFERENCE 1790 "Link Management Protocol, RFC 4204." 1791 ::= { lmpTeLinkEntry 3 } 1793 lmpTeLinkDwdm OBJECT-TYPE 1794 SYNTAX TruthValue 1795 MAX-ACCESS read-create 1796 STATUS current 1797 DESCRIPTION 1798 "This object indicates if the LMP DWDM procedure is enabled 1799 on this TE link." 1800 REFERENCE 1801 "Link Management Protocol (LMP) for Dense Wavelength Division 1802 Multiplexing (DWDM) Optical Line Systems, RFC 4209." 1803 ::= { lmpTeLinkEntry 4 } 1805 lmpTeLinkOperStatus OBJECT-TYPE 1806 SYNTAX INTEGER { 1807 up(1), down(2), testing(3), init(4), degraded(5) 1808 } 1809 MAX-ACCESS read-only 1810 STATUS current 1811 DESCRIPTION 1812 "The actual operational status of this TE link. The status 1813 is set to testing when the TE link is performing link 1814 verification. A degraded state indicates that there is 1815 no active control channel between the pair of nodes that 1816 form the endpoints of the TE link, but yet at least one 1817 data-bearing link on the TE link is allocated." 1818 ::= { lmpTeLinkEntry 5 } 1820 lmpTeLinkRowStatus OBJECT-TYPE 1821 SYNTAX RowStatus 1822 MAX-ACCESS read-create 1823 STATUS current 1824 DESCRIPTION 1825 "This variable is used to create, modify, and/or 1826 delete a row in this table. None of the writable objects 1827 in a row can be changed if the status is active(1). 1828 All read-create objects must have valid and consistent 1829 values before the row can be activated." 1830 ::= { lmpTeLinkEntry 6 } 1832 lmpTeLinkStorageType OBJECT-TYPE 1833 SYNTAX StorageType 1834 MAX-ACCESS read-create 1835 STATUS current 1836 DESCRIPTION 1837 "The storage type for this conceptual row in the 1838 lmpTeLinkTable. Conceptual rows having the value 1839 'permanent' need not allow write-access to any 1840 columnar object in the row." 1841 DEFVAL { nonVolatile } 1842 ::= { lmpTeLinkEntry 7 } 1844 -- End of lmpTeLinkTable 1846 lmpGlobalLinkVerificationInterval OBJECT-TYPE 1847 SYNTAX Unsigned32 1848 UNITS "milliseconds" 1849 MAX-ACCESS read-write 1850 STATUS current 1851 DESCRIPTION 1852 "This object indicates how often the link verification 1853 procedure is executed. The interval is in milliseconds. 1854 A value of 0 is used to indicate that the link 1855 verification procedure should not be executed. The 1856 interval specified in this object should be large enough 1857 to allow the verification procedure to be completed 1858 before the start of the next interval. 1859 Implementations should save the value of this object in 1860 persistent memory so that it survives restarts or reboot." 1861 ::= { lmpObjects 13 } 1863 -- LMP Link Verification Table 1865 lmpLinkVerificationTable OBJECT-TYPE 1866 SYNTAX SEQUENCE OF LmpLinkVerificationEntry 1867 MAX-ACCESS not-accessible 1868 STATUS current 1869 DESCRIPTION 1870 "This table specifies TE link information associated with the 1871 LMP verification procedure." 1872 ::= { lmpObjects 14 } 1874 lmpLinkVerificationEntry OBJECT-TYPE 1875 SYNTAX LmpLinkVerificationEntry 1876 MAX-ACCESS not-accessible 1877 STATUS current 1878 DESCRIPTION 1879 "An entry in this table is created by an LMP-enabled device for 1880 every TE link that supports the LMP verification 1881 procedure." 1882 INDEX { ifIndex } 1883 ::= { lmpLinkVerificationTable 1 } 1885 LmpLinkVerificationEntry ::= SEQUENCE { 1886 lmpLinkVerifyInterval LmpInterval, 1887 lmpLinkVerifyDeadInterval LmpInterval, 1888 lmpLinkVerifyTransportMechanism BITS, 1889 lmpLinkVerifyAllLinks TruthValue, 1890 lmpLinkVerifyTransmissionRate Unsigned32, 1891 lmpLinkVerifyWavelength Unsigned32, 1892 lmpLinkVerifyRowStatus RowStatus, 1893 lmpLinkVerifyStorageType StorageType 1894 } 1896 lmpLinkVerifyInterval OBJECT-TYPE 1897 SYNTAX LmpInterval 1898 MAX-ACCESS read-create 1899 STATUS current 1900 DESCRIPTION 1901 "This object specifies the VerifyInterval parameter used 1902 in the LMP link verification process. It indicates the 1903 interval at which the Test messages are sent." 1904 REFERENCE 1905 "Link Management Protocol, RFC 4204." 1906 ::= { lmpLinkVerificationEntry 1 } 1908 lmpLinkVerifyDeadInterval OBJECT-TYPE 1909 SYNTAX LmpInterval 1910 MAX-ACCESS read-create 1911 STATUS current 1912 DESCRIPTION 1913 "This object specifies the VerifyDeadInterval parameter used 1914 in the verification of the physical connectivity of data- 1915 bearing links. It specifies the observation period used to 1916 detect a Test message at the remote node." 1917 REFERENCE 1918 "Link Management Protocol, RFC 4204." 1919 ::= { lmpLinkVerificationEntry 2 } 1921 lmpLinkVerifyTransportMechanism OBJECT-TYPE 1922 SYNTAX BITS { 1923 -- All encoding types: 1924 payload(0), 1925 -- SONET/SDH encoding type: 1926 dccSectionOverheadBytes(1), 1927 dccLineOverheadBytes(2), 1928 j0Trace(3), 1929 j1Trace(4), 1930 j2Trace(5) 1931 } 1932 MAX-ACCESS read-create 1933 STATUS current 1934 DESCRIPTION 1935 "This defines the transport mechanism for the Test messages. The 1936 scope of this bit mask is restricted to each link encoding 1937 type. The local node will set the bits corresponding to the 1938 various mechanisms it can support for transmitting LMP Test 1939 messages. The receiver chooses the appropriate mechanism in the 1940 BeginVerifyAck message." 1941 REFERENCE 1942 "Link Management Protocol, RFC 4204 1943 Synchronous Optical Network (SONET)/Synchronous Digital 1944 Hierarchy (SDH) Encoding for Link Management Protocol (LMP) 1945 Test Messages, RFC 4207." 1946 ::= { lmpLinkVerificationEntry 3 } 1948 lmpLinkVerifyAllLinks OBJECT-TYPE 1949 SYNTAX TruthValue 1950 MAX-ACCESS read-create 1951 STATUS current 1952 DESCRIPTION 1953 "A value of true(1) for this object indicates that the 1954 verification process checks all unallocated links, otherwise 1955 only the new ports or component links that have been added to 1956 this TE link are verified." 1957 ::= { lmpLinkVerificationEntry 4 } 1959 lmpLinkVerifyTransmissionRate OBJECT-TYPE 1960 SYNTAX Unsigned32 1961 UNITS "bytes per second" 1962 MAX-ACCESS read-create 1963 STATUS current 1964 DESCRIPTION 1965 "This is the transmission rate of the data link over which 1966 the Test messages will be transmitted and is expressed in 1967 bytes per second." 1968 REFERENCE 1969 "Link Management Protocol, RFC 4204." 1970 ::= { lmpLinkVerificationEntry 5 } 1972 lmpLinkVerifyWavelength OBJECT-TYPE 1973 SYNTAX Unsigned32 1974 UNITS "nanometers" 1975 MAX-ACCESS read-create 1976 STATUS current 1977 DESCRIPTION 1978 "This value corresponds to the wavelength at 1979 which the Test messages will be transmitted and is 1980 measured in nanometers (nm). If each data-bearing link 1981 corresponds to a separate wavelength, then this value should 1982 be set to 0." 1984 REFERENCE 1985 "Link Management Protocol, RFC 4204." 1986 ::= { lmpLinkVerificationEntry 6 } 1988 lmpLinkVerifyRowStatus OBJECT-TYPE 1989 SYNTAX RowStatus 1990 MAX-ACCESS read-create 1991 STATUS current 1992 DESCRIPTION 1993 "This variable is used to create, modify, and/or 1994 delete a row in this table. None of the writable objects 1995 in a row can be changed if the status is active(1). 1996 All read-create objects must have valid and consistent 1997 values before the row can be activated." 1998 ::= { lmpLinkVerificationEntry 7 } 2000 lmpLinkVerifyStorageType OBJECT-TYPE 2001 SYNTAX StorageType 2002 MAX-ACCESS read-create 2003 STATUS current 2004 DESCRIPTION 2005 "The storage type for this conceptual row in the 2006 lmpLinkVerificationTable. Conceptual rows having the value 2007 'permanent' need not allow write-access to any 2008 columnar object in the row." 2009 DEFVAL { nonVolatile } 2010 ::= { lmpLinkVerificationEntry 8 } 2012 -- End of lmpLinkVerificationTable 2014 -- LMP TE Link Performance Table 2016 lmpTeLinkPerfTable OBJECT-TYPE 2017 SYNTAX SEQUENCE OF LmpTeLinkPerfEntry 2018 MAX-ACCESS not-accessible 2019 STATUS current 2020 DESCRIPTION 2021 "This table specifies LMP TE link performance counters." 2022 ::= { lmpObjects 15 } 2024 lmpTeLinkPerfEntry OBJECT-TYPE 2025 SYNTAX LmpTeLinkPerfEntry 2026 MAX-ACCESS not-accessible 2027 STATUS current 2028 DESCRIPTION 2029 "An entry in this table is created by an LMP-enabled device for 2030 every TE link. lmpTeCounterDiscontinuityTime is used 2031 to indicate potential discontinuity for all counter objects 2032 in this table." 2034 INDEX { ifIndex } 2035 ::= { lmpTeLinkPerfTable 1 } 2037 LmpTeLinkPerfEntry ::= SEQUENCE { 2038 lmpTeInOctets Counter32, 2039 lmpTeOutOctets Counter32, 2040 lmpTeBeginVerifyReceived Counter32, 2041 lmpTeBeginVerifySent Counter32, 2042 lmpTeBeginVerifyRetransmit Counter32, 2043 lmpTeBeginVerifyAckReceived Counter32, 2044 lmpTeBeginVerifyAckSent Counter32, 2045 lmpTeBeginVerifyNackReceived Counter32, 2046 lmpTeBeginVerifyNackSent Counter32, 2047 lmpTeEndVerifyReceived Counter32, 2048 lmpTeEndVerifySent Counter32, 2049 lmpTeEndVerifyRetransmit Counter32, 2050 lmpTeEndVerifyAckReceived Counter32, 2051 lmpTeEndVerifyAckSent Counter32, 2052 lmpTeTestStatusSuccessReceived Counter32, 2053 lmpTeTestStatusSuccessSent Counter32, 2054 lmpTeTestStatusSuccessRetransmit Counter32, 2055 lmpTeTestStatusFailureReceived Counter32, 2056 lmpTeTestStatusFailureSent Counter32, 2057 lmpTeTestStatusFailureRetransmit Counter32, 2058 lmpTeTestStatusAckReceived Counter32, 2059 lmpTeTestStatusAckSent Counter32, 2060 lmpTeLinkSummaryReceived Counter32, 2061 lmpTeLinkSummarySent Counter32, 2062 lmpTeLinkSummaryRetransmit Counter32, 2063 lmpTeLinkSummaryAckReceived Counter32, 2064 lmpTeLinkSummaryAckSent Counter32, 2065 lmpTeLinkSummaryNackReceived Counter32, 2066 lmpTeLinkSummaryNackSent Counter32, 2067 lmpTeChannelStatusReceived Counter32, 2068 lmpTeChannelStatusSent Counter32, 2069 lmpTeChannelStatusRetransmit Counter32, 2070 lmpTeChannelStatusAckReceived Counter32, 2071 lmpTeChannelStatusAckSent Counter32, 2072 lmpTeChannelStatusReqReceived Counter32, 2073 lmpTeChannelStatusReqSent Counter32, 2074 lmpTeChannelStatusReqRetransmit Counter32, 2075 lmpTeChannelStatusRspReceived Counter32, 2076 lmpTeChannelStatusRspSent Counter32, 2077 lmpTeCounterDiscontinuityTime TimeStamp 2078 } 2080 lmpTeInOctets OBJECT-TYPE 2081 SYNTAX Counter32 2082 MAX-ACCESS read-only 2083 STATUS current 2084 DESCRIPTION 2085 "The total number of LMP message octets received for 2086 this TE link." 2087 ::= { lmpTeLinkPerfEntry 1 } 2089 lmpTeOutOctets OBJECT-TYPE 2090 SYNTAX Counter32 2091 MAX-ACCESS read-only 2092 STATUS current 2093 DESCRIPTION 2094 "The total number of LMP message octets transmitted out 2095 for this TE link." 2096 ::= { lmpTeLinkPerfEntry 2 } 2098 lmpTeBeginVerifyReceived OBJECT-TYPE 2099 SYNTAX Counter32 2100 MAX-ACCESS read-only 2101 STATUS current 2102 DESCRIPTION 2103 "This object counts the number of BeginVerify messages that have 2104 been received for this TE link." 2105 ::= { lmpTeLinkPerfEntry 3 } 2107 lmpTeBeginVerifySent 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 sent for this TE link." 2114 ::= { lmpTeLinkPerfEntry 4 } 2116 lmpTeBeginVerifyRetransmit 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 2122 have been retransmitted for this TE link." 2123 ::= { lmpTeLinkPerfEntry 5 } 2125 lmpTeBeginVerifyAckReceived OBJECT-TYPE 2126 SYNTAX Counter32 2127 MAX-ACCESS read-only 2128 STATUS current 2129 DESCRIPTION 2130 "This object counts the number of BeginVerifyAck messages that 2131 have been received for this TE link." 2132 ::= { lmpTeLinkPerfEntry 6 } 2134 lmpTeBeginVerifyAckSent 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 sent for this TE link." 2141 ::= { lmpTeLinkPerfEntry 7 } 2143 lmpTeBeginVerifyNackReceived OBJECT-TYPE 2144 SYNTAX Counter32 2145 MAX-ACCESS read-only 2146 STATUS current 2147 DESCRIPTION 2148 "This object counts the number of BeginVerifyNack messages that 2149 have been received for this TE link." 2150 ::= { lmpTeLinkPerfEntry 8 } 2152 lmpTeBeginVerifyNackSent 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 sent for this TE link." 2159 ::= { lmpTeLinkPerfEntry 9 } 2161 lmpTeEndVerifyReceived OBJECT-TYPE 2162 SYNTAX Counter32 2163 MAX-ACCESS read-only 2164 STATUS current 2165 DESCRIPTION 2166 "This object counts the number of EndVerify messages that have 2167 been received for this TE link." 2168 ::= { lmpTeLinkPerfEntry 10 } 2170 lmpTeEndVerifySent 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 sent for this TE link." 2177 ::= { lmpTeLinkPerfEntry 11 } 2179 lmpTeEndVerifyRetransmit 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 2185 have been retransmitted over this control channel." 2186 ::= { lmpTeLinkPerfEntry 12 } 2188 lmpTeEndVerifyAckReceived OBJECT-TYPE 2189 SYNTAX Counter32 2190 MAX-ACCESS read-only 2191 STATUS current 2192 DESCRIPTION 2193 "This object counts the number of EndVerifyAck messages that 2194 have been received for this TE link." 2195 ::= { lmpTeLinkPerfEntry 13 } 2197 lmpTeEndVerifyAckSent 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 sent for this TE link." 2204 ::= { lmpTeLinkPerfEntry 14 } 2206 lmpTeTestStatusSuccessReceived OBJECT-TYPE 2207 SYNTAX Counter32 2208 MAX-ACCESS read-only 2209 STATUS current 2210 DESCRIPTION 2211 "This object counts the number of TestStatusSuccess messages 2212 that have been received for this TE link." 2213 ::= { lmpTeLinkPerfEntry 15 } 2215 lmpTeTestStatusSuccessSent 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 sent for this TE link." 2222 ::= { lmpTeLinkPerfEntry 16 } 2224 lmpTeTestStatusSuccessRetransmit 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 retransmitted for this TE link." 2231 ::= { lmpTeLinkPerfEntry 17 } 2233 lmpTeTestStatusFailureReceived OBJECT-TYPE 2234 SYNTAX Counter32 2235 MAX-ACCESS read-only 2236 STATUS current 2237 DESCRIPTION 2238 "This object counts the number of TestStatusFailure messages 2239 that have been received for this TE link." 2240 ::= { lmpTeLinkPerfEntry 18 } 2242 lmpTeTestStatusFailureSent 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 sent for this TE link." 2249 ::= { lmpTeLinkPerfEntry 19 } 2251 lmpTeTestStatusFailureRetransmit 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 retransmitted on this TE link." 2258 ::= { lmpTeLinkPerfEntry 20 } 2260 lmpTeTestStatusAckReceived OBJECT-TYPE 2261 SYNTAX Counter32 2262 MAX-ACCESS read-only 2263 STATUS current 2264 DESCRIPTION 2265 "This object counts the number of TestStatusAck messages that 2266 have been received for this TE link." 2267 ::= { lmpTeLinkPerfEntry 21 } 2269 lmpTeTestStatusAckSent 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 sent for this TE link." 2276 ::= { lmpTeLinkPerfEntry 22 } 2278 lmpTeLinkSummaryReceived OBJECT-TYPE 2279 SYNTAX Counter32 2280 MAX-ACCESS read-only 2281 STATUS current 2282 DESCRIPTION 2283 "This object counts the number of LinkSummary messages that 2284 have been received for this TE link." 2285 ::= { lmpTeLinkPerfEntry 23 } 2287 lmpTeLinkSummarySent 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 sent for this TE link." 2294 ::= { lmpTeLinkPerfEntry 24 } 2296 lmpTeLinkSummaryRetransmit 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 retransmitted over this control channel." 2303 ::= { lmpTeLinkPerfEntry 25 } 2305 lmpTeLinkSummaryAckReceived OBJECT-TYPE 2306 SYNTAX Counter32 2307 MAX-ACCESS read-only 2308 STATUS current 2309 DESCRIPTION 2310 "This object counts the number of LinkSummaryAck messages that 2311 have been received for this TE link." 2312 ::= { lmpTeLinkPerfEntry 26 } 2314 lmpTeLinkSummaryAckSent 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 sent for this TE link." 2321 ::= { lmpTeLinkPerfEntry 27 } 2323 lmpTeLinkSummaryNackReceived OBJECT-TYPE 2324 SYNTAX Counter32 2325 MAX-ACCESS read-only 2326 STATUS current 2327 DESCRIPTION 2328 "This object counts the number of LinkSummaryNack messages that 2329 have been received for this TE link." 2330 ::= { lmpTeLinkPerfEntry 28 } 2332 lmpTeLinkSummaryNackSent 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 sent for this TE link." 2339 ::= { lmpTeLinkPerfEntry 29 } 2341 lmpTeChannelStatusReceived OBJECT-TYPE 2342 SYNTAX Counter32 2343 MAX-ACCESS read-only 2344 STATUS current 2345 DESCRIPTION 2346 "This object counts the number of ChannelStatus messages that 2347 have been received for this TE link." 2348 ::= { lmpTeLinkPerfEntry 30 } 2350 lmpTeChannelStatusSent 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 sent for this TE link." 2357 ::= { lmpTeLinkPerfEntry 31 } 2359 lmpTeChannelStatusRetransmit 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 retransmitted for this TE link." 2366 ::= { lmpTeLinkPerfEntry 32 } 2368 lmpTeChannelStatusAckReceived OBJECT-TYPE 2369 SYNTAX Counter32 2370 MAX-ACCESS read-only 2371 STATUS current 2372 DESCRIPTION 2373 "This object counts the number of ChannelStatusAck messages 2374 that have been received for this TE link." 2375 ::= { lmpTeLinkPerfEntry 33 } 2377 lmpTeChannelStatusAckSent OBJECT-TYPE 2378 SYNTAX Counter32 2379 MAX-ACCESS read-only 2380 STATUS current 2381 DESCRIPTION 2382 "This object counts the number of ChannelStatus messages 2383 that have been sent for this TE link." 2384 ::= { lmpTeLinkPerfEntry 34 } 2386 lmpTeChannelStatusReqReceived OBJECT-TYPE 2387 SYNTAX Counter32 2388 MAX-ACCESS read-only 2389 STATUS current 2390 DESCRIPTION 2391 "This object counts the number of ChannelStatusRequest messages 2392 that have been received for this TE link." 2393 ::= { lmpTeLinkPerfEntry 35 } 2395 lmpTeChannelStatusReqSent 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 sent for this TE link." 2402 ::= { lmpTeLinkPerfEntry 36 } 2404 lmpTeChannelStatusReqRetransmit 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 retransmitted for this TE link." 2411 ::= { lmpTeLinkPerfEntry 37 } 2413 lmpTeChannelStatusRspReceived OBJECT-TYPE 2414 SYNTAX Counter32 2415 MAX-ACCESS read-only 2416 STATUS current 2417 DESCRIPTION 2418 "This object counts the number of ChannelStatusResponse messages 2419 that have been received for this TE link." 2420 ::= { lmpTeLinkPerfEntry 38 } 2422 lmpTeChannelStatusRspSent 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 sent for this TE link." 2429 ::= { lmpTeLinkPerfEntry 39 } 2431 lmpTeCounterDiscontinuityTime OBJECT-TYPE 2432 SYNTAX TimeStamp 2433 MAX-ACCESS read-only 2434 STATUS current 2435 DESCRIPTION 2436 "The value of sysUpTime on the most recent occasion at which 2437 any one or more of this TE link's counters suffered a 2438 discontinuity. The relevant counters are the specific 2439 instances associated with this TE link of any Counter32 2440 object contained in the lmpTeLinkPerfTable. If 2441 no such discontinuities have occurred since the last re- 2442 initialization of the local management subsystem, then this 2443 object contains a zero value." 2444 ::= { lmpTeLinkPerfEntry 40 } 2446 -- End of lmpTeLinkPerfTable 2448 -- LMP Data Link Table 2450 lmpDataLinkTable OBJECT-TYPE 2451 SYNTAX SEQUENCE OF LmpDataLinkEntry 2452 MAX-ACCESS not-accessible 2453 STATUS current 2454 DESCRIPTION 2455 "This table specifies the data-bearing links managed by the 2456 LMP." 2457 ::= { lmpObjects 16 } 2459 lmpDataLinkEntry OBJECT-TYPE 2460 SYNTAX LmpDataLinkEntry 2461 MAX-ACCESS not-accessible 2462 STATUS current 2463 DESCRIPTION 2464 "An entry in this table exists for each ifEntry that represents 2465 a data-bearing link. An ifEntry with an ifIndex must exist 2466 before the corresponding lmpDataLinkEntry is created. 2467 If an entry representing the data-bearing link is destroyed in 2468 the ifTable, then so is the corresponding entry in the 2469 lmpDataLinkTable. The administrative status value is 2470 controlled from the ifEntry. The index to this table is also 2471 used to get information in the componentLinkTable 2472 of the TE-LINK-STD-MIB MIB module." 2473 INDEX { ifIndex } 2474 ::= { lmpDataLinkTable 1 } 2476 LmpDataLinkEntry ::= SEQUENCE { 2477 lmpDataLinkType INTEGER, 2478 lmpDataLinkAddressType InetAddressType, 2479 lmpDataLinkIpAddr InetAddress, 2480 lmpDataLinkRemoteIpAddress InetAddress, 2481 lmpDataLinkRemoteIfId InterfaceIndexOrZero, 2482 lmpDataLinkEncodingType TeLinkEncodingType, 2483 lmpDataLinkActiveOperStatus INTEGER, 2484 lmpDataLinkPassiveOperStatus INTEGER, 2485 lmpDataLinkRowStatus RowStatus, 2486 lmpDataLinkStorageType StorageType 2487 } 2489 lmpDataLinkType OBJECT-TYPE 2490 SYNTAX INTEGER { 2491 port(1), 2492 componentLink(2) 2493 } 2494 MAX-ACCESS read-only 2495 STATUS current 2496 DESCRIPTION 2497 "This attribute specifies whether this data-bearing link is 2498 a port or a component link. Component link are multiplex 2499 capable, whereas ports are not multiplex capable." 2500 REFERENCE 2501 "Link Management Protocol, RFC 4204." 2502 ::= { lmpDataLinkEntry 1 } 2504 lmpDataLinkAddressType OBJECT-TYPE 2505 SYNTAX InetAddressType 2506 MAX-ACCESS read-create 2507 STATUS current 2508 DESCRIPTION 2509 "This attribute specifies the data-bearing link IP address 2510 type. If the data-bearing link is unnumbered, the address 2511 type must be set to unknown(0)." 2512 ::= { lmpDataLinkEntry 2 } 2514 lmpDataLinkIpAddr OBJECT-TYPE 2515 SYNTAX InetAddress 2516 MAX-ACCESS read-create 2517 STATUS current 2518 DESCRIPTION 2519 "The local Internet address for numbered links. The type 2520 of this address is determined by the value of 2521 lmpDataLinkAddressType object. 2523 For IPv4 and IPv6 numbered links, this object represents 2524 the local IP address associated with the data-bearing 2525 link. For an unnumbered link, the local address is 2526 of type unknown and this object is set to the zero-length 2527 string and the ifIndex object then identifies the 2528 unnumbered address." 2529 ::= { lmpDataLinkEntry 3 } 2531 lmpDataLinkRemoteIpAddress OBJECT-TYPE 2532 SYNTAX InetAddress 2533 MAX-ACCESS read-create 2534 STATUS current 2535 DESCRIPTION 2536 "The remote Internet address for numbered data-bearing links. 2537 The type of this address is determined by the 2538 lmpDataLinkAddressType object. 2540 For IPv4 and IPv6 numbered links, this object represents the 2541 remote IP address associated with the data-bearing link. For 2542 an unnumbered link, the remote address is of type unknown 2543 and this object is set to the zero-length string and the 2544 lmpDataLinkRemoteIfId object then identifies the unnumbered 2545 address. 2547 This information is either configured manually or 2548 communicated by the remote node during the link verification 2549 procedure." 2550 ::= { lmpDataLinkEntry 4 } 2552 lmpDataLinkRemoteIfId OBJECT-TYPE 2553 SYNTAX InterfaceIndexOrZero 2554 MAX-ACCESS read-create 2555 STATUS current 2556 DESCRIPTION 2557 "Interface identifier of the remote end point. This 2558 information is either configured manually or 2559 communicated by the remote node during the link verification 2560 procedure." 2561 ::= { lmpDataLinkEntry 5 } 2563 lmpDataLinkEncodingType OBJECT-TYPE 2564 SYNTAX TeLinkEncodingType 2565 MAX-ACCESS read-create 2566 STATUS current 2567 DESCRIPTION 2568 "The encoding type of the data-bearing link." 2569 REFERENCE 2570 "Generalized MPLS Signaling Functional Description, RFC 3471." 2571 ::= { lmpDataLinkEntry 6 } 2573 lmpDataLinkActiveOperStatus OBJECT-TYPE 2574 SYNTAX INTEGER { 2575 upAlloc(1), 2576 upFree(2), 2577 down(3), 2578 testing(4) } 2579 MAX-ACCESS read-only 2580 STATUS current 2581 DESCRIPTION 2582 "The actual operational status of this data-bearing link 2583 (active FSM)." 2584 REFERENCE 2585 "Link Management Protocol, RFC 4204." 2586 ::= { lmpDataLinkEntry 7 } 2588 lmpDataLinkPassiveOperStatus OBJECT-TYPE 2589 SYNTAX INTEGER { 2590 upAlloc(1), 2591 upFree(2), 2592 down(3), 2593 psvTst(4) } 2594 MAX-ACCESS read-only 2595 STATUS current 2596 DESCRIPTION 2597 "The actual operational status of this data-bearing link 2598 (passive FSM)." 2599 REFERENCE 2600 "Link Management Protocol, RFC 4204." 2601 ::= { lmpDataLinkEntry 8 } 2603 lmpDataLinkRowStatus OBJECT-TYPE 2604 SYNTAX RowStatus 2605 MAX-ACCESS read-create 2606 STATUS current 2607 DESCRIPTION 2608 "This variable is used to create, modify, and/or 2609 delete a row in this table. None of the writable objects 2610 in a row can be changed if the status is active(1). 2611 All read-create objects must have valid and consistent 2612 values before the row can be activated." 2613 ::= { lmpDataLinkEntry 9 } 2615 lmpDataLinkStorageType OBJECT-TYPE 2616 SYNTAX StorageType 2617 MAX-ACCESS read-create 2618 STATUS current 2619 DESCRIPTION 2620 "The storage type for this conceptual row in the 2621 lmpDataLinkTable. Conceptual rows having the value 2622 'permanent' need not allow write-access to any 2623 columnar object in the row." 2624 DEFVAL { nonVolatile } 2625 ::= { lmpDataLinkEntry 10 } 2627 -- End of lmpDataLinkTable 2628 -- LMP Data Link Performance Table 2630 lmpDataLinkPerfTable OBJECT-TYPE 2631 SYNTAX SEQUENCE OF LmpDataLinkPerfEntry 2632 MAX-ACCESS not-accessible 2633 STATUS current 2634 DESCRIPTION 2635 "This table specifies the data-bearing links LMP performance 2636 counters." 2637 ::= { lmpObjects 17 } 2639 lmpDataLinkPerfEntry OBJECT-TYPE 2640 SYNTAX LmpDataLinkPerfEntry 2641 MAX-ACCESS not-accessible 2642 STATUS current 2643 DESCRIPTION 2644 "An entry in this table contains information about 2645 the LMP performance counters for the data-bearing links. 2646 lmpDataLinkDiscontinuityTime is used to indicate potential 2647 discontinuity for all counter objects in this table." 2648 INDEX { ifIndex } 2649 ::= { lmpDataLinkPerfTable 1 } 2651 LmpDataLinkPerfEntry ::= SEQUENCE { 2652 lmpDataLinkTestReceived Counter32, 2653 lmpDataLinkTestSent Counter32, 2654 lmpDataLinkActiveTestSuccess Counter32, 2655 lmpDataLinkActiveTestFailure Counter32, 2656 lmpDataLinkPassiveTestSuccess Counter32, 2657 lmpDataLinkPassiveTestFailure Counter32, 2658 lmpDataLinkDiscontinuityTime TimeStamp 2659 } 2661 lmpDataLinkTestReceived OBJECT-TYPE 2662 SYNTAX Counter32 2663 MAX-ACCESS read-only 2664 STATUS current 2665 DESCRIPTION 2666 "This object counts the number of Test messages that have 2667 been received on this data-bearing link." 2668 ::= { lmpDataLinkPerfEntry 1 } 2670 lmpDataLinkTestSent 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 sent on this data-bearing link." 2677 ::= { lmpDataLinkPerfEntry 2 } 2679 lmpDataLinkActiveTestSuccess OBJECT-TYPE 2680 SYNTAX Counter32 2681 MAX-ACCESS read-only 2682 STATUS current 2683 DESCRIPTION 2684 "This object counts the number of data-bearing link tests 2685 that were successful on the active side of this data- 2686 bearing link." 2687 ::= { lmpDataLinkPerfEntry 3 } 2689 lmpDataLinkActiveTestFailure OBJECT-TYPE 2690 SYNTAX Counter32 2691 MAX-ACCESS read-only 2692 STATUS current 2693 DESCRIPTION 2694 "This object counts the number of data-bearing link tests 2695 that failed on the active side of this data-bearing link." 2696 ::= { lmpDataLinkPerfEntry 4 } 2698 lmpDataLinkPassiveTestSuccess 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 were successful on the passive side of this data- 2705 bearing link." 2706 ::= { lmpDataLinkPerfEntry 5 } 2708 lmpDataLinkPassiveTestFailure OBJECT-TYPE 2709 SYNTAX Counter32 2710 MAX-ACCESS read-only 2711 STATUS current 2712 DESCRIPTION 2713 "This object counts the number of data-bearing link tests 2714 that failed on the passive side of this data-bearing link." 2715 ::= { lmpDataLinkPerfEntry 6 } 2717 lmpDataLinkDiscontinuityTime OBJECT-TYPE 2718 SYNTAX TimeStamp 2719 MAX-ACCESS read-only 2720 STATUS current 2721 DESCRIPTION 2722 "The value of sysUpTime on the most recent occasion at which 2723 any one or more of this data-bearing link's counters suffered 2724 a discontinuity. The relevant counters are the specific 2725 instances associated with this data-bearing link of any 2726 Counter32 object contained in the lmpDataLinkPerfTable. If 2727 no such discontinuities have occurred since the last re- 2728 initialization of the local management subsystem, then this 2729 object contains a zero value." 2730 ::= { lmpDataLinkPerfEntry 7 } 2732 -- End of lmpDataLinkPerfTable 2734 -- Notification Configuration 2736 lmpNotificationMaxRate OBJECT-TYPE 2737 SYNTAX Unsigned32 2738 MAX-ACCESS read-write 2739 STATUS current 2740 DESCRIPTION 2741 "The LMP notification rate depends on the size of the network, 2742 the type of links, the network configuration, the 2743 reliability of the network, etc. 2745 When designing this MIB, care has been taken to minimize the 2746 amount of notifications generated for LMP purposes. Wherever 2747 possible, notifications are state driven, meaning the 2748 notifications are sent only when the system changes state. 2749 The only notifications that are repeated and could cause a 2750 problem as far as congestion is concerned are the ones 2751 associated with data link verification. 2752 Without any considerations to handling of these 2753 notifications, a problem may arise if the number of data 2754 links is high. Since the data link verification notifications 2755 can happen only once per data link per link verification 2756 interval, the notification rate should be sustainable if one 2757 chooses an appropriate link verification interval for a given 2758 network configuration. For instance, a network of 100 nodes 2759 with 5 links of 128 wavelengths each and a link verification 2760 of 1 minute with no more than 10% of the links failed at any 2761 given time would have 1 notification per second sent from 2762 each node, or 100 notifications per second for the whole 2763 network. The rest of the notifications are negligible 2764 compared to this number. 2766 To alleviate the congestion problem, the 2767 lmpNotificationMaxRate object can be used to implement a 2768 throttling mechanism. It is also possible to enable/disable 2769 certain type of notifications. 2771 This variable indicates the maximum number of 2772 notifications issued per minute. If events occur 2773 more rapidly, the implementation may simply fail to 2774 emit these notifications during that period, or may 2775 queue them until an appropriate time. A value of 0 2776 means no throttling is applied and events may be 2777 notified at the rate at which they occur. 2779 Implementations should save the value of this object in 2780 persistent memory so that it survives restarts or reboot." 2781 ::= { lmpObjects 18 } 2783 lmpLinkPropertyNotificationsEnabled OBJECT-TYPE 2784 SYNTAX TruthValue 2785 MAX-ACCESS read-write 2786 STATUS current 2787 DESCRIPTION 2788 "If this object is true(1), then it enables the 2789 generation of lmpTeLinkPropertyMismatch 2790 and lmpDataLinkPropertyMismatch notifications, 2791 otherwise these notifications are not emitted. 2792 Implementations should save the value of this object in 2793 persistent memory so that it survives restarts or reboot." 2794 DEFVAL { false } 2795 ::= { lmpObjects 19 } 2797 lmpUnprotectedNotificationsEnabled OBJECT-TYPE 2798 SYNTAX TruthValue 2799 MAX-ACCESS read-write 2800 STATUS current 2801 DESCRIPTION 2802 "If this object is true(1), then it enables the 2803 generation of lmpUnprotected notifications, 2804 otherwise these notifications are not emitted. 2805 Implementations should save the value of this object in 2806 persistent memory so that it survives restarts or reboot." 2807 DEFVAL { false } 2808 ::= { lmpObjects 20 } 2810 lmpCcUpDownNotificationsEnabled OBJECT-TYPE 2811 SYNTAX TruthValue 2812 MAX-ACCESS read-write 2813 STATUS current 2814 DESCRIPTION 2815 "If this object is true(1), then it enables the generation of 2816 lmpControlChannelUp and lmpControlChannelDown notifications, 2817 otherwise these notifications are not emitted. 2818 Implementations should save the value of this object in 2819 persistent memory so that it survives restarts or reboot." 2820 DEFVAL { false } 2821 ::= { lmpObjects 21 } 2823 lmpTeLinkNotificationsEnabled OBJECT-TYPE 2824 SYNTAX TruthValue 2825 MAX-ACCESS read-write 2826 STATUS current 2827 DESCRIPTION 2828 "If this object is true(1), then it enables the 2829 generation of lmpTeLinkDegraded and lmpTeLinkNotDegraded 2830 notifications, otherwise these notifications are not emitted. 2831 Implementations should save the value of this object in 2832 persistent memory so that it survives restarts or reboot." 2833 DEFVAL { false } 2834 ::= { lmpObjects 22 } 2836 lmpDataLinkNotificationsEnabled OBJECT-TYPE 2837 SYNTAX TruthValue 2838 MAX-ACCESS read-write 2839 STATUS current 2840 DESCRIPTION 2841 "If this object is true(1), then it enables the 2842 generation of lmpDataLinkVerificationFailure 2843 notification, otherwise these notifications are not emitted. 2844 Implementations should save the value of this object in 2845 persistent memory so that it survives restarts or reboot." 2846 DEFVAL { false } 2847 ::= { lmpObjects 23 } 2849 -- Notifications 2851 -- Link Property Mismatch Notifications 2853 lmpTeLinkPropertyMismatch NOTIFICATION-TYPE 2854 OBJECTS { teLinkRemoteIpAddr, 2855 teLinkIncomingIfId } 2856 STATUS current 2857 DESCRIPTION 2858 "This notification is generated when a TE link property 2859 mismatch is detected on the node. The received remote TE link 2860 ID of the misconfigured TE link is represented by either 2861 teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether 2862 the TE link is numbered or unnumbered. This notification 2863 should not be sent unless lmpLinkPropertyNotificationsEnabled 2864 is true(1). It is recommended that this notification be reported 2865 only the first time a mismatch is detected. Otherwise, for a 2866 given TE link, this notification can occur no more than once 2867 per verification interval (lmpGlobalLinkVerificationInterval)." 2868 ::= { lmpNotifications 1 } 2870 lmpDataLinkPropertyMismatch NOTIFICATION-TYPE 2871 OBJECTS { lmpDataLinkType, lmpDataLinkRemoteIfId } 2872 STATUS current 2873 DESCRIPTION 2874 "This notification is generated when a data-bearing link 2875 property mismatch is detected on the node. lmpDataLinkType 2876 is used to identify the local identifiers associated with 2877 the data link (the data link interface index can be used 2878 to determine the TE link interface index as this 2879 relationship is captured in the interface stack table). 2880 The remote entity interface ID is the remote entity 2881 interface ID received in the LinkSummary message. 2882 This notification should not be sent unless 2883 lmpLinkPropertyNotificationsEnabled is true(1). It is 2884 recommended that this notification be reported only the 2885 first time a mismatch is detected. Otherwise, for a given 2886 data link, this notification can occur no more than once 2887 per verification interval (lmpGlobalLinkVerificationInterval)." 2888 ::= { lmpNotifications 2 } 2890 -- Neighbor Notification 2892 lmpUnprotected NOTIFICATION-TYPE 2893 OBJECTS { lmpCcNbrNodeId } 2894 STATUS current 2895 DESCRIPTION 2896 "This notification is generated when there are more than one 2897 control channels between LMP neighbors and the last redundant 2898 control channel has failed. If the remaining operational 2899 control channel fails, then there will be no more control 2900 channels between the pair of nodes and all the TE links 2901 between the pair of nodes will go to degraded state. This 2902 notification should not be sent unless 2903 lmpUnprotectedNotificationsEnabled is set to true(1)." 2904 ::= { lmpNotifications 3 } 2906 -- Control Channel Notifications 2908 lmpControlChannelUp NOTIFICATION-TYPE 2909 OBJECTS { lmpCcAdminStatus, lmpCcOperStatus } 2910 STATUS current 2911 DESCRIPTION 2912 "This notification is generated when a control 2913 channel transitions to the up operational state. This 2914 notification should not be sent unless 2915 lmpCcUpDownNotificationsEnabled is true(1)." 2916 ::= { lmpNotifications 4 } 2918 lmpControlChannelDown NOTIFICATION-TYPE 2919 OBJECTS { lmpCcAdminStatus, lmpCcOperStatus } 2920 STATUS current 2921 DESCRIPTION 2922 "This notification is generated when a control channel 2923 transitions out of the up operational state. This 2924 notification should not be sent unless 2925 lmpCcUpDownNotificationsEnabled is true(1)." 2926 ::= { lmpNotifications 5 } 2928 -- TE Link Notification 2930 lmpTeLinkDegraded NOTIFICATION-TYPE 2931 OBJECTS { lmpTeLinkOperStatus } 2932 STATUS current 2933 DESCRIPTION 2934 "This notification is generated when a lmpTeLinkOperStatus 2935 object for a TE link enters the degraded state. This 2936 notification should not be sent unless 2937 lmpTeLinkNotificationsEnabled is true(1)." 2938 ::= { lmpNotifications 6 } 2940 lmpTeLinkNotDegraded NOTIFICATION-TYPE 2941 OBJECTS { lmpTeLinkOperStatus } 2942 STATUS current 2943 DESCRIPTION 2944 "This notification is generated when a lmpTeLinkOperStatus 2945 object for a TE link leaves the degraded state. This 2946 notification should not be sent unless 2947 lmpTeLinkNotificationsEnabled is true(1)." 2948 ::= { lmpNotifications 7 } 2950 -- Data-bearing Link Notification 2952 lmpDataLinkVerificationFailure NOTIFICATION-TYPE 2953 OBJECTS { lmpDataLinkActiveOperStatus, 2954 lmpDataLinkPassiveOperStatus } 2955 STATUS current 2956 DESCRIPTION 2957 "This notification is generated when a data-bearing 2958 link verification fails. This notification should not be sent 2959 unless lmpDataLinkNotificationsEnabled is true(1). For a given 2960 data link, this notification can occur no more than once per 2961 verification interval (lmpGlobalLinkVerificationInterval)." 2962 ::= { lmpNotifications 8 } 2964 -- End of notifications 2966 -- Module compliance 2968 lmpCompliances 2969 OBJECT IDENTIFIER ::= { lmpConformance 1 } 2971 lmpGroups 2972 OBJECT IDENTIFIER ::= { lmpConformance 2 } 2974 lmpModuleFullCompliance MODULE-COMPLIANCE 2975 STATUS current 2976 DESCRIPTION 2977 "Compliance statement for agents that support the 2978 configuration and monitoring of LMP MIB." 2979 MODULE -- this module 2981 MANDATORY-GROUPS { lmpNodeGroup, 2982 lmpControlChannelGroup, 2983 lmpLinkPropertyCorrelationGroup, 2984 lmpPerfGroup, 2985 lmpTeLinkGroup, 2986 lmpDataLinkGroup } 2988 GROUP lmpCcIsNotInterfaceGroup 2989 DESCRIPTION 2990 "This group is mandatory for devices that support 2991 control channels that are not interfaces, in addition to 2992 lmpControlChannelGroup. The following constraints apply: 2993 lmpCcIsIf must at least be read-only returning false(2)." 2995 GROUP lmpCcIsInterfaceGroup 2996 DESCRIPTION 2997 "This group is mandatory for devices that support 2998 control channels that are interfaces, in addition to 2999 lmpControlChannelGroup. The following constraints apply: 3000 lmpCcIsIf must at least be read-only returning true(1)." 3002 GROUP lmpLinkVerificationGroup 3003 DESCRIPTION 3004 "This group is mandatory for devices that support 3005 the link verification procedure." 3007 GROUP lmpNotificationGroup 3008 DESCRIPTION 3009 "This group is optional." 3011 -- lmpNbrTable 3013 OBJECT lmpNbrRowStatus 3014 SYNTAX RowStatus { active(1), notInService(2) } 3015 WRITE-SYNTAX RowStatus { active(1), notInService(2), 3016 createAndGo(4), destroy(6) } 3017 DESCRIPTION 3018 "Support for notReady(3) and createAndWait(5) is 3019 not required." 3021 -- lmpControlChannelTable 3023 OBJECT lmpCcRemoteAddressType 3024 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 3025 DESCRIPTION 3026 "Only ipv4(1) and ipv6(2) address types need to be 3027 supported for non-point-to-point configurations." 3029 OBJECT lmpCcRemoteIpAddr 3030 SYNTAX InetAddress (SIZE(0|4|16)) 3031 DESCRIPTION 3032 "The size of the IP address depends on the address type." 3034 OBJECT lmpCcRowStatus 3035 SYNTAX RowStatus { active(1), notInService(2) } 3036 WRITE-SYNTAX RowStatus { active(1), notInService(2), 3037 createAndGo(4), destroy(6) } 3038 DESCRIPTION 3039 "Support for notReady(3) and createAndWait(5) is 3040 not required." 3042 OBJECT lmpCcOperStatus 3043 SYNTAX INTEGER { up(1), down(2) } 3044 DESCRIPTION 3045 "A value of configSnd(3), configRcv(4), active(5), 3046 goingDown(6) need not be supported." 3048 -- lmpTeLinkTable 3050 OBJECT lmpTeLinkOperStatus 3051 SYNTAX INTEGER { up(1), down(2), degraded(5) } 3052 DESCRIPTION 3053 "The testing(3) and init(4) state need not be supported." 3055 OBJECT lmpTeLinkRowStatus 3056 SYNTAX RowStatus { active(1), notInService(2) } 3057 WRITE-SYNTAX RowStatus { active(1), notInService(2), 3058 createAndGo(4), destroy(6) } 3059 DESCRIPTION 3060 "Support for notReady(3) and createAndWait(5) is 3061 not required." 3063 -- lmpDataLinkTable 3065 OBJECT lmpDataLinkActiveOperStatus 3066 SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) } 3067 DESCRIPTION 3068 "A value of testing(4) need not be supported." 3070 OBJECT lmpDataLinkPassiveOperStatus 3071 SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) } 3072 DESCRIPTION 3073 "A value of psvTst(4) need not be supported." 3075 OBJECT lmpDataLinkRowStatus 3076 SYNTAX RowStatus { active(1), notInService(2) } 3077 WRITE-SYNTAX RowStatus { active(1), notInService(2), 3078 createAndGo(4), destroy(6) } 3079 DESCRIPTION 3080 "Support for notReady(3) and createAndWait(5) is 3081 not required." 3083 ::= { lmpCompliances 1 } 3085 lmpModuleReadOnlyCompliance MODULE-COMPLIANCE 3086 STATUS current 3087 DESCRIPTION 3088 "Compliance statement for agents that support the 3089 monitoring of the LMP MIB." 3090 MODULE -- this module 3092 -- The mandatory groups have to be implemented 3093 -- by all LMP-enabled devices. However, they may all be supported 3094 -- as read-only objects in the case where manual 3095 -- configuration is not supported. 3097 MANDATORY-GROUPS { lmpNodeGroup, 3098 lmpControlChannelGroup, 3099 lmpLinkPropertyCorrelationGroup, 3100 lmpPerfGroup, 3101 lmpTeLinkGroup, 3102 lmpDataLinkGroup } 3104 GROUP lmpCcIsNotInterfaceGroup 3105 DESCRIPTION 3106 "This group is mandatory for devices that support 3107 control channels that are not interfaces, in addition to 3108 lmpControlChannelGroup. The following constraints apply: 3109 lmpCcIsIf must at least be read-only returning false(2)." 3111 GROUP lmpCcIsInterfaceGroup 3112 DESCRIPTION 3113 "This group is mandatory for devices that support 3114 control channels that are interfaces, in addition to 3115 lmpControlChannelGroup. The following constraints apply: 3116 lmpCcIsIf must at least be read-only returning true(1)." 3118 GROUP lmpLinkVerificationGroup 3119 DESCRIPTION 3120 "This group is mandatory for devices that support 3121 the link verification procedure." 3123 GROUP lmpNotificationGroup 3124 DESCRIPTION 3125 "This group is optional." 3127 -- Scalars 3129 OBJECT lmpAdminStatus 3130 MIN-ACCESS read-only 3131 DESCRIPTION 3132 "Write access is not required." 3134 OBJECT lmpGlobalLinkVerificationInterval 3135 MIN-ACCESS read-only 3136 DESCRIPTION 3137 "Write access is not required." 3139 OBJECT lmpCcHelloIntervalDefault 3140 MIN-ACCESS read-only 3141 DESCRIPTION 3142 "Write access is not required." 3144 OBJECT lmpCcHelloIntervalDefaultMin 3145 MIN-ACCESS read-only 3146 DESCRIPTION 3147 "Write access is not required." 3149 OBJECT lmpCcHelloIntervalDefaultMax 3150 MIN-ACCESS read-only 3151 DESCRIPTION 3152 "Write access is not required." 3154 OBJECT lmpCcHelloDeadIntervalDefault 3155 MIN-ACCESS read-only 3156 DESCRIPTION 3157 "Write access is not required." 3159 OBJECT lmpCcHelloDeadIntervalDefaultMin 3160 MIN-ACCESS read-only 3161 DESCRIPTION 3162 "Write access is not required." 3164 OBJECT lmpCcHelloDeadIntervalDefaultMax 3165 MIN-ACCESS read-only 3166 DESCRIPTION 3167 "Write access is not required." 3169 OBJECT lmpNotificationMaxRate 3170 MIN-ACCESS read-only 3171 DESCRIPTION 3172 "Write access is not required." 3174 -- lmpNbrTable 3176 OBJECT lmpNbrRetransmitInterval 3177 MIN-ACCESS read-only 3178 DESCRIPTION 3179 "Write access is not required." 3181 OBJECT lmpNbrRetryLimit 3182 MIN-ACCESS read-only 3183 DESCRIPTION 3184 "Write access is not required." 3186 OBJECT lmpNbrRetransmitDelta 3187 MIN-ACCESS read-only 3188 DESCRIPTION 3189 "Write access is not required." 3191 OBJECT lmpNbrRowStatus 3192 SYNTAX RowStatus { active(1) } 3193 MIN-ACCESS read-only 3194 DESCRIPTION 3195 "Write access is not required, and active(1) is the 3196 only status that needs to be supported." 3198 OBJECT lmpNbrStorageType 3199 MIN-ACCESS read-only 3200 DESCRIPTION 3201 "Write access is not required." 3203 -- lmpControlChannelTable 3205 OBJECT lmpCcUnderlyingIfIndex 3206 MIN-ACCESS read-only 3207 DESCRIPTION 3208 "Write access is not required." 3210 OBJECT lmpCcIsIf 3211 MIN-ACCESS read-only 3212 DESCRIPTION 3213 "Write access is not required." 3215 OBJECT lmpCcNbrNodeId 3216 MIN-ACCESS read-only 3217 DESCRIPTION 3218 "Write access is not required." 3220 OBJECT lmpCcRemoteAddressType 3221 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 3222 MIN-ACCESS read-only 3223 DESCRIPTION 3224 "Only ipv4(1) and ipv6(2) address types need to be 3225 supported for non-point-to-point configurations." 3227 OBJECT lmpCcRemoteIpAddr 3228 SYNTAX InetAddress (SIZE(0|4|16)) 3229 MIN-ACCESS read-only 3230 DESCRIPTION 3231 "The size of the IP address depends on the address type." 3233 OBJECT lmpCcSetupRole 3234 MIN-ACCESS read-only 3235 DESCRIPTION 3236 "Write access is not required." 3238 OBJECT lmpCcAuthentication 3239 MIN-ACCESS read-only 3240 DESCRIPTION 3241 "Write access is not required." 3243 OBJECT lmpCcHelloIntervalMin 3244 MIN-ACCESS read-only 3245 DESCRIPTION 3246 "Write access is not required." 3248 OBJECT lmpCcHelloIntervalMax 3249 MIN-ACCESS read-only 3250 DESCRIPTION 3251 "Write access is not required." 3253 OBJECT lmpCcHelloDeadIntervalMin 3254 MIN-ACCESS read-only 3255 DESCRIPTION 3256 "Write access is not required." 3258 OBJECT lmpCcHelloDeadIntervalMax 3259 MIN-ACCESS read-only 3260 DESCRIPTION 3261 "Write access is not required." 3263 OBJECT lmpCcRowStatus 3264 SYNTAX RowStatus { active(1) } 3265 MIN-ACCESS read-only 3266 DESCRIPTION 3267 "Write access is not required, and active(1) is the 3268 only status that needs to be supported." 3270 OBJECT lmpCcOperStatus 3271 SYNTAX INTEGER { up(1), down(2) } 3272 DESCRIPTION 3273 "A value of configSnd(3), configRcv(4), active(5), 3274 goingDown(6) need not be supported." 3276 OBJECT lmpCcStorageType 3277 MIN-ACCESS read-only 3278 DESCRIPTION 3279 "Write access is not required." 3281 -- lmpLinkVerificationTable 3283 OBJECT lmpLinkVerifyInterval 3284 MIN-ACCESS read-only 3285 DESCRIPTION 3286 "Write access is not required." 3288 OBJECT lmpLinkVerifyDeadInterval 3289 MIN-ACCESS read-only 3290 DESCRIPTION 3291 "Write access is not required." 3293 OBJECT lmpLinkVerifyAllLinks 3294 MIN-ACCESS read-only 3295 DESCRIPTION 3296 "Write access is not required." 3298 -- lmpTeLinkTable 3300 OBJECT lmpTeLinkNbrRemoteNodeId 3301 MIN-ACCESS read-only 3302 DESCRIPTION 3303 "Write access is not required if the link verification 3304 procedure is enabled." 3306 OBJECT lmpTeLinkVerification 3307 MIN-ACCESS read-only 3308 DESCRIPTION 3309 "Write access is not required." 3311 OBJECT lmpTeLinkFaultManagement 3312 MIN-ACCESS read-only 3313 DESCRIPTION 3314 "Write access is not required." 3316 OBJECT lmpTeLinkDwdm 3317 MIN-ACCESS read-only 3318 DESCRIPTION 3319 "Write access is not required." 3321 OBJECT lmpTeLinkOperStatus 3322 SYNTAX INTEGER { up(1), down(2), degraded(5) } 3323 DESCRIPTION 3324 "The testing(3) and init(4) state need not be supported." 3326 OBJECT lmpTeLinkRowStatus 3327 SYNTAX RowStatus { active(1) } 3328 MIN-ACCESS read-only 3329 DESCRIPTION 3330 "Write access is not required, and active(1) is the 3331 only status that needs to be supported." 3333 OBJECT lmpTeLinkStorageType 3334 MIN-ACCESS read-only 3335 DESCRIPTION 3336 "Write access is not required." 3338 -- lmpTeLinkVerificationTable 3340 OBJECT lmpLinkVerifyTransmissionRate 3341 MIN-ACCESS read-only 3342 DESCRIPTION 3343 "Write access is not required." 3345 OBJECT lmpLinkVerifyWavelength 3346 MIN-ACCESS read-only 3347 DESCRIPTION 3348 "Write access is not required." 3350 OBJECT lmpLinkVerifyRowStatus 3351 SYNTAX RowStatus { active(1) } 3352 MIN-ACCESS read-only 3353 DESCRIPTION 3354 "Write access is not required, and active(1) is the 3355 only status that needs to be supported." 3357 OBJECT lmpLinkVerifyStorageType 3358 MIN-ACCESS read-only 3359 DESCRIPTION 3360 "Write access is not required." 3362 -- lmpDataLinkTable 3364 OBJECT lmpDataLinkAddressType 3365 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 3366 MIN-ACCESS read-only 3367 DESCRIPTION 3368 "Only ipv4(1) and ipv6(2) address types need to be 3369 supported for numbered links. For unnumbered links, the 3370 unknown(0) address type needs to be supported." 3372 OBJECT lmpDataLinkIpAddr 3373 SYNTAX InetAddress (SIZE(0|4|16)) 3374 MIN-ACCESS read-only 3375 DESCRIPTION 3376 "Size of data-bearing link IP address depends on type 3377 of data-bearing link. Data-bearing link IP address size 3378 is zero if link is unnumbered, four if link IP address is 3379 IPv4, and sixteen if link IP address is IPv6." 3381 OBJECT lmpDataLinkRemoteIpAddress 3382 SYNTAX InetAddress (SIZE(0|4|16)) 3383 MIN-ACCESS read-only 3384 DESCRIPTION 3385 "Write access is not required if the link verification 3386 procedure is enabled." 3388 OBJECT lmpDataLinkRemoteIfId 3389 MIN-ACCESS read-only 3390 DESCRIPTION 3391 "Write access is not required if the link verification 3392 procedure is enabled." 3394 OBJECT lmpDataLinkEncodingType 3395 MIN-ACCESS read-only 3396 DESCRIPTION 3397 "Write access is not required." 3399 OBJECT lmpDataLinkActiveOperStatus 3400 SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) } 3401 DESCRIPTION 3402 "A value of testing(4) need not be supported." 3404 OBJECT lmpDataLinkPassiveOperStatus 3405 SYNTAX INTEGER { upAlloc(1), upFree(2), down(3) } 3406 DESCRIPTION 3407 "A value of psvTst(4) need not be supported." 3409 OBJECT lmpDataLinkRowStatus 3410 SYNTAX RowStatus { active(1) } 3411 MIN-ACCESS read-only 3412 DESCRIPTION 3413 "Write access is not required, and active(1) is the 3414 only status that needs to be supported." 3416 OBJECT lmpDataLinkStorageType 3417 MIN-ACCESS read-only 3418 DESCRIPTION 3419 "Write access is not required." 3421 ::= { lmpCompliances 2 } 3423 -- Units of conformance 3425 lmpNodeGroup OBJECT-GROUP 3426 OBJECTS { lmpAdminStatus, 3427 lmpOperStatus, 3428 lmpNbrAdminStatus, 3429 lmpNbrOperStatus, 3430 lmpNbrRowStatus, 3431 lmpNbrStorageType, 3432 lmpUnprotectedNotificationsEnabled, 3433 lmpNotificationMaxRate 3434 } 3435 STATUS current 3436 DESCRIPTION 3437 "Collection of objects that represent LMP node 3438 configuration." 3439 ::= { lmpGroups 1 } 3441 lmpControlChannelGroup OBJECT-GROUP 3442 OBJECTS { 3443 lmpNbrRetransmitInterval, 3444 lmpNbrRetryLimit, 3445 lmpNbrRetransmitDelta, 3446 lmpNbrAdminStatus, 3447 lmpNbrOperStatus, 3448 lmpNbrRowStatus, 3449 lmpNbrStorageType, 3450 lmpCcHelloIntervalDefault, 3451 lmpCcHelloIntervalDefaultMin, 3452 lmpCcHelloIntervalDefaultMax, 3453 lmpCcHelloDeadIntervalDefault, 3454 lmpCcHelloDeadIntervalDefaultMin, 3455 lmpCcHelloDeadIntervalDefaultMax, 3456 lmpCcNbrNodeId, 3457 lmpCcRemoteId, 3458 lmpCcRemoteAddressType, 3459 lmpCcRemoteIpAddr, 3460 lmpCcSetupRole, 3461 lmpCcAuthentication, 3462 lmpCcHelloInterval, 3463 lmpCcHelloIntervalMin, 3464 lmpCcHelloIntervalMax, 3465 lmpCcHelloIntervalNegotiated, 3466 lmpCcHelloDeadInterval, 3467 lmpCcHelloDeadIntervalMin, 3468 lmpCcHelloDeadIntervalMax, 3469 lmpCcHelloDeadIntervalNegotiated, 3470 lmpCcOperStatus, 3471 lmpCcRowStatus, 3472 lmpCcStorageType, 3473 lmpCcUpDownNotificationsEnabled 3474 } 3475 STATUS current 3476 DESCRIPTION 3477 "Objects that can be used to configure LMP interface." 3478 ::= { lmpGroups 2 } 3480 lmpCcIsInterfaceGroup OBJECT-GROUP 3481 OBJECTS { lmpCcIsIf } 3482 STATUS current 3483 DESCRIPTION 3484 "Objects that can be used to configure control channels 3485 that are interfaces." 3486 ::= { lmpGroups 3 } 3488 lmpCcIsNotInterfaceGroup OBJECT-GROUP 3489 OBJECTS { lmpCcUnderlyingIfIndex, 3490 lmpCcIsIf, 3491 lmpCcLastChange, 3492 lmpCcAdminStatus 3493 } 3494 STATUS current 3495 DESCRIPTION 3496 "Objects that can be used to configure control channels 3497 that are not interfaces." 3498 ::= { lmpGroups 4 } 3500 lmpLinkPropertyCorrelationGroup OBJECT-GROUP 3501 OBJECTS { lmpLinkPropertyNotificationsEnabled } 3502 STATUS current 3503 DESCRIPTION 3504 "Collection of objects used to configure the link 3505 property correlation procedure." 3506 ::= { lmpGroups 5 } 3508 lmpLinkVerificationGroup OBJECT-GROUP 3509 OBJECTS { lmpGlobalLinkVerificationInterval, 3510 lmpLinkVerifyInterval, 3511 lmpLinkVerifyDeadInterval, 3512 lmpLinkVerifyTransportMechanism, 3513 lmpLinkVerifyAllLinks, 3514 lmpLinkVerifyTransmissionRate, 3515 lmpLinkVerifyWavelength, 3516 lmpLinkVerifyRowStatus, 3517 lmpLinkVerifyStorageType, 3518 lmpDataLinkNotificationsEnabled 3519 } 3520 STATUS current 3521 DESCRIPTION 3522 "Collection of objects that represent the link 3523 verification procedure configuration." 3524 ::= { lmpGroups 6 } 3526 lmpPerfGroup OBJECT-GROUP 3527 OBJECTS { lmpCcInOctets, 3528 lmpCcInDiscards, 3529 lmpCcInErrors, 3530 lmpCcOutOctets, 3531 lmpCcOutDiscards, 3532 lmpCcOutErrors, 3533 lmpCcConfigReceived, 3534 lmpCcConfigSent, 3535 lmpCcConfigRetransmit, 3536 lmpCcConfigAckReceived, 3537 lmpCcConfigAckSent, 3538 lmpCcConfigNackSent, 3539 lmpCcConfigNackReceived, 3540 lmpCcHelloReceived, 3541 lmpCcHelloSent, 3542 lmpCcBeginVerifyReceived, 3543 lmpCcBeginVerifySent, 3544 lmpCcBeginVerifyRetransmit, 3545 lmpCcBeginVerifyAckReceived, 3546 lmpCcBeginVerifyAckSent, 3547 lmpCcBeginVerifyNackReceived, 3548 lmpCcBeginVerifyNackSent, 3549 lmpCcEndVerifyReceived, 3550 lmpCcEndVerifySent, 3551 lmpCcEndVerifyRetransmit, 3552 lmpCcEndVerifyAckReceived, 3553 lmpCcEndVerifyAckSent, 3554 lmpCcTestStatusSuccessReceived, 3555 lmpCcTestStatusSuccessSent, 3556 lmpCcTestStatusSuccessRetransmit, 3557 lmpCcTestStatusFailureReceived, 3558 lmpCcTestStatusFailureSent, 3559 lmpCcTestStatusFailureRetransmit, 3560 lmpCcTestStatusAckReceived, 3561 lmpCcTestStatusAckSent, 3562 lmpCcLinkSummaryReceived, 3563 lmpCcLinkSummarySent, 3564 lmpCcLinkSummaryRetransmit, 3565 lmpCcLinkSummaryAckReceived, 3566 lmpCcLinkSummaryAckSent, 3567 lmpCcLinkSummaryNackReceived, 3568 lmpCcLinkSummaryNackSent, 3569 lmpCcChannelStatusReceived, 3570 lmpCcChannelStatusSent, 3571 lmpCcChannelStatusRetransmit, 3572 lmpCcChannelStatusAckReceived, 3573 lmpCcChannelStatusAckSent, 3574 lmpCcChannelStatusReqReceived, 3575 lmpCcChannelStatusReqSent, 3576 lmpCcChannelStatusReqRetransmit, 3577 lmpCcChannelStatusRspReceived, 3578 lmpCcChannelStatusRspSent, 3579 lmpCcCounterDiscontinuityTime, 3580 lmpTeInOctets, 3581 lmpTeOutOctets, 3582 lmpTeBeginVerifyReceived, 3583 lmpTeBeginVerifySent, 3584 lmpTeBeginVerifyRetransmit, 3585 lmpTeBeginVerifyAckReceived, 3586 lmpTeBeginVerifyAckSent, 3587 lmpTeBeginVerifyNackReceived, 3588 lmpTeBeginVerifyNackSent, 3589 lmpTeEndVerifyReceived, 3590 lmpTeEndVerifySent, 3591 lmpTeEndVerifyRetransmit, 3592 lmpTeEndVerifyAckReceived, 3593 lmpTeEndVerifyAckSent, 3594 lmpTeTestStatusSuccessReceived, 3595 lmpTeTestStatusSuccessSent, 3596 lmpTeTestStatusSuccessRetransmit, 3597 lmpTeTestStatusFailureReceived, 3598 lmpTeTestStatusFailureSent, 3599 lmpTeTestStatusFailureRetransmit, 3600 lmpTeTestStatusAckReceived, 3601 lmpTeTestStatusAckSent, 3602 lmpTeLinkSummaryReceived, 3603 lmpTeLinkSummarySent, 3604 lmpTeLinkSummaryRetransmit, 3605 lmpTeLinkSummaryAckReceived, 3606 lmpTeLinkSummaryAckSent, 3607 lmpTeLinkSummaryNackReceived, 3608 lmpTeLinkSummaryNackSent, 3609 lmpTeChannelStatusReceived, 3610 lmpTeChannelStatusSent, 3611 lmpTeChannelStatusRetransmit, 3612 lmpTeChannelStatusAckReceived, 3613 lmpTeChannelStatusAckSent, 3614 lmpTeChannelStatusReqReceived, 3615 lmpTeChannelStatusReqSent, 3616 lmpTeChannelStatusReqRetransmit, 3617 lmpTeChannelStatusRspSent, 3618 lmpTeChannelStatusRspReceived, 3619 lmpTeCounterDiscontinuityTime, 3620 lmpDataLinkTestReceived, 3621 lmpDataLinkTestSent, 3622 lmpDataLinkActiveTestSuccess, 3623 lmpDataLinkActiveTestFailure, 3624 lmpDataLinkPassiveTestSuccess, 3625 lmpDataLinkPassiveTestFailure, 3626 lmpDataLinkDiscontinuityTime 3627 } 3628 STATUS current 3629 DESCRIPTION 3630 "Collection of objects used to provide performance 3631 information about LMP interfaces and data-bearing links." 3632 ::= { lmpGroups 7 } 3634 lmpTeLinkGroup OBJECT-GROUP 3635 OBJECTS { lmpTeLinkNbrRemoteNodeId, 3636 lmpTeLinkVerification, 3637 lmpTeLinkFaultManagement, 3638 lmpTeLinkDwdm, 3639 lmpTeLinkOperStatus, 3640 lmpTeLinkRowStatus, 3641 lmpTeLinkStorageType, 3642 lmpTeLinkNotificationsEnabled 3643 } 3644 STATUS current 3645 DESCRIPTION 3646 "Objects that can be used to configure TE links." 3647 ::= { lmpGroups 8 } 3649 lmpDataLinkGroup OBJECT-GROUP 3650 OBJECTS { lmpDataLinkType, 3651 lmpDataLinkAddressType, 3652 lmpDataLinkIpAddr, 3653 lmpDataLinkRemoteIpAddress, 3654 lmpDataLinkRemoteIfId, 3655 lmpDataLinkEncodingType, 3656 lmpDataLinkActiveOperStatus, 3657 lmpDataLinkPassiveOperStatus, 3658 lmpDataLinkRowStatus, 3659 lmpDataLinkStorageType 3660 } 3661 STATUS current 3662 DESCRIPTION 3663 "Collection of objects that represent data-bearing link 3664 configuration." 3665 ::= { lmpGroups 9 } 3667 lmpNotificationGroup NOTIFICATION-GROUP 3668 NOTIFICATIONS { lmpTeLinkPropertyMismatch, 3669 lmpDataLinkPropertyMismatch, 3670 lmpUnprotected, 3671 lmpControlChannelUp, 3672 lmpControlChannelDown, 3673 lmpTeLinkDegraded, 3674 lmpTeLinkNotDegraded, 3675 lmpDataLinkVerificationFailure } 3676 STATUS current 3677 DESCRIPTION 3678 "Set of notifications defined in this module." 3679 ::= { lmpGroups 10 } 3681 -- End of LMP-MIB 3682 END 3684 10. Security Considerations 3686 There are a number of management objects defined in this MIB module 3687 with a MAX-ACCESS clause of read-write and/or read-create. Such 3688 objects may be considered sensitive or vulnerable in some network 3689 environments. The support for SET operations in a non-secure 3690 environment without proper protection can have a negative effect on 3691 network operations. These are the tables and objects and their 3692 sensitivity/vulnerability: 3694 - Unauthorized changes to the lmpNbrTable, lmpControlChannelTable, 3695 lmpTeLinkTable, and lmpDataLinkTable may disrupt allocation of 3696 resources in the network. 3698 Some of the readable objects in this MIB module (i.e., objects with a 3699 MAX-ACCESS other than not-accessible) may be considered sensitive or 3700 vulnerable in some network environments. It is thus important to 3701 control even GET and/or NOTIFY access to these objects and possibly 3702 to even encrypt the values of these objects when sending them over 3703 the network via SNMP. These are the tables and objects and their 3704 sensitivity/vulnerability: 3706 - The lmpNbrTable exposes network provider's node IP addresses. 3708 - lmpControlChannelTable exposes network provider's control 3709 network. 3711 - lmpDataLinkTable exposes network provider's data network. 3713 SNMP versions prior to SNMPv3 did not include adequate security. 3714 Even if the network itself is secure (for example by using IPSec), 3715 even then, there is no control as to who on the secure network is 3716 allowed to access and GET/SET (read/change/create/delete) the objects 3717 in this MIB module. 3719 It is RECOMMENDED that implementers consider the security features as 3720 provided by the SNMPv3 framework (see [RFC3410], section 8), 3721 including full support for the SNMPv3 cryptographic mechanisms (for 3722 authentication and privacy). 3724 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3725 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3726 enable cryptographic security. It is then a customer/operator 3727 responsibility to ensure that the SNMP entity giving access to an 3728 instance of this MIB module is properly configured to give access to 3729 the objects only to those principals (users) that have legitimate 3730 rights to indeed GET or SET (change/create/delete) them. 3732 11. Contributors 3734 Sudheer Dharanikota 3735 EMail: sudheer@ieee.org 3737 12. Acknowledgements 3739 The general structure of this document has been modeled around the 3740 MPLS Label Switching Router (LSR) MIB [RFC3813]. 3742 The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and 3743 George Wang. 3745 Thanks to Tom Petch for spotting inconsistencies in RFC 4327 and to 3746 Bert Wijnen for document review. 3748 13. IANA Considerations 3750 No new IANA actions are requested in this document. All IANA actions 3751 from RFC 4327 still hold and are reproduced here for information. 3753 Note that new assignments can only be made via a Standards Action as 3754 specified in [RFC2434]. 3756 13.1. IANA Considerations for lmp ifType 3758 The IANA has assigned 227 ifType for LMP interfaces. 3760 13.2. IANA Considerations for LMP-MIB 3762 The IANA has assigned { transmission 227 } to the LMP-MIB module 3763 specified in this document. 3765 14. Changes from RFC 4327 to RFC XXXX 3766 -- RFC Editor: Please replace XXXX with the assigned RFC number and 3767 -- remove this note. 3769 The following changes have been made relative to RFC 4327. 3771 a. Show that this document obsoletes RFC 4327. 3772 b. Indicate in Abstract that this document provides minor corrections 3773 to RFC 4327. 3774 c. Correct use of TruthValue settings such that True is always 1, and 3775 False is always 2. 3776 d. Update to acknowledgements section. 3777 e. Note in IANA section to show no further action required. 3778 f. Remove identification of RFC 4327 and request RFC Editor to insert 3779 new RFC number. 3780 g. Update timestamps. 3781 h. Update author information. 3782 i. Added punctuation to REFERENCE clauses. 3783 j. Update Revision History clause. 3784 k. Add this section. 3785 l. Remove square braces from references to external documents from 3786 within the MIB module itself. 3788 15. References 3790 15.1. Normative References 3792 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3793 Requirement Levels", BCP 14, RFC 2119, March 1997. 3795 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing 3796 an IANA Considerations Section in RFCs", BCP 26, RFC 3797 2434, October 1998. 3799 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3800 "Structure of Management Information Version 2 3801 (SMIv2)", STD 58, RFC 2578, April 1999. 3803 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3804 "Textual Conventions for SMIv2", STD 58, RFC 2579, 3805 April 1999. 3807 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3808 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3809 April 1999. 3811 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3812 MIB", RFC 2863, June 2000. 3814 [RFC2914] Floyd, S., "Congestion Control Principles", BCP 41, RFC 3815 2914, September 2000. 3817 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching 3818 (GMPLS) Signaling Functional Description", RFC 3471, 3819 January 2003. 3821 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 3822 Schoenwaelder, "Textual Conventions for Internet 3823 Network Addresses", RFC 4001, February 2005. 3825 [RFC4204] Lang, J., "Link Management Protocol (LMP)", RFC 4204, 3826 October 2005. 3828 [RFC4207] Lang, J. and D. Papadimitriou, "Synchronous Optical 3829 Network (SONET)/Synchronous Digital Hierarchy (SDH) 3830 Encoding for Link Management Protocol (LMP) Test 3831 Messages", RFC 4207, October 2005. 3833 [RFC4209] Fredette, A., Ed. and J. Lang, Ed., "Link Management 3834 Protocol (LMP) for Dense Wavelength Division 3835 Multiplexing (DWDM) Optical Line Systems", RFC 4209, 3836 October 2005. 3838 [RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic 3839 Engineering Link Management Information Base", RFC 3840 4220, November 2005. 3842 15.2. Informative References 3844 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3845 "Introduction and Applicability Statements for 3846 Internet-Standard Management Framework", RFC 3410, 3847 December 2002. 3849 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 3850 "Multiprotocol Label Switching (MPLS) Traffic 3851 Engineering (TE) Management Information Base (MIB)", 3852 RFC 3812, June 2004. 3854 16. Authors' Addresses 3856 Martin Dubuc 3858 EMail: dubuc.consulting@sympatico.ca 3859 Thomas D. Nadeau 3860 Cisco Systems, Inc. 3861 1414 Massachusetts Ave. 3862 Boxborough, MA 01719 3864 EMail: tnadeau@cisco.com 3866 Jonathan P. Lang 3867 Sonos, Inc. 3868 223 E. De La Guerra St. 3869 Santa Barbara, CA 93101 3871 EMail: jplang@ieee.org 3873 Evan McGinnis 3874 Hammerhead Systems 3875 640 Clyde Court 3876 Mountain View, CA 94043 3878 EMail: emcginnis@hammerheadsystems.com 3880 Adrian Farrel 3881 Old Dog Consulting 3883 Email: adrian@olddog.co.uk 3885 Full Copyright Statement 3887 Copyright (C) The Internet Society (2006). 3889 This document is subject to the rights, licenses and restrictions 3890 contained in BCP 78, and except as set forth therein, the authors 3891 retain all their rights. 3893 This document and the information contained herein are provided on an 3894 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 3895 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 3896 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 3897 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 3898 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3899 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3901 Intellectual Property 3903 The IETF takes no position regarding the validity or scope of any 3904 Intellectual Property Rights or other rights that might be claimed to 3905 pertain to the implementation or use of the technology described in 3906 this document or the extent to which any license under such rights 3907 might or might not be available; nor does it represent that it has 3908 made any independent effort to identify any such rights. Information 3909 on the procedures with respect to rights in RFC documents can be 3910 found in BCP 78 and BCP 79. 3912 Copies of IPR disclosures made to the IETF Secretariat and any 3913 assurances of licenses to be made available, or the result of an 3914 attempt made to obtain a general license or permission for the use of 3915 such proprietary rights by implementers or users of this 3916 specification can be obtained from the IETF on-line IPR repository at 3917 http://www.ietf.org/ipr. 3919 The IETF invites any interested party to bring to its attention any 3920 copyrights, patents or patent applications, or other proprietary 3921 rights that may cover technology that may be required to implement 3922 this standard. Please address the information to the IETF at 3923 ietf-ipr@ietf.org. 3925 Acknowledgement 3927 Funding for the RFC Editor function is provided by the IETF 3928 Administrative Support Activity (IASA).