idnits 2.17.1 draft-ietf-pwe3-pw-mpls-mib-01.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 Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. (A line matching the expected section header was found, but with an unexpected indentation: ' 1 Abstract' ) ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2 Introduction' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 8 Security Considerations' ) ** 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.) ** There is 1 instance of too long lines in the document, the longest one being 12 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 297 has weird spacing: '...N |VCin inSeg...' == Line 301 has weird spacing: '...| inSeg outSe...' == Line 369 has weird spacing: '...rolWord notK...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 2003) is 7615 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'PW-MIB' on line 1441 looks like a reference -- Missing reference section? 'BCP14' on line 1485 looks like a reference -- Missing reference section? 'FRMWK' on line 1433 looks like a reference -- Missing reference section? 'ENCAP' on line 1429 looks like a reference -- Missing reference section? 'TRANS' on line 1425 looks like a reference -- Missing reference section? 'MPLSArch' on line 1415 looks like a reference -- Missing reference section? 'RFC2571' on line 1488 looks like a reference -- Missing reference section? 'RFC1155' on line 1492 looks like a reference -- Missing reference section? 'RFC1212' on line 1496 looks like a reference -- Missing reference section? 'RFC1215' on line 1499 looks like a reference -- Missing reference section? 'RFC2578' on line 1502 looks like a reference -- Missing reference section? 'RFC2579' on line 1507 looks like a reference -- Missing reference section? 'RFC2580' on line 1511 looks like a reference -- Missing reference section? 'RFC1157' on line 1515 looks like a reference -- Missing reference section? 'RFC1901' on line 1519 looks like a reference -- Missing reference section? 'RFC1906' on line 1525 looks like a reference -- Missing reference section? 'RFC2572' on line 1529 looks like a reference -- Missing reference section? 'RFC2574' on line 1534 looks like a reference -- Missing reference section? 'RFC1905' on line 1538 looks like a reference -- Missing reference section? 'RFC2573' on line 1543 looks like a reference -- Missing reference section? 'RFC2575' on line 1546 looks like a reference -- Missing reference section? 'RFC2570' on line 1550 looks like a reference -- Missing reference section? 'CEPMIB' on line 1444 looks like a reference -- Missing reference section? 'PWTC' on line 1452 looks like a reference -- Missing reference section? 'TEMIB' on line 1456 looks like a reference -- Missing reference section? 'LSRMIB' on line 1448 looks like a reference -- Missing reference section? 'CEP' on line 1421 looks like a reference -- Missing reference section? 'PWREQ' on line 1437 looks like a reference -- Missing reference section? 'LDPMIB' on line 1460 looks like a reference -- Missing reference section? 'LblStk' on line 1466 looks like a reference -- Missing reference section? 'Assigned' on line 1472 looks like a reference -- Missing reference section? 'IANAFamily' on line 1476 looks like a reference -- Missing reference section? 'IFMIB' on line 1482 looks like a reference Summary: 7 errors (**), 0 flaws (~~), 5 warnings (==), 35 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft David Zelig 3 Expires: December 2003 Corrigent Systems 5 A. Malis Thomas D. Nadeau 6 Vivace Networks, Inc. Cisco Systems, Inc. 8 Sharon Mantin Dave Danenberg 9 AxONLinks Litchfield Communications, Inc. 11 June 2003 13 Pseudo Wire (PW) over MPLS PSN Management Information Base 15 draft-ietf-pwe3-pw-mpls-mib-01.txt 17 Status of this Memo 19 This document is an Internet-Draft and is in full conformance 20 with all provisions of Section 10 of RFC2026. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six 28 months and may be updated, replaced, or obsoleted by other 29 documents at any time. It is inappropriate to use Internet-Drafts 30 as reference material or to cite them other than as "work in 31 progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 Copyright (C) The Internet Society (2001). All rights reserved. 40 1 Abstract 42 This memo defines an experimental portion of the Management 43 Information Base (MIB) for use with network management protocols in 44 the Internet community. In particular, it describes MIB module for 45 PW operation over Multi-Protocol Label Switching (MPLS) Label 46 Switch Router (LSR). 48 Management Information Base 50 Table of Contents 52 1 Abstract.......................................................1 53 2 Introduction...................................................2 54 3 Terminology....................................................3 55 4 The SNMP Management Framework..................................3 56 4.1 Object Definitions...........................................4 57 5 Feature Checklist..............................................5 58 6 MIB usage......................................................5 59 6.1 PW-MPLS-MIB usage............................................5 60 6.2 Example of MIB usage.........................................7 61 7 Object definitions............................................10 62 8 Security Considerations.......................................28 63 9 References....................................................28 64 10 Author's Addresses..........................................31 65 11 Full Copyright Statement....................................32 67 2 Introduction 69 This document describes a model for managing pseudo wire services 70 for transmission over different flavors of MPLS tunnels. The 71 general PW MIB [PW-MIB] defines the parameters global to the VC 72 regardless of underlying PSN and emulated service. Indicating PSN 73 type of MPLS in PW-MIB references this module. 75 This document describes the MIB objects that define pseudo wire 76 association to the MPLS PSN, in a way that is not specific to the 77 carried service. 79 Together, [TEMIB and LSRMIB], describe the modeling of an MPLS 80 Tunnel, and a Tunnel's underlying cross-connects. The defined MIB 81 support MPLS-TE PSN, Non TE MPLS PSN (an outer tunnel created by 82 LDP or manually), and MPLS VC only (no outer tunnel). 84 Some flavors of MPLS, such as carrying PW in MPLS in IP and MPLS in 85 GRE are not defined here, waiting to the WG documents that will 86 describe the exact MPLS functionality. It still for further study 87 whether this functionality will be treated in this MIB modules or 88 in another one specific to IP PSN. 90 VC level protection is for further study. Protection is currently 91 assumed at the outer tunnel level only, on bulk of VCs. Future 92 revision of this document will control the behavior of such 93 protection in more details. 95 Note: the current version is the same as the -00 draft. Update 96 of the MIB module will be available once the applicable 97 documents will be finalized by the WG. 99 Management Information Base 101 Conventions used in this document 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 105 this document are to be interpreted as described in RFC-2119 106 [BCP14]. 108 3 Terminology 110 This document uses terminology from the document describing the PW 111 framework [FRMWK], from [ENCAP] and [TRANS]. 113 The terms "Outbound" and "Inbound" in this MIB module are based on 114 the common practice in the MPLS standards, i.e. "outbound" are 115 toward the PSN. However, where these terms are used in an object 116 name, the object description clarifies the exact packet direction 117 to prevent confusion with these terms in other documents. 119 "PSN Tunnel" is a general term indicating a virtual connection 120 between the two PW edge devices. Each tunnel may potentially carry 121 multiple VCs inside. In the scope of this document, it is MPLS 122 tunnel. 124 This document uses terminology from the document describing the 125 MPLS architecture [MPLSArch] for MPLS PSN. A Label Switched Path 126 (LSP) is modeled as described in [LSRMIB and TEMIB] via a series of 127 cross-connects through 1 or more Label switch routers (LSR). 129 In MPLS PSN, a PW connection typically uses a VC (Virtual 130 Connection) Label within a Tunnel Label [TRANS]. Multiple PW VCs 131 each with a unique VC Label can share the same Tunnel. For PW 132 transport over MPLS, the Tunnel Label is known as the "outer" 133 Label, while the VC Label is known as the "inner" Label. An 134 exception to this is with adjacent LSRs or the use of PHP. In this 135 case, there is an option for PW VCs to connect directly without an 136 outer Label. 138 4 The SNMP Management Framework 140 The SNMP Management Framework presently consists of five major 141 components: 143 o An overall architecture, described in RFC 2571 [RFC2571]. 145 o Mechanisms for describing and naming objects and events for the 146 purpose of management. The first version of this Structure of 147 Management Information (SMI) is called SMIv1 and described in STD 148 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 149 [RFC1215]. The second version, called SMIv2, is described in STD 150 Management Information Base 152 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 153 2580 [RFC2580]. 155 o Message protocols for transferring management information. The 156 first version of the SNMP message protocol is called SNMPv1 and 157 described in STD 15, RFC 1157 [RFC1157]. A second version of the 158 SNMP message protocol, which is not an Internet standards track 159 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and 160 RFC 1906 [RFC1906]. The third version of the message protocol is 161 called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 162 [RFC2572] and RFC 2574 [RFC2574]. 164 o Protocol operations for accessing management information. The 165 first set of protocol operations and associated PDU formats is 166 described in STD 15, RFC 1157 [RFC1157]. A second set of protocol 167 operations and associated PDU formats is described in RFC 1905 168 [RFC1905]. 170 o A set of fundamental applications described in RFC 2573 [RFC2573] 171 and the view-based access control mechanism described in RFC 2575 172 [RFC2575]. 174 A more detailed introduction to the current SNMP Management 175 Framework can be found in RFC 2570 [RFC2570]. 177 Managed objects are accessed via a virtual information store, 178 termed the Management Information Base or MIB. Objects in the MIB 179 are defined using the mechanisms defined in the SMI. 181 This memo specifies a MIB module that is compliant to the SMIv2. A 182 MIB conforming to the SMIv1 can be produced through the appropriate 183 translations. The resulting translated MIB must be semantically 184 equivalent, except where objects or events are omitted because no 185 translation is possible (use of Counter64). Some machine readable 186 information in SMIv2 will be converted into textual descriptions in 187 SMIv1 during the translation process. However, this loss of 188 machine readable information is not considered to change the 189 semantics of the MIB. 191 4.1 Object Definitions 193 Managed objects are accessed via a virtual information store, 194 termed the Management Information Base or MIB. Objects in the MIB 195 are defined using the subset of Abstract Syntax Notation One 196 (ASN.1) defined in the SMI. In particular, an OBJECT IDENTIFIER, an 197 administratively assigned name, names each object type. The object 198 type together with an object instance serves to uniquely identify a 199 specific instantiation of the object. For human convenience, we 200 often use a textual string, termed the descriptor, to also refer to 201 the object type. 203 Management Information Base 205 5 Feature Checklist 207 The PW MPLS MIB (PW-MPLS-MIB) is designed to satisfy the following 208 requirements and constraints: 210 - The MIB supports both manually configured and signaled VCs. 212 - The MIB supports point-to-point PW connections. 214 - The MIB enables the use of any emulated service. 216 - The MIB supports MPLS-TE outer tunnel, Non TE MPLS outer tunnel 217 (an outer tunnel signaled by LDP or set-up manually), and no 218 outer tunnel (where the VC label is the only label in the 219 incoming MPLS stack). 221 - The MIB enables both strict and loose incoming VC lookup. In 222 strict mode, only VC carried inside known in advance tunnels or 223 interfaces are accepted. The methods of the association 224 knowledge are out of the scope of this document. 226 6 MIB usage 228 The MIB structure for defining a PW service is composed from three 229 types of modules. 231 The first type is the PW-MIB module [PW-MIB], which configures 232 general parameters of the VC that are common to all types of 233 emulated services and PSNs. 235 The second type of module is per PSN module. There is a different 236 module for each type of PSN. This document defines the MIB module 237 for MPLS (PW-MPLS-MIB). 239 The third type of module is service-specific module, which is 240 emulated signal type dependent. These modules are defined in other 241 documents; see for example [CEPMIB]. 243 [PWTC] defines some of the object types used in these modules. 245 6.1 PW-MPLS-MIB usage 247 - The VC table (pwVcTable) in [PW-MIB] is used for all VC types 248 (ATM, FR, Ethernet, SONET, etc.). This table contains high level 249 generic parameters related to the VC creation. A row is created by 250 the operator for each PW service. 252 - If the PSN type in pwVcTable is MPLS, the agent creates a row in 253 the MPLS specific parameters table (pwMplsVcTable) in PW-MPLS-MIB, 254 Management Information Base 256 which contain MPLS specific parameters such as EXP bits handling 257 and outer tunnel selection. 259 - A row is created by the agent in the MPLS outbound tunnels table 260 (pwVcMplsOutboundTable), which associates the VC to one or more 261 (in a case of backup tunnels) MPLS tunnels. This table simply 262 associates the VC with the entries at the relevant MPLS MIBs. 263 Additional rows in this table may be created manually, if more 264 than one outer tunnel is required (for example for protection 265 purposes). 267 - The MPLS inbound tunnel table (pwVcMplsInboundTable) associates 268 the VC to the incoming tunnel. This (optional) table can be used 269 for restricting the packet reception for a specific PW from pre- 270 defined tunnels, bringing better security and better miss- 271 configuration error immunity. 273 - The MPLS tunnels mapping tabled (pwMplsTeMappingTable and 274 pwMplsNonTeMappingTable) associate the tunnel and the VC label to 275 the VC index. This table is used for easy lookup process when 276 searching VC information. 278 The relation to the MPLS network is by configuration of the edge 279 LSR only - that is to say, the LSR providing the PW function. Since 280 Tunnels are uni-directional, a pair of tunnels must exist (one for 281 inbound, one for outbound). The following graphic depicts a VC that 282 originates and terminates at LSR-M. It uses LSPs A and B formed by 283 Tunnels Ax and Bx continuing through LSR-N to LSR-P. The 284 concatenations of Tunnels create the LSPs. Note: 'X' denotes a 285 Tunnel's cross-connect. 287 Management Information Base 289 LSP-A 290 <- - - - - - - - - - - - - - - - - - - - - - - - - - - - 292 +---- (edge) LSR-M ---+ +--------- LSR-N ---------+ + LSR-P 293 |---+ | | | | 294 | | Tunnel | | Tunnel | | 295 + | A1 (M<-N) +----+ +----+ A2 (M<-P) +----+ +----+ 296 | | <------| | | |<--------------| | | | 297 <-->| N |VCin inSeg |MPLS| |MPLS| outSeg inSeg |MPLS| |MPLS| 298 N S | | <---X<-----| IF | | IF |<------X<------| IF | | IF | 299 A E | S | | |<-->| | | |<-->| | | 300 T R | | --->X----->| | | |------>X------>| | | | 301 I V | P |VCout outSeg| | | | inSeg outSeg | | | | 302 V I | | ------>| | | |-------------->| | | | 303 E C + | Tunnel +----+ +----+ Tunnel +----+ +----+ 304 E |---+ B1 (M->N) | | B2 (M->P) | | 305 | | | | | 306 +---------------------+ +-------------------------+ +----- 308 - - - - - - - - - - - - - - - - - - - - - - - - - - - -> 309 LSP-B 311 The PW-MPLS-MIB supports three options for MPLS network: 313 - In the MPLS-TE case, Tunnel A1 and B1 are created via the MPLS-TE 314 MIB [TEMIB]. The tunnels are associated to the VC by the (4) 315 indexes that uniquely identify the Tunnel at the TE-MIB. 317 - In the Non TE case, Tunnel A1 and B1 are either manually 318 configured or set up with LDP. The tunnels are associated to the VC 319 by the XC index in the MPLS-LSR-MIB [LSRMIB]. 321 - In the VC only case, there is no outer Tunnel on top of the VC 322 label. This case is useful in case of adjacent PE (see [TRANS]) or 323 when LSR-N acts as PHP for the outer tunnel label. In this case, 324 Association is done directly to the physical interfaces in the PW- 325 MPLS-MIB tables. 327 A combination of MPLS-TE outer tunnel(s) and LDP outer tunnel for 328 the same VC is allowed by creating the rows with the same VcIndex 329 with different MPLS tunnel indexes types. 331 6.2 Example of MIB usage 333 In this section we provide an example of using the MIB objects for 334 setting up a VC over MPLS. While this example is not meant to 335 illustrate every permutation of the MIB, it is intended as an aid 336 to understanding some of the key concepts. It is meant to be read 337 after going through the MIB itself. 339 Management Information Base 341 In this example a PW service for CEP is configured over an MPLS-TE 342 tunnel. It uses LDP as in [TRANS] for service set-up. 344 In PW-MIB: 346 In pwVcTable: 347 { 348 pwVcIndex 5, 350 pwVcType cep, 351 pwVcOwner maintenanceProtocol, 352 pwVcPsnType mpls, 353 pwVcSetUpPriority 0, 354 pwVcHoldingPriority 0, 355 pwVcInboundMode loose, 357 pwVcPeerAddrType ipv4(2), 358 pwVcPeerAddr 1.4.3.2, -- In this case equal to the 359 -- peer tunnel IP address 360 pwVcID 10, 361 pwVcLocalGroupID 12, 363 pwVcControlWord false, -- Control word not to be sent 364 pwVcLocalIfMtu 0, -- Do not send ifMtu parameter 365 pwVcLocalIfString false, -- Do not signal if string 367 pwVcRemoteGroupID 0xFFFF, -- Will be received by 368 -- maintenance protocol 369 pwVcRemoteControlWord notKnownYet, 370 pwVcRemoteIfMtu 0, 371 pwVcRemoteIfString "", 373 pwVcOutboundVcLabel 0xFFFF, -- Will be received by 374 -- maintenance protocol 375 pwVcInboundVcLabel 0xFFFF, -- Will be set by signaling 377 pwVcName "Example of CEP VC", 378 pwVcDescr "", 379 .. 381 pwVcAdminStatus up, 382 .. 384 Management Information Base 386 The operator now create a row in pwVcMplsTable based on the 387 VcIndex, that is configured with MPLS specific values: 389 In pwVcMplsTable: 390 { 391 pwVcMplsMplsType mplsTe, 392 pwVcMplsExpBitsMode outerTunnel, 393 pwVcMplsExpBits 0, 394 pwVcMplsTtl 2, 395 pwVcMplsLocalLdpID 1.2.3.4.0.0 -- Global label space 396 pwVcMplsLocalLdpEntityID 0, 397 pwVcMplsPeerLdpID 0, -- Not known yet 398 ... 399 } 401 The operator now associates the VC with an outgoing TE tunnel: 403 In pwVcMplsOutboundTable: 405 { 406 pwVcMplsOutboundIndex 0, -- The first row 407 --for this VCIndex. 408 pwVcMplsOutBoundLsrXcIndex 0, -- MPLS-TE 409 pwVcMplsOutboundTunnelIndex 500, 410 pwVcMplsOutboundTunnelInstance 0, 411 pwVcMplsOutboundTunnelLclLSR 1.2.3.4, -- Always 412 -- the LSR ID of the current node. 413 pwVcMplsOutboundTunnelPeerLSR 1.4.3.2 414 pwVcMplsOutboundIfIndex 0, -- MPLS-TE 416 .. 417 } 419 pwVcMplsInboundTable is not used because loose LDP set-up is used. 421 pwVcMplsTeMappingTable entry will be created by the agent once the 422 outbound table is configured and will enable easy lookup for the 423 VcIndex from knowledge of the outer tunnel indexes. 425 Management Information Base 427 7 Object definitions 429 PW-MPLS-MIB DEFINITIONS ::= BEGIN 431 IMPORTS 432 MODULE-IDENTITY, OBJECT-TYPE, 433 experimental, Unsigned32 434 FROM SNMPv2-SMI 436 MODULE-COMPLIANCE, OBJECT-GROUP 437 FROM SNMPv2-CONF 439 RowStatus, StorageType 440 FROM SNMPv2-TC 442 InterfaceIndexOrZero 443 FROM IF-MIB 445 MplsTunnelIndex, MplsTunnelInstanceIndex, 446 MplsLdpIdentifier, MplsLsrIdentifier 447 FROM MPLS-TC-MIB 449 PwVcIndexType 450 FROM PW-TC-MIB 452 pwVcIndex 453 FROM PW-MIB 455 ; 457 pwVcMplsMIB MODULE-IDENTITY 458 LAST-UPDATED "200206021200Z" -- 02 June 2002 12:00:00 EST 459 ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working 460 Group" 461 CONTACT-INFO 462 " 463 David Zelig 464 Postal: Corrigent Systems 465 126, Yigal Alon St. 466 Tel Aviv, ISRAEL 467 Phone: +972-3-6945273 468 E-mail: davidz@corrigent.com 470 Thomas D. Nadeau 471 Postal: Cisco Systems, Inc. 472 250 Apollo Drive 473 Chelmsford, MA 01824 474 Tel: +1-978-497-3051 475 Email: tnadeau@cisco.com 477 Dave Danenberg 478 Management Information Base 480 Postal: Litchfield Communications, Inc. 481 76 Westbury Park Rd 482 Princeton Building East 483 Watertown, CT 06795 484 Tel: +1-860-945-1573 x3180 485 Email: dave_danenberg@litchfieldcomm.com 487 Sharon Mantin 488 Postal: AxONLink (Israel) Ltd 489 9 Bareket St. 490 Petah Tikva 49517, Israel 491 Tel: +972-3-9263972 492 Email: sharon.mantin@axonlink.com 494 The PWE3 Working Group (email distribution pwe3@ietf.org) " 496 DESCRIPTION 497 "This MIB complements the PW-MIB for PW operation over MPLS. 498 " 500 -- Revision history. 501 REVISION 502 "200206021200Z" -- 02 June 2002 12:00:00 EST 503 DESCRIPTION 504 "Draft-ietf-pwe3-pw-mpls-mib-00 version. Changes from 505 previous version: 506 1) Spliting the mapping table into two tables, one for 507 Non TE application and one for TE application. 508 2) Object types alignment with MPLS MIBs. 510 " 511 REVISION 512 "200201291200Z" -- 29 January 2002 12:00:00 EST 513 DESCRIPTION 514 "Changes from previous version: 515 1) Add LDP entity association. 516 2) Clarify inbound/outbound directions. 517 3) Simplify indexing of outbound and inbound tables 518 and providing get next variables. 519 " 520 REVISION 521 "200107111200Z" -- 7 November 2001 12:00:00 EST 522 DESCRIPTION 523 "Changes from previous version: 524 1) Remove Vc instance from table indexing. 525 2) Update descriptions of indexing and protection. 526 3) Remove the need for MPLS-LSR in case of VC only. 527 4) Change pwVcMplsMplsType to BITS in order to enable 528 multiple types of outer tunnel. 529 5) Add ifindex to outer tunnel tables to support vcOnly 530 option. 532 Management Information Base 534 6) change naming of outbound, inbound and mapping tables to 535 reflect addition of VC only port ifindexes. 536 7) Adapt order of items in mapping table to SNMP convention. 537 " 538 REVISION 539 "200107111200Z" -- July 11 2001 12:00:00 EST 540 DESCRIPTION 541 "draft-zelig-pw-mib-00.txt - initial version" 543 ::= { experimental xxx } -- To be assigned by IANA 545 -- Top-level components of this MIB. 547 -- Traps 548 pwVcMplsNotifications OBJECT IDENTIFIER 549 ::= { pwVcMplsMIB 0 } 550 pwVcMplsNotifyPrefix OBJECT IDENTIFIER 551 ::= { pwVcMplsNotifications 0 } 552 -- Tables, Scalars 553 pwVcMplsObjects OBJECT IDENTIFIER 554 ::= { pwVcMplsMIB 1 } 556 -- Conformance 557 pwVcMplsConformance OBJECT IDENTIFIER 558 ::= { pwVcMplsMIB 2 } 560 -- PW VC MPLS table 562 pwVcMplsTable OBJECT-TYPE 563 SYNTAX SEQUENCE OF PwVcMplsEntry 564 MAX-ACCESS not-accessible 565 STATUS current 566 DESCRIPTION 567 "This table specifies information for VC to be carried over 568 MPLS PSN." 569 ::= { pwVcMplsObjects 1 } 571 pwVcMplsEntry OBJECT-TYPE 572 SYNTAX PwVcMplsEntry 573 MAX-ACCESS not-accessible 574 STATUS current 575 DESCRIPTION 576 "A row in this table represents parameters specific to MPLS 577 PSN for a pseudo wire connection (VC). The row is created 578 automatically by the local agent if the pwVcPsnType is 579 MPLS. It is indexed by pwVcIndex, which uniquely 580 identifying a singular connection. 581 " 583 INDEX { pwVcIndex } 584 Management Information Base 586 ::= { pwVcMplsTable 1 } 588 PwVcMplsEntry ::= SEQUENCE { 589 pwVcMplsMplsType BITS, 590 pwVcMplsExpBitsMode INTEGER, 591 pwVcMplsExpBits Unsigned32, 592 pwVcMplsTtl Unsigned32, 593 pwVcMplsLocalLdpID MplsLdpIdentifier, 594 pwVcMplsLocalLdpEntityID Unsigned32, 595 pwVcMplsPeerLdpID MplsLdpIdentifier, 596 pwVcMplsStorageType StorageType 597 } 599 pwVcMplsMplsType OBJECT-TYPE 600 SYNTAX BITS { 601 mplsTe (0), 602 mplsNonTe (1), 603 vcOnly (2) 604 } 605 MAX-ACCESS read-write 606 STATUS current 607 DESCRIPTION 608 "Set by the operator to indicate the outer tunnel types, if 609 exists. mplsTe is used if the outer tunnel was set-up by 610 MPLS-TE, and mplsNonTe is used the outer tunnel was set up 611 by LDP or manually. Combination of mplsTe and mplsNonTe 612 may exist in case of outer tunnel protection. 613 vcOnly is used if there is no outer tunnel label. vcOnly 614 cannot be combined with mplsNonTe or mplsTe." 615 ::= { pwVcMplsEntry 1 } 617 pwVcMplsExpBitsMode OBJECT-TYPE 618 SYNTAX INTEGER { 619 outerTunnel (1), 620 specifiedValue (2), 621 serviceDependant (3) 622 } 624 MAX-ACCESS read-write 625 STATUS current 626 DESCRIPTION 627 "Set by the operator to indicate the way the VC shim label 628 EXP bits are to be determined. The value of outerTunnel(1) 629 is used where there is an outer tunnel - pwVcMplsMplsType 630 is mplsTe or mplsNonTe. Note that in this case there is no 631 need to mark the VC label with the EXP bits since the VC 632 label is not visible to the intermediate nodes. 633 If there is no outer tunnel, specifiedValue(2) indicate 634 that the value is specified by pwVcMplsExpBits, and 635 serviceDependant(3) indicate that the EXP bits are setup 636 Management Information Base 638 based on a rule specified in the emulated service specific 639 tables, for example when the EXP bits are a function of 640 802.1p marking for Ethernet emulated service." 641 REFERENCE 642 "martini et al, " 643 DEFVAL { outerTunnel } 644 ::= { pwVcMplsEntry 2 } 646 pwVcMplsExpBits OBJECT-TYPE 647 SYNTAX Unsigned32 (0..7) 648 MAX-ACCESS read-write 649 STATUS current 650 DESCRIPTION 651 "Set by the operator to indicate the MPLS EXP bits to be 652 used on the VC shim label if pwVcMplsExpBitsMode is 653 specifiedValue(2), zero otherwise." 654 DEFVAL { 0 } 655 ::= { pwVcMplsEntry 3 } 657 pwVcMplsTtl OBJECT-TYPE 658 SYNTAX Unsigned32 (0..255) 659 MAX-ACCESS read-write 660 STATUS current 661 DESCRIPTION 662 "Set by the operator to indicate the VC TTL bits to be used 663 on the VC shim label." 664 REFERENCE 665 "martini et al, " 666 DEFVAL { 2 } 667 ::= { pwVcMplsEntry 4 } 669 pwVcMplsLocalLdpID OBJECT-TYPE 670 SYNTAX MplsLdpIdentifier 671 MAX-ACCESS read-write 672 STATUS current 673 DESCRIPTION 674 "The local LDP identifier of the LDP entity creating 675 this VC in the local node. As the VC labels are always 676 set from the per platform label space, the last two octets 677 in the LDP ID MUST be always both zeros." 678 REFERENCE 679 ", 680 . 681 " 682 ::= { pwVcMplsEntry 5 } 684 pwVcMplsLocalLdpEntityID OBJECT-TYPE 685 SYNTAX Unsigned32 686 MAX-ACCESS read-write 687 STATUS current 688 DESCRIPTION 689 Management Information Base 691 "The local LDP Entity index of the LDP entity to be used 692 for this VC on the local node. Should be set to all zeros 693 if not used." 694 REFERENCE 695 " 696 " 697 ::= { pwVcMplsEntry 6 } 699 pwVcMplsPeerLdpID OBJECT-TYPE 700 SYNTAX MplsLdpIdentifier 701 MAX-ACCESS read-only 702 STATUS current 703 DESCRIPTION 704 "The peer LDP identifier as identified from the LDP 705 session. Should be zero if not relevant or not known yet." 706 REFERENCE 707 ", 708 . 709 " 710 ::= { pwVcMplsEntry 7 } 712 pwVcMplsStorageType OBJECT-TYPE 713 SYNTAX StorageType 714 MAX-ACCESS read-write 715 STATUS current 716 DESCRIPTION 717 "This variable indicates the storage type for this row." 718 ::= { pwVcMplsEntry 8 } 720 -- End of PW MPLS VC table 722 -- Pseudo Wire VC MPLS Outbound Tunnel table 724 pwVcMplsOutboundIndexNext OBJECT-TYPE 725 SYNTAX Unsigned32 (0..4294967295) 726 MAX-ACCESS read-only 727 STATUS current 728 DESCRIPTION 729 "This object contains an appropriate value to 730 be used for pwVcMplsOutboundIndex when creating 731 entries in the pwVcMplsOutboundTable. The value 732 0 indicates that no unassigned entries are 733 available. To obtain the pwVcMplsOutboundIndex 734 value for a new entry, the manager issues a 735 management protocol retrieval operation to obtain 736 the current value of this object. After each 737 retrieval, the agent should modify the value to 738 the next unassigned index, however the agent MUST 739 NOT assume such retrieval will be done for each 740 row created." 741 ::= { pwVcMplsObjects 2 } 742 Management Information Base 744 pwVcMplsOutboundTable OBJECT-TYPE 745 SYNTAX SEQUENCE OF PwVcMplsOutboundEntry 746 MAX-ACCESS not-accessible 747 STATUS current 748 DESCRIPTION 749 "This table associates VCs using MPLS PSN with the outbound 750 MPLS tunnels (i.e. toward the PSN) or the physical 751 interface in case of VC only." 752 ::= { pwVcMplsObjects 3 } 754 pwVcMplsOutboundEntry OBJECT-TYPE 755 SYNTAX PwVcMplsOutboundEntry 756 MAX-ACCESS not-accessible 757 STATUS current 758 DESCRIPTION 759 "A row in this table represents a link between PW VC (that 760 require MPLS tunnels) and MPLS tunnel toward the PSN. 761 In the case of VC only, it associate the VC with the 762 interface that shall carry the VC. 763 This table is indexed by the pwVcIndex and an additional 764 index enabling multiple rows for the same VC index. 766 At least one entry is created in this table by the operator 767 for each PW VC that requires MPLS PSN. Note that the first 768 entry for each VC can be indexed by pwVcMplsOutboundIndex 769 equal zero without a need for retrieval of 770 pwVcMplsOutboundIndexNext. 772 This table points to the appropriate MPLS MIB. In the case 773 of MPLS-TE, the 4 variables relevant to the indexing of 774 a TE MPLS tunnel are set as in Srinivasan, et al, . 776 In case of Non-TE MPLS (an outer tunnel label assigned by 777 LDP or manually) the table points to the XC entry in the 778 LSR MIB as in Srinivasan, et al, . 779 In case of VC only (no outer tunnel) the ifIndex of the 780 port to carry the VC is configured. 782 Each VC may have multiple rows in this tables if protection 783 is available at the outer tunnel level, each row may be of 784 different type except for VC only, on which only rows with 785 ifIndex of the port are allowed. 786 " 788 INDEX { pwVcIndex, pwVcMplsOutboundIndex } 790 ::= { pwVcMplsOutboundTable 1 } 792 PwVcMplsOutboundEntry ::= SEQUENCE { 793 pwVcMplsOutboundIndex Unsigned32, 794 Management Information Base 796 pwVcMplsOutboundLsrXcIndex Unsigned32, 797 pwVcMplsOutboundTunnelIndex MplsTunnelIndex, 798 pwVcMplsOutboundTunnelInstance MplsTunnelInstanceIndex, 799 pwVcMplsOutboundTunnelLclLSR MplsLsrIdentifier, 800 pwVcMplsOutboundTunnelPeerLSR MplsLsrIdentifier, 801 pwVcMplsOutboundIfIndex InterfaceIndexOrZero, 802 pwVcMplsOutboundRowStatus RowStatus, 803 pwVcMplsOutboundStorageType StorageType 804 } 806 pwVcMplsOutboundIndex OBJECT-TYPE 807 SYNTAX Unsigned32 (0..4294967295) 808 MAX-ACCESS not-accessible 809 STATUS current 810 DESCRIPTION 811 "Arbitrary index for enabling multiple rows per VC in 812 this table. Next available free index can be retrieved 813 using pwVcMplsOutboundIndexNext. 814 " 815 ::= { pwVcMplsOutboundEntry 1 } 817 pwVcMplsOutboundLsrXcIndex OBJECT-TYPE 818 SYNTAX Unsigned32 819 MAX-ACCESS read-create 820 STATUS current 821 DESCRIPTION 822 "This object will be set by the operator. If the outer 823 label is defined in the MPL-LSR-MIB, i.e. set by LDP 824 or manually, this object points to the XC index 825 of the outer tunnel. Otherwise, it is set to zero." 826 ::= { pwVcMplsOutboundEntry 2 } 828 pwVcMplsOutboundTunnelIndex OBJECT-TYPE 829 SYNTAX MplsTunnelIndex 830 MAX-ACCESS read-create 831 STATUS current 832 DESCRIPTION 833 "Part of set of indexes for outbound tunnel in the case of 834 MPLS-TE outer tunnel, otherwise set to zero." 835 ::= { pwVcMplsOutboundEntry 3 } 837 pwVcMplsOutboundTunnelInstance OBJECT-TYPE 838 SYNTAX MplsTunnelInstanceIndex 839 MAX-ACCESS read-create 840 STATUS current 841 DESCRIPTION 842 "Part of set of indexes for outbound tunnel in the case of 843 MPLS-TE outer tunnel, otherwise set to zero." 844 ::= { pwVcMplsOutboundEntry 4 } 845 Management Information Base 847 pwVcMplsOutboundTunnelLclLSR OBJECT-TYPE 848 SYNTAX MplsLsrIdentifier 849 MAX-ACCESS read-create 850 STATUS current 851 DESCRIPTION 852 "Part of set of indexes for outbound tunnel in the case of 853 MPLS-TE outer tunnel, otherwise set to zero." 854 ::= { pwVcMplsOutboundEntry 5 } 856 pwVcMplsOutboundTunnelPeerLSR OBJECT-TYPE 857 SYNTAX MplsLsrIdentifier 858 MAX-ACCESS read-create 859 STATUS current 860 DESCRIPTION 861 "Part of set of indexes for outbound tunnel in the case of 862 MPLS-TE outer tunnel, otherwise set to zero." 863 ::= { pwVcMplsOutboundEntry 6 } 865 pwVcMplsOutboundIfIndex OBJECT-TYPE 866 SYNTAX InterfaceIndexOrZero 867 MAX-ACCESS read-create 868 STATUS current 869 DESCRIPTION 870 "In case of VC only (no outer tunnel), this object holds 871 the ifIndex of the outbound port, otherwise set to zero." 872 ::= { pwVcMplsOutboundEntry 7 } 874 pwVcMplsOutboundRowStatus OBJECT-TYPE 875 SYNTAX RowStatus 876 MAX-ACCESS read-create 877 STATUS current 878 DESCRIPTION 879 "For creating, modifying, and deleting this row." 880 ::= { pwVcMplsOutboundEntry 8 } 882 pwVcMplsOutboundStorageType OBJECT-TYPE 883 SYNTAX StorageType 884 MAX-ACCESS read-create 885 STATUS current 886 DESCRIPTION 887 "This variable indicates the storage type for this object." 888 ::= { pwVcMplsOutboundEntry 9 } 890 -- End of Pseudo Wire VC MPLS Outbound Tunnel table 892 -- Pseudo Wire VC MPLS Inbound Tunnel table 894 pwVcMplsInboundIndexNext OBJECT-TYPE 895 SYNTAX Unsigned32 (0..4294967295) 896 MAX-ACCESS read-only 897 Management Information Base 899 STATUS current 900 DESCRIPTION 901 "This object contains an appropriate value to 902 be used for pwVcMplsInboundIndex when creating 903 entries in the pwVcMplsInboundTable. The value 904 0 indicates that no unassigned entries are 905 available. To obtain the pwVcMplsInboundIndex 906 value for a new entry, the manager issues a 907 management protocol retrieval operation to obtain 908 the current value of this object. After each 909 retrieval, the agent should modify the value to 910 the next unassigned index, however the agent MUST 911 NOT assume such retrieval will be done for each 912 row created." 913 ::= { pwVcMplsObjects 4 } 915 pwVcMplsInboundTable OBJECT-TYPE 916 SYNTAX SEQUENCE OF PwVcMplsInboundEntry 917 MAX-ACCESS not-accessible 918 STATUS current 919 DESCRIPTION 920 "This table associates VCs using MPLS PSN with the inbound 921 MPLS tunnels (i.e. for packets coming from the PSN), 922 if such association is desired (mainly for security 923 reasons)." 924 ::= { pwVcMplsObjects 5 } 926 pwVcMplsInboundEntry OBJECT-TYPE 927 SYNTAX PwVcMplsInboundEntry 928 MAX-ACCESS not-accessible 929 STATUS current 930 DESCRIPTION 931 "A row in this table represents a link between PW VCs (that 932 require MPLS tunnels) and MPLS tunnel for packets arriving 933 from the PSN. 934 This table is indexed by the set of indexes used to 935 identify the VC - pwVcIndex and an additional 936 index enabling multiple rows for the same VC index. 938 Note that the first entry for each VC can be indexed by 939 pwVcMplsOutboundIndex equal zero without a need for 940 retrieval of pwVcMplsInboundIndexNext. 942 An entry is created in this table either automatically by 943 the local agent or created manually by the operator in 944 cases that strict mode is required. 946 Note that the control messages contain VC ID and VC type, 947 which together with the remote IP address identify the 948 pwVcIndex in the local node. 950 Management Information Base 952 This table points to the appropriate MPLS MIB. In the case 953 of MPLS-TE, the 4 variables relevant to the indexing of a 954 TE MPLS tunnel are set as in Srinivasan, et al, . 957 In case of non-TE MPLS tunnel (an outer tunnel label 958 assigned by LDP or manually) the table points to the XC 959 entry in the MPLS-LSR-MIB as in Srinivasan, et al, . 962 Each VC may have multiple rows in this tables if protection 963 is available at the outer tunnel level, each row may be of 964 different type except for VC only, on which only rows with 965 ifIndex of the port are allowed. 966 " 968 INDEX { pwVcIndex, pwVcMplsInboundIndex } 970 ::= { pwVcMplsInboundTable 1 } 972 PwVcMplsInboundEntry ::= SEQUENCE { 973 pwVcMplsInboundIndex Unsigned32, 974 pwVcMplsInboundLsrXcIndex Unsigned32, 975 pwVcMplsInboundTunnelIndex MplsTunnelIndex, 976 pwVcMplsInboundTunnelInstance MplsTunnelInstanceIndex, 977 pwVcMplsInboundTunnelLclLSR MplsLsrIdentifier, 978 pwVcMplsInboundTunnelPeerLSR MplsLsrIdentifier, 979 pwVcMplsInboundIfIndex InterfaceIndexOrZero, 980 pwVcMplsInboundRowStatus RowStatus, 981 pwVcMplsInboundStorageType StorageType 982 } 984 pwVcMplsInboundIndex OBJECT-TYPE 985 SYNTAX Unsigned32 (0..4294967295) 986 MAX-ACCESS not-accessible 987 STATUS current 988 DESCRIPTION 989 "Arbitrary index for enabling multiple rows per VC in 990 this table. Next available free index can be retrieved 991 using pwVcMplsInboundIndexNext. 992 " 993 ::= { pwVcMplsInboundEntry 1 } 995 pwVcMplsInboundLsrXcIndex OBJECT-TYPE 996 SYNTAX Unsigned32 997 MAX-ACCESS read-create 998 STATUS current 999 DESCRIPTION 1000 "If the outer label is defined in the MPL-LSR-MIB, i.e. set 1001 by LDP or manually, this object points to the XC index 1002 of the outer tunnel. Otherwise, it is set to zero." 1003 Management Information Base 1005 ::= { pwVcMplsInboundEntry 2 } 1007 pwVcMplsInboundTunnelIndex OBJECT-TYPE 1008 SYNTAX MplsTunnelIndex 1009 MAX-ACCESS read-create 1010 STATUS current 1011 DESCRIPTION 1012 "Part of set of indexes for outbound tunnel in the case of 1013 MPLS-TE outer tunnel, otherwise set to zero." 1014 ::= { pwVcMplsInboundEntry 3 } 1016 pwVcMplsInboundTunnelInstance OBJECT-TYPE 1017 SYNTAX MplsTunnelInstanceIndex 1018 MAX-ACCESS read-create 1019 STATUS current 1020 DESCRIPTION 1021 "Part of set of indexes for outbound tunnel in the case of 1022 MPLS-TE outer tunnel, otherwise set to zero." 1023 ::= { pwVcMplsInboundEntry 4 } 1025 pwVcMplsInboundTunnelLclLSR OBJECT-TYPE 1026 SYNTAX MplsLsrIdentifier 1027 MAX-ACCESS read-create 1028 STATUS current 1029 DESCRIPTION 1030 "Part of set of indexes for outbound tunnel in the case of 1031 MPLS-TE outer tunnel, otherwise set to zero." 1032 ::= { pwVcMplsInboundEntry 5 } 1034 pwVcMplsInboundTunnelPeerLSR OBJECT-TYPE 1035 SYNTAX MplsLsrIdentifier 1036 MAX-ACCESS read-create 1037 STATUS current 1038 DESCRIPTION 1039 "Part of set of indexes for outbound tunnel in the case of 1040 MPLS-TE outer tunnel, otherwise set to zero." 1041 ::= { pwVcMplsInboundEntry 6 } 1043 pwVcMplsInboundIfIndex OBJECT-TYPE 1044 SYNTAX InterfaceIndexOrZero 1045 MAX-ACCESS read-create 1046 STATUS current 1047 DESCRIPTION 1048 "In case of VC only (no outer tunnel), this object holds the 1049 ifIndex of the inbound port, otherwise set to zero." 1050 ::= { pwVcMplsInboundEntry 7 } 1052 pwVcMplsInboundRowStatus OBJECT-TYPE 1053 SYNTAX RowStatus 1054 MAX-ACCESS read-create 1055 Management Information Base 1057 STATUS current 1058 DESCRIPTION 1059 "For creating, modifying, and deleting this row." 1060 ::= { pwVcMplsInboundEntry 8 } 1062 pwVcMplsInboundStorageType OBJECT-TYPE 1063 SYNTAX StorageType 1064 MAX-ACCESS read-create 1065 STATUS current 1066 DESCRIPTION 1067 "This variable indicates the storage type for this row." 1068 ::= { pwVcMplsInboundEntry 9 } 1070 -- End of Pseudo Wire VC MPLS Inbound Tunnel table 1072 -- MPLS to VC Mapping Tables. 1074 pwVcMplsNonTeMappingTable OBJECT-TYPE 1075 SYNTAX SEQUENCE OF PwVcMplsNonTeMappingEntry 1076 MAX-ACCESS not-accessible 1077 STATUS current 1078 DESCRIPTION 1079 "This table maps an inbound/outbound Tunnel to a VC in non- 1080 TE applications." 1081 ::= { pwVcMplsObjects 6 } 1083 pwVcMplsNonTeMappingEntry OBJECT-TYPE 1084 SYNTAX PwVcMplsNonTeMappingEntry 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "A row in this table represents the association 1089 between the PW VC and it's non TE MPLS outer Tunnel 1090 it's physical interface if there is no outer tunnel 1091 (VC only). 1093 An application can use this table to quickly retrieve the 1094 PW carried over specific non-TE MPLS outer tunnel or 1095 physical interface. 1097 The table in indexed by the XC index for MPLS Non-TE 1098 tunnel, or ifIndex of the port in VC only case, the 1099 direction of the VC in the specific entry and the VCIndex. 1101 The same table is used in both inbound and outbound 1102 directions, but in a different row for each direction. If 1103 the inbound association is not known, no rows should exist 1104 for it. 1106 Rows are created by the local agent when all the 1107 Management Information Base 1109 association data is available for display." 1111 INDEX { pwVcMplsNonTeMappingTunnelDirection, 1112 pwVcMplsNonTeMappingXcTunnelIndex, 1113 pwVcMplsNonTeMappingIfIndex, 1114 pwVcMplsNonTeMappingVcIndex } 1116 ::= { pwVcMplsNonTeMappingTable 1 } 1118 PwVcMplsNonTeMappingEntry ::= SEQUENCE { 1119 pwVcMplsNonTeMappingTunnelDirection INTEGER, 1120 pwVcMplsNonTeMappingXcTunnelIndex Unsigned32, 1121 pwVcMplsNonTeMappingIfIndex InterfaceIndexOrZero, 1122 pwVcMplsNonTeMappingVcIndex PwVcIndexType 1123 } 1125 pwVcMplsNonTeMappingTunnelDirection OBJECT-TYPE 1126 SYNTAX INTEGER { 1127 outbound (1), -- From the PE toward the PSN 1128 inbound (2) -- From the PSN into the PE 1129 } 1130 MAX-ACCESS not-accessible 1131 STATUS current 1132 DESCRIPTION 1133 "Identifies if the row represent an outbound or inbound 1134 mapping." 1135 ::= { pwVcMplsNonTeMappingEntry 1 } 1137 pwVcMplsNonTeMappingXcTunnelIndex OBJECT-TYPE 1138 SYNTAX Unsigned32 (0..4294967295) 1139 MAX-ACCESS not-accessible 1140 STATUS current 1141 DESCRIPTION 1142 "Index for the conceptual XC row identifying Tunnel to VC 1143 mappings when the outer tunnel is created by the MPLS-LSR- 1144 MIB, Zero otherwise." 1145 ::= { pwVcMplsNonTeMappingEntry 2 } 1147 pwVcMplsNonTeMappingIfIndex OBJECT-TYPE 1148 SYNTAX InterfaceIndexOrZero 1149 MAX-ACCESS not-accessible 1150 STATUS current 1151 DESCRIPTION 1152 "Identify the port on which the VC is carried for VC only 1153 case." 1154 ::= { pwVcMplsNonTeMappingEntry 3 } 1156 pwVcMplsNonTeMappingVcIndex OBJECT-TYPE 1157 SYNTAX PwVcIndexType 1158 MAX-ACCESS read-only 1159 Management Information Base 1161 STATUS current 1162 DESCRIPTION 1163 "The value that represent the VC in the pwVcTable." 1164 ::= { pwVcMplsNonTeMappingEntry 4 } 1166 -- End of Non-TE MPLS Tunnel to VC Mapping Table 1168 pwVcMplsTeMappingTable OBJECT-TYPE 1169 SYNTAX SEQUENCE OF PwVcMplsTeMappingEntry 1170 MAX-ACCESS not-accessible 1171 STATUS current 1172 DESCRIPTION 1173 "This table maps an inbound/outbound Tunnel to a VC in 1174 MPLS-TE applications." 1175 ::= { pwVcMplsObjects 7 } 1177 pwVcMplsTeMappingEntry OBJECT-TYPE 1178 SYNTAX PwVcMplsTeMappingEntry 1179 MAX-ACCESS not-accessible 1180 STATUS current 1181 DESCRIPTION 1182 "A row in this table represents the association 1183 between a PW VC and it's MPLS-TE outer Tunnel. 1185 An application can use this table to quickly retrieve the 1186 PW carried over specific TE MPLS outer tunnel. 1188 The table in indexed by the 4 indexes of a TE tunnel, 1189 the direction of the VC specific entry and the VcIndex. 1191 The same table is used in both inbound and outbound 1192 directions, a different row for each direction. If the 1193 inbound association is not known, no rows should exist for 1194 it. 1196 Rows are created by the local agent when all the 1197 association data is available for display." 1199 INDEX { pwVcMplsTeMappingTunnelDirection, 1200 pwVcMplsTeMappingTunnelIndex, 1201 pwVcMplsTeMappingTunnelInstance, 1202 pwVcMplsTeMappingTunnelPeerLsrID, 1203 pwVcMplsTeMappingTunnelLocalLsrID, 1204 pwVcMplsTeMappingVcIndex } 1206 ::= { pwVcMplsTeMappingTable 1 } 1208 PwVcMplsTeMappingEntry ::= SEQUENCE { 1209 pwVcMplsTeMappingTunnelDirection INTEGER, 1210 pwVcMplsTeMappingTunnelIndex MplsTunnelIndex, 1211 pwVcMplsTeMappingTunnelInstance MplsTunnelInstanceIndex, 1212 Management Information Base 1214 pwVcMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier, 1215 pwVcMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier, 1216 pwVcMplsTeMappingVcIndex PwVcIndexType 1217 } 1219 pwVcMplsTeMappingTunnelDirection OBJECT-TYPE 1220 SYNTAX INTEGER { 1221 outbound (1), -- From the PE toward the PSN 1222 inbound (2) -- From the PSN into the PE 1223 } 1224 MAX-ACCESS not-accessible 1225 STATUS current 1226 DESCRIPTION 1227 "Identifies if the row represent an outbound or inbound 1228 mapping." 1229 ::= { pwVcMplsTeMappingEntry 1 } 1231 pwVcMplsTeMappingTunnelIndex OBJECT-TYPE 1232 SYNTAX MplsTunnelIndex 1233 MAX-ACCESS not-accessible 1234 STATUS current 1235 DESCRIPTION 1236 "Primary index for the conceptual row identifying the 1237 MPLS-TE tunnel." 1238 ::= { pwVcMplsTeMappingEntry 2 } 1240 pwVcMplsTeMappingTunnelInstance OBJECT-TYPE 1241 SYNTAX MplsTunnelInstanceIndex 1242 MAX-ACCESS not-accessible 1243 STATUS current 1244 DESCRIPTION 1245 "Identifies an instance of the MPLS-TE tunnel." 1246 ::= { pwVcMplsTeMappingEntry 3 } 1248 pwVcMplsTeMappingTunnelPeerLsrID OBJECT-TYPE 1249 SYNTAX MplsLsrIdentifier 1250 MAX-ACCESS not-accessible 1251 STATUS current 1252 DESCRIPTION 1253 "Identifies an Peer LSR when the outer tunnel is MPLS-TE 1254 based." 1255 ::= { pwVcMplsTeMappingEntry 4 } 1257 pwVcMplsTeMappingTunnelLocalLsrID OBJECT-TYPE 1258 SYNTAX MplsLsrIdentifier 1259 MAX-ACCESS not-accessible 1260 STATUS current 1261 DESCRIPTION 1262 "Identifies the local LSR." 1263 ::= { pwVcMplsTeMappingEntry 5 } 1264 Management Information Base 1266 pwVcMplsTeMappingVcIndex OBJECT-TYPE 1267 SYNTAX PwVcIndexType 1268 MAX-ACCESS read-only 1269 STATUS current 1270 DESCRIPTION 1271 "The value that represent the VC in the pwVcTable." 1272 ::= { pwVcMplsTeMappingEntry 6 } 1274 -- End of TE MPLS Tunnel to VC Mapping Table 1276 -- Notifications - PW over MPLS - FFS 1277 -- End of notifications. 1279 -- conformance information 1281 -- Note: Conformance at the object access and values level is 1282 -- still FFS, therefore current conformance is defined at the 1283 -- object existence level only. 1285 pwVcMplsGroups OBJECT IDENTIFIER ::= { pwVcMplsConformance 1 } 1286 pwVcMplsCompliances OBJECT IDENTIFIER ::= { pwVcMplsConformance 2 } 1288 pwMplsModuleCompliance MODULE-COMPLIANCE 1289 STATUS current 1290 DESCRIPTION 1291 "The compliance statement for agent that support PW 1292 over MPLS PSN operation." 1294 MODULE -- this module 1295 MANDATORY-GROUPS { pwVcMplsGroup, 1296 pwVcMplsOutboundGroup, 1297 pwVcMplsMappingGroup 1298 } 1300 GROUP pwVcMplsInboundGroup 1301 DESCRIPTION 1302 "This group is mandatory for those PE that support PW 1303 over MPLS PSN." 1305 ::= { pwVcMplsCompliances 1 } 1307 -- Units of conformance. 1309 pwVcMplsGroup OBJECT-GROUP 1310 OBJECTS { 1311 pwVcMplsMplsType, 1312 pwVcMplsExpBitsMode, 1313 pwVcMplsExpBits, 1314 pwVcMplsTtl, 1315 Management Information Base 1317 pwVcMplsLocalLdpID, 1318 pwVcMplsLocalLdpEntityID, 1319 pwVcMplsPeerLdpID, 1320 pwVcMplsStorageType 1321 } 1323 STATUS current 1324 DESCRIPTION 1325 "Collection of objects needed for PW VC 1326 over MPLS PSN configuration." 1327 ::= { pwVcMplsGroups 1 } 1329 pwVcMplsOutboundGroup OBJECT-GROUP 1330 OBJECTS { 1331 pwVcMplsOutboundIndexNext, 1332 pwVcMplsOutboundLsrXcIndex, 1333 pwVcMplsOutboundTunnelIndex, 1334 pwVcMplsOutboundTunnelInstance, 1335 pwVcMplsOutboundTunnelLclLSR, 1336 pwVcMplsOutboundTunnelPeerLSR, 1337 pwVcMplsOutboundIfIndex, 1338 pwVcMplsOutboundRowStatus, 1339 pwVcMplsOutboundStorageType 1340 } 1342 STATUS current 1343 DESCRIPTION 1344 "Collection of objects needed for outbound association of 1345 VC and MPLS tunnel." 1346 ::= { pwVcMplsGroups 2 } 1348 pwVcMplsInboundGroup OBJECT-GROUP 1349 OBJECTS { 1350 pwVcMplsInboundIndexNext, 1351 pwVcMplsInboundLsrXcIndex, 1352 pwVcMplsInboundTunnelIndex, 1353 pwVcMplsInboundTunnelInstance, 1354 pwVcMplsInboundTunnelLclLSR, 1355 pwVcMplsInboundTunnelPeerLSR, 1356 pwVcMplsInboundIfIndex, 1357 pwVcMplsInboundRowStatus, 1358 pwVcMplsInboundStorageType 1359 } 1361 STATUS current 1362 DESCRIPTION 1363 "Collection of objects needed for inbound association of 1364 VC and MPLS tunnel. This group is mandatory if strict 1365 mode is implemented." 1366 Management Information Base 1368 ::= { pwVcMplsGroups 3 } 1370 pwVcMplsMappingGroup OBJECT-GROUP 1371 OBJECTS { 1372 pwVcMplsNonTeMappingVcIndex, 1373 pwVcMplsTeMappingVcIndex 1374 } 1376 STATUS current 1377 DESCRIPTION 1378 "Collection of objects used for mapping of tunnels and VC 1379 labels to VC index." 1380 ::= { pwVcMplsGroups 4 } 1382 END -- of PW-MPLS-MIB 1384 8 Security Considerations 1386 There are a number of management objects defined in this MIB that 1387 have a MAX-ACCESS clause of read-write and/or read-create. Such 1388 objects may be considered sensitive or vulnerable in some network 1389 environments. The support for SET operations in a non-secure 1390 environment without proper protection can have a negative effect on 1391 network operations. 1393 SNMPv1 by itself is not a secure environment. Even if the network 1394 itself is secure (for example by using IPSec), even then, there is 1395 no control as to who on the secure network is allowed to access and 1396 GET/SET (read/change/create/delete) the objects in this MIB. 1398 It is recommended that the implementers consider the security 1399 features as provided by the SNMPv3 framework. Specifically, the 1400 use of the User-based Security Model RFC 2574 [RFC2574] and the 1401 View-based Access Control Model RFC 2575 [RFC2575] is recommended. 1403 It is then a customer/user responsibility to ensure that the SNMP 1404 entity giving access to an instance of this MIB, is properly 1405 configured to give access to the objects only to those principals 1406 (users) that have legitimate rights to indeed GET or SET 1407 (change/create/delete) them. 1409 The use of strict inbound VC lookup the security problems related 1410 to a global VC space in a node is greatly reduced, by limiting the 1411 accepted packets to a small set of controlled tunnels. 1413 9 References 1415 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 1416 "Multiprotocol Label Switching Architecture", RFC 3031, 1417 Jan 2001. 1419 Management Information Base 1421 [CEP] Malis, A., et al, "SONET/SDH Circuit Emulation over 1422 Packet (CEP)", Internet Draft , November 2001. 1425 [TRANS] Martini et al, "Transport of Layer 2 Frames Over MPLS" 1426 , April 1427 2002. 1429 [ENCAP] Martini et al, "Encapsulation Methods for Transport of 1430 Layer 2 Frames Over MPLS", , November 2001. 1433 [FRMWK] Pate et al, "Framework for Pseudo Wire Emulation Edge- 1434 to-Edge (PWE3)", , 1435 February 2002. 1437 [PWREQ] Xiao et al, "Requirements for Pseudo Wire Emulation 1438 Edge-to-Edge (PWE3)", , November 2001. 1441 [PW-MIB] Zelig et al, "Pseudo Wire (PW) Management Information 1442 Base", , June 2003. 1444 [CEPMIB] Danenberg et al, "SONET/SDH Circuit Emulation Service 1445 Over MPLS (CEP) Management Information Base Using 1446 SMIv2", , June 2003. 1448 [LSRMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T. "MPLS 1449 Label Switch Router Management Information Base Using 1450 SMIv2", draft-ietf-mpls-lsr-mib-08.txt, January 2002. 1452 [PWTC] Nadeau, T., et al, "Definitions for Textual Conventions 1453 and OBJECT-IDENTITIES for Pseudo-Wires Management", 1454 , June 2003. 1456 [TEMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T. "MPLS 1457 Traffic Engineering Management Information Base Using 1458 SMIv2", , January 2002. 1460 [LDPMIB] J. Cucchiara et al, "Definitions of Managed Objects for 1462 the Multiprotocol Label Switching, Label Distribution 1463 Protocol (LDP), , 1464 August 2001. 1466 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., 1467 Federokow, G., Li, T., and A. Conta, "MPLS Label Stack 1468 Encoding", RFC 3032, January 2001. 1470 Management Information Base 1472 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", RFC 1473 1700, October 1994. See also: http://www.isi.edu/in- 1474 notes/iana/assignments/smi-numbers 1476 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 1477 FAMILY NUMBERS,(http://www.isi.edu/in- 1478 notes/iana/assignements/address-family-numbers), for 1479 MIB see: 1480 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 1482 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces 1483 Group MIB using SMIv2", RFC 2863, January 2000. 1485 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 1486 requirement Levels", BCP 14, RFC 2119, March 1997. 1488 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1489 Architecture for Describing SNMP Management 1490 Frameworks", RFC 2571, April 1999. 1492 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 1493 Identification of Management Information for TCP/IP- 1494 based Internets", STD 16, RFC 1155, May 1990. 1496 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 1497 STD 16, RFC 1212, March 1991. 1499 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 1500 the SNMP", RFC 1215, March 1991. 1502 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1503 J, Rose, M., and S. Waldbusser, "Structure of 1504 Management Information Version 2 (SMIv2)", STD 58, RFC 1505 2578, April 1999. 1507 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1508 J, Rose, M., and S. Waldbusser, "Textual Conventions 1509 for SMIv2", STD 58, RFC 2579, April 1999. 1511 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1512 J, Rose, M., and S. Waldbusser, "Conformance Statements 1513 for SMIv2", STD 58, RFC 2580, April 1999. 1515 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 1516 "Simple Network Management Protocol", STD 15, RFC 1157, 1517 May 1990. 1519 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1520 "Introduction to Community-based SNMPv2", RFC 1901, 1521 January 1996. 1523 Management Information Base 1525 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1526 "Transport Mappings for Version 2 of the Simple Network 1527 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1529 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1530 "Message Processing and Dispatching for the Simple 1531 Network Management Protocol (SNMP)", RFC 2572, April 1532 1999. 1534 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 1535 Model (USM) for version 3 of the Simple Network 1536 Management Protocol (SNMPv3)", RFC 2574, April 1999. 1538 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1539 "Protocol Operations for Version 2 of the Simple 1540 Network Management Protocol (SNMPv2)", RFC 1905, 1541 January 1996. 1543 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 1544 Applications", RFC 2573, April 1999. 1546 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1547 Access Control Model (VACM) for the Simple Network 1548 Management Protocol (SNMP)", RFC 2575, April 1999. 1550 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1551 "Introduction to Version 3 of the Internet-standard 1552 Network Management Framework", RFC 2570, April 1999. 1554 10 Author's Addresses 1556 David Zelig 1557 Corrigent Systems 1558 126, Yigal Alon st. 1559 Tel Aviv, ISRAEL 1560 Phone: +972-3-6945273 1561 Email: davidz@corrigent.com 1563 Thomas D. Nadeau 1564 Cisco Systems, Inc. 1565 250 Apollo Drive 1566 Chelmsford, MA 01824 1567 Email: tnadeau@cisco.com 1569 Dave Danenberg 1570 Litchfield Communications, Inc. 1571 76 Westbury Park Rd 1572 Princeton Building East 1573 Watertown, CT 06795 1574 Email: dave_danenberg@litchfieldcomm.com 1575 Management Information Base 1577 Andrew G. Malis 1578 Vivace Networks, Inc. 1579 2730 Orchard Parkway 1580 San Jose, CA 95134 1581 Email: Andy.Malis@vivacenetworks.com 1583 Sharon Mantin 1584 AxONLink (Israel) Ltd 1585 9 Bareket St. 1586 Petah Tikva 49517, Israel 1587 Phone: +972-3-9263972 1588 Email: sharon.mantin@axonlink.com 1590 11 Full Copyright Statement 1592 Copyright (C) The Internet Society (2000). All Rights Reserved. 1594 This document and translations of it may be copied and furnished to 1595 others, and derivative works that comment on or otherwise explain 1596 it or assist in its implementation may be prepared, copied, 1597 published and distributed, in whole or in part, without restriction 1598 of any kind, provided that the above copyright notice and this 1599 paragraph are included on all such copies and derivative works. 1600 However, this document itself may not be modified in any way, such 1601 as by removing the copyright notice or references to the Internet 1602 Society or other Internet organizations, except as needed for the 1603 purpose of developing Internet standards in which case the 1604 procedures for copyrights defined in the Internet Standards process 1605 must be followed, or as required to translate it into languages 1606 other than English. 1608 The limited permissions granted above are perpetual and will not be 1609 revoked by the Internet Society or its successors or assigns. This 1610 document and the information contained herein is provided on an "AS 1611 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1612 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1613 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1614 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1615 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.