idnits 2.17.1 draft-ietf-pwe3-cep-mib-16.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 and authors 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 contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 8, 2011) is 4797 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Pseudowire Edge-to-Edge Emulation D. Zelig, Ed. 3 Internet-Draft Oversi Systems 4 Intended status: Standards Track R. Cohen, Ed. 5 Expires: September 7, 2011 Resolute Networks 6 T. Nadeau, Ed. 7 Huawei 8 March 8, 2011 10 SONET/SDH Circuit Emulation Service Over Packet (CEP) Management 11 Information Base (MIB) Using SMIv2 12 draft-ietf-pwe3-cep-mib-16 14 Abstract 16 This memo defines a portion of the Management Information Base (MIB) 17 for use with network management protocols in the Internet community. 18 In particular, it describes managed objects for modeling SONET/SDH 19 circuits over a Packet Switch Network (PSN). 21 Requirements Language 23 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 24 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 25 document are to be interpreted as described in RFC2119 [RFC2119]. 27 Status of this Memo 29 This Internet-Draft is submitted to IETF in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF), its areas, and its working groups. Note that 34 other groups may also distribute working documents as Internet- 35 Drafts. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 The list of current Internet-Drafts can be accessed at 43 http://www.ietf.org/ietf/1id-abstracts.txt. 45 The list of Internet-Draft Shadow Directories can be accessed at 46 http://www.ietf.org/shadow.html. 48 This Internet-Draft will expire on July 31, 2011. 50 Copyright Notice 51 Copyright (c) 2011 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and 59 restrictions with respect to this document. Code Components 60 extracted from this document must include Simplified BSD License 61 text as described in Section 4.e of the Trust Legal Provisions and 62 are provided without warranty as described in the Simplified BSD 63 License. 65 This document may contain material from IETF Documents or IETF 66 Contributions published or made publicly available before November 67 10, 2008. The person(s) controlling the copyright in some of this 68 material may not have granted the IETF Trust the right to allow 69 modifications of such material outside the IETF Standards Process. 70 Without obtaining an adequate license from the person(s) controlling 71 the copyright in such materials, this document may not be modified 72 outside the IETF Standards Process, and derivative works of it may 73 not be created outside the IETF Standards Process, except to format 74 it for publication as an RFC or to translate it into languages other 75 than English. 77 Table of Contents 79 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 80 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 81 3. Co-Authors . . . . . . . . . . . . . . . . . . . . . . . . . . 4 82 4. The Internet-Standard Management Framework . . . . . . . . . . 4 83 5. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . 4 84 6. MIB Module Description and Usage . . . . . . . . . . . . . . . 5 85 6.1. PW-CEP-STD-MIB Summary . . . . . . . . . . . . . . . . . . 5 86 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 6 87 6.3. PW-STD-MIB Modules Usage . . . . . . . . . . . . . . . . . 6 88 6.4. PW-CEP-STD-MIB Module Usage . . . . . . . . . . . . . . . 7 89 6.5. Example of PW-CEP-STD-MIB Usage . . . . . . . . . . . . . 7 90 7. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 9 91 8. Security Considerations . . . . . . . . . . . . . . . . . . . 67 92 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 68 93 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69 94 10.1. Normative References . . . . . . . . . . . . . . . . . . . 69 95 10.2. Informative References . . . . . . . . . . . . . . . . . . 70 96 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 70 98 1. Introduction 100 This document describes a model for managing encapsulated SONET/SDH 101 Time Division Multiplexed (TDM) digital signals for transmission over 102 a Packet Switched Network (PSN). 104 This document is closely related to [RFC4842], which describes the 105 technology to encapsulate TDM signals and provide the Circuit 106 Emulation Service over a Packet Switched Network (PSN). 108 The model for Circuit Emulation Service Over Packet (CEP) 109 management is a MIB module. The PW-CEP-STD-MIB 110 module described in this document works closely with the MIB modules 111 described in [RFC5601] and the textual conventions defined in 112 [RFC5542]. In the spirit of the [RFC2863], a CEP connection will be 113 a pseudowire(PW), and will therefore not be represented in the 114 ifTable. 116 CEP is currently specified to carry "structured" SONET/SDH paths, 117 meaning that each SONET/SDH PATH/VT within the section/line/path can 118 be processed separately. The SONET/SDH section/line/path interface 119 stack is modeled within [RFC3592]. 121 This document adopts the definitions, acronyms and mechanisms 122 described in [RFC3985]. Unless otherwise stated, the mechanisms of 123 [RFC3985] apply and will not be re-described here. 125 Conventions used in this document 127 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 128 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 129 document are to be interpreted as described in [RFC2119]. 131 2. Terminology 133 CEP terminology comes from [RFC4842] that describes a mechanism for 134 transporting SONET/SDH Time Division Multiplexed (TDM) digital 135 signals over a packet-oriented network. The mechanism for structured 136 emulation (as outlined in [RFC4842]) terminates the SONET/SDH 137 section and line overhead and then breaks the SONET/SDH path's 138 Synchronous Payload Envelope (SPE) into fragments for transmission 139 over a PSN. Mechanism for terminating of the SONET/SDH path overhead 140 and extracting SONET VTs are also described in [RFC4842]. Mechanisms 141 for Fractional SONET/SDH SPE emulation are described in [RFC4842]. A 142 CEP header is appended at the beginning of each fragment to provide 143 information regarding where the SPE begins within the packet stream, 144 a sequence number and pointer adjustment information (see [RFC4842]). 146 "Outbound" references the traffic direction where a SONET/SDH path's 147 payload (SPE) is received, adapted to packet, assigned a PW label and 148 sent into the PSN. 150 Conversely, "inbound" is the direction where packets are received 151 from the PSN, packet payloads are reassembled back into an SPE and 152 inserted as a SONET/SDH path into the SONET/SDH section and line. 154 Since a SONET/SDH path is bi-directional and symmetrical, CEP uses 155 the same SONET/SDH time-slot, SONET/SDH width and packet size. 156 Inbound and outbound PW labels may differ. 158 3. Co-Authors 160 The individuals listed below are co-authors of this document. Dave 161 Danenberg was the editor of this document at the pre-WG versions of 162 the PW MIB modules. 164 Andrew G. Malis - Tellabs 166 Dave Danenberg - Litchfield Communications 168 Scott C. Park - Litchfield Communications 170 4. The Internet-Standard Management Framework 172 For a detailed overview of the documents that describe the current 173 Internet-Standard Management Framework, please refer to section 7 of 174 RFC 3410 [RFC3410]. 176 Managed objects are accessed via a virtual information store, termed 177 the Management Information Base or MIB. MIB objects are generally 178 accessed through the Simple Network Management Protocol (SNMP). 179 Objects in the MIB are defined using the mechanisms defined in the 180 Structure of Management Information (SMI). This memo specifies a MIB 181 module that is compliant to the SMIv2, which is described in STD 58, 182 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 183 [RFC2580]. 185 5. Feature Checklist 187 The PW-CEP-STD-MIB module is designed to satisfy the following 188 requirements and constraints: 190 - The MIB module is designed to work with the PW-STD-MIB[RFC5601] 191 module. 193 - The MIB module is independent of the PSN type. 195 - The MIB module supports all the signal types as defined in 196 [RFC4842]: SPE, fractional SPE, VT, both SONET and SDH mapping and 197 all the optional features as defined in [RFC4842]. 199 - The MIB module reports all the statistics as defined by [RFC4842]. 201 6. MIB Module Description and Usage 203 For clarity of the description below, in most cases we refer to the 204 SONET PATH signal configuration only, but the same examples are 205 applicable for SDH signals and VT level processing as well, as 206 described in [RFC3985]. 208 6.1. PW-CEP-STD-MIB Summary 210 - The CEP PW Table (pwCepTable) contains the SONET/SDH Path/VT 211 ifIndex, SONET/SDH Path Time slot, the pwCepCfgTable index, config 212 error indications and various status indications. 214 - The CEP PW Configuration Parameter Table (pwCepCfgTable) has 215 objects for CEP PW configuration. In situations where sets of 216 config objects are common amongst more than one CEP PW, a single 217 entry here may be referenced by many pwCepTable entries. 219 - The CEP Performance Current Table (pwCemPerfCurrentTable) contains 220 CEP stats for the current 15-minute period. 222 - The CEP Performance 15 Minute Interval Table 223 (pwCemPerfIntervalTable) is similar to the pwCemPerfCurrentTable. 224 It contains historical intervals (usually 96 15-minute entries to 225 cover a 24 hour period). 227 Note: the performance interval statistics are supported by CEP due 228 to the very function of CEP - that is, processing SONET/SDH. See 229 [RFC3592]. 231 - The CEP Performance 1 day Table (pwCepPerf1DayTable) contains 232 statistics accumulated during the current day and contains 233 previous days historical statistics. 235 - The CEP Fractional Table (pwCepFracTable) adds configuration and 236 monitoring parameters for fractional SPE PWs. 238 6.2. MIB modules required for IMPORTS 239 The PW-CEP-STD-MIB IMPORTS objects from SNMPv2-SMI [RFC2578], 240 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], SNMP-FRAMEWORK-MIB 241 [RFC3411], PerfHist-TC-MIB [RFC3593], HC-PerfHist-TC-MIB [RFC3705], 242 IF-MIB [RFC2863], PW-STD-MIB [RFC5601] and PW-TC-STD-MIB [RFC5542]. 244 6.3. PW-STD-MIB Modules Usage 246 The MIB module structure for defining a PW service is composed of 247 three layers of MIB modules functioning together. This general model 248 is defined in the PWE3 architecture [RFC3985]. The layering model is 249 intended to sufficiently isolate PW services from the underlying PSN 250 layer that carries the emulated service. This is done at the same 251 time as providing a standard means for connecting any supported 252 services to any supported PSNs. 254 The first layer, known as the service layer, contains service- 255 specific modules such as the one defined in this document. These 256 modules define service-specific management objects that interface or 257 collaborate with existing MIB modules for the native version of the 258 service. The service-specific module "glues" the standard modules to 259 the PWE3 MIB modules. The PW-CEP-STD-MIB module defined in this memo 260 serves as one of the PW type-specific MIB module. 262 The next layer of the PWE3 MIB framework is the PW-STD-MIB module 263 [RFC5601]. This module is used to configure general parameters of 264 PWs that are common to all types of emulated services and PSNs. This 265 layer is connected to the service-specific layer above and the PSN 266 layer below. 268 The PSN layer provides PSN-specific modules for each type of PSN. 269 These modules associate the PW with one or more "tunnels" that carry 270 the service over the PSN. These modules are defined in other 271 documents. This module is used to "glue" the PW service to the 272 underlying PSN-specific MIB modules. 274 6.4. PW-CEP-STD-MIB Module Usage 276 Configuring a CEP PW involves the following steps. 278 First create an entry in the pwTable: 280 - Follow steps as defined in [RFC5601]. 282 Configure the PSN tunnel in the respective PSN specific PWE3 PSN glue 283 MIB module and the respective PSN specific MIB modules. Configure 284 the SONET Path parameters: 286 - Set the SONET path width in the sonetPathCurrentTable [RFC3592]. 288 - Set the SONET path index and the SONET path starting time slot in 289 the pwCepTable. 291 NOTE: The agent had created an entry in the pwCepTable based on the 292 entry created in the pwTable. 294 Configure the CEP PW: 296 - If necessary, create an entry in the pwCepCfgTable (a suitable 297 entry may already exist). Set packet length, etc. 299 - Set the index of this pwCepCfgTable entry in the pwCepTable. 301 Observe the CEP PW: 303 - Once a CEP PW is operational, the pwCepPerfCurrentTable, 304 pwCepPerfIntervalTable and pwCepPerf1DayTable can be used to 305 monitor the various counts, indicators and conditions of the PW. 307 6.5. Example of PW-CEP-STD-MIB Usage 309 In this section we provide an example of using the MIB objects 310 described in Section 7 to set up a CEP PW. While this example is not 311 meant to illustrate every permutation of the MIB, it is intended as 312 an aid to understanding some of the key concepts. It is meant to be 313 read after going through the MIB itself. See [RFC5601] for an 314 example of setting up PSN Tunnels. 316 First configure the SONET path width, starting time-slot and 317 associated CEP PW. In this case, an STS-3c starts at SONET time slot 318 1 (and is distributed normally within the SONET frame). In the 319 following example, the ifIndex for the sonetPathCurrentEntry is 23, 320 while the pwCepCfgTable index is 9. 322 In [RFC3592] sonetPathCurrentEntry (ifIndex = 23) : 324 { 325 sonetPathCurrentWidth = 3, 326 sonetPathCurrentStatus 327 ... 328 ... 329 } 331 Create an entry in the pwCepCfgTable (index = 9) : 333 { 334 pwCepCfgSonetPaylaodLength = 783 -- payload bytes 335 pwCepCfgMinPktLength = 0 -- no minimum 336 pwCepCfgPktReorder = true 337 pwCepCfgEnableDBA = unequipped 338 pwCepCfgRtpHdrSuppress = false 339 pwCepCfgJtrBfrDepth = 500 -- micro-seconds 341 pwCepCfgConsecPktsInsync = 2 -- Exit LOPS state 342 pwCepCfgConsecMissingOutSync = 10 -- Enter LOPS state 344 pwCepCfgPktErrorPlayOutValue = 0xFF -- All ones 346 pwCepCfgMissingPktsToSes = 3 -- packets, 347 pwCepCfgSesToUas = 2 -- seconds, 348 pwCepCfgSecsToExitUas = 10 -- seconds, 350 pwCepCfgRowStatus = createAndGo 351 } 353 In the PW-STD-MIB module: Get a new index and create a new pwTable 354 entry using pwIndexNext (here, the PW index = 83) and pwRowStatus. 355 In this new entry, set pwType to 'cep'. The agent will create a new 356 entry in the pwCepTable. Set the SONET path ifIndex, SONET path time 357 slot and Cfg Table indexes within this new pwCep table entry: 358 { 359 pwCepSonetIfIndex = 23 -- Index of associated entry 360 -- in sonetPathCurrent table. 362 pwCepCfgIndex = 9 -- Index of associated entry 363 -- in pwCepCfg table (above). 364 } 366 7. Object Definitions 368 PW-CEP-STD-MIB DEFINITIONS ::= BEGIN 370 IMPORTS 371 MODULE-IDENTITY, OBJECT-TYPE, 372 Integer32, Counter32, Unsigned32, Counter64, mib-2 373 FROM SNMPv2-SMI -- RFC 2578 375 MODULE-COMPLIANCE, OBJECT-GROUP 376 FROM SNMPv2-CONF -- RFC 2580 378 TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, 379 TimeStamp 380 FROM SNMPv2-TC -- RFC 2579 382 SnmpAdminString 383 FROM SNMP-FRAMEWORK-MIB -- RFC 3411 385 InterfaceIndexOrZero, InterfaceIndex 386 FROM IF-MIB -- RFC 2863 388 PerfCurrentCount, PerfIntervalCount 389 FROM PerfHist-TC-MIB -- RFC 3593 391 HCPerfCurrentCount, HCPerfIntervalCount, HCPerfTimeElapsed, 392 HCPerfValidIntervals 393 FROM HC-PerfHist-TC-MIB -- RFC 3705 395 pwIndex 396 FROM PW-STD-MIB -- RFC 5601 397 -- RFC Editor: Please replace PWMIB with actual RFC number and 398 -- remove this note 400 PwCfgIndexOrzero 401 FROM PW-TC-STD-MIB -- RFC 5542 402 -- RFC Editor: Please replace PWTC with actual RFC number and 403 -- remove this note 404 ; 406 -- The PW CEP MIB 408 pwCepStdMIB MODULE-IDENTITY 409 LAST-UPDATED "201103081200Z" -- 8 March 2011 12:00:00 GMT 410 ORGANIZATION "Pseudowire Emulation Edge-to-Edge (PWE3) 411 Working Group" 412 CONTACT-INFO 413 " 414 David Zelig (Ed.) 415 E-mail: David Zelig 417 Ron Cohen (Ed.) 418 Email: ronc@resolutenetworks.com 420 Thomas D. Nadeau (Ed.) 421 Email: tnadeau@lucidvision.com 423 The PWE3 Working Group (email distribution pwe3@ietf.org, 424 http://www.ietf.org/html.charters/pwe3-charter.html) 425 " 427 DESCRIPTION 428 "This MIB module contains managed object definitions for 429 Circuit Emulation over Packet (CEP) as in: Malis, A., 430 Prayson, P., Cohen, R. and Zelig, D. 'Synchronous Optical 431 Network/Synchronous Digital Hierarchy (SONET/SDH) 432 Circuit Emulation over Packet (CEP)', RFC 4842. 434 Copyright (c) 2011 IETF Trust and the persons identified 435 as the document authors. All rights reserved. This version 436 of this MIB module is part of RFC xxxx; See the RFC itself 437 for full legal notices. 439 -- RFC Editor: Please replace XXXX with actual RFC number and 440 -- remove this note 441 " 442 -- Revision history. 443 REVISION "201103081200Z" -- 8 March 2011 12:00:00 GMT 444 DESCRIPTION "Initial version published as part of RFC XXXX." 445 -- RFC Editor: Please replace XXXX with actual RFC number and remove 446 -- this note 448 ::= { mib-2 XXXX } -- To be assigned by IANA 449 -- RFC Editor: Please replace the XXXX with the 450 -- IANA assigned value and remove this note 452 -- Local Textual conventions 454 PwCepSonetEbm ::= TEXTUAL-CONVENTION 455 STATUS current 456 DESCRIPTION 457 "Equipped Bit Mask (EBM) used for fractional STS-1/VC-3. The 458 EBM bits are the 28 least significant bits out of the 32 459 bit value." 460 SYNTAX Unsigned32 462 PwCepSdhVc4Ebm ::= TEXTUAL-CONVENTION 463 STATUS current 464 DESCRIPTION 465 "Equipped Bit Mask (EBM) used for each TUG-3 in fractional 466 VC-4 circuits. The EBM bits are the 30 least significant 467 bits out of the 32 bit value." 468 SYNTAX Unsigned32 470 PwCepSonetVtgMap ::= TEXTUAL-CONVENTION 471 STATUS current 472 DESCRIPTION 473 "The VT/VC types carried in the 7 VTG/TUG-2s. The format is 474 28 bits in the form of an Equipped Bit Mask (EBM) for 475 fractional STS-1/VC-3. The mapping specifies the maximal 476 occupancies of VT/VC within each VTG/TUG-2. For example, 477 all four bits are set to 1 in this objects it represents a 478 VTG carrying VT1.5/VC11s, while only three are set when 479 VT2/VC12 are carried within this VTG. 481 The relevant bits are the 28 least significant bits out of 482 the 32 bit value." 483 SYNTAX Unsigned32 485 PwCepFracAsyncMap ::= TEXTUAL-CONVENTION 486 STATUS current 487 DESCRIPTION 488 "The type of Asynchronous mapping carried inside STS-1, VC-3 489 or TUG-3 containing TU-3 circuit." 491 SYNTAX INTEGER { 492 other ( 1), 493 ds3 ( 2), 494 e3 ( 3) 495 } 497 -- Top level components of this MIB module. 499 -- Tables, Scalars 500 pwCepObjects OBJECT IDENTIFIER 501 ::= { pwCepStdMIB 1 } 502 -- Conformance 503 pwCepConformance OBJECT IDENTIFIER 504 ::= { pwCepStdMIB 2 } 506 -- CEP PW table 508 pwCepTable OBJECT-TYPE 509 SYNTAX SEQUENCE OF PwCepEntry 510 MAX-ACCESS not-accessible 511 STATUS current 512 DESCRIPTION 513 "This table contains objects and parameters for managing and 514 monitoring the CEP PW." 515 ::= { pwCepObjects 1 } 517 pwCepEntry OBJECT-TYPE 518 SYNTAX PwCepEntry 519 MAX-ACCESS not-accessible 520 STATUS current 521 DESCRIPTION 522 "Each entry represents the association of a SONET/SDH PATH or 523 VT to a PW. This table is indexed by the pwIndex of the 524 applicable PW entry in the pwTable. 526 An entry is created in this table by the agent for every 527 entry in the pwTable with a pwType equals 'cep'. 529 All read-write object in this table MAY be changed at any 530 time, however change of some objects (for example 531 pwCepCfgIndex) during PW forwarding state may cause 532 traffic disruption. 534 Manual entries in this table SHOULD be preserved after a 535 reboot, the agent MUST ensure the integrity of those 536 entries. If the set of entries of a specific row are found to 537 be non consistent after reboot, the PW pwOperStatus MUST be 538 declared as notPresent(5). 539 " 541 INDEX { pwIndex } 543 ::= { pwCepTable 1 } 545 PwCepEntry ::= SEQUENCE { 547 pwCepType INTEGER, 548 pwCepSonetIfIndex InterfaceIndexOrZero, 549 pwCepSonetConfigErrorOrStatus BITS, 550 pwCepCfgIndex PwCfgIndexOrzero, 551 pwCepTimeElapsed HCPerfTimeElapsed, 552 pwCepValidIntervals HCPerfValidIntervals, 553 pwCepIndications BITS, 554 pwCepLastEsTimeStamp TimeStamp, 555 pwCepPeerCepOption Unsigned32 556 } 558 pwCepType OBJECT-TYPE 559 SYNTAX INTEGER { 560 spe (1), 561 vt (2), 562 fracSpe (3) 563 } 564 MAX-ACCESS read-write 565 STATUS current 566 DESCRIPTION 567 "Specifies the sub-type of CEP PW. Currently only 568 structured types are supported: 570 'spe'(1) : SONET STS-Nc signals. 571 'vt' (2) : SONET VT-x (x=1.5,2,3,6) signals. 572 'fracSpe' (3) : SONET fractional STS-1 or SDH fractional 573 VC-3 or VC-4 carrying tributaries or 574 Asynchronous signals. 576 Support of 'vt' mode or 'fracSpe' mode is optional." 577 DEFVAL 578 { spe } 580 ::= { pwCepEntry 1 } 582 pwCepSonetIfIndex OBJECT-TYPE 583 SYNTAX InterfaceIndexOrZero 584 MAX-ACCESS read-write 585 STATUS current 586 DESCRIPTION 587 "This is a unique index within the ifTable. It represents 588 the interface index for the SONET path for SPE emulation 589 (RFC3593 section 3.3), an interface index for the SONET 590 VT (RFC3593 section 3.4) if the VT to be emulated is 591 extracted a SONET signal or locally mapped from a physical 592 interface. 594 A value of zero indicates an interface index that has yet 595 to be determined. 596 Once set, if the SONET ifIndex is (for some reason) later 597 removed, the agent MAY delete the associated PW rows 598 (e.g., this pwCepTableEntry). If the agent does not 599 delete the rows, it is RECOMMENDED that the agent set this 600 object to zero." 602 ::= { pwCepEntry 2 } 604 pwCepSonetConfigErrorOrStatus OBJECT-TYPE 605 SYNTAX BITS { 606 other ( 0), 607 timeslotInUse ( 1), 608 timeslotMisuse ( 2), 609 peerDbaIncompatible ( 3), -- Status Only 610 peerEbmIncompatible ( 4), 611 peerRtpIncompatible ( 5), 612 peerAsyncIncompatible ( 6), 613 peerDbaAsymmetric ( 7), -- Status Only 614 peerEbmAsymmetric ( 8), 615 peerRtpAsymmetric ( 9), 616 peerAsyncAsymmetric (10) 617 } 618 MAX-ACCESS read-only 619 STATUS current 620 DESCRIPTION 621 "This object reports a configuration mismatch inside 622 the local node or between the local node and the peer node. 623 Some bits indicate an error and some are simply status 624 report that does not affect the forwarding process. 626 'timeslotInUse'(1) is set when another CEP PW has already 627 reserved a timeslot(s) that this CEP PW is attempting to 628 reserved. 630 'timeslotMisuse'(2) is set when the stated timeslot this 631 PW is trying to use is not legal. For example, if 632 specifying a starting timeslot of 45 for a SONET path of 633 an STS-12c width. 635 The peerZZZIncompatible bits are set if the local configuration 636 is not compatible with the peer configuration as available 637 from the CEP option received from the peer through the 638 signaling process and the the local node cannot support such 639 asymmetric configuration. 641 The peerZZZAsymmetric bits are set if the local configuration 642 is not compatible with the peer configuration as available 643 from the CEP option received from the peer through the 644 signaling process, however the local node can support such 645 asymmetric configuration. 646 " 648 REFERENCE 649 "Malis, A., et al, 'Synchronous Optical Network/Synchronous 650 Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet 651 (CEP), RFC 4842, section 12. " 652 ::= { pwCepEntry 3 } 654 pwCepCfgIndex OBJECT-TYPE 655 SYNTAX PwCfgIndexOrzero 656 MAX-ACCESS read-write 657 STATUS current 658 DESCRIPTION 659 "Index to CEP configuration table below. Multiple CEP PWs 660 MAY share a single pwCepCfgEntry. 662 The value 0 indicates that no entries are available." 663 ::= { pwCepEntry 4 } 665 pwCepTimeElapsed OBJECT-TYPE 666 SYNTAX HCPerfTimeElapsed 667 UNITS "seconds" 668 MAX-ACCESS read-only 669 STATUS current 670 DESCRIPTION 671 "The number of seconds, including partial seconds, 672 that have elapsed since the beginning of the current 673 measurement period. If, for some reason, such as an 674 adjustment in the system's time-of-day clock, the 675 current interval exceeds the maximum value, the 676 agent will return the maximum value." 678 ::= { pwCepEntry 5 } 680 pwCepValidIntervals OBJECT-TYPE 681 SYNTAX HCPerfValidIntervals 682 MAX-ACCESS read-only 683 STATUS current 684 DESCRIPTION 685 "The number (n) of previous 15-minute intervals for which data 686 was collected. 688 An agent with CEP capability MUST be capable of supporting 689 at least 4 intervals. The RECOMMENDED default of value for 690 n is 32 and n MUST NOT exceed 96." 691 ::= { pwCepEntry 6 } 693 pwCepIndications OBJECT-TYPE 694 SYNTAX BITS { 695 missingPkt ( 0), 696 ooRngDropped( 1), 697 jtrBfrUnder ( 2), 698 pktMalformed( 3), 699 lops ( 4), 700 cepRdi ( 5), 701 cepAis ( 6), 702 badHdrStack ( 7), 703 cepNeFailure( 8), 704 cepFeFailure( 9) 705 } 706 MAX-ACCESS read-write 707 STATUS current 708 DESCRIPTION 709 "Definitions: 711 'missingPkt'(0) - While playing out a sequence of packets, a 712 at least one packet was determined to be missing based on a 713 gap in the CEP sequence number. Note: If the implementation 714 supports packet re-ordering, detecting gaps SHOULD take 715 place as they are played out, not as they arrive. This 716 provides time for mis-ordered packets to arrive late. 718 'ooRngDropped'(1) - At least one Packet arrived outside the 719 range of the jitter buffer. This may be because the 720 jitter buffer is full, or the sequence number addresses 721 a buffer outside the current jitter buffer range, or 722 addresses an already occupied buffer within range. 723 Whether or not packet re-ordering is supported by the 724 implementation, this indication MUST be supported. 726 'jtrBfrUnder'(2) - The jitter buffer underflowed because 727 not enough packets arriving as packets were being 728 played out. 730 'pktMalformed'(3) - Any error related to unexpected 731 packet format (except bad header stack) or unexpected 732 length. 734 'lops'(4) - Loss Of Packet Synchronization. 736 'cepRdi'(5) - Circuit Emulation over Packet Remote Defect 737 Indication. RDI is Generated by the remote CEP de-packetizer 738 when LOPS is detected. 740 'cepAis'(6) - Remote CEP packetizer has detected AIS 742 on its incoming SONET stream. cepAis MUST NOT (in 743 itself) cause a CEP PW down notification. 745 'badHdrStack'(7) - This indication is set when the number of 746 CEP header extensions detected in incoming packets does 747 not match the expected number. 749 'cepNeFailure'(8) - Set when CEP-NE failure is currently 750 declared. 752 'cepFeFailure'(8) - Set when CEP-FE failure is currently 753 declared. 755 This object MUST hold the accumulated indications, until the 756 next SNMP write that clear the indication(s). 758 Writing a non zero value MUST fail. 760 Currently there is no hierarchy of CEP defects. 762 The algorithm used to capture these indications 763 is implementation specific." 765 ::= { pwCepEntry 7 } 767 pwCepLastEsTimeStamp OBJECT-TYPE 768 SYNTAX TimeStamp 769 MAX-ACCESS read-only 770 STATUS current 771 DESCRIPTION 772 "The value of sysUpTime on the most recent occasion at 773 which the CEP PW entered the ES or SES state." 775 ::= { pwCepEntry 8 } 777 pwCepPeerCepOption OBJECT-TYPE 778 SYNTAX Unsigned32 779 MAX-ACCESS read-only 780 STATUS current 781 DESCRIPTION 782 "The value of CEP option parameter as received from the peer 783 by the PW signaling protocol." 785 ::= { pwCepEntry 9 } 787 -- End of CEP PW table 789 -- Obtain index for PW CEP Configuration table entries 791 pwCepCfgIndexNext OBJECT-TYPE 792 SYNTAX PwCfgIndexOrzero 793 MAX-ACCESS read-only 794 STATUS current 795 DESCRIPTION 796 "This object contains an appropriate value to be used 797 for pwCepCfgIndex when creating entries in the 798 pwCepCfgTable. The value 0 indicates that no 799 unassigned entries are available. To obtain the 800 value of pwCepCfgIndex for a new entry in the 801 pwCepCfgTable, the manager issues a management 802 protocol retrieval operation to obtain the current 803 value of pwCepCfgIndex. After each retrieval 804 operation, the agent should modify the value to 805 reflect the next unassigned index. After a manager 806 retrieves a value the agent will determine through 807 its local policy when this index value will be made 808 available for reuse." 810 ::= { pwCepObjects 2 } 812 -- PW CEP PW Configuration Table 814 pwCepCfgTable OBJECT-TYPE 815 SYNTAX SEQUENCE OF PwCepCfgEntry 816 MAX-ACCESS not-accessible 817 STATUS current 818 DESCRIPTION 819 "This table contains a set of parameters that may be 820 referenced by one or more CEP PWs by pwCepTable." 822 ::= { pwCepObjects 3 } 824 pwCepCfgEntry OBJECT-TYPE 825 SYNTAX PwCepCfgEntry 826 MAX-ACCESS not-accessible 827 STATUS current 828 DESCRIPTION 829 "These parameters define the characteristics of a 830 CEP PW. They are grouped here to ease NMS burden. 831 Once an entry is created here it may be re-used 832 by many PWs. 834 By default, all the read-create objects MUST NOT be 835 changed after row activation, unless specifically indicated 836 in the individual object description. If the operator 837 wish to change value of a read-create object, the 838 pwCepCfgRowStatus MUST be set to notInService(2). 840 The agent MUST NOT allow the change of the pwCepCfgRowStatus 841 from the active(1) state for pwCepCfgEntry which is in 842 use by at least one active PW. 844 Manual entries in this table SHOULD be preserved after a 845 re-boot, the agent MUST ensure the integrity of those 846 entries. If the set of entries of a specific row are found to 847 be non consistent after reboot, the affected PWs pwOperStatus 848 MUST be declared as notPresent(5). 849 " 851 INDEX { pwCepCfgTableIndex } 853 ::= { pwCepCfgTable 1 } 855 PwCepCfgEntry ::= SEQUENCE { 856 pwCepCfgTableIndex Unsigned32, 857 pwCepSonetPayloadLength Unsigned32, 858 pwCepCfgMinPktLength Unsigned32, 859 pwCepCfgPktReorder TruthValue, 860 pwCepCfgEnableDBA BITS, 861 pwCepCfgRtpHdrSuppress TruthValue, 863 pwCepCfgJtrBfrDepth Unsigned32, 865 pwCepCfgConsecPktsInsync Unsigned32, 866 pwCepCfgConsecMissingOutSync Unsigned32, 868 pwCepCfgPktErrorPlayOutValue Unsigned32, 870 pwCepCfgMissingPktsToSes Unsigned32, 871 pwCepCfgSesToUas Unsigned32, 872 pwCepCfgSecsToExitUas Unsigned32, 873 pwCepCfgName SnmpAdminString, 875 pwCepCfgRowStatus RowStatus, 876 pwCepCfgStorageType StorageType 877 } 879 pwCepCfgTableIndex OBJECT-TYPE 880 SYNTAX Unsigned32 (1..4294967295) 881 MAX-ACCESS not-accessible 882 STATUS current 883 DESCRIPTION 884 "Primary index to this table." 885 ::= { pwCepCfgEntry 1 } 887 pwCepSonetPayloadLength OBJECT-TYPE 888 SYNTAX Unsigned32 889 MAX-ACCESS read-create 890 STATUS current 891 DESCRIPTION 892 "The number of SONET bytes of the Path or VT carried as 893 payload within one packet. For example, for STS-1/VC-3 SPE 894 circuits, value of 783 bytes indicates that each packet 895 carries payload equivalent to one frame. For VT1.5/VC11 896 circuits, a payload length of 104 bytes indicates that each 897 packet carries payload equivalent to one VT1.5 super-frame. 898 The actual payload size may be different, due to bandwidth 899 reduction modes, e.g. DBA mode or dynamically assigned 900 fractional SPE. This length applies to 901 inbound and outbound packets carrying user payload. 902 Although there is no control over inbound packets, those 903 of illegal length are discarded and accounted for (see 904 pwCepPerf...Malformed.) 905 The default values are determined by the pwCepType: 906 783 for pwCepType equal spe(2) or fracSpe(3). 907 For vt(3) modes, the applicable super-frame payload size 908 is the default value. 909 " 910 REFERENCE 911 "Malis, A., et al, 'Synchronous Optical Network/Synchronous 912 Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet 913 (CEP), RFC 4842, sections 5.1 and 12.1" 914 ::= { pwCepCfgEntry 2 } 916 pwCepCfgMinPktLength OBJECT-TYPE 917 SYNTAX Unsigned32 918 MAX-ACCESS read-create 919 STATUS current 920 DESCRIPTION 921 "This object defines the minimum CEP packet length in 922 number of bytes (including CEP header and payload). 923 It applies to CEP's bandwidth-savings packets. Currently 924 DBA is the only bandwidth-savings packet type (in the 925 future, CEP may support compression). Minimum packet 926 length is necessary in some systems or networks. 928 Setting Zero here indicates that there is no minimum 929 packet restriction." 931 DEFVAL { 0 } 933 ::= { pwCepCfgEntry 3 } 935 pwCepCfgPktReorder OBJECT-TYPE 936 SYNTAX TruthValue 937 MAX-ACCESS read-only 938 STATUS current 939 DESCRIPTION 940 "This object defines if reordering is applied for incoming 941 packets. 943 If set 'true' - as inbound packets are queued in the 944 jitter buffer, out of order packets are re-ordered. The 945 maximum sequence number differential (i.e., the range in 946 which re-sequencing can occur) is dependant on the depth 947 of the jitter buffer. 949 If the local agent support packet re-ordering, the default 950 value SHOULD be set to 'true', otherwise, this value 951 SHOULD be set to 'false'." 953 ::= { pwCepCfgEntry 4 } 955 pwCepCfgEnableDBA OBJECT-TYPE 956 SYNTAX BITS { 957 ais (0), 958 unequipped (1) 959 } 961 MAX-ACCESS read-create 962 STATUS current 963 DESCRIPTION 964 "This object defines when DBA (dynamic bandwidth 965 allocation) is applied for packets sent toward the PSN. 967 Setting 'ais' MUST cause CEP packet payload suppression 968 when AIS is detected on the associated SONET path. 970 Similarly, 'unequipped' MUST cause payload suppression 971 when an un-equipped condition is detected on the SONET/SDH 972 PATH/VT. 973 During DBA condition, CEP packets will continue 974 to be sent, but with indicators set in the CEP header 975 instructing the remote to play all ones (for AIS) or all 976 zeros (for un-equipped) onto its SONET/SDH path. 978 NOTE: Some implementations may not support this feature. 979 In these cases, this object should be read-only." 981 REFERENCE 982 "Malis, A., et al, 'Synchronous Optical Network/Synchronous 983 Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet 984 (CEP), RFC 4842, section 11.1. " 986 ::= { pwCepCfgEntry 5 } 988 pwCepCfgRtpHdrSuppress OBJECT-TYPE 989 SYNTAX TruthValue 990 MAX-ACCESS read-create 991 STATUS current 992 DESCRIPTION 993 "If this object is set to 'true', an RTP header is not 994 pre-pended to the CEP packet." 995 REFERENCE 996 "Malis, A., et al, 'Synchronous Optical Network/Synchronous 997 Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet 998 (CEP), RFC 4842, section 5.3." 999 DEFVAL 1000 { true } 1002 ::= { pwCepCfgEntry 6 } 1004 pwCepCfgJtrBfrDepth OBJECT-TYPE 1005 SYNTAX Unsigned32 1006 UNITS "micro-seconds" 1007 MAX-ACCESS read-create 1008 STATUS current 1009 DESCRIPTION 1010 "This object defines the number of microseconds 1011 of expected packet delay variation for this CEP PW 1012 over the PSN. 1014 The actual jitter buffer MUST be at least twice this 1015 value for proper operation. 1017 If configured to a value not supported by the 1018 implementation, the agent MUST reject the SNMP Set 1019 operation." 1020 REFERENCE 1021 "The control of jitter and wander within digital 1022 networks which are based on the synchronous digital 1023 hierarchy (SDH), ITU-T Recommendation G.825." 1024 ::= { pwCepCfgEntry 7 } 1026 -- 1027 -- The following counters work together to integrate (filter) 1028 -- errors and the lack of errors on the CEP PW. An error is 1029 -- caused by a missing packet. Missing packet can be a result 1030 -- of packet loss in the network, (uncorrectable) packet out 1031 -- of sequence, packet length error, jitter buffer overflow, 1032 -- and jitter buffer underflow. The result declares whether 1033 -- or not the CEP PW is in Loss of Packet Sync (LOPS) state. 1034 -- 1036 pwCepCfgConsecPktsInsync OBJECT-TYPE 1037 SYNTAX Unsigned32 1038 MAX-ACCESS read-create 1039 STATUS current 1040 DESCRIPTION 1041 "Consecutive pkts with sequential sequence 1042 numbers required to exit the LOPS state." 1043 REFERENCE 1044 "Malis, A., et al, 'Synchronous Optical Network/Synchronous 1045 Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet 1046 (CEP), RFC 4842, section 6.2.2. " 1047 DEFVAL 1048 { 2 } 1050 ::= { pwCepCfgEntry 8 } 1052 pwCepCfgConsecMissingOutSync OBJECT-TYPE 1053 SYNTAX Unsigned32 1054 MAX-ACCESS read-create 1055 STATUS current 1056 DESCRIPTION 1057 "Consecutive missing pkts required to enter 1058 the LOPS state." 1059 REFERENCE 1060 "Malis, A., et al, 'Synchronous Optical Network/Synchronous 1061 Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet 1062 (CEP), RFC 4842, section 6.2.2. " 1063 DEFVAL 1064 { 10 } 1066 ::= { pwCepCfgEntry 9 } 1068 pwCepCfgPktErrorPlayOutValue OBJECT-TYPE 1069 SYNTAX Unsigned32 (0..255) 1070 MAX-ACCESS read-create 1071 STATUS current 1072 DESCRIPTION 1073 "This object defines the value played when inbound packets 1074 have over/underflowed the jitter buffer, or are missing 1075 for any reason. This byte pattern is sent (played) on 1076 the SONET path." 1077 DEFVAL 1078 { 255 } -- Play all ones, equal to AIS indications. 1079 ::= { pwCepCfgEntry 10 } 1081 pwCepCfgMissingPktsToSes OBJECT-TYPE 1082 SYNTAX Unsigned32 1083 UNITS "seconds" 1084 MAX-ACCESS read-create 1085 STATUS current 1086 DESCRIPTION 1087 "The number of missing packets detected (consecutive or not) 1088 within a 1 second window to cause a Severely Errored 1089 Second (SES) to be counted." 1090 REFERENCE 1091 "Malis, A., et al, 'Synchronous Optical Network/Synchronous 1092 Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet 1093 (CEP), RFC 4842, section 10.1." 1094 DEFVAL 1095 { 3 } 1096 ::= { pwCepCfgEntry 11 } 1098 pwCepCfgSesToUas OBJECT-TYPE 1099 SYNTAX Unsigned32 1100 UNITS "seconds" 1101 MAX-ACCESS read-create 1102 STATUS current 1103 DESCRIPTION 1104 "The number of consecutive SESs before declaring PW in UAS 1105 state (and at which point pwCepPerfUASs starts counting). 1106 The SesToUas default value is 10 seconds. 1108 NOTE: Similar to RFC 3592, If the agent chooses to update 1109 the various performance statistics in real time it MUST 1110 be prepared to retroactively reduce the ES, SES, counts by 1111 this value and increase the UAS count by this value when it 1112 determines that UAS state has been entered. 1114 NOTE: See pwCepPerfSESs and pwCepPerfUASs." 1115 REFERENCE 1116 "Malis, A., et al, 'Synchronous Optical Network/Synchronous 1117 Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet 1118 (CEP), RFC 4842, section 10.1." 1119 DEFVAL 1120 { 10 } 1121 ::= { pwCepCfgEntry 12 } 1123 pwCepCfgSecsToExitUas OBJECT-TYPE 1124 SYNTAX Unsigned32 1125 UNITS "seconds" 1126 MAX-ACCESS read-create 1127 STATUS current 1128 DESCRIPTION 1129 "The number of consecutive nonSESs before declaring PW is NOT 1130 in UAS state (and at which point pwCepPerfUASs stops 1131 counting)." 1132 REFERENCE 1133 "Malis, A., et al, 'Synchronous Optical Network/Synchronous 1134 Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet 1135 (CEP), RFC 4842, section 10.1." 1136 DEFVAL { 10 } 1137 ::= { pwCepCfgEntry 13 } 1139 pwCepCfgName OBJECT-TYPE 1140 SYNTAX SnmpAdminString 1141 MAX-ACCESS read-create 1142 STATUS current 1143 DESCRIPTION 1144 "This variable contains the name of the Configuration entry. 1145 This name may be used to help the NMS to display the 1146 purpose of the entry." 1147 ::= { pwCepCfgEntry 14 } 1149 pwCepCfgRowStatus OBJECT-TYPE 1150 SYNTAX RowStatus 1151 MAX-ACCESS read-create 1152 STATUS current 1153 DESCRIPTION 1154 "For creating, modifying and deleting this row. 1156 None of the read-create objects values can be changed 1157 when pwCepCfgRowStatus is in the active(1) state. Changes 1158 are allowed when the pwRowStatus is in notInService(2) or 1159 notReady(3) states only. 1161 If the operator need to change one of the values for an 1162 active row (for example in order to fix a mismatch in 1163 configuration between the local node and the peer), the 1164 pwCepCfgRowStatus should be first changed to 1165 notInService(2), the objects may be changed now and later 1166 to active(1) in order to re-initiate the signaling process 1167 with the new values in effect. 1169 Change of status from the active(1) state or deleting a row 1170 SHOULD be blocked by the local agent if the row is 1171 referenced by any pwCepEntry those pwRowStatus 1172 is in the active(1) state." 1174 ::= { pwCepCfgEntry 15 } 1176 pwCepCfgStorageType OBJECT-TYPE 1177 SYNTAX StorageType 1178 MAX-ACCESS read-create 1179 STATUS current 1180 DESCRIPTION 1181 "This object indicates the storage type for this row." 1182 DEFVAL { nonVolatile } 1184 ::= { pwCepCfgEntry 16 } 1186 -- End of CEP PW Configuration Parameter Table 1188 -- Fractional CEP Configuration Table 1190 pwCepFracTable OBJECT-TYPE 1191 SYNTAX SEQUENCE OF PwCepFracEntry 1192 MAX-ACCESS not-accessible 1193 STATUS current 1194 DESCRIPTION 1195 "This table contains a set of parameters for CEP PWs with 1196 pwCepType FRAC type." 1197 ::= { pwCepObjects 4 } 1199 pwCepFracEntry OBJECT-TYPE 1200 SYNTAX PwCepFracEntry 1201 MAX-ACCESS not-accessible 1202 STATUS current 1203 DESCRIPTION 1204 "An entry of this table can be created in two options: 1205 - By the EMS in advance for creating the PW. 1206 - By the agent automatically when the PW is set up. 1208 The first option is typically used when there is an NSP 1209 cross-connect option between the physical ports and the 1210 emulated (virtual ports), while the second MAY be used 1211 when there is a one-to-one mapping between the emulated 1212 signal and the physical signal. " 1214 INDEX { pwCepFracIndex } 1215 ::= { pwCepFracTable 1 } 1217 PwCepFracEntry ::= SEQUENCE { 1219 pwCepFracIndex InterfaceIndex, 1220 pwCepFracMode INTEGER, 1221 pwCepFracConfigError BITS, 1222 pwCepFracAsync PwCepFracAsyncMap, 1223 pwCepFracVtgMap PwCepSonetVtgMap, 1224 pwCepFracEbm PwCepSonetEbm, 1225 pwCepFracPeerEbm PwCepSonetEbm, 1226 pwCepFracSdhVc4Mode INTEGER, 1227 pwCepFracSdhVc4Tu3Map1 PwCepFracAsyncMap, 1228 pwCepFracSdhVc4Tu3Map2 PwCepFracAsyncMap, 1229 pwCepFracSdhVc4Tu3Map3 PwCepFracAsyncMap, 1230 pwCepFracSdhVc4Tug2Map1 PwCepSonetVtgMap, 1231 pwCepFracSdhVc4Tug2Map2 PwCepSonetVtgMap, 1232 pwCepFracSdhVc4Tug2Map3 PwCepSonetVtgMap, 1233 pwCepFracSdhVc4Ebm1 PwCepSdhVc4Ebm, 1234 pwCepFracSdhVc4Ebm2 PwCepSdhVc4Ebm, 1235 pwCepFracSdhVc4Ebm3 PwCepSdhVc4Ebm, 1236 pwCepFracSdhVc4PeerEbm1 PwCepSdhVc4Ebm, 1237 pwCepFracSdhVc4PeerEbm2 PwCepSdhVc4Ebm, 1238 pwCepFracSdhVc4PeerEbm3 PwCepSdhVc4Ebm, 1239 pwCepFracRowStatus RowStatus, 1240 pwCepFracStorageType StorageType 1241 } 1243 pwCepFracIndex OBJECT-TYPE 1244 SYNTAX InterfaceIndex 1245 MAX-ACCESS not-accessible 1246 STATUS current 1247 DESCRIPTION 1248 "This is the index of this table. It is a unique 1249 index within the ifTable. It represents the interface index 1250 for the SONET path (RFC 3592 section 3.3) for fractional SPE 1251 emulation. 1253 It may represent an internal (virtual) interface if an NSP 1254 function exists between the physical interface and the 1255 emulation process." 1257 ::= { pwCepFracEntry 1 } 1259 pwCepFracMode OBJECT-TYPE 1260 SYNTAX INTEGER { 1261 notApplicable ( 1), 1262 dynamic ( 2), 1263 static ( 3), 1264 staticWithEbm ( 4), 1265 staticAsync ( 5) 1266 } 1267 MAX-ACCESS read-create 1268 STATUS current 1269 DESCRIPTION 1270 "Fractional mode for STS-1/VC-3 or VC-4 circuits: 1271 notApplicable - When this object is not applicable. 1272 dynamic - EBM carried within the CEP header. Unequipped 1273 VTs are removed from the payload on the fly. 1274 static - EBM not carried within the CEP header. Only VTs 1275 defined in the EBM are carried within the payload. 1276 staticWithEbm - EBM carried within the CEP header. Only 1277 VTs defined in the EBM are carried within the 1278 payload. 1279 staticAsync - Asynchronous E3/T3 fixed byte removal only. " 1281 DEFVAL 1282 { dynamic } 1284 ::= { pwCepFracEntry 2 } 1286 pwCepFracConfigError OBJECT-TYPE 1287 SYNTAX BITS { 1288 other ( 0), 1289 vtgMapEbmConflict ( 1), 1290 vtgMapAsyncConflict ( 2) 1291 } 1292 MAX-ACCESS read-only 1293 STATUS current 1294 DESCRIPTION 1295 "vtgMapEbmConflict(1) is set when the configured static EBM 1296 does not match the configured vtgMap for fractional 1297 STS-1/VC-3 circuits, or when the TUG2Map is in conflict with 1298 the static EBM for VC-4 circuits. For example, if the vtgMap 1299 specifies that VTG#1 carries VT2 VTs while the EBM indicate 1300 that four VTs are equipped within VTG#1. 1302 vtgMapAsyncConflict(2) is set when there is a conflict between 1303 the mode, the async indication and the vtgMap fields. For 1304 example, fractional mode is set to Static Async while the 1305 VtgMap indicate that the STS-1/VC-3 carries VTs, or in 1306 fractional VC-4 circuits where both async1 and Tug2Map are 1307 set." 1309 ::= { pwCepFracEntry 3 } 1311 pwCepFracAsync OBJECT-TYPE 1312 SYNTAX PwCepFracAsyncMap 1313 MAX-ACCESS read-create 1314 STATUS current 1315 DESCRIPTION 1316 "This object defines the The asynchronous payload carried 1317 within the STS-1/VC-3. This object is applicable when 1318 pwCepFracMode equals 'staticAsync' and MUST equals to 1319 'other' otherwise." 1321 DEFVAL { other } 1323 ::= { pwCepFracEntry 4 } 1325 pwCepFracVtgMap OBJECT-TYPE 1326 SYNTAX PwCepSonetVtgMap 1327 MAX-ACCESS read-create 1328 STATUS current 1329 DESCRIPTION 1330 "This object defines the VT/VC types of the seven 1331 VTG/TUG-2 within the STS-1/VC-3. 1332 This variable should be set when 'dynamic', 'static' 1333 or 'staticWithEbm' Fractional STS-1/VC-3 pwCepFracMode 1334 is selected. " 1336 ::= { pwCepFracEntry 5 } 1338 pwCepFracEbm OBJECT-TYPE 1339 SYNTAX PwCepSonetEbm 1340 MAX-ACCESS read-create 1341 STATUS current 1342 DESCRIPTION 1343 "This object holds the static Equipped Bit Mask (EBM) 1344 for STS-1/VC-3 channel. 1345 This variable MAY be set when 'static' or 1346 'staticWithEbm' Fractional STS-1/VC-3 pwCepFracMode is 1347 selected. 1348 It is possible that the configuration of other MIB modules 1349 will define the EBM value - in these cases this object is 1350 read-only and reflects the actual EBM that would be used." 1352 ::= { pwCepFracEntry 6 } 1354 pwCepFracPeerEbm OBJECT-TYPE 1355 SYNTAX PwCepSonetEbm 1356 MAX-ACCESS read-only 1357 STATUS current 1358 DESCRIPTION 1359 "This object reports the Equipped Bit Mask (EBM) for 1360 STS-1/VC-3 channel as received from the peer within 1361 the CEP extension header." 1363 ::= { pwCepFracEntry 7 } 1365 pwCepFracSdhVc4Mode OBJECT-TYPE 1366 SYNTAX INTEGER { 1367 notApplicable ( 1), 1368 dynamic ( 2), 1369 static ( 3), 1370 staticWithEbm ( 4) 1371 } 1372 MAX-ACCESS read-create 1373 STATUS current 1374 DESCRIPTION 1376 "Fractional mode for VC-4 circuits: 1378 notApllicable - When this is not VC-4 circuit. 1379 dynamic - EBM carried within the CEP header. Unequipped 1380 VTs are removed from the payload on the fly. 1381 static - EBM not carried within the CEP header. Only VTs 1382 defined in the EBM are carried within the payload. 1383 staticWithEbm - EBM carried within the CEP header. Only 1384 VTs defined in the EBM are carried within the 1385 payload. " 1387 DEFVAL { notApplicable } 1389 ::= { pwCepFracEntry 8 } 1391 pwCepFracSdhVc4Tu3Map1 OBJECT-TYPE 1392 SYNTAX PwCepFracAsyncMap 1393 MAX-ACCESS read-create 1394 STATUS current 1395 DESCRIPTION 1396 "The type of Asynchronous mapping carried inside STS-1, VC-3 1397 or TUG-3 containing TU-3 circuit." 1399 DEFVAL { other } 1400 ::= { pwCepFracEntry 9 } 1402 pwCepFracSdhVc4Tu3Map2 OBJECT-TYPE 1403 SYNTAX PwCepFracAsyncMap 1404 MAX-ACCESS read-create 1405 STATUS current 1406 DESCRIPTION 1407 "If the second TUG-3 within the VC-4 contains a TU-3, this 1408 variable must be set." 1410 DEFVAL { other } 1411 ::= { pwCepFracEntry 10 } 1413 pwCepFracSdhVc4Tu3Map3 OBJECT-TYPE 1414 SYNTAX PwCepFracAsyncMap 1415 MAX-ACCESS read-create 1416 STATUS current 1417 DESCRIPTION 1418 "If the third TUG-3 within the VC-4 contains a TU-3, this 1419 variable must be set. " 1421 DEFVAL { other } 1423 ::= { pwCepFracEntry 11 } 1425 pwCepFracSdhVc4Tug2Map1 OBJECT-TYPE 1426 SYNTAX PwCepSonetVtgMap 1427 MAX-ACCESS read-create 1428 STATUS current 1429 DESCRIPTION 1430 "The VC types of the seven TUG-2 within the first 1431 TUG-3 of the VC-4. " 1433 ::= { pwCepFracEntry 12 } 1435 pwCepFracSdhVc4Tug2Map2 OBJECT-TYPE 1436 SYNTAX PwCepSonetVtgMap 1437 MAX-ACCESS read-create 1438 STATUS current 1439 DESCRIPTION 1440 "The VC types of the seven TUG-2 within the second 1441 TUG-3 of the VC-4. " 1442 ::= { pwCepFracEntry 13 } 1444 pwCepFracSdhVc4Tug2Map3 OBJECT-TYPE 1445 SYNTAX PwCepSonetVtgMap 1446 MAX-ACCESS read-create 1447 STATUS current 1448 DESCRIPTION 1449 "The VC types of the seven TUG-2 within the third 1450 TUG-3 of the VC-4. " 1452 ::= { pwCepFracEntry 14 } 1454 pwCepFracSdhVc4Ebm1 OBJECT-TYPE 1455 SYNTAX PwCepSdhVc4Ebm 1456 MAX-ACCESS read-create 1457 STATUS current 1458 DESCRIPTION 1459 "Static Equipped Bit Mask (EBM) for first TUG-3 within 1460 the VC-4. 1461 This variable should be set when 'static' or 1462 'staticWithEbm' Fractional VC-4 pwCepFracMode is 1463 selected. 1464 It is possible that the EBM that would be used is 1465 available based on configuration of other MIB modules. 1466 In these cases this object is read-only and reflects the 1467 actual EBM that would be used." 1469 ::= { pwCepFracEntry 15 } 1471 pwCepFracSdhVc4Ebm2 OBJECT-TYPE 1472 SYNTAX PwCepSdhVc4Ebm 1473 MAX-ACCESS read-create 1474 STATUS current 1475 DESCRIPTION 1476 "Static Equipped Bit Mask (EBM) for second TUG-3 within 1477 the VC-4. 1478 This variable should be set when 'static' or 1479 'StaticWithEbm' Fractional VC-4 pwCepFracMode is 1480 selected. 1481 It is possible that the EBM that would be used is 1482 available based on configuration of other MIB modules. 1483 In these cases this object is read-only and reflects the 1484 actual EBM that would be used." 1486 ::= { pwCepFracEntry 16 } 1488 pwCepFracSdhVc4Ebm3 OBJECT-TYPE 1489 SYNTAX PwCepSdhVc4Ebm 1490 MAX-ACCESS read-create 1491 STATUS current 1492 DESCRIPTION 1493 "Static Equipped Bit Mask (EBM) for third TUG-3 within 1494 the VC-4. 1495 This variable should be set when 'Static' or 1496 'staticWithEbm' Fractional VC-4 pwCepFracMode is 1497 selected. 1498 It is possible that the EBM that would be used is 1499 available based on configuration of other MIB modules. 1500 In these cases this object is read-only and reflects the 1501 actual EBM that would be used." 1503 ::= { pwCepFracEntry 17 } 1505 pwCepFracSdhVc4PeerEbm1 OBJECT-TYPE 1506 SYNTAX PwCepSdhVc4Ebm 1507 MAX-ACCESS read-only 1508 STATUS current 1509 DESCRIPTION 1510 "Equipped Bit Mask (EBM) for the first TUG-3 within 1511 the fractional VC-4 channel received from peer 1512 within the CEP extension header." 1514 ::= { pwCepFracEntry 18 } 1516 pwCepFracSdhVc4PeerEbm2 OBJECT-TYPE 1517 SYNTAX PwCepSdhVc4Ebm 1518 MAX-ACCESS read-only 1519 STATUS current 1520 DESCRIPTION 1521 "Equipped Bit Mask (EBM) for the second TUG-3 within 1522 the fractional VC-4 channel received from peer 1523 within the CEP extension header." 1525 ::= { pwCepFracEntry 19 } 1527 pwCepFracSdhVc4PeerEbm3 OBJECT-TYPE 1528 SYNTAX PwCepSdhVc4Ebm 1529 MAX-ACCESS read-only 1530 STATUS current 1531 DESCRIPTION 1532 "Equipped Bit Mask (EBM) for the third TUG-3 within 1533 the fractional VC-4 channel received from peer 1534 within the CEP extension header." 1536 ::= { pwCepFracEntry 20 } 1538 pwCepFracRowStatus OBJECT-TYPE 1539 SYNTAX RowStatus 1540 MAX-ACCESS read-create 1541 STATUS current 1542 DESCRIPTION 1543 "For creating, modifying and deleting this row. 1544 This object MAY be changed at any time." 1546 ::= { pwCepFracEntry 21 } 1548 pwCepFracStorageType OBJECT-TYPE 1549 SYNTAX StorageType 1550 MAX-ACCESS read-create 1551 STATUS current 1552 DESCRIPTION 1553 "This variable indicates the storage type for this 1554 object." 1556 DEFVAL { nonVolatile } 1557 ::= { pwCepFracEntry 22 } 1559 -- End Fractional CEP Configuration Table 1561 -- CEP PW Performance Current Interval Table. 1563 pwCepPerfCurrentTable OBJECT-TYPE 1564 SYNTAX SEQUENCE OF PwCepPerfCurrentEntry 1565 MAX-ACCESS not-accessible 1566 STATUS current 1567 DESCRIPTION 1568 "CEP bridges the SONET and packet worlds. In the packet 1569 world, counts typically start from the time of service 1570 creation - and don't stop. In the SONET world, counts are 1571 kept in 15-minute intervals. The PW CEP MIB supports both 1572 methods. The current 15-minute interval counts are in 1573 this table. The interval and total stats are in tables 1574 following this. 1576 This table provides per CEP PW performance information. 1577 HC (high capacity) counters are required for some counts 1578 due to the high speeds expected with CEP services. A SONET 1579 path of width 48 (STS-48c) can rollover non-HC counters in 1580 a few minutes." 1582 ::= { pwCepObjects 5 } 1584 pwCepPerfCurrentEntry OBJECT-TYPE 1585 SYNTAX PwCepPerfCurrentEntry 1586 MAX-ACCESS not-accessible 1587 STATUS current 1588 DESCRIPTION 1589 "An entry in this table is created by the agent for every 1590 pwCep entry. After 15 minutes, the contents of this table 1591 entry are copied to a new entry in the pwCepPerfInterval 1592 table and the counts in this entry are reset to zero." 1594 INDEX { pwIndex } 1596 ::= { pwCepPerfCurrentTable 1 } 1598 PwCepPerfCurrentEntry ::= SEQUENCE { 1599 pwCepPerfCurrentDbaInPacketsHC HCPerfCurrentCount, 1600 pwCepPerfCurrentDbaOutPacketsHC HCPerfCurrentCount, 1602 pwCepPerfCurrentInNegPtrAdjust PerfCurrentCount, 1603 pwCepPerfCurrentInPosPtrAdjust PerfCurrentCount, 1604 pwCepPerfCurrentInPtrAdjustSecs PerfCurrentCount, 1605 pwCepPerfCurrentOutNegPtrAdjust PerfCurrentCount, 1606 pwCepPerfCurrentOutPosPtrAdjust PerfCurrentCount, 1607 pwCepPerfCurrentOutPtrAdjustSecs PerfCurrentCount, 1608 pwCepPerfCurrentAbsPtrAdjust Integer32, 1610 pwCepPerfCurrentMissingPkts PerfCurrentCount, 1611 pwCepPerfCurrentPktsOoseq PerfCurrentCount, 1612 pwCepPerfCurrentPktsOoRngDropped PerfCurrentCount, 1613 pwCepPerfCurrentJtrBfrUnderruns PerfCurrentCount, 1614 pwCepPerfCurrentPktsMalformed PerfCurrentCount, 1615 pwCepPerfCurrentSummaryErrors PerfCurrentCount, 1617 pwCepPerfCurrentESs PerfCurrentCount, 1618 pwCepPerfCurrentSESs PerfCurrentCount, 1619 pwCepPerfCurrentUASs PerfCurrentCount, 1620 pwCepPerfCurrentFC PerfCurrentCount 1621 } 1623 pwCepPerfCurrentDbaInPacketsHC OBJECT-TYPE 1624 SYNTAX HCPerfCurrentCount 1625 MAX-ACCESS read-only 1626 STATUS current 1627 DESCRIPTION 1628 "Number of DBA packets received." 1629 ::= { pwCepPerfCurrentEntry 1 } 1631 pwCepPerfCurrentDbaOutPacketsHC OBJECT-TYPE 1632 SYNTAX HCPerfCurrentCount 1633 MAX-ACCESS read-only 1634 STATUS current 1635 DESCRIPTION 1636 "Number of DBA packets sent." 1637 ::= { pwCepPerfCurrentEntry 2 } 1639 -- Pointer adjustment stats 1641 pwCepPerfCurrentInNegPtrAdjust OBJECT-TYPE 1642 SYNTAX PerfCurrentCount 1643 MAX-ACCESS read-only 1644 STATUS current 1645 DESCRIPTION 1646 "Number of negative pointer adjustments sent on the 1647 SONET path based on CEP pointer adjustments received." 1648 ::= { pwCepPerfCurrentEntry 3 } 1650 pwCepPerfCurrentInPosPtrAdjust OBJECT-TYPE 1651 SYNTAX PerfCurrentCount 1652 MAX-ACCESS read-only 1653 STATUS current 1654 DESCRIPTION 1655 "Number of positive pointer adjustments sent on the 1656 SONET path based on CEP pointer adjustments received." 1657 ::= { pwCepPerfCurrentEntry 4 } 1659 pwCepPerfCurrentInPtrAdjustSecs OBJECT-TYPE 1660 SYNTAX PerfCurrentCount 1661 UNITS "seconds" 1662 MAX-ACCESS read-only 1663 STATUS current 1664 DESCRIPTION 1665 "Number of seconds in which a positive or negative pointer 1666 adjustment was sent on the SONET path." 1667 ::= { pwCepPerfCurrentEntry 5 } 1669 pwCepPerfCurrentOutNegPtrAdjust OBJECT-TYPE 1670 SYNTAX PerfCurrentCount 1671 MAX-ACCESS read-only 1672 STATUS current 1673 DESCRIPTION 1674 "Number of negative pointer adjustments seen on the 1675 SONET path and encoded onto sent CEP packets." 1676 ::= { pwCepPerfCurrentEntry 6 } 1678 pwCepPerfCurrentOutPosPtrAdjust OBJECT-TYPE 1679 SYNTAX PerfCurrentCount 1680 MAX-ACCESS read-only 1681 STATUS current 1682 DESCRIPTION 1683 "Number of positive pointer adjustments seen on the 1684 SONET path and encoded onto sent CEP packets." 1685 ::= { pwCepPerfCurrentEntry 7 } 1687 pwCepPerfCurrentOutPtrAdjustSecs OBJECT-TYPE 1688 SYNTAX PerfCurrentCount 1689 UNITS "seconds" 1690 MAX-ACCESS read-only 1691 STATUS current 1692 DESCRIPTION 1693 "Number of seconds in which a positive or negative pointer 1694 adjustment was seen on the SONET path." 1695 ::= { pwCepPerfCurrentEntry 8 } 1697 pwCepPerfCurrentAbsPtrAdjust OBJECT-TYPE 1698 SYNTAX Integer32 1699 MAX-ACCESS read-only 1700 STATUS current 1701 DESCRIPTION 1702 "Indicates the relative adjustment drift between 1703 inbound and outbound streams. 1705 It is calculated as absolute value of : 1706 ( InPosPtrAdjust - InNegPtrAdjust ) - 1707 (OutPosPtrAdjust - OutNegPtrAdjust) " 1708 ::= { pwCepPerfCurrentEntry 9 } 1710 pwCepPerfCurrentMissingPkts OBJECT-TYPE 1711 SYNTAX PerfCurrentCount 1712 MAX-ACCESS read-only 1713 STATUS current 1714 DESCRIPTION 1715 "Number of missing packets (as detected via CEP header 1716 sequence number gaps)." 1717 ::= { pwCepPerfCurrentEntry 10 } 1719 pwCepPerfCurrentPktsOoseq OBJECT-TYPE 1720 SYNTAX PerfCurrentCount 1721 MAX-ACCESS read-only 1722 STATUS current 1723 DESCRIPTION 1724 "Number of packets detected out of sequence (via CEP 1725 header sequence numbers), but successfully re-ordered. 1726 Note: Some implementations may not support this 1727 feature (see pwCepCfgPktReorder)." 1728 ::= { pwCepPerfCurrentEntry 11 } 1730 pwCepPerfCurrentPktsOoRngDropped OBJECT-TYPE 1731 SYNTAX PerfCurrentCount 1732 MAX-ACCESS read-only 1733 STATUS current 1734 DESCRIPTION 1735 "Number of packets detected out of range (via CEP header 1736 sequence numbers) and could not be re-ordered, or could not 1737 fit in the jitter buffer." 1738 ::= { pwCepPerfCurrentEntry 12 } 1740 pwCepPerfCurrentJtrBfrUnderruns OBJECT-TYPE 1741 SYNTAX PerfCurrentCount 1742 MAX-ACCESS read-only 1743 STATUS current 1744 DESCRIPTION 1745 "Number of times a packet needed to be played out and the 1746 jitter buffer was empty." 1747 ::= { pwCepPerfCurrentEntry 13 } 1749 pwCepPerfCurrentPktsMalformed OBJECT-TYPE 1750 SYNTAX PerfCurrentCount 1751 MAX-ACCESS read-only 1752 STATUS current 1753 DESCRIPTION 1754 "Number of packets detected with unexpected size, or bad 1755 headers stack." 1756 ::= { pwCepPerfCurrentEntry 14 } 1758 pwCepPerfCurrentSummaryErrors OBJECT-TYPE 1759 SYNTAX PerfCurrentCount 1760 MAX-ACCESS read-only 1761 STATUS current 1762 DESCRIPTION 1763 "A summary of all the packet error types above (from 1764 missing packets to bad length packets)." 1765 ::= { pwCepPerfCurrentEntry 15 } 1767 pwCepPerfCurrentESs OBJECT-TYPE 1768 SYNTAX PerfCurrentCount 1769 UNITS "seconds" 1770 MAX-ACCESS read-only 1771 STATUS current 1772 DESCRIPTION 1773 "The counter associated with the number of Errored 1774 Seconds encountered." 1775 ::= { pwCepPerfCurrentEntry 16 } 1777 pwCepPerfCurrentSESs OBJECT-TYPE 1778 SYNTAX PerfCurrentCount 1779 UNITS "seconds" 1780 MAX-ACCESS read-only 1781 STATUS current 1782 DESCRIPTION 1783 "The counter associated with the number of 1784 Severely Errored Seconds encountered." 1785 ::= { pwCepPerfCurrentEntry 17 } 1787 pwCepPerfCurrentUASs OBJECT-TYPE 1788 SYNTAX PerfCurrentCount 1789 UNITS "seconds" 1790 MAX-ACCESS read-only 1791 STATUS current 1792 DESCRIPTION 1793 "The counter associated with the number of 1794 Unavailable Seconds encountered." 1795 ::= { pwCepPerfCurrentEntry 18 } 1797 pwCepPerfCurrentFC OBJECT-TYPE 1798 SYNTAX PerfCurrentCount 1799 MAX-ACCESS read-only 1800 STATUS current 1801 DESCRIPTION 1802 "CEP Failure Counts (FC-CEP). The number of CEP failure 1803 events. A failure event begins when the LOPS failure 1804 is declared and ends when the failure is cleared. A 1805 failure event that begins in one period and ends in 1806 another period is counted only in the period in which 1807 it begins." 1808 ::= { pwCepPerfCurrentEntry 19 } 1810 -- End CEP PW Performance Current Interval Table 1812 -- CEP PW Performance 15-Minutes Interval Table. 1814 pwCepPerfIntervalTable OBJECT-TYPE 1815 SYNTAX SEQUENCE OF PwCepPerfIntervalEntry 1816 MAX-ACCESS not-accessible 1817 STATUS current 1818 DESCRIPTION 1819 "This table provides per CEP PW performance information 1820 much like the pwCepPerfCurrentTable above. However, 1821 these counts represent historical 15-minute intervals. 1822 Typically, this table will have a maximum of 96 entries 1823 for a 24 hour period, but is not limited to this. 1824 NOTE: Counter64 objects are used here, Counter32 is 1825 too small for OC-768 CEP PWs." 1827 ::= { pwCepObjects 6 } 1829 pwCepPerfIntervalEntry OBJECT-TYPE 1830 SYNTAX PwCepPerfIntervalEntry 1831 MAX-ACCESS not-accessible 1832 STATUS current 1833 DESCRIPTION 1834 "An entry in this table is created by the agent for 1835 every pwCepPerfCurrentEntry that is 15 minutes old. 1836 The contents of the Current entry are copied to the new 1837 entry here. The Current entry, then resets its counts 1838 to zero for the next current 15-minute interval. 1839 pwCepIndex is found in the pwCepCfg table." 1841 INDEX { pwIndex, pwCepPerfIntervalNumber } 1843 ::= { pwCepPerfIntervalTable 1 } 1845 PwCepPerfIntervalEntry ::= SEQUENCE { 1846 pwCepPerfIntervalNumber Integer32, 1847 pwCepPerfIntervalValidData TruthValue, 1848 pwCepPerfIntervalReset INTEGER, 1849 pwCepPerfIntervalTimeElapsed HCPerfTimeElapsed, 1851 pwCepPerfIntervalDbaInPacketsHC HCPerfIntervalCount, 1852 pwCepPerfIntervalDbaOutPacketsHC HCPerfIntervalCount, 1854 pwCepPerfIntervalInNegPtrAdjust PerfIntervalCount, 1855 pwCepPerfIntervalInPosPtrAdjust PerfIntervalCount, 1856 pwCepPerfIntervalInPtrAdjustSecs PerfIntervalCount, 1857 pwCepPerfIntervalOutNegPtrAdjust PerfIntervalCount, 1858 pwCepPerfIntervalOutPosPtrAdjust PerfIntervalCount, 1859 pwCepPerfIntervalOutPtrAdjustSecs PerfIntervalCount, 1860 pwCepPerfIntervalAbsPtrAdjust Integer32, 1862 pwCepPerfIntervalMissingPkts PerfIntervalCount, 1863 pwCepPerfIntervalPktsOoseq PerfIntervalCount, 1864 pwCepPerfIntervalPktsOoRngDropped PerfIntervalCount, 1865 pwCepPerfIntervalJtrBfrUnderruns PerfIntervalCount, 1866 pwCepPerfIntervalPktsMalformed PerfIntervalCount, 1867 pwCepPerfIntervalSummaryErrors PerfIntervalCount, 1869 pwCepPerfIntervalESs PerfIntervalCount, 1870 pwCepPerfIntervalSESs PerfIntervalCount, 1871 pwCepPerfIntervalUASs PerfIntervalCount, 1872 pwCepPerfIntervalFC PerfIntervalCount 1873 } 1875 pwCepPerfIntervalNumber OBJECT-TYPE 1876 SYNTAX Integer32 (1..96) 1877 MAX-ACCESS not-accessible 1878 STATUS current 1879 DESCRIPTION 1880 "A number (between 1 and 96 to cover a 24 hour 1881 period) which identifies the interval for which the set 1882 of statistics is available. The interval identified by 1 1883 is the most recently completed 15-minute interval and 1884 the interval identified by N is the interval immediately 1885 preceding the one identified by N-1. The minimum range of 1886 N is 1 through 4. The default range is 1 through 32. The 1887 maximum value of N is 1 through 96." 1888 ::= { pwCepPerfIntervalEntry 1 } 1890 pwCepPerfIntervalValidData OBJECT-TYPE 1891 SYNTAX TruthValue 1892 MAX-ACCESS read-only 1893 STATUS current 1894 DESCRIPTION 1895 "This variable indicates if the data for this interval 1896 is valid." 1897 ::= { pwCepPerfIntervalEntry 2 } 1899 pwCepPerfIntervalReset OBJECT-TYPE 1900 SYNTAX INTEGER { 1901 reset (1), 1902 normal(2) 1903 } 1904 MAX-ACCESS read-create 1905 STATUS current 1906 DESCRIPTION 1907 "Used in cases where the user knows that the errors 1908 within this interval should not be counted. Writing 1909 'reset' sets all error counts to zero. The value of 1910 0 was not used here due to issues with 1911 implementations." 1912 ::= { pwCepPerfIntervalEntry 3 } 1914 pwCepPerfIntervalTimeElapsed OBJECT-TYPE 1915 SYNTAX HCPerfTimeElapsed 1916 UNITS "seconds" 1917 MAX-ACCESS read-only 1918 STATUS current 1919 DESCRIPTION 1920 "The duration of a particular interval in seconds, 1921 Adjustments in the system's time-of-day clock may 1922 cause the interval to be greater or less than, the 1923 normal value. Therefore this actual interval value 1924 is provided." 1925 ::= { pwCepPerfIntervalEntry 4 } 1927 pwCepPerfIntervalDbaInPacketsHC OBJECT-TYPE 1928 SYNTAX HCPerfIntervalCount 1929 MAX-ACCESS read-only 1930 STATUS current 1931 DESCRIPTION 1932 "Number of DBA packets received." 1933 ::= { pwCepPerfIntervalEntry 5 } 1935 pwCepPerfIntervalDbaOutPacketsHC OBJECT-TYPE 1936 SYNTAX HCPerfIntervalCount 1937 MAX-ACCESS read-only 1938 STATUS current 1939 DESCRIPTION 1940 "Number of DBA packets sent." 1941 ::= { pwCepPerfIntervalEntry 6 } 1943 -- Pointer adjustment stats 1944 pwCepPerfIntervalInNegPtrAdjust OBJECT-TYPE 1945 SYNTAX PerfIntervalCount 1946 MAX-ACCESS read-only 1947 STATUS current 1948 DESCRIPTION 1949 "Number of negative pointer adjustments sent on the 1950 SONET path based on CEP pointer adjustments received." 1951 ::= { pwCepPerfIntervalEntry 7 } 1953 pwCepPerfIntervalInPosPtrAdjust OBJECT-TYPE 1954 SYNTAX PerfIntervalCount 1955 MAX-ACCESS read-only 1956 STATUS current 1957 DESCRIPTION 1958 "Number of positive pointer adjustments sent on the 1959 SONET path based on CEP pointer adjustments received." 1960 ::= { pwCepPerfIntervalEntry 8 } 1962 pwCepPerfIntervalInPtrAdjustSecs OBJECT-TYPE 1963 SYNTAX PerfIntervalCount 1964 UNITS "seconds" 1965 MAX-ACCESS read-only 1966 STATUS current 1967 DESCRIPTION 1968 "Number of seconds in which a positive or negative 1969 pointer adjustment was sent on the SONET path." 1970 ::= { pwCepPerfIntervalEntry 9 } 1972 pwCepPerfIntervalOutNegPtrAdjust OBJECT-TYPE 1973 SYNTAX PerfIntervalCount 1974 MAX-ACCESS read-only 1975 STATUS current 1976 DESCRIPTION 1977 "Number of negative pointer adjustments seen on the 1978 SONET path and encoded onto sent CEP packets." 1979 ::= { pwCepPerfIntervalEntry 10 } 1981 pwCepPerfIntervalOutPosPtrAdjust OBJECT-TYPE 1982 SYNTAX PerfIntervalCount 1983 MAX-ACCESS read-only 1984 STATUS current 1985 DESCRIPTION 1986 "Number of positive pointer adjustments seen on the 1987 SONET path and encoded onto sent CEP packets." 1988 ::= { pwCepPerfIntervalEntry 11 } 1990 pwCepPerfIntervalOutPtrAdjustSecs OBJECT-TYPE 1991 SYNTAX PerfIntervalCount 1992 UNITS "seconds" 1993 MAX-ACCESS read-only 1994 STATUS current 1995 DESCRIPTION 1996 "Number of seconds in which a positive or negative 1997 pointer adjustment was seen on the SONET path." 1998 ::= { pwCepPerfIntervalEntry 12 } 2000 pwCepPerfIntervalAbsPtrAdjust OBJECT-TYPE 2001 SYNTAX Integer32 2002 MAX-ACCESS read-only 2003 STATUS current 2004 DESCRIPTION 2005 "The relative adjustment drift between inbound 2006 and outbound streams. 2008 It is calculated as absolute value of : 2009 ( InPosPtrAdjust - InNegPtrAdjust) - 2010 (OutPosPtrAdjust - OutNegPtrAdjust) " 2011 ::= { pwCepPerfIntervalEntry 13 } 2013 pwCepPerfIntervalMissingPkts OBJECT-TYPE 2014 SYNTAX PerfIntervalCount 2015 MAX-ACCESS read-only 2016 STATUS current 2017 DESCRIPTION 2018 "Number of missing packets (as detected via CEP header 2019 sequence number gaps)." 2020 ::= { pwCepPerfIntervalEntry 14 } 2022 pwCepPerfIntervalPktsOoseq OBJECT-TYPE 2023 SYNTAX PerfIntervalCount 2024 MAX-ACCESS read-only 2025 STATUS current 2026 DESCRIPTION 2027 "Number of packets detected out of sequence (via CEP 2028 header sequence numbers), but successfully re-ordered. 2029 Note: Some implementations mat not support this 2030 feature (see pwCepCfgPktReorder)." 2031 ::= { pwCepPerfIntervalEntry 15 } 2033 pwCepPerfIntervalPktsOoRngDropped OBJECT-TYPE 2034 SYNTAX PerfIntervalCount 2035 MAX-ACCESS read-only 2036 STATUS current 2037 DESCRIPTION 2038 "Number of packets detected out of range (via CEP 2039 header sequence numbers) and could not be re- 2040 ordered, or could not fit in the jitter buffer." 2041 ::= { pwCepPerfIntervalEntry 16 } 2043 pwCepPerfIntervalJtrBfrUnderruns OBJECT-TYPE 2044 SYNTAX PerfIntervalCount 2045 MAX-ACCESS read-only 2046 STATUS current 2047 DESCRIPTION 2048 "Number of times a packet needed to be played 2049 out and the jitter buffer was empty." 2050 ::= { pwCepPerfIntervalEntry 17 } 2052 pwCepPerfIntervalPktsMalformed OBJECT-TYPE 2053 SYNTAX PerfIntervalCount 2054 MAX-ACCESS read-only 2055 STATUS current 2056 DESCRIPTION 2057 "Number of packets detected with unexpected size, or bad 2058 headers stack." 2059 ::= { pwCepPerfIntervalEntry 18 } 2061 pwCepPerfIntervalSummaryErrors OBJECT-TYPE 2062 SYNTAX PerfIntervalCount 2063 MAX-ACCESS read-only 2064 STATUS current 2065 DESCRIPTION 2066 "A summary of all the packet error types above (from 2067 missing packets to bad length packets)." 2068 ::= { pwCepPerfIntervalEntry 19 } 2070 pwCepPerfIntervalESs OBJECT-TYPE 2071 SYNTAX PerfIntervalCount 2072 UNITS "seconds" 2073 MAX-ACCESS read-only 2074 STATUS current 2075 DESCRIPTION 2076 "The counter associated with the number of Errored 2077 Seconds encountered." 2078 ::= { pwCepPerfIntervalEntry 20 } 2080 pwCepPerfIntervalSESs OBJECT-TYPE 2081 SYNTAX PerfIntervalCount 2082 UNITS "seconds" 2083 MAX-ACCESS read-only 2084 STATUS current 2085 DESCRIPTION 2086 "The counter associated with the number of 2087 Severely Errored Seconds encountered." 2088 ::= { pwCepPerfIntervalEntry 21 } 2090 pwCepPerfIntervalUASs OBJECT-TYPE 2091 SYNTAX PerfIntervalCount 2092 UNITS "seconds" 2093 MAX-ACCESS read-only 2094 STATUS current 2095 DESCRIPTION 2096 "The counter associated with the number of 2097 Unavailable Seconds encountered." 2098 ::= { pwCepPerfIntervalEntry 22 } 2100 pwCepPerfIntervalFC OBJECT-TYPE 2101 SYNTAX PerfIntervalCount 2102 MAX-ACCESS read-only 2103 STATUS current 2104 DESCRIPTION 2105 "CEP Failure Counts (FC-CEP). The number of CEP failure 2106 events. A failure event begins when the LOPS failure 2107 is declared and ends when the failure is cleared. A 2108 failure event that begins in one period and ends in 2109 another period is counted only in the period in which 2110 it begins." 2111 ::= { pwCepPerfIntervalEntry 23 } 2113 -- End CEP PW Performance 15 Minutes Interval Table 2115 -- CEP PW Day Performance Table 2117 pwCepPerf1DayIntervalTable OBJECT-TYPE 2118 SYNTAX SEQUENCE OF PwCepPerf1DayIntervalEntry 2119 MAX-ACCESS not-accessible 2120 STATUS current 2121 DESCRIPTION 2122 "This table provides per CEP PW performance information 2123 the current day measurement and the previous days interval. 2125 On the extreme cases where one of the error counters has 2126 overflowed during the one day interval, the error counter 2127 MUST NOT wrap around and MUST return the maximum value." 2128 ::= { pwCepObjects 7 } 2130 pwCepPerf1DayIntervalEntry OBJECT-TYPE 2131 SYNTAX PwCepPerf1DayIntervalEntry 2132 MAX-ACCESS not-accessible 2133 STATUS current 2134 DESCRIPTION 2135 "An entry is created in this table by the agent for 2136 every entry in the pwCepTable and for each day 2137 interval up to the number of supported historical 2138 intervals." 2140 INDEX { pwIndex, pwCepPerf1DayIntervalNumber } 2142 ::= { pwCepPerf1DayIntervalTable 1 } 2144 PwCepPerf1DayIntervalEntry ::= SEQUENCE { 2146 pwCepPerf1DayIntervalNumber Unsigned32, 2147 pwCepPerf1DayIntervalValidData TruthValue, 2148 pwCepPerf1DayIntervalMoniSecs HCPerfTimeElapsed, 2150 pwCepPerf1DayIntervalDbaInPacketsHC Counter64, 2151 pwCepPerf1DayIntervalDbaOutPacketsHC Counter64, 2153 pwCepPerf1DayIntervalInNegPtrAdjust Counter32, 2154 pwCepPerf1DayIntervalInPosPtrAdjust Counter32, 2155 pwCepPerf1DayIntervalInPtrAdjustSecs Counter32, 2156 pwCepPerf1DayIntervalOutNegPtrAdjust Counter32, 2157 pwCepPerf1DayIntervalOutPosPtrAdjust Counter32, 2158 pwCepPerf1DayIntervalOutPtrAdjustSecs Counter32, 2159 pwCepPerf1DayIntervalAbsPtrAdjust Integer32, 2161 pwCepPerf1DayIntervalMissingPkts Counter32, 2162 pwCepPerf1DayIntervalPktsOoseq Counter32, 2163 pwCepPerf1DayIntervalPktsOoRngDropped Counter32, 2164 pwCepPerf1DayIntervalJtrBfrUnderruns Counter32, 2165 pwCepPerf1DayIntervalPktsMalformed Counter32, 2166 pwCepPerf1DayIntervalSummaryErrors Counter32, 2168 pwCepPerf1DayIntervalESs Counter32, 2169 pwCepPerf1DayIntervalSESs Counter32, 2170 pwCepPerf1DayIntervalUASs Counter32, 2171 pwCepPerf1DayIntervalFC Counter32 2172 } 2174 pwCepPerf1DayIntervalNumber OBJECT-TYPE 2175 SYNTAX Unsigned32(1..31) 2176 MAX-ACCESS not-accessible 2177 STATUS current 2178 DESCRIPTION 2179 "History Data Interval number. Interval 1 is the current day 2180 measurement period, interval 2 is the most recent previous 2181 day; interval 30 is 31 days ago." 2182 ::= { pwCepPerf1DayIntervalEntry 1 } 2184 pwCepPerf1DayIntervalValidData OBJECT-TYPE 2185 SYNTAX TruthValue 2186 MAX-ACCESS read-only 2187 STATUS current 2188 DESCRIPTION 2189 "This variable indicates if the data for this interval 2190 is valid." 2191 ::= { pwCepPerf1DayIntervalEntry 2 } 2193 pwCepPerf1DayIntervalMoniSecs OBJECT-TYPE 2194 SYNTAX HCPerfTimeElapsed 2195 UNITS "seconds" 2196 MAX-ACCESS read-only 2197 STATUS current 2198 DESCRIPTION 2199 "The amount of time in the 1-day interval over which the 2200 performance monitoring information is actually counted. 2201 This value will be the same as the interval duration except 2202 in a situation where performance monitoring data could not 2203 be collected for any reason or agent clock adjustments." 2204 ::= { pwCepPerf1DayIntervalEntry 3 } 2206 pwCepPerf1DayIntervalDbaInPacketsHC OBJECT-TYPE 2207 SYNTAX Counter64 2208 MAX-ACCESS read-only 2209 STATUS current 2210 DESCRIPTION 2211 "Number of DBA packets received." 2212 ::= { pwCepPerf1DayIntervalEntry 4 } 2214 pwCepPerf1DayIntervalDbaOutPacketsHC OBJECT-TYPE 2215 SYNTAX Counter64 2216 MAX-ACCESS read-only 2217 STATUS current 2218 DESCRIPTION 2219 "Number of DBA packets sent." 2220 ::= { pwCepPerf1DayIntervalEntry 5 } 2222 -- Pointer adjustment stats 2223 pwCepPerf1DayIntervalInNegPtrAdjust OBJECT-TYPE 2224 SYNTAX Counter32 2225 MAX-ACCESS read-only 2226 STATUS current 2227 DESCRIPTION 2228 "Number of negative pointer adjustments sent on the 2229 SONET path based on CEP pointer adjustments received." 2230 ::= { pwCepPerf1DayIntervalEntry 6 } 2232 pwCepPerf1DayIntervalInPosPtrAdjust OBJECT-TYPE 2233 SYNTAX Counter32 2234 MAX-ACCESS read-only 2235 STATUS current 2236 DESCRIPTION 2237 "Number of positive pointer adjustments sent on the 2238 SONET path based on CEP pointer adjustments received." 2239 ::= { pwCepPerf1DayIntervalEntry 7 } 2241 pwCepPerf1DayIntervalInPtrAdjustSecs OBJECT-TYPE 2242 SYNTAX Counter32 2243 UNITS "seconds" 2244 MAX-ACCESS read-only 2245 STATUS current 2246 DESCRIPTION 2247 "Number of seconds in which a positive or negative pointer 2248 adjustment was sent on the SONET path." 2249 ::= { pwCepPerf1DayIntervalEntry 8 } 2251 pwCepPerf1DayIntervalOutNegPtrAdjust OBJECT-TYPE 2252 SYNTAX Counter32 2253 MAX-ACCESS read-only 2254 STATUS current 2255 DESCRIPTION 2256 "Number of negative pointer adjustments seen on the 2257 SONET path and encoded onto sent CEP packets." 2258 ::= { pwCepPerf1DayIntervalEntry 9 } 2260 pwCepPerf1DayIntervalOutPosPtrAdjust OBJECT-TYPE 2261 SYNTAX Counter32 2262 MAX-ACCESS read-only 2263 STATUS current 2264 DESCRIPTION 2265 "Number of positive pointer adjustments seen on the 2266 SONET path and encoded onto sent CEP packets." 2267 ::= { pwCepPerf1DayIntervalEntry 10 } 2269 pwCepPerf1DayIntervalOutPtrAdjustSecs OBJECT-TYPE 2270 SYNTAX Counter32 2271 UNITS "seconds" 2272 MAX-ACCESS read-only 2273 STATUS current 2274 DESCRIPTION 2275 "Number of seconds in which a positive or negative pointer 2276 adjustment was seen on the SONET path." 2277 ::= { pwCepPerf1DayIntervalEntry 11 } 2279 pwCepPerf1DayIntervalAbsPtrAdjust OBJECT-TYPE 2280 SYNTAX Integer32 2281 MAX-ACCESS read-only 2282 STATUS current 2283 DESCRIPTION 2284 "The relative adjustment of drift between inbound 2285 and outbound streams. It is calculated as absolute 2286 value of : 2287 ( InPosPtrAdjust - InNegPtrAdjust) - 2288 (OutPosPtrAdjust - OutNegPtrAdjust) " 2289 ::= { pwCepPerf1DayIntervalEntry 12 } 2291 pwCepPerf1DayIntervalMissingPkts OBJECT-TYPE 2292 SYNTAX Counter32 2293 MAX-ACCESS read-only 2294 STATUS current 2295 DESCRIPTION 2296 "Number of missing packets (as detected via CEP header 2297 sequence number gaps)." 2298 ::= { pwCepPerf1DayIntervalEntry 13 } 2300 pwCepPerf1DayIntervalPktsOoseq OBJECT-TYPE 2301 SYNTAX Counter32 2302 MAX-ACCESS read-only 2303 STATUS current 2304 DESCRIPTION 2305 "Number of packets detected out of sequence (via CEP 2306 header sequence numbers), but successfully re-ordered. 2307 Note: Some implementations may not support this feature 2308 (see pwCepCfgPktReorder)." 2309 ::= { pwCepPerf1DayIntervalEntry 14 } 2311 pwCepPerf1DayIntervalPktsOoRngDropped OBJECT-TYPE 2312 SYNTAX Counter32 2313 MAX-ACCESS read-only 2314 STATUS current 2315 DESCRIPTION 2316 "Number of packets detected out of range (via CEP header 2317 sequence numbers) and could not be re-ordered, or could not 2318 fit in the jitter buffer." 2319 ::= { pwCepPerf1DayIntervalEntry 15 } 2321 pwCepPerf1DayIntervalJtrBfrUnderruns OBJECT-TYPE 2322 SYNTAX Counter32 2323 MAX-ACCESS read-only 2324 STATUS current 2325 DESCRIPTION 2326 "Number of times a packet needed to be played out and the 2327 jitter buffer was empty." 2328 ::= { pwCepPerf1DayIntervalEntry 16 } 2330 pwCepPerf1DayIntervalPktsMalformed OBJECT-TYPE 2331 SYNTAX Counter32 2332 MAX-ACCESS read-only 2333 STATUS current 2334 DESCRIPTION 2335 "Number of packets detected with unexpected size, or bad 2336 headers stack." 2337 ::= { pwCepPerf1DayIntervalEntry 17 } 2339 pwCepPerf1DayIntervalSummaryErrors OBJECT-TYPE 2340 SYNTAX Counter32 2341 MAX-ACCESS read-only 2342 STATUS current 2343 DESCRIPTION 2344 "A summary of all the packet error types above (from 2345 missing packets to bad length packets)." 2346 ::= { pwCepPerf1DayIntervalEntry 18 } 2348 pwCepPerf1DayIntervalESs OBJECT-TYPE 2349 SYNTAX Counter32 2350 UNITS "seconds" 2351 MAX-ACCESS read-only 2352 STATUS current 2353 DESCRIPTION 2354 "The counter associated with the number of Errored 2355 Seconds encountered." 2356 ::= { pwCepPerf1DayIntervalEntry 19 } 2358 pwCepPerf1DayIntervalSESs OBJECT-TYPE 2359 SYNTAX Counter32 2360 UNITS "seconds" 2361 MAX-ACCESS read-only 2362 STATUS current 2363 DESCRIPTION 2364 "The counter associated with the number of Severely 2365 Errored Seconds. See pwCepCfgMissingPktsToSes." 2366 ::= { pwCepPerf1DayIntervalEntry 20 } 2368 pwCepPerf1DayIntervalUASs OBJECT-TYPE 2369 SYNTAX Counter32 2370 UNITS "seconds" 2371 MAX-ACCESS read-only 2372 STATUS current 2373 DESCRIPTION 2374 "The counter associated with the number of 2375 unavailable seconds. See pwCepCfgSesToUAS. 2377 NOTE: When first entering the UAS state, the number 2378 of SesToUas is added to this object, then as each 2379 additional UAS occurs, this object increments by one. 2381 NOTE: Similar to RFC 3592, if the agent chooses to update 2382 the various performance statistics in real time then it must 2383 be prepared to retroactively reduce the ES, SES, counts (by 2384 the value of pwCepCfgSesToUas) and increase the UAS 2385 count (by that same value) when it determines that UAS 2386 state has been entered." 2387 ::= { pwCepPerf1DayIntervalEntry 21 } 2389 pwCepPerf1DayIntervalFC OBJECT-TYPE 2390 SYNTAX Counter32 2391 MAX-ACCESS read-only 2392 STATUS current 2393 DESCRIPTION 2394 "CEP Failure Counts (FC-CEP). The number of CEP failure 2395 events. A failure event begins when the LOPS failure 2396 is declared and ends when the failure is cleared." 2397 ::= { pwCepPerf1DayIntervalEntry 22 } 2399 -- End of PW CEP 1 Day Interval Performance table 2401 -- Conformance Information 2403 pwCepGroups OBJECT IDENTIFIER ::= { pwCepConformance 1 } 2405 pwCepCompliances OBJECT IDENTIFIER ::= { pwCepConformance 2 } 2407 -- Compliance statement for full compliant implementations 2409 pwCepModuleFullCompliance MODULE-COMPLIANCE 2410 STATUS current 2411 DESCRIPTION 2412 "The compliance statement for agent that support full 2413 CEP PW configuration through this MIB module." 2415 MODULE -- this module 2416 MANDATORY-GROUPS { pwCepGroup, 2417 pwCepCfgGroup, 2418 pwCepPerfCurrentGroup, 2419 pwCepPerfIntervalGroup, 2420 pwCepPerf1DayIntervalGroup 2421 } 2423 GROUP pwCepFractionalGroup 2424 DESCRIPTION "This group is only mandatory for implementations 2425 that support fractional SPE. 2426 " 2428 GROUP pwCepFractionalSts1Vc3Group 2429 DESCRIPTION "This group is only mandatory for implementations 2430 that support the fractional STS-1/VC-3. 2432 " 2434 GROUP pwCepFractionalVc4Group 2435 DESCRIPTION "This group is only mandatory for implementations 2436 that support the Fractional VC-4. 2437 " 2439 GROUP pwCepSignalingGroup 2440 DESCRIPTION "This group is only mandatory for implementations 2441 that support the CEP PW signaling. 2442 " 2444 OBJECT pwCepType 2445 SYNTAX INTEGER { spe(1) } 2446 MIN-ACCESS read-only 2447 DESCRIPTION "The support of the value vt(2) or fracSpe(3) is 2448 optional. If either of these options are supported, 2449 read-write access is not required." 2451 OBJECT pwCepSonetPayloadLength 2452 MIN-ACCESS read-only 2453 DESCRIPTION "Write access is not required for implementations 2454 that support only the default values (which are 2455 based on the pwCepType)." 2457 OBJECT pwCepCfgMinPktLength 2458 MIN-ACCESS read-only 2459 DESCRIPTION "Write access is not required for implementations 2460 that support only a single pre-defined value." 2462 OBJECT pwCepCfgEnableDBA 2463 MIN-ACCESS read-only 2464 DESCRIPTION "Write access is not required for implementations 2465 that support only a single pre-defined value." 2467 OBJECT pwCepCfgRtpHdrSuppress 2468 MIN-ACCESS read-only 2469 DESCRIPTION "Write access is not required for implementations 2470 that do not support RTP header for CEP connections." 2472 OBJECT pwCepCfgConsecPktsInsync 2473 MIN-ACCESS read-only 2474 DESCRIPTION "Write access is not required for implementations 2475 that support only a single pre-defined value." 2477 OBJECT pwCepCfgConsecMissingOutSync 2478 MIN-ACCESS read-only 2479 DESCRIPTION "Write access is not required for implementations 2480 that support only a single pre-defined value." 2482 OBJECT pwCepCfgPktErrorPlayOutValue 2483 MIN-ACCESS read-only 2484 DESCRIPTION "Write access is not required for implementations 2485 that support only a single pre-defined value." 2487 OBJECT pwCepCfgMissingPktsToSes 2488 MIN-ACCESS read-only 2489 DESCRIPTION "Write access is not required for implementations 2490 that support only a single pre-defined value." 2492 OBJECT pwCepCfgSesToUas 2493 MIN-ACCESS read-only 2494 DESCRIPTION "Write access is not required for implementations 2495 that support only a single pre-defined value." 2497 OBJECT pwCepCfgSecsToExitUas 2498 MIN-ACCESS read-only 2499 DESCRIPTION "Write access is not required for implementations 2500 that support only a single pre-defined value." 2502 OBJECT pwCepCfgName 2503 MIN-ACCESS read-only 2504 DESCRIPTION "Write access is not required." 2506 OBJECT pwCepCfgRowStatus 2507 SYNTAX RowStatus { active(1), notInService(2), 2508 notReady(3) } 2509 WRITE-SYNTAX RowStatus { active(1), notInService(2), 2510 createAndGo(4), destroy(6) 2511 } 2513 DESCRIPTION "Support for createAndWait is not required." 2515 OBJECT pwCepFracMode 2516 MIN-ACCESS read-only 2517 DESCRIPTION "Write access is not required for implementations 2518 that support only a single pre-defined value." 2520 OBJECT pwCepFracAsync 2521 SYNTAX PwCepFracAsyncMap { other(1) } 2522 MIN-ACCESS read-only 2523 DESCRIPTION "Support for ds3(2) or e3(3) and read-write access 2524 is not required if the implementation do not support 2525 these options." 2527 OBJECT pwCepFracVtgMap 2528 MIN-ACCESS read-only 2529 DESCRIPTION "Write access is not required for implementations 2530 that support only a single pre-defined value." 2532 OBJECT pwCepFracEbm 2533 MIN-ACCESS read-only 2534 DESCRIPTION "Write access is not required for implementations 2535 where the EBM is derived from configuration in 2536 other MIB modules." 2538 OBJECT pwCepFracSdhVc4Mode 2539 MIN-ACCESS read-only 2540 DESCRIPTION "Write access is not required for implementations 2541 that support only a single pre-defined value." 2543 OBJECT pwCepFracSdhVc4Tu3Map1 2544 MIN-ACCESS read-only 2545 DESCRIPTION "Write access is not required for implementations 2546 that support only a single pre-defined value." 2548 OBJECT pwCepFracSdhVc4Tu3Map2 2549 MIN-ACCESS read-only 2550 DESCRIPTION "Write access is not required for implementations 2551 that support only a single pre-defined value." 2553 OBJECT pwCepFracSdhVc4Tu3Map3 2554 MIN-ACCESS read-only 2555 DESCRIPTION "Write access is not required for implementations 2556 that support only a single pre-defined value." 2558 OBJECT pwCepFracSdhVc4Tug2Map1 2559 MIN-ACCESS read-only 2560 DESCRIPTION "Write access is not required for implementations 2561 that support only a single pre-defined value." 2563 OBJECT pwCepFracSdhVc4Tug2Map2 2564 MIN-ACCESS read-only 2565 DESCRIPTION "Write access is not required for implementations 2566 that support only a single pre-defined value." 2568 OBJECT pwCepFracSdhVc4Tug2Map3 2569 MIN-ACCESS read-only 2570 DESCRIPTION "Write access is not required for implementations 2571 that support only a single pre-defined value." 2573 OBJECT pwCepFracSdhVc4Ebm1 2574 MIN-ACCESS read-only 2575 DESCRIPTION "Write access is not required for implementations 2576 where the EBM is derived from configuration in 2577 other MIB modules." 2579 OBJECT pwCepFracSdhVc4Ebm2 2580 MIN-ACCESS read-only 2581 DESCRIPTION "Write access is not required for implementations 2582 where the EBM is derived from configuration in 2583 other MIB modules." 2585 OBJECT pwCepFracSdhVc4Ebm3 2586 MIN-ACCESS read-only 2587 DESCRIPTION "Write access is not required for implementations 2588 where the EBM is derived from configuration in 2589 other MIB modules." 2591 OBJECT pwCepFracRowStatus 2592 SYNTAX RowStatus { active(1), notInService(2), 2593 notReady(3) } 2594 WRITE-SYNTAX RowStatus { active(1), notInService(2), 2595 createAndGo(4), destroy(6) 2596 } 2597 DESCRIPTION "Support for createAndWait is not required." 2599 ::= { pwCepCompliances 1 } 2601 -- Compliance requirement for read only compliant implementations. 2603 pwCepModuleReadOnlyCompliance MODULE-COMPLIANCE 2604 STATUS current 2605 DESCRIPTION 2606 "The compliance statement for agents that provide read 2607 only support for PW CEP MIB Module. Such devices can 2608 then be monitored but cannot be configured using this 2609 MIB module." 2611 MODULE -- this module 2612 MANDATORY-GROUPS { pwCepGroup, 2613 pwCepCfgGroup, 2614 pwCepPerfCurrentGroup, 2615 pwCepPerfIntervalGroup, 2616 pwCepPerf1DayIntervalGroup 2617 } 2619 GROUP pwCepFractionalGroup 2620 DESCRIPTION "This group is only mandatory for implementations 2621 that support fractional SPE. 2622 " 2624 GROUP pwCepFractionalSts1Vc3Group 2625 DESCRIPTION "This group is only mandatory for implementations 2626 that support the fractional STS-1/VC-3. 2628 " 2630 GROUP pwCepFractionalVc4Group 2631 DESCRIPTION "This group is only mandatory for implementations 2632 that support the Fractional VC-4. 2633 " 2635 GROUP pwCepSignalingGroup 2636 DESCRIPTION "This group is only mandatory for implementations 2637 that support the CEP PW signaling. 2638 " 2640 OBJECT pwCepType 2641 MIN-ACCESS read-only 2642 DESCRIPTION "Write access is not required." 2644 OBJECT pwCepSonetIfIndex 2645 MIN-ACCESS read-only 2646 DESCRIPTION "Write access is not required." 2648 OBJECT pwCepCfgIndex 2649 MIN-ACCESS read-only 2650 DESCRIPTION "Write access is not required." 2652 OBJECT pwCepSonetPayloadLength 2653 MIN-ACCESS read-only 2654 DESCRIPTION "Write access is not required." 2656 OBJECT pwCepCfgMinPktLength 2657 MIN-ACCESS read-only 2658 DESCRIPTION "Write access is not required." 2660 OBJECT pwCepCfgEnableDBA 2661 MIN-ACCESS read-only 2662 DESCRIPTION "Write access is not required." 2664 OBJECT pwCepCfgRtpHdrSuppress 2665 MIN-ACCESS read-only 2666 DESCRIPTION "Write access is not required." 2668 OBJECT pwCepCfgJtrBfrDepth 2669 MIN-ACCESS read-only 2670 DESCRIPTION "Write access is not required." 2672 OBJECT pwCepCfgConsecPktsInsync 2673 MIN-ACCESS read-only 2674 DESCRIPTION "Write access is not required." 2676 OBJECT pwCepCfgConsecMissingOutSync 2677 MIN-ACCESS read-only 2678 DESCRIPTION "Write access is not required." 2680 OBJECT pwCepCfgPktErrorPlayOutValue 2681 MIN-ACCESS read-only 2682 DESCRIPTION "Write access is not required." 2684 OBJECT pwCepCfgMissingPktsToSes 2685 MIN-ACCESS read-only 2686 DESCRIPTION "Write access is not required." 2688 OBJECT pwCepCfgSesToUas 2689 MIN-ACCESS read-only 2690 DESCRIPTION "Write access is not required." 2692 OBJECT pwCepCfgSecsToExitUas 2693 MIN-ACCESS read-only 2694 DESCRIPTION "Write access is not required." 2696 OBJECT pwCepCfgRowStatus 2697 MIN-ACCESS read-only 2698 DESCRIPTION "Write access is not required.." 2700 OBJECT pwCepCfgStorageType 2701 MIN-ACCESS read-only 2702 DESCRIPTION "Write access is not required.." 2704 OBJECT pwCepFracMode 2705 MIN-ACCESS read-only 2706 DESCRIPTION "Write access is not required." 2708 OBJECT pwCepFracAsync 2709 MIN-ACCESS read-only 2710 DESCRIPTION "Write access is not required." 2712 OBJECT pwCepFracVtgMap 2713 MIN-ACCESS read-only 2714 DESCRIPTION "Write access is not required." 2716 OBJECT pwCepFracEbm 2717 MIN-ACCESS read-only 2718 DESCRIPTION "Write access is not required." 2720 OBJECT pwCepFracSdhVc4Mode 2721 MIN-ACCESS read-only 2722 DESCRIPTION "Write access is not required." 2724 OBJECT pwCepFracSdhVc4Tu3Map1 2725 MIN-ACCESS read-only 2726 DESCRIPTION "Write access is not required." 2728 OBJECT pwCepFracSdhVc4Tu3Map2 2729 MIN-ACCESS read-only 2730 DESCRIPTION "Write access is not required." 2732 OBJECT pwCepFracSdhVc4Tu3Map3 2733 MIN-ACCESS read-only 2734 DESCRIPTION "Write access is not required." 2736 OBJECT pwCepFracSdhVc4Tug2Map1 2737 MIN-ACCESS read-only 2738 DESCRIPTION "Write access is not required." 2740 OBJECT pwCepFracSdhVc4Tug2Map2 2741 MIN-ACCESS read-only 2742 DESCRIPTION "Write access is not required." 2744 OBJECT pwCepFracSdhVc4Tug2Map3 2745 MIN-ACCESS read-only 2746 DESCRIPTION "Write access is not required." 2748 OBJECT pwCepFracSdhVc4Ebm1 2749 MIN-ACCESS read-only 2750 DESCRIPTION "Write access is not required." 2752 OBJECT pwCepFracSdhVc4Ebm2 2753 MIN-ACCESS read-only 2754 DESCRIPTION "Write access is not required." 2756 OBJECT pwCepFracSdhVc4Ebm3 2757 MIN-ACCESS read-only 2758 DESCRIPTION "Write access is not required." 2760 OBJECT pwCepFracRowStatus 2761 MIN-ACCESS read-only 2762 DESCRIPTION "Write access is not required." 2764 OBJECT pwCepFracStorageType 2765 MIN-ACCESS read-only 2766 DESCRIPTION "Write access is not required." 2768 ::= { pwCepCompliances 2 } 2770 -- Units of conformance. 2772 pwCepGroup OBJECT-GROUP 2773 OBJECTS { 2774 pwCepType, 2775 pwCepSonetIfIndex, 2776 pwCepSonetConfigErrorOrStatus, 2777 pwCepCfgIndex, 2778 pwCepTimeElapsed, 2779 pwCepValidIntervals, 2780 pwCepIndications, 2781 pwCepLastEsTimeStamp 2782 } 2783 STATUS current 2784 DESCRIPTION 2785 "Collection of objects for basic CEP PW config and 2786 status." 2787 ::= { pwCepGroups 1 } 2789 pwCepSignalingGroup OBJECT-GROUP 2790 OBJECTS { 2791 pwCepPeerCepOption 2792 } 2793 STATUS current 2794 DESCRIPTION 2795 "Collection of objects required if the network element 2796 support CEP connections signaling." 2797 ::= { pwCepGroups 2 } 2799 pwCepCfgGroup OBJECT-GROUP 2800 OBJECTS { 2801 pwCepCfgIndexNext, 2803 pwCepSonetPayloadLength, 2804 pwCepCfgMinPktLength, 2805 pwCepCfgPktReorder, 2806 pwCepCfgEnableDBA, 2808 pwCepCfgRtpHdrSuppress, 2810 pwCepCfgJtrBfrDepth, 2812 pwCepCfgConsecPktsInsync, 2813 pwCepCfgConsecMissingOutSync, 2815 pwCepCfgPktErrorPlayOutValue, 2817 pwCepCfgMissingPktsToSes, 2818 pwCepCfgSesToUas, 2819 pwCepCfgSecsToExitUas, 2821 pwCepCfgName, 2823 pwCepCfgRowStatus, 2824 pwCepCfgStorageType 2825 } 2826 STATUS current 2827 DESCRIPTION 2828 "Collection of detailed objects needed to 2829 configure CEP PWs." 2830 ::= { pwCepGroups 3 } 2832 pwCepPerfCurrentGroup OBJECT-GROUP 2833 OBJECTS { 2834 pwCepPerfCurrentDbaInPacketsHC, 2835 pwCepPerfCurrentDbaOutPacketsHC, 2837 pwCepPerfCurrentInNegPtrAdjust, 2838 pwCepPerfCurrentInPosPtrAdjust, 2839 pwCepPerfCurrentInPtrAdjustSecs, 2840 pwCepPerfCurrentOutNegPtrAdjust, 2841 pwCepPerfCurrentOutPosPtrAdjust, 2842 pwCepPerfCurrentOutPtrAdjustSecs, 2843 pwCepPerfCurrentAbsPtrAdjust, 2844 pwCepPerfCurrentMissingPkts, 2845 pwCepPerfCurrentPktsOoseq, 2846 pwCepPerfCurrentPktsOoRngDropped, 2847 pwCepPerfCurrentJtrBfrUnderruns, 2848 pwCepPerfCurrentPktsMalformed, 2849 pwCepPerfCurrentSummaryErrors, 2851 pwCepPerfCurrentESs, 2852 pwCepPerfCurrentSESs, 2853 pwCepPerfCurrentUASs, 2854 pwCepPerfCurrentFC 2855 } 2856 STATUS current 2857 DESCRIPTION 2858 "Collection of statistics objects for CEP PWs." 2859 ::= { pwCepGroups 4 } 2861 pwCepPerfIntervalGroup OBJECT-GROUP 2862 OBJECTS { 2863 pwCepPerfIntervalValidData, 2864 pwCepPerfIntervalReset, 2865 pwCepPerfIntervalTimeElapsed, 2867 pwCepPerfIntervalDbaInPacketsHC, 2868 pwCepPerfIntervalDbaOutPacketsHC, 2870 pwCepPerfIntervalInNegPtrAdjust, 2871 pwCepPerfIntervalInPosPtrAdjust, 2872 pwCepPerfIntervalInPtrAdjustSecs, 2873 pwCepPerfIntervalOutNegPtrAdjust, 2874 pwCepPerfIntervalOutPosPtrAdjust, 2875 pwCepPerfIntervalOutPtrAdjustSecs, 2876 pwCepPerfIntervalAbsPtrAdjust, 2878 pwCepPerfIntervalMissingPkts, 2879 pwCepPerfIntervalPktsOoseq, 2880 pwCepPerfIntervalPktsOoRngDropped, 2881 pwCepPerfIntervalJtrBfrUnderruns, 2882 pwCepPerfIntervalPktsMalformed, 2883 pwCepPerfIntervalSummaryErrors, 2885 pwCepPerfIntervalESs, 2886 pwCepPerfIntervalSESs, 2887 pwCepPerfIntervalUASs, 2888 pwCepPerfIntervalFC 2890 } 2891 STATUS current 2892 DESCRIPTION 2893 "Collection of statistics objects for CEP PWs." 2894 ::= { pwCepGroups 5 } 2896 pwCepPerf1DayIntervalGroup OBJECT-GROUP 2897 OBJECTS { 2898 pwCepPerf1DayIntervalValidData, 2899 pwCepPerf1DayIntervalMoniSecs, 2901 pwCepPerf1DayIntervalDbaInPacketsHC, 2902 pwCepPerf1DayIntervalDbaOutPacketsHC, 2904 pwCepPerf1DayIntervalInNegPtrAdjust, 2905 pwCepPerf1DayIntervalInPosPtrAdjust, 2906 pwCepPerf1DayIntervalInPtrAdjustSecs, 2907 pwCepPerf1DayIntervalOutNegPtrAdjust, 2908 pwCepPerf1DayIntervalOutPosPtrAdjust, 2909 pwCepPerf1DayIntervalOutPtrAdjustSecs, 2910 pwCepPerf1DayIntervalAbsPtrAdjust, 2912 pwCepPerf1DayIntervalMissingPkts, 2913 pwCepPerf1DayIntervalPktsOoseq, 2914 pwCepPerf1DayIntervalPktsOoRngDropped, 2915 pwCepPerf1DayIntervalJtrBfrUnderruns, 2916 pwCepPerf1DayIntervalPktsMalformed, 2917 pwCepPerf1DayIntervalSummaryErrors, 2919 pwCepPerf1DayIntervalESs, 2920 pwCepPerf1DayIntervalSESs, 2921 pwCepPerf1DayIntervalUASs, 2922 pwCepPerf1DayIntervalFC 2923 } 2924 STATUS current 2925 DESCRIPTION 2926 "Collection of statistics objects for CEP PWs." 2927 ::= { pwCepGroups 6 } 2929 pwCepFractionalGroup OBJECT-GROUP 2930 OBJECTS { 2931 pwCepFracRowStatus, 2932 pwCepFracStorageType 2933 } 2934 STATUS current 2935 DESCRIPTION 2936 "Collection of fractional SPE objects. These objects 2937 are optional and should be supported only if 2938 fractional SPE is supported within the network 2939 element. " 2940 ::= { pwCepGroups 7 } 2942 pwCepFractionalSts1Vc3Group OBJECT-GROUP 2943 OBJECTS { 2944 pwCepFracMode, 2945 pwCepFracConfigError, 2946 pwCepFracAsync, 2947 pwCepFracVtgMap, 2948 pwCepFracEbm, 2949 pwCepFracPeerEbm 2950 } 2951 STATUS current 2952 DESCRIPTION 2953 "Collection of fractional STS-1/VC3 objects. These objects 2954 are optional and should be supported only if 2955 fractional STS-1/VC3 is supported within the network 2956 element. " 2957 ::= { pwCepGroups 8 } 2959 pwCepFractionalVc4Group OBJECT-GROUP 2960 OBJECTS { 2961 pwCepFracSdhVc4Mode, 2962 pwCepFracSdhVc4Tu3Map1, 2963 pwCepFracSdhVc4Tu3Map2, 2964 pwCepFracSdhVc4Tu3Map3, 2965 pwCepFracSdhVc4Tug2Map1, 2966 pwCepFracSdhVc4Tug2Map2, 2967 pwCepFracSdhVc4Tug2Map3, 2968 pwCepFracSdhVc4Ebm1, 2969 pwCepFracSdhVc4Ebm2, 2970 pwCepFracSdhVc4Ebm3, 2971 pwCepFracSdhVc4PeerEbm1, 2972 pwCepFracSdhVc4PeerEbm2, 2973 pwCepFracSdhVc4PeerEbm3 2974 } 2975 STATUS current 2976 DESCRIPTION 2977 "Collection of fractional VC4 objects. These objects 2978 are optional and should be supported only if 2979 fractional VC4 is supported within the network 2980 element. " 2981 ::= { pwCepGroups 9 } 2983 END 2985 8. Security Considerations 2987 It is clear that this MIB module is potentially useful for monitoring 2988 CEP PWs. This MIB can also be used for configuration of certain 2989 objects and anything that can be configured can be incorrectly 2990 configured, with potentially disastrous results. 2992 There are number of management objects defined in this MIB module 2993 with a MAX-ACCESS clause of read-write and/or read-create. Such 2994 objects may be considered sensitive or vulnerable in some network 2995 environments. The support for SET operations in a non-secure 2996 environment without proper protection can have a negative effect on 2997 network operations. These are the tables and objects and their 2998 sensitivity/vulnerability: 3000 o the pwCepTable, pwCepCfgTable and pwCepFracTable contains objects 3001 to CEP PW parameters on a Provider Edge (PE) device. Unauthorized 3002 access to objects in these tables could result in disruption of 3003 traffic on the network. The use of stronger mechanisms such as 3004 SNMPv3 security should be considered where possible. 3005 Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent 3006 which implements this MIB module. Administrators should consider 3007 whether read access to these objects should be allowed, since read 3008 access may be undesirable under certain circumstances. 3010 Some of the readable objects in this MIB module (i.e., objects with a 3011 MAX-ACCESS other than not-accessible), may be considered sensitive or 3012 vulnerable in some network environments. It is thus important to 3013 control even GET and/or NOTIFY access to these objects and possibly 3014 to even encrypt the values of these objects when sending them over 3015 the network via SNMP. These are the tables and objects and their 3016 sensitivity/vulnerability: 3018 o the pwCepTable, pwCepPerfCurrentTable, pwCepPerfIntervalTable and 3019 pwCepPerf1DayTable collectively show the CEP pseudowire 3020 connectivity topology and its performance characteristics. If an 3021 Administrator does not want to reveal this information, then these 3022 tables should be considered sensitive/vulnerable. 3024 SNMP versions prior to SNMPv3 did not include adequate security. 3025 Even if the network itself is secure (for example by using IPsec), 3026 even then, there is no control as to who on the secure network is 3027 allowed to access and GET/SET (read/change/create/delete) the objects 3028 in this MIB module. 3030 It is RECOMMENDED that implementers consider the security features as 3031 provided by the SNMPv3 framework (see [RFC3410], section 8), 3032 including full support for the SNMPv3 cryptographic mechanisms (for 3033 authentication and privacy). 3035 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3036 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3037 enable cryptographic security. It is then a customer/operator 3038 responsibility to ensure that the SNMP entity giving access to an 3039 instance of this MIB module, is properly configured to give access to 3040 the objects only to those principals (users) that have legitimate 3041 rights to indeed GET or SET (change/create/delete) them. 3043 9. IANA Considerations 3045 The MIB module in this document uses the following IANA-assigned 3046 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 3048 Descriptor OBJECT IDENTIFIER value 3049 ---------- ----------------------- 3051 pwCepStdMIB { mib-2 XXXX } 3053 Editor's Note (to be removed prior to publication): The IANA is 3054 requested to assign a value for "XXXX" under the 'mib-2' subtree and 3055 to record the assignment in the SMI Numbers registry. When the 3056 assignment has been made, the RFC Editor is asked to replace "XXXX" 3058 (here and in the MIB module) with the assigned value and to remove 3059 this note. 3061 10. References 3062 10.1. Normative References 3064 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3065 Requirement Levels", BCP 14, RFC 2119, March 1997. 3067 [RFC5542] Nadeau, T., Ed., Zelig, D., Ed., and O. Nicklass, Ed., 3068 "Definitions of Textual Conventions for Pseudowire (PW) 3069 Management", RFC 5542, May 2009. 3071 [RFC5601] Nadeau, T., Ed. and D. Zelig, Ed. "Pseudowire (PW) 3072 Management Information Base (MIB)", RFC 5601, July 2009. 3074 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3075 Requirement Levels", BCP 14, RFC 2119, March 1997. 3077 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3078 Schoenwaelder, Ed., "Structure of Management Information 3079 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3081 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3082 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3083 STD 58, RFC 2579, April 1999. 3085 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3086 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3087 April 1999. 3089 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3090 MIB", RFC 2863, June 2000. 3092 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 3093 Architecture for Describing Simple Network Management 3094 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 3095 December 2002. 3097 [RFC3592] Tesink, K., "Definitions of Managed Objects for the 3098 Synchronous Optical Network/Synchronous Digital Hierarchy 3099 (SONET/SDH) Interface Type", RFC 3592, September 2003. 3101 [RFC3593] Tesink, K., "Textual Conventions for MIB Modules Using 3102 Performance History Based on 15 Minute Intervals", 3103 RFC 3593, September 2003. 3105 [RFC3705] Ray, B. and R. Abbi, "High Capacity Textual Conventions 3106 for MIB Modules Using Performance History Based on 15 3107 Minute Intervals", RFC 3705, February 2004. 3109 [RFC4842] Malis, A., Pate, P., Cohen, R., and D. Zelig, "Synchronous 3110 Optical Network/Synchronous Digital Hierarchy (SONET/SDH) 3111 Circuit Emulation over Packet (CEP)", RFC 4842, 3112 April 2007. 3114 10.2. Informative References 3116 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3117 "Introduction and Applicability Statements for Internet- 3118 Standard Management Framework", RFC 3410, December 2002. 3120 [RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to- 3121 Edge (PWE3) Architecture", RFC 3985, March 2005. 3123 Authors' Addresses 3125 David Zelig (editor) 3126 Oversi 3127 1 Rishon LeZion St. 3128 Em HaMoshavot Center 3129 Petach Tikva 3130 Israel, 49723 3132 Phone: +972-77-333-7777 3133 Email: David Zelig 3135 Ron Cohen (editor) 3136 Resolute Networks 3137 2480 Sand Hill Road, Suite 200 3138 Menlo Park, CA 94025 3139 USA 3141 Email: ronc@resolutenetworks.com 3143 Thomas D. Nadeau (editor) 3144 Email: tnadeau@lucidvision.com 3146 Acknowledgment 3148 Funding for the RFC Editor function is provided by the IETF 3149 Administrative Support Activity (IASA).