idnits 2.17.00 (12 Aug 2021) /tmp/idnits44940/draft-danenberg-sonet-ces-mpls-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: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 40 longer pages, the longest (page 10) being 66 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** 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. ** The abstract seems to contain references ([MPLSArch,MPLSFW]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 6 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 293 has weird spacing: '... outSeg inSeg...' == Line 297 has weird spacing: '...| inSeg outSe...' -- 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 190, but not defined == Unused Reference: 'ENCAP' is defined on line 2119, but no explicit reference was found in the text == Unused Reference: 'LblStk' is defined on line 2138, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 2143, but no explicit reference was found in the text == Unused Reference: 'IANAFamily' is defined on line 2148, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 2166, but no explicit reference was found in the text == Unused Reference: 'RFC2574' is defined on line 2171, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 2178, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 2183, but no explicit reference was found in the text == Unused Reference: 'RFC2575' is defined on line 2186, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 2191, but no explicit reference was found in the text == Unused Reference: 'IPSEC' is defined on line 2249, but no explicit reference was found in the text == Unused Reference: 'ATOMMIB' is defined on line 2256, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'MPLSArch' -- Possible downref: Non-RFC (?) normative reference: ref. 'MPLSFW' -- Possible downref: Non-RFC (?) normative reference: ref. 'CEM' -- Possible downref: Non-RFC (?) normative reference: ref. 'TRANS' -- Possible downref: Non-RFC (?) normative reference: ref. 'ENCAP' == Outdated reference: draft-ietf-mpls-lsr-mib has been published as RFC 3813 -- Possible downref: Non-RFC (?) normative reference: ref. 'TEMIB' ** Obsolete normative reference: RFC 1595 (ref. 'SONETMIB') (Obsoleted by RFC 2558) -- Possible downref: Non-RFC (?) normative reference: ref. 'LblStk' ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAFamily' ** Obsolete normative reference: RFC 2271 (ref. 'SNMPArch') (Obsoleted by RFC 2571) -- Possible downref: Non-RFC (?) normative reference: ref. 'SMIv1' ** 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) ** Obsolete normative reference: RFC 1902 (ref. 'SMIv2') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. 'SNMPv2TC') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. 'SNMPv2Conf') (Obsoleted by RFC 2580) ** 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) ** Obsolete normative reference: RFC 2233 (ref. 'IFMIB') (Obsoleted by RFC 2863) Summary: 29 errors (**), 0 flaws (~~), 19 warnings (==), 14 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Dave Danenberg 2 Internet Draft Scott C. Park 3 Expires: Aug 2001 Litchfield Communications, Inc. 5 Thomas D. Nadeau 6 Cisco Systems, Inc. 8 Andrew G. Malis 9 Vivace Networks, Inc. 11 February 22 2001 13 SONET/SDH Circuit Emulation Service Over MPLS (CEM) Management 14 Information Base Using SMIv2 16 draft-danenberg-sonet-ces-mpls-mib-00.txt 18 Status of this Memo 20 This document is an Internet-Draft and is in full conformance with 21 all provisions of Section 10 of RFC2026. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as Internet- 26 Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six 29 months and may be updated, replaced, or obsoleted by other documents 30 at any 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 1 Abstract 41 This memo defines an experimental portion of the Management 42 Information Base (MIB) for use with network management protocols in 43 the Internet community. In particular, it describes managed objects 44 for modeling an adaptation of SONET/SDH circuits over a Multi- 45 Protocol Label Switching (MPLS) [MPLSArch, MPLSFW] Label Switch 46 Router (LSR). 48 Danenberg et al 1 49 Table of Contents 51 1 Abstract.....................................................1 52 2 Introduction.................................................2 53 3 Terminology..................................................3 54 4 The SNMP Management Framework................................4 55 4.1 Object Definitions..........................................5 56 5 Feature Checklist............................................5 57 6 CEM MIB usage................................................5 58 6.1 How Tunnels and Segments work with CEM......................6 59 6.2 Summary of CEM MIB..........................................6 60 6.3 CEM configuration Step by Step..............................7 61 7 Example of CEM Setup.........................................8 62 7.1 Backup Tunnels.............................................10 63 7.2 Adjacent LSRs..............................................12 64 8 CEM MIB Definitions.........................................12 65 9 References..................................................38 66 10 Author's Addresses.........................................41 67 11 Full Copyright Statement...................................42 69 2 Introduction 71 This document describes a model for managing encapsulated time 72 division multiplexed (TDM) digital signals for transmission over a 73 packet-oriented MPLS network. 75 This document is closely related to [CEM], which describes a circuit 76 emulation header used to encapsulate TDM signals and provide the 77 Circuit Emulation Service over MPLS (CEM). This document is also 78 related to [TRANS and ENCAP], describing the transport and 79 encapsulation of Layer 2 circuits over MPLS, respectively. 81 The model for CEM management is a MIB. The CEM MIB described in this 82 document works closely with the MIBs described in [TEMIB and LSRMIB]. 84 Together, [TEMIB and LSRMIB], describe the modeling of an MPLS 85 Tunnel, and a Tunnel's underlying cross-connects. In the spirit of 86 the [IFMIB], a CEM connection will be a virtual connection (VC), and 87 will therefore not be represented in the ifTable. 89 There are functionalities introduced here that are not discussed in 90 [CEM, ENCAP, or TRANS]. So consider them as points of discussion for 91 now. For example, introduced here is the concept of switching CEM VCs 93 between Primary and Backup MPLS Tunnels. Considering the speeds of 94 CEM VCs, there is likely a requirement for automatic protection 95 switching (APS) for tunnels carrying CEM traffic. CEM defects will be 97 used as input to CEM APS decisions. It is for further study to use 98 other mechanisms for CEM APS (see draft-chang-mpls-path-protection- 99 02.txt for other work in this area). 101 Danenberg et al Expires August 2001 2 102 CEM dynamic bandwidth allocation (DBA) is also introduced in this 103 MIB. CEM DBA will send packets with only a CEM Header (i.e., no 104 payload) that will signal local conditions (such as AIS and un- 105 equipped) when user traffic is not present. The remote CEM will play 106 out "canned" SONET payloads when DBA is signaled. 108 CEM is currently designed to carry SONET paths as a "structured" 109 adaptation (see Terminology). "Unstructured" CEM is for future 110 consideration. The CEM MIB will reference SONET paths as modeled 111 within [SONETMIB]. 113 Comments should be made directly to the MPLS mailing list at 114 mpls@uu.net. 116 This memo does not, in its draft form, specify a standard for the 117 Internet community. 119 Conventions used in this document 121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 123 this document are to be interpreted as described in RFC-2119 124 [BCP14]. 126 3 Terminology 128 This document uses terminology from the document describing the 129 MPLS architecture [MPLSArch]. A Label Switched Path (LSP) is modeled 130 as described in [LSRMIB and TEMIB] via a series of cross-connects 131 through 1 or more Label switch routers (LSR). 133 CEM terminology comes from the CEM draft that describes a mechanism 134 for transporting time division multiplexed (TDM) digital signals 135 over a packet-oriented MPLS network. The mechanism outlined in the 136 CEM draft terminates the SONET section and line overhead and then 137 breaks the SONET path's Synchronous Payload Envelope (SPE) into 138 fragments for transmission over a packet-based network. A 32-bit TDM 139 header is appended at the beginning of each fragment to provide 140 information regarding where the SPE begins within the packet stream, 141 a sequence number, and pointer adjustment information. 143 "Adaptation" refers to the method of adapting a "foreign" 144 communications protocol such that it can be carried by a "native" 145 protocol. In this case, the foreign protocol is SONET/SDH and the 146 native protocol is MPLS. 148 "Outbound" references the traffic direction where a SONET path's 149 payload (SPE) is received, adapted to MPLS, assigned a VC label, and 150 sent into the MPLS network. 152 Conversely, "inbound" is the direction where packets are received 153 from the MPLS network, packet payloads are reassembled back into an 154 SPE, and inserted as a SONET path into the SONET section and line. 156 Danenberg et al Expires August 2001 3 157 Since A SONET path is bi-directional and symmetrical, it uses the 158 same SONET time-slot, SONET width, MPLS packet size, and VC Label for 160 outbound and inbound traffic. 162 CEM will normally transmit into an originating "head" end of a Tunnel 164 LSP, and receive from a terminating "tail" end a Tunnel LSP. A CEM 165 connection typically uses a VC (virtual connection) Label within a 166 Tunnel Label [TRANS]. Multiple CEM VCs each with a unique MPLS VC 167 Label and similar traffic engineering requirements can share the same 169 MPLS Tunnel. For Layer 2 transport over MPLS, the Tunnel Label is 170 known as the "outer" Label, while the VC Label is known as the 171 "inner" Label. An exception to this is with adjacent LSRs. In this 172 case, there is an option for CEM VCs to connect directly without an 173 outer Label. 175 VCs can be configured to switch to a "Backup Tunnel". The active 176 Tunnel may be referred to as "In-service", while inactive Tunnels are 178 "Standby". 180 4 The SNMP Management Framework 182 The SNMP Management Framework presently consists of five major 183 components: 185 - An overall architecture, described in RFC 2271 [SNMPArch]. 187 - Mechanisms for describing and naming objects and events for the 188 purpose of management. The first version of this Structure of 189 Management Information (SMI) is called SMIv1 and described in RFC 190 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 [SNMPv1Traps]. 191 The second version, called SMIv2, is described in RFC 1902 [SMIv2], 192 RFC 1903 [SNMPv2TC] and RFC 1904 [SNMPv2Conf]. 194 - Message protocols for transferring management information. The 195 first version of the SNMP message protocol is called SNMPv1 and 196 described in RFC 1157 [SNMPv1]. A second version of the SNMP message 198 protocol, which is not an Internet standards track protocol, is 199 called SNMPv2c and described in RFC 1901 [SNMPv2c] and RFC 1906 200 [SNMPv2TM]. The third version of the message protocol is called 201 SNMPv3 and described in RFC 1906 [SNMPv2TM], RFC 2272 [SNMPv3MP] and 202 RFC 2574 [SNMPv3USM]. 204 - Protocol operations for accessing management information. The 205 first set of protocol operations and associated PDU formats is 206 described in RFC 1157 [SNMPv1]. A second set of protocol operations 207 and associated PDU formats is described in RFC 1905 [SNMPv2PO]. 209 - A set of fundamental applications described in RFC 2273 210 [SNMPv3App] and the view-based access control mechanism described in 211 RFC 2575 [SNMPv3VACM]. 213 Danenberg et al Expires August 2001 4 214 Managed objects are accessed via a virtual information store, termed 215 the Management Information Base or MIB. Objects in the MIB are 216 defined using the mechanisms defined in the SMI. This memo specifies 217 a MIB module that is compliant to the SMIv2. A MIB conforming to the 218 SMIv1 can be produced through the appropriate translations. The 219 resulting translated MIB must be semantically equivalent, except 220 where objects or events are omitted because no translation is 221 possible (use of Counter64). Some machine-readable information in 222 SMIv2 will be converted into textual descriptions in SMIv1 during the 224 translation process. However, this loss of machine-readable 225 information is not considered to change the semantics of the MIB. 227 4.1 Object Definitions 229 Managed objects are accessed via a virtual information store, termed 230 the Management Information Base or MIB. Objects in the MIB are 231 defined using the subset of Abstract Syntax Notation One (ASN.1) 232 defined in the SMI. In particular, each object type is named by an 233 OBJECT IDENTIFIER, an administratively assigned name. The object type 235 together with an object instance serves to uniquely identify a 236 specific instantiation of the object. For human convenience, we 237 often use a textual string, termed the descriptor, to also refer to 238 the object type. 240 5 Feature Checklist 242 The Circuit Emulation over MPLS MIB (CEM-MIB) is designed to satisfy 243 the following requirements and constraints: 245 - The MIB supports manually configured CEM VCs. Although, the VC ID 246 parameters needed for LDP are contained within this MIB. Adaptation 247 circuits (like CEM VCs) configured via any MPLS signaling protocol 248 are for future study. 250 - The MIB supports point-to-point CEM connections. Point-to- 251 multipoint connections are for future study. 253 - The MIB establishes the adaptation connection by referencing the 254 SONET path (within the ifTable [IFMIB]) to be adapted, the VC (inner) 256 Label, and the two Tunnels [TEMIB] that carry the bi-directional 257 SONET path. 259 - The MIB configures the Tunnel and VCs: for Tunnel APS. 261 - The MIB configures the connection: name, packet length, error 262 actions, etc. 264 - The MIB reports: operational state, packet counts, error counts, 265 etc. 267 6 CEM MIB usage 269 Danenberg et al Expires August 2001 5 270 6.1 How Tunnels and Segments work with CEM 272 The following sections do not cover setting up a full connection 273 across an MPLS network. They cover the configuration of the edge LSR 274 - that is to say, the LSR providing the CEM function. Since Tunnels 275 are uni-directional, a pair of Tunnels must be configured (one for 276 inbound, one for outbound). The following graphic depicts a CEM VC 277 that originates and terminates at LSR-M. It uses LSPs A and B formed 278 by Tunnels Ax and Bx continuing through LSR-N to LSR-P. The 279 concatenations of Tunnels create the LSPs. Note: since the CEM cross- 280 connects terminate and originate at LSR-M, the in and out segments 281 are not in tandem pairs (as they are in the transit LSR-N), this is 282 per [LSRMIB]. Note: 'X' denotes a Tunnel's cross-connect. 284 LSP-A 285 <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 287 +---- (edge) LSR-M ---+ +--------- LSR-N ---------+ + LSR-P 289 | | | | | 290 | Tunnel | | Tunnel | | 291 +---+ A1 (M<-N) +----+ +----+ A2 (M<-P) +----+ +----+ 292 | | <------| | | |<--------------| | | | 293 <-->|CEM| inSeg |MPLS| |MPLS| outSeg inSeg |MPLS| |MPLS| 294 S P | | <---X<-----| IF | | IF |<------X<------| IF | | IF | 295 O a | | | |<-->| | | |<-->| | 296 N t | | --->X----->| | | |------>X------>| | | | 297 E h | | outSeg | | | | inSeg outSeg | | | | 298 T | | ------>| | | |-------------->| | | | 299 +---+ Tunnel +----+ +----+ Tunnel +----+ +----+ 300 | B1 (M->N) | | B2 (M->P) | | 301 | | | | | 302 +---------------------+ +-------------------------+ +----- 304 - - - - - - - - - - - - - - - - - - - - - - - - - - - - -> 305 LSP-B 307 6.2 Summary of CEM MIB 309 - The CEM SONET extension (mplsCemSonetPathExtTable) is used to 310 indicate the time slot of the SONET path to be adapted. 312 - The CEM VC Table (mplsCemVcTable) is used for associating a SONET 313 path with a pair of MPLS Tunnels (inbound and outbound). Its many 314 objects are used to control VCs. 316 - The CEM Performance Table (mplsCemVcPerfTable) is an augmentation 317 of the mplsCemVcTable and contains many objects for monitoring VCs. 319 - The CEM Mapping Table (mplsCemMappingTable) is used to map the 320 inbound Tunnel and VC Label to the Circuit ID. The Circuit ID is the 321 index to an entry in the mplsCemVcTable. 323 - The Tunnel Extension Table (mplsCemTunnelExtTable) is used to 324 configure any Tunnel switchover parameters. 326 Danenberg et al Expires August 2001 6 327 - The Tunnel Extension Performance Table (mplsCemTunnelExtPerfTable) 328 is used to monitor indications not available in the 329 mplsTunnelPerfTable. 331 6.3 CEM configuration Step by Step 333 Configuring a CEM VC and a pair of Tunnels (at LSR-M) involves the 334 following steps. 336 First configure the Tunnels and their cross-connects: 338 - Follow steps as defined in [TEMIB] to configure a Tunnel. 340 - Follow steps as defined in [LSRMIB] to set up the outbound cross- 341 connect for that Tunnel. As this is the Tunnel origination (head- 342 end), the cross-connect will not reference an InSegment and the 343 ingress LSR ID will be set to that of the local (edge) LSR. 345 - Set up the inbound cross-connect per [LSRMIB]. As this is the 346 Tunnel termination (tail-end), the cross-connect will not reference 347 an OutSegment and the egress LSR ID will be set to that of the local 348 (edge) LSR. 350 Configure the SONET parameters: 352 - Set the SONET path width in the sonetPathCurrentTable [SONETMIB]. 354 - Set the SONET path starting time slot in the 355 mplsCemSonetPathExtTable. 357 Configure the CEM VC: 359 - Create an entry in the mplsCemVcTable. The first index is obtained 360 from the agent, the second is the VC instance. (Note: there may be 361 multiple instances of an mplsCemVcTable entry for use with Backup 362 Tunnels.) Now bind this entry to the SONET ifIndex [SONETMIB], the VC 364 Label, and the inbound and outbound tunnels [TEMIB] by setting those 365 objects. 367 - Set other parameters in the mplsCemVcTable (packet length, etc.). 369 - Although MPLS signaling of CEM is outside the scope of this 370 document, LDP parameters are defined in the mplsCemVcTable: VC ID 371 length, VC group ID, and optional VC parameters (the VC Circuit ID 372 can be the mplsCemVcTable index, the VC Type for CEM is specified in 373 [TRANS]). 375 - Use the VC Label to create an entry in the mplsCemMappingTable. 376 This table is indexed by the inbound Tunnel's indexes plus the VC 377 Label. It associates the inbound Tunnel and VC Label to the 378 mplsCemVcTable entry. 380 Danenberg et al Expires August 2001 7 381 - Once a CEM VC is operational, the mplsCemVcPerfTable is used to 382 monitor the various counts, indicators, and conditions of the VC. 384 Advanced CEM configuration (mplsCemVcTable and 385 mplsCemTunnelExtTable): 387 - VC backup. In the mplsCemVcTable, as part of CEM APS, set the 388 criteria for switching this VC to the Backup Tunnel. 390 - Tunnel Table. In the mplsCemTunnelExtTable, an entry is created 391 here for each entry in the mplsCemMappingTable. This 392 mplsCemTunnelExtTable table is indexed with the same indexes as the 393 inbound Tunnel [TEMIB]. 395 - Tunnel Backup. As with VC backup, there are objects for setting 396 Tunnel Backup switchover criteria. For Tunnels, they are in the 397 mplsCemTunnelExtTable. An entry is created in this table by the agent 399 for every entry in the mplsCemMappingTable, and is indexed as the 400 inbound Tunnel is indexed [TEMIB]. Backup Tunnel switchovers will 401 switch all VCs in bulk. It is for this reason that care must be taken 403 if Tunnel Backup and VC Backup mechanisms are both configured. 405 Note: CEM VCs are always configured with a pair of Tunnels (inbound 406 and outbound). When a second set of CEM VC and Backup Tunnel is 407 configured, then there will be a total of 4 Tunnels involved. To 408 reduce complexities, it is recommended to design the agent's APS 409 mechanism to switch completely from one CEM VC/Tunnel set to another. 411 For example, do not use an inbound Primary Tunnel with an outbound 412 Backup Tunnel. To mix Primary and Backup Tunnels is for future study. 414 7 Example of CEM Setup 416 In this section we provide an example of using the MIB objects 417 described in section 8 to set up a CEM VC. While this example is not 418 meant to illustrate every permutation of the MIB, it is intended as 419 an aid to understanding some of the key concepts. It is meant to be 420 read after going through the MIB itself. See [LSRMIB] and [TEMIB] for 422 an example of setting up Tunnels, their segments and cross-connects. 424 First configure the SONET path width, starting time-slot, and 425 associated CEM VC. In this case, an STS-3c starts at SONET time slot 426 1 (and is evenly distributed within the SONET frame). The ifIndex for 428 both the sonetPathCurrentEntry and mplsCemSonetPathExtTable is 23. 430 In sonetPathCurrentEntry: 431 { 432 sonetPathCurrentWidth = 3, 433 sonetPathCurrentStatus 434 ... 435 ... 436 } 438 Danenberg et al Expires August 2001 8 439 In mplsCemSonetPathExtTable: 440 { 441 mplsCemSonetPathExtVcIndex = 1 442 mplsCemSonetPathExtTimeSlot = 1 443 } 445 Then create a CEM configuration entry in mplsCemVcTable. The indexes 446 are Index and Instance. Set PathIfIndex and VcLabel. The tunnel 447 pointers [TEMIB] contain LSR IDs (normally IP addresses) as indexes. 449 In mplsCemVcTable: 450 { 451 mplsCemVcIndex = 1 452 mplsCemVcInstance = 1 453 mplsCemVcSonetPathIfIndex = 23 454 mplsCemVcVcLabel = 55 455 mplsCemVcPriority = 1 456 mplsCemVcName = "My Tunnel", 457 mplsCemVcDescr = "Here to there" 458 mplsCemVcCreateTime = Feb 7 2001 459 mplsCemVcInTunnelIndex = 1 460 mplsCemVcInTunnelInstance = 1 461 mplsCemVcInTunnelIngLSR = 123.123.125.1 462 mplsCemVcInTunnelLclLSR = 123.123.126.1 463 mplsCemVcOutTunnelIndex = 2 464 mplsCemVcOutTunnelInstance = 1 465 mplsCemVcOutTunnelLclLSR = 123.123.126.1 466 mplsCemVcOutTunnelEgrLSR = 123.123.125.1 467 mplsCemVcPktLength = 500 -- payload bytes 468 mplsCemVcExpBits = 0 469 mplsCemVcPktResequence = 0 470 mplsCemVcEnableDBA = 0 471 mplsCemVcJtrBfrDepth = 50 -- packets 472 mplsCemVcErrorAction = playAllOnes 473 mplsCemVcDownAction = playAllOnes 474 mplsCemVcIntegrateToDown1 = 1000 -- microseconds 475 mplsCemVcIntegrateToDown2 = 500 476 mplsCemVcIntegrateToUp1 = 10000 477 mplsCemVcIntegrateToUp2 = 0 478 mplsCemVcApsEnable = false 479 mplsCemVcApsCriteria = 0 480 mplsCemVcApsHoldOffTimer = 0 481 mplsCemVcApsRevertTimer = 0 482 mplsCemVcLdpVcIdLength = 0 483 mplsCemVcLdpGroupId = 0 484 mplsCemVcLdpOptParam1 = 0 485 mplsCemVcLdpOptParam2 = 0 486 mplsCemVcTrapEnable = true 487 mplsCemVcAdminStatus = up 488 mplsCemVcRowStatus = createAndGo 489 } 491 Danenberg et al Expires August 2001 9 492 Now make the association of the inbound Tunnel and VC Label to the 493 mplsCemVcTable entry. The Tunnel Index, Instance, Ingress & Local LSR 495 IDs, and VC Label are the 5 indexes for this table. Since the inbound 497 Tunnel terminates here, its egress LSR ID should be that of the local 499 (edge) LSR. Creating an entry in this table causes a corresponding 500 entry to be made in the mplsCemTunnelExt and mplsCemTunnelExtPerf 501 tables. 503 In mplsCemMappingTable: 504 { 505 mplsCemMappingInTunnelIndex = 1 506 mplsCemMappingInTunnelInstance = 1 507 mplsCemMappingInTunnelIngressLSR = 123.123.125.1 508 mplsCemMappingInTunnelLocalLSR = 123.123.126.1 509 mplsCemMappingVcLabel = 55 510 mplsCemMappingVcIndex = 1 511 mplsCemMappingVcInstance = 1 512 mplsCemMappingRowStatus = createAndGo 513 } 515 Now configure the Tunnel extension table. It has the same indexes as 516 the mplsTunnelTable entry for the inbound Tunnel. An entry in this 517 table was created automatically when the mplsCemMapping table entry 518 was created. 520 In MplsCemTunnelExtTable: 521 { 522 mplsCemTunnelExtApsEnable = false 523 mplsCemTunnelExtApsCriteria = 0 524 mplsCemTunnelExtApsHoldoffTimer = 0 525 mplsCemTunnelExtApsRevertTimer = 0 526 mplsCemTunnelExtApsViaCemVcIndex = 0 527 mplsCemTunnelExtApsViaCemVcInstance = 0 528 } 530 7.1 Backup Tunnels 532 At this time, the type of APS supported by Backup Tunnels is for uni- 533 directional protection switching. The approach used here supports 1+1 535 switching where APS decisions are made on the inbound ("sink") side 536 based on CEM errors. Since CEM packets are emitted at regular 537 intervals and contain sequence numbers, failures can be detected 538 quickly and reliably. 540 An area for further study is 1:1 switching - normally this requires a 542 backward defect indication. However, this may be accomplished by 543 forcing an upstream error, when downstream errors occur. In other 544 words, when the sink side sees CEM errors and switches to standby, it 546 could turn off its outbound packet stream, thereby forcing remote CEM 548 errors, and causing the remote to also switch to standby. Also for 549 further study is obtaining failure indications from other than CEM 550 errors (e.g., OAM). 552 Danenberg et al Expires August 2001 10 553 If Backup Tunnels are desired, they should be configured in the 554 mplsTunnelTable [TEMIB]. They MUST be configured in this table as 555 entries using the same mplsTunnelIndex primary index, but with 556 unique mplsTunnelInstances as secondary indexes. This will result in 557 the tunnel instances being configured in a group. It is also 558 important to note that these secondary entries may contain different 559 LSR IDs, as well as different corresponding tunnelHopTable, 560 tunnelARHopTable, and tunnelCHop entries. For example, if it were 561 desired to create a tunnel with one back up path, the 562 mplsTunnelTable would contain two entries with a primary index of 2. 563 Their two entries would have secondary indexes (mplsTunnelInstance) 564 of 5 and 8. Hence, there would be two entries: (2,5) and (2,8). The 565 secondary tunnel (2,8) should have a different cross-connect 566 (mplsTunnelXCPointer) as it should take a different path (i.e.: to 567 protect nodes or links) through the network to circumvent a network 568 failure. It should also be the case that the Tunnel Label differs 569 between both instances of the tunnel. 571 For a CEM VC to utilize a Backup Tunnel, there will be another 572 instance of the CEM VC within the mplsCemVcTable (forming a CEM VC 573 group). Each group member will have the same Index, PathIfIndex, and 574 VcLabel, but with a unique mplsCemVcInstance. Each CEM VC instance 575 will reference a different Tunnel (within a group of Tunnels). As 576 with the Tunnels, a primary CEM VC may be instance-1 while a backup 577 VC may be instance-2. 579 The switchover criteria in the mplsCemVc and mplsCemTunnelExt tables 580 control the switchover when groups of CEM VCs and Tunnels have been 581 configured. If the switchover is tunnel-based (that is, bulk VC 582 switchover is being employed), then the mplsCemVc switchover criteria 584 should be none (and vice-versa). 586 Whether Tunnel Backup decisions are VC-based or tunnel-based, it is 587 the APS criterion that initiates switchover processing. The system 588 may then look for other Tunnels (within the group) that have no 589 failures (according to criteria). If a switchover is to occur and 590 there is more than one "good" Tunnel to switch to, then the Tunnel 591 and CEM VC instances are used to decide (lower instances have higher 592 priority). Things causing a bad tunnel are: administrative settings 593 (CEM VC or Tunnel admin down), CEM jitter buffer errors, CEM missing 594 packets, and CEM header errors (other criteria are for future study). 596 The "revertive" setting can also initiate a switch. This parameter is 598 useful for non-primary Tunnels where you may want to switch back to a 600 Primary Tunnel even if the Backup Tunnel is OK. Finally there is 601 "hunt" mode for initiating switches in situations where the active 602 Tunnel is bad, but there are no defect indications available from the 604 standby Tunnels. 606 APS timers: There is a timer for use with "revertive" to delay 607 switching back a Primary Tunnel once that Tunnel looks good. There is 609 also a hold-off timer to delay switching from an active Tunnel once 610 it looks bad. 612 Danenberg et al Expires August 2001 11 613 It is possible that the bandwidth for a Backup Tunnel may be less 614 than that of the Primary Tunnel. In this case, when VCs are switched 615 over to the Backup, lower priority VCs may have to be dropped (set 616 dormant). The mplsCemVcPriority object is provided for this purpose. 617 Sorting and dropping is normally the responsibility the CAC 618 (connection admission control) function within an LSR. 620 7.2 Adjacent LSRs 622 This section explains the how to configure CEM VCs that are connected 624 via adjacent LSRs. 626 As [TRANS] points out, a VC label within a Tunnel label may not be 627 necessary in the Adjacent LSR case. To configure such a connection, 628 all the steps described above would be the same except when 629 configuring the OutSegment [LSRMIB]. In this case, PushTopLabel in 630 the [LSRMIB] object would be set false. 632 8 CEM MIB Definitions 634 MPLS-CEM-MIB DEFINITIONS ::= BEGIN 636 IMPORTS 637 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 638 experimental, Integer32, Counter32, Unsigned32, 639 Counter64, Gauge32 640 FROM SNMPv2-SMI 642 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 643 FROM SNMPv2-CONF 645 TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, 646 TimeStamp, DisplayString 647 FROM SNMPv2-TC 649 InterfaceIndex, InterfaceIndexOrZero 650 FROM IF-MIB 652 MplsLSPID, MplsLabel 653 FROM MPLS-LSR-MIB 655 MplsLsrId, MplsTunnelIndex, MplsTunnelInstanceIndex 656 FROM MPLS-TE-MIB; 658 mplsCemMIB MODULE-IDENTITY 659 LAST-UPDATED "200102211200Z" -- 21 Feb 2001 12:00:00 EST 660 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 661 CONTACT-INFO 662 " Dave Danenberg 663 Postal: Litchfield Communications, Inc. 664 76 Westbury Park Rd 665 Princeton Building East 666 Watertown, CT 06795 667 Tel: +1-860-945-1573 x3180 669 Danenberg et al Expires August 2001 12 670 Email: dave_danenberg@litchfieldcomm.com 672 Thomas D. Nadeau 673 Postal: Cisco Systems, Inc. 674 250 Apollo Drive 675 Chelmsford, MA 01824 676 Tel: +1-978-244-3051 677 Email: tnadeau@cisco.com 679 Andrew G. Malis 680 Postal: Vivace Networks, Inc. 681 2730 Orchard Parkway 682 San Jose, CA 95134 683 Email: Andy.Malis@vivacenetworks.com 685 Scott Park 686 Postal: Litchfield Communications, Inc. 687 76 Westbury Park Rd 688 Princeton Building East 689 Watertown, CT 06795 690 Tel: +1-860-945-1573 x3185 691 Email: scott_park@litchfieldcomm.com 693 The MPLS Working Group (email distribution mpls@uu.net)" 695 DESCRIPTION 696 "This MIB contains managed object definitions for Circuit 697 Emulation over MPLS as in: Malis, A., Vogelsang, S., and 699 Martini, L. 'SONET/SDH Circuit Emulation Service Over MPLS 700 (CEM) encapsulation', Internet Draft , February 2001. This MIB is dependant on 702 the MIBs as defined by T. Nadeau, C. Srinivasan, and A. 703 Viswanathan and 704 " 706 -- Revision history. 707 REVISION 708 "200102141200Z " -- 14 Feb 2001 12:00:00 EST 709 DESCRIPTION 710 "Initial version for closed review." 711 REVISION 712 "200102221200Z " -- 22 Feb 2001 12:00:00 EST 713 DESCRIPTION 714 "Updates, cleanup, and clarifications after review amongst 715 authors." 716 ::= { experimental 9999 } 718 -- Top level components of this MIB. 720 -- Traps 721 mplsCemNotifications OBJECT IDENTIFIER ::= { mplsCemMIB 0 } 722 mplsCemNotifyPrefix OBJECT IDENTIFIER ::= { mplsCemNotifications 0 723 } 725 Danenberg et al Expires August 2001 13 726 -- Tables, Scalars 727 mplsCemObjects OBJECT IDENTIFIER ::= { mplsCemMIB 1 } 729 -- Conformance 730 -- mplsCemConformance OBJECT IDENTIFIER ::= { mplsCemMIB 2 } 732 -- MPLS CEM Virtual Connection (VC) Table. 734 mplsCemVcIndexNext OBJECT-TYPE 735 SYNTAX Unsigned32 736 MAX-ACCESS read-only 737 STATUS current 738 DESCRIPTION 739 "This object contains an appropriate value to be used 740 for mplsCemVcIndex when creating entries in the 741 mplsCemVcTable. The value 0 indicates that no 742 unassigned entries are available. To obtain the 743 value of mplsCemVcIndex for a new entry in the 744 mplsCemVcTable, the manager issues a management 745 protocol retrieval operation to obtain the current 746 value of mplsCemVcIndex. After each retrieval 747 operation, the agent should modify the value to 748 reflect the next unassigned index. After a manager 749 retrieves a value the agent will determine through 750 its local policy when this index value will be made 751 available for reuse." 752 ::= { mplsCemObjects 1 } 754 mplsCemVcTable OBJECT-TYPE 755 SYNTAX SEQUENCE OF MplsCemVcEntry 756 MAX-ACCESS not-accessible 757 STATUS current 758 DESCRIPTION 759 "This table specifies information for connecting 760 SONET paths and MPLS Tunnels." 761 ::= { mplsCemObjects 2 } 763 mplsCemVcEntry OBJECT-TYPE 764 SYNTAX MplsCemVcEntry 765 MAX-ACCESS not-accessible 766 STATUS current 767 DESCRIPTION 768 "A row in this table represents a connection for CEM. It 769 is indexed by : 771 - The mplsCemVcIndex. Uniquely identifying a singular 772 CEM connection or a group. If a group, individual CEM 773 connections are identified by the Instance. 775 - The mplsCemVcInstance." 777 INDEX { mplsCemVcIndex, mplsCemVcInstance } 779 Danenberg et al Expires August 2001 14 780 ::= { mplsCemVcTable 1 } 782 MplsCemVcEntry ::= SEQUENCE { 783 mplsCemVcIndex Unsigned32, 784 mplsCemVcInstance Unsigned32, 785 mplsCemVcSonetPathIfIndex InterfaceIndexOrZero, 786 mplsCemVcLabel MplsLabel, 787 mplsCemVcPriority Unsigned32, 788 mplsCemVcName DisplayString, 789 mplsCemVcDescr DisplayString, 790 mplsCemVcCreateTime TimeStamp, 791 mplsCemVcUpTime TimeTicks, 793 mplsCemVcInTunnelIndex MplsTunnelIndex, 794 mplsCemVcInTunnelInstance MplsTunnelInstanceIndex, 795 mplsCemVcInTunnelIngLSR MplsLsrId, 796 mplsCemVcInTunnelLclLSR MplsLsrId, 798 mplsCemVcOutTunnelIndex MplsTunnelIndex, 799 mplsCemVcOutTunnelInstance MplsTunnelInstanceIndex, 800 mplsCemVcOutTunnelLclLSR MplsLsrId, 801 mplsCemVcOutTunnelEgrLSR MplsLsrId, 803 mplsCemVcPktLength Unsigned32, 804 mplsCemVcExpBits Unsigned32, 805 mplsCemVcPktResequence TruthValue, 806 mplsCemVcEnableDBA BITS, 807 mplsCemVcJtrBfrDepth Unsigned32, 808 mplsCemVcErrorAction INTEGER, 809 mplsCemVcDownAction INTEGER, 810 mplsCemVcIntegrateToDown1 Unsigned32, 811 mplsCemVcIntegrateToDown2 Unsigned32, 812 mplsCemVcIntegrateToUp1 Unsigned32, 813 mplsCemVcIntegrateToUp2 Unsigned32, 814 mplsCemVcApsEnable TruthValue, 815 mplsCemVcApsCriteria BITS, 816 mplsCemVcDefects BITS, 817 mplsCemVcApsHoldoffTimer Unsigned32, 818 mplsCemVcApsRevertTimer Unsigned32, 819 mplsCemVcApsStatus INTEGER, 820 mplsCemVcLdpVcIdLength Unsigned32, 821 mplsCemVcLdpGroupId Unsigned32, 822 mplsCemVcLdpOptParam1 Unsigned32, 823 mplsCemVcLdpOptParam2 Unsigned32, 824 mplsCemVcTrapEnable TruthValue, 825 mplsCemVcAdminStatus INTEGER, 826 mplsCemVcOperStatus INTEGER, 827 mplsCemVcRowStatus RowStatus, 828 mplsCemVcStorageType StorageType 829 } 831 mplsCemVcIndex OBJECT-TYPE 832 SYNTAX Unsigned32 833 MAX-ACCESS accessible-for-notify 835 Danenberg et al Expires August 2001 15 836 STATUS current 837 DESCRIPTION 838 "Primary index for the conceptual row identifying 839 a group of CEM VCs." 840 ::= { mplsCemVcEntry 1 } 842 mplsCemVcInstance OBJECT-TYPE 843 SYNTAX Unsigned32 844 MAX-ACCESS accessible-for-notify 845 STATUS current 846 DESCRIPTION 847 "Uniquely identifies an instance of a CEM VC. It is 848 useful to identify multiple instances for the purpose of 849 backup VCs." 850 ::= { mplsCemVcEntry 2 } 852 mplsCemVcSonetPathIfIndex OBJECT-TYPE 853 SYNTAX InterfaceIndexOrZero 854 MAX-ACCESS accessible-for-notify 855 STATUS current 856 DESCRIPTION 857 "This is a unique index within the ifTable. It represents 858 the interface index for the SONET path. A value of zero 859 indicates an ifIndex that has yet to be configured or 860 has since disappeared." 861 ::= { mplsCemVcEntry 3 } 863 mplsCemVcLabel OBJECT-TYPE 864 SYNTAX MplsLabel 865 MAX-ACCESS accessible-for-notify 866 STATUS current 867 DESCRIPTION 868 "The incoming and outgoing label for this VC. This 869 value is placed in the Label field of the outgoing MPLS 870 shim header." 871 ::= { mplsCemVcEntry 4 } 873 mplsCemVcPriority OBJECT-TYPE 874 SYNTAX Unsigned32 875 MAX-ACCESS read-create 876 STATUS current 877 DESCRIPTION 878 "Used when resources on a tunnel or backup tunnel are 879 overbooked. The agent (connection admission control) can 880 sort CEM VC entries that share an overbooked tunnel. 881 Lower mplsCemVcPriority values have higher priority. 882 VCs dropped will be set 'dormant' (as indicated in 883 mplsCemVcOperStatus)." 884 ::= { mplsCemVcEntry 5 } 886 mplsCemVcName OBJECT-TYPE 887 SYNTAX DisplayString 888 MAX-ACCESS read-create 889 STATUS current 891 Danenberg et al Expires August 2001 16 892 DESCRIPTION 893 "The canonical name assigned to the CEM VC. This 894 name can be used to refer to the CEM VC on the 895 LSRs console port." 896 ::= { mplsCemVcEntry 6 } 898 mplsCemVcDescr OBJECT-TYPE 899 SYNTAX DisplayString 900 MAX-ACCESS read-create 901 STATUS current 902 DESCRIPTION 903 "A textual string containing information about the 904 CEM VC. If there is no description this object 905 contains a zero length string." 906 ::= { mplsCemVcEntry 7 } 908 mplsCemVcCreateTime OBJECT-TYPE 909 SYNTAX TimeStamp 910 MAX-ACCESS read-create 911 STATUS current 912 DESCRIPTION 913 "System time when theis CEM VC was created." 914 ::= { mplsCemVcEntry 8 } 916 mplsCemVcUpTime OBJECT-TYPE 917 SYNTAX TimeTicks 918 MAX-ACCESS read-only 919 STATUS current 920 DESCRIPTION 921 "Number of consecutive ticks this CEM VC has been 'up' 922 as observed in mplsCemVcOperStatus." 923 ::= { mplsCemVcEntry 9 } 925 -- The following 8 objects represent the indexes for the 926 -- inbound and outbound tunnels for this CEM VC. 927 mplsCemVcInTunnelIndex OBJECT-TYPE 928 SYNTAX MplsTunnelIndex 929 MAX-ACCESS read-create 930 STATUS current 931 DESCRIPTION "Part of set of indexes for inbound tunnel" 932 REFERENCE 933 "Srinivasan, C., Viswanathan, A., and T. Nadeau, 934 MPLS Traffic Engineering Management Information 935 Base Using SMIv2 , 936 November 2000." 937 ::= { mplsCemVcEntry 10 } 938 mplsCemVcInTunnelInstance OBJECT-TYPE 939 SYNTAX MplsTunnelInstanceIndex 940 MAX-ACCESS read-create 941 STATUS current 942 DESCRIPTION "Part of set of indexes for inbound tunnel" 943 ::= { mplsCemVcEntry 11 } 944 mplsCemVcInTunnelIngLSR OBJECT-TYPE 945 SYNTAX MplsLsrId 947 Danenberg et al Expires August 2001 17 948 MAX-ACCESS read-create 949 STATUS current 950 DESCRIPTION "Part of set of indexes for inbound tunnel" 951 ::= { mplsCemVcEntry 12 } 952 mplsCemVcInTunnelLclLSR OBJECT-TYPE 953 SYNTAX MplsLsrId 954 MAX-ACCESS read-create 955 STATUS current 956 DESCRIPTION "Part of set of indexes for inbound tunnel" 957 ::= { mplsCemVcEntry 13 } 958 mplsCemVcOutTunnelIndex OBJECT-TYPE 959 SYNTAX MplsTunnelIndex 960 MAX-ACCESS read-create 961 STATUS current 962 DESCRIPTION "Part of set of indexes for outbound tunnel" 963 ::= { mplsCemVcEntry 14 } 964 mplsCemVcOutTunnelInstance OBJECT-TYPE 965 SYNTAX MplsTunnelInstanceIndex 966 MAX-ACCESS read-create 967 STATUS current 968 DESCRIPTION "Part of set of indexes for outbound tunnel" 969 ::= { mplsCemVcEntry 15 } 970 mplsCemVcOutTunnelLclLSR OBJECT-TYPE 971 SYNTAX MplsLsrId 972 MAX-ACCESS read-create 973 STATUS current 974 DESCRIPTION "Part of set of indexes for outbound tunnel" 975 ::= { mplsCemVcEntry 16 } 976 mplsCemVcOutTunnelEgrLSR OBJECT-TYPE 977 SYNTAX MplsLsrId 978 MAX-ACCESS read-create 979 STATUS current 980 DESCRIPTION "Part of set of indexes for outbound tunnel" 981 ::= { mplsCemVcEntry 17 } 983 mplsCemVcPktLength OBJECT-TYPE 984 SYNTAX Unsigned32 985 MAX-ACCESS read-create 986 STATUS current 987 DESCRIPTION 988 "This is the packet or payload length for this CEM 989 VC. It is fixed and applies to inbound and 990 outbound packets carrying user payload. Note: DBA 991 packets have their own length and are not effected 992 by this." 993 ::= { mplsCemVcEntry 18 } 995 mplsCemVcExpBits OBJECT-TYPE 996 SYNTAX Unsigned32 997 MAX-ACCESS read-create 998 STATUS current 999 DESCRIPTION 1000 "This value is placed in the EXP bit field of the 1002 Danenberg et al Expires August 2001 18 1003 outbound MPLS shim header (with the VC Label). These 1004 EXP bits convey to the LSR the PHB to be applied to 1005 these packets." 1006 REFERENCE 1007 "Faucher, F, et al, MPLS Support of Differentiated 1008 Services Feb 2001." 1009 ::= { mplsCemVcEntry 19 } 1011 mplsCemVcPktResequence OBJECT-TYPE 1012 SYNTAX TruthValue 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION 1016 "Reports if implementation provides packet re-sequencing. 1017 With this, as inbound packets are queued in the jitter 1018 buffer, out of order packets are re-sequenced. The 1019 maximum sequence number differential (order correction 1020 can occur within) is dependant on the depth of the 1021 jitter buffer. See mplsCemVcJtrBfrDepth." 1022 ::= { mplsCemVcEntry 20 } 1024 mplsCemVcEnableDBA OBJECT-TYPE 1025 SYNTAX BITS { 1026 allOnesOnAis(0), 1027 allZerosOnUnequipped(1) 1028 } 1029 MAX-ACCESS read-create 1030 STATUS current 1031 DESCRIPTION 1032 "Any bits set here MUST enable the DBA (dynamic bandwidth 1033 allocation) feature for the specified condition. Setting 1034 allOnesOnAis will cause CEM packet payload suppression 1035 when AIS is detected on the associated SONET path. 1036 Similarly, allZerosOnUnequipped will cause payload 1037 suppression when the SONET path is un-equipped. During 1038 these conditions, CEM packets will continue to be sent, 1039 but with indicators set in the CEM header instructing the 1040 remote to play all ones or zeros onto its SONET path. 1041 Note: some implementations may not support this feature." 1042 ::= { mplsCemVcEntry 21 } 1044 mplsCemVcJtrBfrDepth OBJECT-TYPE 1045 SYNTAX Unsigned32 1046 MAX-ACCESS read-create 1047 STATUS current 1048 DESCRIPTION 1049 "This setting configures the number of packet buffers 1050 reserved for this CEM VC. (This object would not apply 1051 in implementations that support CEM VC groups, but 1052 cannot process inbound packets on CEM VCs that are 1053 currently in standby.) This object essentially sets 1054 the maximum amount of time allowed between CEM packets 1055 before the jitter buffer empties. This variable should 1056 be set based on the SONET path width (speed) and the 1058 Danenberg et al Expires August 2001 19 1059 amount of delay variation expected to be introduced by 1060 the network. Like bandwidth, jitter buffers are likely 1061 to be a limited resource to be managed." 1062 ::= { mplsCemVcEntry 22 } 1064 mplsCemVcErrorAction OBJECT-TYPE 1065 SYNTAX INTEGER { 1066 playAllOnes(1), 1067 playAllZeros(2), 1068 playPseudoRandom(3) 1069 } 1070 MAX-ACCESS read-create 1071 STATUS current 1072 DESCRIPTION 1073 "These are the actions to take when inbound packets are 1074 missing due to gap in sequence numbers (uncorrectable via 1075 available re-sequencing), jitter buffer underruns, or 1076 packets with bad CEM headers. These patterns are sent 1077 (played) on the SONET path. These settings are used for 1078 immediate errors and (unless the mplsCemVcDownAction is 1079 'none') are not in effect once the CEM VC is 'down'." 1080 ::= { mplsCemVcEntry 23 } 1082 mplsCemVcDownAction OBJECT-TYPE 1083 SYNTAX INTEGER { 1084 errorAction(1), 1085 playAllOnes(2), 1086 playAllZeros(3), 1087 playPseudoRandom(4) 1088 } 1089 MAX-ACCESS read-create 1090 STATUS current 1091 DESCRIPTION 1092 "These are the actions to take once the CEM VC has been 1093 declared 'down' (as observed in mplsCemVcOperStatus). 1094 These patterns are sent (played) on the SONET path. 1095 See Integration Timers for events causing CEM VC 'down'. 1096 If 'errorAction' is selected, then the mplsCemVcErrorAction 1097 settings stay in effect even after the CEM VC is 'down'." 1098 ::= { mplsCemVcEntry 24 } 1100 -- 1101 -- The following 4 timers work together to integrate (filter) 1102 -- errors and the lack of errors on the CEM VC. Errors are: 1103 -- missing packet, packet out of sequence, CEM header error, 1104 -- jitter buffer error. Example of usage : 1105 -- 1106 -- When an error occurs, Down1 and Down2 start counting, if 1107 -- no errors occur within Down2, Down1 is cancelled. If errors 1108 -- do occur within Down2, the Down2 timer is restarted. The CEM 1109 -- VC is 'down' if Down1 expires - then Up1 starts counting. 1110 -- If an error occurs within Up1, Up1 is restarted. The CEM VC 1111 -- is 'up' if Up1 expires. Based on this, Down2 must be less 1112 -- than Down1. Up2 timer usage is for further study. 1114 Danenberg et al Expires August 2001 20 1115 -- 1116 -- Other usage of these integration objects is for further study. 1117 -- For example, these objects may be moved to their own new table 1118 -- where rows in the new table would be referenced in the CEM VC 1119 -- table to support separate integration of the various CEM errors 1120 -- (buffer errors, missing packets, CEM header errors). 1121 -- 1122 mplsCemVcIntegrateToDown1 OBJECT-TYPE 1123 SYNTAX Unsigned32 1124 MAX-ACCESS read-create 1125 STATUS current 1126 DESCRIPTION "See comment above - units are microseconds." 1127 ::= { mplsCemVcEntry 25 } 1129 mplsCemVcIntegrateToDown2 OBJECT-TYPE 1130 SYNTAX Unsigned32 1131 MAX-ACCESS read-create 1132 STATUS current 1133 DESCRIPTION "See comment above - units are microseconds." 1134 ::= { mplsCemVcEntry 26 } 1136 mplsCemVcIntegrateToUp1 OBJECT-TYPE 1137 SYNTAX Unsigned32 1138 MAX-ACCESS read-create 1139 STATUS current 1140 DESCRIPTION "See comment above - units are microseconds." 1141 ::= { mplsCemVcEntry 27 } 1143 mplsCemVcIntegrateToUp2 OBJECT-TYPE 1144 SYNTAX Unsigned32 1145 MAX-ACCESS read-create 1146 STATUS current 1147 DESCRIPTION "See comment above - units are microseconds." 1148 ::= { mplsCemVcEntry 28 } 1150 mplsCemVcApsEnable OBJECT-TYPE 1151 SYNTAX TruthValue 1152 MAX-ACCESS read-create 1153 STATUS current 1154 DESCRIPTION 1155 "Enables this CEM VC (as part of a group) to be used for 1156 APS. A CEM VC group is created when a unique CEM VC index 1157 (in mplsCemVcTable) has multiple instances. Setting 1158 mplsCemVcApsEnable to 'false' may be useful when a CEM VC 1159 is suspect, being debugged, or not fully configured. 1160 Note: some implementations may not support APS." 1161 ::= { mplsCemVcEntry 29 } 1163 mplsCemVcApsCriteria OBJECT-TYPE 1164 SYNTAX BITS { 1165 cemError(0), 1166 cemErrorStbyOK(256), 1167 revertive(512), 1168 hunt(1024) 1170 Danenberg et al Expires August 2001 21 1171 } 1172 MAX-ACCESS read-create 1173 STATUS current 1174 DESCRIPTION 1175 "Bits set here represent defects and modes for switching 1176 the SONET path from the active CEM VC to another within 1177 this VC's group. Defects include: CEM errors (jitter 1178 buffer errors, missing packets, bad CEM headers). 1179 Separating these CEM defects into individually selectable 1180 bits, or adding other types of defect indications (e.g. 1181 OAM status) is for future study. 1183 Modes: 1184 The 'cemErrorStbyOK' mode setting is useful in APS network 1185 configurations where CEM traffic is not present on standby 1186 inbound VCs. Therefore they are expected to have CEM 1187 errors, but are still to be considered as viable switch- 1188 over candidates. cemErrorStbyOK essentially masks CEM 1189 errors when this CEM VC is in standby. 1191 'revertive' mode is useful for non-preferred CEM VCs where 1192 you may want to switch back to a preferred VC that has no 1193 defects while the currently active VC also has no defects 1194 (see mplsCemVcApsRevertTimer). 'revertive' should NOT be 1195 used when standby VCs have no defect indications available. 1196 If 'revertive' is not set, then manual reversion is possible 1198 by simply setting the active CEM VC's admin status 'down', 1199 then 'up'. Preferred should NOT have 'revertive' set. 1201 'hunt' mode is useful when standby VCs offer no defect 1202 indications (see mplsCemVcApsHoldOffTimer). 'hunt' should 1203 not be used when standby VCs have available defect 1204 indications. Hunting assumes standby VCs are good, if not 1205 the down timers will determine it's bad, and hunting 1206 continues. 1208 'hunt' and 'revertive' are mutually exclusive." 1209 ::= { mplsCemVcEntry 30 } 1211 mplsCemVcDefects OBJECT-TYPE 1212 SYNTAX BITS { 1213 cemError(0) 1214 } 1215 MAX-ACCESS read-only 1216 STATUS current 1217 DESCRIPTION 1218 "Current state of these CEM VC defects. The cemError 1219 indicator is a summary of any error associated with 1220 processing inbound CEM packets. Separately displaying 1221 CEM errors types (buffer errors, missing packets, and 1222 header errors) are for future study. Also other bits 1223 here may be defined here to show results of error trend 1224 analysis. These bits MUST be aligned with 1225 mplsCemVcApsCriteria bits so mplsCemVcApsCriteria can 1227 Danenberg et al Expires August 2001 22 1228 be used as a mask. 1229 Note: other defect indications (e.g. from OAM) are for 1230 future study." 1231 ::= { mplsCemVcEntry 31 } 1233 mplsCemVcApsHoldoffTimer OBJECT-TYPE -- units are in seconds 1234 SYNTAX Unsigned32 1235 MAX-ACCESS read-create 1236 STATUS current 1237 DESCRIPTION 1238 "Used to hold-off an APS switch after the CEM VC has been 1239 determined 'down'. The purpose is to allow potential 1240 recovery schemes within lower communications layers a 1241 chance to recover. 1243 Also useful in 'hunt' mode to hold off switching to the 1244 next CEM VC (slows oscillation when all VCs are down)." 1245 ::= { mplsCemVcEntry 32 } 1247 mplsCemVcApsRevertTimer OBJECT-TYPE -- units are in seconds 1248 SYNTAX Unsigned32 1249 MAX-ACCESS read-create 1250 STATUS current 1251 DESCRIPTION 1252 "If this CEM VC is active and 'up', then this timer is 1253 used in conjunction with 'revertive' (if set above). 1254 The reversion would be delayed for this time." 1255 ::= { mplsCemVcEntry 33 } 1257 mplsCemVcApsStatus OBJECT-TYPE 1258 SYNTAX INTEGER { 1259 active(1), 1260 standby(2) 1261 } 1262 MAX-ACCESS read-only 1263 STATUS current 1264 DESCRIPTION 1265 "If part of a CEM VC group, this indicates if the 1266 CEM VC has been selected (via APS algorithm/protocol) 1267 to connect the associated Tunnel to the SONET path. 1268 If not part of a group, then always 'active'." 1269 ::= { mplsCemVcEntry 34 } 1271 mplsCemVcLdpVcIdLength OBJECT-TYPE 1272 SYNTAX Unsigned32 1273 MAX-ACCESS read-create 1274 STATUS current 1275 DESCRIPTION 1276 "For use by LDP signaling" 1277 ::= { mplsCemVcEntry 35 } 1279 mplsCemVcLdpGroupId OBJECT-TYPE 1280 SYNTAX Unsigned32 1281 MAX-ACCESS read-create 1283 Danenberg et al Expires August 2001 23 1284 STATUS current 1285 DESCRIPTION 1286 "For use by LDP signaling" 1287 ::= { mplsCemVcEntry 36 } 1289 mplsCemVcLdpOptParam1 OBJECT-TYPE 1290 SYNTAX Unsigned32 1291 MAX-ACCESS read-create 1292 STATUS current 1293 DESCRIPTION 1294 "For use by LDP signaling" 1295 ::= { mplsCemVcEntry 37 } 1297 mplsCemVcLdpOptParam2 OBJECT-TYPE 1298 SYNTAX Unsigned32 1299 MAX-ACCESS read-create 1300 STATUS current 1301 DESCRIPTION 1302 "For use by LDP signaling" 1303 ::= { mplsCemVcEntry 38 } 1305 mplsCemVcTrapEnable OBJECT-TYPE 1306 SYNTAX TruthValue 1307 MAX-ACCESS read-write 1308 STATUS current 1309 DESCRIPTION 1310 "If this object is true, generation of mplsCemVcUp 1311 and mplsCemVcDown traps aare enabled for this CEM VC, 1312 otherwise these traps are not emitted." 1313 DEFVAL { false } 1314 ::= { mplsCemVcEntry 39} 1316 mplsCemVcAdminStatus OBJECT-TYPE 1317 SYNTAX INTEGER { 1318 up(1), -- ready to pass packets 1319 down(2), 1320 testing(3) -- in some test mode 1321 } 1322 MAX-ACCESS read-create 1323 STATUS current 1324 DESCRIPTION 1325 "The desired operational status of this CEM VC." 1326 ::= { mplsCemVcEntry 40 } 1328 mplsCemVcOperStatus OBJECT-TYPE 1329 SYNTAX INTEGER { 1330 up(1), -- ready to pass packets 1331 down(2), 1332 testing(3), -- in some test mode 1333 unknown(4), -- status cannot be determined 1334 dormant(5), 1335 notPresent(6), -- some component is missing 1336 lowerLayerDown(7) -- down due to the state of 1337 -- lower layer interfaces 1339 Danenberg et al Expires August 2001 24 1340 } 1341 MAX-ACCESS read-only 1342 STATUS current 1343 DESCRIPTION 1344 "Indicates the actual operational status of this CEM VC." 1345 ::= { mplsCemVcEntry 41 } 1347 mplsCemVcRowStatus OBJECT-TYPE 1348 SYNTAX RowStatus 1349 MAX-ACCESS read-create 1350 STATUS current 1351 DESCRIPTION 1352 "For creating, modifying, and deleting this row." 1353 ::= { mplsCemVcEntry 42 } 1355 mplsCemVcStorageType OBJECT-TYPE 1356 SYNTAX StorageType 1357 MAX-ACCESS read-create 1358 STATUS current 1359 DESCRIPTION 1360 "This variable indicates the storage type for this 1361 object." 1362 ::= { mplsCemVcEntry 43 } 1364 -- End of MPLS CEM Virtual Connection (VC) Table 1366 -- MPLS CEM VC Performance Table. 1368 mplsCemVcPerfTable OBJECT-TYPE 1369 SYNTAX SEQUENCE OF MplsCemVcPerfEntry 1370 MAX-ACCESS not-accessible 1371 STATUS current 1372 DESCRIPTION 1373 "This table provides per CEM VC performance information. 1374 Note: outbound errors are not being considered. It is 1375 assumed (at this time) that CEM packets will be forwarded 1376 as they are generated. i.e., it is assumed that there 1377 are no local outbound packet congestion issues. HC (high 1378 capacity) counters are needed for packet counts due to 1379 the high speeds expected with CEM. A SONET path of width 1380 48 can rollover a non-HC counter in a few minutes." 1381 ::= { mplsCemObjects 3 } 1383 mplsCemVcPerfEntry OBJECT-TYPE 1384 SYNTAX MplsCemVcPerfEntry 1385 MAX-ACCESS not-accessible 1386 STATUS current 1387 DESCRIPTION 1388 "An entry in this table is created by the agent for every 1389 mplsCemVcEntry. It is an extension to mplsCemVcEntry." 1391 AUGMENTS { mplsCemVcEntry } 1393 Danenberg et al Expires August 2001 25 1394 ::= { mplsCemVcPerfTable 1 } 1396 MplsCemVcPerfEntry ::= SEQUENCE { 1397 mplsCemVcPerfTotalInPacketsHC Counter64, 1398 mplsCemVcPerfTotalOutPacketsHC Counter64, 1399 mplsCemVcPerfDbaInPacketsHC Counter64, 1400 mplsCemVcPerfDbaOutPacketsHC Counter64, 1401 mplsCemVcPerfInNegPtrAdjustHC Counter64, 1402 mplsCemVcPerfInPosPtrAdjustHC Counter64, 1403 mplsCemVcPerfOutNegPtrAdjustHC Counter64, 1404 mplsCemVcPerfOutPosPtrAdjustHC Counter64, 1405 mplsCemVcPerfCrctHdrErrors Counter32, 1406 mplsCemVcPerfUncrctHdrErrors Counter32, 1407 mplsCemVcPerfMissingPkts Counter32, 1408 mplsCemVcPerfPktsOoseq Counter32, 1409 mplsCemVcPerfJtrBfrUnderruns Counter32, 1410 mplsCemVcPerfJtrBfrOverruns Counter32, 1411 mplsCemVcPerfDiscontinuityTime TimeStamp 1412 } 1414 mplsCemVcPerfTotalInPacketsHC OBJECT-TYPE 1415 SYNTAX Counter64 1416 MAX-ACCESS read-only 1417 STATUS current 1418 DESCRIPTION 1419 "Number of inbound packets received." 1420 ::= { mplsCemVcPerfEntry 1 } 1422 mplsCemVcPerfTotalOutPacketsHC OBJECT-TYPE 1423 SYNTAX Counter64 1424 MAX-ACCESS read-only 1425 STATUS current 1426 DESCRIPTION 1427 "Number of outbound packets sent." 1428 ::= { mplsCemVcPerfEntry 2 } 1430 mplsCemVcPerfDbaInPacketsHC OBJECT-TYPE 1431 SYNTAX Counter64 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "Number of DBA packets received." 1436 ::= { mplsCemVcPerfEntry 3 } 1438 mplsCemVcPerfDbaOutPacketsHC OBJECT-TYPE 1439 SYNTAX Counter64 1440 MAX-ACCESS read-only 1441 STATUS current 1442 DESCRIPTION 1443 "Number of DBA packets sent." 1444 ::= { mplsCemVcPerfEntry 4 } 1446 mplsCemVcPerfInNegPtrAdjustHC OBJECT-TYPE 1447 SYNTAX Counter64 1449 Danenberg et al Expires August 2001 26 1450 MAX-ACCESS read-only 1451 STATUS current 1452 DESCRIPTION 1453 "Number of negative pointer adjustments made on the 1454 SONET path based on CEM pointer adjustments received." 1455 ::= { mplsCemVcPerfEntry 5 } 1457 mplsCemVcPerfInPosPtrAdjustHC OBJECT-TYPE 1458 SYNTAX Counter64 1459 MAX-ACCESS read-only 1460 STATUS current 1461 DESCRIPTION 1462 "Number of postive pointer adjustments made on the 1463 SONET path based on CEM pointer adjustments received." 1464 ::= { mplsCemVcPerfEntry 6 } 1466 mplsCemVcPerfOutNegPtrAdjustHC OBJECT-TYPE 1467 SYNTAX Counter64 1468 MAX-ACCESS read-only 1469 STATUS current 1470 DESCRIPTION 1471 "Number of negative pointer adjustments seen on the 1472 SONET path and encoded onto sent CEM packets." 1473 ::= { mplsCemVcPerfEntry 7 } 1475 mplsCemVcPerfOutPosPtrAdjustHC OBJECT-TYPE 1476 SYNTAX Counter64 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "Number of positive pointer adjustments seen on the 1481 SONET path and encoded onto sent CEM packets." 1482 ::= { mplsCemVcPerfEntry 8 } 1484 mplsCemVcPerfCrctHdrErrors OBJECT-TYPE 1485 SYNTAX Counter32 1486 MAX-ACCESS read-only 1487 STATUS current 1488 DESCRIPTION 1489 "Number of correctable CEM header errors detected on 1490 inbound CEM packets." 1491 ::= { mplsCemVcPerfEntry 9 } 1493 mplsCemVcPerfUncrctHdrErrors OBJECT-TYPE 1494 SYNTAX Counter32 1495 MAX-ACCESS read-only 1496 STATUS current 1497 DESCRIPTION 1498 "Number of uncorrectable CEM header errors detected on 1499 inbound CEM packets." 1500 ::= { mplsCemVcPerfEntry 10 } 1502 mplsCemVcPerfMissingPkts OBJECT-TYPE 1503 SYNTAX Counter32 1505 Danenberg et al Expires August 2001 27 1506 MAX-ACCESS read-only 1507 STATUS current 1508 DESCRIPTION 1509 "Number of missing packets (as detected via CEM header 1510 sequence number gaps)." 1511 ::= { mplsCemVcPerfEntry 11 } 1513 mplsCemVcPerfPktsOoseq OBJECT-TYPE 1514 SYNTAX Counter32 1515 MAX-ACCESS read-only 1516 STATUS current 1517 DESCRIPTION 1518 "Number of packets detected out of sequence (via CEM 1519 header sequence numbers), but were able to be re-sequenced. 1520 That is, the differential in sequence numbers was less 1521 than the jitter buffer depth. Note: some implementations 1522 may not support this feature (see mplsCemVcPktResequence). 1523 Any packets so far out of sequence that a re-sequencer 1524 can not correct for would be counted as missing packet." 1525 ::= { mplsCemVcPerfEntry 12 } 1527 mplsCemVcPerfJtrBfrUnderruns OBJECT-TYPE 1528 SYNTAX Counter32 1529 MAX-ACCESS read-only 1530 STATUS current 1531 DESCRIPTION 1532 "Number of times the jitter buffer transitioned to empty." 1533 ::= { mplsCemVcPerfEntry 13 } 1535 mplsCemVcPerfJtrBfrOverruns OBJECT-TYPE 1536 SYNTAX Counter32 1537 MAX-ACCESS read-only 1538 STATUS current 1539 DESCRIPTION 1540 "Number of packets received while jitter buffer is full." 1541 ::= { mplsCemVcPerfEntry 14 } 1543 mplsCemVcPerfDiscontinuityTime OBJECT-TYPE 1544 SYNTAX TimeStamp 1545 MAX-ACCESS read-only 1546 STATUS current 1547 DESCRIPTION 1548 "The value of sysUpTime on the most recent occasion at 1549 which any one or more of this segment's Counter32 or 1550 Counter64 suffered a discontinuity. If no such 1551 discontinuities have occurred since the last re- 1552 initialization of the local management subsystem, then 1553 this object contains a zero value." 1554 ::= { mplsCemVcPerfEntry 15 } 1556 -- End MPLS CEM VC Performance Table 1558 -- MPLS CEM Mapping Table. 1560 Danenberg et al Expires August 2001 28 1561 mplsCemMappingTable OBJECT-TYPE 1562 SYNTAX SEQUENCE OF MplsCemMappingEntry 1563 MAX-ACCESS not-accessible 1564 STATUS current 1565 DESCRIPTION 1566 "This table maps an inbound Tunnel/VcLabel to a CEM VC." 1567 ::= { mplsCemObjects 4 } 1569 mplsCemMappingEntry OBJECT-TYPE 1570 SYNTAX MplsCemMappingEntry 1571 MAX-ACCESS not-accessible 1572 STATUS current 1573 DESCRIPTION 1574 "A row in this table represents the inbound connection 1575 between a Tunnel/VcLabel and CEM VC/instance. It is 1576 indexed by the same 4 indexes that index the inbound 1577 Tunnel, then adds the VC Label as a 5th index. The Tunnel 1578 referenced here is in the mplsTunnelTable. 1580 - The mplsCemMappingInTunnelIndex uniquely identifies a 1581 singular Tunnel or a group. If a group, individual 1582 Tunnels are identified by the Instance. 1584 - The mplsCemMappingInTunnelInstance. 1586 - ID (normally an IP address) for the ingress LSR, 1587 mplsCemMappingInTunnelIngressLSR. 1589 - ID (normally an IP address) of the Local (egress) LSR, 1590 mplsCemMappingInTunnelLocalLSR, 1592 - and the VC Label, mplsCemMappingVcLabel." 1594 INDEX { mplsCemMappingInTunnelIndex, 1595 mplsCemMappingInTunnelInstance, 1596 mplsCemMappingInTunnelIngressLSR, 1597 mplsCemMappingInTunnelLocalLSR, 1598 mplsCemMappingVcLabel } 1600 ::= { mplsCemMappingTable 1 } 1602 MplsCemMappingEntry ::= SEQUENCE { 1603 mplsCemMappingInTunnelIndex MplsTunnelIndex, 1604 mplsCemMappingInTunnelInstance MplsTunnelInstanceIndex, 1605 mplsCemMappingInTunnelIngressLSR MplsLsrId, 1606 mplsCemMappingInTunnelLocalLSR MplsLsrId, 1607 mplsCemMappingVcLabel MplsLabel, 1608 mplsCemMappingVcIndex Integer32, 1609 mplsCemMappingVcInstance Integer32, 1610 mplsCemMappingRowStatus RowStatus, 1611 mplsCemMappingStorageType StorageType 1612 } 1614 Danenberg et al Expires August 2001 29 1615 mplsCemMappingInTunnelIndex OBJECT-TYPE 1616 SYNTAX MplsTunnelIndex 1617 MAX-ACCESS accessible-for-notify 1618 STATUS current 1619 DESCRIPTION 1620 "Primary index for the conceptual row identifying 1621 a group of Tunnel/VcLabel to CEM VC mappings." 1622 ::= { mplsCemMappingEntry 1 } 1624 mplsCemMappingInTunnelInstance OBJECT-TYPE 1625 SYNTAX MplsTunnelInstanceIndex 1626 MAX-ACCESS accessible-for-notify 1627 STATUS current 1628 DESCRIPTION 1629 "Uniquely identifies an instance of a mapping" 1630 ::= { mplsCemMappingEntry 2 } 1632 mplsCemMappingInTunnelIngressLSR OBJECT-TYPE 1633 SYNTAX MplsLsrId 1634 MAX-ACCESS accessible-for-notify 1635 STATUS current 1636 DESCRIPTION 1637 "Uniquely identifies an ingress LSR" 1638 ::= { mplsCemMappingEntry 3 } 1640 mplsCemMappingInTunnelLocalLSR OBJECT-TYPE 1641 SYNTAX MplsLsrId 1642 MAX-ACCESS accessible-for-notify 1643 STATUS current 1644 DESCRIPTION 1645 "Uniquely identifies the local LSR" 1646 ::= { mplsCemMappingEntry 4 } 1648 mplsCemMappingVcLabel OBJECT-TYPE 1649 SYNTAX MplsLabel 1650 MAX-ACCESS accessible-for-notify 1651 STATUS current 1652 DESCRIPTION 1653 "Identifies a unique label on this tunnel" 1654 ::= { mplsCemMappingEntry 5 } 1656 mplsCemMappingVcIndex OBJECT-TYPE 1657 SYNTAX Integer32 1658 MAX-ACCESS read-create 1659 STATUS current 1660 DESCRIPTION 1661 "Index for entry (or group of entries, in the case of backup 1662 VCs) in the mplsCemVcTable. This value can also be thought 1663 of as the Circuit ID." 1664 ::= { mplsCemMappingEntry 6 } 1666 mplsCemMappingVcInstance OBJECT-TYPE 1667 SYNTAX Integer32 1668 MAX-ACCESS read-create 1670 Danenberg et al Expires August 2001 30 1671 STATUS current 1672 DESCRIPTION 1673 "Identifies a unique member within a CEM VC group. 1674 (This could of course be a group of one.)" 1675 ::= { mplsCemMappingEntry 7 } 1677 mplsCemMappingRowStatus OBJECT-TYPE 1678 SYNTAX RowStatus 1679 MAX-ACCESS read-create 1680 STATUS current 1681 DESCRIPTION 1682 "For creating, modifying, and deleting this row." 1683 ::= { mplsCemMappingEntry 8 } 1685 mplsCemMappingStorageType OBJECT-TYPE 1686 SYNTAX StorageType 1687 MAX-ACCESS read-create 1688 STATUS current 1689 DESCRIPTION 1690 "This variable indicates the storage type for this 1691 object." 1692 ::= { mplsCemMappingEntry 9 } 1694 -- End of MPLS CEM Mapping Table 1696 -- MPLS Tunnel Extension Table 1698 mplsCemTunnelExtTable OBJECT-TYPE 1699 SYNTAX SEQUENCE OF MplsCemTunnelExtEntry 1700 MAX-ACCESS not-accessible 1701 STATUS current 1702 DESCRIPTION 1703 "This table is an extension to the mplsTunnelTable. This 1704 table exists to configure parameters useful for CEM APS." 1705 ::= { mplsCemObjects 5 } 1707 mplsCemTunnelExtEntry OBJECT-TYPE 1708 SYNTAX MplsCemTunnelExtEntry 1709 MAX-ACCESS not-accessible 1710 STATUS current 1711 DESCRIPTION 1712 "A row in this table represents a Tunnel used for CEM VCs. 1713 The Tunnel referenced here is in the mplsTunnelTable. 1714 It is indexed by the same 4 indexes of the inbound Tunnel: 1716 - The mplsCemTunnelExtIndex uniquely identifies a 1717 singular Tunnel or a group. If a group, individual 1718 Tunnels are identified by the Instance. 1720 - The mplsCemTunnelExtInstance. 1722 - ID (normally an IP address) for the ingress LSR, 1723 mplsCemTunnelExtIngressLSR. 1725 Danenberg et al Expires August 2001 31 1726 - ID (normally an IP address) of the Local (egress) LSR, 1727 mplsCemTunnelExtLocalLSR. In the mplsTunnelTable, this 1728 index would be referred to as the Egress LSR ID. Since 1729 CEM is always at a tunnel termination, the egress LSR 1730 is always the local (edge) LSR. 1732 The local agent creates an entry here for every entry 1733 created in the mplsCemMappingTable." 1735 INDEX { mplsCemTunnelExtIndex, 1736 mplsCemTunnelExtInstance, 1737 mplsCemTunnelExtIngressLSR, 1738 mplsCemTunnelExtLocalLSR } 1740 ::= { mplsCemTunnelExtTable 1 } 1742 MplsCemTunnelExtEntry::= SEQUENCE { 1743 mplsCemTunnelExtApsEnable TruthValue, 1744 mplsCemTunnelExtApsCriteria BITS, 1745 mplsCemTunnelExtDefects BITS, 1746 mplsCemTunnelExtApsHoldoffTimer Unsigned32, 1747 mplsCemTunnelExtApsRevertTimer Unsigned32, 1748 mplsCemTunnelExtApsViaCemVcIndex Unsigned32, 1749 mplsCemTunnelExtApsViaCemVcInstance Unsigned32, 1750 mplsCemTunnelExtStorageType StorageType 1751 } 1753 mplsCemTunnelExtApsEnable OBJECT-TYPE 1754 SYNTAX TruthValue 1755 MAX-ACCESS read-create 1756 STATUS current 1757 DESCRIPTION 1758 "Enables this Tunnel (as part of a group) to be used for 1759 APS. Remember a Tunnel group is created when a unique 1760 Tunnel index (in mplsTunnelTable) has multiple instances. 1761 Tunnel disabling may be useful when a Tunnel is suspect, 1762 being debugged, or not fully configured. 1763 Note: some implementations may not support APS." 1764 ::= { mplsCemTunnelExtEntry 1 } 1766 mplsCemTunnelExtApsCriteria OBJECT-TYPE 1767 SYNTAX BITS { 1768 cemVcCriteria(0), 1769 revertive(512), 1770 hunt(1024) 1771 } 1772 MAX-ACCESS read-write 1773 STATUS current 1774 DESCRIPTION 1775 "Bits set here represent defects and modes for switching 1776 all VCs within this Tunnel to another Tunnel that has no 1777 APS defects. Currently, only CEM defects are available. 1778 Separating and individually selecting CEM defects (buffer 1780 Danenberg et al Expires August 2001 32 1781 errors, header errors, etc.) is for future study. Also, 1782 for future study: determining a Tunnel's state of 1783 usefulness via other indications (such as OAM). 1785 If 'cemVcCriteria' is set, mplsCemTunnelExtApsViaCemVc 1786 is used to index the CEM VC for which defects are 1787 included. The purpose of this is in situations when 1788 CEM VCs can generate better defects than Tunnels (for 1789 example: buffer errors). 1791 Revertive and Hunt modes: 1792 'revertive' is useful for non-primary Tunnels where you 1793 may want to switch back to a primary Tunnel that has no 1794 defects while the currently active also has no defects 1795 (see mplsCemTunnelExtApsRevertTimer). 'revertive' should 1796 NOT be used when standby Tunnels have no available defect 1797 indications. If 'revertive' is not set, then manual 1798 reversion is possible by simply setting the active 1799 Tunnel's admin status 'down', then 'up'. 1801 'hunt' is useful when standby Tunnels offer no defect 1802 indications (see mplsCemTunnelExtApsHoldOffTimer). 1803 'hunt' should not be used when standby Tunnels have 1804 available defect indications. Hunting assumes standby 1805 Tunnels are good, if not the down timers will determine 1806 it's bad, and hunting continues. 1808 'hunt' and 'revertive' are mutually exclusive. 1810 Note: criteria defect bits here MUST align with 1811 mplsCemTunnelExtDefects so it can be used as a mask." 1812 ::= { mplsCemTunnelExtEntry 6 } 1814 mplsCemTunnelExtDefects OBJECT-TYPE 1815 SYNTAX BITS { 1816 cemVcCriteria(0) 1817 } 1818 MAX-ACCESS read-only 1819 STATUS current 1820 DESCRIPTION 1821 "Current state of Tunnel defect indications. Other bits 1822 here may be defined here to show results of error trend 1823 analysis. Note: These bits MUST be aligned with 1824 mplsCemTunnelExtApsCriteria bits so 1825 mplsCemTunnelExtApsCriteria can be used as a mask. 1826 Note: other defect indications (e.g. from OAM) are for 1827 future study." 1828 ::= { mplsCemTunnelExtEntry 7 } 1830 mplsCemTunnelExtApsHoldoffTimer OBJECT-TYPE -- units are in seconds 1831 SYNTAX Unsigned32 1832 MAX-ACCESS read-create 1833 STATUS current 1835 Danenberg et al Expires August 2001 33 1836 DESCRIPTION 1837 "Primarily used to hold-off an APS switch after the Tunnel 1838 has been determined 'down'. The purpose is to allow 1839 potential recovery schemes within lower communications 1840 layers a chance to recover. 1842 Also useful in 'hunt' mode to hold off switching to the 1843 next Tunnel (slows oscillation when all Tunnels are down)." 1844 ::= { mplsCemTunnelExtEntry 8 } 1846 mplsCemTunnelExtApsRevertTimer OBJECT-TYPE -- units are in seconds 1847 SYNTAX Unsigned32 1848 MAX-ACCESS read-create 1849 STATUS current 1850 DESCRIPTION 1851 "If this Tunnel is active and 'up', then this timer 1852 is used in conjunction with 'revertive' (if set above). 1853 The reversion would be delayed for this time." 1854 ::= { mplsCemTunnelExtEntry 9 } 1856 mplsCemTunnelExtApsViaCemVcIndex OBJECT-TYPE 1857 SYNTAX Unsigned32 1858 MAX-ACCESS read-write 1859 STATUS current 1860 DESCRIPTION 1861 "Index of the CEM VC from which APS defect criteria are 1862 included with this Tunnel's APS criteria." 1863 ::= { mplsCemTunnelExtEntry 10 } 1865 mplsCemTunnelExtApsViaCemVcInstance OBJECT-TYPE 1866 SYNTAX Unsigned32 1867 MAX-ACCESS read-write 1868 STATUS current 1869 DESCRIPTION 1870 "Instance of the CEM VC from which APS defect criteria 1871 are included with this Tunnel's APS criteria." 1872 ::= { mplsCemTunnelExtEntry 11 } 1874 mplsCemTunnelExtStorageType OBJECT-TYPE 1875 SYNTAX StorageType 1876 MAX-ACCESS read-write 1877 STATUS current 1878 DESCRIPTION 1879 "This variable indicates the storage type for this object." 1880 ::= { mplsCemTunnelExtEntry 12 } 1882 -- End of MPLS Tunnel Extension Table 1884 -- MPLS CEM Tunnel Extension Performance Table 1886 mplsCemTunnelExtPerfTable OBJECT-TYPE 1887 SYNTAX SEQUENCE OF MplsCemTunnelExtPerfEntry 1888 MAX-ACCESS not-accessible 1890 Danenberg et al Expires August 2001 34 1891 STATUS current 1892 DESCRIPTION 1893 "This table is an extension to the mplsTunnelTable. It 1894 provides per Tunnel performance information." 1895 ::= { mplsCemObjects 6 } 1897 mplsCemTunnelExtPerfEntry OBJECT-TYPE 1898 SYNTAX MplsCemTunnelExtPerfEntry 1899 MAX-ACCESS not-accessible 1900 STATUS current 1901 DESCRIPTION 1902 "An entry in this table is created by the agent for every 1903 mplsCemTunnelExtEntry. It is an extension to 1904 mplsCemTunnelExtEntry." 1906 AUGMENTS { mplsCemTunnelExtEntry } 1908 ::= { mplsCemTunnelExtPerfTable 1 } 1910 MplsCemTunnelExtPerfEntry ::= SEQUENCE { 1911 mplsCemTunnelExtPerfFailedLabelLookups Counter32, 1912 mplsCemTunnelExtPerfLastFailedLookup MplsLabel 1913 } 1915 mplsCemTunnelExtPerfFailedLabelLookups OBJECT-TYPE 1916 SYNTAX Counter32 1917 MAX-ACCESS read-only 1918 STATUS current 1919 DESCRIPTION 1920 "Number of packets with unexpected labels received. This 1921 count is based on inbound VC labels seen that are not 1922 configured for this Tunnel." 1923 ::= { mplsCemTunnelExtPerfEntry 1 } 1925 mplsCemTunnelExtPerfLastFailedLookup OBJECT-TYPE 1926 SYNTAX MplsLabel 1927 MAX-ACCESS read-only 1928 STATUS current 1929 DESCRIPTION 1930 "Contains label from the packet that last failed a label 1931 lookup on this Tunnel." 1932 ::= { mplsCemTunnelExtPerfEntry 2 } 1934 -- End of MPLS Tunnel Extension Performance Table 1936 -- MPLS CEM SONET Path Extension Table. 1938 mplsCemSonetPathExtTable OBJECT-TYPE 1939 SYNTAX SEQUENCE OF MplsCemSonetPathExtEntry 1940 MAX-ACCESS not-accessible 1941 STATUS current 1942 DESCRIPTION 1943 "This table associates a SONET path with a CEM VC 1945 Danenberg et al Expires August 2001 35 1946 (or CEM VC group) and provides the starting time-slot 1947 of the SONET path. It as assumed that the transmit 1948 and receive sides of the SONET path have the same 1949 starting time-slots. It is also assumed that STSn 1950 paths have contiguous time-slots." 1951 ::= { mplsCemObjects 7 } 1953 mplsCemSonetPathExtEntry OBJECT-TYPE 1954 SYNTAX MplsCemSonetPathExtEntry 1955 MAX-ACCESS not-accessible 1956 STATUS current 1957 DESCRIPTION 1958 "This table is indexed by the SONET path ifIndex. An 1959 entry to this table is created by the agent when an 1960 entry is created in the mplsCemVcTable." 1962 INDEX { mplsCemSonetPathExtSonetIfIndex } 1964 ::= { mplsCemSonetPathExtTable 1 } 1966 MplsCemSonetPathExtEntry ::= SEQUENCE { 1967 mplsCemSonetPathExtVcIndex Unsigned32, 1968 mplsCemSonetPathExtTimeSlot Unsigned32, 1969 mplsCemSonetPathExtStorageType StorageType 1970 } 1972 mplsCemSonetPathExtVcIndex OBJECT-TYPE 1973 SYNTAX Unsigned32 1974 MAX-ACCESS read-write 1975 STATUS current 1976 DESCRIPTION 1977 "Index to entry in the mplsCemVcTable." 1978 ::= { mplsCemSonetPathExtEntry 1 } 1980 mplsCemSonetPathExtTimeSlot OBJECT-TYPE 1981 SYNTAX Unsigned32 (1..192) 1982 MAX-ACCESS read-write 1983 STATUS current 1984 DESCRIPTION 1985 "Starting time-slot for this SONET path within the 1986 SONET line and section. For OC-48, this value could 1987 range from 1 to 48. The SONET path width must be taken 1988 into consideration here, for example, in an OC-48 an 1989 STS-3c could not start at time-slot 47." 1990 ::= { mplsCemSonetPathExtEntry 2 } 1992 mplsCemSonetPathExtStorageType OBJECT-TYPE 1993 SYNTAX StorageType 1994 MAX-ACCESS read-write 1995 STATUS current 1996 DESCRIPTION 1997 "This variable indicates the storage type for this 1998 object." 1999 ::= { mplsCemSonetPathExtEntry 3 } 2001 Danenberg et al Expires August 2001 36 2002 -- End of MPLS CEM SONET Path Extension Table. 2004 -- Notifications - CEM VC 2006 mplsCemTrapEnable OBJECT-TYPE 2007 SYNTAX TruthValue 2008 MAX-ACCESS read-write 2009 STATUS current 2010 DESCRIPTION 2011 "If this object is true, then it enables the 2012 generation of mplsCemVcUp and mplsCemVcDown 2013 traps, otherwise these traps are not emitted. 2014 These traps are also individually enabled 2015 for each CEM VC." 2016 DEFVAL { false } 2017 ::= { mplsCemObjects 8 } 2019 mplsCemVcUp NOTIFICATION-TYPE 2020 OBJECTS { mplsCemVcIndex, 2021 mplsCemVcInstance, 2022 mplsCemVcOperStatus, 2023 mplsCemVcAdminStatus, 2024 mplsCemVcSonetPathIfIndex } 2025 STATUS current 2026 DESCRIPTION 2027 "This notification is generated when a 2028 mplsCemVcOperStatus object for one of the configured 2029 CEM VC entries is about to leave the down state and 2030 transition into some other state (but not into the 2031 notPresent state). This other state is indicated by 2032 the included value of mplsCemVcOperStatus." 2033 ::= { mplsCemNotifyPrefix 1 } 2035 mplsCemVcDown NOTIFICATION-TYPE 2036 OBJECTS { mplsCemVcIndex, 2037 mplsCemVcInstance, 2038 mplsCemVcOperStatus, 2039 mplsCemVcAdminStatus, 2040 mplsCemVcSonetPathIfIndex } 2041 STATUS current 2042 DESCRIPTION 2043 "This notification is generated when a 2044 mplsCemVcOperStatus object for one of the configured 2045 CEM VC entries is about to enter the down state and 2046 transition into some other state (but not from the 2047 notPresent state). This other state is indicated by 2048 the included value of mplsCemVcOperStatus." 2049 ::= { mplsCemNotifyPrefix 2 } 2051 mplsCemVcApsFrom NOTIFICATION-TYPE 2052 OBJECTS { mplsCemVcIndex, 2053 mplsCemVcInstance, 2055 Danenberg et al Expires August 2001 37 2056 mplsCemVcOperStatus, 2057 mplsCemVcAdminStatus, 2058 mplsCemVcSonetPathIfIndex } 2059 STATUS current 2060 DESCRIPTION 2061 "This notification is generated when the CEM VC APS 2062 mechanism has initiated a switch from the specified 2063 Index/Instance to find a 'good' CEM VC within the same 2064 group. To reduce the number of Traps, it is recommended 2065 to only generate mplsCemVcApsFrom when first initiating 2066 attempt to find a good CEM VC instance. That is, do not 2067 generate Traps if the APS mechanism is continuing to 2068 switch looking for an CEM VC group member that is good." 2069 ::= { mplsCemNotifyPrefix 3 } 2071 mplsCemVcApsTo NOTIFICATION-TYPE 2072 OBJECTS { mplsCemVcIndex, 2073 mplsCemVcInstance, 2074 mplsCemVcOperStatus, 2075 mplsCemVcAdminStatus, 2076 mplsCemVcSonetPathIfIndex } 2077 STATUS current 2078 DESCRIPTION 2079 "This notification is generated when the CEM VC APS 2080 mechanism has switched to and settled on a CEM VC Index 2081 and Instance that is 'good' (whether from a bad VC or 2082 when reverting)." 2083 ::= { mplsCemNotifyPrefix 4 } 2085 -- Note: generating Traps for Tunnel (bulk VC) APS switching is 2086 -- for further study. 2088 -- End of notifications. 2090 END 2092 9 References 2094 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 2095 "Multiprotocol Label Switching Architecture", 2096 Internet Draft , 2097 August 1999. 2099 [MPLSFW] Callon, R., Doolan, P., Feldman, N., Fredette, A., 2100 Swallow, G., and A. Viswanathan, "A Framework for 2101 Multiprotocol Label Switching", Internet Draft 2102 , September 1999. 2104 [CEM] Malis, A., Vogelsang, S., and Martini, L. "SONET/SDH 2106 Circuit Emulation Service Over MPLS (CEM) 2108 encapsulation", Internet Draft , February 2001. 2112 Danenberg et al Expires August 2001 38 2114 [TRANS] Martini et al, "Transport of Layer 2 Frames Over 2115 MPLS" , 2117 November 2000. 2119 [ENCAP] Martini et al, "Encapsulation Methods for Transport 2121 of Layer 2 Frames Over MPLS", , November 2000. 2124 [LSRMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T. 2125 "MPLS Label Switch Router Management Information 2126 Base Using SMIv2", draft-ietf-mpls-lsr-mib-07.txt, 2127 January 2001. 2129 [TEMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T. 2130 "MPLS Traffic Engineering Management Information 2131 Base Using SMIv2", , 2133 November 2000. 2135 [SONETMIB] Brown, T. and Tesink, K. "Definitions of Managed 2136 Objects for the SONET/SDH Interface Type", RFC 1595. 2138 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., 2139 Federokow, G., Li, T., and A. Conta, "MPLS Label 2140 Stack Encoding", Internet Draft , September 1999. 2143 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 2144 RFC 1700, October 1994. See also: 2145 http://www.isi.edu/in-notes/iana/assignments/smi- 2146 numbers 2148 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 2149 FAMILY NUMBERS,(http://www.isi.edu/in- 2150 notes/iana/assignements/address-family-numbers), 2151 for MIB see: 2152 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 2153 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An 2154 Architecture for Describing SNMP Management 2155 Frameworks", RFC 2271, January 1998. 2157 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 2158 Identification of Management Information for TCP/IP- 2160 based Internets", RFC 1155, May 1990. 2162 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 2163 Definitions", RFC 1212, March 1991. 2164 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use 2165 with the SNMP", RFC 1215, March 1991. 2166 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2167 "Message Processing and Dispatching for the Simple 2168 Network Management Protocol (SNMP)", RFC 2572, 2169 April 1999. 2171 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 2173 Danenberg et al Expires August 2001 39 2174 Model (USM) for version 3 of the Simple Network 2175 Management Protocol (SNMPv3)", RFC 2574, April 2176 1999. 2178 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 2179 Waldbusser, "Protocol Operations for Version 2 of 2180 the Simple Network Management Protocol (SNMPv2)", 2181 RFC 1905, January 1996. 2183 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2184 Applications", RFC 2573, April 1999. 2186 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2187 based Access Control Model (VACM) for the Simple 2188 Network Management Protocol (SNMP)", RFC 2575, 2189 April 1999. 2191 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2192 "Introduction to Version 3 of the Internet-standard 2193 Network Management Framework", RFC 2570, April 2194 1999. 2196 [SMIv2] Case, J., McCloghrie, K., Rose, M., and S. 2197 Waldbusser, "Structure of Management Information 2198 for Version 2 of the Simple Network Management 2199 Protocol (SNMPv2)", RFC 1902, January 1996. 2201 [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. 2202 Waldbusser, "Textual Conventions for Version 2 of 2203 the Simple Network Management Protocol (SNMPv2)", 2204 RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 2205 January 1996. 2207 [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. 2208 Waldbusser, "Conformance Statements for Version 2 2209 of the Simple Network Management Protocol 2210 (SNMPv2)", RFC 1904, January 1996. 2211 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2212 "Simple Network Management Protocol", RFC 1157, May 2213 1990. 2215 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 2216 Waldbusser, "Introduction to Community-based 2217 SNMPv2", RFC 1901, January 1996. 2219 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 2220 Waldbusser, "Transport Mappings for Version 2 of 2221 the Simple Network Management Protocol (SNMPv2)", 2222 RFC 1906, January 1996. 2224 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2225 "Message Processing and Dispatching for the Simple 2226 Network Management Protocol (SNMP)", RFC 2272, 2228 Danenberg et al Expires August 2001 40 2229 January 1998. 2231 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security 2232 Model (USM) for version 3 of the Simple Network 2233 Management Protocol (SNMPv3)", RFC 2574, April 2234 1999. 2236 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 2237 Waldbusser, "Protocol Operations for Version 2 of 2238 the Simple Network Management Protocol (SNMPv2)", 2239 RFC 1905, January 1996. 2241 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2242 Applications", RFC 2273, January 1998. 2244 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2245 based Access Control Model (VACM) for the Simple 2246 Network Management Protocol (SNMP)", RFC 2575, 2247 April 1999. 2249 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 2250 for the Internet Protocol", RFC 2401, November 2251 1998. 2253 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces 2254 Group MIB using SMIv2", RFC 2233, Nov. 1997 2256 [ATOMMIB] Tesink, K., "Definitions of Managed Objects for ATM 2257 Management", RFC 2515, Feb. 1999 2259 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 2260 Requirement Levels", BCP 14, RFC 2119, March 1997. 2262 10 Author's Addresses 2264 Dave Danenberg 2265 Litchfield Communications, Inc. 2266 76 Westbury Park Rd 2267 Princeton Building East 2268 Watertown, CT 06795 2269 Email: dave_danenberg@litchfieldcomm.com 2271 Thomas D. Nadeau 2272 Cisco Systems, Inc. 2273 250 Apollo Drive 2274 Chelmsford, MA 01824 2275 Email: tnadeau@cisco.com 2277 Andrew G. Malis 2278 Vivace Networks, Inc. 2279 2730 Orchard Parkway 2280 San Jose, CA 95134 2282 Danenberg et al Expires August 2001 41 2283 Email: Andy.Malis@vivacenetworks.com 2285 Scott C. Park 2286 Litchfield Communications, Inc. 2287 76 Westbury Park Rd 2288 Princeton Building East 2289 Watertown, CT 06795 2290 Email: scott_park@litchfieldcomm.com 2292 11 Full Copyright Statement 2294 "Copyright (C) The Internet Society (2001). All Rights Reserved. This 2296 document and translations of it may be copied and furnished to 2297 others, and derivative works that comment on or otherwise explain it 2298 or assist in its implementation may be prepared, copied, published 2299 and distributed, in whole or in part, without restriction of any 2300 kind, provided that the above copyright notice and this paragraph are 2302 included on all such copies and derivative works. However, this 2303 document itself may not be modified in any way, such as by removing 2304 the copyright notice or references to the Internet Society or other 2305 Internet organizations, except as needed for the purpose of 2306 developing Internet standards in which case the procedures for 2307 copyrights defined in the Internet Standards process must be 2308 followed, or as required to translate it into languages other than 2309 English. 2311 The limited permissions granted above are perpetual and will not be 2312 revoked by the Internet Society or its successors or assigns. 2314 This document and the information contained herein is provided on an 2315 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2316 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2317 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2318 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2319 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2321 Acknowledgement 2323 Funding for the RFC Editor function is currently provided by the 2324 Internet Society. 2326 Danenberg et al Expires August 2001 42