idnits 2.17.1 draft-ietf-pwe3-pw-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 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 28 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 293 has weird spacing: '...N |VCin inSeg...' == Line 297 has weird spacing: '...| inSeg outSe...' == Line 365 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 2002) is 7979 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 1437 looks like a reference -- Missing reference section? 'BCP14' on line 1480 looks like a reference -- Missing reference section? 'FRMWK' on line 1429 looks like a reference -- Missing reference section? 'ENCAP' on line 1425 looks like a reference -- Missing reference section? 'TRANS' on line 1421 looks like a reference -- Missing reference section? 'MPLSArch' on line 1411 looks like a reference -- Missing reference section? 'RFC2571' on line 1483 looks like a reference -- Missing reference section? 'RFC1155' on line 1487 looks like a reference -- Missing reference section? 'RFC1212' on line 1491 looks like a reference -- Missing reference section? 'RFC1215' on line 1494 looks like a reference -- Missing reference section? 'RFC2578' on line 1497 looks like a reference -- Missing reference section? 'RFC2579' on line 1502 looks like a reference -- Missing reference section? 'RFC2580' on line 1506 looks like a reference -- Missing reference section? 'RFC1157' on line 1510 looks like a reference -- Missing reference section? 'RFC1901' on line 1514 looks like a reference -- Missing reference section? 'RFC1906' on line 1520 looks like a reference -- Missing reference section? 'RFC2572' on line 1524 looks like a reference -- Missing reference section? 'RFC2574' on line 1529 looks like a reference -- Missing reference section? 'RFC1905' on line 1533 looks like a reference -- Missing reference section? 'RFC2573' on line 1538 looks like a reference -- Missing reference section? 'RFC2575' on line 1541 looks like a reference -- Missing reference section? 'RFC2570' on line 1545 looks like a reference -- Missing reference section? 'CEPMIB' on line 1440 looks like a reference -- Missing reference section? 'PWTC' on line 1448 looks like a reference -- Missing reference section? 'TEMIB' on line 1452 looks like a reference -- Missing reference section? 'LSRMIB' on line 1444 looks like a reference -- Missing reference section? 'CEP' on line 1417 looks like a reference -- Missing reference section? 'PWREQ' on line 1433 looks like a reference -- Missing reference section? 'LDPMIB' on line 1456 looks like a reference -- Missing reference section? 'LblStk' on line 1461 looks like a reference -- Missing reference section? 'Assigned' on line 1467 looks like a reference -- Missing reference section? 'IANAFamily' on line 1471 looks like a reference -- Missing reference section? 'IFMIB' on line 1477 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 2002 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 2002 13 Pseudo Wire (PW) over MPLS PSN Management Information Base 15 draft-ietf-pwe3-pw-mpls-mib-00.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 Management Information Base 97 Conventions used in this document 99 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 100 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 101 this document are to be interpreted as described in RFC-2119 102 [BCP14]. 104 3 Terminology 106 This document uses terminology from the document describing the PW 107 framework [FRMWK], from [ENCAP] and [TRANS]. 109 The terms "Outbound" and "Inbound" in this MIB module are based on 110 the common practice in the MPLS standards, i.e. "outbound" are 111 toward the PSN. However, where these terms are used in an object 112 name, the object description clarifies the exact packet direction 113 to prevent confusion with these terms in other documents. 115 "PSN Tunnel" is a general term indicating a virtual connection 116 between the two PW edge devices. Each tunnel may potentially carry 117 multiple VCs inside. In the scope of this document, it is MPLS 118 tunnel. 120 This document uses terminology from the document describing the 121 MPLS architecture [MPLSArch] for MPLS PSN. A Label Switched Path 122 (LSP) is modeled as described in [LSRMIB and TEMIB] via a series of 123 cross-connects through 1 or more Label switch routers (LSR). 125 In MPLS PSN, a PW connection typically uses a VC (Virtual 126 Connection) Label within a Tunnel Label [TRANS]. Multiple PW VCs 127 each with a unique VC Label can share the same Tunnel. For PW 128 transport over MPLS, the Tunnel Label is known as the "outer" 129 Label, while the VC Label is known as the "inner" Label. An 130 exception to this is with adjacent LSRs or the use of PHP. In this 131 case, there is an option for PW VCs to connect directly without an 132 outer Label. 134 4 The SNMP Management Framework 136 The SNMP Management Framework presently consists of five major 137 components: 139 o An overall architecture, described in RFC 2571 [RFC2571]. 141 o Mechanisms for describing and naming objects and events for the 142 purpose of management. The first version of this Structure of 143 Management Information (SMI) is called SMIv1 and described in STD 144 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 145 [RFC1215]. The second version, called SMIv2, is described in STD 146 Management Information Base 148 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 149 2580 [RFC2580]. 151 o Message protocols for transferring management information. The 152 first version of the SNMP message protocol is called SNMPv1 and 153 described in STD 15, RFC 1157 [RFC1157]. A second version of the 154 SNMP message protocol, which is not an Internet standards track 155 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and 156 RFC 1906 [RFC1906]. The third version of the message protocol is 157 called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 158 [RFC2572] and RFC 2574 [RFC2574]. 160 o Protocol operations for accessing management information. The 161 first set of protocol operations and associated PDU formats is 162 described in STD 15, RFC 1157 [RFC1157]. A second set of protocol 163 operations and associated PDU formats is described in RFC 1905 164 [RFC1905]. 166 o A set of fundamental applications described in RFC 2573 [RFC2573] 167 and the view-based access control mechanism described in RFC 2575 168 [RFC2575]. 170 A more detailed introduction to the current SNMP Management 171 Framework can be found in RFC 2570 [RFC2570]. 173 Managed objects are accessed via a virtual information store, 174 termed the Management Information Base or MIB. Objects in the MIB 175 are defined using the mechanisms defined in the SMI. 177 This memo specifies a MIB module that is compliant to the SMIv2. A 178 MIB conforming to the SMIv1 can be produced through the appropriate 179 translations. The resulting translated MIB must be semantically 180 equivalent, except where objects or events are omitted because no 181 translation is possible (use of Counter64). Some machine readable 182 information in SMIv2 will be converted into textual descriptions in 183 SMIv1 during the translation process. However, this loss of 184 machine readable information is not considered to change the 185 semantics of the MIB. 187 4.1 Object Definitions 189 Managed objects are accessed via a virtual information store, 190 termed the Management Information Base or MIB. Objects in the MIB 191 are defined using the subset of Abstract Syntax Notation One 192 (ASN.1) defined in the SMI. In particular, an OBJECT IDENTIFIER, an 193 administratively assigned name, names each object type. The object 194 type together with an object instance serves to uniquely identify a 195 specific instantiation of the object. For human convenience, we 196 often use a textual string, termed the descriptor, to also refer to 197 the object type. 199 Management Information Base 201 5 Feature Checklist 203 The PW MPLS MIB (PW-MPLS-MIB) is designed to satisfy the following 204 requirements and constraints: 206 - The MIB supports both manually configured and signaled VCs. 208 - The MIB supports point-to-point PW connections. 210 - The MIB enables the use of any emulated service. 212 - The MIB supports MPLS-TE outer tunnel, Non TE MPLS outer tunnel 213 (an outer tunnel signaled by LDP or set-up manually), and no 214 outer tunnel (where the VC label is the only label in the 215 incoming MPLS stack). 217 - The MIB enables both strict and loose incoming VC lookup. In 218 strict mode, only VC carried inside known in advance tunnels or 219 interfaces are accepted. The methods of the association 220 knowledge are out of the scope of this document. 222 6 MIB usage 224 The MIB structure for defining a PW service is composed from three 225 types of modules. 227 The first type is the PW-MIB module [PW-MIB], which configures 228 general parameters of the VC that are common to all types of 229 emulated services and PSNs. 231 The second type of module is per PSN module. There is a different 232 module for each type of PSN. This document defines the MIB module 233 for MPLS (PW-MPLS-MIB). 235 The third type of module is service-specific module, which is 236 emulated signal type dependent. These modules are defined in other 237 documents; see for example [CEPMIB]. 239 [PWTC] defines some of the object types used in these modules. 241 6.1 PW-MPLS-MIB usage 243 - The VC table (pwVcTable) in [PW-MIB] is used for all VC types 244 (ATM, FR, Ethernet, SONET, etc.). This table contains high level 245 generic parameters related to the VC creation. A row is created by 246 the operator for each PW service. 248 - If the PSN type in pwVcTable is MPLS, the agent creates a row in 249 the MPLS specific parameters table (pwMplsVcTable) in PW-MPLS-MIB, 250 Management Information Base 252 which contain MPLS specific parameters such as EXP bits handling 253 and outer tunnel selection. 255 - A row is created by the agent in the MPLS outbound tunnels table 256 (pwVcMplsOutboundTable), which associates the VC to one or more 257 (in a case of backup tunnels) MPLS tunnels. This table simply 258 associates the VC with the entries at the relevant MPLS MIBs. 259 Additional rows in this table may be created manually, if more 260 than one outer tunnel is required (for example for protection 261 purposes). 263 - The MPLS inbound tunnel table (pwVcMplsInboundTable) associates 264 the VC to the incoming tunnel. This (optional) table can be used 265 for restricting the packet reception for a specific PW from pre- 266 defined tunnels, bringing better security and better miss- 267 configuration error immunity. 269 - The MPLS tunnels mapping tabled (pwMplsTeMappingTable and 270 pwMplsNonTeMappingTable) associate the tunnel and the VC label to 271 the VC index. This table is used for easy lookup process when 272 searching VC information. 274 The relation to the MPLS network is by configuration of the edge 275 LSR only - that is to say, the LSR providing the PW function. Since 276 Tunnels are uni-directional, a pair of tunnels must exist (one for 277 inbound, one for outbound). The following graphic depicts a VC that 278 originates and terminates at LSR-M. It uses LSPs A and B formed by 279 Tunnels Ax and Bx continuing through LSR-N to LSR-P. The 280 concatenations of Tunnels create the LSPs. Note: 'X' denotes a 281 Tunnel's cross-connect. 283 Management Information Base 285 LSP-A 286 <- - - - - - - - - - - - - - - - - - - - - - - - - - - - 288 +---- (edge) LSR-M ---+ +--------- LSR-N ---------+ + LSR-P 289 |---+ | | | | 290 | | Tunnel | | Tunnel | | 291 + | A1 (M<-N) +----+ +----+ A2 (M<-P) +----+ +----+ 292 | | <------| | | |<--------------| | | | 293 <-->| N |VCin inSeg |MPLS| |MPLS| outSeg inSeg |MPLS| |MPLS| 294 N S | | <---X<-----| IF | | IF |<------X<------| IF | | IF | 295 A E | S | | |<-->| | | |<-->| | | 296 T R | | --->X----->| | | |------>X------>| | | | 297 I V | P |VCout outSeg| | | | inSeg outSeg | | | | 298 V I | | ------>| | | |-------------->| | | | 299 E C + | Tunnel +----+ +----+ Tunnel +----+ +----+ 300 E |---+ B1 (M->N) | | B2 (M->P) | | 301 | | | | | 302 +---------------------+ +-------------------------+ +----- 304 - - - - - - - - - - - - - - - - - - - - - - - - - - - -> 305 LSP-B 307 The PW-MPLS-MIB supports three options for MPLS network: 309 - In the MPLS-TE case, Tunnel A1 and B1 are created via the MPLS-TE 310 MIB [TEMIB]. The tunnels are associated to the VC by the (4) 311 indexes that uniquely identify the Tunnel at the TE-MIB. 313 - In the Non TE case, Tunnel A1 and B1 are either manually 314 configured or set up with LDP. The tunnels are associated to the VC 315 by the XC index in the MPLS-LSR-MIB [LSRMIB]. 317 - In the VC only case, there is no outer Tunnel on top of the VC 318 label. This case is useful in case of adjacent PE (see [TRANS]) or 319 when LSR-N acts as PHP for the outer tunnel label. In this case, 320 Association is done directly to the physical interfaces in the PW- 321 MPLS-MIB tables. 323 A combination of MPLS-TE outer tunnel(s) and LDP outer tunnel for 324 the same VC is allowed by creating the rows with the same VcIndex 325 with different MPLS tunnel indexes types. 327 6.2 Example of MIB usage 329 In this section we provide an example of using the MIB objects for 330 setting up a VC over MPLS. While this example is not meant to 331 illustrate every permutation of the MIB, it is intended as an aid 332 to understanding some of the key concepts. It is meant to be read 333 after going through the MIB itself. 335 Management Information Base 337 In this example a PW service for CEP is configured over an MPLS-TE 338 tunnel. It uses LDP as in [TRANS] for service set-up. 340 In PW-MIB: 342 In pwVcTable: 343 { 344 pwVcIndex 5, 346 pwVcType cep, 347 pwVcOwner maintenanceProtocol, 348 pwVcPsnType mpls, 349 pwVcSetUpPriority 0, 350 pwVcHoldingPriority 0, 351 pwVcInboundMode loose, 353 pwVcPeerAddrType ipv4(2), 354 pwVcPeerAddr 1.4.3.2, -- In this case equal to the 355 -- peer tunnel IP address 356 pwVcID 10, 357 pwVcLocalGroupID 12, 359 pwVcControlWord false, -- Control word not to be sent 360 pwVcLocalIfMtu 0, -- Do not send ifMtu parameter 361 pwVcLocalIfString false, -- Do not signal if string 363 pwVcRemoteGroupID 0xFFFF, -- Will be received by 364 -- maintenance protocol 365 pwVcRemoteControlWord notKnownYet, 366 pwVcRemoteIfMtu 0, 367 pwVcRemoteIfString "", 369 pwVcOutboundVcLabel 0xFFFF, -- Will be received by 370 -- maintenance protocol 371 pwVcInboundVcLabel 0xFFFF, -- Will be set by signaling 373 pwVcName "Example of CEP VC", 374 pwVcDescr "", 375 .. 377 pwVcAdminStatus up, 378 .. 380 Management Information Base 382 The operator now create a row in pwVcMplsTable based on the 383 VcIndex, that is configured with MPLS specific values: 385 In pwVcMplsTable: 386 { 387 pwVcMplsMplsType mplsTe, 388 pwVcMplsExpBitsMode outerTunnel, 389 pwVcMplsExpBits 0, 390 pwVcMplsTtl 2, 391 pwVcMplsLocalLdpID 1.2.3.4.0.0 -- Global label space 392 pwVcMplsLocalLdpEntityID 0, 393 pwVcMplsPeerLdpID 0, -- Not known yet 394 ... 395 } 397 The operator now associates the VC with an outgoing TE tunnel: 399 In pwVcMplsOutboundTable: 401 { 402 pwVcMplsOutboundIndex 0, -- The first row 403 --for this VCIndex. 404 pwVcMplsOutBoundLsrXcIndex 0, -- MPLS-TE 405 pwVcMplsOutboundTunnelIndex 500, 406 pwVcMplsOutboundTunnelInstance 0, 407 pwVcMplsOutboundTunnelLclLSR 1.2.3.4, -- Always 408 -- the LSR ID of the current node. 409 pwVcMplsOutboundTunnelPeerLSR 1.4.3.2 410 pwVcMplsOutboundIfIndex 0, -- MPLS-TE 412 .. 413 } 415 pwVcMplsInboundTable is not used because loose LDP set-up is used. 417 pwVcMplsTeMappingTable entry will be created by the agent once the 418 outbound table is configured and will enable easy lookup for the 419 VcIndex from knowledge of the outer tunnel indexes. 421 Management Information Base 423 7 Object definitions 425 PW-MPLS-MIB DEFINITIONS ::= BEGIN 427 IMPORTS 428 MODULE-IDENTITY, OBJECT-TYPE, 429 experimental, Unsigned32 430 FROM SNMPv2-SMI 432 MODULE-COMPLIANCE, OBJECT-GROUP 433 FROM SNMPv2-CONF 435 RowStatus, StorageType 436 FROM SNMPv2-TC 438 InterfaceIndexOrZero 439 FROM IF-MIB 441 MplsTunnelIndex, MplsTunnelInstanceIndex, 442 MplsLdpIdentifier, MplsLsrIdentifier 443 FROM MPLS-TC-MIB 445 PwVcIndexType 446 FROM PW-TC-MIB 448 pwVcIndex 449 FROM PW-MIB 451 ; 453 pwVcMplsMIB MODULE-IDENTITY 454 LAST-UPDATED "200206021200Z" -- 02 June 2002 12:00:00 EST 455 ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working 456 Group" 457 CONTACT-INFO 458 " 459 David Zelig 460 Postal: Corrigent Systems 461 126, Yigal Alon St. 462 Tel Aviv, ISRAEL 463 Phone: +972-3-6945273 464 E-mail: davidz@corrigent.com 466 Thomas D. Nadeau 467 Postal: Cisco Systems, Inc. 468 250 Apollo Drive 469 Chelmsford, MA 01824 470 Tel: +1-978-497-3051 471 Email: tnadeau@cisco.com 473 Dave Danenberg 474 Management Information Base 476 Postal: Litchfield Communications, Inc. 477 76 Westbury Park Rd 478 Princeton Building East 479 Watertown, CT 06795 480 Tel: +1-860-945-1573 x3180 481 Email: dave_danenberg@litchfieldcomm.com 483 Sharon Mantin 484 Postal: AxONLink (Israel) Ltd 485 9 Bareket St. 486 Petah Tikva 49517, Israel 487 Tel: +972-3-9263972 488 Email: sharon.mantin@axonlink.com 490 The PWE3 Working Group (email distribution pwe3@ietf.org) " 492 DESCRIPTION 493 "This MIB complements the PW-MIB for PW operation over MPLS. 494 " 496 -- Revision history. 497 REVISION 498 "200206021200Z" -- 02 June 2002 12:00:00 EST 499 DESCRIPTION 500 "Draft-ietf-pwe3-pw-mpls-mib-00 version. Changes from 501 previous version: 502 1) Spliting the mapping table into two tables, one for 503 Non TE application and one for TE application. 504 2) Object types alignment with MPLS MIBs. 506 " 507 REVISION 508 "200201291200Z" -- 29 January 2002 12:00:00 EST 509 DESCRIPTION 510 "Changes from previous version: 511 1) Add LDP entity association. 512 2) Clarify inbound/outbound directions. 513 3) Simplify indexing of outbound and inbound tables 514 and providing get next variables. 515 " 516 REVISION 517 "200107111200Z" -- 7 November 2001 12:00:00 EST 518 DESCRIPTION 519 "Changes from previous version: 520 1) Remove Vc instance from table indexing. 521 2) Update descriptions of indexing and protection. 522 3) Remove the need for MPLS-LSR in case of VC only. 523 4) Change pwVcMplsMplsType to BITS in order to enable 524 multiple types of outer tunnel. 525 5) Add ifindex to outer tunnel tables to support vcOnly 526 option. 528 Management Information Base 530 6) change naming of outbound, inbound and mapping tables to 531 reflect addition of VC only port ifindexes. 532 7) Adapt order of items in mapping table to SNMP convention. 533 " 534 REVISION 535 "200107111200Z" -- July 11 2001 12:00:00 EST 536 DESCRIPTION 537 "draft-zelig-pw-mib-00.txt - initial version" 539 ::= { experimental xxx } -- To be assigned by IANA 541 -- Top-level components of this MIB. 543 -- Traps 544 pwVcMplsNotifications OBJECT IDENTIFIER 545 ::= { pwVcMplsMIB 0 } 546 pwVcMplsNotifyPrefix OBJECT IDENTIFIER 547 ::= { pwVcMplsNotifications 0 } 548 -- Tables, Scalars 549 pwVcMplsObjects OBJECT IDENTIFIER 550 ::= { pwVcMplsMIB 1 } 552 -- Conformance 553 pwVcMplsConformance OBJECT IDENTIFIER 554 ::= { pwVcMplsMIB 2 } 556 -- PW VC MPLS table 558 pwVcMplsTable OBJECT-TYPE 559 SYNTAX SEQUENCE OF PwVcMplsEntry 560 MAX-ACCESS not-accessible 561 STATUS current 562 DESCRIPTION 563 "This table specifies information for VC to be carried over 564 MPLS PSN." 565 ::= { pwVcMplsObjects 1 } 567 pwVcMplsEntry OBJECT-TYPE 568 SYNTAX PwVcMplsEntry 569 MAX-ACCESS not-accessible 570 STATUS current 571 DESCRIPTION 572 "A row in this table represents parameters specific to MPLS 573 PSN for a pseudo wire connection (VC). The row is created 574 automatically by the local agent if the pwVcPsnType is 575 MPLS. It is indexed by pwVcIndex, which uniquely 576 identifying a singular connection. 577 " 579 INDEX { pwVcIndex } 580 Management Information Base 582 ::= { pwVcMplsTable 1 } 584 PwVcMplsEntry ::= SEQUENCE { 585 pwVcMplsMplsType BITS, 586 pwVcMplsExpBitsMode INTEGER, 587 pwVcMplsExpBits Unsigned32, 588 pwVcMplsTtl Unsigned32, 589 pwVcMplsLocalLdpID MplsLdpIdentifier, 590 pwVcMplsLocalLdpEntityID Unsigned32, 591 pwVcMplsPeerLdpID MplsLdpIdentifier, 592 pwVcMplsStorageType StorageType 593 } 595 pwVcMplsMplsType OBJECT-TYPE 596 SYNTAX BITS { 597 mplsTe (0), 598 mplsNonTe (1), 599 vcOnly (2) 600 } 601 MAX-ACCESS read-write 602 STATUS current 603 DESCRIPTION 604 "Set by the operator to indicate the outer tunnel types, if 605 exists. mplsTe is used if the outer tunnel was set-up by 606 MPLS-TE, and mplsNonTe is used the outer tunnel was set up 607 by LDP or manually. Combination of mplsTe and mplsNonTe 608 may exist in case of outer tunnel protection. 609 vcOnly is used if there is no outer tunnel label. vcOnly 610 cannot be combined with mplsNonTe or mplsTe." 611 ::= { pwVcMplsEntry 1 } 613 pwVcMplsExpBitsMode OBJECT-TYPE 614 SYNTAX INTEGER { 615 outerTunnel (1), 616 specifiedValue (2), 617 serviceDependant (3) 618 } 620 MAX-ACCESS read-write 621 STATUS current 622 DESCRIPTION 623 "Set by the operator to indicate the way the VC shim label 624 EXP bits are to be determined. The value of outerTunnel(1) 625 is used where there is an outer tunnel - pwVcMplsMplsType 626 is mplsTe or mplsNonTe. Note that in this case there is no 627 need to mark the VC label with the EXP bits since the VC 628 label is not visible to the intermediate nodes. 629 If there is no outer tunnel, specifiedValue(2) indicate 630 that the value is specified by pwVcMplsExpBits, and 631 serviceDependant(3) indicate that the EXP bits are setup 632 Management Information Base 634 based on a rule specified in the emulated service specific 635 tables, for example when the EXP bits are a function of 636 802.1p marking for Ethernet emulated service." 637 REFERENCE 638 "martini et al, " 639 DEFVAL { outerTunnel } 640 ::= { pwVcMplsEntry 2 } 642 pwVcMplsExpBits OBJECT-TYPE 643 SYNTAX Unsigned32 (0..7) 644 MAX-ACCESS read-write 645 STATUS current 646 DESCRIPTION 647 "Set by the operator to indicate the MPLS EXP bits to be 648 used on the VC shim label if pwVcMplsExpBitsMode is 649 specifiedValue(2), zero otherwise." 650 DEFVAL { 0 } 651 ::= { pwVcMplsEntry 3 } 653 pwVcMplsTtl OBJECT-TYPE 654 SYNTAX Unsigned32 (0..255) 655 MAX-ACCESS read-write 656 STATUS current 657 DESCRIPTION 658 "Set by the operator to indicate the VC TTL bits to be used 659 on the VC shim label." 660 REFERENCE 661 "martini et al, " 662 DEFVAL { 2 } 663 ::= { pwVcMplsEntry 4 } 665 pwVcMplsLocalLdpID OBJECT-TYPE 666 SYNTAX MplsLdpIdentifier 667 MAX-ACCESS read-write 668 STATUS current 669 DESCRIPTION 670 "The local LDP identifier of the LDP entity creating 671 this VC in the local node. As the VC labels are always 672 set from the per platform label space, the last two octets 673 in the LDP ID MUST be always both zeros." 674 REFERENCE 675 ", 676 . 677 " 678 ::= { pwVcMplsEntry 5 } 680 pwVcMplsLocalLdpEntityID OBJECT-TYPE 681 SYNTAX Unsigned32 682 MAX-ACCESS read-write 683 STATUS current 684 DESCRIPTION 685 Management Information Base 687 "The local LDP Entity index of the LDP entity to be used 688 for this VC on the local node. Should be set to all zeros 689 if not used." 690 REFERENCE 691 " 692 " 693 ::= { pwVcMplsEntry 6 } 695 pwVcMplsPeerLdpID OBJECT-TYPE 696 SYNTAX MplsLdpIdentifier 697 MAX-ACCESS read-only 698 STATUS current 699 DESCRIPTION 700 "The peer LDP identifier as identified from the LDP 701 session. Should be zero if not relevant or not known yet." 702 REFERENCE 703 ", 704 . 705 " 706 ::= { pwVcMplsEntry 7 } 708 pwVcMplsStorageType OBJECT-TYPE 709 SYNTAX StorageType 710 MAX-ACCESS read-write 711 STATUS current 712 DESCRIPTION 713 "This variable indicates the storage type for this row." 714 ::= { pwVcMplsEntry 8 } 716 -- End of PW MPLS VC table 718 -- Pseudo Wire VC MPLS Outbound Tunnel table 720 pwVcMplsOutboundIndexNext OBJECT-TYPE 721 SYNTAX Unsigned32 (0..4294967295) 722 MAX-ACCESS read-only 723 STATUS current 724 DESCRIPTION 725 "This object contains an appropriate value to 726 be used for pwVcMplsOutboundIndex when creating 727 entries in the pwVcMplsOutboundTable. The value 728 0 indicates that no unassigned entries are 729 available. To obtain the pwVcMplsOutboundIndex 730 value for a new entry, the manager issues a 731 management protocol retrieval operation to obtain 732 the current value of this object. After each 733 retrieval, the agent should modify the value to 734 the next unassigned index, however the agent MUST 735 NOT assume such retrieval will be done for each 736 row created." 737 ::= { pwVcMplsObjects 2 } 738 Management Information Base 740 pwVcMplsOutboundTable OBJECT-TYPE 741 SYNTAX SEQUENCE OF PwVcMplsOutboundEntry 742 MAX-ACCESS not-accessible 743 STATUS current 744 DESCRIPTION 745 "This table associates VCs using MPLS PSN with the outbound 746 MPLS tunnels (i.e. toward the PSN) or the physical 747 interface in case of VC only." 748 ::= { pwVcMplsObjects 3 } 750 pwVcMplsOutboundEntry OBJECT-TYPE 751 SYNTAX PwVcMplsOutboundEntry 752 MAX-ACCESS not-accessible 753 STATUS current 754 DESCRIPTION 755 "A row in this table represents a link between PW VC (that 756 require MPLS tunnels) and MPLS tunnel toward the PSN. 757 In the case of VC only, it associate the VC with the 758 interface that shall carry the VC. 759 This table is indexed by the pwVcIndex and an additional 760 index enabling multiple rows for the same VC index. 762 At least one entry is created in this table by the operator 763 for each PW VC that requires MPLS PSN. Note that the first 764 entry for each VC can be indexed by pwVcMplsOutboundIndex 765 equal zero without a need for retrieval of 766 pwVcMplsOutboundIndexNext. 768 This table points to the appropriate MPLS MIB. In the case 769 of MPLS-TE, the 4 variables relevant to the indexing of 770 a TE MPLS tunnel are set as in Srinivasan, et al, . 772 In case of Non-TE MPLS (an outer tunnel label assigned by 773 LDP or manually) the table points to the XC entry in the 774 LSR MIB as in Srinivasan, et al, . 775 In case of VC only (no outer tunnel) the ifIndex of the 776 port to carry the VC is configured. 778 Each VC may have multiple rows in this tables if protection 779 is available at the outer tunnel level, each row may be of 780 different type except for VC only, on which only rows with 781 ifIndex of the port are allowed. 782 " 784 INDEX { pwVcIndex, pwVcMplsOutboundIndex } 786 ::= { pwVcMplsOutboundTable 1 } 788 PwVcMplsOutboundEntry ::= SEQUENCE { 789 pwVcMplsOutboundIndex Unsigned32, 790 Management Information Base 792 pwVcMplsOutboundLsrXcIndex Unsigned32, 793 pwVcMplsOutboundTunnelIndex MplsTunnelIndex, 794 pwVcMplsOutboundTunnelInstance MplsTunnelInstanceIndex, 795 pwVcMplsOutboundTunnelLclLSR MplsLsrIdentifier, 796 pwVcMplsOutboundTunnelPeerLSR MplsLsrIdentifier, 797 pwVcMplsOutboundIfIndex InterfaceIndexOrZero, 798 pwVcMplsOutboundRowStatus RowStatus, 799 pwVcMplsOutboundStorageType StorageType 800 } 802 pwVcMplsOutboundIndex OBJECT-TYPE 803 SYNTAX Unsigned32 (0..4294967295) 804 MAX-ACCESS not-accessible 805 STATUS current 806 DESCRIPTION 807 "Arbitrary index for enabling multiple rows per VC in 808 this table. Next available free index can be retrieved 809 using pwVcMplsOutboundIndexNext. 810 " 811 ::= { pwVcMplsOutboundEntry 1 } 813 pwVcMplsOutboundLsrXcIndex OBJECT-TYPE 814 SYNTAX Unsigned32 815 MAX-ACCESS read-create 816 STATUS current 817 DESCRIPTION 818 "This object will be set by the operator. If the outer 819 label is defined in the MPL-LSR-MIB, i.e. set by LDP 820 or manually, this object points to the XC index 821 of the outer tunnel. Otherwise, it is set to zero." 822 ::= { pwVcMplsOutboundEntry 2 } 824 pwVcMplsOutboundTunnelIndex OBJECT-TYPE 825 SYNTAX MplsTunnelIndex 826 MAX-ACCESS read-create 827 STATUS current 828 DESCRIPTION 829 "Part of set of indexes for outbound tunnel in the case of 830 MPLS-TE outer tunnel, otherwise set to zero." 831 ::= { pwVcMplsOutboundEntry 3 } 833 pwVcMplsOutboundTunnelInstance OBJECT-TYPE 834 SYNTAX MplsTunnelInstanceIndex 835 MAX-ACCESS read-create 836 STATUS current 837 DESCRIPTION 838 "Part of set of indexes for outbound tunnel in the case of 839 MPLS-TE outer tunnel, otherwise set to zero." 840 ::= { pwVcMplsOutboundEntry 4 } 841 Management Information Base 843 pwVcMplsOutboundTunnelLclLSR OBJECT-TYPE 844 SYNTAX MplsLsrIdentifier 845 MAX-ACCESS read-create 846 STATUS current 847 DESCRIPTION 848 "Part of set of indexes for outbound tunnel in the case of 849 MPLS-TE outer tunnel, otherwise set to zero." 850 ::= { pwVcMplsOutboundEntry 5 } 852 pwVcMplsOutboundTunnelPeerLSR OBJECT-TYPE 853 SYNTAX MplsLsrIdentifier 854 MAX-ACCESS read-create 855 STATUS current 856 DESCRIPTION 857 "Part of set of indexes for outbound tunnel in the case of 858 MPLS-TE outer tunnel, otherwise set to zero." 859 ::= { pwVcMplsOutboundEntry 6 } 861 pwVcMplsOutboundIfIndex OBJECT-TYPE 862 SYNTAX InterfaceIndexOrZero 863 MAX-ACCESS read-create 864 STATUS current 865 DESCRIPTION 866 "In case of VC only (no outer tunnel), this object holds 867 the ifIndex of the outbound port, otherwise set to zero." 868 ::= { pwVcMplsOutboundEntry 7 } 870 pwVcMplsOutboundRowStatus OBJECT-TYPE 871 SYNTAX RowStatus 872 MAX-ACCESS read-create 873 STATUS current 874 DESCRIPTION 875 "For creating, modifying, and deleting this row." 876 ::= { pwVcMplsOutboundEntry 8 } 878 pwVcMplsOutboundStorageType OBJECT-TYPE 879 SYNTAX StorageType 880 MAX-ACCESS read-create 881 STATUS current 882 DESCRIPTION 883 "This variable indicates the storage type for this object." 884 ::= { pwVcMplsOutboundEntry 9 } 886 -- End of Pseudo Wire VC MPLS Outbound Tunnel table 888 -- Pseudo Wire VC MPLS Inbound Tunnel table 890 pwVcMplsInboundIndexNext OBJECT-TYPE 891 SYNTAX Unsigned32 (0..4294967295) 892 MAX-ACCESS read-only 893 Management Information Base 895 STATUS current 896 DESCRIPTION 897 "This object contains an appropriate value to 898 be used for pwVcMplsInboundIndex when creating 899 entries in the pwVcMplsInboundTable. The value 900 0 indicates that no unassigned entries are 901 available. To obtain the pwVcMplsInboundIndex 902 value for a new entry, the manager issues a 903 management protocol retrieval operation to obtain 904 the current value of this object. After each 905 retrieval, the agent should modify the value to 906 the next unassigned index, however the agent MUST 907 NOT assume such retrieval will be done for each 908 row created." 909 ::= { pwVcMplsObjects 4 } 911 pwVcMplsInboundTable OBJECT-TYPE 912 SYNTAX SEQUENCE OF PwVcMplsInboundEntry 913 MAX-ACCESS not-accessible 914 STATUS current 915 DESCRIPTION 916 "This table associates VCs using MPLS PSN with the inbound 917 MPLS tunnels (i.e. for packets coming from the PSN), 918 if such association is desired (mainly for security 919 reasons)." 920 ::= { pwVcMplsObjects 5 } 922 pwVcMplsInboundEntry OBJECT-TYPE 923 SYNTAX PwVcMplsInboundEntry 924 MAX-ACCESS not-accessible 925 STATUS current 926 DESCRIPTION 927 "A row in this table represents a link between PW VCs (that 928 require MPLS tunnels) and MPLS tunnel for packets arriving 929 from the PSN. 930 This table is indexed by the set of indexes used to 931 identify the VC - pwVcIndex and an additional 932 index enabling multiple rows for the same VC index. 934 Note that the first entry for each VC can be indexed by 935 pwVcMplsOutboundIndex equal zero without a need for 936 retrieval of pwVcMplsInboundIndexNext. 938 An entry is created in this table either automatically by 939 the local agent or created manually by the operator in 940 cases that strict mode is required. 942 Note that the control messages contain VC ID and VC type, 943 which together with the remote IP address identify the 944 pwVcIndex in the local node. 946 Management Information Base 948 This table points to the appropriate MPLS MIB. In the case 949 of MPLS-TE, the 4 variables relevant to the indexing of a 950 TE MPLS tunnel are set as in Srinivasan, et al, . 953 In case of non-TE MPLS tunnel (an outer tunnel label 954 assigned by LDP or manually) the table points to the XC 955 entry in the MPLS-LSR-MIB as in Srinivasan, et al, . 958 Each VC may have multiple rows in this tables if protection 959 is available at the outer tunnel level, each row may be of 960 different type except for VC only, on which only rows with 961 ifIndex of the port are allowed. 962 " 964 INDEX { pwVcIndex, pwVcMplsInboundIndex } 966 ::= { pwVcMplsInboundTable 1 } 968 PwVcMplsInboundEntry ::= SEQUENCE { 969 pwVcMplsInboundIndex Unsigned32, 970 pwVcMplsInboundLsrXcIndex Unsigned32, 971 pwVcMplsInboundTunnelIndex MplsTunnelIndex, 972 pwVcMplsInboundTunnelInstance MplsTunnelInstanceIndex, 973 pwVcMplsInboundTunnelLclLSR MplsLsrIdentifier, 974 pwVcMplsInboundTunnelPeerLSR MplsLsrIdentifier, 975 pwVcMplsInboundIfIndex InterfaceIndexOrZero, 976 pwVcMplsInboundRowStatus RowStatus, 977 pwVcMplsInboundStorageType StorageType 978 } 980 pwVcMplsInboundIndex OBJECT-TYPE 981 SYNTAX Unsigned32 (0..4294967295) 982 MAX-ACCESS not-accessible 983 STATUS current 984 DESCRIPTION 985 "Arbitrary index for enabling multiple rows per VC in 986 this table. Next available free index can be retrieved 987 using pwVcMplsInboundIndexNext. 988 " 989 ::= { pwVcMplsInboundEntry 1 } 991 pwVcMplsInboundLsrXcIndex OBJECT-TYPE 992 SYNTAX Unsigned32 993 MAX-ACCESS read-create 994 STATUS current 995 DESCRIPTION 996 "If the outer label is defined in the MPL-LSR-MIB, i.e. set 997 by LDP or manually, this object points to the XC index 998 of the outer tunnel. Otherwise, it is set to zero." 999 Management Information Base 1001 ::= { pwVcMplsInboundEntry 2 } 1003 pwVcMplsInboundTunnelIndex OBJECT-TYPE 1004 SYNTAX MplsTunnelIndex 1005 MAX-ACCESS read-create 1006 STATUS current 1007 DESCRIPTION 1008 "Part of set of indexes for outbound tunnel in the case of 1009 MPLS-TE outer tunnel, otherwise set to zero." 1010 ::= { pwVcMplsInboundEntry 3 } 1012 pwVcMplsInboundTunnelInstance OBJECT-TYPE 1013 SYNTAX MplsTunnelInstanceIndex 1014 MAX-ACCESS read-create 1015 STATUS current 1016 DESCRIPTION 1017 "Part of set of indexes for outbound tunnel in the case of 1018 MPLS-TE outer tunnel, otherwise set to zero." 1019 ::= { pwVcMplsInboundEntry 4 } 1021 pwVcMplsInboundTunnelLclLSR OBJECT-TYPE 1022 SYNTAX MplsLsrIdentifier 1023 MAX-ACCESS read-create 1024 STATUS current 1025 DESCRIPTION 1026 "Part of set of indexes for outbound tunnel in the case of 1027 MPLS-TE outer tunnel, otherwise set to zero." 1028 ::= { pwVcMplsInboundEntry 5 } 1030 pwVcMplsInboundTunnelPeerLSR OBJECT-TYPE 1031 SYNTAX MplsLsrIdentifier 1032 MAX-ACCESS read-create 1033 STATUS current 1034 DESCRIPTION 1035 "Part of set of indexes for outbound tunnel in the case of 1036 MPLS-TE outer tunnel, otherwise set to zero." 1037 ::= { pwVcMplsInboundEntry 6 } 1039 pwVcMplsInboundIfIndex OBJECT-TYPE 1040 SYNTAX InterfaceIndexOrZero 1041 MAX-ACCESS read-create 1042 STATUS current 1043 DESCRIPTION 1044 "In case of VC only (no outer tunnel), this object holds the 1045 ifIndex of the inbound port, otherwise set to zero." 1046 ::= { pwVcMplsInboundEntry 7 } 1048 pwVcMplsInboundRowStatus OBJECT-TYPE 1049 SYNTAX RowStatus 1050 MAX-ACCESS read-create 1051 Management Information Base 1053 STATUS current 1054 DESCRIPTION 1055 "For creating, modifying, and deleting this row." 1056 ::= { pwVcMplsInboundEntry 8 } 1058 pwVcMplsInboundStorageType OBJECT-TYPE 1059 SYNTAX StorageType 1060 MAX-ACCESS read-create 1061 STATUS current 1062 DESCRIPTION 1063 "This variable indicates the storage type for this row." 1064 ::= { pwVcMplsInboundEntry 9 } 1066 -- End of Pseudo Wire VC MPLS Inbound Tunnel table 1068 -- MPLS to VC Mapping Tables. 1070 pwVcMplsNonTeMappingTable OBJECT-TYPE 1071 SYNTAX SEQUENCE OF PwVcMplsNonTeMappingEntry 1072 MAX-ACCESS not-accessible 1073 STATUS current 1074 DESCRIPTION 1075 "This table maps an inbound/outbound Tunnel to a VC in non- 1076 TE applications." 1077 ::= { pwVcMplsObjects 6 } 1079 pwVcMplsNonTeMappingEntry OBJECT-TYPE 1080 SYNTAX PwVcMplsNonTeMappingEntry 1081 MAX-ACCESS not-accessible 1082 STATUS current 1083 DESCRIPTION 1084 "A row in this table represents the association 1085 between the PW VC and it's non TE MPLS outer Tunnel 1086 it's physical interface if there is no outer tunnel 1087 (VC only). 1089 An application can use this table to quickly retrieve the 1090 PW carried over specific non-TE MPLS outer tunnel or 1091 physical interface. 1093 The table in indexed by the XC index for MPLS Non-TE 1094 tunnel, or ifIndex of the port in VC only case, the 1095 direction of the VC in the specific entry and the VCIndex. 1097 The same table is used in both inbound and outbound 1098 directions, but in a different row for each direction. If 1099 the inbound association is not known, no rows should exist 1100 for it. 1102 Rows are created by the local agent when all the 1103 Management Information Base 1105 association data is available for display." 1107 INDEX { pwVcMplsNonTeMappingTunnelDirection, 1108 pwVcMplsNonTeMappingXcTunnelIndex, 1109 pwVcMplsNonTeMappingIfIndex, 1110 pwVcMplsNonTeMappingVcIndex } 1112 ::= { pwVcMplsNonTeMappingTable 1 } 1114 PwVcMplsNonTeMappingEntry ::= SEQUENCE { 1115 pwVcMplsNonTeMappingTunnelDirection INTEGER, 1116 pwVcMplsNonTeMappingXcTunnelIndex Unsigned32, 1117 pwVcMplsNonTeMappingIfIndex InterfaceIndexOrZero, 1118 pwVcMplsNonTeMappingVcIndex PwVcIndexType 1119 } 1121 pwVcMplsNonTeMappingTunnelDirection OBJECT-TYPE 1122 SYNTAX INTEGER { 1123 outbound (1), -- From the PE toward the PSN 1124 inbound (2) -- From the PSN into the PE 1125 } 1126 MAX-ACCESS not-accessible 1127 STATUS current 1128 DESCRIPTION 1129 "Identifies if the row represent an outbound or inbound 1130 mapping." 1131 ::= { pwVcMplsNonTeMappingEntry 1 } 1133 pwVcMplsNonTeMappingXcTunnelIndex OBJECT-TYPE 1134 SYNTAX Unsigned32 (0..4294967295) 1135 MAX-ACCESS not-accessible 1136 STATUS current 1137 DESCRIPTION 1138 "Index for the conceptual XC row identifying Tunnel to VC 1139 mappings when the outer tunnel is created by the MPLS-LSR- 1140 MIB, Zero otherwise." 1141 ::= { pwVcMplsNonTeMappingEntry 2 } 1143 pwVcMplsNonTeMappingIfIndex OBJECT-TYPE 1144 SYNTAX InterfaceIndexOrZero 1145 MAX-ACCESS not-accessible 1146 STATUS current 1147 DESCRIPTION 1148 "Identify the port on which the VC is carried for VC only 1149 case." 1150 ::= { pwVcMplsNonTeMappingEntry 3 } 1152 pwVcMplsNonTeMappingVcIndex OBJECT-TYPE 1153 SYNTAX PwVcIndexType 1154 MAX-ACCESS read-only 1155 Management Information Base 1157 STATUS current 1158 DESCRIPTION 1159 "The value that represent the VC in the pwVcTable." 1160 ::= { pwVcMplsNonTeMappingEntry 4 } 1162 -- End of Non-TE MPLS Tunnel to VC Mapping Table 1164 pwVcMplsTeMappingTable OBJECT-TYPE 1165 SYNTAX SEQUENCE OF PwVcMplsTeMappingEntry 1166 MAX-ACCESS not-accessible 1167 STATUS current 1168 DESCRIPTION 1169 "This table maps an inbound/outbound Tunnel to a VC in 1170 MPLS-TE applications." 1171 ::= { pwVcMplsObjects 7 } 1173 pwVcMplsTeMappingEntry OBJECT-TYPE 1174 SYNTAX PwVcMplsTeMappingEntry 1175 MAX-ACCESS not-accessible 1176 STATUS current 1177 DESCRIPTION 1178 "A row in this table represents the association 1179 between a PW VC and it's MPLS-TE outer Tunnel. 1181 An application can use this table to quickly retrieve the 1182 PW carried over specific TE MPLS outer tunnel. 1184 The table in indexed by the 4 indexes of a TE tunnel, 1185 the direction of the VC specific entry and the VcIndex. 1187 The same table is used in both inbound and outbound 1188 directions, a different row for each direction. If the 1189 inbound association is not known, no rows should exist for 1190 it. 1192 Rows are created by the local agent when all the 1193 association data is available for display." 1195 INDEX { pwVcMplsTeMappingTunnelDirection, 1196 pwVcMplsTeMappingTunnelIndex, 1197 pwVcMplsTeMappingTunnelInstance, 1198 pwVcMplsTeMappingTunnelPeerLsrID, 1199 pwVcMplsTeMappingTunnelLocalLsrID, 1200 pwVcMplsTeMappingVcIndex } 1202 ::= { pwVcMplsTeMappingTable 1 } 1204 PwVcMplsTeMappingEntry ::= SEQUENCE { 1205 pwVcMplsTeMappingTunnelDirection INTEGER, 1206 pwVcMplsTeMappingTunnelIndex MplsTunnelIndex, 1207 pwVcMplsTeMappingTunnelInstance MplsTunnelInstanceIndex, 1208 Management Information Base 1210 pwVcMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier, 1211 pwVcMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier, 1212 pwVcMplsTeMappingVcIndex PwVcIndexType 1213 } 1215 pwVcMplsTeMappingTunnelDirection OBJECT-TYPE 1216 SYNTAX INTEGER { 1217 outbound (1), -- From the PE toward the PSN 1218 inbound (2) -- From the PSN into the PE 1219 } 1220 MAX-ACCESS not-accessible 1221 STATUS current 1222 DESCRIPTION 1223 "Identifies if the row represent an outbound or inbound 1224 mapping." 1225 ::= { pwVcMplsTeMappingEntry 1 } 1227 pwVcMplsTeMappingTunnelIndex OBJECT-TYPE 1228 SYNTAX MplsTunnelIndex 1229 MAX-ACCESS not-accessible 1230 STATUS current 1231 DESCRIPTION 1232 "Primary index for the conceptual row identifying the 1233 MPLS-TE tunnel." 1234 ::= { pwVcMplsTeMappingEntry 2 } 1236 pwVcMplsTeMappingTunnelInstance OBJECT-TYPE 1237 SYNTAX MplsTunnelInstanceIndex 1238 MAX-ACCESS not-accessible 1239 STATUS current 1240 DESCRIPTION 1241 "Identifies an instance of the MPLS-TE tunnel." 1242 ::= { pwVcMplsTeMappingEntry 3 } 1244 pwVcMplsTeMappingTunnelPeerLsrID OBJECT-TYPE 1245 SYNTAX MplsLsrIdentifier 1246 MAX-ACCESS not-accessible 1247 STATUS current 1248 DESCRIPTION 1249 "Identifies an Peer LSR when the outer tunnel is MPLS-TE 1250 based." 1251 ::= { pwVcMplsTeMappingEntry 4 } 1253 pwVcMplsTeMappingTunnelLocalLsrID OBJECT-TYPE 1254 SYNTAX MplsLsrIdentifier 1255 MAX-ACCESS not-accessible 1256 STATUS current 1257 DESCRIPTION 1258 "Identifies the local LSR." 1259 ::= { pwVcMplsTeMappingEntry 5 } 1260 Management Information Base 1262 pwVcMplsTeMappingVcIndex OBJECT-TYPE 1263 SYNTAX PwVcIndexType 1264 MAX-ACCESS read-only 1265 STATUS current 1266 DESCRIPTION 1267 "The value that represent the VC in the pwVcTable." 1268 ::= { pwVcMplsTeMappingEntry 6 } 1270 -- End of TE MPLS Tunnel to VC Mapping Table 1272 -- Notifications - PW over MPLS - FFS 1273 -- End of notifications. 1275 -- conformance information 1277 -- Note: Conformance at the object access and values level is 1278 -- still FFS, therefore current conformance is defined at the 1279 -- object existence level only. 1281 pwVcMplsGroups OBJECT IDENTIFIER ::= { pwVcMplsConformance 1 } 1282 pwVcMplsCompliances OBJECT IDENTIFIER ::= { pwVcMplsConformance 2 } 1284 pwMplsModuleCompliance MODULE-COMPLIANCE 1285 STATUS current 1286 DESCRIPTION 1287 "The compliance statement for agent that support PW 1288 over MPLS PSN operation." 1290 MODULE -- this module 1291 MANDATORY-GROUPS { pwVcMplsGroup, 1292 pwVcMplsOutboundGroup, 1293 pwVcMplsMappingGroup 1294 } 1296 GROUP pwVcMplsInboundGroup 1297 DESCRIPTION 1298 "This group is mandatory for those PE that support PW 1299 over MPLS PSN." 1301 ::= { pwVcMplsCompliances 1 } 1303 -- Units of conformance. 1305 pwVcMplsGroup OBJECT-GROUP 1306 OBJECTS { 1307 pwVcMplsMplsType, 1308 pwVcMplsExpBitsMode, 1309 pwVcMplsExpBits, 1310 pwVcMplsTtl, 1311 Management Information Base 1313 pwVcMplsLocalLdpID, 1314 pwVcMplsLocalLdpEntityID, 1315 pwVcMplsPeerLdpID, 1316 pwVcMplsStorageType 1317 } 1319 STATUS current 1320 DESCRIPTION 1321 "Collection of objects needed for PW VC 1322 over MPLS PSN configuration." 1323 ::= { pwVcMplsGroups 1 } 1325 pwVcMplsOutboundGroup OBJECT-GROUP 1326 OBJECTS { 1327 pwVcMplsOutboundIndexNext, 1328 pwVcMplsOutboundLsrXcIndex, 1329 pwVcMplsOutboundTunnelIndex, 1330 pwVcMplsOutboundTunnelInstance, 1331 pwVcMplsOutboundTunnelLclLSR, 1332 pwVcMplsOutboundTunnelPeerLSR, 1333 pwVcMplsOutboundIfIndex, 1334 pwVcMplsOutboundRowStatus, 1335 pwVcMplsOutboundStorageType 1336 } 1338 STATUS current 1339 DESCRIPTION 1340 "Collection of objects needed for outbound association of 1341 VC and MPLS tunnel." 1342 ::= { pwVcMplsGroups 2 } 1344 pwVcMplsInboundGroup OBJECT-GROUP 1345 OBJECTS { 1346 pwVcMplsInboundIndexNext, 1347 pwVcMplsInboundLsrXcIndex, 1348 pwVcMplsInboundTunnelIndex, 1349 pwVcMplsInboundTunnelInstance, 1350 pwVcMplsInboundTunnelLclLSR, 1351 pwVcMplsInboundTunnelPeerLSR, 1352 pwVcMplsInboundIfIndex, 1353 pwVcMplsInboundRowStatus, 1354 pwVcMplsInboundStorageType 1355 } 1357 STATUS current 1358 DESCRIPTION 1359 "Collection of objects needed for inbound association of 1360 VC and MPLS tunnel. This group is mandatory if strict 1361 mode is implemented." 1362 Management Information Base 1364 ::= { pwVcMplsGroups 3 } 1366 pwVcMplsMappingGroup OBJECT-GROUP 1367 OBJECTS { 1368 pwVcMplsNonTeMappingVcIndex, 1369 pwVcMplsTeMappingVcIndex 1370 } 1372 STATUS current 1373 DESCRIPTION 1374 "Collection of objects used for mapping of tunnels and VC 1375 labels to VC index." 1376 ::= { pwVcMplsGroups 4 } 1378 END -- of PW-MPLS-MIB 1380 8 Security Considerations 1382 There are a number of management objects defined in this MIB that 1383 have a MAX-ACCESS clause of read-write and/or read-create. Such 1384 objects may be considered sensitive or vulnerable in some network 1385 environments. The support for SET operations in a non-secure 1386 environment without proper protection can have a negative effect on 1387 network operations. 1389 SNMPv1 by itself is not a secure environment. Even if the network 1390 itself is secure (for example by using IPSec), even then, there is 1391 no control as to who on the secure network is allowed to access and 1392 GET/SET (read/change/create/delete) the objects in this MIB. 1394 It is recommended that the implementers consider the security 1395 features as provided by the SNMPv3 framework. Specifically, the 1396 use of the User-based Security Model RFC 2574 [RFC2574] and the 1397 View-based Access Control Model RFC 2575 [RFC2575] is recommended. 1399 It is then a customer/user responsibility to ensure that the SNMP 1400 entity giving access to an instance of this MIB, is properly 1401 configured to give access to the objects only to those principals 1402 (users) that have legitimate rights to indeed GET or SET 1403 (change/create/delete) them. 1405 The use of strict inbound VC lookup the security problems related 1406 to a global VC space in a node is greatly reduced, by limiting the 1407 accepted packets to a small set of controlled tunnels. 1409 9 References 1411 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 1412 "Multiprotocol Label Switching Architecture", RFC 3031, 1413 Jan 2001. 1415 Management Information Base 1417 [CEP] Malis, A., et al, "SONET/SDH Circuit Emulation over 1418 Packet (CEP)", Internet Draft , November 2001. 1421 [TRANS] Martini et al, "Transport of Layer 2 Frames Over MPLS" 1422 , April 1423 2002. 1425 [ENCAP] Martini et al, "Encapsulation Methods for Transport of 1426 Layer 2 Frames Over MPLS", , November 2001. 1429 [FRMWK] Pate et al, "Framework for Pseudo Wire Emulation Edge- 1430 to-Edge (PWE3)", , 1431 February 2002. 1433 [PWREQ] Xiao et al, "Requirements for Pseudo Wire Emulation 1434 Edge-to-Edge (PWE3)", , November 2001. 1437 [PW-MIB] Zelig et al, "Pseudo Wire (PW) Management Information 1438 Base", , June 2002. 1440 [CEPMIB] Danenberg et al, "SONET/SDH Circuit Emulation Service 1441 Over MPLS (CEP) Management Information Base Using 1442 SMIv2", , June 2002. 1444 [LSRMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T. "MPLS 1445 Label Switch Router Management Information Base Using 1446 SMIv2", draft-ietf-mpls-lsr-mib-08.txt, January 2002. 1448 [PWTC] Nadeau, T., et al, "Definitions for Textual Conventions 1449 and OBJECT-IDENTITIES for Pseudo-Wires Management", 1450 , June 2002. 1452 [TEMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T. "MPLS 1453 Traffic Engineering Management Information Base Using 1454 SMIv2", , January 2002. 1456 [LDPMIB] J. Cucchiara et al, "Definitions of Managed Objects for 1457 the Multiprotocol Label Switching, Label Distribution 1458 Protocol (LDP), , 1459 August 2001. 1461 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., 1462 Federokow, G., Li, T., and A. Conta, "MPLS Label Stack 1463 Encoding", RFC 3032, January 2001. 1465 Management Information Base 1467 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", RFC 1468 1700, October 1994. See also: http://www.isi.edu/in- 1469 notes/iana/assignments/smi-numbers 1471 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 1472 FAMILY NUMBERS,(http://www.isi.edu/in- 1473 notes/iana/assignements/address-family-numbers), for 1474 MIB see: 1475 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 1477 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces 1478 Group MIB using SMIv2", RFC 2863, January 2000. 1480 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 1481 requirement Levels", BCP 14, RFC 2119, March 1997. 1483 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1484 Architecture for Describing SNMP Management 1485 Frameworks", RFC 2571, April 1999. 1487 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 1488 Identification of Management Information for TCP/IP- 1489 based Internets", STD 16, RFC 1155, May 1990. 1491 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 1492 STD 16, RFC 1212, March 1991. 1494 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 1495 the SNMP", RFC 1215, March 1991. 1497 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1498 J, Rose, M., and S. Waldbusser, "Structure of 1499 Management Information Version 2 (SMIv2)", STD 58, RFC 1500 2578, April 1999. 1502 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1503 J, Rose, M., and S. Waldbusser, "Textual Conventions 1504 for SMIv2", STD 58, RFC 2579, April 1999. 1506 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1507 J, Rose, M., and S. Waldbusser, "Conformance Statements 1508 for SMIv2", STD 58, RFC 2580, April 1999. 1510 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 1511 "Simple Network Management Protocol", STD 15, RFC 1157, 1512 May 1990. 1514 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1515 "Introduction to Community-based SNMPv2", RFC 1901, 1516 January 1996. 1518 Management Information Base 1520 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1521 "Transport Mappings for Version 2 of the Simple Network 1522 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1524 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1525 "Message Processing and Dispatching for the Simple 1526 Network Management Protocol (SNMP)", RFC 2572, April 1527 1999. 1529 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 1530 Model (USM) for version 3 of the Simple Network 1531 Management Protocol (SNMPv3)", RFC 2574, April 1999. 1533 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1534 "Protocol Operations for Version 2 of the Simple 1535 Network Management Protocol (SNMPv2)", RFC 1905, 1536 January 1996. 1538 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 1539 Applications", RFC 2573, April 1999. 1541 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1542 Access Control Model (VACM) for the Simple Network 1543 Management Protocol (SNMP)", RFC 2575, April 1999. 1545 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1546 "Introduction to Version 3 of the Internet-standard 1547 Network Management Framework", RFC 2570, April 1999. 1549 10 Author's Addresses 1551 David Zelig 1552 Corrigent Systems 1553 126, Yigal Alon st. 1554 Tel Aviv, ISRAEL 1555 Phone: +972-3-6945273 1556 Email: davidz@corrigent.com 1558 Thomas D. Nadeau 1559 Cisco Systems, Inc. 1560 250 Apollo Drive 1561 Chelmsford, MA 01824 1562 Email: tnadeau@cisco.com 1564 Dave Danenberg 1565 Litchfield Communications, Inc. 1566 76 Westbury Park Rd 1567 Princeton Building East 1568 Watertown, CT 06795 1569 Email: dave_danenberg@litchfieldcomm.com 1570 Management Information Base 1572 Andrew G. Malis 1573 Vivace Networks, Inc. 1574 2730 Orchard Parkway 1575 San Jose, CA 95134 1576 Email: Andy.Malis@vivacenetworks.com 1578 Sharon Mantin 1579 AxONLink (Israel) Ltd 1580 9 Bareket St. 1581 Petah Tikva 49517, Israel 1582 Phone: +972-3-9263972 1583 Email: sharon.mantin@axonlink.com 1585 11 Full Copyright Statement 1587 Copyright (C) The Internet Society (2000). All Rights Reserved. 1589 This document and translations of it may be copied and furnished to 1590 others, and derivative works that comment on or otherwise explain 1591 it or assist in its implementation may be prepared, copied, 1592 published and distributed, in whole or in part, without restriction 1593 of any kind, provided that the above copyright notice and this 1594 paragraph are included on all such copies and derivative works. 1595 However, this document itself may not be modified in any way, such 1596 as by removing the copyright notice or references to the Internet 1597 Society or other Internet organizations, except as needed for the 1598 purpose of developing Internet standards in which case the 1599 procedures for copyrights defined in the Internet Standards process 1600 must be followed, or as required to translate it into languages 1601 other than English. 1603 The limited permissions granted above are perpetual and will not be 1604 revoked by the Internet Society or its successors or assigns. This 1605 document and the information contained herein is provided on an "AS 1606 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1607 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1608 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1609 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1610 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.