idnits 2.17.1 draft-ietf-ccamp-lmp-mib-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 18 instances of too long lines in the document, the longest one being 5 characters in excess of 72. ** The abstract seems to contain references ([LMP]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 129, but not defined == Missing Reference: 'IF-MIB' is mentioned on line 408, but not defined == Unused Reference: 'GMPLS' is defined on line 2447, but no explicit reference was found in the text == Unused Reference: 'BUNDLE' is defined on line 2456, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 2467, but no explicit reference was found in the text == Unused Reference: 'IANAFamily' is defined on line 2473, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 2493, but no explicit reference was found in the text == Unused Reference: 'RFC2574' is defined on line 2498, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 2503, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 2508, but no explicit reference was found in the text == Unused Reference: 'RFC2575' is defined on line 2511, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 2516, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'LMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS' -- Possible downref: Non-RFC (?) normative reference: ref. 'BUNDLE' -- Possible downref: Non-RFC (?) normative reference: ref. 'BUNDLE-MIB' ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAFamily' ** Obsolete normative reference: RFC 2571 (ref. 'SNMPArch') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. 'SNMPv1Traps') ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. 'SNMPv1') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. 'SNMPv2c') ** Obsolete normative reference: RFC 1906 (ref. 'SNMPv2TM') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. 'SNMPv3MP') (Obsoleted by RFC 2572) -- Duplicate reference: RFC2574, mentioned in 'SNMPv3USM', was also mentioned in 'RFC2574'. ** Obsolete normative reference: RFC 2574 (ref. 'SNMPv3USM') (Obsoleted by RFC 3414) -- Duplicate reference: RFC1905, mentioned in 'SNMPv2PO', was also mentioned in 'RFC1905'. ** Obsolete normative reference: RFC 1905 (ref. 'SNMPv2PO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. 'SNMPv3App') (Obsoleted by RFC 2573) -- Duplicate reference: RFC2575, mentioned in 'SNMPv3VACM', was also mentioned in 'RFC2575'. ** Obsolete normative reference: RFC 2575 (ref. 'SNMPv3VACM') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC') (Obsoleted by RFC 4301) Summary: 26 errors (**), 0 flaws (~~), 14 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Martin Dubuc 3 Internet Draft edgeflow, Inc. 4 Expires: April 2002 5 Sudheer Dharanikota 6 Nayna Networks, Inc. 8 Thomas D. Nadeau 9 Cisco Systems, Inc. 11 Jonathan P. Lang 12 Evan McGinnis 13 Calient Networks, Inc. 15 Link Management Protocol Management Information Base Using SMIv2 17 draft-ietf-ccamp-lmp-mib-00.txt 19 Status of this Memo 21 This document is an Internet-Draft and is in full conformance with 22 all provisions of Section 10 of RFC 2026. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that other 26 groups may also distribute working documents as Internet- Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet- Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 39 Table of Contents 41 1. Abstract ..................................................... 2 42 2. Introduction ................................................. 2 43 3. Terminology .................................................. 3 44 4. The SNMP Management Framework ................................ 3 45 4.1. Object Definitions ........................................... 4 46 5. Feature Checklist ............................................ 4 47 6. Outline ...................................................... 5 48 6.1. Summary of LMP MIB ........................................... 6 49 7. Brief Description of MIB Objects ............................. 6 50 7.1. lmpNbrTable .................................................. 6 51 7.2. lmpControlChannelTable ....................................... 6 52 7.3. lmpControlChannelPerfTable ................................... 6 53 7.4. lmpTeLinkTable ............................................... 7 54 7.5. lmpLinkVerificationTable ..................................... 7 55 7.6. lmpDataBearingLinkTable ...................................... 7 56 7.7. lmpDataBearingLinkPerfTable .................................. 7 57 8. Example of LMP Control Channel Interface Setup ............... 7 58 9. Application of the Interface Group to LMP .................... 10 59 9.1. Support of the LMP Layer by ifTable .......................... 10 60 10. Link Management Protocol MIB Definitions ..................... 12 61 11. Security Considerations ...................................... 51 62 12. Acknowledgments .............................................. 52 63 13. References ................................................... 52 64 14. Authors' Addresses ........................................... 55 65 15. Full Copyright Statement ..................................... 55 67 1. Abstract 69 This memo defines an experimental portion of the Management Informa- 70 tion Base (MIB) for use with network management protocols in the 71 Internet community. In particular, it describes managed objects for 72 modeling the Link Management Protocol (LMP) [LMP]. 74 2. Introduction 76 This memo defines an experimental portion of the Management Informa- 77 tion Base (MIB) for use with network management protocols in the 78 Internet community. In particular, it describes managed objects for 79 modeling the Link Management Protocol (LMP) [LMP]. 81 Comments should be made directly to the ccamp mailing list at 82 ccamp@ops.ietf.org. 84 This memo does not, in its draft form, specify a standard for the 85 Internet community. 87 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 88 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 89 document are to be interpreted as described in RFC 2119, reference 90 [BCP14]. 92 3. Terminology 94 This document uses terminology from the document describing the Link 95 Management Protocol [LMP]. An "LMP adjacency" is formed between two 96 nodes that support the same capabilities, and LMP messages are 97 exchanged between the node pair over control channels that form this 98 adjacency. Several control channels can be active at the same time. 99 With the exception of messages related to control channel management, 100 any time a LMP message needs to be transferred to a neighbor node, it 101 can be sent on any of the active control channels. The control chan- 102 nels can also be used to exchange MPLS control plane information or 103 routing information. 105 LMP is designed to support aggregation of one or more data-bearing 106 links into a traffic-engineering (TE) link. The data-bearing links 107 can be either component links or ports depending on their multiplex- 108 ing capability (see [LMP] for distinction between port and component 109 link). Furthermore, the data-bearing links may be defined as primary 110 or secondary data-bearing links, where a secondary data-bearing link 111 is used to protect a primary data-bearing link, i.e. if a primary 112 data-bearing link fails, data traffic is switched over to one of the 113 secondary data-bearing links. 115 Each TE link is associated with an LMP adjacency, and one or more 116 control channels are used to exchange LMP messages. In turn, control 117 channels are used to manage one or more TE links. 119 4. The SNMP Management Framework 121 The SNMP Management Framework presently consists of five major com- 122 ponents: 124 - An overall architecture, described in RFC 2571 [SNMPArch]. 126 - Mechanisms for describing and naming objects and events for the 127 purpose of management. The first version of this Structure of 128 Management Information (SMI) is called SMIv1 and described in 129 RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 130 [SNMPv1Traps]. The second version, called SMIv2, is described 131 in RFC 2578 [SMIv2], RFC 2579 [SNMPv2TC] and RFC 2580 132 [SNMPv2Conf]. 134 - Message protocols for transferring management information. The 135 first version of the SNMP message protocol is called SNMPv1 136 and described in RFC 1157 [SNMPv1]. A second version of the 137 SNMP message protocol, which is not an Internet standards 138 track protocol, is called SNMPv2c and described in RFC 1901 140 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the 141 message protocol is called SNMPv3 and described in RFC 1906 142 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. 144 - Protocol operations for accessing management information. The 145 first set of protocol operations and associated PDU formats is 146 described in RFC 1157 [SNMPv1]. A second set of protocol 147 operations and associated PDU formats is described in RFC 1905 148 [SNMPv2PO]. 150 - A set of fundamental applications described in RFC 2273 151 [SNMPv3App] and the view-based access control mechanism 152 described in RFC 2575 [SNMPv3VACM]. 154 Managed objects are accessed via a virtual information store, termed 155 the Management Information Base or MIB. Objects in the MIB are 156 defined using the mechanisms defined in the SMI. This memo specifies 157 a MIB module that is compliant to the SMIv2. A MIB conforming to the 158 SMIv1 can be produced through the appropriate translations. The 159 resulting translated MIB must be semantically equivalent, except 160 where objects or events are omitted because no translation is possi- 161 ble (use of Counter64). Some machine-readable information in SMIv2 162 will be converted into textual descriptions in SMIv1 during the 163 translation process. However, this loss of machine-readable informa- 164 tion is not considered to change the semantics of the MIB. 166 4.1. Object Definitions 168 Managed objects are accessed via a virtual information store, termed 169 the Management Information Base or MIB. Objects in the MIB are 170 defined using the subset of Abstract Syntax Notation One (ASN.1) 171 defined in the SMI. In particular, each object type is named by an 172 OBJECT IDENTIFIER, an administratively assigned name. The object 173 type together with an object instance serves to uniquely identify a 174 specific instantiation of the object. For human convenience, we often 175 use a textual string, termed the descriptor, to also refer to the 176 object type. 178 5. Feature Checklist 180 The Link Management protocol MIB (LMP-MIB) is designed to satisfy the 181 following requirements and constraints: 183 - The MIB supports the enabling and disabling of LMP capability 184 on LMP capable interfaces of a photonic switch, optical 185 cross-connect or router. 187 - The MIB is used provide information about LMP adjacencies. 189 - Support is provided for configuration of the keep alive and 190 link verification parameters. 192 - The MIB is used to express the mapping between local and remote 193 TE links, as well as local and remote interface identifiers for 194 port or component link. 196 - Performance counters are provided for measuring LMP 197 performance on a per-control channel basis. Performance counters 198 are 199 also provided for measuring LMP performance on the data-bearing 200 links. 202 Note that the LMP MIB goes hand-in-hand with the Link Bundling MIB 203 [BUNDLE-MIB]. The TE link table, which is used to associate data- 204 bearing links to TE links, is defined in the Link Bundling MIB. The 205 TE link table in the LMP MIB contains TE link information specific to 206 LMP. 208 6. Outline 210 Configuring LMP through an optical device involves the following 211 steps: 213 - Enabling LMP on LMP capable interfaces through control channel 214 configuration. 216 - Optionally specifying link verification parameters. 218 - Configuring the data-bearing links and associating them to the 219 appropriate TE link (this association is stored in the 220 ifStackTable of the Interfaces Group MIB). 222 - Identifying which control channels manage the TE link. 224 6.1. Summary of LMP MIB 226 The MIB objects for performing these actions consist of the following 227 tables: 229 - The remote node table is used to identify the pair 230 of nodes that exchange LMP messages over control channels. 232 - The control channel table (lmpControlChannelTable) is used 233 for enabling the LMP protocol on LMP-capable interfaces. 235 - The control channel performance table 236 (lmpControlChannelPerfTable) is used for collecting 237 LMP performance counts on a per-control channel basis. 239 - The TE link table (lmpTeLinkTable) is used for 240 specifying LMP information associated with TE links. 242 - The link verification table (lmpLinkVerificationTable) is used for 243 configuring the LMP link verification parameters of TE links. 245 - The data-bearing link table (lmpDataBearingLinkTable) is used to 246 specify the data-bearing links that are associated with TE links. 248 - The data-bearing link performance table 249 (lmpDataBearingLinkPerfTable) is used for collecting LMP 250 performance counts on data-bearing links. 252 These tables are described in the subsequent sections. 254 7. Brief Description of MIB Objects 256 Sections 7.1-7.3 describe objects pertaining to LMP-capable inter- 257 faces. Section 7.4 to 7.7 describes objects for specifying TE links 258 and data-bearing links. The MIB objects were derived from the LMP 259 document [LMP]. 261 7.1. lmpNbrTable 263 This table identifies the pairs of nodes on which LMP is enabled. 265 7.2. lmpControlChannelTable 267 This table represents the interfaces that are LMP capable (i.e. capa- 268 ble of transmitting LMP messages). A photonic switch, optical cross- 269 connect, or router creates an entry in this table for every LMP capa- 270 ble interface on that device. 272 7.3. lmpControlChannelPerfTable 274 This table contains the objects to measure the LMP performance of LMP 275 capable interfaces and is an AUGMENT to the lmpControlChannelTable. 276 High capacity counters are provided for objects that are likely to 277 wrap around quickly. 279 7.4. lmpTeLinkTable 281 This table represents the TE link information specific to LMP. 283 7.5. lmpLinkVerificationTable 285 This table represents the link verification parameters associated 286 with the TE links. 288 7.6. lmpDataBearingLinkTable 290 The data-bearing link table enumerates the data-bearing links that 291 are associated with each TE link. 293 7.7. lmpDataBearingLinkPerfTable 295 This table contains the objects to measure the LMP performance of 296 data-bearing links and is an AUGMENT to the lmpDataBearingLinkTable. 298 8. Example of LMP Control Channel Setup 300 In this section we provide a brief example of using the MIB 301 objects described in section 11 to set up an LMP control channel. 302 While this example is not meant to illustrate every nuance of the 303 MIB, it is intended as an aid to understanding some of the key 304 concepts. It is meant to be read after going through the MIB itself. 306 Suppose that one would like to form an LMP adjacency between two 307 nodes using two control channels. Suppose also that there are 308 three data-bearing links. We also assume that the data-bearing 309 links are ports (lambdas). We also assume that the link 310 verification procedure is not enabled. The following example 311 illustrates which rows and corresponding objects might be created 312 to accomplish this. 314 First, LMP must be enabled between the pair of nodes. 316 In lmpNbrTable: 317 { 318 lmpNbrNodeId = 'c0010101'H, -- 192.1.1.1 319 lmpNbrRetransmitInterval = 10, 320 lmpNbrAdminStatus = up(1), 321 lmpNbrRowStatus = createAndGo(4) 322 } 324 Then, the control channels must be set up. These are created in 325 the lmpControlChannelTable. 327 In lmpControlChannelTable: 328 { 329 ifIndex = 1, 330 lmpCcUnderlyingIfIndex = 1, 331 lmCcIsIf = false(1), 332 lmpCcAuthentication = false(1), 333 lmpCcConfigRetransmitInterval = 10, 334 lmpCcHelloInterval = 15, 335 lmpCcHelloIntervalMin = 15, 336 lmpCcHelloIntervalMax = 1000, 337 lmpCcHelloDeadInterval = 45, 338 lmpCcHelloDeadIntervalMin = 45, 339 lmpCcHelloDeadIntervalMax = 1000, 340 lmpCcAdminStatus = up(1), 341 lmpCcRowStatus = createAndGo(4) 342 } 344 { 345 lmpCcId = 2, 346 lmpCcUnderlyingIfIndex = 2, 347 lmCcIsIf = false(1), 348 lmpCcAuthentication = false(1), 349 lmpCcConfigRetransmitInterval = 10, 350 lmpCcHelloInterval = 15, 351 lmpCcHelloIntervalMin = 15, 352 lmpCcHelloIntervalMax = 1000, 353 lmpCcHelloDeadInterval = 45, 354 lmpCcHelloDeadIntervalMin = 45, 355 lmpCcHelloDeadIntervalMax = 1000, 356 lmpCcAdminStatus = up(1), 357 lmpCcRowStatus = createAndGo(4) 358 } 360 Next, the three data-bearing links are created. For each data- 361 bearing link, an ifEntry with the same ifIndex needs to be created 362 beforehand. 364 In lmpDataBearingLinkTable: 365 { 366 ifIndex = 41, 367 lmpDataBearingLinkRemoteIfId = 47, 368 lmpDataBearingLinkRowStatus = createAndGo(4) 369 } 371 { 372 ifIndex = 43, 373 lmpDataBearingLinkRemoteIfId = 42, 374 lmpDataBearingLinkRowStatus = createAndGo(4) 375 } 377 { 378 ifIndex = 44, 379 lmpDataBearingLinkRemoteIfId = 48, 380 lmpDataBearingLinkRowStatus = createAndGo(4) 381 } 383 Note that the data-bearing link type (lmpDataBearingLinkType) does 384 not need to be provisioned as it is automatically populated by the 385 node. The definition of the protection role (primary or 386 secondary) for the data-bearing links is stored in the 387 dataBearingChannelTable of the Link Bundling MIB [BUNDLE-MIB]. 389 Then, a TE link is created as an ifEntry with ifType teLink in 390 the ifTable. 392 Once the TE link is created in the ifTable, a TE link entry 393 is created in the LMP MIB to specify TE link information specific 394 to LMP. 396 In lmpTeLinkTable: 397 { 398 ifIndex = 20, 399 lmpTeLinkVerification = true(2), 400 lmpTeLinkFaultIsolation = true(2), 401 lmpTeLinkDwdm = false(1), 402 lmpTeLinkBitRate = 100000, 403 lmpTeLinkWavelength = 0, 404 lmpTeLinkRowStatus = createAndGo(4) 405 } 407 The association between the data-bearing links and the TE links is 408 stored in the ifStackTable [IF-MIB]. 410 In parallel with the entry created in the lmpTeLinkTable, an entry 411 may be created in the teLinkTable of Link Bundling MIB 412 [BUNDLE-MIB]. 414 9. Application of the Interface Group to LMP 416 The Interfaces Group of MIB II defines generic managed objects for 417 managing interfaces. This memo contains the media-specific 418 extensions to the Interfaces Group for managing LMP control channels 419 that are modeled as interfaces. If the control channel as defined in 420 the lmpControlChannelTable is modeled as an ifEntry, then the 421 following definition applies. An lmpControlChannelTable entry is 422 designated as being represented as an Interfaces MIB ifEntry if the 423 lmpControlChannelEntry object lmpCcIsIf is set to true (2). In this 424 case, the control channel SHOULD be modeled as an ifEntry and 425 provide appropriate interface stacking as defined below. 427 This memo assumes the interpretation of the Interfaces Group to be 428 in accordance with [IFMIB] which states that the interfaces table 429 (ifTable) contains information on the managed resource's 430 interfaces and that each sub-layer below the internetwork layer of 431 a network interface is considered an interface. Since the LMP 432 interface only carries control traffic, it is considered to be below 433 the internetwork layer. Thus, the LMP interface may be represented 434 as an entry in the ifTable. The inter-relation of entries in the 435 ifTable is defined by Interfaces Stack Group defined in [IFMIB]. 437 When LMP control channels are modeled as interfaces, the interface 438 stack table must appear as follows for the LMP control channel 439 interfaces: 441 +----------------------------------------+ 442 | LMP-interface ifType = lmp(TBD) + 443 +----------------------------------------+ 444 | Underlying Layer... + 445 +----------------------------------------+ 447 In the above diagram, "Underlying Layer..." refers to the ifIndex 448 of any interface type over which the LMP interface will transmit 449 its traffic. Note that if the underlying layer provides multiple 450 access to its media (i.e.: Ethernet), then it is possible to stack 451 multiple LMP interfaces on top of this interface in parallel. 453 9.1. Support of the LMP Layer by ifTable 455 Some specific interpretations of ifTable for the LMP layer 456 follow. 458 Object Use for the LMP layer 460 ifIndex Each LMP interface may be represented by an ifEntry. 462 ifDescr Description of the LMP interface. 464 ifType The value that is allocated for LMP is TBD. 465 This number will be assigned by the IANA. 467 ifSpeed The total bandwidth in bits per second for use by 468 the LMP layer. 470 ifPhysAddress Unused. 472 ifAdminStatus This variable indicates the administrator's intent 473 as to whether LMP should be enabled, disabled, or 474 running in some diagnostic testing mode on this 475 interface. Also see [IFMIB]. 477 ifOperStatus This value reflects the actual or operational 478 status of LMP on this interface. 480 ifLastChange See [IFMIB]. 482 ifInOctets The number of received octets over the interface, 483 i.e., the number of received, octets received as 484 labeled packets. 486 ifOutOctets The number of transmitted octets over the 487 interface, i.e., the number of octets transmitted 488 as labeled packets. 490 ifInErrors The number of labeled packets dropped due to 491 uncorrectable errors. 493 ifInUnknownProtos 494 The number of received packets discarded during 495 packet header validation, including packets with 496 unrecognized label values. 498 ifOutErrors See [IFMIB]. 500 ifName Textual name (unique on this system) of the 501 interface or an octet string of zero length. 503 ifLinkUpDownTrapEnable 504 Default is disabled (2). 506 ifConnectorPresent 507 Set to false (2). 509 ifHighSpeed See [IFMIB]. 511 ifHCInOctets The 64-bit version of ifInOctets; supported if 512 required by the compliance statements in [IFMIB]. 514 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 515 required by the compliance statements in [IFMIB]. 517 ifAlias The non-volatile 'alias' name for the interface as 518 specified by a network manager. 520 ifCounterDiscontinuityTime 521 See [IFMIB]. 523 10. LMP MIB Definitions 525 LMP-MIB DEFINITIONS ::= BEGIN 527 IMPORTS 528 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 529 experimental, Integer32, Unsigned32, Counter32, Counter64, 530 TimeTicks, IpAddress 531 FROM SNMPv2-SMI 533 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 534 FROM SNMPv2-CONF 536 TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, 537 RowPointer, TimeStamp 538 FROM SNMPv2-TC 540 InterfaceIndex, InterfaceIndexOrZero, ifIndex, ifStackHigherLayer 541 FROM IF-MIB 543 teLinkRemoteIpAddr, teLinkIncomingIfId 544 FROM LINK-BUNDLING-MIB; 546 lmpMIB MODULE-IDENTITY 547 LAST-UPDATED "200110181200Z" -- 18 October 2001 12:00:00 EST 548 ORGANIZATION "Common Control and Measurement Protocols (CCAMP) 549 Working Group" 550 CONTACT-INFO 551 " Martin Dubuc 552 Postal: edgeflow, Inc. 553 329 March Rd. 554 Kanata, ON, CANADA K2K 2E1 555 Tel: +1-613-270-9279 x253 556 Email: martin.dubuc@edgeflow.com 557 Sudheer Dharanikota 558 Postal: Nayna Networks, Inc. 559 157 Topaz Street 560 Milipitas, CA 95035 561 Tel: +1-408-956-8000 x357 562 Email: sudheer@nayna.com 564 Thomas D. Nadeau 565 Postal: Cisco Systems, Inc. 566 300 Apollo Drive 567 Chelmsford, MA 01824 568 Tel: +1-978-244-3051 569 Email: tnadeau@cisco.com 571 Jonathan P. Lang 572 Postal: Calient Networks, Inc. 573 25 Castilian Drive 574 Goleta, CA 93117 575 Email: jplang@calient.net 577 Evan McGinnis 578 Postal: Calient Networks, Inc. 579 5853 Rue Ferrari 580 San Jose, CA 95138 581 Email: evan@calient.net" 583 DESCRIPTION 584 "This MIB contains managed object definitions for the 585 Link Management Protocol (LMP) as 586 defined in: Lang, J., Mitra, K., Drake, J., Kompella, K., 587 Rekhter, Y., Berger, L., Saha, D., 588 Basak, D., Sandick, H., Zinin, A., and 589 Rajagopalan, B., Link Management Protocol, 590 Internet Draft , 591 September 2001." 593 -- Revision history. 594 REVISION 595 "200110181200Z" -- 18 October 2001 12:00:00 EST 596 DESCRIPTION 597 "- Minor syntax fixes. 598 - Added lmpCcId. Changed type of lmpRemoteCcId. 599 - Updated lmpTeLinkEncodingType. 600 - Removed lmpRemoteTeLinkType and lmpRemoteTeLinkId (their 601 content can be derived from LINK-BUNDLING-MIB). 602 - Added lmpCcLastChange, lmpCcCounterDiscontinuityTime and 603 lmpDataBearingLinkCounterDiscontinuityTime. 605 - Moved lmpTeLinkBitRate and lmpTeLinkWavelength to 606 lmpLinkVerificationTable. 607 - Updated lmpDataBearingLinkOperStatus. 608 - Modified performance counters to account for changes in 609 channel status message types. 610 - Changed indices for lmpTeLinkPropertyMismatch and 611 lmpDataBearingLinkPropertyMismatch traps. 612 - Renamed lmpNbrLinkSumRetransmitInterval. Removed 613 lmpNbrRetransmitTimeout. 614 - Added lmpCcUnderlyingIfId, lmpCcIsIf and lmpCcSetupRole." 615 REVISION 616 "200105221200Z" -- 22 May 2001 12:00:00 EST 617 DESCRIPTION 618 "Updates based on IETF-50 feedback. Aligned with 619 upcoming version of LMP draft." 620 REVISION 621 "200102221200Z" -- 22 February 2001 12:00:00 EST 622 DESCRIPTION 623 "Updates based on MPLS mailing list feedback." 624 REVISION 625 "200101261200Z" -- 26 January 2001 12:00:00 EST 626 DESCRIPTION 627 "Initial draft version." 628 ::= { experimental 113 } 630 -- Textual Conventions 632 NodeID ::= TEXTUAL-CONVENTION 633 STATUS current 634 DESCRIPTION 635 "This value represents a Node ID." 636 SYNTAX IpAddress 638 LmpInterval ::= TEXTUAL-CONVENTION 639 DISPLAY-HINT "d" 640 STATUS current 641 DESCRIPTION 642 "The interval delay in milliseconds." 643 SYNTAX Unsigned32 (1..65535) 645 LmpRetransmitInterval ::= TEXTUAL-CONVENTION 646 DISPLAY-HINT "d" 647 STATUS current 648 DESCRIPTION 649 "The retransmission interval delay in milliseconds." 650 SYNTAX Unsigned32 (1..4294967295) 652 -- Top level components of this MIB 654 -- Traps 655 lmpNotifications OBJECT IDENTIFIER ::= { lmpMIB 0 } 656 -- Tables, Scalars 657 lmpObjects OBJECT IDENTIFIER ::= { lmpMIB 1 } 658 -- Conformance 659 lmpConformance OBJECT IDENTIFIER ::= { lmpMIB 2 } 661 lmpAdminStatus OBJECT-TYPE 662 SYNTAX INTEGER { up(1), down(2) } 663 MAX-ACCESS read-write 664 STATUS current 665 DESCRIPTION 666 "The desired operational status of LMP on the node." 667 DEFVAL { up } 668 ::= { lmpObjects 1 } 670 -- LMP Neighbor Table 672 lmpNbrTable OBJECT-TYPE 673 SYNTAX SEQUENCE OF LmpNbrEntry 674 MAX-ACCESS not-accessible 675 STATUS current 676 DESCRIPTION 677 "This table specifies the neighbor node to which control channels 678 may be established." 679 ::= { lmpObjects 2 } 681 lmpNbrEntry OBJECT-TYPE 682 SYNTAX LmpNbrEntry 683 MAX-ACCESS not-accessible 684 STATUS current 685 DESCRIPTION 686 "An entry in this table is created by a LMP-enabled device for 687 every pair of nodes that can establish control channels." 688 INDEX { lmpNbrNodeId } 689 ::= { lmpNbrTable 1 } 691 LmpNbrEntry ::= SEQUENCE { 692 lmpNbrNodeId NodeID, 693 lmpNbrRetransmitInterval LmpRetransmitInterval, 694 lmpNbrAdminStatus INTEGER, 695 lmpNbrOperStatus INTEGER, 696 lmpNbrRowStatus RowStatus, 697 lmpNbrStorageType StorageType 699 } 701 lmpNbrNodeId OBJECT-TYPE 702 SYNTAX NodeID 703 MAX-ACCESS accessible-for-notify 704 STATUS current 705 DESCRIPTION 706 "This is a unique index for an entry in the 707 LmpNbrTable. This value represents the 708 remote Node ID." 709 ::= { lmpNbrEntry 1 } 711 lmpNbrRetransmitInterval OBJECT-TYPE 712 SYNTAX LmpRetransmitInterval 713 MAX-ACCESS read-create 714 STATUS current 715 DESCRIPTION 716 "This object specifies the interval that is used for the 717 retransmission of LinkSummary, BeginVerify and EndVerify messages." 718 REFERENCE 719 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 720 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 721 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 722 B. Rajagopalan, September 2001." 723 ::= { lmpNbrEntry 2 } 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 3 } 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 4 } 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." 748 ::= { lmpNbrEntry 5 } 750 lmpNbrStorageType OBJECT-TYPE 751 SYNTAX StorageType 752 MAX-ACCESS read-create 753 STATUS current 754 DESCRIPTION 755 "The storage type for this entry." 756 ::= { lmpNbrEntry 6 } 758 -- End of lmpNbrTable 760 lmpCcHelloIntervalDefault OBJECT-TYPE 761 SYNTAX LmpInterval 762 MAX-ACCESS read-write 763 STATUS current 764 DESCRIPTION 765 "This object specifies the default value for the HelloInterval 766 parameter used in the Hello protocol keep-alive phase. It 767 indicates how frequently LMP Hello messages will be sent." 768 REFERENCE 769 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 770 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 771 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 772 B. Rajagopalan, September 2001." 773 ::= { lmpObjects 3 } 775 lmpCcHelloIntervalDefaultMin OBJECT-TYPE 776 SYNTAX LmpInterval 777 MAX-ACCESS read-write 778 STATUS current 779 DESCRIPTION 780 "This object specifies the default minimum value for the 781 HelloInterval parameter." 782 ::= { lmpObjects 4 } 784 lmpCcHelloIntervalDefaultMax OBJECT-TYPE 785 SYNTAX LmpInterval 786 MAX-ACCESS read-write 787 STATUS current 788 DESCRIPTION 789 "This object specifies the default maximum value for the 790 HelloInterval parameter." 791 ::= { lmpObjects 5 } 793 lmpCcHelloDeadIntervalDefault OBJECT-TYPE 794 SYNTAX LmpInterval 795 MAX-ACCESS read-write 796 STATUS current 797 DESCRIPTION 798 "This object specifies the default HelloDeadInterval parameter to 799 use in the Hello protocol keep-alive phase. It indicates how long 800 a device should wait before declaring the control channel dead. 801 The HelloDeadInterval parameter must be greater than the 802 HelloInterval parameter and should be at least three times the 803 value of HelloInterval." 804 REFERENCE 805 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 806 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 807 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 808 B. Rajagopalan, September 2001." 809 ::= { lmpObjects 6 } 811 lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE 812 SYNTAX LmpInterval 813 MAX-ACCESS read-write 814 STATUS current 815 DESCRIPTION 816 "This object specifies the default minimum value for the 817 HelloDeadInterval parameter." 818 ::= { lmpObjects 7 } 820 lmpCcHelloDeadIntervalDefaultMax OBJECT-TYPE 821 SYNTAX LmpInterval 822 MAX-ACCESS read-write 823 STATUS current 824 DESCRIPTION 825 "This object specifies the default maximum value for the 826 HelloDeadInterval parameter." 827 ::= { lmpObjects 8 } 829 -- LMP Control Channel Table 831 lmpControlChannelTable OBJECT-TYPE 832 SYNTAX SEQUENCE OF LmpControlChannelEntry 833 MAX-ACCESS not-accessible 834 STATUS current 835 DESCRIPTION 836 "This table specifies LMP control channel information." 837 ::= { lmpObjects 9 } 839 lmpControlChannelEntry OBJECT-TYPE 840 SYNTAX LmpControlChannelEntry 841 MAX-ACCESS not-accessible 842 STATUS current 843 DESCRIPTION 844 "An entry in this table is created by a LMP-enabled device for 845 every control channel. Whenever a new entry is created with lmpCcIsIf 846 set to true(2), then a corresponding entry is created in ifTable as 847 well (see RFC 2863)." 848 INDEX { lmpCcId } 849 ::= { lmpControlChannelTable 1 } 851 LmpControlChannelEntry ::= SEQUENCE { 852 lmpCcId Unsigned32, 853 lmpCcUnderlyingIfIndex InterfaceIndexOrZero, 854 lmpCcIsIf TruthValue, 855 lmpCcNbrNodeId NodeID, 856 lmpRemoteCcId Unsigned32, 857 lmpCcSetupRole INTEGER, 858 lmpCcAuthentication TruthValue, 859 lmpCcConfigRetransmitInterval LmpRetransmitInterval, 860 lmpCcConfigRetransmitTimeout Unsigned32, 861 lmpCcHelloInterval LmpInterval, 862 lmpCcHelloIntervalMin LmpInterval, 863 lmpCcHelloIntervalMax LmpInterval, 864 lmpCcHelloDeadInterval LmpInterval, 865 lmpCcHelloDeadIntervalMin LmpInterval, 866 lmpCcHelloDeadIntervalMax LmpInterval, 867 lmpCcLastChange TimeTicks, 868 lmpCcAdminStatus INTEGER, 869 lmpCcOperStatus INTEGER, 870 lmpCcRowStatus RowStatus, 871 lmpCcStorageType StorageType 872 } 874 lmpCcId OBJECT-TYPE 875 SYNTAX Unsigned32 876 MAX-ACCESS read-create 877 STATUS current 878 DESCRIPTION 879 "This value represents the local control channel identifier." 880 ::= { lmpControlChannelEntry 1 } 882 lmpCcUnderlyingIfIndex OBJECT-TYPE 883 SYNTAX InterfaceIndexOrZero 884 MAX-ACCESS read-create 885 STATUS current 886 DESCRIPTION 887 "This value represents the underlying interface index. If set to 0, 888 then the control channel is not associated with any underlying 889 interface. If the control channel is not associated with an 890 underlying interface, the control channel's operational status 891 must not be up(1), nor should the control channel forward or 892 receive traffic." 893 ::= { lmpControlChannelEntry 2 } 895 lmpCcIsIf OBJECT-TYPE 896 SYNTAX TruthValue 897 MAX-ACCESS read-create 898 STATUS current 899 DESCRIPTION 900 "Denotes whether or not this control channel corresponds to 901 an interface represented in the interfaces group table." 902 ::= { lmpControlChannelEntry 3 } 904 lmpCcNbrNodeId OBJECT-TYPE 905 SYNTAX NodeID 906 MAX-ACCESS read-only 907 STATUS current 908 DESCRIPTION 909 "This is the Node ID of the control channel remote node. 910 This value gets created by the node when a Config message 911 is received or when an outgoing Config message is acknowledged 912 by the remote node." 913 ::= { lmpControlChannelEntry 4 } 915 lmpRemoteCcId OBJECT-TYPE 916 SYNTAX Unsigned32 917 MAX-ACCESS read-only 918 STATUS current 919 DESCRIPTION 920 "This value represents the remote control channel identifier. It is 921 determined during the negotiation phase. A value 922 of zero means that the remote control channel identifier has not 923 yet been assigned." 924 ::= { lmpControlChannelEntry 5 } 926 lmpCcSetupRole OBJECT-TYPE 927 SYNTAX INTEGER { active(1), passive(2) } 928 MAX-ACCESS read-create 929 STATUS current 930 DESCRIPTION 931 "The role that this node should take during establishment of this 932 control channel. An active node will initiate establishment. A 933 passive node will wait for the remote node to initiate. A pair 934 of nodes that both take the passive role will never establish 935 communications." 936 DEFVAL { active } 937 ::= { lmpControlChannelEntry 6 } 939 lmpCcAuthentication OBJECT-TYPE 940 SYNTAX TruthValue 941 MAX-ACCESS read-create 942 STATUS current 943 DESCRIPTION 944 "This object indicates whether the control channel should use 945 authentication." 946 REFERENCE 947 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 948 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 949 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 950 B. Rajagopalan, September 2001." 951 ::= { lmpControlChannelEntry 7 } 953 lmpCcConfigRetransmitInterval OBJECT-TYPE 954 SYNTAX LmpRetransmitInterval 955 MAX-ACCESS read-create 956 STATUS current 957 DESCRIPTION 958 "This object specifies the interval that is used for the 959 retransmission of Config messages during the parameter 960 negotiation phase." 961 REFERENCE 962 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 963 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 964 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 965 B. Rajagopalan, September 2001." 966 ::= { lmpControlChannelEntry 8 } 968 lmpCcConfigRetransmitTimeout OBJECT-TYPE 969 SYNTAX Unsigned32 970 MAX-ACCESS read-create 971 STATUS current 972 DESCRIPTION 973 "This object specifies the Config retransmission timeout 974 period. If the specified timeout expires and no Config, 975 ConfigAck or ConfigNack message has been received, a node 976 can stop retransmitting Config messages on the control 977 channel. A value of 0 is used to indicate that a node should 978 never stop retransmission." 979 REFERENCE 980 "draft-ccamp-ietf-lmp-01.txt - Link Management Protocol (LMP), 981 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 982 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 983 B. Rajagopalan, September 2001." 984 DEFVAL { 0 } 985 ::= { lmpControlChannelEntry 9 } 987 lmpCcHelloInterval OBJECT-TYPE 988 SYNTAX LmpInterval 989 MAX-ACCESS read-create 990 STATUS current 991 DESCRIPTION 992 "This object specifies the value of the HelloInterval 993 parameter. Once the control channel is active, it represents 994 the negotiated value of the HelloInterval." 995 ::= { lmpControlChannelEntry 10 } 997 lmpCcHelloIntervalMin OBJECT-TYPE 998 SYNTAX LmpInterval 999 MAX-ACCESS read-create 1000 STATUS current 1001 DESCRIPTION 1002 "This object specifies the minimum value for the 1003 HelloInterval parameter." 1004 ::= { lmpControlChannelEntry 11 } 1006 lmpCcHelloIntervalMax OBJECT-TYPE 1007 SYNTAX LmpInterval 1008 MAX-ACCESS read-create 1009 STATUS current 1010 DESCRIPTION 1011 "This object specifies the maximum value for the 1012 HelloInterval parameter." 1013 ::= { lmpControlChannelEntry 12 } 1015 lmpCcHelloDeadInterval OBJECT-TYPE 1016 SYNTAX LmpInterval 1017 MAX-ACCESS read-create 1018 STATUS current 1019 DESCRIPTION 1020 "This object specifies the value of the HelloDeadInterval 1021 parameter. Once the control channel is active, it represents 1022 the negotiated value of the HelloDeadInterval." 1023 ::= { lmpControlChannelEntry 13 } 1025 lmpCcHelloDeadIntervalMin OBJECT-TYPE 1026 SYNTAX LmpInterval 1027 MAX-ACCESS read-create 1028 STATUS current 1029 DESCRIPTION 1030 "This object specifies the minimum value for the 1031 HelloDeadInterval parameter." 1032 ::= { lmpControlChannelEntry 14 } 1034 lmpCcHelloDeadIntervalMax OBJECT-TYPE 1035 SYNTAX LmpInterval 1036 MAX-ACCESS read-create 1037 STATUS current 1038 DESCRIPTION 1039 "This object specifies the maximum value for the 1040 HelloDeadInterval parameter." 1041 ::= { lmpControlChannelEntry 15 } 1043 lmpCcLastChange OBJECT-TYPE 1044 SYNTAX TimeTicks 1045 MAX-ACCESS read-only 1046 STATUS current 1047 DESCRIPTION 1048 "The value of sysUpTime at the time the control channel entered 1049 its current operational state. If the current state was 1050 entered prior to the last re-initialization of the local 1051 network management subsystem, then this object contains a 1052 zero value." 1053 ::= { lmpControlChannelEntry 16 } 1055 lmpCcAdminStatus OBJECT-TYPE 1056 SYNTAX INTEGER { up(1), down(2) } 1057 MAX-ACCESS read-create 1058 STATUS current 1059 DESCRIPTION 1060 "The desired operational status of this control channel." 1061 ::= { lmpControlChannelEntry 17 } 1063 lmpCcOperStatus OBJECT-TYPE 1064 SYNTAX INTEGER { 1065 up(1), 1066 down(2), 1067 configSnd(3), 1068 configRcv(4), 1069 active(5), 1070 goingDown(6) 1071 } 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1075 "The actual operational status of this control channel 1076 interface." 1077 ::= { lmpControlChannelEntry 18 } 1079 lmpCcRowStatus OBJECT-TYPE 1080 SYNTAX RowStatus 1081 MAX-ACCESS read-create 1082 STATUS current 1083 DESCRIPTION 1084 "This variable is used to create, modify, and/or 1085 delete a row in this table." 1086 ::= { lmpControlChannelEntry 19 } 1088 lmpCcStorageType OBJECT-TYPE 1089 SYNTAX StorageType 1090 MAX-ACCESS read-create 1091 STATUS current 1092 DESCRIPTION 1093 "The storage type for this entry." 1094 ::= { lmpControlChannelEntry 20 } 1096 -- End of lmpControlChannelTable 1098 -- LMP Control Channel Performance Table 1100 lmpControlChannelPerfTable OBJECT-TYPE 1101 SYNTAX SEQUENCE OF LmpControlChannelPerfEntry 1102 MAX-ACCESS not-accessible 1103 STATUS current 1104 DESCRIPTION 1105 "This table specifies LMP control channel performance counters." 1106 ::= { lmpObjects 10 } 1108 lmpControlChannelPerfEntry OBJECT-TYPE 1109 SYNTAX LmpControlChannelPerfEntry 1110 MAX-ACCESS not-accessible 1111 STATUS current 1112 DESCRIPTION 1113 "An entry in this table is created by a LMP-enabled device for 1114 every control channel." 1115 AUGMENTS { lmpControlChannelEntry } 1116 ::= { lmpControlChannelPerfTable 1 } 1118 LmpControlChannelPerfEntry ::= SEQUENCE { 1119 lmpCcHCInOctets Counter64, 1120 lmpCcInDiscards Counter32, 1121 lmpCcInErrors Counter32, 1122 lmpCcHCOutOctets Counter64, 1123 lmpCcOutDiscards Counter32, 1124 lmpCcOutErrors Counter32, 1125 lmpCcHCHelloReceived Counter64, 1126 lmpCcHCHelloSent Counter64, 1127 lmpCcConfigReceived Counter32, 1128 lmpCcConfigSent Counter32, 1129 lmpCcConfigRetransmit Counter32, 1130 lmpCcLinkSummaryReceived Counter32, 1131 lmpCcLinkSummarySent Counter32, 1132 lmpCcLinkSummaryRetransmit Counter32, 1133 lmpCcChannelStatusReceived Counter32, 1134 lmpCcChannelStatusSent Counter32, 1135 lmpCcChannelStatusRequestReceived Counter32, 1136 lmpCcChannelStatusRequestSent Counter32, 1137 lmpCcChannelStatusResponseReceived Counter32, 1138 lmpCcChannelStatusResponseSent Counter32, 1139 lmpCcCounterDiscontinuityTime TimeStamp 1140 } 1142 lmpCcHCInOctets OBJECT-TYPE 1143 SYNTAX Counter64 1144 MAX-ACCESS read-only 1145 STATUS current 1146 DESCRIPTION 1147 "The total number of LMP message octets received on the 1148 control channel." 1149 ::= { lmpControlChannelPerfEntry 1 } 1151 lmpCcInDiscards OBJECT-TYPE 1152 SYNTAX Counter32 1153 MAX-ACCESS read-only 1154 STATUS current 1155 DESCRIPTION 1156 "The number of inbound packets which were chosen to be 1157 discarded even though no errors had been detected. One 1158 possible reason for discarding such a packet could be to 1159 free up buffer space." 1160 ::= { lmpControlChannelPerfEntry 2 } 1162 lmpCcInErrors OBJECT-TYPE 1163 SYNTAX Counter32 1164 MAX-ACCESS read-only 1165 STATUS current 1166 DESCRIPTION 1167 "The number of inbound packets that contained errors 1168 preventing them from being processed by LMP." 1169 ::= { lmpControlChannelPerfEntry 3 } 1171 lmpCcHCOutOctets OBJECT-TYPE 1172 SYNTAX Counter64 1173 MAX-ACCESS read-only 1174 STATUS current 1175 DESCRIPTION 1176 "The total number of LMP message octets transmitted out of 1177 the control channel." 1178 ::= { lmpControlChannelPerfEntry 4 } 1180 lmpCcOutDiscards OBJECT-TYPE 1181 SYNTAX Counter32 1182 MAX-ACCESS read-only 1183 STATUS current 1184 DESCRIPTION 1185 "The number of outbound packets which were chosen to be 1186 discarded even though no errors had been detected to prevent 1187 their being transmitted. One possible reason for discarding 1188 such a packet could be to free up buffer space." 1189 ::= { lmpControlChannelPerfEntry 5 } 1191 lmpCcOutErrors OBJECT-TYPE 1192 SYNTAX Counter32 1193 MAX-ACCESS read-only 1194 STATUS current 1195 DESCRIPTION 1196 "The number of outbound packets that could not be 1197 transmitted because of errors." 1198 ::= { lmpControlChannelPerfEntry 6 } 1200 lmpCcHCHelloReceived OBJECT-TYPE 1201 SYNTAX Counter64 1202 MAX-ACCESS read-only 1203 STATUS current 1204 DESCRIPTION 1205 "This object counts the number of Hello messages that have 1206 been received on this control channel." 1207 ::= { lmpControlChannelPerfEntry 7 } 1209 lmpCcHCHelloSent OBJECT-TYPE 1210 SYNTAX Counter64 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "This object counts the number of Hello messages that have 1215 been sent on this control channel." 1216 ::= { lmpControlChannelPerfEntry 8 } 1218 lmpCcConfigReceived OBJECT-TYPE 1219 SYNTAX Counter32 1220 MAX-ACCESS read-only 1221 STATUS current 1222 DESCRIPTION 1223 "This object counts the number of Config messages that have 1224 been received on this control channel." 1226 ::= { lmpControlChannelPerfEntry 9 } 1228 lmpCcConfigSent OBJECT-TYPE 1229 SYNTAX Counter32 1230 MAX-ACCESS read-only 1231 STATUS current 1232 DESCRIPTION 1233 "This object counts the number of Config messages that have 1234 been sent on this control channel." 1235 ::= { lmpControlChannelPerfEntry 10 } 1237 lmpCcConfigRetransmit OBJECT-TYPE 1238 SYNTAX Counter32 1239 MAX-ACCESS read-only 1240 STATUS current 1241 DESCRIPTION 1242 "This object counts the number of Config messages that 1243 have been retransmitted over this interface." 1244 ::= { lmpControlChannelPerfEntry 11 } 1246 lmpCcLinkSummaryReceived OBJECT-TYPE 1247 SYNTAX Counter32 1248 MAX-ACCESS read-only 1249 STATUS current 1250 DESCRIPTION 1251 "This object counts the number of LinkSummary messages that have 1252 been received on this control channel." 1253 ::= { lmpControlChannelPerfEntry 12 } 1255 lmpCcLinkSummarySent OBJECT-TYPE 1256 SYNTAX Counter32 1257 MAX-ACCESS read-only 1258 STATUS current 1259 DESCRIPTION 1260 "This object counts the number of LinkSummary messages that have 1261 been sent on this control channel." 1262 ::= { lmpControlChannelPerfEntry 13 } 1264 lmpCcLinkSummaryRetransmit OBJECT-TYPE 1265 SYNTAX Counter32 1266 MAX-ACCESS read-only 1267 STATUS current 1268 DESCRIPTION 1269 "This object counts the number of LinkSummary messages that 1270 have been retransmitted over this interface." 1271 ::= { lmpControlChannelPerfEntry 14 } 1273 lmpCcChannelStatusReceived OBJECT-TYPE 1274 SYNTAX Counter32 1275 MAX-ACCESS read-only 1276 STATUS current 1277 DESCRIPTION 1278 "This object counts the number of ChannelStatus messages that have 1279 been received on this control channel." 1280 ::= { lmpControlChannelPerfEntry 15 } 1282 lmpCcChannelStatusSent OBJECT-TYPE 1283 SYNTAX Counter32 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "This object counts the number of ChannelStatus messages that have 1288 been sent on this control channel." 1289 ::= { lmpControlChannelPerfEntry 16 } 1291 lmpCcChannelStatusRequestReceived OBJECT-TYPE 1292 SYNTAX Counter32 1293 MAX-ACCESS read-only 1294 STATUS current 1295 DESCRIPTION 1296 "This object counts the number of ChannelStatusRequest messages that 1297 have been received on this control channel." 1298 ::= { lmpControlChannelPerfEntry 17 } 1300 lmpCcChannelStatusRequestSent OBJECT-TYPE 1301 SYNTAX Counter32 1302 MAX-ACCESS read-only 1303 STATUS current 1304 DESCRIPTION 1305 "This object counts the number of ChannelStatusRequest messages that 1306 have been sent on this control channel." 1307 ::= { lmpControlChannelPerfEntry 18 } 1309 lmpCcChannelStatusResponseReceived OBJECT-TYPE 1310 SYNTAX Counter32 1311 MAX-ACCESS read-only 1312 STATUS current 1313 DESCRIPTION 1314 "This object counts the number of ChannelStatusResponse messages that 1315 have been received on this control channel." 1316 ::= { lmpControlChannelPerfEntry 19 } 1318 lmpCcChannelStatusResponseSent OBJECT-TYPE 1319 SYNTAX Counter32 1320 MAX-ACCESS read-only 1321 STATUS current 1322 DESCRIPTION 1323 "This object counts the number of ChannelStatusResponse messages that 1324 have been sent on this control channel." 1325 ::= { lmpControlChannelPerfEntry 20 } 1327 lmpCcCounterDiscontinuityTime OBJECT-TYPE 1328 SYNTAX TimeStamp 1329 MAX-ACCESS read-only 1330 STATUS current 1331 DESCRIPTION 1332 "The value of sysUpTime on the most recent occasion at which 1333 any one or more of this control channel's counters suffered a 1334 discontinuity. The relevant counters are the specific 1335 instances associated with this control channel of any Counter32 or 1336 Counter64 object contained in the lmpControlChannelPerfTable. If 1337 no such discontinuities have occurred since the last re- 1338 initialization of the local management subsystem, then this 1339 object contains a zero value." 1340 ::= { lmpControlChannelPerfEntry 21 } 1342 -- End of lmpControlChannelPerfTable 1344 -- LMP TE Link Table 1346 lmpTeLinkTable OBJECT-TYPE 1347 SYNTAX SEQUENCE OF LmpTeLinkEntry 1348 MAX-ACCESS not-accessible 1349 STATUS current 1350 DESCRIPTION 1351 "This table contains a collection of TE link." 1352 ::= { lmpObjects 11 } 1354 lmpTeLinkEntry OBJECT-TYPE 1355 SYNTAX LmpTeLinkEntry 1356 MAX-ACCESS not-accessible 1357 STATUS current 1358 DESCRIPTION 1359 "An entry in this table exists for each ifEntry with an 1360 ifType of teLink(TBD), i.e. for every TE link. An ifEntry 1361 with an ifIndex must exist before the corresponding 1362 teLinkEntry is created. If a TE link entry in the ifTable is 1363 destroyed, then so is the corresponding entry in the 1364 teLinkTable. The administrative status value is controlled 1365 from the ifEntry. Setting the administrative status to 1366 testing prompts LMP to start link verification on the TE link. 1367 Information about the TE link that is not LMP specific is also 1368 contained in teLinkTable [BUNDLE-MIB]." 1370 INDEX { ifIndex } 1371 ::= { lmpTeLinkTable 1 } 1373 LmpTeLinkEntry ::= SEQUENCE { 1374 lmpTeLinkNbrNodeId NodeID, 1375 lmpTeLinkVerification TruthValue, 1376 lmpTeLinkFaultIsolation TruthValue, 1377 lmpTeLinkDwdm TruthValue, 1378 lmpTeLinkOperStatus INTEGER, 1379 lmpTeLinkRowStatus RowStatus, 1380 lmpTeLinkStorageType StorageType 1381 } 1383 lmpTeLinkNbrNodeId OBJECT-TYPE 1384 SYNTAX NodeID 1385 MAX-ACCESS read-create 1386 STATUS current 1387 DESCRIPTION 1388 "This is the Node ID of the TE link remote node." 1389 ::= { lmpTeLinkEntry 1 } 1391 lmpTeLinkVerification OBJECT-TYPE 1392 SYNTAX TruthValue 1393 MAX-ACCESS read-create 1394 STATUS current 1395 DESCRIPTION 1396 "This object indicates if the extended LMP link verification 1397 procedure is enabled for this TE link." 1398 REFERENCE 1399 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 1400 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1401 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1402 B. Rajagopalan, September 2001." 1403 ::= { lmpTeLinkEntry 2 } 1405 lmpTeLinkFaultIsolation OBJECT-TYPE 1406 SYNTAX TruthValue 1407 MAX-ACCESS read-create 1408 STATUS current 1409 DESCRIPTION 1410 "This object indicates if the extended LMP fault isolation 1411 procedure is enabled on this TE link." 1412 REFERENCE 1413 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 1414 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1415 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1416 B. Rajagopalan, September 2001." 1417 ::= { lmpTeLinkEntry 3 } 1419 lmpTeLinkDwdm OBJECT-TYPE 1420 SYNTAX TruthValue 1421 MAX-ACCESS read-create 1422 STATUS current 1423 DESCRIPTION 1424 "This object indicates if the extended LMP DWDM procedure 1425 is enabled on this TE link." 1426 REFERENCE 1427 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 1428 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1429 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1430 B. Rajagopalan, September 2001." 1431 ::= { lmpTeLinkEntry 4 } 1433 lmpTeLinkOperStatus OBJECT-TYPE 1434 SYNTAX INTEGER { up(1), down(2), testing(3), degraded(4) } 1435 MAX-ACCESS read-only 1436 STATUS current 1437 DESCRIPTION 1438 "The actual operational status of this TE link. The status 1439 is set to testing when the TE link is performing link 1440 verification. A degraded status indicates that the TE link 1441 cannot provide the provisioned protection level, but yet, 1442 there is no disruption of service. For instance, if the 1443 protection type is 1+1 and one link is down, the TE link 1444 still carries the requested amount of data traffic, but 1445 this traffic is not protected anymore." 1446 ::= { lmpTeLinkEntry 5 } 1448 lmpTeLinkRowStatus OBJECT-TYPE 1449 SYNTAX RowStatus 1450 MAX-ACCESS read-create 1451 STATUS current 1452 DESCRIPTION 1453 "This variable is used to create, modify, and/or 1454 delete a row in this table." 1455 ::= { lmpTeLinkEntry 6 } 1457 lmpTeLinkStorageType OBJECT-TYPE 1458 SYNTAX StorageType 1459 MAX-ACCESS read-create 1460 STATUS current 1461 DESCRIPTION 1462 "This variable indicates the storage type for this 1463 object." 1464 ::= { lmpTeLinkEntry 7 } 1466 -- End of lmpTeLinkTable 1467 lmpLinkVerificationInterval OBJECT-TYPE 1468 SYNTAX Unsigned32 1469 MAX-ACCESS read-write 1470 STATUS current 1471 DESCRIPTION 1472 "This object indicates how often the link verification procedure 1473 is executed. The interval is in milliseconds." 1474 ::= { lmpObjects 12 } 1476 -- LMP Link Verification Table 1478 lmpLinkVerificationTable OBJECT-TYPE 1479 SYNTAX SEQUENCE OF LmpLinkVerificationEntry 1480 MAX-ACCESS not-accessible 1481 STATUS current 1482 DESCRIPTION 1483 "This table specifies TE link information 1484 associated with the LMP verification procedure." 1485 ::= { lmpObjects 13 } 1487 lmpLinkVerificationEntry OBJECT-TYPE 1488 SYNTAX LmpLinkVerificationEntry 1489 MAX-ACCESS not-accessible 1490 STATUS current 1491 DESCRIPTION 1492 "An entry in this table is created by a LMP-enabled device for 1493 every TE link that supports the LMP verification 1494 procedure." 1495 AUGMENTS { lmpTeLinkEntry } 1496 ::= { lmpLinkVerificationTable 1 } 1498 LmpLinkVerificationEntry ::= SEQUENCE { 1499 lmpVerifyInterval LmpInterval, 1500 lmpVerifyDeadInterval LmpInterval, 1501 lmpVerifyTransportMechanism BITS, 1502 lmpVerifyAllLinks INTEGER, 1503 lmpTeLinkBitRate Unsigned32, 1504 lmpTeLinkWavelength Unsigned32 1505 } 1507 lmpVerifyInterval OBJECT-TYPE 1508 SYNTAX LmpInterval 1509 MAX-ACCESS read-create 1510 STATUS current 1511 DESCRIPTION 1512 "This object specifies the VerifyInterval parameter used 1513 in the LMP link verification process. It indicates the interval 1514 at which the Test messages are sent." 1515 REFERENCE 1516 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 1517 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1518 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1519 B. Rajagopalan, September 2001." 1520 ::= { lmpLinkVerificationEntry 1 } 1522 lmpVerifyDeadInterval OBJECT-TYPE 1523 SYNTAX LmpInterval 1524 MAX-ACCESS read-create 1525 STATUS current 1526 DESCRIPTION 1527 "This object specifies the VerifyDeadInterval parameter used 1528 in the verification of the physical connectivity of data-bearing 1529 links. It specifies the observation period used to detect a Test 1530 message at the remote node." 1531 REFERENCE 1532 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 1533 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1534 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1535 B. Rajagopalan, September 2001." 1536 ::= { lmpLinkVerificationEntry 2 } 1538 lmpVerifyTransportMechanism OBJECT-TYPE 1539 SYNTAX BITS { 1540 -- SONET/SDH encoding type: 1541 j0OverheadBytes(0), 1542 dccSectionOverheadBytes(1), 1543 dccLineOverheadBytes(2), 1544 pos(3) 1545 -- GigE encoding type: TBD 1546 -- 10GigE encoding type: TBD 1547 } 1548 MAX-ACCESS read-create 1549 STATUS current 1550 DESCRIPTION 1551 "This defines the transport mechanism for the Test messages. The 1552 scope of this bit mask is restricted to each link encoding 1553 type. The local node will set the bits corresponding to the 1554 various mechanisms it can support for transmitting LMP Test 1555 messages. The receiver chooses the appropriate mechanism in the 1556 BeginVerifyAck message." 1557 REFERENCE 1558 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 1559 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1560 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1561 B. Rajagopalan, September 2001." 1563 ::= { lmpLinkVerificationEntry 3 } 1565 lmpVerifyAllLinks OBJECT-TYPE 1566 SYNTAX INTEGER { verifyAllLinks(1), verifyNewLinks(2) } 1567 MAX-ACCESS read-create 1568 STATUS current 1569 DESCRIPTION 1570 "This object indicates whether the verification process checks 1571 all entities or only the new entities that have been added to 1572 this TE link." 1573 ::= { lmpLinkVerificationEntry 4 } 1575 lmpTeLinkBitRate OBJECT-TYPE 1576 SYNTAX Unsigned32 1577 MAX-ACCESS read-create 1578 STATUS current 1579 DESCRIPTION 1580 "This is the bit rate at which the Test messages will be 1581 transmitted and is expressed in bytes per second." 1582 REFERENCE 1583 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 1584 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1585 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1586 B. Rajagopalan, September 2001." 1587 ::= { lmpLinkVerificationEntry 5 } 1589 lmpTeLinkWavelength OBJECT-TYPE 1590 SYNTAX Unsigned32 1591 MAX-ACCESS read-create 1592 STATUS current 1593 DESCRIPTION 1594 "This value corresponds to the wavelength at 1595 which the Test messages will be transmitted over and is 1596 measured in nanometers (nm). If each data-bearing link 1597 corresponds to a separate wavelength, than this value should be 1598 set to 0." 1599 REFERENCE 1600 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 1601 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1602 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1603 B. Rajagopalan, September 2001." 1604 ::= { lmpLinkVerificationEntry 6 } 1606 -- End of lmpLinkVerificationTable 1608 -- LMP Data Bearing Link Table 1609 lmpDataBearingLinkTable OBJECT-TYPE 1610 SYNTAX SEQUENCE OF LmpDataBearingLinkEntry 1611 MAX-ACCESS not-accessible 1612 STATUS current 1613 DESCRIPTION 1614 "This table specifies the data-bearing links managed by the 1615 LMP." 1616 ::= { lmpObjects 14 } 1618 lmpDataBearingLinkEntry OBJECT-TYPE 1619 SYNTAX LmpDataBearingLinkEntry 1620 MAX-ACCESS not-accessible 1621 STATUS current 1622 DESCRIPTION 1623 "An entry in this table exists for each ifEntry that represents 1624 a data-bearing link. An ifEntry with an ifIndex must exist 1625 before the corresponding lmpDataBearingLinkEntry is created. 1626 If an entry representing the data-bearing link is destroyed in 1627 the ifTable, then so is the corresponding entry in the 1628 lmpDataBearingLinkTable. The administrative status value is 1629 controlled from the ifEntry. The index to this table also 1630 used to get information in the dataBearingChannelTable 1631 [BUNDLE-MIB]." 1632 INDEX { ifIndex } 1633 ::= { lmpDataBearingLinkTable 1 } 1635 LmpDataBearingLinkEntry ::= SEQUENCE { 1636 lmpDataBearingLinkType INTEGER, 1637 lmpDataBearingLinkRemoteIfId InterfaceIndexOrZero, 1638 lmpDataBearingLinkEncodingType INTEGER, 1639 lmpDataBearingLinkOperStatus INTEGER, 1640 lmpDataBearingLinkRowStatus RowStatus, 1641 lmpDataBearingLinkStorageType StorageType 1642 } 1644 lmpDataBearingLinkType OBJECT-TYPE 1645 SYNTAX INTEGER { 1646 port(1), 1647 componentLink(2) 1648 } 1649 MAX-ACCESS read-only 1650 STATUS current 1651 DESCRIPTION 1652 "This attribute specifies whether this data-bearing link is 1653 a port or a component link. Component link are multiplex 1654 capable whereas, ports are not multiplex capable." 1655 REFERENCE 1656 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 1657 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1658 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1659 B. Rajagopalan, September 2001." 1660 ::= { lmpDataBearingLinkEntry 1 } 1662 lmpDataBearingLinkRemoteIfId OBJECT-TYPE 1663 SYNTAX InterfaceIndexOrZero 1664 MAX-ACCESS read-create 1665 STATUS current 1666 DESCRIPTION 1667 "Interface identifier of the remote end point. This 1668 information is either configured manually or is 1669 communicated by the remote node during the link verification 1670 procedure." 1671 ::= { lmpDataBearingLinkEntry 2 } 1673 lmpDataBearingLinkEncodingType OBJECT-TYPE 1674 SYNTAX INTEGER { 1675 packet(1), 1676 ethernetV2(2), 1677 ansiPdh(3), 1678 etsiPdh(4), 1679 sdhItu1996(5), 1680 sonetAnsi1995(6), 1681 digitalWrapper(7), 1682 lambda(8), 1683 fiber(9), 1684 ethernet8023(10), 1685 sdhItu2000(11), 1686 sonetAnsi2000(12) 1687 } 1688 MAX-ACCESS read-create 1689 STATUS current 1690 DESCRIPTION 1691 "The encoding type of the data-bearing link." 1692 REFERENCE 1693 "draft-ietf-mpls-generalized-signaling-05.txt - Generalized 1694 MPLS Signaling Functional Description, P. Ashwood-Smith, 1695 A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan, 1696 E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha, 1697 V. Sharma, G. Swallow, Z. Tang, July 2001." 1698 ::= { lmpDataBearingLinkEntry 3 } 1700 lmpDataBearingLinkOperStatus OBJECT-TYPE 1701 SYNTAX INTEGER { 1702 upAlloc(1), 1703 upFree(2), 1704 down(3), 1705 testing(4), 1706 psvTst(5), 1707 degraded(6) } 1708 MAX-ACCESS read-only 1709 STATUS current 1710 DESCRIPTION 1711 "The actual operational status of this data-bearing link. 1712 A data-bearing link is in the degraded state if the 1713 control channel and associated backup control channel(s) are 1714 down but the data-bearing link is still operational." 1715 REFERENCE 1716 "draft-ietf-ccamp-lmp-01.txt - Link Management Protocol (LMP), 1717 J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, 1718 L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin, 1719 B. Rajagopalan, September 2001." 1720 ::= { lmpDataBearingLinkEntry 4 } 1722 lmpDataBearingLinkRowStatus OBJECT-TYPE 1723 SYNTAX RowStatus 1724 MAX-ACCESS read-create 1725 STATUS current 1726 DESCRIPTION 1727 "This variable is used to create, modify, and/or 1728 delete a row in this table." 1729 ::= { lmpDataBearingLinkEntry 5 } 1731 lmpDataBearingLinkStorageType OBJECT-TYPE 1732 SYNTAX StorageType 1733 MAX-ACCESS read-create 1734 STATUS current 1735 DESCRIPTION 1736 "This variable indicates the storage type for this 1737 object." 1738 ::= { lmpDataBearingLinkEntry 6 } 1740 -- End of lmpDataBearingLinkTable 1742 -- LMP Data Bearing Link Performance Table 1744 lmpDataBearingLinkPerfTable OBJECT-TYPE 1745 SYNTAX SEQUENCE OF LmpDataBearingLinkPerfEntry 1746 MAX-ACCESS not-accessible 1747 STATUS current 1748 DESCRIPTION 1749 "This table specifies the data-bearing links LMP performance 1750 counters." 1751 ::= { lmpObjects 15 } 1753 lmpDataBearingLinkPerfEntry OBJECT-TYPE 1754 SYNTAX LmpDataBearingLinkPerfEntry 1755 MAX-ACCESS not-accessible 1756 STATUS current 1757 DESCRIPTION 1758 "An entry in this table contains information about 1759 the LMP performance counters for the data-bearing links." 1760 AUGMENTS { lmpDataBearingLinkEntry } 1761 ::= { lmpDataBearingLinkPerfTable 1 } 1763 LmpDataBearingLinkPerfEntry ::= SEQUENCE { 1764 lmpDataBearingLinkTestReceived Counter32, 1765 lmpDataBearingLinkTestSent Counter32, 1766 lmpDataBearingLinkCounterDiscontinuityTime TimeStamp 1767 } 1769 lmpDataBearingLinkTestReceived OBJECT-TYPE 1770 SYNTAX Counter32 1771 MAX-ACCESS read-only 1772 STATUS current 1773 DESCRIPTION 1774 "This object counts the number of Test messages that have 1775 been received on this control channel." 1776 ::= { lmpDataBearingLinkPerfEntry 1 } 1778 lmpDataBearingLinkTestSent OBJECT-TYPE 1779 SYNTAX Counter32 1780 MAX-ACCESS read-only 1781 STATUS current 1782 DESCRIPTION 1783 "This object counts the number of Test messages that have 1784 been sent on this control channel." 1785 ::= { lmpDataBearingLinkPerfEntry 2 } 1787 lmpDataBearingLinkCounterDiscontinuityTime OBJECT-TYPE 1788 SYNTAX TimeStamp 1789 MAX-ACCESS read-only 1790 STATUS current 1791 DESCRIPTION 1792 "The value of sysUpTime on the most recent occasion at which 1793 any one or more of this data-bearing link's counters suffered a 1794 discontinuity. The relevant counters are the specific 1795 instances associated with this data-bearing link of any Counter32 or 1796 Counter64 object contained in the lmpDataBearingLinkPerfTable. If 1797 no such discontinuities have occurred since the last re- 1798 initialization of the local management subsystem, then this 1799 object contains a zero value." 1800 ::= { lmpDataBearingLinkPerfEntry 3 } 1802 -- End of lmpDataBearingLinkPerfTable 1804 -- Notification Configuration 1806 lmpLinkPropertyMismatchTrapEnable OBJECT-TYPE 1807 SYNTAX TruthValue 1808 MAX-ACCESS read-write 1809 STATUS current 1810 DESCRIPTION 1811 "If this object is true, then it enables the 1812 generation of lmpTeLinkPropertyMismatch 1813 and lmpDataBearingLinkPropertyMismatch traps, 1814 otherwise these traps are not emitted." 1815 DEFVAL { false } 1816 ::= { lmpObjects 16 } 1818 lmpUnprotectedTrapEnable OBJECT-TYPE 1819 SYNTAX TruthValue 1820 MAX-ACCESS read-write 1821 STATUS current 1822 DESCRIPTION 1823 "If this object is true, then it enables the 1824 generation of lmpUnprotected trap, 1825 otherwise these traps are not emitted." 1826 DEFVAL { false } 1827 ::= { lmpObjects 17 } 1829 lmpCcUpDownTrapEnable OBJECT-TYPE 1830 SYNTAX TruthValue 1831 MAX-ACCESS read-write 1832 STATUS current 1833 DESCRIPTION 1834 "If this object is true, then it enables the generation of 1835 lmpControlChannelUp and lmpControlChannelDown traps, 1836 otherwise these traps are not emitted." 1837 DEFVAL { false } 1838 ::= { lmpObjects 18 } 1840 lmpTeLinkTrapEnable OBJECT-TYPE 1841 SYNTAX TruthValue 1842 MAX-ACCESS read-write 1843 STATUS current 1844 DESCRIPTION 1845 "If this object is true, then it enables the 1846 generation of lmpTeLinkDegraded trap, 1847 otherwise these traps are not emitted." 1848 DEFVAL { false } 1849 ::= { lmpObjects 19 } 1851 -- Notifications 1853 -- Link Property Mismatch Traps 1855 lmpTeLinkPropertyMismatch NOTIFICATION-TYPE 1856 OBJECTS { ifIndex, 1857 teLinkRemoteIpAddr, 1858 teLinkIncomingIfId } 1859 STATUS current 1860 DESCRIPTION 1861 "This notification is generated when a TE link property 1862 mismatch is detected on the node. ifIndex is the 1863 interface index of the misconfigured TE link. The received remote 1864 TE link id is represented by either teLinkRemoteIpAddr 1865 or teLinkIncomingIfId depending on whether the TE link is 1866 numbered or unnumbered." 1867 ::= { lmpNotifications 1 } 1869 lmpDataBearingLinkPropertyMismatch NOTIFICATION-TYPE 1870 OBJECTS { ifStackHigherLayer, 1871 ifIndex, 1872 lmpDataBearingLinkRemoteIfId } 1873 STATUS current 1874 DESCRIPTION 1875 "This notification is generated when a data-bearing link 1876 property mismatch is detected on the node. ifStackHigherLayer 1877 is the interface index of the TE link. The second ifIndex is 1878 the interface index of the data-bearing link. The remote entity 1879 interface id is the remote entity interface id received in the 1880 LinkSummary message." 1881 ::= { lmpNotifications 2 } 1883 -- Neighbor Trap 1885 lmpUnprotected NOTIFICATION-TYPE 1886 OBJECTS { lmpCcNbrNodeId } 1887 STATUS current 1888 DESCRIPTION 1889 "This notification is generated when all but one control channel 1890 is operational. If the only operational control channel fails, 1891 then there will be no more control channels between the pair of 1892 nodes and all the data-bearing links between the pair of nodes 1893 will go to degraded state." 1894 ::= { lmpNotifications 3 } 1896 -- Control Channel Trap 1898 lmpControlChannelUp NOTIFICATION-TYPE 1899 OBJECTS { ifIndex } 1900 STATUS current 1901 DESCRIPTION 1902 "This notification is generated when a control 1903 channel transitions to the up operational state." 1904 ::= { lmpNotifications 4 } 1906 lmpControlChannelDown NOTIFICATION-TYPE 1907 OBJECTS { ifIndex } 1908 STATUS current 1909 DESCRIPTION 1910 "This notification is generated when a control 1911 channel transitions to the down operational state." 1912 ::= { lmpNotifications 5 } 1914 -- TE Link Trap 1916 lmpTeLinkDegraded NOTIFICATION-TYPE 1917 OBJECTS { ifIndex } 1918 STATUS current 1919 DESCRIPTION 1920 "This notification is generated when a lmpTeLinkOperStatus 1921 object for a TE link enters the degraded state." 1922 ::= { lmpNotifications 6 } 1924 -- End of notifications 1926 -- Module compliance 1928 lmpGroups 1929 OBJECT IDENTIFIER ::= { lmpConformance 1 } 1931 lmpCompliances 1932 OBJECT IDENTIFIER ::= { lmpConformance 2 } 1934 lmpModuleCompliance MODULE-COMPLIANCE 1935 STATUS current 1936 DESCRIPTION 1937 "Compliance statement for agents that support the 1938 LMP MIB." 1939 MODULE -- this module 1941 -- The mandatory groups have to be implemented 1942 -- by all LMP-enabled devices. However, they may all be supported 1943 -- as read-only objects in the case where manual 1944 -- configuration is unsupported. 1946 MANDATORY-GROUPS { lmpNodeGroup, 1947 lmpControlChannelGroup, 1948 lmpLinkPropertyCorrelationGroup, 1949 lmpPerfGroup, 1950 lmpTeLinkGroup, 1951 lmpDataBearingLinkGroup } 1953 GROUP lmpControlChannelIsNotInterfaceGroup 1954 DESCRIPTION 1955 "This group is mandatory for devices which support 1956 control channels that are not interfaces, in addition to 1957 lmpControlChannelGroup. The following constraints apply: 1958 lmpCcIsIf must at least be read-only returning false(1)." 1960 GROUP lmpControlChannelIsInterfaceGroup 1961 DESCRIPTION 1962 "This group is mandatory for devices which support 1963 control channels that are interfaces, in addition to 1964 lmpControlChannelGroup. The following constraints apply: 1965 lmpCcIsIf must at least be read-only returning true(2)." 1967 GROUP lmpLinkVerificationGroup 1968 DESCRIPTION 1969 "This group is mandatory for devices which support 1970 the link verification procedure." 1972 -- Scalars 1974 OBJECT lmpAdminStatus 1975 MIN-ACCESS read-only 1976 DESCRIPTION 1977 "Write access is not required." 1979 OBJECT lmpLinkVerificationInterval 1980 MIN-ACCESS read-only 1981 DESCRIPTION 1982 "Write access is not required." 1984 OBJECT lmpCcHelloIntervalDefault 1985 MIN-ACCESS read-only 1986 DESCRIPTION 1987 "Write access is not required." 1989 OBJECT lmpCcHelloIntervalDefaultMin 1990 MIN-ACCESS read-only 1991 DESCRIPTION 1992 "Write access is not required." 1994 OBJECT lmpCcHelloIntervalDefaultMax 1995 MIN-ACCESS read-only 1996 DESCRIPTION 1997 "Write access is not required." 1999 OBJECT lmpCcHelloDeadIntervalDefault 2000 MIN-ACCESS read-only 2001 DESCRIPTION 2002 "Write access is not required." 2004 OBJECT lmpCcHelloDeadIntervalDefaultMin 2005 MIN-ACCESS read-only 2006 DESCRIPTION 2007 "Write access is not required." 2009 OBJECT lmpCcHelloDeadIntervalDefaultMax 2010 MIN-ACCESS read-only 2011 DESCRIPTION 2012 "Write access is not required." 2014 -- lmpNbrTable 2016 OBJECT lmpNbrRetransmitInterval 2017 MIN-ACCESS read-only 2018 DESCRIPTION 2019 "Write access is not required." 2021 OBJECT lmpNbrRowStatus 2022 SYNTAX INTEGER { active(1), notInService(2), 2023 createAndGo(4), destroy(6) } 2024 MIN-ACCESS read-only 2025 DESCRIPTION 2026 "The notReady(3) and createAndWait(5) states need 2027 not be supported." 2029 OBJECT lmpNbrStorageType 2030 SYNTAX INTEGER { other(1) } 2031 MIN-ACCESS read-only 2032 DESCRIPTION 2033 "Only other(1) needs to be supported." 2035 -- lmpControlChannelTable 2037 OBJECT lmpCcUnderlyingIfIndex 2038 MIN-ACCESS read-only 2039 DESCRIPTION 2040 "Write access is not required." 2042 OBJECT lmpCcIsIf 2043 MIN-ACCESS read-only 2044 DESCRIPTION 2045 "Write access is not required." 2047 OBJECT lmpCcSetupRole 2048 MIN-ACCESS read-only 2049 DESCRIPTION 2050 "Write access is not required." 2052 OBJECT lmpCcAuthentication 2053 MIN-ACCESS read-only 2054 DESCRIPTION 2055 "Write access is not required." 2057 OBJECT lmpCcConfigRetransmitInterval 2058 MIN-ACCESS read-only 2059 DESCRIPTION 2060 "Write access is not required." 2062 OBJECT lmpCcConfigRetransmitTimeout 2063 MIN-ACCESS read-only 2064 DESCRIPTION 2065 "Write access is not required." 2067 OBJECT lmpCcHelloIntervalMin 2068 MIN-ACCESS read-only 2069 DESCRIPTION 2070 "Write access is not required." 2072 OBJECT lmpCcHelloIntervalMax 2073 MIN-ACCESS read-only 2074 DESCRIPTION 2075 "Write access is not required." 2077 OBJECT lmpCcHelloDeadIntervalMin 2078 MIN-ACCESS read-only 2079 DESCRIPTION 2080 "Write access is not required." 2082 OBJECT lmpCcHelloDeadIntervalMax 2083 MIN-ACCESS read-only 2084 DESCRIPTION 2085 "Write access is not required." 2087 OBJECT lmpCcRowStatus 2088 SYNTAX INTEGER { active(1), notInService(2), 2089 createAndGo(4), destroy(6) } 2090 MIN-ACCESS read-only 2091 DESCRIPTION 2092 "The notReady(3) and createAndWait(5) states need 2093 not be supported." 2095 OBJECT lmpCcOperStatus 2096 SYNTAX INTEGER { up(1), down(2) } 2097 MIN-ACCESS read-only 2098 DESCRIPTION 2099 "A value of active(3), configuring(4), goingDown(5) 2100 need not be supported." 2102 OBJECT lmpCcStorageType 2103 SYNTAX INTEGER { other(1) } 2104 MIN-ACCESS read-only 2105 DESCRIPTION 2106 "Only other(1) needs to be supported." 2108 -- lmpLinkVerificationTable 2110 OBJECT lmpVerifyInterval 2111 MIN-ACCESS read-only 2112 DESCRIPTION 2113 "Write access is not required." 2115 OBJECT lmpVerifyDeadInterval 2116 MIN-ACCESS read-only 2117 DESCRIPTION 2118 "Write access is not required." 2120 OBJECT lmpVerifyAllLinks 2121 MIN-ACCESS read-only 2122 DESCRIPTION 2123 "Write access is not required." 2125 -- lmpTeLinkTable 2127 OBJECT lmpTeLinkNbrNodeId 2128 MIN-ACCESS read-only 2129 DESCRIPTION 2130 "Write access is not required if the link verification 2131 procedure is enabled." 2133 OBJECT lmpTeLinkVerification 2134 MIN-ACCESS read-only 2135 DESCRIPTION 2136 "Write access is not required." 2138 OBJECT lmpTeLinkFaultIsolation 2139 MIN-ACCESS read-only 2140 DESCRIPTION 2141 "Write access is not required." 2143 OBJECT lmpTeLinkDwdm 2144 MIN-ACCESS read-only 2145 DESCRIPTION 2146 "Write access is not required." 2148 OBJECT lmpTeLinkOperStatus 2149 SYNTAX INTEGER { up(1), down(2), degraded(4) } 2150 MIN-ACCESS read-only 2151 DESCRIPTION 2152 "The testing(3) state need not be supported." 2154 OBJECT lmpTeLinkRowStatus 2155 SYNTAX INTEGER { active(1), notInService(2), 2156 createAndGo(4), destroy(6) } 2157 MIN-ACCESS read-only 2158 DESCRIPTION 2159 "The notReady(3) and createAndWait(5) states need 2160 not be supported." 2162 OBJECT lmpTeLinkStorageType 2163 SYNTAX INTEGER { other(1) } 2164 MIN-ACCESS read-only 2165 DESCRIPTION 2166 "Only other(1) needs to be supported." 2168 -- lmpTeLinkVerificationTable 2170 OBJECT lmpTeLinkBitRate 2171 MIN-ACCESS read-only 2172 DESCRIPTION 2173 "Write access is not required." 2175 OBJECT lmpTeLinkWavelength 2176 MIN-ACCESS read-only 2177 DESCRIPTION 2178 "Write access is not required." 2180 -- lmpDataBearingLinkTable 2182 OBJECT lmpDataBearingLinkRemoteIfId 2183 MIN-ACCESS read-only 2184 DESCRIPTION 2185 "Write access is not required if the link verification 2186 procedure is enabled." 2188 OBJECT lmpDataBearingLinkEncodingType 2189 MIN-ACCESS read-only 2190 DESCRIPTION 2191 "Write access is not required." 2193 OBJECT lmpDataBearingLinkOperStatus 2194 SYNTAX INTEGER { up(1), down(2), degraded(4) } 2195 MIN-ACCESS read-only 2196 DESCRIPTION 2197 "A value of testing(3) need not be supported." 2199 OBJECT lmpDataBearingLinkRowStatus 2200 SYNTAX INTEGER { active(1), notInService(2), 2201 createAndGo(4), destroy(6) } 2202 MIN-ACCESS read-only 2203 DESCRIPTION 2204 "The notReady(3) and createAndWait(5) states need 2205 not be supported." 2207 OBJECT lmpDataBearingLinkStorageType 2208 SYNTAX INTEGER { other(1) } 2209 MIN-ACCESS read-only 2210 DESCRIPTION 2211 "Only other(1) needs to be supported." 2213 ::= { lmpCompliances 1 } 2215 -- Units of conformance 2217 lmpNodeGroup OBJECT-GROUP 2218 OBJECTS { lmpAdminStatus, 2219 lmpNbrAdminStatus, 2220 lmpNbrOperStatus, 2221 lmpNbrRowStatus, 2222 lmpNbrStorageType, 2223 lmpUnprotectedTrapEnable 2224 } 2225 STATUS current 2226 DESCRIPTION 2227 "Collection of objects needed for LMP node configuration." 2228 ::= { lmpGroups 1 } 2230 lmpControlChannelGroup OBJECT-GROUP 2231 OBJECTS { 2232 lmpNbrNodeId, 2233 lmpNbrRetransmitInterval, 2234 lmpNbrAdminStatus, 2235 lmpNbrOperStatus, 2236 lmpNbrRowStatus, 2237 lmpNbrStorageType, 2238 lmpCcHelloIntervalDefault, 2239 lmpCcHelloIntervalDefaultMin, 2240 lmpCcHelloIntervalDefaultMax, 2241 lmpCcHelloDeadIntervalDefault, 2242 lmpCcHelloDeadIntervalDefaultMin, 2243 lmpCcHelloDeadIntervalDefaultMax, 2244 lmpCcNbrNodeId, 2245 lmpCcId, 2246 lmpRemoteCcId, 2247 lmpCcSetupRole, 2248 lmpCcAuthentication, 2249 lmpCcConfigRetransmitInterval, 2250 lmpCcConfigRetransmitTimeout, 2251 lmpCcHelloInterval, 2252 lmpCcHelloIntervalMin, 2253 lmpCcHelloIntervalMax, 2254 lmpCcHelloDeadInterval, 2255 lmpCcHelloDeadIntervalMin, 2256 lmpCcHelloDeadIntervalMax, 2257 lmpCcOperStatus, 2258 lmpCcRowStatus, 2259 lmpCcStorageType, 2260 lmpCcUpDownTrapEnable 2261 } 2262 STATUS current 2263 DESCRIPTION 2264 "Collection of objects needed for LMP interface 2265 configuration." 2266 ::= { lmpGroups 2 } 2268 lmpControlChannelIsInterfaceGroup OBJECT-GROUP 2269 OBJECTS { lmpCcIsIf } 2270 STATUS current 2271 DESCRIPTION 2272 "Objects needed to implement control channels that are 2273 interfaces." 2274 ::= { lmpGroups 3 } 2276 lmpControlChannelIsNotInterfaceGroup OBJECT-GROUP 2277 OBJECTS { 2278 lmpCcUnderlyingIfIndex, 2279 lmpCcIsIf, 2280 lmpCcLastChange, 2281 lmpCcAdminStatus 2282 } 2283 STATUS current 2284 DESCRIPTION 2285 "Objects needed to implement control channels that are not 2286 interfaces." 2287 ::= { lmpGroups 4 } 2289 lmpLinkPropertyCorrelationGroup OBJECT-GROUP 2290 OBJECTS { lmpLinkPropertyMismatchTrapEnable } 2291 STATUS current 2292 DESCRIPTION 2293 "Collection of objects needed to implement the link 2294 property correlation procedure." 2295 ::= { lmpGroups 5 } 2297 lmpLinkVerificationGroup OBJECT-GROUP 2298 OBJECTS { lmpLinkVerificationInterval, 2299 lmpVerifyInterval, 2300 lmpVerifyDeadInterval, 2301 lmpVerifyTransportMechanism, 2302 lmpVerifyAllLinks, 2303 lmpTeLinkBitRate, 2304 lmpTeLinkWavelength 2305 } 2306 STATUS current 2307 DESCRIPTION 2308 "Collection of objects needed to implement the link 2309 verification procedure." 2310 ::= { lmpGroups 6 } 2312 lmpPerfGroup OBJECT-GROUP 2313 OBJECTS { lmpCcHCInOctets, 2314 lmpCcInDiscards, 2315 lmpCcInErrors, 2316 lmpCcHCOutOctets, 2317 lmpCcOutDiscards, 2318 lmpCcOutErrors, 2319 lmpCcHCHelloReceived, 2320 lmpCcHCHelloSent, 2321 lmpCcConfigReceived, 2322 lmpCcConfigSent, 2323 lmpCcConfigRetransmit, 2324 lmpCcLinkSummaryReceived, 2325 lmpCcLinkSummarySent, 2326 lmpCcLinkSummaryRetransmit, 2327 lmpCcChannelStatusReceived, 2328 lmpCcChannelStatusSent, 2329 lmpCcChannelStatusRequestReceived, 2330 lmpCcChannelStatusRequestSent, 2331 lmpCcChannelStatusResponseReceived, 2332 lmpCcChannelStatusResponseSent, 2333 lmpCcCounterDiscontinuityTime, 2334 lmpDataBearingLinkTestReceived, 2335 lmpDataBearingLinkTestSent, 2336 lmpDataBearingLinkCounterDiscontinuityTime 2337 } 2338 STATUS current 2339 DESCRIPTION 2340 "Collection of objects needed for providing performance 2341 information about LMP interfaces and data-bearing links." 2342 ::= { lmpGroups 7 } 2344 lmpTeLinkGroup OBJECT-GROUP 2345 OBJECTS { lmpTeLinkNbrNodeId, 2346 lmpTeLinkVerification, 2347 lmpTeLinkFaultIsolation, 2348 lmpTeLinkDwdm, 2349 lmpTeLinkOperStatus, 2350 lmpTeLinkRowStatus, 2351 lmpTeLinkStorageType, 2352 lmpTeLinkTrapEnable 2353 } 2354 STATUS current 2355 DESCRIPTION 2356 "Collection of objects needed for TE link configuration." 2357 ::= { lmpGroups 8 } 2359 lmpDataBearingLinkGroup OBJECT-GROUP 2360 OBJECTS { lmpDataBearingLinkType, 2361 lmpDataBearingLinkRemoteIfId, 2362 lmpDataBearingLinkEncodingType, 2363 lmpDataBearingLinkOperStatus, 2364 lmpDataBearingLinkRowStatus, 2365 lmpDataBearingLinkStorageType 2366 } 2367 STATUS current 2368 DESCRIPTION 2369 "Collection of objects needed for data-bearing link 2370 configuration." 2371 ::= { lmpGroups 9 } 2373 lmpNotificationGroup NOTIFICATION-GROUP 2374 NOTIFICATIONS { lmpTeLinkPropertyMismatch, 2375 lmpDataBearingLinkPropertyMismatch, 2376 lmpUnprotected, 2377 lmpControlChannelUp, 2378 lmpControlChannelDown, 2379 lmpTeLinkDegraded } 2380 STATUS current 2381 DESCRIPTION 2382 "Set of notifications implemented in this module. 2383 None is mandatory." 2384 ::= { lmpGroups 10 } 2386 -- End of LMP-MIB 2387 END 2389 11. Security Considerations 2391 It is clear that this MIB is potentially useful for monitoring of LMP 2392 enabled devices. This MIB can also be used for configuration of cer- 2393 tain objects, and anything that can be configured can be incorrectly 2394 configured, with potentially disastrous results. 2396 At this writing, no security holes have been identified beyond those 2397 that SNMP Security [SNMPArch] is itself intended to address. These 2398 relate to primarily controlled access to sensitive information and 2399 the ability to configure a device - or which might result from opera- 2400 tor error, which is beyond the scope of any security architecture. 2402 There are a number of management objects defined in this MIB which 2403 have a MAX-ACCESS clause of read-write and/or read-create. Such 2404 objects may be considered sensitive or vulnerable in some network 2405 environments. The support for SET operations in a non-secure environ- 2406 ment without proper protection can have a negative effect on network 2407 operations. The use of SNMP Version 3 is recommended over prior ver- 2408 sions, for configuration control, as its security model is improved. 2410 SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if 2411 the network itself is secure (for example by using IPSec [IPSEC]), 2412 there is no control as to who on the secure network is allowed to 2413 access and GET/SET (read/change/create/delete) the objects in this 2414 MIB. It is recommended that the implementers consider the security 2415 features as provided by the SNMPv3 framework. Specifically, the use 2416 of the User-based Security Model [SNMPv3USM] and the View-based 2417 Access Control [SNMPv3VACM] is recommended. It is then a 2418 customer/user responsibility to ensure that the SNMP entity giving 2419 access to an instance of this MIB is properly configured to give 2420 access to the objects only to those principals (users) that have leg- 2421 itimate rights to indeed GET or SET (change/create/delete) them. 2423 There are a number of managed objects in this MIB that may contain 2424 information that may be sensitive from a business perspective, in 2425 that they represent a customer's interface to the G-MPLS network. 2426 Allowing uncontrolled access to these objects could result in mali- 2427 cious and unwanted disruptions of network traffic or incorrect confi- 2428 gurations for these customers. There are no objects that are particu- 2429 larly sensitive in their own right, such as passwords or monetary 2430 amounts. 2432 12. Acknowledgments 2434 The general structure of this draft has been modeled around draft- 2435 ietf-mpls-lsr-mib-06.txt. 2437 The authors wish to thank Dmitry Ryumkin. 2439 13. References 2441 [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., 2442 Rekhter, Y., Berger, L., Saha, S., Basak, D., 2443 Sandick, H., Zinin, A., and Rajagopalan, B., 2444 "Link Management Protocol", Internet Draft 2445 , September 2001. 2447 [GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L., 2448 Bernstein, G., Drake, J., Fan, Y., Kompella, K., 2449 Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., 2450 Saha, D., Sharma, V., Swallow, G., and Tang, Z., 2451 "Generalized MPLS Signaling Function Description", 2452 Internet Draft 2453 , 2454 July 2001. 2456 [BUNDLE] Kompella, K., Rekhter, Y., and Berger, L., 2457 "Link Bundling in MPLS Traffic Engineering", 2458 Internet Draft , 2459 February 2001. 2461 [BUNDLE-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J., 2462 "Link Bundling Management Information Base using 2463 SMIv2", 2464 Internet Draft , 2465 May 2001. 2467 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 2468 RFC 1700, October 1994. See also: 2470 http://www.isi.edu/in-notes/iana/assignments/smi- 2471 numbers 2473 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 2474 FAMILY NUMBERS, (http://www.isi.edu/in- 2475 notes/iana/assignements/address-family-numbers), 2476 for MIB see: 2477 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 2479 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An 2480 Architecture for Describing SNMP Management 2481 Frameworks", RFC 2571, April 1999. 2483 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 2484 Identification of Management Information for TCP/IP- 2485 based Internets", RFC 1155, May 1990. 2487 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 2488 Definitions", RFC 1212, March 1991. 2490 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use 2491 with the SNMP", RFC 1215, March 1991. 2493 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2494 "Message Processing and Dispatching for the Simple 2495 Network Management Protocol (SNMP)", RFC 2572, 2496 April 1999. 2498 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 2499 Model (USM) for version 3 of the Simple Network 2500 Management Protocol (SNMPv3)", RFC 2574, April 2501 1999. 2503 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 2504 Waldbusser, "Protocol Operations for Version 2 of 2505 the Simple Network Management Protocol (SNMPv2)", 2506 RFC 1905, January 1996. 2508 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2509 Applications", RFC 2573, April 1999. 2511 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2512 based Access Control Model (VACM) for the Simple 2513 Network Management Protocol (SNMP)", RFC 2575, 2514 April 1999. 2516 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2517 "Introduction to Version 3 of the Internet-standard 2518 Network Management Framework", RFC 2570, April 2519 1999. 2521 [SMIv2] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2522 Case, J., Rose, M., and S. Waldbusser, 2523 "Structure of Management Information 2524 Version 2 (SMIv2)", RFC 2578, April 1999. 2526 [SNMPv2TC] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2527 Case, J., Rose, M., and S. Waldbusser, 2528 "Textual Conventions for SMIv2", 2529 RFC 2579, April 1999. 2531 [SNMPv2Conf] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2532 Case, J., Rose, M., and S. Waldbusser, 2533 "Conformance Statements for SMIv2", 2534 RFC 2580, April 1999. 2536 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2537 "Simple Network Management Protocol", RFC 1157, May 2538 1990. 2540 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 2541 Waldbusser, "Introduction to Community-based 2542 SNMPv2", RFC 1901, January 1996. 2544 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 2545 Waldbusser, "Transport Mappings for Version 2 of 2546 the Simple Network Management Protocol (SNMPv2)", 2547 RFC 1906, January 1996. 2549 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2550 "Message Processing and Dispatching for the Simple 2551 Network Management Protocol (SNMP)", RFC 2272, 2552 January 1998. 2554 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security 2555 Model (USM) for version 3 of the Simple Network 2556 Management Protocol (SNMPv3)", RFC 2574, April 2557 1999. 2559 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 2560 Waldbusser, "Protocol Operations for Version 2 of 2561 the Simple Network Management Protocol (SNMPv2)", 2562 RFC 1905, January 1996. 2564 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2565 Applications", RFC 2273, January 1998. 2567 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2568 based Access Control Model (VACM) for the Simple 2569 Network Management Protocol (SNMP)", RFC 2575, 2570 April 1999. 2572 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 2573 for the Internet Protocol", RFC 2401, November 2574 1998. 2576 [IFMIB] McCloghrie, K., and Kastenholtz, F., "The Interfaces 2577 Group MIB", RFC 2863, June 2000. 2579 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 2580 Requirement Levels", BCP 14, RFC 2119, March 1997. 2582 14. Authors' Addresses 2584 Martin Dubuc Jonathan P. Lang 2585 edgeflow, Inc. Calient Networks, Inc. 2586 329 March Rd. 25 Castilian Drive 2587 Kanata, ON, CANADA K2K 2E1 Goleta, CA 93117 2588 Phone: +1-613-270-9279 x253 Email: jplang@calient.net 2589 Email: martin.dubuc@edgeflow.com 2591 Sudheer Dharanikota Evan McGinnis 2592 Nayna Networks, Inc. Calient Networks, Inc. 2593 157 Topaz Street 5853 Rue Ferrari 2594 Milipitas, CA 95035 San Jose, CA 95138 2595 Phone: +1-408-956-8000 x357 Email: evan@calient.net 2596 Email: sudheer@nayna.com 2598 Thomas D. Nadeau 2599 Cisco Systems, Inc. 2600 300 Apollo Drive 2601 Chelmsford, MA 01824 2602 Phone: +1-978-244-3051 2603 Email: tnadeau@cisco.com 2605 15. Full Copyright Statement 2607 Copyright (C) The Internet Society (2000). All Rights Reserved. 2609 This document and translations of it may be copied and furnished to 2610 others, and derivative works that comment on or otherwise explain it 2611 or assist in its implementation may be prepared, copied, published 2612 and distributed, in whole or in part, without restriction of any 2613 kind, provided that the above copyright notice and this paragraph are 2614 included on all such copies and derivative works. However, this docu- 2615 ment itself may not be modified in any way, such as by removing the 2616 copyright notice or references to the Internet Society or other 2617 Internet organizations, except as needed for the purpose of develop- 2618 ing Internet standards in which case the procedures for copyrights 2619 defined in the Internet Standards process must be followed, or as 2620 required to translate it into languages other than English. 2622 The limited permissions granted above are perpetual and will not be 2623 revoked by the Internet Society or its successors or assigns. This 2624 document and the information contained herein is provided on an "AS 2625 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2626 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2627 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 2628 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 2629 OR FITNESS FOR A PARTICULAR PURPOSE.