idnits 2.17.1 draft-sathappan-pw-atm-mib-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 32 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The abstract seems to contain references ([FRMWK]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 262 has weird spacing: '...pported true(...' == Line 273 has weird spacing: '...pported true(...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (March 2002) is 8072 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: 'AToM' is mentioned on line 296, but not defined == Missing Reference: 'LDPMIB' is mentioned on line 230, but not defined == Missing Reference: 'TEMIB' is mentioned on line 230, but not defined == Unused Reference: 'VPLS' is defined on line 839, but no explicit reference was found in the text == Unused Reference: 'ENETLIKE' is defined on line 854, but no explicit reference was found in the text == Unused Reference: 'IFMIB' is defined on line 863, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'FRMWK' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWREQ' -- Possible downref: Non-RFC (?) normative reference: ref. 'VPLS' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWTC' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWMPLSMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'ENETLIKE' ** Obsolete normative reference: RFC 2233 (ref. 'IFMIB') (Obsoleted by RFC 2863) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) Summary: 18 errors (**), 0 flaws (~~), 12 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Senthilkumar Sathappan 3 Internet Draft Marichetty Venkatesan 4 Expires: September 2002 Marconi Communications 6 Thomas D. Nadeau 7 Cisco Systems, Inc. 9 March 2002 11 PW ATM Pseudo Wire (PW) Emulation Network Management 12 Information Base Using SMIv2 14 draft-sathappan-pw-atm-mib-00.txt 16 Status of this Memo 18 This document is an Internet-Draft and is in full conformance with 19 all provisions of Section 10 of RFC2026. 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 27 months and may be updated, replaced, or obsoleted by other documents 28 at any 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 Copyright (C) The Internet Society (2001). All rights reserved. 39 1.0 Abstract 41 This memo defines an experimental portion of the Management 42 Information Base (MIB) for use with network management protocols in 43 the Internet community. In particular, it describes managed objects 44 for modeling an adaptation of ATM VCs over a Packet Switch Network 45 (PSN) as defined in the PWE3 Framework [FRMWK]. 47 Table of Contents 49 1 Abstract.....................................................1 50 2 Introduction.................................................3 51 3 Terminology..................................................4 52 4 The SNMP Management Framework................................4 53 4.1 Object Definitions...........................................5 54 5 Feature Checklist............................................5 55 6 PW-MIB usage.................................................6 56 6.1 PW-ATM-MIB usage.............................................6 57 7 PW-ATM MIB Summary...........................................6 58 8 Object definitions...........................................7 59 9 Security Considerations......................................16 60 10 References...................................................18 61 11 Author's Addresses...........................................20 62 12 Full Copyright Statement.....................................20 64 2.0 Introduction 66 This document describes a Management Information Base for managing ATM VC 67 emulation over a Packet Switched Network(PSN). 69 This document follows the Requirements for Pseudo-Wire Emulation 70 Edge-to-Edge [PWREQ] document, The MIB objects closely work with the MIBs 71 described in [PWMIB] and the textual conventions defined in [PWTC]. 73 The MIB objects are defined in a way that is not specific to the PSN that 74 is emulating this service. 76 3.0 Terminology 78 This document follows the terminology used in PW framework [FRMWK]. 80 Outbound References the traffic direction where a ATM Cell 81 is received, adapted to packet, assigned a VC label, 82 and sent into the PSN. 84 Inbound The direction where packets are received 85 from the PSN, cells are reconstructed from the packet 86 payloads, and sent into the ATM Network as cells. 88 Adaptation Refers to the method of adapting a "foreign" 89 communications protocol such that it can be 90 carried by a packet switched net (the PSN). For 91 example, in a ATM service the foreign protocol 92 is ATM. The PSN may be MPLS. 94 PSN Public Switched Network. 96 PSN Tunnel A general term indicating a virtual connection 97 between the two PW edge devices. In practice 98 this connection is not limited to path-oriented 99 types of PSNs such as MPLS. An example of a non- 100 path-oriented PSN is an IP PSN. 102 Conventions used in this document 104 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 105 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 106 this document are to be interpreted as described in RFC-2119 107 [BCP14]. 109 4.0 The SNMP Management Framework 111 The SNMP Management Framework presently consists of five major 112 components: 114 o An overall architecture, described in RFC 2571 [RFC2571]. 116 o Mechanisms for describing and naming objects and events for the 117 purpose of management. The first version of this Structure of 118 Management Information (SMI) is called SMIv1 and described in STD 16, 119 RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 120 [RFC1215]. The second version, called SMIv2, is described in STD 58, 121 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 122 [RFC2580]. 124 o Message protocols for transferring management information. The 125 first version of the SNMP message protocol is called SNMPv1 and 126 described in STD 15, RFC 1157 [RFC1157]. A second version of the 127 SNMP message protocol, which is not an Internet standards track 128 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and 129 RFC 1906 [RFC1906]. The third version of the message protocol is 130 called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] 131 and RFC 2574 [RFC2574]. 133 o Protocol operations for accessing management information. The 134 first set of protocol operations and associated PDU formats is 135 described in STD 15, RFC 1157 [RFC1157]. A second set of protocol 136 operations and associated PDU formats is described in RFC 1905 137 [RFC1905]. 139 o A set of fundamental applications described in RFC 2573 140 [RFC2573] and the view-based access control mechanism described in 141 RFC 2575 [RFC2575]. 143 A more detailed introduction to the current SNMP Management Framework 144 can be found in RFC 2570 [RFC2570]. Managed objects are accessed via 145 a virtual information store, termed the Management Information Base 146 or MIB. Objects in the MIB are defined using the mechanisms defined 147 in the SMI. This memo specifies a MIB module that is compliant to the 148 SMIv2. A MIB conforming to the SMIv1 can be produced through the 149 appropriate translations. The resulting translated MIB must be 150 semantically equivalent, except where objects or events are omitted 151 because no translation is possible (use of Counter64). Some machine 152 readable information in SMIv2 will be converted into textual 153 descriptions in SMIv1 during the translation process. However, this 154 loss of machine readable information is not considered to change the 155 semantics of the MIB. 157 4.1 Object Definitions 159 Managed objects are accessed via a virtual information store, termed 160 the Management Information Base or MIB. Objects in the MIB are 161 defined using the subset of Abstract Syntax Notation One (ASN.1) 162 defined in the SMI. In particular, each object type is named by an 163 OBJECT IDENTIFIER, an administratively assigned name. The object type 164 together with an object instance serves to uniquely identify a 165 specific instantiation of the object. For human convenience, we 166 often use a textual string, termed the descriptor, to also refer to 167 the object type. 169 5.0 Feature Checklist 171 This MIB is designed to satisfy the following requirements and 172 constraints: 174 - Fit within the architecture defined [PWMIB]. 176 - Fit within the model for VC definition/management 177 as defined in the [AToM] MIB. 179 - MIB supports manually configured ATM VCs 181 - MIB supports automatically configured ATM VCs 183 - The MIB enables the use of any PSN 185 - The MIB supports point-to-point ATM VC connections. 186 Point-to-multipoint and multipoint-to-point connections 187 are for future study. 189 - The MIB allows configuration of all the parameters needed 190 to establish a PW ATM VC. 192 - The MIB reports: ATM performance metrics for the PW ATM VC. 193 This includes cells received, tagged, rejected, transmitted 194 and lost. 196 - ATM OAM cell support. 198 - The MIB does not consider ILMI support 200 6.0 PW-MIB usage 202 The MIB structure for defining a PW service is composed of three 203 layers of MIB modules functioning together. This general model is 204 defined in the PWE3 Framework [FRMWK]. The layering model is 205 intended to sufficiently isolate PW services from the underlying PSN 206 layer that carries the emulated service. This is done at the same 207 time as providing a standard means for connecting any supported 208 services to any supported PSNs. 210 The first layer known as the service layer contains service-specific 211 modules such as the one defined in this document. These modules 212 define service-specific management objects that interface or 213 collaborate with existing MIB modules for the native version of the 215 service. The service-specific module "glues" the standard module to 216 the PWE MIB framework. 218 The next layer of the PWE MIB framework is comprised of the PW-MIB 219 module [PWMIB]. This module is used to configure general parameters 220 of PW VCs that are common to all types of emulated services and PSNs. 221 This layer is connected to the service-specific layer above, and the 222 PSN layer below. 224 The PSN layer provides PSN-specific modules for each type of PSN. 225 These modules associate the VC with one or more "tunnels" that carry 226 the service over the PSN. These modules are defined in other 227 documents. This module is used to "glue" the PW service to the 228 underlying PSN-specific MIB modules. In the case of MPLS, for 229 example, the PW-MPLS MIB [PWMPLSMIB] is used to connect the PW 230 service to either the MPLS-LDP [LDPMIB] or MPLS-TE [TEMIB] MIBs. 232 [PWTC] defines some of the object types used in these modules. 234 6.1 ATM-PW MIB Usage 236 In this section we provide an example of using the MIB objects 237 described in section 8 to set up a ATM VC. While this example is not meant 238 to illustrate every permutation of the MIB, it is intended as an aid in the 239 understanding of some key concepts. It is meant to be read after going 240 through the MIB itself. See [PWMIB] for an example of setting up a PSN 241 Tunnel. 243 The following example illustrates how a user will set up a AAL5 ATM VC on 244 a switch/router with cells entering the switch/router through ATM Interface 245 with IfIndex 1000, VPI 1 and VCI 100 (from ATM Network to PSN - outbound 246 direction) and on the way back, It goes out of the switch/router through 247 ATM Interface 1000 with VPI 1 and VCI 100 (PSN to ATM Network - inbound 248 direction) 249 First create an entry in PW MIB with pwVcType atmAal5Vcc(2), 250 then create entries in inbound and outbound tables. 252 In PW ATM MIB 254 In pwAtmOutboundTable: 255 { 256 pwAtmOutboundAtmIf 1000 --Outbound AtmIf 257 pwAtmOutboundVpi 1 --Outbound VPI 258 pwAtmOutboundVci 100 --Outbound VCI 259 pwAtmOutboundTrafficParamDescr 0.0 -- Best Effort 260 pwAtmOutboundRowStatus createAndGo 261 pwAtmOutboundClpQosMapping false(0) --CLP wont be mapped to QoS 262 pwAtmOutboundOamCellSupported true(1) --OAM cells will be sent 263 pwAtmOutboundOverhead 15 264 } 266 In pwAtmInboundTable 267 { 268 pwAtmInboundAtmIf 1000 --Inbound AtmIf 269 pwAtmInboundVpi 1 --Inbound VPI 270 pwAtmInboundVci 100 --Inbound VCI 271 pwAtmInboundTrafficParamDescr 0.0 --Best Effort 272 pwAtmInboundRowStatus createAndGo 273 pwAtmInboundOamCellSupported true(1) --Will accept OAM Cells 274 } 276 7.0 PW-ATM MIB Summary 278 This MIB consists of 4 tables. 280 - PW VC ATM Outbound Table 281 This Table is used to configure a outbound ATM VC Entry. 283 - PW VC ATM Inbound Table 284 This Table is used to configure a inbound ATM VC Entry. 286 - PW VC ATM Outbound Perf Table 287 This Table contains the statsistics for an ATM VC Entry in the 288 Outbound direction 290 - PW VC ATM Inbound Perf Table 291 This Table contains the statsistics for an ATM VC Entry in the 292 Inbound direction 294 A TrafficParamDescr Table is not defined as part of this MIB so that users 295 can refer to any ATM TrafficDescr Table (e.g atmTrafficDescrParamTable 296 present in the [AToM] MIB) 298 8.0 Object Definitions 300 PW-ATM-MIB DEFINITIONS ::= BEGIN 302 IMPORTS 303 MODULE-IDENTITY, OBJECT-TYPE, experimental, Integer32 304 Counter32, Counter64 305 FROM SNMPv2-SMI 307 MODULE-COMPLIANCE, OBJECT-GROUP 308 FROM SNMPv2-CONF 310 TruthValue, RowStatus, RowPointer 311 FROM SNMPv2-TC 313 InterfaceIndex 314 FROM IF-MIB 316 pwVcIndex 317 FROM PW-MIB 319 AtmVpIdentifier, AtmVcIdentifier 320 FROM ATM-TC-MIB; 322 pwAtmMIB MODULE-IDENTITY 323 LAST-UPDATED "200202261200Z" -- 26 February 2002 12:00:00 EST 324 ORGANIZATION "Pseudo-Wire Emulation Edge-to-Edge (PWE3) 325 Working Group" 326 CONTACT-INFO 327 "Senthilkumar Sathappan 328 Postal: 1000 Marconi Drive 329 Warrendale PA 15086 330 Tel: +1-724-742-6147 331 Email: senthilkumar.sathappan@marconi.com 333 Marichetty Venkatesan 334 Postal: 1000 Marconi Drive 335 Warrendale PA 15086 336 Tel: +1-724-742-7058 337 Email: marichetty.venkatesan@marconi.com 339 Thomas D. Nadeau 340 Postal: Cisco Systems, Inc. 341 250 Apollo Drive 342 Chelmsford, MA 01824 343 Tel: +1-978-497-3051 344 Email: tnadeau@cisco.com 346 Discussion and general questions should be posed to 347 the PWE3 Working Group (pwe3@ietf.org)." 349 DESCRIPTION 350 "This MIB contains managed object definitions for Pseudo Wire 351 emulation of ATM over Packet Switched Networks(PSN). 353 This MIB reports to the PW-MIB. The PW-MIB contains 354 structures and MIB associations generic to Pseudo-Wire 355 Virtual Circuit (VC) emulation. VC-specific MIBs (such as 356 this) contain config and stats for specific VC types." 358 -- Revision history. 359 REVISION "200202261200Z" -- 26 February 2002 12:00:00 EST 360 DESCRIPTION "Initial Version" 361 ::= { experimental 979 } -- To be assigned by IANA 363 -- Top-level components of this MIB 365 pwAtmNotifications OBJECT IDENTIFIER ::= { pwAtmMIB 0 } 366 pwAtmObjects OBJECT IDENTIFIER ::= { pwAtmMIB 1 } 367 pwAtmConformance OBJECT IDENTIFIER ::= { pwAtmMIB 2 } 369 -- PW VC ATM Outboud Table 371 pwAtmOutboundTable OBJECT-TYPE 372 SYNTAX SEQUENCE OF PwAtmOutboundEntry 373 MAX-ACCESS not-accessible 374 STATUS current 375 DESCRIPTION 376 "This table specifies the information for an ATM VC to be carried 377 over PSN in the outbound direction." 378 ::= { pwAtmObjects 1 } 380 pwAtmOutboundEntry OBJECT-TYPE 381 SYNTAX PwAtmOutboundEntry 382 MAX-ACCESS not-accessible 383 STATUS current 384 DESCRIPTION 385 "A row in this table represents an ATM VC that needs to be adapted 386 and carried over PSN. This table is indexed by pwVcIndex from 387 pwVcTable." 388 INDEX { pwVcIndex } 389 ::= { pwAtmOutboundTable 1 } 391 PwAtmOutboundEntry ::= SEQUENCE { 392 pwAtmOutboundAtmIf InterfaceIndex, 393 pwAtmOutboundVpi AtmVpIdentifier, 394 pwAtmOutboundVci AtmVcIdentifier, 395 pwAtmOutboundTrafficParamDescr RowPointer, 396 pwAtmOutboundRowStatus RowStatus, 397 pwAtmOutboundClpQosMapping TruthValue, 398 pwAtmOutboundOamCellSupported TruthValue, 399 pwAtmOutboundOverhead Integer32 400 } 402 pwAtmOutboundAtmIf OBJECT-TYPE 403 SYNTAX InterfaceIndex 404 MAX-ACCESS read-create 405 STATUS current 406 DESCRIPTION 407 "The ATM Interface that receives cells from the ATM network." 408 ::= { pwAtmOutboundEntry 1 } 410 pwAtmOutboundVpi OBJECT-TYPE 411 SYNTAX AtmVpIdentifier 412 MAX-ACCESS read-create 413 STATUS current 414 DESCRIPTION 415 "VPI value of this ATM VC. 416 If the pwVcType is atmTransparent then the value will be set to 417 zero." 418 ::= { pwAtmOutboundEntry 2 } 420 pwAtmOutboundVci OBJECT-TYPE 421 SYNTAX AtmVcIdentifier 422 MAX-ACCESS read-create 423 STATUS current 424 DESCRIPTION 425 "VCI value of this ATM VC. 426 If the pwVcType is atmTransparent or atmVpcCell then the value 427 will be set to zero." 428 ::= { pwAtmOutboundEntry 3 } 430 pwAtmOutboundTrafficParamDescr OBJECT-TYPE 431 SYNTAX RowPointer 432 MAX-ACCESS read-create 433 STATUS current 434 DESCRIPTION 435 "This object represents a pointer to a ATM traffic parameter 436 specification table which will be employed while receiving cells 437 from the ATM network. This table should contain a set of 438 self-consistent ATM traffic parameters including the ATM 439 traffic service category. A value of 0.0 indicates Best Effort" 440 ::= { pwAtmOutboundEntry 4 } 442 pwAtmOutboundRowStatus OBJECT-TYPE 443 SYNTAX RowStatus 444 MAX-ACCESS read-create 445 STATUS current 446 DESCRIPTION 447 "This Object is used to create, modify or delete a row in this 448 table." 449 ::= { pwAtmOutboundEntry 5 } 451 pwAtmOutboundClpQosMapping OBJECT-TYPE 452 SYNTAX TruthValue 453 MAX-ACCESS read-create 454 STATUS current 455 DESCRIPTION 456 "This Object indicates whether the CLP bits are considered when 457 determining the value placed in the Quality of Service fields 458 (e.g. EXP fields of the MPLS Label Stack) of the encapsulating 459 protocol." 460 ::= { pwAtmOutboundEntry 6 } 462 pwAtmOutboundOamCellSupported OBJECT-TYPE 463 SYNTAX TruthValue 464 MAX-ACCESS read-create 465 STATUS current 466 DESCRIPTION 467 "This Object indicates whether OAM Cells are transported on this 468 VC." 469 ::= { pwAtmOutboundEntry 7 } 471 pwAtmOutboundOverhead OBJECT-TYPE 472 SYNTAX Integer32 (0..20) 473 MAX-ACCESS read-create 474 STATUS current 475 DESCRIPTION 476 "This Object represents the ATM overhead (% value) to be 477 applied when calculating QoS rates in the 478 MPLS domain for atmAal5Vcc transport. This object will be 479 set to zero in the cell transport mode as the 480 bandwidth needed to carry cells in the MPLS domain will be 481 higher (since Tunnel label, VC label and an 482 optional control word has to transmitted with every cell)". 483 DEFVAL { 15 } 484 ::= { pwAtmOutboundEntry 8 } 486 -- End of PW VC ATM Outbound Table 488 -- PW VC ATM Outbound Perf Table 490 pwAtmOutboundPerfTable OBJECT-TYPE 491 SYNTAX SEQUENCE OF PwAtmOutboundPerfEntry 492 MAX-ACCESS not-accessible 493 STATUS current 494 DESCRIPTION 495 "This table specifies performance-related attributes for 496 an ATM VC in the outbound direction." 497 ::= { pwAtmObjects 2 } 498 pwAtmOutboundPerfEntry OBJECT-TYPE 499 SYNTAX PwAtmOutboundPerfEntry 500 MAX-ACCESS not-accessible 501 STATUS current 502 DESCRIPTION 503 "A row in this table represents performance for an ATM VC in the 504 outbound direction" 505 AUGMENTS { pwAtmOutboundEntry } 506 ::= { pwAtmOutboundPerfTable 1 } 508 PwAtmOutboundPerfEntry ::= SEQUENCE { 509 pwAtmOutboundCellsReceived Counter32, 510 pwAtmOutboundCellsRejected Counter32, 511 pwAtmOutboundCellsTagged Counter32, 512 pwAtmOutboundHCCellsReceived Counter64, 513 pwAtmOutboundHCCellsRejected Counter64, 514 pwAtmOutboundHCCellsTagged Counter64 515 } 517 pwAtmOutboundCellsReceived OBJECT-TYPE 518 SYNTAX Counter32 519 MAX-ACCESS read-only 520 STATUS current 521 DESCRIPTION 522 "This Object indicates the number of cells received by this VC." 523 ::= { pwAtmOutboundPerfEntry 1 } 525 pwAtmOutboundCellsRejected OBJECT-TYPE 526 SYNTAX Counter32 527 MAX-ACCESS read-only 528 STATUS current 529 DESCRIPTION 530 "This Object indicates the number of cells that were rejected by 531 this VC because of policing." 532 ::= { pwAtmOutboundPerfEntry 2 } 534 pwAtmOutboundCellsTagged OBJECT-TYPE 535 SYNTAX Counter32 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION 539 "This Object indicates the number of cells that were Tagged." 540 ::= { pwAtmOutboundPerfEntry 3 } 542 pwAtmOutboundHCCellsReceived OBJECT-TYPE 543 SYNTAX Counter64 544 MAX-ACCESS read-only 545 STATUS current 546 DESCRIPTION 547 "High capacity counter for number of cells received by this VC." 548 ::= { pwAtmOutboundPerfEntry 4 } 550 pwAtmOutboundHCCellsRejected OBJECT-TYPE 551 SYNTAX Counter64 552 MAX-ACCESS read-only 553 STATUS current 554 DESCRIPTION 555 "High Capacity counter for number of cells that were rejected by 556 this VC because of policing." 557 ::= { pwAtmOutboundPerfEntry 5 } 559 pwAtmOutboundHCCellsTagged OBJECT-TYPE 560 SYNTAX Counter64 561 MAX-ACCESS read-only 562 STATUS current 563 DESCRIPTION 564 "High capacity counter for number of cells that were Tagged." 565 ::= { pwAtmOutboundPerfEntry 6 } 567 -- End of PW VC ATM Outbound Perf Table 569 -- PW VC ATM Inbound Table 571 pwAtmInboundTable OBJECT-TYPE 572 SYNTAX SEQUENCE OF PwAtmInboundEntry 573 MAX-ACCESS not-accessible 574 STATUS current 575 DESCRIPTION 576 "This table specifies the information for an ATM VC in the 577 Inbound direction." 578 ::= { pwAtmObjects 3 } 580 pwAtmInboundEntry OBJECT-TYPE 581 SYNTAX PwAtmInboundEntry 582 MAX-ACCESS not-accessible 583 STATUS current 584 DESCRIPTION 585 "A row in this table represents an ATM VC that needs to be sent 586 into the ATM Network after reconstructing cells from Packets 587 received from a PSN This table is indexed by pwVcIndex from 588 pwVcTable" 589 INDEX { pwVcIndex } 590 ::= { pwAtmInboundTable 1 } 592 PwAtmInboundEntry ::= SEQUENCE { 593 pwAtmInboundAtmIf InterfaceIndex, 594 pwAtmInboundVpi AtmVpIdentifier, 595 pwAtmInboundVci AtmVcIdentifier, 596 pwAtmInboundTrafficParamDescr RowPointer, 597 pwAtmInboundRowStatus RowStatus, 598 pwAtmInboundOamCellSupported TruthValue 599 } 601 pwAtmInboundAtmIf OBJECT-TYPE 602 SYNTAX InterfaceIndex 603 MAX-ACCESS read-create 604 STATUS current 605 DESCRIPTION 606 "The ATM Interface that sends cells into the ATM network after 607 reconstructing cells from packets received from a PSN." 608 ::= { pwAtmInboundEntry 1 } 610 pwAtmInboundVpi OBJECT-TYPE 611 SYNTAX AtmVpIdentifier 612 MAX-ACCESS read-create 613 STATUS current 614 DESCRIPTION 615 "VPI value of this ATM VC. 616 If the pwVcType is atmTransparent then the value will be set to 617 zero." 618 ::= { pwAtmInboundEntry 2 } 620 pwAtmInboundVci OBJECT-TYPE 621 SYNTAX AtmVcIdentifier 622 MAX-ACCESS read-create 623 STATUS current 624 DESCRIPTION 625 "VCI value of this ATM VC. 626 If the pwVcType is atmTransparent or atmVpcCell then the value 627 will be set to zero." 628 ::= { pwAtmInboundEntry 3 } 630 pwAtmInboundTrafficParamDescr OBJECT-TYPE 631 SYNTAX RowPointer 632 MAX-ACCESS read-create 633 STATUS current 634 DESCRIPTION 635 "This object represents a pointer to a ATM traffic parameter 636 specification table which will be employed while transmit into the 637 ATM network. This table contains a set of self-consistent 638 ATM traffic parameters including the ATM traffic service category. 639 A value of 0.0 indicates Best Effort" 640 ::= { pwAtmInboundEntry 4 } 642 pwAtmInboundRowStatus OBJECT-TYPE 643 SYNTAX RowStatus 644 MAX-ACCESS read-create 645 STATUS current 646 DESCRIPTION 647 "This Object is used to create, modify or delete a row in this 648 table." 649 ::= { pwAtmInboundEntry 5 } 651 pwAtmInboundOamCellSupported OBJECT-TYPE 652 SYNTAX TruthValue 653 MAX-ACCESS read-create 654 STATUS current 655 DESCRIPTION 656 "This Object indicates whether this VC can receive OAM Cells." 657 ::= { pwAtmInboundEntry 6 } 659 -- End of PW VC ATM Inbound Table 661 -- PW VC ATM Inbound Perf Table 663 pwAtmInboundPerfTable OBJECT-TYPE 664 SYNTAX SEQUENCE OF PwAtmInboundPerfEntry 665 MAX-ACCESS not-accessible 666 STATUS current 667 DESCRIPTION 668 "This table specifies the performance for an ATM VC in the 669 Inbound direction." 670 ::= { pwAtmObjects 4 } 672 pwAtmInboundPerfEntry OBJECT-TYPE 673 SYNTAX PwAtmInboundPerfEntry 674 MAX-ACCESS not-accessible 675 STATUS current 676 DESCRIPTION 677 "This table specifies performance-related attributes for 678 an ATM VC in the inbound direction." 679 AUGMENTS { pwAtmInboundEntry } 680 ::= {pwAtmInboundPerfTable 1} 682 PwAtmInboundPerfEntry ::= SEQUENCE { 683 pwAtmInboundPerfCellsXmit Counter32, 684 pwAtmInboundPerfCellsLost Counter32, 685 pwAtmInboundPerfHCCellsXmit Counter64, 686 pwAtmInboundPerfHCCellsLost Counter64 687 } 689 pwAtmInboundPerfCellsXmit OBJECT-TYPE 690 SYNTAX Counter32 691 MAX-ACCESS read-only 692 STATUS current 693 DESCRIPTION 694 "This Object indicates the number of cells that were transmitted 695 into ATM network by this VC." 696 ::= { pwAtmInboundPerfEntry 1 } 698 pwAtmInboundPerfCellsLost OBJECT-TYPE 699 SYNTAX Counter32 700 MAX-ACCESS read-only 701 STATUS current 702 DESCRIPTION 703 "This Object indicates the number of cells that were dropped by 704 this VC." 705 ::= { pwAtmInboundPerfEntry 2 } 707 pwAtmInboundPerfHCCellsXmit OBJECT-TYPE 708 SYNTAX Counter64 709 MAX-ACCESS read-only 710 STATUS current 711 DESCRIPTION 712 "High Capacity counter for the number of cells that were 713 transmitted into ATM network by this VC." 714 ::= { pwAtmInboundPerfEntry 3 } 716 pwAtmInboundPerfHCCellsLost OBJECT-TYPE 717 SYNTAX Counter64 718 MAX-ACCESS read-only 719 STATUS current 720 DESCRIPTION 721 "High Capacity counter for number of cells that were dropped by 722 this VC." 723 ::= { pwAtmInboundPerfEntry 4 } 725 -- End of PW VC ATM Inbound Table 727 -- conformance information 729 pwAtmGroups OBJECT IDENTIFIER ::= { pwAtmConformance 1 } 730 pwAtmCompliances OBJECT IDENTIFIER ::= { pwAtmConformance 2 } 732 pwAtmModuleCompliance MODULE-COMPLIANCE 733 STATUS current 734 DESCRIPTION 735 "The compliance statement for agent that support PW 736 ATM." 738 MODULE -- this module 739 MANDATORY-GROUPS { pwAtmOutboundGroup, 740 pwAtmOutboundPerfGroup, 741 pwAtmInboundGroup, 742 pwAtmInboundPerfGroup 743 } 744 ::= { pwAtmCompliances 1 } 746 -- Units of conformance. 748 pwAtmOutboundGroup OBJECT-GROUP 749 OBJECTS { pwAtmOutboundAtmIf, 750 pwAtmOutboundVpi, 751 pwAtmOutboundVci, 752 pwAtmOutboundTrafficParamDescr, 753 pwAtmOutboundRowStatus, 754 pwAtmOutboundClpQosMapping, 755 pwAtmOutboundOamCellSupported, 756 pwAtmOutboundOverhead 757 } 758 STATUS current 759 DESCRIPTION 760 "Collection of objects for basic ATM PW outbound config." 761 ::= { pwAtmGroups 1 } 763 pwAtmOutboundPerfGroup OBJECT-GROUP 764 OBJECTS { pwAtmOutboundCellsReceived, 765 pwAtmOutboundCellsRejected, 766 pwAtmOutboundCellsTagged, 767 pwAtmOutboundHCCellsReceived, 768 pwAtmOutboundHCCellsRejected, 769 pwAtmOutboundHCCellsTagged 770 } 771 STATUS current 772 DESCRIPTION 773 "Collection of objects counting various outbound ATM PW statistics." 774 ::= { pwAtmGroups 2 } 776 pwAtmInboundGroup OBJECT-GROUP 777 OBJECTS { pwAtmInboundAtmIf, 778 pwAtmInboundVpi, 779 pwAtmInboundVci, 780 pwAtmInboundTrafficParamDescr, 781 pwAtmInboundRowStatus, 782 pwAtmInboundOamCellSupported 783 } 784 STATUS current 785 DESCRIPTION 786 "Collection of objects for basic ATM PW inbound config." 787 ::= { pwAtmGroups 3 } 789 pwAtmInboundPerfGroup OBJECT-GROUP 790 OBJECTS { pwAtmInboundPerfCellsXmit, 791 pwAtmInboundPerfCellsLost, 792 pwAtmInboundPerfHCCellsXmit, 793 pwAtmInboundPerfHCCellsLost 794 } 795 STATUS current 796 DESCRIPTION 797 "Collection of objects counting various inbound ATM PW statistics." 798 ::= { pwAtmGroups 4 } 800 END 802 9.0 Security Considerations 804 There are a number of management objects defined in this MIB that 805 have a MAX-ACCESS clause of read-write and/or read-create. Such 806 objects may be considered sensitive or vulnerable in some network 807 environments. The support for SET operations in a non-secure 808 environment without proper protection can have a negative effect on 809 network operations. 811 No managed objects in this MIB contain sensitive information. 813 SNMPv1 by itself is not a secure environment. Even if the network 814 itself is secure (for example by using IPSec), even then, there is no 815 control as to who on the secure network is allowed to access and 816 GET/SET (read/change/create/delete) the objects in this MIB. 818 It is recommended that the implementers consider the security 819 features as provided by the SNMPv3 framework. Specifically, the use 820 of the User-based Security Model RFC 2574 [RFC2574] and the View- 821 based Access Control Model RFC 2575 [RFC2575] is recommended. 823 It is then a customer/user responsibility to ensure that the SNMP 824 entity giving access to an instance of this MIB, is properly 825 configured to give access to the objects only to those principals 826 (users) that have legitimate rights to indeed GET or SET 827 (change/create/delete) them. 829 10.0 References 831 [FRMWK] Pate et al, "Framework for Pseudo Wire Emulation Edge-to- 832 Edge (PWE3)", , 833 September 2001. 835 [PWREQ] Xiao et al, "Requirements for Pseudo Wire Emulation Edge- 836 to-Edge (PWE3)", , 837 November 2001. 839 [VPLS] Augustyn et al, "Requirements for Virtual Private LAN 840 Services (VPLS)", , October 2001. 843 [PWTC] Nadeau, T., et al, " Definitions for Textual Conventions 844 and OBJECT-IDENTITIES for Pseudo-Wires Management", 845 , February 2002. 847 [PWMIB] Zelig et al, "Pseudo Wire (PW) Management Information 848 Base",, February 2001. 850 [PWMPLSMIB] Zelig et al, "Pseudo Wire (PW) Over MPLS PSN Management 851 Information Base", , 852 February 2002. 854 [ENETLIKE] Flick, J., "Definitions of Managed Objects for the 855 Ethernet-like Interface Types", , June 2001. 858 [IANAFamily]Internet Assigned Numbers Authority (IANA), ADDRESS 859 FAMILY NUMBERS,(http://www.isi.edu/in- 860 notes/iana/assignements/address-family-numbers), for MIB 861 see: ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 863 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces 864 Group MIB using SMIv2", RFC 2233, Nov. 1997 866 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 867 requirement Levels", BCP 14, RFC 2119, March 1997. 869 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 870 Architecture for Describing SNMP Management Frameworks", 871 RFC 2571, April 1999. 873 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 874 Identification of Management Information for TCP/IP- 875 based Internets", STD 16, RFC 1155, May 1990. 877 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 878 STD 16, RFC 1212, March 1991. 880 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 881 the SNMP", RFC 1215, March 1991. 883 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J, 884 Rose, M., and S. Waldbusser, "Structure of Management 885 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 886 1999. 888 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J, 889 Rose, M., and S. Waldbusser, "Textual Conventions for 890 SMIv2", STD 58, RFC 2579, April 1999. 892 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J, 893 Rose, M., and S. Waldbusser, "Conformance Statements for 894 SMIv2", STD 58, RFC 2580, April 1999. 896 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 897 "Simple Network Management Protocol", STD 15, RFC 1157, 898 May 1990. 900 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 901 "Introduction to Community-based SNMPv2", RFC 1901, 902 January 1996. 904 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 905 "Transport Mappings for Version 2 of the Simple Network 906 Management Protocol (SNMPv2)", RFC 1906, January 1996. 908 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 909 "Message Processing and Dispatching for the Simple 910 Network Management Protocol (SNMP)", RFC 2572, April 911 1999. 913 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 914 Model (USM) for version 3 of the Simple Network 915 Management Protocol (SNMPv3)", RFC 2574, April 1999. 917 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 918 "Protocol Operations for Version 2 of the Simple Network 919 Management Protocol (SNMPv2)", RFC 1905, January 1996. 921 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 922 Applications", RFC 2573, April 1999. 924 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 925 Access Control Model (VACM) for the Simple Network 926 Management Protocol (SNMP)", RFC 2575, April 1999. 928 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 929 "Introduction to Version 3 of the Internet-standard 930 Network Management Framework", RFC 2570, April 1999. 932 10.0 Authors' Addresses 934 Senthilkumar Sathappan 935 Marconi Communications 937 Marichetty Venkatesan 938 Marconi Communications 939 Thomas D. Nadeau 940 Cisco Systems, Inc. 941 250 Apollo Drive 942 Chelmsford, MA 01824 943 Email: tnadeau@cisco.com 945 11.0 Full Copyright Statement 947 Copyright (C) The Internet Society (2000). All Rights Reserved. 949 This document and translations of it may be copied and furnished to 950 others, and derivative works that comment on or otherwise explain it 951 or assist in its implementation may be prepared, copied, published 952 and distributed, in whole or in part, without restriction of any 953 kind, provided that the above copyright notice and this paragraph are 954 included on all such copies and derivative works. However, this 955 document itself may not be modified in any way, such as by removing 956 the copyright notice or references to the Internet Society or other 957 Internet organizations, except as needed for the purpose of 958 developing Internet standards in which case the procedures for 959 copyrights defined in the Internet Standards process must be 960 followed, or as required to translate it into languages other than 961 English. 963 The limited permissions granted above are perpetual and will not be 964 revoked by the Internet Society or its successors or assigns. This 965 document and the information contained herein is provided on an "AS 966 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 967 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 968 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 969 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 970 OR FITNESS FOR A PARTICULAR PURPOSE.