idnits 2.17.1 draft-ietf-pwe3-pw-atm-mib-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 19. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1673. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1684. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1691. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1697. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 12, 2008) is 5669 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'PWTC' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWMPLSMIB' Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Pseudo Wire Edge to Edge Emulation O. Nicklass 3 Internet-Draft RADVISION Ltd. 4 Intended status: Standards Track S. Sathappan 5 Expires: April 15, 2009 M. Venkatesan 6 Marconi Communications 7 T. Nadeau 8 Cisco Systems, Inc. 9 October 12, 2008 11 Managed Objects for ATM over Packet Switched Network (PSN) 12 draft-ietf-pwe3-pw-atm-mib-06.txt 14 Status of this Memo 16 By submitting this Internet-Draft, each author represents that any 17 applicable patent or other IPR claims of which he or she is aware 18 have been or will be disclosed, and any of which he or she becomes 19 aware will be disclosed, in accordance with Section 6 of BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 This Internet-Draft will expire on April 15, 2009. 39 Abstract 41 This memo defines a portion of the Management Information Base (MIB) 42 for use with network management protocols in the Internet community. 43 In particular, it describes managed objects for modeling ATM 44 Pseudowire (PW) carrying ATM cells over Packet Switch Network (PSN). 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 50 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 51 4. The Internet-Standard Management Framework . . . . . . . . . . 4 52 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 53 6. Relation to other PW-MIB modules . . . . . . . . . . . . . . . 5 54 7. ATM-PW MIB Usage . . . . . . . . . . . . . . . . . . . . . . . 6 55 8. Structure of the MIB module . . . . . . . . . . . . . . . . . 7 56 9. Object definition . . . . . . . . . . . . . . . . . . . . . . 8 57 10. Security considerations . . . . . . . . . . . . . . . . . . . 36 58 11. IANA considerations . . . . . . . . . . . . . . . . . . . . . 37 59 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 38 60 12.1. Normative references . . . . . . . . . . . . . . . . . . 38 61 12.2. Informative references . . . . . . . . . . . . . . . . . 39 62 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 39 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 39 64 Intellectual Property and Copyright Statements . . . . . . . . . . 41 66 1. Introduction 68 This document describes a model for managing "emulated" ATM services 69 over a Packet Switched Network(PSN). 71 The document follows the requirements for Pseudo-Wire Emulation Edge- 72 to-Edge [PWREQ], and closely related to [ATMENCAP] and [ATMTRANS] 73 which describe the encapsulation of ATM signals and provide the 74 Emulation Service over a Packet Switched Network. 76 The ATM management model consists of several MIB modules, following 77 the layering model described in the PWE3 Architecture [PWARCH] 78 document. The ATM MIB module described in this document works 79 closely with the MIB modules described in [AToMTC], [AToM], [IFMIB], 80 [PWMIB] and the textual conventions defined in [PWTC]. The 81 conceptual layering and relationship among all those is described in 82 Figure 1 and in the "Relation to other PW-MIB modules" section listed 83 below. AN ATM connection will be a pseudo-wire (PW) connection. It 84 will not be treated as an interface and will therefore not be 85 represented in the ifTable. 87 Figure 1:Conceptual Layering 89 +-------------------+ 90 | ATM MIB | ATM-TC-MIB, 91 +-------------------+ ATMMIB 92 | 93 +-------------------+ 94 Service | ATM PW MIB | PW-ATM-MIB 95 Layer +-------------------+ 97 - - - - - - - - - - - | - - - - - - - - - - - - - - - 98 Generic +-------------------+ 99 PW | Generic PW MIBS | PW-TC-MIB, 100 Layer +-------------------+ PW-STD-MIB 101 - - - - - - - - - - - -| - - - - - - - - - - - - - - - 102 +-------------------+ 103 PSN VC | MPLS VC MIBS | PW-MPLS-MIB 104 Layer +-------------------+ 105 - - - - - - - - - - - -| - - - - - - - - - - - - - - - 106 +-------------------+ 107 PSN | MPLS MIBs | MPLS-TE-STD-MIB, 108 Layer +-------------------+ MPLS-LSR-STD-MIB 110 Figure 1 112 Comments should be made directly to PWE3 group at pwe3@ietf.org. 114 2. Conventions 116 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 117 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 118 document are to be interpreted as described in RFC 2119 [BCP14]. 120 3. Terminology 122 This document follows the terminology used in PW Architecture 123 [PWARCH]. 125 PSN bound References the traffic direction where a ATM Cell 126 is received, adapted to packet, assigned a PW 127 label, and sent into the PSN. Within the MIB 128 objects it is called outbound. 130 CE bound The direction where packets are received 131 from the PSN, cells are reconstructed from the 132 packet payloads, and sent into the ATM Network 133 as cells. Within the MIB objects it is called 134 inbound. 136 Adaptation Refers to the method of adapting a "foreign" 137 communications protocol such that it can be 138 carried by a packet switched net (the PSN). For 139 example, in a ATM service the foreign protocol 140 is ATM. The PSN may be MPLS. 142 PSN Packet Switched Network. 144 PSN Tunnel A general term indicating a virtual connection 145 between the two PW edge devices. In practice 146 this connection is not limited to path-oriented 147 types of PSNs such as MPLS. An example of a non- 148 path-oriented PSN is an IP PSN. 150 4. The Internet-Standard Management Framework 152 For a detailed overview of the documents that describe the current 153 Internet-Standard Management Framework, please refer to section 7 of 154 RFC 3410 [RFC3410]. 156 Managed objects are accessed via a virtual information store, termed 157 the Management Information Base or MIB. MIB objects are generally 158 accessed through the Simple Network Management Protocol (SNMP). 159 Objects in the MIB are defined using the mechanisms defined in the 160 Structure of Management Information (SMI). This memo specifies a MIB 161 module that is compliant to the SMIv2, which is described in STD 58, 162 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 163 [RFC2580]. 165 5. Overview 167 This MIB module is designed to satisfy the following requirements and 168 constraints: 169 o - Fit within the architecture defined by [PWARCH] and [PWMIB]. 170 o - Fit within the model for VP/VC definitions and management 171 concept as defined in the [AToM] MIB. 172 o - Supports manually configured ATM PWs 173 o - Supports automatically configured ATM PWs 174 o - The MIB module enables the use of any PSN type 175 o - The MIB module supports point-to-point ATM PW connections. 176 Point-to-multipoint and multipoint-to-point connections are for 177 future study. 178 o - The MIB module allows configuration of all the parameters needed 179 to establish a PW to carry ATM cells. 180 o - The MIB module reports: ATM performance metrics for the ATM PW. 181 This includes cells transmit, Cells dropped, Cells received, and 182 unknownCells. In addition it reports performance metrics at 183 packet level. 184 o - ATM OAM cell support. 185 o - The MIB module does not consider ILMI support 187 6. Relation to other PW-MIB modules 189 The MIB structure for defining a PW service is composed of three 190 layers of MIB modules functioning together. This general model is 191 defined in the PWE3 Architecture [PWARCH]. The layering model is 192 intended to sufficiently isolate PW services from the underlying PSN 193 layer that carries the emulated service. This is done at the same 194 time as providing a standard means for connecting any supported 195 services to any supported PSNs. 197 The first layer known as the service layer contains service-specific 198 modules such as the one defined in this document. These modules 199 define service-specific management objects that interface or 200 collaborate with existing MIB modules for the native version of the 201 service. The service-specific module "glues" the standard module to 202 the PWE MIB framework. 204 The next layer of the PWE MIB framework is comprised of the PW-MIB 205 module [PWMIB]. This module is used to configure general parameters 206 of PW connections that are common to all types of emulated services 207 and PSNs. This layer is connected to the service-specific layer 208 above, and the PSN layer below. 210 The PSN layer provides PSN-specific modules for each type of PSN. 211 These modules associate the PW with one or more "tunnels" that carry 212 the service over the PSN. These modules are defined in other 213 documents. This module is used to "glue" the PW service to the 214 underlying PSN-specific MIB modules. In the case of MPLS, for 215 example, the PW-MPLS MIB [PWMPLSMIB] is used to connect the PW 216 service to either the MPLS-LDP [LDPMIB] or MPLS-TE [TEMIB] MIBs. 218 [PWTC] defines some of the object types used in these modules. 220 7. ATM-PW MIB Usage 222 This section provides an example of using the MIB objects described 223 in section 9 to set up an ATM PW. While this example is not meant to 224 illustrate every permutation of the MIB, it is intended as an aid in 225 the understanding of some key concepts. It is meant to be read after 226 going through the MIB itself. See [PWMIB] for an example of setting 227 up a PSN Tunnel. 229 The following example illustrates how a user will set up an AAL5 ATM 230 PW on a switch/router with cells entering the switch/router through 231 ATM Interface with IfIndex 1000 [IFMIB], VPI 1 and VCI 100 (from ATM 232 Network to PSN - outbound direction) and on the way back, it goes out 233 of the switch/router through ATM Interface 1000 with VPI 1 and VCI 234 100 (PSN to ATM Network - inbound direction) 236 First create an entry in PW MIB with pwType atmAal5SduVcc(2), then 237 create entries in pwAtmCfg table, inbound and outbound tables. 239 In PW ATM MIB 240 In pwAtmCfgTable: 242 pwAtmCfgMaxCellConcatenation 29 243 pwAtmCfgTimeoutMode enabled(3) 244 pwAtmClpQosMapping false(0) --CLP will not be mapped to QoS 245 pwAtmOamCellSupported true(1) --OAM cells will be supported 247 In pwAtmOutboundTable: 248 { 249 pwAtmOutboundAtmIf 1000 --Outbound AtmIf 250 pwAtmOutboundVpi 1 --Outbound VPI 251 pwAtmOutboundVci 100 --Outbound VCI 252 pwAtmOutboundTrafficParamDescr 0.0 --Best Effort 253 pwAtmOutboundRowStatus createAndGo 254 } 256 In pwAtmInboundTable 257 { 258 pwAtmInboundAtmIf 1000 --Inbound AtmIf 259 pwAtmInboundVpi 1 --Inbound VPI 260 pwAtmInboundVci 100 --Inbound VCI 261 pwAtmInboundTrafficParamDescr 0.0 --Best Effort 262 pwAtmInboundRowStatus createAndGo 264 } 266 8. Structure of the MIB module 268 This MIB consists of 4 types of tables; 269 It is important to note that the TrafficParamDescr Table is not 270 defined as part of this MIB although an object pointing to such 271 table entry exist in all configuration tables of this MIB module. 272 Users can refer to any ATM TrafficDescr (TD) Table if there is a 273 need to overwrite the TD assigned to the ATM endpoint in the ATM 274 service MIB [AToM]. 275 - PW ATM Cfg Table A table for generic parameters for ATM PW 276 configuration that is applicable for each ATM PW. 277 - PW ATM Outbound Table There are 2 tables to configure an 278 outbound ATM PW depending on the type of service. One table for 279 1: 1 service, and the other for N:1 service and transparent cell 280 mode [ATMTRANS]. 281 - PW ATM Inbound Table There are 2 tables to configure an inbound 282 ATM PW depending on the type of service. One table for 1: 1 283 service, and the other for N:1 service and transparent cell mode. 285 - PW ATM Perf Table There are 3 tables each contains the relevant 286 time dependent statistics for an ATM PW Entry. There is a current 287 table, 15 minutes interval table and one day interval table. The 288 tables are aligned with statistic model of other PW services. 290 9. Object definition 292 PW-ATM-MIB DEFINITIONS ::= BEGIN 294 IMPORTS 295 MODULE-IDENTITY, OBJECT-TYPE, 296 Counter32, Unsigned32, mib-2 297 FROM SNMPv2-SMI 299 MODULE-COMPLIANCE, OBJECT-GROUP 300 FROM SNMPv2-CONF 302 TruthValue, RowStatus, RowPointer 303 FROM SNMPv2-TC 305 PerfCurrentCount, PerfIntervalCount 306 FROM PerfHist-TC-MIB 308 InterfaceIndex 309 FROM IF-MIB 311 pwIndex 312 FROM PW-STD-MIB 314 AtmVpIdentifier, AtmVcIdentifier 315 FROM ATM-TC-MIB; 317 pwAtmMIB MODULE-IDENTITY 318 LAST-UPDATED "200804290000Z" -- 2008 319 ORGANIZATION "Pseudo-Wire Emulation Edge-to-Edge (PWE3) 320 Working Group" 321 CONTACT-INFO 322 "Senthilkumar Sathappan 323 Postal: 1000 Marconi Drive 324 Warrendale PA 15086 325 Tel: +1-724-742-6147 326 Email: senthilkumar.sathappan@marconi.com 328 Marichetty Venkatesan 329 Postal: 1000 Marconi Drive 330 Warrendale PA 15086 331 Tel: +1-724-742-7058 332 Email: venkatesan.marichetty@marconi.com 334 Thomas D. Nadeau 335 Postal: Cisco Systems, Inc. 336 250 Apollo Drive 337 Chelmsford, MA 01824 338 Tel: +1-978-497-3051 339 Email: tnadeau@cisco.com 341 Orly Nicklass 342 Postal: RADVISION Ltd. 343 24 Raul Wallenberg 344 Tel Aviv, Israel 345 Email: orlyn@radvision.com 347 Discussion and general questions should be posed to 348 the PWE3 Working Group (pwe3@ietf.org)." 350 DESCRIPTION 351 "This MIB contains managed object definitions for 352 Pseudo Wire emulation of ATM over Packet Switched 353 Networks (PSN). 355 This MIB supplements the PW-STD-MIB module. 356 The PW-STD-MIB contains structures and MIB associations 357 generic to Pseudo-Wire (PW) emulation. PW-specific 358 MIBs (such as this) contain config and stats for specific 359 PW types. 361 Copyright (C) The IETF Trust (2008). This version of 362 this MIB module is part of RFC XXXX; see the RFC itself for 363 full legal notices. 364 -- RFC Ed.: replace XXXX with actual RFC number & remove this 365 note" 367 -- Revision history. 369 REVISION "200804290000Z" -- 2008 370 DESCRIPTION "Initial version published as RFC XXXX." 371 -- RFC Ed.: replace XXXX with actual RFC number & remove this 372 -- note" 374 ::= { mib-2 YYY } 375 -- RFC Editor: replace YYY with IANA-assigned number & remove this 376 -- note. Please see IANA considerations section. 378 -- Top-level components of this MIB 380 pwAtmNotifications OBJECT IDENTIFIER ::= { pwAtmMIB 0 } 381 pwAtmObjects OBJECT IDENTIFIER ::= { pwAtmMIB 1 } 382 pwAtmConformance OBJECT IDENTIFIER ::= { pwAtmMIB 2 } 384 -- ATM PW PSN Bound(Outbound) Table for 1 to 1 connection 386 pwAtmOutboundTable OBJECT-TYPE 387 SYNTAX SEQUENCE OF PwAtmOutboundEntry 388 MAX-ACCESS not-accessible 389 STATUS current 390 DESCRIPTION 391 "This table specifies the information for an ATM PW to 392 be carried over PSN in the outbound direction. An 393 entry is created in this table for every entry in 394 the pwTable with a pwType equal to one of the following: 395 atmAal5SduVcc(2), atmCell1to1Vcc(12), atmCell1to1Vpc(13) 396 or atmAal5PduVcc(14), or atmTransparent(3)." 397 ::= { pwAtmObjects 1 } 399 pwAtmOutboundEntry OBJECT-TYPE 400 SYNTAX PwAtmOutboundEntry 401 MAX-ACCESS not-accessible 402 STATUS current 403 DESCRIPTION 404 "A row in this table represents an ATM PW that needs to be 405 adapted and carried over PSN. This table is indexed by 406 pwIndex from pwTable. Unless otherwise specified, all 407 writeable objects in this table MUST NOT be changed after 408 row activation in the generic pwTable and values must 409 persist after reboot." 410 REFERENCE 411 "See [PWMIB] " 413 INDEX { pwIndex } 414 ::= { pwAtmOutboundTable 1 } 416 PwAtmOutboundEntry ::= SEQUENCE { 417 pwAtmOutboundAtmIf InterfaceIndex, 418 pwAtmOutboundVpi AtmVpIdentifier, 419 pwAtmOutboundVci AtmVcIdentifier, 420 pwAtmOutboundTrafficParamDescr RowPointer, 421 pwAtmOutboundRowStatus RowStatus 422 } 424 pwAtmOutboundAtmIf OBJECT-TYPE 425 SYNTAX InterfaceIndex 426 MAX-ACCESS read-create 427 STATUS current 428 DESCRIPTION 429 "The ATM Interface that receives cells from the ATM 430 network." 431 ::= { pwAtmOutboundEntry 1 } 433 pwAtmOutboundVpi OBJECT-TYPE 434 SYNTAX AtmVpIdentifier 435 MAX-ACCESS read-create 436 STATUS current 437 DESCRIPTION 438 "VPI value of this ATM PW. The value may indicate the 439 translated value when egress generates new VPI." 440 ::= { pwAtmOutboundEntry 2 } 442 pwAtmOutboundVci OBJECT-TYPE 443 SYNTAX AtmVcIdentifier 444 MAX-ACCESS read-create 445 STATUS current 446 DESCRIPTION 447 "VCI value of this ATM PW. The value may indicate the 448 translated value when egress generates new VCI." 449 ::= { pwAtmOutboundEntry 3 } 451 pwAtmOutboundTrafficParamDescr OBJECT-TYPE 452 SYNTAX RowPointer 453 MAX-ACCESS read-create 454 STATUS current 455 DESCRIPTION 456 "This object represents a pointer to an ATM traffic parameter 457 specific row in either a private or standard table which 458 will be employed while receiving cells from the ATM network. 459 This row should contain a set of self-consistent ATM traffic 460 parameters including the ATM traffic service category. 461 A value of 0.0 indicates Best Effort" 462 ::= { pwAtmOutboundEntry 4 } 464 pwAtmOutboundRowStatus OBJECT-TYPE 465 SYNTAX RowStatus 466 MAX-ACCESS read-create 467 STATUS current 468 DESCRIPTION 469 "This Object is used to create, modify or delete a row in 470 this table. Unless otherwise specified, all writeable 471 objects in this table MUST NOT be changed after row 472 activation as explained in the pwAtmOutboundEntry " 473 ::= { pwAtmOutboundEntry 5 } 475 -- End of ATM PW Outbound Table 477 -- ATM PW CE Bound(Inbound) Table for 1 to 1 mode 479 pwAtmInboundTable OBJECT-TYPE 480 SYNTAX SEQUENCE OF PwAtmInboundEntry 481 MAX-ACCESS not-accessible 482 STATUS current 483 DESCRIPTION 484 "This table specifies the information for an ATM PW in the 485 Inbound direction." 486 ::= { pwAtmObjects 3 } 488 pwAtmInboundEntry OBJECT-TYPE 489 SYNTAX PwAtmInboundEntry 490 MAX-ACCESS not-accessible 491 STATUS current 492 DESCRIPTION 493 "A row in this table represents an ATM PW that needs to be 494 sent into the ATM Network after reconstructing cells from 495 Packets received from a PSN. This table is indexed by 496 pwIndex from pwTable. An entry is created in this table 497 for every entry in the pwTable with a 498 pwType equal to one of the following: 499 atmAal5SduVcc(2), atmCell1to1Vcc(12), atmCell1to1Vpc(13,) 500 or atmAal5PduVcc(14), or atmTransparent(3).Unless otherwise 501 specified, all writeable objects in this table MUST NOT 502 be changed after row activation in the generic pwTable 503 and values must persist after reboot." 504 REFERENCE 505 "See [PWMIB] " 507 INDEX { pwIndex } 508 ::= { pwAtmInboundTable 1 } 510 PwAtmInboundEntry ::= SEQUENCE { 511 pwAtmInboundAtmIf InterfaceIndex, 512 pwAtmInboundVpi AtmVpIdentifier, 513 pwAtmInboundVci AtmVcIdentifier, 514 pwAtmInboundTrafficParamDescr RowPointer, 515 pwAtmInboundRowStatus RowStatus 516 } 518 pwAtmInboundAtmIf OBJECT-TYPE 519 SYNTAX InterfaceIndex 520 MAX-ACCESS read-create 521 STATUS current 522 DESCRIPTION 523 "The ATM Interface that sends cells into the ATM network 524 after reconstructing cells from packets received from 525 a PSN." 526 ::= { pwAtmInboundEntry 1 } 528 pwAtmInboundVpi OBJECT-TYPE 529 SYNTAX AtmVpIdentifier 530 MAX-ACCESS read-create 531 STATUS current 532 DESCRIPTION 533 "VPI value of this ATM PW. 534 If the pwType is atmTransparent then the value will 535 be set to zero." 536 ::= { pwAtmInboundEntry 2 } 538 pwAtmInboundVci OBJECT-TYPE 539 SYNTAX AtmVcIdentifier 540 MAX-ACCESS read-create 541 STATUS current 542 DESCRIPTION 543 "VCI value of this ATM PW. 544 If the pwType is atmTransparent atmCell1to1Vpc or 545 atmCellNto1Vpc then the value will be set to zero." 546 ::= { pwAtmInboundEntry 3 } 548 pwAtmInboundTrafficParamDescr OBJECT-TYPE 549 SYNTAX RowPointer 550 MAX-ACCESS read-create 551 STATUS current 552 DESCRIPTION 553 "This object represents a pointer to a ATM traffic parameter 554 specific row in either a private or standard table which will 555 be employed while transmit into the ATM network. This table 556 contains a set of self-consistent ATM traffic parameters 557 including the ATM traffic service category. A value of 0.0 558 indicates Best Effort." 560 ::= { pwAtmInboundEntry 4 } 562 pwAtmInboundRowStatus OBJECT-TYPE 563 SYNTAX RowStatus 564 MAX-ACCESS read-create 565 STATUS current 566 DESCRIPTION 567 "This Object is used to create, modify or delete a row in 568 this table.Unless otherwise specified, all writeable 569 objects in this table MUST NOT be changed after row 570 activation as explained in the pwAtmInboundEntry " 571 ::= { pwAtmInboundEntry 5 } 573 -- End of ATM PW Inbound Table 575 --Generic ATM PW table for all types of ATM PW connection. 577 pwAtmCfgTable OBJECT-TYPE 578 SYNTAX SEQUENCE OF PwAtmCfgEntry 579 MAX-ACCESS not-accessible 580 STATUS current 581 DESCRIPTION 582 "This table specifies generic information for an ATM PW 583 to be carried over PSN in any mode." 584 ::= { pwAtmObjects 5 } 585 pwAtmCfgEntry OBJECT-TYPE 586 SYNTAX PwAtmCfgEntry 587 MAX-ACCESS not-accessible 588 STATUS current 589 DESCRIPTION 590 "This table contains a set of parameters for 591 the ATM PW that needs to be adapted and carried 592 over PSN. This table is indexed by pwIndex from 593 pwTable. An entry is created for every newly ATM 594 type associated pwIndex in the pwTable. Unless 595 otherwise specified, all read-write objects in 596 this table MAY be changed when the PW is defined 597 as not active and all RW objects values must 598 persist after reboot" 599 REFERENCE 600 "See [PWMIB] " 602 INDEX { pwIndex } 603 ::= { pwAtmCfgTable 1 } 605 PwAtmCfgEntry ::= SEQUENCE { 606 pwAtmCfgMaxCellConcatenation Unsigned32, 607 pwAtmCfgFarEndMaxCellConcatenation Unsigned32, 608 pwAtmCfgTimeoutMode INTEGER, 609 pwAtmClpQosMapping TruthValue 610 } 612 pwAtmCfgMaxCellConcatenation OBJECT-TYPE 613 SYNTAX Unsigned32 (1..29) 614 MAX-ACCESS read-write 615 STATUS current 616 DESCRIPTION 617 "The maximum number of ATM cells that can be 618 concatenated into one PW packet towards PSN. 619 In non LDP or other signaling protocol environment, 620 this object MAY be changed at anytime, but traffic 621 might be interuppted, otherwise, it may be changed 622 when PW is not active." 623 ::= { pwAtmCfgEntry 1 } 625 pwAtmCfgFarEndMaxCellConcatenation OBJECT-TYPE 626 SYNTAX Unsigned32 (1..29) 627 MAX-ACCESS read-write 628 STATUS current 629 DESCRIPTION 630 "The maximum number of ATM cells that can be 631 concatenated into one PW packet towards PSN as reported by 632 the far end. If no LDP in use, the object will either 633 return value 0 or allow setting it for calculating 634 protocol overhead." 635 ::= { pwAtmCfgEntry 2 } 637 pwAtmCfgTimeoutMode OBJECT-TYPE 638 SYNTAX INTEGER 639 { 640 notApplicable (1), 641 disabled (2), 642 enabled (3) 643 } 644 MAX-ACCESS read-write 645 STATUS current 646 DESCRIPTION 647 "This objects determines whether a packet can be 648 transmitted to the PSN based on time out expiration 649 for collecting cells or not. The actual handling of the 650 time out is implementation specific-as such this object 651 may be changed at any time under proper consideration of 652 traffic interupption effect." 653 ::= { pwAtmCfgEntry 3 } 655 pwAtmClpQosMapping OBJECT-TYPE 656 SYNTAX TruthValue 657 MAX-ACCESS read-write 658 STATUS current 659 DESCRIPTION 660 "This Object indicates whether the CLP bits should be 661 considered when setting the value in the Quality 662 of Service fields of the encapsulating protocol 663 (e.g. EXP fields of the MPLS Label Stack). Selecting 664 True allows the drop precedence to be preserved 665 across the PSN. In transparent cell transport, 666 the value of this object MUST be false(2), in other 667 cases it can be changed at any time." 668 REFERENCE 669 "See [ATMENCAP] section 12" 670 ::= { pwAtmCfgEntry 4 } 672 -- Device capable of implementing N:1, 1:1 and transparent cell 673 -- mode assumes to support the N:1 table for all 674 -- modes with respective applicable setting. 675 -- In such implementation, user can create an entry for either 676 -- 1:1 or transparent cell transport modes only 677 -- in pwAtmInboundNto1Table. The side effect of such 678 -- will be an automatic create of the respective line in the 679 -- pwAtmOutboundNto1Table. 681 -- ATM PW Outbound Table for N to 1 connection 683 pwAtmOutboundNto1Table OBJECT-TYPE 684 SYNTAX SEQUENCE OF PwAtmOutboundNto1Entry 685 MAX-ACCESS not-accessible 686 STATUS current 687 DESCRIPTION 688 "This table specifies the information for an ATM PW to 689 be carried over PSN in the outbound direction. Up to 690 N entries can be created in this table for every 691 entry in the pwTable with a pwType equal to: 692 atmCellNto1Vcc(9), or atmCellNto1Vpc(10). 693 An entry can be created only when the VP/VC are known. 694 A single entry will be created in this table for every 695 entry in the pwTable with a pwType equal to 696 one of the following: atmCell1to1Vcc(12), or 697 atmCell1to1Vpc(13), or atmAal5PduVcc(14), or 698 atmAal5SduVcc(2), or atmTransparent(3). 699 " 700 ::= { pwAtmObjects 6 } 702 pwAtmOutboundNto1Entry OBJECT-TYPE 703 SYNTAX PwAtmOutboundNto1Entry 704 MAX-ACCESS not-accessible 705 STATUS current 706 DESCRIPTION 707 "A row in this table represents an ATM PW that needs to be 708 adapted and carried over PSN. This table is indexed by 709 pwIndex from pwTable and the ATM interface with VPL/ VCLs. 710 In atmTransparent(3), Vpi and VCi will be 0xFFFF 711 during set operation. 712 Unless otherwise specified, all read-create objects in this 713 table MUST NOT be changed after row activation 714 and SHOULD remain unchanged after reboot." 715 INDEX { pwIndex, pwAtmOutboundNto1AtmIf , 716 pwAtmOutboundNto1Vpi, 717 pwAtmOutboundNto1Vci } 718 ::= { pwAtmOutboundNto1Table 1 } 720 PwAtmOutboundNto1Entry ::= SEQUENCE { 721 pwAtmOutboundNto1AtmIf InterfaceIndex, 722 pwAtmOutboundNto1Vpi AtmVpIdentifier, 723 pwAtmOutboundNto1Vci AtmVcIdentifier, 724 pwAtmOutboundNto1RowStatus RowStatus, 725 pwAtmOutboundNto1TrafficParamDescr RowPointer, 726 pwAtmOutboundNto1MappedVpi AtmVpIdentifier, 727 pwAtmOutboundNto1MappedVci AtmVcIdentifier 728 } 730 pwAtmOutboundNto1AtmIf OBJECT-TYPE 731 SYNTAX InterfaceIndex 732 MAX-ACCESS not-accessible 733 STATUS current 734 DESCRIPTION 735 "The ATM Interface that receives cells from the ATM network." 736 ::= { pwAtmOutboundNto1Entry 1 } 738 pwAtmOutboundNto1Vpi OBJECT-TYPE 739 SYNTAX AtmVpIdentifier 740 MAX-ACCESS not-accessible 741 STATUS current 742 DESCRIPTION 743 "VPI value of this ATM PW. In atmTransparent(3), 744 Vpi will be the equivalent of 0xFFFF" 745 ::= { pwAtmOutboundNto1Entry 2 } 747 pwAtmOutboundNto1Vci OBJECT-TYPE 748 SYNTAX AtmVcIdentifier 749 MAX-ACCESS not-accessible 750 STATUS current 751 DESCRIPTION 752 "VCI value of this ATM PW. In atmTransparent(3), or 753 VP case, the value will be the equivalent of 754 0xFFFF" 755 ::= { pwAtmOutboundNto1Entry 3 } 757 pwAtmOutboundNto1RowStatus OBJECT-TYPE 758 SYNTAX RowStatus 759 MAX-ACCESS read-create 760 STATUS current 761 DESCRIPTION 762 "This Object is used to create, modify or delete a row in 763 this table." 764 ::= { pwAtmOutboundNto1Entry 4 } 766 pwAtmOutboundNto1TrafficParamDescr OBJECT-TYPE 767 SYNTAX RowPointer 768 MAX-ACCESS read-create 769 STATUS current 770 DESCRIPTION 771 "This object represents a pointer to a ATM traffic parameter 772 specific row in either private or standard table which will 773 be employed while receiving cells from the ATM network. 774 This table should contain a set 775 of self-consistent ATM traffic parameters including the ATM 776 traffic service category. A value of 0.0 indicates Best 777 Effort." 779 ::= { pwAtmOutboundNto1Entry 5 } 781 pwAtmOutboundNto1MappedVpi OBJECT-TYPE 782 SYNTAX AtmVpIdentifier 783 MAX-ACCESS read-create 784 STATUS current 785 DESCRIPTION 786 "The egress generated VPI value of this ATM PW. The 787 entry is valid for PW type of atmCellNto1Vcc(9), 788 atmCellNto1Vpc(10), atmCell1to1Vcc(12), or 789 atmCell1to1Vpc(13). In other types, the value will be the 790 equivalent of 0xFFFF. Value MAY be changed when the 791 PW is defined as not active " 792 ::= { pwAtmOutboundNto1Entry 6 } 794 pwAtmOutboundNto1MappedVci OBJECT-TYPE 795 SYNTAX AtmVcIdentifier 796 MAX-ACCESS read-create 797 STATUS current 798 DESCRIPTION 799 "The egress generated VCI value of this ATM PW. The 800 entry is valid for PW type of atmCellNto1Vcc(9), 801 atmCellNto1Vpc(10), atmCell1to1Vcc(12), or 802 atmCell1to1Vpc(13. In VP case or other types, the 803 value will be the equivalent of 0xFFFF. 804 Value MAY be changed when the PW is defined 805 as not active." 806 ::= { pwAtmOutboundNto1Entry 7 } 808 -- ATM PW Inbound Table for N to 1 connection 809 pwAtmInboundNto1Table OBJECT-TYPE 810 SYNTAX SEQUENCE OF PwAtmInboundNto1Entry 811 MAX-ACCESS not-accessible 812 STATUS current 813 DESCRIPTION 814 "This table specifies the information for an ATM PW to 815 be carried over PSN in the Inbound direction. Up to 816 N entries can be created in this table for every 817 entry in the pwTable with a pwType equal to: 818 atmCellNto1Vcc(9), or atmCellNto1Vpc(10). 819 An entry can be created only when the VP/VC are known. 820 A single entry will be created in this table for every 821 entry in the pwTable with a pwType equal to 822 one of the following:atmCell1to1Vcc(12), or 823 atmCell1to1Vpc(13), or atmAal5PduVcc(14), or 824 atmAal5SduVcc(2), or atmTransparent(3)." 825 ::= { pwAtmObjects 7 } 827 pwAtmInboundNto1Entry OBJECT-TYPE 828 SYNTAX PwAtmInboundNto1Entry 829 MAX-ACCESS not-accessible 830 STATUS current 831 DESCRIPTION 832 "A row in this table represents an ATM PW that needs to be 833 adapted and carried over PSN. This table is indexed by 834 pwIndex from pwTable and the ATM interface with VPL/ VCLs. 835 In atmTransparent(3), Vpi and VCi will be 0xFFFF 836 during set operation. 837 Unless otherwise specified, all Read-Creat objects in this 838 table MUST NOT be changed after row activation 839 and SHOULD remain unchanged after reboot." 840 INDEX { pwIndex, pwAtmInboundNto1AtmIf , 841 pwAtmInboundNto1Vpi, 842 pwAtmInboundNto1Vci 843 } 844 ::= { pwAtmInboundNto1Table 1 } 846 PwAtmInboundNto1Entry ::= SEQUENCE { 847 pwAtmInboundNto1AtmIf InterfaceIndex, 848 pwAtmInboundNto1Vpi AtmVpIdentifier, 849 pwAtmInboundNto1Vci AtmVcIdentifier, 850 pwAtmInboundNto1RowStatus RowStatus, 851 pwAtmInboundNto1TrafficParamDescr RowPointer, 852 pwAtmInboundNto1MappedVpi AtmVpIdentifier, 853 pwAtmInboundNto1MappedVci AtmVcIdentifier 854 } 856 pwAtmInboundNto1AtmIf OBJECT-TYPE 857 SYNTAX InterfaceIndex 858 MAX-ACCESS not-accessible 859 STATUS current 860 DESCRIPTION 861 "The ATM Interface that receives cells from the ATM network." 862 ::= { pwAtmInboundNto1Entry 1 } 864 pwAtmInboundNto1Vpi OBJECT-TYPE 865 SYNTAX AtmVpIdentifier 866 MAX-ACCESS not-accessible 867 STATUS current 868 DESCRIPTION 869 "VPI value of this ATM PW. In atmTransparent(3), 870 Vpi will be the equivalent of 0xFFFF." 871 ::= { pwAtmInboundNto1Entry 2 } 873 pwAtmInboundNto1Vci OBJECT-TYPE 874 SYNTAX AtmVcIdentifier 875 MAX-ACCESS not-accessible 876 STATUS current 877 DESCRIPTION 878 "VCI value of this ATM PW. In atmTransparent(3), or 879 VP case, the value will be the equivalent of 880 0xFFFF" 881 ::= { pwAtmInboundNto1Entry 3 } 883 pwAtmInboundNto1RowStatus OBJECT-TYPE 884 SYNTAX RowStatus 885 MAX-ACCESS read-create 886 STATUS current 887 DESCRIPTION 888 "This Object is used to create, modify or delete a row in 889 this table." 890 ::= { pwAtmInboundNto1Entry 4 } 892 pwAtmInboundNto1TrafficParamDescr OBJECT-TYPE 893 SYNTAX RowPointer 894 MAX-ACCESS read-create 895 STATUS current 896 DESCRIPTION 897 "This object represents a pointer to a ATM traffic parameter 898 specific row in either private or standard table which will 899 be employed while receiving cells from the ATM network. 900 This table should contain a set 901 of self-consistent ATM traffic parameters including the ATM 902 traffic service category. A value of 0.0 indicates Best 903 Effort." 905 ::= { pwAtmInboundNto1Entry 5 } 907 pwAtmInboundNto1MappedVpi OBJECT-TYPE 908 SYNTAX AtmVpIdentifier 909 MAX-ACCESS read-create 910 STATUS current 911 DESCRIPTION 912 "The generated VPI value of this ATM PW. The 913 entry is valid for PW type of atmCellNto1Vcc(9), 914 atmCellNto1Vpc(10), atmCell1to1Vcc(12), or 915 atmCell1to1Vpc(13). In other types, the value will be the 916 equivalent of 0xFFFF. Value MAY be changed when the 917 PW is defined as not active." 918 ::= { pwAtmInboundNto1Entry 6 } 920 pwAtmInboundNto1MappedVci OBJECT-TYPE 921 SYNTAX AtmVcIdentifier 922 MAX-ACCESS read-create 923 STATUS current 924 DESCRIPTION 925 "The generated VCI value of this ATM PW. The 926 entry is valid for PW type of atmCellNto1Vcc(9), 927 atmCellNto1Vpc(10), atmCell1to1Vcc(12), or 928 atmCell1to1Vpc(13. In VP case or other types, the 929 value will be the equivalent of 0xFFFF. 930 Value MAY be changed when the 931 PW is defined as not active." 932 ::= { pwAtmInboundNto1Entry 7 } 934 -- ATM PW Outbound Perf Table 936 -- The following supplement the counters presented in the 937 -- PW generic MIB 938 -- ATM PW Performance Current Table. 940 pwAtmPerfCurrentTable OBJECT-TYPE 941 SYNTAX SEQUENCE OF PwAtmPerfCurrentEntry 942 MAX-ACCESS not-accessible 943 STATUS current 944 DESCRIPTION 945 "The current 15 minute interval counts are in 946 this table. 947 This table provides performance information per ATM PW." 948 ::= { pwAtmObjects 8 } 950 pwAtmPerfCurrentEntry OBJECT-TYPE 951 SYNTAX PwAtmPerfCurrentEntry 952 MAX-ACCESS not-accessible 953 STATUS current 954 DESCRIPTION 955 "An entry in this table is created by the agent for every 956 pwAtmCfgTable entry. After 15 minutes, the contents of this 957 table entry are copied to a new entry in the 958 pwAtmPerfInterval table and the counts in this entry 959 are reset to zero." 960 INDEX { pwIndex } 961 ::= { pwAtmPerfCurrentTable 1 } 963 PwAtmPerfCurrentEntry ::= SEQUENCE { 964 pwAtmPerfCurrentMissingPkts PerfCurrentCount, 965 pwAtmPerfCurrentPktsReOrder PerfCurrentCount, 966 pwAtmPerfCurrentPktsMisOrder PerfCurrentCount, 967 pwAtmPerfCurrentPktsTimeout PerfCurrentCount, 968 pwAtmPerfCurrentCellsXmit PerfCurrentCount, 969 pwAtmPerfCurrentCellsDropped PerfCurrentCount, 970 pwAtmPerfCurrentCellsReceived PerfCurrentCount, 971 pwAtmPerfCurrentUnknownCells PerfCurrentCount 972 } 974 pwAtmPerfCurrentMissingPkts OBJECT-TYPE 975 SYNTAX PerfCurrentCount 976 MAX-ACCESS read-only 977 STATUS current 978 DESCRIPTION 979 "Number of missing packets (as detected via control word 980 sequence number gaps)." 981 ::= { pwAtmPerfCurrentEntry 1 } 983 pwAtmPerfCurrentPktsReOrder OBJECT-TYPE 984 SYNTAX PerfCurrentCount 985 MAX-ACCESS read-only 986 STATUS current 987 DESCRIPTION 988 "Number of packets detected out of sequence (via control 989 word sequence number), but successfully re-ordered. 990 Note: some implementations may not support this Feature." 991 ::= { pwAtmPerfCurrentEntry 2 } 993 pwAtmPerfCurrentPktsMisOrder OBJECT-TYPE 994 SYNTAX PerfCurrentCount 995 MAX-ACCESS read-only 996 STATUS current 997 DESCRIPTION 998 "Number of packets detected out of order (via control word 999 sequence numbers)." 1000 ::= { pwAtmPerfCurrentEntry 3 } 1002 pwAtmPerfCurrentPktsTimeout OBJECT-TYPE 1003 SYNTAX PerfCurrentCount 1004 MAX-ACCESS read-only 1005 STATUS current 1006 DESCRIPTION 1007 "Number of packets transmitted due to timeout expiration 1008 while attempting to collect cells." 1009 ::= { pwAtmPerfCurrentEntry 4 } 1011 pwAtmPerfCurrentCellsXmit OBJECT-TYPE 1012 SYNTAX PerfCurrentCount 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION 1016 "Number of transmitted cells." 1017 ::= { pwAtmPerfCurrentEntry 5 } 1019 pwAtmPerfCurrentCellsDropped OBJECT-TYPE 1020 SYNTAX PerfCurrentCount 1021 MAX-ACCESS read-only 1022 STATUS current 1023 DESCRIPTION 1024 "Number of dropped cells." 1025 ::= { pwAtmPerfCurrentEntry 6 } 1027 pwAtmPerfCurrentCellsReceived OBJECT-TYPE 1028 SYNTAX PerfCurrentCount 1029 MAX-ACCESS read-only 1030 STATUS current 1031 DESCRIPTION 1032 "Number of received cells." 1033 ::= { pwAtmPerfCurrentEntry 7 } 1035 pwAtmPerfCurrentUnknownCells OBJECT-TYPE 1036 SYNTAX PerfCurrentCount 1037 MAX-ACCESS read-only 1038 STATUS current 1039 DESCRIPTION 1040 "Number of cells received from the PSN with unknown VPI or 1041 VCI values. This object is relevant only in N:1 mode." 1042 ::= { pwAtmPerfCurrentEntry 8 } 1044 -- End ATM PW Performance Current Interval Table 1046 -- ATM PW Performance Interval Table. 1048 pwAtmPerfIntervalTable OBJECT-TYPE 1049 SYNTAX SEQUENCE OF PwAtmPerfIntervalEntry 1050 MAX-ACCESS not-accessible 1051 STATUS current 1052 DESCRIPTION 1053 "This table provides performance information per ATM PW 1054 similar to the pwAtmPerfCurrentTable above. However, 1055 these counts represent historical 15 minute intervals. 1056 Typically, this table will have a maximum of 96 entries 1057 for a 24 hour period. " 1058 ::= { pwAtmObjects 9 } 1060 pwAtmPerfIntervalEntry OBJECT-TYPE 1061 SYNTAX PwAtmPerfIntervalEntry 1062 MAX-ACCESS not-accessible 1063 STATUS current 1064 DESCRIPTION 1065 "An entry in this table is created by the agent for 1066 every pwAtmPerfCurrentEntry that is 15 minutes old. 1067 The contents of the Current entry are copied to the new 1068 entry here. The Current entry, then resets its counts 1069 to zero for the next current 15 minute interval. " 1070 INDEX { pwIndex, pwAtmPerfIntervalNumber } 1071 ::= { pwAtmPerfIntervalTable 1 } 1073 PwAtmPerfIntervalEntry ::= SEQUENCE { 1074 pwAtmPerfIntervalNumber Unsigned32, 1075 pwAtmPerfIntervalValidData TruthValue, 1076 pwAtmPerfIntervalDuration Unsigned32, 1077 pwAtmPerfIntervalMissingPkts PerfIntervalCount, 1078 pwAtmPerfIntervalPktsReOrder PerfIntervalCount, 1079 pwAtmPerfIntervalPktsMisOrder PerfIntervalCount, 1080 pwAtmPerfIntervalPktsTimeout PerfIntervalCount, 1081 pwAtmPerfIntervalCellsXmit PerfIntervalCount, 1082 pwAtmPerfIntervalCellsDropped PerfIntervalCount, 1083 pwAtmPerfIntervalCellsReceived PerfIntervalCount, 1084 pwAtmPerfIntervalUnknownCells PerfIntervalCount 1085 } 1087 pwAtmPerfIntervalNumber OBJECT-TYPE 1088 SYNTAX Unsigned32 (1..96) 1089 MAX-ACCESS not-accessible 1090 STATUS current 1091 DESCRIPTION 1092 "A number (normally between 1 and 96 to cover a 24 hour 1093 period) which identifies the interval for which the set 1094 of statistics is available. The interval identified by 1 1095 is the most recently completed 15 minute interval, and 1096 the interval identified by N is the interval immediately 1097 preceding the one identified by N-1. The minimum range of 1098 N is 1 through 4. The default range is 1 through 32. The 1099 maximum value of N is 96." 1100 ::= { pwAtmPerfIntervalEntry 1 } 1102 pwAtmPerfIntervalValidData OBJECT-TYPE 1103 SYNTAX TruthValue 1104 MAX-ACCESS read-only 1105 STATUS current 1106 DESCRIPTION 1107 "This variable indicates if the data for this interval 1108 is valid." 1109 ::= { pwAtmPerfIntervalEntry 2 } 1111 pwAtmPerfIntervalDuration OBJECT-TYPE 1112 SYNTAX Unsigned32 1113 MAX-ACCESS read-only 1114 STATUS current 1115 DESCRIPTION 1116 "The duration of a particular interval in seconds, 1117 Adjustments in the system's time-of-day clock, may 1118 cause the interval to be greater or less than, the 1119 normal value. Therefore this actual interval value 1120 is provided." 1121 ::= { pwAtmPerfIntervalEntry 3 } 1123 pwAtmPerfIntervalMissingPkts OBJECT-TYPE 1124 SYNTAX PerfIntervalCount 1125 MAX-ACCESS read-only 1126 STATUS current 1127 DESCRIPTION 1128 "Number of missing packets (as detected via control 1129 word sequence number gaps)." 1130 ::= { pwAtmPerfIntervalEntry 4 } 1132 pwAtmPerfIntervalPktsReOrder OBJECT-TYPE 1133 SYNTAX PerfIntervalCount 1134 MAX-ACCESS read-only 1135 STATUS current 1136 DESCRIPTION 1137 "Number of packets detected out of sequence (via control 1138 word sequence number), but successfully re-ordered. 1139 Note: some implementations may not support this 1140 Feature." 1141 ::= { pwAtmPerfIntervalEntry 5 } 1143 pwAtmPerfIntervalPktsMisOrder OBJECT-TYPE 1144 SYNTAX PerfIntervalCount 1145 MAX-ACCESS read-only 1146 STATUS current 1147 DESCRIPTION 1148 "Number of packets detected out of order (via control word 1149 sequence numbers)." 1150 ::= { pwAtmPerfIntervalEntry 6 } 1152 pwAtmPerfIntervalPktsTimeout OBJECT-TYPE 1153 SYNTAX PerfIntervalCount 1154 MAX-ACCESS read-only 1155 STATUS current 1156 DESCRIPTION 1157 "Number of packets transmitted due to timeout expiration." 1158 ::= { pwAtmPerfIntervalEntry 7 } 1160 pwAtmPerfIntervalCellsXmit OBJECT-TYPE 1161 SYNTAX PerfIntervalCount 1162 MAX-ACCESS read-only 1163 STATUS current 1164 DESCRIPTION 1165 "Number of transmitted cells." 1166 ::= { pwAtmPerfIntervalEntry 8 } 1168 pwAtmPerfIntervalCellsDropped OBJECT-TYPE 1169 SYNTAX PerfIntervalCount 1170 MAX-ACCESS read-only 1171 STATUS current 1172 DESCRIPTION 1173 "Number of dropped cells." 1174 ::= { pwAtmPerfIntervalEntry 9 } 1176 pwAtmPerfIntervalCellsReceived OBJECT-TYPE 1177 SYNTAX PerfIntervalCount 1178 MAX-ACCESS read-only 1179 STATUS current 1180 DESCRIPTION 1181 "Number of received cells." 1182 ::= { pwAtmPerfIntervalEntry 10 } 1184 pwAtmPerfIntervalUnknownCells OBJECT-TYPE 1185 SYNTAX PerfIntervalCount 1186 MAX-ACCESS read-only 1187 STATUS current 1188 DESCRIPTION 1189 "Number of cells received from the PSN with unknown VPI or 1190 VCI values. This object is relevant only in N:1 mode." 1191 ::= { pwAtmPerfIntervalEntry 11 } 1193 -- End ATM PW Performance Interval Table 1195 -- ATM PW 1day Performance Table 1196 pwAtmPerf1DayIntervalTable OBJECT-TYPE 1197 SYNTAX SEQUENCE OF PwAtmPerf1DayIntervalEntry 1198 MAX-ACCESS not-accessible 1199 STATUS current 1200 DESCRIPTION 1201 "This table provides performance information per ATM PW 1202 similar to the pwAtmPerfIntervalTable above. However, 1203 these counters represent historical 1 day intervals up to 1204 one full month." 1205 ::= { pwAtmObjects 10 } 1207 pwAtmPerf1DayIntervalEntry OBJECT-TYPE 1208 SYNTAX PwAtmPerf1DayIntervalEntry 1209 MAX-ACCESS not-accessible 1210 STATUS current 1211 DESCRIPTION 1212 "An entry is created in this table by the agent 1213 for every entry in the pwAtmCfgTable table." 1214 INDEX { pwIndex,pwAtmPerf1DayIntervalNumber } 1215 ::= { pwAtmPerf1DayIntervalTable 1 } 1217 PwAtmPerf1DayIntervalEntry ::= SEQUENCE { 1218 pwAtmPerf1DayIntervalNumber Unsigned32, 1219 pwAtmPerf1DayIntervalValidData TruthValue, 1220 pwAtmPerf1DayIntervalDuration Unsigned32, 1221 pwAtmPerf1DayIntervalMissingPkts Counter32, 1222 pwAtmPerf1DayIntervalPktsReOrder Counter32, 1223 pwAtmPerf1DayIntervalPktsMisOrder Counter32, 1224 pwAtmPerf1DayIntervalPktsTimeout Counter32, 1225 pwAtmPerf1DayIntervalCellsXmit Counter32, 1226 pwAtmPerf1DayIntervalCellsDropped Counter32, 1227 pwAtmPerf1DayIntervalCellsReceived Counter32, 1228 pwAtmPerf1DayIntervalUnknownCells Counter32 1229 } 1231 pwAtmPerf1DayIntervalNumber OBJECT-TYPE 1232 SYNTAX Unsigned32 (1..365) 1233 MAX-ACCESS not-accessible 1234 STATUS current 1235 DESCRIPTION 1236 "The number of interval, where 1 indicates current day 1237 measured period and 2 and above indicate previous days 1238 respectively" 1239 ::= { pwAtmPerf1DayIntervalEntry 1 } 1241 pwAtmPerf1DayIntervalValidData OBJECT-TYPE 1242 SYNTAX TruthValue 1243 MAX-ACCESS read-only 1244 STATUS current 1245 DESCRIPTION 1246 "This object indicates if the data for this interval 1247 is valid." 1248 ::= { pwAtmPerf1DayIntervalEntry 2 } 1250 pwAtmPerf1DayIntervalDuration OBJECT-TYPE 1251 SYNTAX Unsigned32 1252 MAX-ACCESS read-only 1253 STATUS current 1254 DESCRIPTION 1255 "The duration of a particular interval in seconds, 1256 Adjustments in the system's time-of-day clock, may 1257 cause the interval to be greater or less than, the 1258 normal value. Therefore this actual interval value 1259 is provided." 1260 ::= { pwAtmPerf1DayIntervalEntry 3 } 1262 pwAtmPerf1DayIntervalMissingPkts OBJECT-TYPE 1263 SYNTAX Counter32 1264 MAX-ACCESS read-only 1265 STATUS current 1266 DESCRIPTION 1267 "Number of missing packets (as detected via control word 1268 sequence number gaps)." 1269 ::= { pwAtmPerf1DayIntervalEntry 4 } 1271 pwAtmPerf1DayIntervalPktsReOrder OBJECT-TYPE 1272 SYNTAX Counter32 1273 MAX-ACCESS read-only 1274 STATUS current 1275 DESCRIPTION 1276 "Number of packets detected out of sequence (via control 1277 word sequence number), but successfully re-ordered. 1278 Note: some implementations may not support this 1279 feature." 1280 ::= { pwAtmPerf1DayIntervalEntry 5 } 1282 pwAtmPerf1DayIntervalPktsMisOrder OBJECT-TYPE 1283 SYNTAX Counter32 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "Number of packets detected out of order(via control word 1288 sequence numbers), and could not be re-ordered." 1289 ::= { pwAtmPerf1DayIntervalEntry 6 } 1291 pwAtmPerf1DayIntervalPktsTimeout OBJECT-TYPE 1292 SYNTAX Counter32 1293 MAX-ACCESS read-only 1294 STATUS current 1295 DESCRIPTION 1296 "Number of packets transmitted due to timeout expiration." 1297 ::= { pwAtmPerf1DayIntervalEntry 7 } 1299 pwAtmPerf1DayIntervalCellsXmit OBJECT-TYPE 1300 SYNTAX Counter32 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "Number of transmitted cells." 1305 ::= { pwAtmPerf1DayIntervalEntry 8 } 1307 pwAtmPerf1DayIntervalCellsDropped OBJECT-TYPE 1308 SYNTAX Counter32 1309 MAX-ACCESS read-only 1310 STATUS current 1311 DESCRIPTION 1312 "Number of dropped cells." 1313 ::= { pwAtmPerf1DayIntervalEntry 9 } 1315 pwAtmPerf1DayIntervalCellsReceived OBJECT-TYPE 1316 SYNTAX Counter32 1317 MAX-ACCESS read-only 1318 STATUS current 1319 DESCRIPTION 1320 "Number of received cells." 1321 ::= { pwAtmPerf1DayIntervalEntry 10 } 1323 pwAtmPerf1DayIntervalUnknownCells OBJECT-TYPE 1324 SYNTAX Counter32 1325 MAX-ACCESS read-only 1326 STATUS current 1327 DESCRIPTION 1328 "Number of cells received from the PSN with unknown VPI 1329 or VCI value. This object is relevant only in N:1 mode." 1330 ::= { pwAtmPerf1DayIntervalEntry 11 } 1332 -- End of ATM PW Performance table 1334 pwAtmCompliances OBJECT IDENTIFIER ::= { pwAtmConformance 1 } 1335 pwAtmGroups OBJECT IDENTIFIER ::= { pwAtmConformance 2 } 1336 pwAtmCompliance MODULE-COMPLIANCE 1337 STATUS current 1338 DESCRIPTION 1339 "The compliance statement for agent that support 1340 ATM PW." 1341 MODULE -- this module 1342 MANDATORY-GROUPS { pwAtmCfgGroup, 1343 pwAtmPerfGroup 1344 } 1346 OBJECT pwAtmCfgFarEndMaxCellConcatenation 1347 MIN-ACCESS read-only 1348 DESCRIPTION 1349 "The ability to set this object 1350 is not required." 1352 GROUP pwAtmOutbound1to1Group 1353 DESCRIPTION "This group is mandatory only for implementations 1354 that support the ATM PW 1:1 mode and not using 1355 Nto1 table." 1357 GROUP pwAtmInbound1to1Group 1358 DESCRIPTION "This group is mandatory only for implementations 1359 that support the ATM PW 1:1 mode and not using 1360 Nto1 table." 1362 GROUP pwAtmOutboundNto1Group 1363 DESCRIPTION "This group is mandatory only for implementations 1364 that support the ATM PW N:1 and transparent mode." 1366 GROUP pwAtmInboundNto1Group 1367 DESCRIPTION "This group is mandatory only for implementations 1368 that support the ATM PW N:1 and transparent mode." 1370 ::= { pwAtmCompliances 2 } 1372 -- Units of conformance. 1374 pwAtmCfgGroup OBJECT-GROUP 1375 OBJECTS {pwAtmCfgMaxCellConcatenation, 1376 pwAtmCfgFarEndMaxCellConcatenation, 1377 pwAtmCfgTimeoutMode, 1378 pwAtmClpQosMapping 1379 } 1381 STATUS current 1382 DESCRIPTION 1383 "Collection of objects for basic ATM PW 1384 config." 1385 ::= { pwAtmGroups 5 } 1387 pwAtmPerfGroup OBJECT-GROUP 1388 OBJECTS {pwAtmPerfCurrentMissingPkts, 1389 pwAtmPerfCurrentPktsReOrder, 1390 pwAtmPerfCurrentPktsMisOrder, 1391 pwAtmPerfCurrentPktsTimeout, 1392 pwAtmPerfCurrentCellsXmit, 1393 pwAtmPerfCurrentCellsDropped, 1394 pwAtmPerfCurrentCellsReceived, 1395 pwAtmPerfCurrentUnknownCells, 1396 pwAtmPerfIntervalValidData, 1397 pwAtmPerfIntervalDuration, 1398 pwAtmPerfIntervalMissingPkts, 1399 pwAtmPerfIntervalPktsReOrder, 1400 pwAtmPerfIntervalPktsMisOrder, 1401 pwAtmPerfIntervalPktsTimeout, 1402 pwAtmPerfIntervalCellsXmit, 1403 pwAtmPerfIntervalCellsDropped, 1404 pwAtmPerfIntervalCellsReceived, 1405 pwAtmPerfIntervalUnknownCells, 1406 pwAtmPerf1DayIntervalValidData, 1407 pwAtmPerf1DayIntervalDuration, 1408 pwAtmPerf1DayIntervalMissingPkts, 1409 pwAtmPerf1DayIntervalPktsReOrder, 1410 pwAtmPerf1DayIntervalPktsMisOrder, 1411 pwAtmPerf1DayIntervalPktsTimeout, 1412 pwAtmPerf1DayIntervalCellsXmit, 1413 pwAtmPerf1DayIntervalCellsDropped, 1414 pwAtmPerf1DayIntervalCellsReceived, 1415 pwAtmPerf1DayIntervalUnknownCells 1416 } 1417 STATUS current 1418 DESCRIPTION 1419 "Collection of objects for basic ATM PW Performance." 1420 ::= { pwAtmGroups 6 } 1421 pwAtmOutbound1to1Group OBJECT-GROUP 1422 OBJECTS {pwAtmOutboundAtmIf, 1423 pwAtmOutboundVpi, 1424 pwAtmOutboundVci, 1425 pwAtmOutboundTrafficParamDescr, 1426 pwAtmOutboundRowStatus 1427 } 1428 STATUS current 1429 DESCRIPTION 1430 "Collection of objects for basic 1:1 ATM PW outbound 1431 config." 1432 ::= { pwAtmGroups 7 } 1434 pwAtmInbound1to1Group OBJECT-GROUP 1435 OBJECTS {pwAtmInboundAtmIf, 1436 pwAtmInboundVpi, 1437 pwAtmInboundVci, 1438 pwAtmInboundTrafficParamDescr, 1439 pwAtmInboundRowStatus 1440 } 1441 STATUS current 1442 DESCRIPTION 1443 "Collection of objects for basic 1:1 ATM PW inbound 1444 config." 1445 ::= { pwAtmGroups 8 } 1447 pwAtmOutboundNto1Group OBJECT-GROUP 1448 OBJECTS {pwAtmOutboundNto1RowStatus, 1449 pwAtmOutboundNto1TrafficParamDescr, 1450 pwAtmOutboundNto1MappedVpi, 1451 pwAtmOutboundNto1MappedVci 1452 } 1453 STATUS current 1454 DESCRIPTION 1455 "Collection of objects for N:1 or 1:1 or transparent 1456 ATM PW outbound config." 1457 ::= { pwAtmGroups 9 } 1458 pwAtmInboundNto1Group OBJECT-GROUP 1459 OBJECTS {pwAtmInboundNto1RowStatus, 1460 pwAtmInboundNto1TrafficParamDescr, 1461 pwAtmInboundNto1MappedVpi, 1462 pwAtmInboundNto1MappedVci 1463 } 1464 STATUS current 1465 DESCRIPTION 1466 "Collection of objects for N:1 or 1:1 or transparent 1467 ATM PW inbound config." 1468 ::= { pwAtmGroups 10 } 1470 END 1472 10. Security considerations 1474 There are a number of management objects defined in this MIB module 1475 with a MAX-ACCESS clause of read-write and/or read-create. Such 1476 objects may be considered sensitive or vulnerable in some network 1477 environments. The support for SET operations in a non-secure 1478 environment without proper protection can have a negative effect on 1479 network operations. These are the tables and objects and their 1480 sensitivity/vulnerability: 1482 The pwAtmOutboundTable, pwAtmInboundTable, pwAtmCfgTable, 1483 pwAtmOutboundNto1Table, and pwAtmInboundNto1Table contain objects of 1484 ATM PW parameters on a Provider Edge (PE) device. Unauthorized 1485 access to objects in these tables could result in disruption of 1486 traffic on the network. 1488 The use of stronger mechanisms such as SNMPv3 security should be 1489 considered where possible. Specifically, SNMPv3 VACM and USM MUST be 1490 used with any SNMPV3 agent, which implements this MIB module. 1491 Administrators should consider whether read access to these objects 1492 should be allowed, since read access may be undesirable under certain 1493 circumstances. 1495 Some of the readable objects in this MIB module (i.e., objects with a 1496 MAX-ACCESS other than not-accessible) may be considered sensitive or 1497 vulnerable in some network environments. It is thus important to 1498 control even GET and/or NOTIFY access to these objects and possibly 1499 to even encrypt the values of these objects when sending them over 1500 the network via SNMP. These are the tables and objects and their 1501 sensitivity/vulnerability: 1503 The pwATMCfgTable, pwAtmPerfCurrentTable, pwAtmPerfIntervalTable and 1504 pwAtmPerf1DayIntervalTable collectively show the ATM pseudo wire 1505 connectivity topology and its performance characteristics. 1507 If an Administrator does not want to reveal this information, then 1508 these tables should be considered sensitive/vulnerable. 1510 SNMP versions prior to SNMPv3 did not include adequate security. 1511 Even if the network itself is secure (for example by using IPsec), 1512 even then, there is no control as to who on the secure network is 1513 allowed to access and GET/SET (read/change/create/delete) the objects 1514 in this MIB module. 1516 It is RECOMMENDED that implementers consider the security features as 1517 provided by the SNMPv3 framework (see [RFC3410], section 8), 1518 including full support for the SNMPv3 cryptographic mechanisms (for 1519 authentication and privacy). 1521 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1522 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1523 enable cryptographic security. It is then a customer/operator 1524 responsibility to ensure that the SNMP entity giving access to an 1525 instance of this MIB module, is properly configured to give access to 1526 the objects only to those principals (users) that have legitimate 1527 rights to indeed GET or SET (change/create/delete) them. 1529 11. IANA considerations 1531 The MIB module in this document uses the following IANA-assigned 1532 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 1534 Descriptor OBJECT IDENTIFIER value 1536 ---------- ----------------------- 1538 pwATMMIB { mib-2 XXX } 1540 Editor's Note (to be removed prior to publication): the IANA is 1541 requested to assign a value for "XXX" under the 'mib-2' subtree and 1542 to record the assignment in the SMI Numbers registry. When the 1543 assignment has been made, the RFC Editor is asked to replace "XXX" 1544 (here and in the MIB module) with the assigned value and to remove 1545 this note. 1547 12. References 1549 12.1. Normative references 1551 [PWTC] Nadeau, T., Zelig D. "Definitions for Textual 1552 Conventions and OBJECT-IDENTITIES for Pseudo-Wires 1553 Management", work-in-progress. 1555 [PWMIB] Zelig D., Nadeau T., "Pseudo Wire (PW) Management 1556 Information Base", work-in-progress. 1558 [PWMPLSMIB] Zelig et al, "Pseudo Wire (PW) Over MPLS PSN Management 1559 Information Base", work-in-progress. 1561 [ATMENCAP] Martini et al, "Encapsulation Methods for Transport 1562 of Asynchronous Transfer Mode (ATM) over MPLS 1563 Networks", RFC 4717, December 2006. 1565 [ATMTRANS] Malis et al, "PWE3 ATM Transparent Cell Transport 1566 Service", RFC 4816, February 2007. 1568 [AToM] Tesink, K., "Definitions of Managed Objects for ATM 1569 Management", RFC 2515, October 1999. 1571 [AToMTC] Noto, M., Spiegel, E. and K. Tesink, Editors, "Definitions 1572 of Textual Conventions and OBJECT-IDENTITIES for ATM 1573 Management", RFC 2514, February 1999. 1575 [LDPMIB] J. Cucchiara, H. Sjostrand, J. Luciani "Definitions 1576 of Managed Objects for the Multiprotocol 1577 Label Switching (MPLS), Label Distribution Protocol 1578 (LDP)", RFC 3815, June 2004 1580 [TEMIB] C. Srinivasan, Bloomberg L.P., A. Viswanathan, 1581 T. Nadeau, "Multiprotocol Label Switching (MPLS) 1582 Traffic Engineering (TE) Management Information Base 1583 MIB)" RFC 3812, June 2004. 1585 [IFMIB] McCloghrie, K. and F. Kastenholz, "The Interfaces 1586 Group MIB", RFC 2863, June 2000. 1588 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1589 J., Rose, M. and S. Waldbusser, "Structure of 1590 Management Information Version 2 (SMIv2)", STD 58, RFC 1591 2578, April 1999. 1593 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1594 J., Rose, M. and S. Waldbusser, "Textual Conventions 1595 for SMIv2", STD 58, RFC 2579, April 1999. 1597 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1598 J., Rose, M. and S. Waldbusser, "Conformance 1599 Statements for SMIv2", STD 58, RFC 2580, April 1999. 1601 [BCP14] S. Bradner, "Key words for use in RFCs to Indicate 1602 Requirement Levels", RFC 2119 (BCP 14), March 1997 1604 12.2. Informative references 1606 [PWREQ] Xiao et al, "Requirements for Pseudo Wire Emulation Edge- 1607 to-Edge (PWE3)", RFC 3916, September 2004. 1609 [PWARCH] Bryant S., Pate P., "PWE3 Architecture", RFC 3985, 1610 March 2005. 1612 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1613 "Introduction and Applicability Statements for 1614 Internet-Standard Management Framework", RFC 3410, 1615 December 2002. 1617 13. Acknowledgements 1619 This document was produced by the PWE3 Working Group. Special thanks 1620 to Bert Wijnen for close review and good suggestions. 1622 Authors' Addresses 1624 Orly Nicklass 1625 RADVISION Ltd. 1626 24 Raul Wallenberg St. 1627 Tel Aviv 1628 ISRAEL 1630 Phone: +972 3 7679444 1631 Email: orlyn@radvision.com 1632 Senthilkumar Sathappan 1633 Marconi Communications 1634 1000 Marconi Drive 1635 Warrendale, PA 15086 1636 USA 1638 Phone: +1-724-742-6147 1639 Email: senthilkumar.sathappan@marconi.com 1641 Marichetty Venkatesan 1642 Marconi Communications 1643 1000 Marconi Drive 1644 Warrendale, PA 15086 1645 USA 1647 Phone: +1-724-742-7058 1648 Email: venkatesan.marichetty@marconi.com 1650 Thomas D. Nadeau 1651 Cisco Systems, Inc. 1652 250 Apollo Drive 1653 Chelmsford, MA 01824 1654 USA 1656 Phone: +1-978-497-3051 1657 Email: tnadeau@cisco.com 1659 Full Copyright Statement 1661 Copyright (C) The IETF Trust (2008). 1663 This document is subject to the rights, licenses and restrictions 1664 contained in BCP 78, and except as set forth therein, the authors 1665 retain all their rights. 1667 This document and the information contained herein are provided on an 1668 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1669 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1670 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1671 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1672 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1673 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1675 Intellectual Property 1677 The IETF takes no position regarding the validity or scope of any 1678 Intellectual Property Rights or other rights that might be claimed to 1679 pertain to the implementation or use of the technology described in 1680 this document or the extent to which any license under such rights 1681 might or might not be available; nor does it represent that it has 1682 made any independent effort to identify any such rights. Information 1683 on the procedures with respect to rights in RFC documents can be 1684 found in BCP 78 and BCP 79. 1686 Copies of IPR disclosures made to the IETF Secretariat and any 1687 assurances of licenses to be made available, or the result of an 1688 attempt made to obtain a general license or permission for the use of 1689 such proprietary rights by implementers or users of this 1690 specification can be obtained from the IETF on-line IPR repository at 1691 http://www.ietf.org/ipr. 1693 The IETF invites any interested party to bring to its attention any 1694 copyrights, patents or patent applications, or other proprietary 1695 rights that may cover technology that may be required to implement 1696 this standard. Please address the information to the IETF at 1697 ietf-ipr@ietf.org.