idnits 2.17.00 (12 Aug 2021) /tmp/idnits45787/draft-danenberg-pw-cem-mib-02.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 47 longer pages, the longest (page 4) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 2002) is 7311 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2571' is mentioned on line 154, but not defined ** Obsolete undefined reference: RFC 2571 (Obsoleted by RFC 3411) == Missing Reference: 'RFC1155' is mentioned on line 160, but not defined == Missing Reference: 'RFC1212' is mentioned on line 160, but not defined == Missing Reference: 'RFC1215' is mentioned on line 161, but not defined == Missing Reference: 'RFC2578' is mentioned on line 162, but not defined == Missing Reference: 'RFC2579' is mentioned on line 162, but not defined == Missing Reference: 'RFC2580' is mentioned on line 163, but not defined == Missing Reference: 'RFC1157' is mentioned on line 176, but not defined == Missing Reference: 'RFC1901' is mentioned on line 169, but not defined == Missing Reference: 'RFC1906' is mentioned on line 171, but not defined ** Obsolete undefined reference: RFC 1906 (Obsoleted by RFC 3417) == Unused Reference: 'ENCAP' is defined on line 2410, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 2422, but no explicit reference was found in the text == Unused Reference: 'IANAFamily' is defined on line 2427, but no explicit reference was found in the text == Unused Reference: 'SNMPArch' is defined on line 2433, but no explicit reference was found in the text == Unused Reference: 'SMIv1' is defined on line 2437, but no explicit reference was found in the text == Unused Reference: 'SNMPv1Traps' is defined on line 2444, but no explicit reference was found in the text == Unused Reference: 'SMIv2' is defined on line 2477, but no explicit reference was found in the text == Unused Reference: 'SNMPv2TC' is defined on line 2482, but no explicit reference was found in the text == Unused Reference: 'SNMPv2Conf' is defined on line 2488, but no explicit reference was found in the text == Unused Reference: 'SNMPv1' is defined on line 2492, but no explicit reference was found in the text == Unused Reference: 'SNMPv2c' is defined on line 2496, but no explicit reference was found in the text == Unused Reference: 'SNMPv2TM' is defined on line 2500, but no explicit reference was found in the text == Unused Reference: 'SNMPv3MP' is defined on line 2507, but no explicit reference was found in the text == Unused Reference: 'SNMPv3USM' is defined on line 2512, but no explicit reference was found in the text == Unused Reference: 'SNMPv2PO' is defined on line 2517, but no explicit reference was found in the text == Unused Reference: 'SNMPv3App' is defined on line 2522, but no explicit reference was found in the text == Unused Reference: 'SNMPv3VACM' is defined on line 2525, but no explicit reference was found in the text == Unused Reference: 'IPSEC' is defined on line 2530, but no explicit reference was found in the text == Unused Reference: 'ATOMMIB' is defined on line 2537, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'CEP' -- Possible downref: Non-RFC (?) normative reference: ref. 'LAYER' -- Possible downref: Non-RFC (?) normative reference: ref. 'TRANS' -- Possible downref: Non-RFC (?) normative reference: ref. 'ENCAP' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWTC' ** Obsolete normative reference: RFC 2558 (ref. 'SONETMIB') (Obsoleted by RFC 3592) ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAFamily' ** Obsolete normative reference: RFC 2271 (ref. 'SNMPArch') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. 'SNMPv1Traps') ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 1902 (ref. 'SMIv2') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. 'SNMPv2TC') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. 'SNMPv2Conf') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. 'SNMPv1') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. 'SNMPv2c') -- Possible downref: Non-RFC (?) normative reference: ref. 'SNMPv2TM' ** Obsolete normative reference: RFC 2272 (ref. 'SNMPv3MP') (Obsoleted by RFC 2572) -- Duplicate reference: RFC2574, mentioned in 'SNMPv3USM', was also mentioned in 'RFC2574'. ** Obsolete normative reference: RFC 2574 (ref. 'SNMPv3USM') (Obsoleted by RFC 3414) -- Duplicate reference: RFC1905, mentioned in 'SNMPv2PO', was also mentioned in 'RFC1905'. ** Obsolete normative reference: RFC 1905 (ref. 'SNMPv2PO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. 'SNMPv3App') (Obsoleted by RFC 2573) -- Duplicate reference: RFC2575, mentioned in 'SNMPv3VACM', was also mentioned in 'RFC2575'. ** Obsolete normative reference: RFC 2575 (ref. 'SNMPv3VACM') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC') (Obsoleted by RFC 4301) ** Obsolete normative reference: RFC 2233 (ref. 'IFMIB') (Obsoleted by RFC 2863) Summary: 29 errors (**), 0 flaws (~~), 32 warnings (==), 13 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Dave Danenberg 2 Internet Draft Scott C. Park 3 Expires: Nov 2002 Litchfield Communications, Inc. 5 Thomas D. Nadeau 6 Cisco Systems, Inc. 8 David Zelig 9 Corrigent Systems 11 Andrew G. Malis 12 Vivace Networks, Inc. 14 May 2002 16 SONET/SDH Circuit Emulation Service Over Packet (CEP) Management 17 Information Base Using SMIv2 19 draft-danenberg-pw-cem-mib-02.txt 21 Status of this Memo 23 This document is an Internet-Draft and is in full conformance with 24 all provisions of Section 10 of RFC2026. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF), its areas, and its working groups. Note that 28 other groups may also distribute working documents as Internet- 29 Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six 32 months and may be updated, replaced, or obsoleted by other documents 33 at any time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 The list of current Internet-Drafts can be accessed at 37 http://www.ietf.org/ietf/1id-abstracts.txt 39 The list of Internet-Draft Shadow Directories can be accessed at 40 http://www.ietf.org/shadow.html. 42 Copyright (C) The Internet Society (2001). All rights reserved. 44 1 Abstract 46 This memo defines an experimental portion of the Management 47 Information Base (MIB) for use with network management protocols in 48 the Internet community. In particular, it describes managed objects 49 for modeling Native Service Processing of SONET/SDH circuits over a 50 Packet Switch Network (PSN). 52 Danenberg et al 1 53 Table of Contents 55 1 Abstract.....................................................1 56 2 Introduction.................................................2 57 3 Terminology..................................................3 58 4 The SNMP Management Framework................................3 59 4.1 Object Definitions..........................................4 60 5 Feature Checklist............................................5 61 6 CEP MIB usage................................................5 62 6.1 Summary of CEP MIB..........................................5 63 6.2 CEP configuration Step by Step..............................6 64 7 Example of CEP Setup.........................................7 65 8 CEP MIB definitions..........................................9 66 9 References..................................................46 67 10 Author's Addresses.........................................49 68 11 Full Copyright Statement...................................50 70 2 Introduction 72 This document describes a model for managing encapsulated SONET Time 73 Division Multiplexed (TDM) digital signals for transmission over a 74 Packet Switched Network (PSN). 76 This document is closely related to [CEP], which describes the 77 technology to encapsulate TDM signals and provide the Circuit 78 Emulation Service over a Packet Switched Network (PSN). This document 79 is also related to [TRANS and ENCAP], describing the transport and 80 encapsulation of Layer 2 circuits over MPLS, respectively. NOTE: the 81 CEP encapsulation can be used over non-MPLS PSNs as well as MPLS 82 PSNs. 84 The model for CEP management is a MIB. The CEP MIB described in this 85 document works closely with the MIBs described in [PWMIB] and the 86 textual conventions defined in [PWTC]. In the spirit of the [IFMIB], 87 a CEP connection will be a virtual connection (VC), and will 88 therefore not be represented in the ifTable. 90 CEP is currently specified to carry "structured" SONET paths. Meaning 91 that each SONET path within the section/line can be processed 92 separately. The SONET section/line interface stack is modeled within 93 [SONETMIB]. The CEP MIB will reference SONET paths as modeled within 94 [SONETMIB]. 96 Comments should be made directly to PWE3 at pwe3@ietf.org. 98 This memo does not, in its draft form, specify a standard for the 99 Internet community. 101 Conventions used in this document 103 Danenberg et al Expires November 2002 2 104 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 105 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 106 this document are to be interpreted as described in RFC-2119 107 [BCP14]. 109 3 Terminology 111 CEP terminology comes from the CEP draft that describes a mechanism 112 for transporting SONET Time Division Multiplexed (TDM) digital 113 signals over a packet-oriented network. The mechanism for structured 114 (as outlined in the CEP draft) terminates the SONET section and line 115 overhead and then breaks the SONET path's Synchronous Payload 116 Envelope (SPE) into fragments for transmission over a PSN. A CEP 117 header is appended at the beginning of each fragment to provide 118 information regarding where the SPE begins within the packet stream, 119 a sequence number, and pointer adjustment information (see [CEP]). 121 "NSP" (Native Service Processing) refers to the method of adapting a 122 "native" service such that it can be presented to the PW (Pseudo- 123 Wire) for transmission across the packet core. In this case, the 124 native protocol is SONET/SDH. See [LAYER]. 126 "Outbound" references the traffic direction where a SONET path's 127 payload (SPE) is received, adapted to packet, assigned a VC label, 128 and sent into the PSN. 130 Conversely, "inbound" is the direction where packets are received 131 from the PSN, packet payloads are reassembled back into an SPE, and 132 inserted as a SONET path into the SONET section and line. 134 Since A SONET path is bi-directional and symmetrical, it uses the 135 same SONET time-slot, SONET width, packet size. Inbound and outbound 136 VC labels may differ. 138 CEP will normally transmit into an originating "head" end of a PSN's 139 tunnel, and receive from a terminating "tail" end a PSN's tunnel. In 140 the case of an MPLS PSN, a CEP connection typically uses a VC 141 (virtual connection) Label within a Tunnel Label [TRANS]. Multiple 142 CEP VCs each with a unique VC Label and similar traffic engineering 143 requirements can share the same PSN tunnel. For MPLS PSNs, the Tunnel 144 Label is known as the "outer" Label, while the VC Label is known as 145 the "inner" Label. An exception to this is with adjacent MPLS LSRs. 146 In this case, there is an option for CEP VCs to connect directly 147 without an outer Label. 149 4 The SNMP Management Framework 151 The SNMP Management Framework presently consists of five major 152 components: 154 o An overall architecture, described in RFC 2571 [RFC2571]. 156 Danenberg et al Expires November 2002 3 157 o Mechanisms for describing and naming objects and events for the 158 purpose of management. The first version of this Structure of 159 Management Information (SMI) is called SMIv1 and described in STD 16, 160 RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 161 [RFC1215]. The second version, called SMIv2, is described in STD 58, 162 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 163 [RFC2580]. 165 o Message protocols for transferring management information. The 166 first version of the SNMP message protocol is called SNMPv1 and 167 described in STD 15, RFC 1157 [RFC1157]. A second version of the 168 SNMP message protocol, which is not an Internet standards track 169 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and 170 RFC 1906 [RFC1906]. The third version of the message protocol is 171 called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] 172 and RFC 2574 [RFC2574]. 174 o Protocol operations for accessing management information. The 175 first set of protocol operations and associated PDU formats is 176 described in STD 15, RFC 1157 [RFC1157]. A second set of protocol 177 operations and associated PDU formats is described in RFC 1905 178 [RFC1905]. 180 o A set of fundamental applications described in RFC 2573 181 [RFC2573] and the view-based access control mechanism described in 182 RFC 2575 [RFC2575]. 184 A more detailed introduction to the current SNMP Management Framework 185 can be found in RFC 2570 [RFC2570]. Managed objects are accessed via 186 a virtual information store, termed the Management Information Base 187 or MIB. Objects in the MIB are defined using the mechanisms defined 188 in the SMI. This memo specifies a MIB module that is compliant to the 189 SMIv2. A MIB conforming to the SMIv1 can be produced through the 190 appropriate translations. The resulting translated MIB must be 191 semantically equivalent, except where objects or events are omitted 192 because no translation is possible (use of Counter64). Some machine 193 readable information in SMIv2 will be converted into textual 194 descriptions in SMIv1 during the translation process. However, this 195 loss of machine readable information is not considered to change the 196 semantics of the MIB. 198 4.1 Object Definitions 200 Managed objects are accessed via a virtual information store, termed 201 the Management Information Base or MIB. Objects in the MIB are 202 defined using the subset of Abstract Syntax Notation One (ASN.1) 203 defined in the SMI. In particular, each object type is named by an 204 OBJECT IDENTIFIER, an administratively assigned name. The object type 205 together with an object instance serves to uniquely identify a 206 specific instantiation of the object. For human convenience, we 207 often use a textual string, termed the descriptor, to also refer to 208 the object type. 210 Danenberg et al Expires November 2002 4 211 5 Feature Checklist 213 This MIB is designed to satisfy the following requirements and 214 constraints: 216 - Fits within the architecture defined [PWMIB]. 218 - The MIB supports point-to-point CEP connections. Point-to- 219 multipoint connections are for future study. 221 - The MIB configures the connection: timeslots, packet length, error 222 actions, and many other CEP objects. 224 - The MIB reports: packet counts, error counts, and many other status 225 objects. 227 6 CEP MIB usage 229 6.1 Summary of CEP MIB 231 - The CEP VC Table (pwVcCepTable) contains the SONET Path ifIndex, 232 SONET Path Time slot, the pwVcCepCfgTable index, config error 233 indications, and various status indications. 235 - The CEP VC Configuration Parameter Table (pwVcCepCfgTable) has 236 objects for CEP VC configuration. In situations where sets of config 237 objects are common amongst more than 1 CEP VC, 1 entry here may be 238 referenced by many pwVcCepTable entries. 240 - The CEP Performance Current Table (pwVcCemPerfCurrentTable) 241 contains CEP stats for the current 15-minute period. 243 - The CEP Performance Interval Table (pwVcCemPerfIntervalTable) is 244 similar to the pwVcCemPerfCurrentTable. It contains historical 245 intervals (usually 96 15-minute entries to cover a 24 hour period). 247 Note: the performance interval statistics are supported by CEP due to 248 the very function of CEP - that is, processing SONET. See [SONETMIB]. 250 - The CEP Performance Total Table (pwVcCepPerfTotalTable) is similar 251 to the pwVcCemPerfCurrentTable. It contains statistics accumulated 252 since the CEP VC was first established. 254 - The Conformance Config Table (pwVcCepConformanceCfgTable) allows 255 the vendor to specify the extent to which certain objects are 256 supported (or not). 258 Danenberg et al Expires November 2002 5 259 6.2 CEP configuration Step by Step 261 Configuring a CEP VC involves the following steps. 263 First create an entry in the pwVcTable and configure the PSN tunnels: 265 - Follow steps as defined in [PWMIB]. 267 Configure the SONET Path parameters : 269 - Set the SONET path width in the sonetPathCurrentTable [SONETMIB]. 271 - Set the SONET path index and the SONET path starting time slot in 272 the pwVcCepTable. 274 NOTE: The agent will have created an entry in the pwVcCepTable based 275 on the entry created in the pwVcTable. 277 Configure the CEP VC: 279 - If necessary, create an entry in the pwVcCepCfgTable (a suitable 280 entry may already exist). Set packet length, etc. 282 - Set the index of this pwVcCepCfgTable entry in the pwVcCepTable. 284 Observe the CEP VC: 286 - Once a CEP VC is operational, the pwVcCepPerfCurrentTable, 287 pwVcCepPerfIntervalTable, and pwVcCepPerfTotalTable are used to 288 monitor the various counts, indicators, and conditions of the VC. 290 Conforming to the CEP MIB objects: 292 - The pwVcCepConformanceCfgTable is used to state True/False whether 293 certain objects are supported. An ASCII string object is available 294 with every True/False object as a means to explain the extent of 295 'true' support, or perhaps explain why the 'false' was set. 297 Danenberg et al Expires November 2002 6 298 7 Example of CEP Setup 300 In this section we provide an example of using the MIB objects 301 described in section 8 to set up a CEP VC (width of 3 STSs, starting 302 at time slot 1). While this example is not meant to illustrate every 303 permutation of the MIB, it is intended as an aid to understanding 304 some of the key concepts. It is meant to be read after going through 305 the MIB itself. See [PWMIB] for an example of setting up PSN Tunnels. 307 First configure the SONET path width, starting time-slot, and 308 associated CEP VC. In this case, an STS-3c starts at SONET time slot 309 1 (and is distributed normally within the SONET frame). In the 310 following example, the ifIndex for the sonetPathCurrentEntry is 23, 311 while the pwVcCepCfgTable index is 9. 313 In [SONETMIB] sonetPathCurrentEntry (ifIndex = 23) : 314 { 315 sonetPathCurrentWidth = 3, 316 sonetPathCurrentStatus 317 ... 318 ... 319 } 321 Create an entry in the pwVcCepCfgTable (index = 9) : 322 { 323 pwVcCepCfgNormalPktLength = 500 -- payload bytes 324 pwVcCepCfgMinPktLength = 0 -- no minimum 325 pwVcCepCfgPktReorder = FALSE 326 pwVcCepCfgEnableDBA = ais 327 pwVcCepCfgJtrBfrDepth = 500 -- micro-seconds 329 pwVcCepCfgConsecPktsInsync = 2 -- Exit LOPS state 330 pwVcCepCfgConsecMissingOutSync = 10 -- Enter LOPS state 332 pwVcCepCfgPktErrorPlayOutValue = playAllOnes 334 pwVcCepCfgMissingPktsToSes = 3 -- packets, 335 pwVcCepCfgSesToUas = 2 -- seconds, 336 pwVcCepCfgSecsToExitUas = 10 -- seconds, 338 pwVcCepCfgRowStatus = createAndGo 339 } 341 Check that there are no error bits set in pwVcCepConfigError. 343 Danenberg et al Expires November 2002 7 344 In PW-MIB: Get a new index and create a new pwVcTable entry using 345 pwVcIndexNext (here, the VC index = 83) and pwVcRowStatus. In this 346 new entry, set pwVcType to 'cep'. This should create a new entry in 347 the pwVcCepTable. Set up and the SONET path ifIndex, SONET path time 348 slot, and Cfg Table indexes within this new pwVcCep table entry: 350 { 351 pwVcCepSonetIfIndex = 23 -- Index of associated entry 352 -- in sonetPathCurrent table. 354 pwVcCepSonetTimeSlot = 1 -- Starting time slot. 356 pwVcCepCfgIndex = 9 -- Index of associated entry 357 -- in pwVcCepCfg table (above). 358 } 360 Check that there are no error bits set in pwVcCepSonetConfigError. 362 Danenberg et al Expires November 2002 8 363 8 CEP MIB definitions 365 PW-CEP-MIB DEFINITIONS ::= BEGIN 367 IMPORTS 368 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 369 experimental, Integer32, Counter32, Unsigned32, 370 Counter64 371 FROM SNMPv2-SMI 373 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 374 FROM SNMPv2-CONF 376 TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, 377 TimeStamp 378 FROM SNMPv2-TC 380 InterfaceIndexOrZero 381 FROM IF-MIB 383 PerfCurrentCount, PerfIntervalCount 384 FROM PerfHist-TC-MIB 386 pwVcIndex, pwVcOperStatus 387 FROM PW-MIB 389 SnmpAdminString 390 FROM SNMP-FRAMEWORK-MIB; 392 -- The CEP MIB 394 pwVcCepMIB MODULE-IDENTITY 395 LAST-UPDATED "0205291200Z" -- May 29 2002 12:00:00 EST 396 ORGANIZATION "Pseudo-Wire Emulation Edge-to-Edge (PWE3) 397 Working Group" 398 CONTACT-INFO 399 " Dave Danenberg 400 Postal: Litchfield Communications, Inc. 401 27 Princeton Rd 402 Princeton Center West 403 Watertown, CT 06795 404 Tel: +1-203-591-7062 405 Email: dave_danenberg@litchfieldcomm.com 407 Thomas D. Nadeau 408 Postal: Cisco Systems, Inc. 409 250 Apollo Drive 410 Chelmsford, MA 01824 411 Tel: +1-978-244-3051 412 Email: tnadeau@cisco.com 414 David Zelig 415 Postal: Corrigent Systems LTD. 417 Danenberg et al Expires November 2002 9 418 126, Yigal Alon St. 419 Tel Aviv, ISRAEL 420 Phone: +972-3-6945273 421 E-mail: davidz@corrigent.com 423 Scott Park 424 Postal: Litchfield Communications, Inc. 425 27 Princeton Rd 426 Princeton Center West 427 Watertown, CT 06795 428 Tel: +1-203-591-7066 429 Email: scott_park@litchfieldcomm.com 431 Andrew G. Malis 432 Postal: Vivace Networks, Inc. 433 2730 Orchard Parkway 434 San Jose, CA 95134 435 Email: Andy.Malis@vivacenetworks.com 437 Or the PWE3 Working Group (pwe3@ietf.org) " 439 DESCRIPTION 440 "This MIB contains managed object definitions for Circuit 441 Emulation over Packet (CEP) as in: Malis, A., Vogelsang, 442 S., Johnson, T., and Martini, L. 'SONET/SDH Circuit 443 Emulation Over Packet (CEP) encapsulation', Internet Draft 444 , expires September 2002. 446 This MIB reports to the PW-MIB. The PW-MIB contains 447 structures and MIB associations generic to Pseudo-Wire 448 Virtual Circuit (VC) emulation. VC-specific MIBs (such as 449 this) contain config and stats for specific VC types." 451 -- Revision history. 452 REVISION 453 "0205291200Z" -- 29 May 2002 12:00:00 EST 454 DESCRIPTION 455 "- Renamed EsTimeStamp to LastErrorTimeStamp. 456 - Renamed LastDefectsAtEs to LatchedIndications. 457 - Renamed CurrentDefects to CurrentIndications. 458 - Renamed defect indications (cepAis, cepRdi). 459 - Renamed DBA bit settings (ais and unequipped). 460 - Added objects: CfgJtrBfrResetOorange and 461 CfgJtrBfrResetOorangeCnt. 462 - Moved SONET Time Slot and Time Slot cfg error 463 to CEP table from SONET extension table. Deleted 464 SONET extension table. 465 - Added Failure Counts (FCs) to stats tables. 466 - Removed pwVcCepPerfCurrentTimeElapsed (it is 467 a duplicate of pwVcCepTimeElapsed). 468 - Removed 32-bit counters that were duplicates 469 of 64-bit (HC) counters. 470 - Other minor changes." 472 Danenberg et al Expires November 2002 10 473 REVISION 474 "0202271200Z" -- 27 February 2002 12:00:00 EST 475 DESCRIPTION 476 "- Added objects pwVcCepTimeElapsed and 477 pwVcCepValidIntervals for more accurate knowledge 478 of interval data. 479 - Changed pwVcCepCfgJtrBfrDepth units from packets 480 to microseconds, and updated description. 481 - Changed JtrBfrOoseqDropped to JtrBfrOoRngDropped 482 (i.e, 'out of sequence' to 'out of range'). 483 - Removed JtrBfrOverruns counter objects. This info 484 is now contained within the JtrBfrOoRngDropped 485 object. 486 - Changed description of JtrBfrUnderrun. 487 - Moved LastDefectsAtEs, LastEsTimeStamp, and 488 DiscontinuityTime to the pwVcCepTable table. 489 Removed them as conformance config objects. 490 - Created new CurrentDefects in CepTable. 491 - Added cepAis to and changed rdi to cepRdi 492 (both are now in LastDefectsAtEs). Added note 493 to cepAis - it must not (in itself) cause a 494 cep down notification. 495 - Changed the pwVcCepSonetExtTable to augment 496 the sonetPathCurrentTable in RFC 2558. Imported 497 sonetPathCurrentTable from the SONET-MIB. 498 - Renamed PktResequence to PktReorder." 500 REVISION 501 "0111161200Z" -- 16 November 2001 12:00:00 EST 502 DESCRIPTION 503 "- Changed CEM to CEP. 504 - Removed: 'unstructured' CEP type, ECC references, 505 and signaling (CEP options) references, multiple 506 VC instances references, and APS references. 507 - Improved descriptions and some improved object names. 508 - New conformance section. New ConformanceCfg table. 509 - PktResequence is now read-only. 510 - ConfMaxPktLength is now ConfNormalPktLength. 511 - Replaced User Error Action with PlayOutValue. 512 - New cfg object : consecutive non-SESs to exit UAS. 513 - New cfg objects : elapsed time for stats intervals. 514 - New stats object: summary packet error. 515 - New object : added ConfigError to SonetExt table. 517 - NOTE: Many objects added, deleted, or moved - so many 518 OIDs have been re-ordered." 520 REVISION 521 "0109071200Z" -- 07 September 2001 12:00:00 EST 522 DESCRIPTION 523 "- Separated Top level Cfg objects from Total CEM stats. 524 - Removed references to VC instances." 526 Danenberg et al Expires November 2002 11 527 REVISION 528 "0107191200Z" -- 19 July 2001 12:00:00 EST 529 DESCRIPTION 530 "Based on the PWE3 Requirements/Framework, the original 531 CEM MIB (draft-danenberg-sonet-ces-mpls-mib-00.txt) has 532 Been split into 3 drafts: 534 - PW-MIB (Zelig, et al). Service-independent MIB. 535 - PW-TC-MIB (Nadeau, et al). Textual Conventions. 536 - PW-CEM-MIB (Danenberg, et al). Service-specific MIB. 538 Aside from the split, then PW-CEM-MIB has undergone 539 other changes: 541 - Ability to define LOPS (loss of packet sync), SES 542 and UAS. 543 - Support for 'unstructured' operation. 544 - Support for CEM-RDI. 545 - Many more minor changes and clarifications." 547 ::= { experimental xxxx } -- To be assigned by IANA 549 -- Local Textual conventions 550 PwVcCepCfgIndex ::= TEXTUAL-CONVENTION 551 STATUS current 552 DESCRIPTION 553 "Index into the pwVcCepCfgTable." 554 SYNTAX Unsigned32 556 -- Top level components of this MIB. 558 -- Traps 559 pwVcCepNotifications OBJECT IDENTIFIER 560 ::= { pwVcCepMIB 0 } 561 pwVcCepNotifyPrefix OBJECT IDENTIFIER 562 ::= { pwVcCepNotifications 0 } 563 -- Tables, Scalars 564 pwVcCepObjects OBJECT IDENTIFIER 565 ::= { pwVcCepMIB 1 } 566 -- Conformance 567 pwVcCepConformance OBJECT IDENTIFIER 568 ::= { pwVcCepMIB 2 } 570 -- CEP VC table 572 pwVcCepTable OBJECT-TYPE 573 SYNTAX SEQUENCE OF PwVcCepEntry 574 MAX-ACCESS not-accessible 575 STATUS current 576 DESCRIPTION 577 "This table contains the index to the entry SONET path 578 table for this CEP VC, and the index to the CEP config 579 table." 581 Danenberg et al Expires November 2002 12 582 ::= { pwVcCepObjects 1 } 584 pwVcCepEntry OBJECT-TYPE 585 SYNTAX PwVcCepEntry 586 MAX-ACCESS not-accessible 587 STATUS current 588 DESCRIPTION 589 "This MIB reports to the PW-MIB. This table is indexed by 590 the same index that was created for the associated entry 591 in the PW VC Table (in the PW-MIB). 593 - The PwVcIndex. 595 An entry is created in this table by the agent for every 596 entry in the pwVc table with a VcType of 'cep'." 598 INDEX { pwVcIndex } 600 ::= { pwVcCepTable 1 } 602 PwVcCepEntry ::= SEQUENCE { 604 pwVcCepType INTEGER, 605 pwVcCepSonetIfIndex InterfaceIndexOrZero, 606 pwVcCepSonetTimeSlot Unsigned32, 607 pwVcCepSonetConfigError BITS, 608 pwVcCepCfgIndex PwVcCepCfgIndex, 609 pwVcCepTimeElapsed Integer32, 610 pwVcCepValidIntervals Integer32, 611 pwVcCepCurrentIndications BITS, 612 pwVcCepLatchedIndications BITS, 613 pwVcCepLastEsTimeStamp TimeStamp 614 } 616 pwVcCepType OBJECT-TYPE 617 SYNTAX INTEGER { 618 structured (1) 619 } 620 MAX-ACCESS read-only 621 STATUS current 622 DESCRIPTION 623 "Specifies the type of CEP VC. Currently only 624 structured types are supported. Other CEP Types 625 may be defined in the future. 626 Note: This object MUST be changed to 'read-write' 627 if other CEP types are added." 628 DEFVAL { structured } 629 ::= { pwVcCepEntry 1 } 631 pwVcCepSonetIfIndex OBJECT-TYPE 632 SYNTAX InterfaceIndexOrZero 633 MAX-ACCESS read-write 634 STATUS current 635 DESCRIPTION 637 Danenberg et al Expires November 2002 13 638 "This is a unique index within the ifTable. It represents 639 the interface index for the SONET path. A value of zero 640 indicates an interface index that has yet to be determined. 641 Once set, if the SONET ifIndex is (for some reason) later 642 removed, the agent MAY delete the associated PW VC rows 643 (e.g., this pwVcCep table entry). If the agent does not 644 delete the rows, it is recommended that the agent set this 645 object to zero." 646 ::= { pwVcCepEntry 2 } 648 pwVcCepSonetTimeSlot OBJECT-TYPE 649 SYNTAX Unsigned32 (1..192) 650 MAX-ACCESS read-write 651 STATUS current 652 DESCRIPTION 653 "In structured CEP, this object indicates the starting 654 time-slot for this SONET path within the SONET line 655 and section. For OC-48, this value could range from 1 656 to 48. The SONET path width must be taken into 657 consideration here. For example, in an OC-48, an 658 STS-3c could not start at time-slot 47." 659 REFERENCE "RFC 2558, sonetPathCurrentWidth." 660 ::= { pwVcCepEntry 3 } 662 pwVcCepSonetConfigError OBJECT-TYPE 663 SYNTAX BITS { 664 other ( 0), 665 timeslotInUse ( 1), 666 timeslotMisuse( 2) 667 } 668 MAX-ACCESS read-only 669 STATUS current 670 DESCRIPTION 671 "timeslotInUse is when another CEP VC (via SONET ifIndex) 672 has already reserved a timeslot(s) that this CEP VC 673 is attempting to reserved. 674 timeslotMisuse is set, for example, if specifying a 675 starting timeslot of 45 for a SONET path of an STS-12c 676 width." 677 ::= { pwVcCepEntry 4 } 679 pwVcCepCfgIndex OBJECT-TYPE 680 SYNTAX PwVcCepCfgIndex 681 MAX-ACCESS read-write 682 STATUS current 683 DESCRIPTION 684 "Index to CEP configuration table below. It is likely that 685 multiple CEP VCs will share 1 CEP Cfg table entry." 686 ::= { pwVcCepEntry 5 } 688 pwVcCepTimeElapsed OBJECT-TYPE 689 SYNTAX Integer32 (1..900) 690 MAX-ACCESS read-only 691 STATUS current 693 Danenberg et al Expires November 2002 14 694 DESCRIPTION 695 "The number of seconds, including partial seconds, 696 that have elapsed since the beginning of the current 697 measurement period. If, for some reason, such as an 698 adjustment in the system's time-of-day clock, the 699 current interval exceeds the maximum value, the 700 agent will return the maximum value." 701 ::= { pwVcCepEntry 6 } 703 pwVcCepValidIntervals OBJECT-TYPE 704 SYNTAX Integer32 (0..96) 705 MAX-ACCESS read-only 706 STATUS current 707 DESCRIPTION 708 "The number of previous 15-minute intervals 709 for which data was collected. 710 An agent with CEP capability must be capable 711 of supporting at least n intervals. The minimum value 712 of n is 4, The default of n is 32 and the maximum value 713 of n is 96. 714 The value will be unless the measurement was 715 (re-)started within the last (*15) minutes, in which 716 case the value will be the number of complete 15 717 minute intervals for which the agent has at least 718 some data. In certain cases (e.g., in the case 719 where the agent is a proxy) it is possible that some 720 intervals are unavailable. In this case, this 721 interval is the maximum interval number for 722 which data is available. " 723 ::= { pwVcCepEntry 7 } 725 pwVcCepCurrentIndications OBJECT-TYPE 726 SYNTAX BITS { 727 missingPkt ( 0), 728 ooRngDropped( 1), 729 jtrBfrUnder ( 2), 730 pktBadLength( 3), 731 lops ( 4), 732 cepRdi ( 5), 733 cepAis ( 6) 734 } 735 MAX-ACCESS read-only 736 STATUS current 737 DESCRIPTION 738 "Definitions: 740 missingPkt - While playing out a sequence of packets, 741 a packet(s) was determined to be missing based on 742 a gap in the CEP sequence number. Note: If the imple- 743 mentation supports packet re-ordering, detecting gaps 744 should not take place as packets arrive, only as they 745 are played out - this gives time for mis-ordered packets 746 to arrive late. 748 Danenberg et al Expires November 2002 15 749 ooRngDropped - Packet(s) arrives that is outside the 750 range of the jitter buffer. This may be because the 751 jitter buffer is full, or the sequence number addresses 752 a buffer outside the current jitter buffer range, or 753 addresses an already occupied buffer within range. 754 Whether or not packet re-ordering is supported by the 755 implementation, this indication MUST be supported. 757 jtrBfrUnder - The jitter buffer underflowed due to 758 not enough packets arriving as packets were being 759 played out. 761 pktBadLength - Non-bandwidth-saving packet arrives 762 larger or smaller than pwVcCepCfgNormalPktLength. 764 lops - Loss Of Packet Sync. See malis-pwe3-sonet. 766 cepRdi - Circuit Emulation over Packet Remote 767 Defect Indication. Generated by the remote CEP 768 de-packetizer when detecting LOPS. Note: not gen- 769 erated by the remote SONET function. See malis- 770 pwe3-sonet. 772 cepAis - Remote CEP packetizer has detected AIS 773 on its incoming SONET stream. See malis-pwe3-sonet. 774 Note: cepAis MUST NOT (in itself) cause a CEP 775 down notification. This would be a layer violation. 777 Note: currently there is no hierarchy of CEP defects. 779 Note: the algorithm used to capture these indications 780 is implementation specific." 781 ::= { pwVcCepEntry 8 } 783 pwVcCepLatchedIndications OBJECT-TYPE 784 SYNTAX BITS { 785 missingPkt ( 0), 786 ooRngDropped( 1), 787 jtrBfrUnder ( 2), 788 pktBadLength( 3), 789 lops ( 4), 790 cepRdi ( 5), 791 cepAis ( 6) 792 } 793 MAX-ACCESS read-only 794 STATUS current 795 DESCRIPTION 796 "The state of CEP indicators when the CEP VC last declared 797 an errored second (either as ES, SES or a second with 798 errors inside a UAS) condition. At this time, only LOPS 799 can create a failure. Since indicators other than LOPS are 800 useful, all are latched here. For bit definitions, see 801 pwVcCepCurrentIndications above. 803 Danenberg et al Expires November 2002 16 804 Note: the algorithm used to latch these indications when 805 entering an defect state is implementation specific." 806 ::= { pwVcCepEntry 9 } 808 pwVcCepLastEsTimeStamp OBJECT-TYPE 809 SYNTAX TimeStamp 810 MAX-ACCESS read-only 811 STATUS current 812 DESCRIPTION 813 "The value of sysUpTime on the most recent occasion at 814 which the CEP VC entered the ES or SES state." 815 ::= { pwVcCepEntry 10 } 817 -- End of PW CEP VC table 819 -- Obtain index for PW CEP Configuration table entries 820 pwVcCepCfgIndexNext OBJECT-TYPE 821 SYNTAX PwVcCepCfgIndex 822 MAX-ACCESS read-only 823 STATUS current 824 DESCRIPTION 825 "This object contains an appropriate value to be used 826 for pwVcCepCfgIndex when creating entries in the 827 pwVcCepCfgTable. The value 0 indicates that no 828 unassigned entries are available. To obtain the 829 value of pwVcCepCfgIndex for a new entry in the 830 pwVcCepCfgTable, the manager issues a management 831 protocol retrieval operation to obtain the current 832 value of pwVcCepCfgIndex. After each retrieval 833 operation, the agent should modify the value to 834 reflect the next unassigned index. After a manager 835 retrieves a value the agent will determine through 836 its local policy when this index value will be made 837 available for reuse." 838 ::= { pwVcCepObjects 2 } 840 -- PW CEP VC Configuration Table 842 pwVcCepCfgTable OBJECT-TYPE 843 SYNTAX SEQUENCE OF PwVcCepCfgEntry 844 MAX-ACCESS not-accessible 845 STATUS current 846 DESCRIPTION 847 "This table contains a set of parameters that may be 848 referenced by 1 or more CEP VCs by pwVcCepTable." 849 ::= { pwVcCepObjects 3 } 851 pwVcCepCfgEntry OBJECT-TYPE 852 SYNTAX PwVcCepCfgEntry 853 MAX-ACCESS not-accessible 854 STATUS current 855 DESCRIPTION 856 "These parameters define the characteristics of a 858 Danenberg et al Expires November 2002 17 859 CEP VC. They are grouped here to ease NMS burden. 860 Once an entry is created here it may be re-used 861 by many VCs." 863 INDEX { pwVcCepCfgTableIndex } 865 ::= { pwVcCepCfgTable 1 } 867 PwVcCepCfgEntry ::= SEQUENCE { 868 pwVcCepCfgTableIndex PwVcCepCfgIndex, 869 pwVcCepConfigError BITS, 871 pwVcCepCfgNormalPktLength Unsigned32, 872 pwVcCepCfgMinPktLength Unsigned32, 873 pwVcCepCfgPktReorder TruthValue, 874 pwVcCepCfgEnableDBA BITS, 876 pwVcCepCfgJtrBfrDepth Unsigned32, 877 pwVcCepCfgJtrBfrRebuildOor TruthValue, 878 pwVcCepCfgJtrBfrRebuildOorCount Unsigned32, 880 pwVcCepCfgConsecPktsInsync Unsigned32, 881 pwVcCepCfgConsecMissingOutSync Unsigned32, 883 pwVcCepCfgPktErrorPlayOutValue Unsigned32, 885 pwVcCepCfgMissingPktsToSes Unsigned32, 886 pwVcCepCfgSesToUas Unsigned32, 887 pwVcCepCfgSecsToExitUas Unsigned32, 889 pwVcCepCfgRowStatus RowStatus, 890 pwVcCepCfgStorageType StorageType 891 } 893 pwVcCepCfgTableIndex OBJECT-TYPE 894 SYNTAX PwVcCepCfgIndex 895 MAX-ACCESS not-accessible 896 STATUS current 897 DESCRIPTION 898 "Primary index to this table" 899 ::= { pwVcCepCfgEntry 1 } 901 pwVcCepConfigError OBJECT-TYPE 902 SYNTAX BITS { 903 other ( 0), 904 dba ( 1), 905 lopsPktCount ( 2), 906 pktLength ( 3), 907 jtrBfrDepth ( 4) 908 } 909 MAX-ACCESS read-only 910 STATUS current 911 DESCRIPTION 912 "Various configurations errors. Illegal settings within 914 Danenberg et al Expires November 2002 18 915 the pwVcCepCfg or pwVcCepSonetExt tables." 916 ::= { pwVcCepCfgEntry 2 } 918 pwVcCepCfgNormalPktLength OBJECT-TYPE 919 SYNTAX Unsigned32 920 MAX-ACCESS read-create 921 STATUS current 922 DESCRIPTION 923 "This is the CEP packet length in number of bytes 924 (including CEP header and payload) used when the 925 packet is NOT a DBA packet. This length applies to 926 inbound and outbound packets carrying user payload. 927 Although there is no control over inbound packets, 928 those of illegal length are discarded and accounted 929 for (see pwVcCepPerf...PktsBadLength.) 931 Note: DBA packets have their own (shorter) length 932 and are not effected by this setting. If CEP payload 933 compression were supported (future), compressed packets 934 would have their own (shorter) length and also not 935 effected by this setting. " 936 REFERENCE 937 "See FEC element format and Interfaces Parameters format 938 in Martini. L, et al, . For use of payload bytes see Malis, A., et al, 940 ." 941 ::= { pwVcCepCfgEntry 3 } 943 pwVcCepCfgMinPktLength OBJECT-TYPE 944 SYNTAX Unsigned32 945 MAX-ACCESS read-create 946 STATUS current 947 DESCRIPTION 948 "This is the minimum CEP packet length in number of 949 bytes (including CEP header and payload). It applies 950 to CEP's bandwidth-savings packets. Currently DBA is 951 the only bandwidth-savings packet type (in the future, 952 CEP may support compression). Minimum packet length is 953 necessary in some systems or networks. 955 Setting Zero here indicates that there is no minimum 956 packet restriction." 958 REFERENCE 959 "See FEC element format and Interfaces Parameters format 960 in Martini. L, et al, . For use of payload bytes see Malis, A., et al, 962 ." 963 DEFVAL { 0 } 964 ::= { pwVcCepCfgEntry 4 } 966 pwVcCepCfgPktReorder OBJECT-TYPE 967 SYNTAX TruthValue 969 Danenberg et al Expires November 2002 19 970 MAX-ACCESS read-only 971 STATUS current 972 DESCRIPTION 973 "If set True: as inbound packets are queued in the 974 jitter buffer, out of order packets are re-ordeed. The 975 maximum sequence number differential (i.e., the range in 976 which resequencing can occur) is dependant on the depth 977 of the jitter buffer. See pwVcCepCfgJtrBfrDepth. 979 NOTE: Some implementations may not support this feature. 980 The agent is then required to set this False." 981 ::= { pwVcCepCfgEntry 5 } 983 pwVcCepCfgEnableDBA OBJECT-TYPE 984 SYNTAX BITS { 985 ais (0), 986 unequipped (1) 987 } 988 MAX-ACCESS read-create 989 STATUS current 990 DESCRIPTION 991 "Bits set here MUST enable the DBA (dynamic bandwidth 992 allocation) feature for the specified condition. Setting 993 'ais' MUST cause CEP packet payload suppression 994 when AIS is detected on the associated SONET path. 995 Similarly, 'unequipped' MUST cause payload suppression 996 when an un-equipped condition is detected on the SONET 997 path. During these conditions, CEP packets will continue 998 to be sent, but with indicators set in the CEP header 999 instructing the remote to play all ones (for AIS) or all 1000 zeros (for un-equipped) onto its SONET path. 1002 NOTE: Some implementations may not support this feature. 1003 In these cases, if the 'ais' or 'unequipped' bits are set, 1004 then 'dba' error code MUST be set in pwVcCepConfigError." 1005 REFERENCE 1006 "See Malis, A., et al, ." 1007 DEFVAL { { unequipped } } 1008 ::= { pwVcCepCfgEntry 6 } 1010 pwVcCepCfgJtrBfrDepth OBJECT-TYPE 1011 SYNTAX Unsigned32 1012 UNITS "micro-seconds" 1013 MAX-ACCESS read-create 1014 STATUS current 1015 DESCRIPTION 1016 "This setting configures the number of microseconds 1017 of expected packet delay variation for this CEP VC 1018 over the PSN. 1020 The actual jitter buffer MUST be at least twice this 1021 value for proper operation, and is implementation 1022 specific. 1024 Danenberg et al Expires November 2002 20 1025 If configured to a value not supported by the 1026 implementation, the agent MUST return an error code 1027 'jtrBfrDepth' in 'pwVcCepConfigError ' 1029 NOTE: Like bandwidth and time-slots, jitter buffers 1030 are a limited resource to be managed." 1031 ::= { pwVcCepCfgEntry 7 } 1033 pwVcCepCfgJtrBfrRebuildOor OBJECT-TYPE 1034 SYNTAX TruthValue 1035 MAX-ACCESS read-create 1036 STATUS current 1037 DESCRIPTION 1038 "When set TRUE, the jitter buffer will rebuild when 1039 the RebuildOorCoutnt (consecutive out-of-range 1040 packet counter) has reached it's config'ed setting. 1041 If set FALSE, then the jitter buffer will continue 1042 to function regardless of out-of-range packets." 1043 DEFVAL { true } 1044 ::= { pwVcCepCfgEntry 8 } 1046 pwVcCepCfgJtrBfrRebuildOorCount OBJECT-TYPE 1047 SYNTAX Unsigned32 (0..255) 1048 MAX-ACCESS read-create 1049 STATUS current 1050 DESCRIPTION 1051 "Used by RebuildOor above. For every consecutive 1052 out-of-range packet received, a count is incremented. 1053 If it matches this value, the jitter bfr resets and 1054 rebuilds." 1055 DEFVAL { 3 } 1056 ::= { pwVcCepCfgEntry 9 } 1058 -- 1059 -- The following counters work together to integrate (filter) 1060 -- errors and the lack of errors on the CEP VC. An error is 1061 -- caused by a missing packet. Missing packet can be a result 1062 -- of: packet loss in the network, (uncorrectable) packet out 1063 -- of sequence, packet length error, jitter buffer overflow, 1064 -- and jitter buffer underflow. The result is declaring whether 1065 -- or not the CEP VC is in Loss of Packet Sync (LOPS) state. 1066 -- 1067 pwVcCepCfgConsecPktsInsync OBJECT-TYPE 1068 SYNTAX Unsigned32 1069 MAX-ACCESS read-create 1070 STATUS current 1071 DESCRIPTION "Consecutive pkts with sequential sequence 1072 numbers required to exit the LOPS state." 1073 REFERENCE 1074 "See Malis, A., et al, ." 1075 DEFVAL { 2 } 1076 ::= { pwVcCepCfgEntry 10 } 1078 Danenberg et al Expires November 2002 21 1079 pwVcCepCfgConsecMissingOutSync OBJECT-TYPE 1080 SYNTAX Unsigned32 1081 MAX-ACCESS read-create 1082 STATUS current 1083 DESCRIPTION "Consecutive missing pkts required to enter 1084 the LOPS state." 1085 REFERENCE 1086 "See Malis, A., et al, ." 1087 DEFVAL { 10 } 1088 ::= { pwVcCepCfgEntry 11 } 1090 pwVcCepCfgPktErrorPlayOutValue OBJECT-TYPE 1091 SYNTAX Unsigned32 (0..255) 1092 MAX-ACCESS read-create 1093 STATUS current 1094 DESCRIPTION 1095 "This is the value played when inbound packets have 1096 over/underflowed the jitter buffer, or are missing 1097 for any reason. This byte pattern is sent (played) on 1098 the SONET path." 1099 DEFVAL { 255 } -- Play all ones 1100 ::= { pwVcCepCfgEntry 12 } 1102 pwVcCepCfgMissingPktsToSes OBJECT-TYPE 1103 SYNTAX Unsigned32 1104 UNITS "seconds" 1105 MAX-ACCESS read-create 1106 STATUS current 1107 DESCRIPTION 1108 "Number of missing packets detected (consecutive or not) 1109 within a 1 second window to cause a Severely Errored 1110 Second (SES) to be counted." 1111 DEFVAL { 3 } 1112 ::= { pwVcCepCfgEntry 13 } 1114 pwVcCepCfgSesToUas OBJECT-TYPE 1115 SYNTAX Unsigned32 1116 UNITS "seconds" 1117 MAX-ACCESS read-create 1118 STATUS current 1119 DESCRIPTION 1120 "Number of consecutive SESs before declaring VC in UAS 1121 state (and at which point pwVcCepPerfUASs starts counting). 1122 The SesToUas default value is 10 seconds. 1124 NOTE: Similar to RFC 2558, If the agent chooses to update 1125 the various performance statistics in real time then it must 1126 be prepared to retroactively reduce the ES, SES, counts by 1127 this value and increase the UAS count by this value when it 1128 determines that UAS state has been entered. 1130 NOTE: See pwVcCepPerfSESs and pwVcCepPerfUASs." 1131 DEFVAL { 10 } 1133 Danenberg et al Expires November 2002 22 1134 ::= { pwVcCepCfgEntry 14 } 1136 pwVcCepCfgSecsToExitUas OBJECT-TYPE 1137 SYNTAX Unsigned32 1138 UNITS "seconds" 1139 MAX-ACCESS read-create 1140 STATUS current 1141 DESCRIPTION 1142 "Number of consecutive nonSESs before declaring VC is NOT 1143 in UAS state (and at which point pwVcCepPerfUASs stops 1144 counting)." 1145 DEFVAL { 10 } 1146 ::= { pwVcCepCfgEntry 15 } 1148 pwVcCepCfgRowStatus OBJECT-TYPE 1149 SYNTAX RowStatus 1150 MAX-ACCESS read-create 1151 STATUS current 1152 DESCRIPTION 1153 "For creating, modifying, and deleting this row." 1154 ::= { pwVcCepCfgEntry 16 } 1156 pwVcCepCfgStorageType OBJECT-TYPE 1157 SYNTAX StorageType 1158 MAX-ACCESS read-create 1159 STATUS current 1160 DESCRIPTION 1161 "This variable indicates the storage type for this 1162 object." 1163 ::= { pwVcCepCfgEntry 17 } 1165 -- End of PW CEP VC Configuration Parameter Table 1167 -- CEP VC Performance Current Interval Table. 1169 pwVcCepPerfCurrentTable OBJECT-TYPE 1170 SYNTAX SEQUENCE OF PwVcCepPerfCurrentEntry 1171 MAX-ACCESS not-accessible 1172 STATUS current 1173 DESCRIPTION 1174 "CEP bridges the SONET and packet worlds. In the packet 1175 world, counts typically start from the time of service 1176 creation - and don't stop. In the SONET world, counts are 1177 kept in 15 minute intervals. The CEP-MIB supports both 1178 methods. The current 15 minute interval counts are in 1179 this table. The interval and total stats are in tables 1180 following this. 1182 This table provides per CEP VC performance information. 1183 HC (high capacity) counters are required for some counts 1184 due to the high speeds expected with CEP services. A SONET 1185 path of width 48 (STS-48c) can rollover non-HC counters in 1186 a few minutes." 1188 Danenberg et al Expires November 2002 23 1189 ::= { pwVcCepObjects 4 } 1191 pwVcCepPerfCurrentEntry OBJECT-TYPE 1192 SYNTAX PwVcCepPerfCurrentEntry 1193 MAX-ACCESS not-accessible 1194 STATUS current 1195 DESCRIPTION 1196 "An entry in this table is created by the agent for every 1197 pwVcCep entry. After 15 minutes, the contents of this table 1198 entry are copied to a new entry in the pwVcCepPerfInterval 1199 table and the counts in this entry are reset to zero." 1201 INDEX { pwVcIndex } 1203 ::= { pwVcCepPerfCurrentTable 1 } 1205 PwVcCepPerfCurrentEntry ::= SEQUENCE { 1206 pwVcCepPerfCurrentDbaInPacketsHC Counter64, 1207 pwVcCepPerfCurrentDbaOutPacketsHC Counter64, 1209 pwVcCepPerfCurrentInNegPtrAdjust Counter32, 1210 pwVcCepPerfCurrentInPosPtrAdjust Counter32, 1211 pwVcCepPerfCurrentInPtrAdjustSecs Counter32, 1212 pwVcCepPerfCurrentOutNegPtrAdjust Counter32, 1213 pwVcCepPerfCurrentOutPosPtrAdjust Counter32, 1214 pwVcCepPerfCurrentOutPtrAdjustSecs Counter32, 1215 pwVcCepPerfCurrentAbsPtrAdjust Integer32, 1217 pwVcCepPerfCurrentMissingPkts Counter32, 1218 pwVcCepPerfCurrentPktsOoseq Counter32, 1219 pwVcCepPerfCurrentPktsOoRngDropped Counter32, 1220 pwVcCepPerfCurrentJtrBfrUnderruns Counter32, 1221 pwVcCepPerfCurrentPktsBadLength Counter32, 1222 pwVcCepPerfCurrentSummaryErrors Counter32, 1224 pwVcCepPerfCurrentESs PerfCurrentCount, 1225 pwVcCepPerfCurrentSESs PerfCurrentCount, 1226 pwVcCepPerfCurrentUASs PerfCurrentCount, 1227 pwVcCepPerfCurrentFC PerfCurrentCount 1228 } 1230 pwVcCepPerfCurrentDbaInPacketsHC OBJECT-TYPE 1231 SYNTAX Counter64 1232 MAX-ACCESS read-only 1233 STATUS current 1234 DESCRIPTION 1235 "Number of DBA packets received." 1236 ::= { pwVcCepPerfCurrentEntry 1 } 1238 pwVcCepPerfCurrentDbaOutPacketsHC OBJECT-TYPE 1239 SYNTAX Counter64 1240 MAX-ACCESS read-only 1241 STATUS current 1242 DESCRIPTION 1244 Danenberg et al Expires November 2002 24 1245 "Number of DBA packets sent." 1246 ::= { pwVcCepPerfCurrentEntry 2 } 1248 -- Pointer adjustment stats 1249 pwVcCepPerfCurrentInNegPtrAdjust OBJECT-TYPE 1250 SYNTAX Counter32 1251 MAX-ACCESS read-only 1252 STATUS current 1253 DESCRIPTION 1254 "Number of negative pointer adjustments sent on the 1255 SONET path based on CEP pointer adjustments received." 1256 ::= { pwVcCepPerfCurrentEntry 3 } 1258 pwVcCepPerfCurrentInPosPtrAdjust OBJECT-TYPE 1259 SYNTAX Counter32 1260 MAX-ACCESS read-only 1261 STATUS current 1262 DESCRIPTION 1263 "Number of postive pointer adjustments sent on the 1264 SONET path based on CEP pointer adjustments received." 1265 ::= { pwVcCepPerfCurrentEntry 4 } 1267 pwVcCepPerfCurrentInPtrAdjustSecs OBJECT-TYPE 1268 SYNTAX Counter32 1269 MAX-ACCESS read-only 1270 STATUS current 1271 DESCRIPTION 1272 "Number of seconds in which a pos or neg pointer 1273 adjustment was sent on the SONET path." 1274 ::= { pwVcCepPerfCurrentEntry 5 } 1276 pwVcCepPerfCurrentOutNegPtrAdjust OBJECT-TYPE 1277 SYNTAX Counter32 1278 MAX-ACCESS read-only 1279 STATUS current 1280 DESCRIPTION 1281 "Number of negative pointer adjustments seen on the 1282 SONET path and encoded onto sent CEP packets." 1283 ::= { pwVcCepPerfCurrentEntry 6 } 1285 pwVcCepPerfCurrentOutPosPtrAdjust OBJECT-TYPE 1286 SYNTAX Counter32 1287 MAX-ACCESS read-only 1288 STATUS current 1289 DESCRIPTION 1290 "Number of positive pointer adjustments seen on the 1291 SONET path and encoded onto sent CEP packets." 1292 ::= { pwVcCepPerfCurrentEntry 7 } 1294 pwVcCepPerfCurrentOutPtrAdjustSecs OBJECT-TYPE 1295 SYNTAX Counter32 1296 MAX-ACCESS read-only 1297 STATUS current 1299 Danenberg et al Expires November 2002 25 1300 DESCRIPTION 1301 "Number of seconds in which a pos or neg pointer 1302 adjustment was seen on the SONET path." 1303 ::= { pwVcCepPerfCurrentEntry 8 } 1305 pwVcCepPerfCurrentAbsPtrAdjust OBJECT-TYPE 1306 SYNTAX Integer32 1307 MAX-ACCESS read-only 1308 STATUS current 1309 DESCRIPTION 1310 "Absolute Pointer adjustments is relative adjustment 1311 drifts between inbound and outbound streams. It is 1312 calculated as absolute value of : 1313 ( InPosPtrAdjust - InNegPtrAdjust) - 1314 (OutPosPtrAdjust - OutNegPtrAdjust) " 1315 ::= { pwVcCepPerfCurrentEntry 9 } 1317 pwVcCepPerfCurrentMissingPkts OBJECT-TYPE 1318 SYNTAX Counter32 1319 MAX-ACCESS read-only 1320 STATUS current 1321 DESCRIPTION 1322 "Number of missing packets (as detected via CEP header 1323 sequence number gaps)." 1324 ::= { pwVcCepPerfCurrentEntry 10 } 1326 pwVcCepPerfCurrentPktsOoseq OBJECT-TYPE 1327 SYNTAX Counter32 1328 MAX-ACCESS read-only 1329 STATUS current 1330 DESCRIPTION 1331 "Number of packets detected out of sequence (via CEP 1332 header sequence numbers), but successfully re-ordered. 1333 Note: some implementations may not support this 1334 feature (see pwVcCepCfgPktReorder)." 1335 ::= { pwVcCepPerfCurrentEntry 11 } 1337 pwVcCepPerfCurrentPktsOoRngDropped OBJECT-TYPE 1338 SYNTAX Counter32 1339 MAX-ACCESS read-only 1340 STATUS current 1341 DESCRIPTION 1342 "Number of packets detected out of range (via CEP 1343 header sequence numbers), and could not be re- 1344 ordered, or could not fit in the jitter buffer." 1345 ::= { pwVcCepPerfCurrentEntry 12 } 1347 pwVcCepPerfCurrentJtrBfrUnderruns OBJECT-TYPE 1348 SYNTAX Counter32 1349 MAX-ACCESS read-only 1350 STATUS current 1351 DESCRIPTION 1352 "Number of times a packet needed to be played 1353 out and the jitter buffer was empty." 1355 Danenberg et al Expires November 2002 26 1356 ::= { pwVcCepPerfCurrentEntry 13 } 1358 pwVcCepPerfCurrentPktsBadLength OBJECT-TYPE 1359 SYNTAX Counter32 1360 MAX-ACCESS read-only 1361 STATUS current 1362 DESCRIPTION 1363 "Number of normal (non-bandwidth-saving packets received) 1364 larger or smaller than pwVcCepCfgNormalPktLength." 1365 ::= { pwVcCepPerfCurrentEntry 14 } 1367 pwVcCepPerfCurrentSummaryErrors OBJECT-TYPE 1368 SYNTAX Counter32 1369 MAX-ACCESS read-only 1370 STATUS current 1371 DESCRIPTION 1372 "A summary of all the packet error types above (from 1373 missing packets to bad length packets)." 1374 ::= { pwVcCepPerfCurrentEntry 15 } 1376 pwVcCepPerfCurrentESs OBJECT-TYPE 1377 SYNTAX PerfCurrentCount 1378 MAX-ACCESS read-only 1379 STATUS current 1380 DESCRIPTION 1381 "The counter associated with the number of Errored 1382 Seconds encountered." 1383 ::= { pwVcCepPerfCurrentEntry 16 } 1385 pwVcCepPerfCurrentSESs OBJECT-TYPE 1386 SYNTAX PerfCurrentCount 1387 MAX-ACCESS read-only 1388 STATUS current 1389 DESCRIPTION 1390 "The counter associated with the number of 1391 Severely Errored Seconds encountered." 1392 ::= { pwVcCepPerfCurrentEntry 17 } 1394 pwVcCepPerfCurrentUASs OBJECT-TYPE 1395 SYNTAX PerfCurrentCount 1396 MAX-ACCESS read-only 1397 STATUS current 1398 DESCRIPTION 1399 "The counter associated with the number of 1400 Unavailable Seconds encountered." 1401 ::= { pwVcCepPerfCurrentEntry 18 } 1403 pwVcCepPerfCurrentFC OBJECT-TYPE 1404 SYNTAX PerfCurrentCount 1405 MAX-ACCESS read-only 1406 STATUS current 1407 DESCRIPTION 1408 "CEP Failure Counts (FC-CEP). The number of CEP failure 1409 events. A failure event begins when the LOPS failure 1411 Danenberg et al Expires November 2002 27 1412 is declared, and ends when the failure is cleared. A 1413 failure event that begins in one period and ends in 1414 another period is counted only in the period in which 1415 it begins." 1416 ::= { pwVcCepPerfCurrentEntry 19 } 1418 -- End PW CEP VC Performance Current Interval Table 1420 -- PW CEP VC Performance Interval Table. 1422 pwVcCepPerfIntervalTable OBJECT-TYPE 1423 SYNTAX SEQUENCE OF PwVcCepPerfIntervalEntry 1424 MAX-ACCESS not-accessible 1425 STATUS current 1426 DESCRIPTION 1427 "This table provides per CEP VC performance information 1428 much like the pwVcCepPerfCurrentTable above. However, 1429 these counts represent historical 15 minute intervals. 1430 Typically, this table will have a maximum of 96 entries 1431 for a 24 hour period, but is not limited to this. 1432 NOTE: Counter64 objects are used here, Counter32 is 1433 too small for OC-768 CEP VCs." 1434 ::= { pwVcCepObjects 5 } 1436 pwVcCepPerfIntervalEntry OBJECT-TYPE 1437 SYNTAX PwVcCepPerfIntervalEntry 1438 MAX-ACCESS not-accessible 1439 STATUS current 1440 DESCRIPTION 1441 "An entry in this table is created by the agent for 1442 every pwVcCepPerfCurrentEntry that is 15 minutes old. 1443 The contents of the Current entry are copied to the new 1444 entry here. The Current entry, then resets its counts 1445 to zero for the next current 15 minute interval. 1446 pwVcCepIndex is found in the pwVcCepCfg table." 1448 INDEX { pwVcIndex, pwVcCepPerfIntervalNumber } 1450 ::= { pwVcCepPerfIntervalTable 1 } 1452 PwVcCepPerfIntervalEntry ::= SEQUENCE { 1453 pwVcCepPerfIntervalNumber Unsigned32, 1454 pwVcCepPerfIntervalValidData TruthValue, 1455 pwVcCepPerfIntervalReset INTEGER, 1456 pwVcCepPerfIntervalTimeElapsed Integer32, 1458 pwVcCepPerfIntervalDbaInPacketsHC Counter64, 1459 pwVcCepPerfIntervalDbaOutPacketsHC Counter64, 1461 pwVcCepPerfIntervalInNegPtrAdjust Counter32, 1462 pwVcCepPerfIntervalInPosPtrAdjust Counter32, 1463 pwVcCepPerfIntervalInPtrAdjustSecs Counter32, 1464 pwVcCepPerfIntervalOutNegPtrAdjust Counter32, 1466 Danenberg et al Expires November 2002 28 1467 pwVcCepPerfIntervalOutPosPtrAdjust Counter32, 1468 pwVcCepPerfIntervalOutPtrAdjustSecs Counter32, 1469 pwVcCepPerfIntervalAbsPtrAdjust Integer32, 1471 pwVcCepPerfIntervalMissingPkts Counter32, 1472 pwVcCepPerfIntervalPktsOoseq Counter32, 1473 pwVcCepPerfIntervalPktsOoRngDropped Counter32, 1474 pwVcCepPerfIntervalJtrBfrUnderruns Counter32, 1475 pwVcCepPerfIntervalPktsBadLength Counter32, 1476 pwVcCepPerfIntervalSummaryErrors Counter32, 1478 pwVcCepPerfIntervalESs PerfIntervalCount, 1479 pwVcCepPerfIntervalSESs PerfIntervalCount, 1480 pwVcCepPerfIntervalUASs PerfIntervalCount, 1481 pwVcCepPerfIntervalFC PerfIntervalCount 1482 } 1484 pwVcCepPerfIntervalNumber OBJECT-TYPE 1485 SYNTAX Unsigned32 1486 MAX-ACCESS not-accessible 1487 STATUS current 1488 DESCRIPTION 1489 "A number (normally between 1 and 96 to cover a 24 hour 1490 period) which identifies the interval for which the set 1491 of statistics is available. The interval identified by 1 1492 is the most recently completed 15 minute interval, and 1493 the interval identified by N is the interval immediately 1494 preceding the one identified by N-1. The minimum range of 1495 N is 1 through 4. The default range is 1 through 32. The 1496 maximum value of N is 1 through 96." 1497 ::= { pwVcCepPerfIntervalEntry 1 } 1499 pwVcCepPerfIntervalValidData OBJECT-TYPE 1500 SYNTAX TruthValue 1501 MAX-ACCESS read-only 1502 STATUS current 1503 DESCRIPTION 1504 "This variable indicates if the data for this interval 1505 is valid." 1506 ::= { pwVcCepPerfIntervalEntry 2 } 1508 pwVcCepPerfIntervalReset OBJECT-TYPE 1509 SYNTAX INTEGER { 1510 reset (1), 1511 normal(2) 1512 } 1513 MAX-ACCESS read-create 1514 STATUS current 1515 DESCRIPTION 1516 "Used in cases where the user knows that the errors 1517 within this interval should not be counted. Writing 1518 'reset' sets all error counts to zero." 1519 ::= { pwVcCepPerfIntervalEntry 3 } 1521 Danenberg et al Expires November 2002 29 1522 pwVcCepPerfIntervalTimeElapsed OBJECT-TYPE 1523 SYNTAX Integer32 1524 MAX-ACCESS read-only 1525 STATUS current 1526 DESCRIPTION 1527 "The duration of a particular interval in seconds, 1528 Adjustments in the system's time-of-day clock, may 1529 cause the interval to be greater or less than, the 1530 normal value. Therefore this actual interval value 1531 is provided." 1532 ::= { pwVcCepPerfIntervalEntry 4 } 1534 pwVcCepPerfIntervalDbaInPacketsHC OBJECT-TYPE 1535 SYNTAX Counter64 1536 MAX-ACCESS read-only 1537 STATUS current 1538 DESCRIPTION 1539 "Number of DBA packets received." 1540 ::= { pwVcCepPerfIntervalEntry 5 } 1542 pwVcCepPerfIntervalDbaOutPacketsHC OBJECT-TYPE 1543 SYNTAX Counter64 1544 MAX-ACCESS read-only 1545 STATUS current 1546 DESCRIPTION 1547 "Number of DBA packets sent." 1548 ::= { pwVcCepPerfIntervalEntry 6 } 1550 -- Pointer adjustment stats 1551 pwVcCepPerfIntervalInNegPtrAdjust OBJECT-TYPE 1552 SYNTAX Counter32 1553 MAX-ACCESS read-only 1554 STATUS current 1555 DESCRIPTION 1556 "Number of negative pointer adjustments sent on the 1557 SONET path based on CEP pointer adjustments received." 1558 ::= { pwVcCepPerfIntervalEntry 7 } 1560 pwVcCepPerfIntervalInPosPtrAdjust OBJECT-TYPE 1561 SYNTAX Counter32 1562 MAX-ACCESS read-only 1563 STATUS current 1564 DESCRIPTION 1565 "Number of postive pointer adjustments sent on the 1566 SONET path based on CEP pointer adjustments received." 1567 ::= { pwVcCepPerfIntervalEntry 8 } 1569 pwVcCepPerfIntervalInPtrAdjustSecs OBJECT-TYPE 1570 SYNTAX Counter32 1571 MAX-ACCESS read-only 1572 STATUS current 1573 DESCRIPTION 1574 "Number of seconds in which a pos or neg pointer 1576 Danenberg et al Expires November 2002 30 1577 adjustment was sent on the SONET path." 1578 ::= { pwVcCepPerfIntervalEntry 9 } 1580 pwVcCepPerfIntervalOutNegPtrAdjust OBJECT-TYPE 1581 SYNTAX Counter32 1582 MAX-ACCESS read-only 1583 STATUS current 1584 DESCRIPTION 1585 "Number of negative pointer adjustments seen on the 1586 SONET path and encoded onto sent CEP packets." 1587 ::= { pwVcCepPerfIntervalEntry 10 } 1589 pwVcCepPerfIntervalOutPosPtrAdjust OBJECT-TYPE 1590 SYNTAX Counter32 1591 MAX-ACCESS read-only 1592 STATUS current 1593 DESCRIPTION 1594 "Number of positive pointer adjustments seen on the 1595 SONET path and encoded onto sent CEP packets." 1596 ::= { pwVcCepPerfIntervalEntry 11 } 1598 pwVcCepPerfIntervalOutPtrAdjustSecs OBJECT-TYPE 1599 SYNTAX Counter32 1600 MAX-ACCESS read-only 1601 STATUS current 1602 DESCRIPTION 1603 "Number of seconds in which a pos or neg pointer 1604 adjustment was seen on the SONET path." 1605 ::= { pwVcCepPerfIntervalEntry 12 } 1607 pwVcCepPerfIntervalAbsPtrAdjust OBJECT-TYPE 1608 SYNTAX Integer32 1609 MAX-ACCESS read-only 1610 STATUS current 1611 DESCRIPTION 1612 "Absolute Pointer adjustments is relative adjustment 1613 drifts between inbound and outbound streams. It is 1614 calculated as absolute value of : 1615 ( InPosPtrAdjust - InNegPtrAdjust) - 1616 (OutPosPtrAdjust - OutNegPtrAdjust) " 1617 ::= { pwVcCepPerfIntervalEntry 13 } 1619 pwVcCepPerfIntervalMissingPkts OBJECT-TYPE 1620 SYNTAX Counter32 1621 MAX-ACCESS read-only 1622 STATUS current 1623 DESCRIPTION 1624 "Number of missing packets (as detected via CEP header 1625 sequence number gaps)." 1626 ::= { pwVcCepPerfIntervalEntry 14 } 1628 pwVcCepPerfIntervalPktsOoseq OBJECT-TYPE 1629 SYNTAX Counter32 1630 MAX-ACCESS read-only 1632 Danenberg et al Expires November 2002 31 1633 STATUS current 1634 DESCRIPTION 1635 "Number of packets detected out of sequence (via CEP 1636 header sequence numbers), but succesfully re-ordered. 1637 Note: some implementations mat not support this 1638 feature (see pwVcCepCfgPktReorder)." 1639 ::= { pwVcCepPerfIntervalEntry 15 } 1641 pwVcCepPerfIntervalPktsOoRngDropped OBJECT-TYPE 1642 SYNTAX Counter32 1643 MAX-ACCESS read-only 1644 STATUS current 1645 DESCRIPTION 1646 "Number of packets detected out of range (via CEP 1647 header sequence numbers), and could not be re- 1648 ordered, or could not fit in the jitter buffer." 1649 ::= { pwVcCepPerfIntervalEntry 16 } 1651 pwVcCepPerfIntervalJtrBfrUnderruns OBJECT-TYPE 1652 SYNTAX Counter32 1653 MAX-ACCESS read-only 1654 STATUS current 1655 DESCRIPTION 1656 "Number of times a packet needed to be played 1657 out and the jitter buffer was empty." 1658 ::= { pwVcCepPerfIntervalEntry 17 } 1660 pwVcCepPerfIntervalPktsBadLength OBJECT-TYPE 1661 SYNTAX Counter32 1662 MAX-ACCESS read-only 1663 STATUS current 1664 DESCRIPTION 1665 "Number of packets received larger or smaller than 1666 pwVcCepCfgNormalPktLength." 1667 ::= { pwVcCepPerfIntervalEntry 18 } 1669 pwVcCepPerfIntervalSummaryErrors OBJECT-TYPE 1670 SYNTAX Counter32 1671 MAX-ACCESS read-only 1672 STATUS current 1673 DESCRIPTION 1674 "A summary of all the packet error types above (from 1675 missing packets to bad length packets)." 1676 ::= { pwVcCepPerfIntervalEntry 19 } 1678 pwVcCepPerfIntervalESs OBJECT-TYPE 1679 SYNTAX PerfIntervalCount 1680 MAX-ACCESS read-only 1681 STATUS current 1682 DESCRIPTION 1683 "The counter associated with the number of Errored 1684 Seconds encountered." 1685 ::= { pwVcCepPerfIntervalEntry 20 } 1687 Danenberg et al Expires November 2002 32 1688 pwVcCepPerfIntervalSESs OBJECT-TYPE 1689 SYNTAX PerfIntervalCount 1690 MAX-ACCESS read-only 1691 STATUS current 1692 DESCRIPTION 1693 "The counter associated with the number of 1694 Severely Errored Seconds encountered." 1695 ::= { pwVcCepPerfIntervalEntry 21 } 1697 pwVcCepPerfIntervalUASs OBJECT-TYPE 1698 SYNTAX PerfIntervalCount 1699 MAX-ACCESS read-only 1700 STATUS current 1701 DESCRIPTION 1702 "The counter associated with the number of 1703 Unavailable Seconds encountered." 1704 ::= { pwVcCepPerfIntervalEntry 22 } 1706 pwVcCepPerfIntervalFC OBJECT-TYPE 1707 SYNTAX PerfIntervalCount 1708 MAX-ACCESS read-only 1709 STATUS current 1710 DESCRIPTION 1711 "CEP Failure Counts (FC-CEP). The number of CEP failure 1712 events. A failure event begins when the LOPS failure 1713 is declared, and ends when the failure is cleared. A 1714 failure event that begins in one period and ends in 1715 another period is counted only in the period in which 1716 it begins." 1717 ::= { pwVcCepPerfIntervalEntry 23 } 1719 -- End PW CEP VC Performance Interval Table 1721 -- PW CEP VC Total Performance Table 1723 pwVcCepPerfTotalTable OBJECT-TYPE 1724 SYNTAX SEQUENCE OF PwVcCepPerfTotalEntry 1725 MAX-ACCESS not-accessible 1726 STATUS current 1727 DESCRIPTION 1728 "This table provides per CEP VC performance information 1729 much like the pwVcCepPerfIntervalTable above. However, 1730 these counts represent complete historical information. 1731 NOTE: Counter64 objects are used here, Counter32 is 1732 too small for OC-768 CEP VCs." 1733 ::= { pwVcCepObjects 6 } 1735 pwVcCepPerfTotalEntry OBJECT-TYPE 1736 SYNTAX PwVcCepPerfTotalEntry 1737 MAX-ACCESS not-accessible 1738 STATUS current 1739 DESCRIPTION 1740 "An entry is created in this table by the agent for 1742 Danenberg et al Expires November 2002 33 1743 every entry in the pwVcCep table." 1745 INDEX { pwVcIndex } 1747 ::= { pwVcCepPerfTotalTable 1 } 1749 PwVcCepPerfTotalEntry ::= SEQUENCE { 1751 pwVcCepPerfTotalDbaInPacketsHC Counter64, 1752 pwVcCepPerfTotalDbaOutPacketsHC Counter64, 1754 pwVcCepPerfTotalInNegPtrAdjust Counter32, 1755 pwVcCepPerfTotalInPosPtrAdjust Counter32, 1756 pwVcCepPerfTotalInPtrAdjustSecs Counter32, 1757 pwVcCepPerfTotalOutNegPtrAdjust Counter32, 1758 pwVcCepPerfTotalOutPosPtrAdjust Counter32, 1759 pwVcCepPerfTotalOutPtrAdjustSecs Counter32, 1760 pwVcCepPerfTotalAbsPtrAdjust Integer32, 1762 pwVcCepPerfTotalMissingPkts Counter32, 1763 pwVcCepPerfTotalPktsOoseq Counter32, 1764 pwVcCepPerfTotalPktsOoRngDropped Counter32, 1765 pwVcCepPerfTotalJtrBfrUnderruns Counter32, 1766 pwVcCepPerfTotalPktsBadLength Counter32, 1767 pwVcCepPerfTotalSummaryErrors Counter32, 1769 pwVcCepPerfTotalESs Counter32, 1770 pwVcCepPerfTotalSESs Counter32, 1771 pwVcCepPerfTotalUASs Counter32, 1772 pwVcCepPerfTotalFC Counter32, 1773 pwVcCepPerfTotalDiscontinuityTime TimeStamp 1774 } 1776 pwVcCepPerfTotalDbaInPacketsHC OBJECT-TYPE 1777 SYNTAX Counter64 1778 MAX-ACCESS read-only 1779 STATUS current 1780 DESCRIPTION 1781 "Number of DBA packets received." 1782 ::= { pwVcCepPerfTotalEntry 1 } 1784 pwVcCepPerfTotalDbaOutPacketsHC OBJECT-TYPE 1785 SYNTAX Counter64 1786 MAX-ACCESS read-only 1787 STATUS current 1788 DESCRIPTION 1789 "Number of DBA packets sent." 1790 ::= { pwVcCepPerfTotalEntry 2 } 1792 -- Pointer adjustment stats 1793 pwVcCepPerfTotalInNegPtrAdjust OBJECT-TYPE 1794 SYNTAX Counter32 1795 MAX-ACCESS read-only 1797 Danenberg et al Expires November 2002 34 1798 STATUS current 1799 DESCRIPTION 1800 "Number of negative pointer adjustments sent on the 1801 SONET path based on CEP pointer adjustments received." 1802 ::= { pwVcCepPerfTotalEntry 3 } 1804 pwVcCepPerfTotalInPosPtrAdjust OBJECT-TYPE 1805 SYNTAX Counter32 1806 MAX-ACCESS read-only 1807 STATUS current 1808 DESCRIPTION 1809 "Number of postive pointer adjustments sent on the 1810 SONET path based on CEP pointer adjustments received." 1811 ::= { pwVcCepPerfTotalEntry 4 } 1813 pwVcCepPerfTotalInPtrAdjustSecs OBJECT-TYPE 1814 SYNTAX Counter32 1815 MAX-ACCESS read-only 1816 STATUS current 1817 DESCRIPTION 1818 "Number of seconds in which a pos or neg pointer 1819 adjustment was sent on the SONET path." 1820 ::= { pwVcCepPerfTotalEntry 5 } 1822 pwVcCepPerfTotalOutNegPtrAdjust OBJECT-TYPE 1823 SYNTAX Counter32 1824 MAX-ACCESS read-only 1825 STATUS current 1826 DESCRIPTION 1827 "Number of negative pointer adjustments seen on the 1828 SONET path and encoded onto sent CEP packets." 1829 ::= { pwVcCepPerfTotalEntry 6 } 1831 pwVcCepPerfTotalOutPosPtrAdjust OBJECT-TYPE 1832 SYNTAX Counter32 1833 MAX-ACCESS read-only 1834 STATUS current 1835 DESCRIPTION 1836 "Number of positive pointer adjustments seen on the 1837 SONET path and encoded onto sent CEP packets." 1838 ::= { pwVcCepPerfTotalEntry 7 } 1840 pwVcCepPerfTotalOutPtrAdjustSecs OBJECT-TYPE 1841 SYNTAX Counter32 1842 MAX-ACCESS read-only 1843 STATUS current 1844 DESCRIPTION 1845 "Number of seconds in which a pos or neg pointer 1846 adjustment was seen on the SONET path." 1847 ::= { pwVcCepPerfTotalEntry 8 } 1849 pwVcCepPerfTotalAbsPtrAdjust OBJECT-TYPE 1850 SYNTAX Integer32 1851 MAX-ACCESS read-only 1853 Danenberg et al Expires November 2002 35 1854 STATUS current 1855 DESCRIPTION 1856 "Absolute Pointer adjustments is relative adjustment 1857 drifts between inbound and outbound streams. It is 1858 calculated as absolute value of : 1859 ( InPosPtrAdjust - InNegPtrAdjust) - 1860 (OutPosPtrAdjust - OutNegPtrAdjust) " 1861 ::= { pwVcCepPerfTotalEntry 9 } 1863 pwVcCepPerfTotalMissingPkts OBJECT-TYPE 1864 SYNTAX Counter32 1865 MAX-ACCESS read-only 1866 STATUS current 1867 DESCRIPTION 1868 "Number of missing packets (as detected via CEP header 1869 sequence number gaps)." 1870 ::= { pwVcCepPerfTotalEntry 10 } 1872 pwVcCepPerfTotalPktsOoseq OBJECT-TYPE 1873 SYNTAX Counter32 1874 MAX-ACCESS read-only 1875 STATUS current 1876 DESCRIPTION 1877 "Number of packets detected out of sequence (via CEP 1878 header sequence numbers), but successfully re-ordered. 1879 Note: some implementations may not support this feature 1880 (see pwVcCepCfgPktReorder)." 1881 ::= { pwVcCepPerfTotalEntry 11 } 1883 pwVcCepPerfTotalPktsOoRngDropped OBJECT-TYPE 1884 SYNTAX Counter32 1885 MAX-ACCESS read-only 1886 STATUS current 1887 DESCRIPTION 1888 "Number of packets detected out of range (via CEP 1889 header sequence numbers), and could not be re- 1890 ordered, or could not fit in the jitter buffer." 1891 ::= { pwVcCepPerfTotalEntry 12 } 1893 pwVcCepPerfTotalJtrBfrUnderruns OBJECT-TYPE 1894 SYNTAX Counter32 1895 MAX-ACCESS read-only 1896 STATUS current 1897 DESCRIPTION 1898 "Number of times a packet needed to be played 1899 out and the jitter buffer was empty." 1900 ::= { pwVcCepPerfTotalEntry 13 } 1902 pwVcCepPerfTotalPktsBadLength OBJECT-TYPE 1903 SYNTAX Counter32 1904 MAX-ACCESS read-only 1905 STATUS current 1906 DESCRIPTION 1907 "Number of packets received larger or smaller than 1909 Danenberg et al Expires November 2002 36 1910 pwVcCepCfgNormalPktLength." 1911 ::= { pwVcCepPerfTotalEntry 14 } 1913 pwVcCepPerfTotalSummaryErrors OBJECT-TYPE 1914 SYNTAX Counter32 1915 MAX-ACCESS read-only 1916 STATUS current 1917 DESCRIPTION 1918 "A summary of all the packet error types above (from 1919 missing packets to bad length packets)." 1920 ::= { pwVcCepPerfTotalEntry 15 } 1922 pwVcCepPerfTotalESs OBJECT-TYPE 1923 SYNTAX Counter32 1924 MAX-ACCESS read-only 1925 STATUS current 1926 DESCRIPTION 1927 "The counter associated with the number of Errored 1928 Seconds encountered. See future versions of 1929 draft-malis-pwe3-sonet-02.txt for definition of ES." 1930 ::= { pwVcCepPerfTotalEntry 16 } 1932 pwVcCepPerfTotalSESs OBJECT-TYPE 1933 SYNTAX Counter32 1934 MAX-ACCESS read-only 1935 STATUS current 1936 DESCRIPTION 1937 "The counter associated with the number of Severely 1938 Errored Seconds. See pwVcCepCfgMissingPktsToSes. 1939 Also see future versions of draft-malis-pwe3-sonet 1940 for definition." 1941 ::= { pwVcCepPerfTotalEntry 17 } 1943 pwVcCepPerfTotalUASs OBJECT-TYPE 1944 SYNTAX Counter32 1945 MAX-ACCESS read-only 1946 STATUS current 1947 DESCRIPTION 1948 "The counter associated with the number of 1949 UnAvailable Seconds. See pwVcCepCfgSesToUAS. 1951 NOTE: When first entering the UAS state, the number 1952 of SesToUas is added to this object, then as each 1953 additional UAS occurs, this object increments by one. 1955 NOTE: Similar to RFC 2558, If the agent chooses to update 1956 the various performance statistics in real time then it must 1957 be prepared to retroactively reduce the ES, SES, counts (by 1958 the value of pwVcCepCfgSesToUas) and increase the UAS 1959 count (by that same value) when it determines that UAS 1960 state has been entered." 1961 ::= { pwVcCepPerfTotalEntry 18 } 1963 pwVcCepPerfTotalFC OBJECT-TYPE 1965 Danenberg et al Expires November 2002 37 1966 SYNTAX Counter32 1967 MAX-ACCESS read-only 1968 STATUS current 1969 DESCRIPTION 1970 "CEP Failure Counts (FC-CEP). The number of CEP failure 1971 events. A failure event begins when the LOPS failure 1972 is declared, and ends when the failure is cleared." 1973 ::= { pwVcCepPerfTotalEntry 19 } 1975 pwVcCepPerfTotalDiscontinuityTime OBJECT-TYPE 1976 SYNTAX TimeStamp 1977 MAX-ACCESS read-only 1978 STATUS current 1979 DESCRIPTION 1980 "The value of sysUpTime on the most recent occasion at 1981 which any one or more of this segment's Counter32 or 1982 Counter64 suffered a discontinuity. If no such 1983 discontinuities have occurred since the last re- 1984 initialization of the local management subsystem, then 1985 this object contains a zero value." 1986 ::= { pwVcCepPerfTotalEntry 20 } 1988 -- End of PW CEP Total Performance table 1990 -- Notifications - CEP VC 1992 pwVcCepGlobalNotifyEnable OBJECT-TYPE 1993 SYNTAX TruthValue 1994 MAX-ACCESS read-write 1995 STATUS current 1996 DESCRIPTION 1997 "If this object is true, then it enables the 1998 generation of pwVcCepUp and pwVcCepDown 1999 notifications, otherwise these notifications are 2000 not emitted. 2001 Note: enabling/disabling notifications for 2002 individual CEP VCs is for further study." 2003 DEFVAL { false } 2004 ::= { pwVcCepObjects 8 } 2006 pwVcCepUp NOTIFICATION-TYPE 2007 OBJECTS { pwVcOperStatus } 2008 STATUS current 2009 DESCRIPTION 2010 "This notification is generated when a CEP VC has 2011 exited the 'failure' state." 2012 ::= { pwVcCepNotifyPrefix 1 } 2014 pwVcCepDown NOTIFICATION-TYPE 2015 OBJECTS { pwVcCepLatchedIndications } 2016 STATUS current 2017 DESCRIPTION 2019 Danenberg et al Expires November 2002 38 2020 "This notification is generated when a CEP VC has 2021 entered the 'failure' state. See description of 2022 LastIndications object." 2023 ::= { pwVcCepNotifyPrefix 2 } 2025 -- End of notifications. 2027 -- Conformance Configuration table 2029 pwVcCepConformanceCfgTable OBJECT-TYPE 2030 SYNTAX SEQUENCE OF PwVcCepConformanceCfgEntry 2031 MAX-ACCESS not-accessible 2032 STATUS current 2033 DESCRIPTION 2034 "This table provides the means for the agent to 2035 declare whether certain CEP VC statistics objects 2036 are supported (conformed to) or not. If not 2037 supported, then the object MUST be return 0." 2038 ::= { pwVcCepObjects 9 } 2040 pwVcCepConformanceCfgEntry OBJECT-TYPE 2041 SYNTAX PwVcCepConformanceCfgEntry 2042 MAX-ACCESS not-accessible 2043 STATUS current 2044 DESCRIPTION 2045 "The agent MUST create a single entry in this table." 2047 INDEX { pwVcCepConformanceCfgIndex } 2049 ::= { pwVcCepConformanceCfgTable 1 } 2051 PwVcCepConformanceCfgEntry ::= SEQUENCE { 2052 pwVcCepConformanceCfgIndex INTEGER, 2054 pwVcCepPerfDbaInPacketsHCTruth TruthValue, 2055 pwVcCepPerfDbaInPacketsHCDesc SnmpAdminString, 2057 pwVcCepPerfDbaOutPacketsHCTruth TruthValue, 2058 pwVcCepPerfDbaOutPacketsHCDesc SnmpAdminString, 2060 pwVcCepPerfPktsOoseqTruth TruthValue, 2061 pwVcCepPerfPktsOoseqDesc SnmpAdminString, 2063 pwVcCepPerfPktsOoRngDroppedTruth TruthValue, 2064 pwVcCepPerfPktsOoRngDroppedDesc SnmpAdminString, 2066 pwVcCepPerfSummaryErrorsTruth TruthValue, 2067 pwVcCepPerfSummaryErrorsDesc SnmpAdminString 2068 } 2070 pwVcCepConformanceCfgIndex OBJECT-TYPE 2071 SYNTAX INTEGER (0..128) 2072 MAX-ACCESS not-accessible 2074 Danenberg et al Expires November 2002 39 2075 STATUS current 2076 DESCRIPTION 2077 "Any arbitrary number" 2078 ::= { pwVcCepConformanceCfgEntry 1 } 2080 pwVcCepPerfDbaInPacketsHCTruth OBJECT-TYPE 2081 SYNTAX TruthValue 2082 MAX-ACCESS read-only 2083 STATUS current 2084 DESCRIPTION 2085 "Tells whether the pwVcCepPerf...DbaInPacketsHC 2086 in the pwVcCepPerf...Table is supported." 2087 ::= { pwVcCepConformanceCfgEntry 2 } 2089 pwVcCepPerfDbaInPacketsHCDesc OBJECT-TYPE 2090 SYNTAX SnmpAdminString 2091 MAX-ACCESS read-only 2092 STATUS current 2093 DESCRIPTION 2094 "Explanation for pwVcCepPerf...DbaInPacketsHC 2095 support in the pwVcCepPerf...Table." 2096 ::= { pwVcCepConformanceCfgEntry 3 } 2098 pwVcCepPerfDbaOutPacketsHCTruth OBJECT-TYPE 2099 SYNTAX TruthValue 2100 MAX-ACCESS read-only 2101 STATUS current 2102 DESCRIPTION 2103 "Tells whether the pwVcCepPerf...DbaOutPacketsHC 2104 in the pwVcCepPerf...Table is supported." 2105 ::= { pwVcCepConformanceCfgEntry 4 } 2107 pwVcCepPerfDbaOutPacketsHCDesc OBJECT-TYPE 2108 SYNTAX SnmpAdminString 2109 MAX-ACCESS read-only 2110 STATUS current 2111 DESCRIPTION 2112 "Explanation for pwVcCepPerf...DbaOutPacketsHC 2113 support in the pwVcCepPerf...Table." 2114 ::= { pwVcCepConformanceCfgEntry 5 } 2116 pwVcCepPerfPktsOoseqTruth OBJECT-TYPE 2117 SYNTAX TruthValue 2118 MAX-ACCESS read-only 2119 STATUS current 2120 DESCRIPTION 2121 "Tells whether the pwVcCepPerf...PktsOoseq 2122 in the pwVcCepPerf...Table is supported." 2123 ::= { pwVcCepConformanceCfgEntry 6 } 2125 pwVcCepPerfPktsOoseqDesc OBJECT-TYPE 2126 SYNTAX SnmpAdminString 2127 MAX-ACCESS read-only 2128 STATUS current 2130 Danenberg et al Expires November 2002 40 2131 DESCRIPTION 2132 "Explanation for pwVcCepPerf...PktsOoseq 2133 support in the pwVcCepPerf...Table." 2134 ::= { pwVcCepConformanceCfgEntry 7 } 2136 pwVcCepPerfPktsOoRngDroppedTruth OBJECT-TYPE 2137 SYNTAX TruthValue 2138 MAX-ACCESS read-only 2139 STATUS current 2140 DESCRIPTION 2141 "Tells whether the pwVcCepPerf...PktsOoRngDropped 2142 in the pwVcCepPerf...Table is supported." 2143 ::= { pwVcCepConformanceCfgEntry 8 } 2145 pwVcCepPerfPktsOoRngDroppedDesc OBJECT-TYPE 2146 SYNTAX SnmpAdminString 2147 MAX-ACCESS read-only 2148 STATUS current 2149 DESCRIPTION 2150 "Explanation for pwVcCepPerf...PktsOoRngDropped 2151 support in the pwVcCepPerf...Table." 2152 ::= { pwVcCepConformanceCfgEntry 9 } 2154 pwVcCepPerfSummaryErrorsTruth OBJECT-TYPE 2155 SYNTAX TruthValue 2156 MAX-ACCESS read-only 2157 STATUS current 2158 DESCRIPTION 2159 "Tells whether the pwVcCepPerf...SummaryError 2160 in the pwVcCepPerf...Table is supported." 2161 ::= { pwVcCepConformanceCfgEntry 10 } 2163 pwVcCepPerfSummaryErrorsDesc OBJECT-TYPE 2164 SYNTAX SnmpAdminString 2165 MAX-ACCESS read-only 2166 STATUS current 2167 DESCRIPTION 2168 "Explanation for pwVcCepPerf...SummaryError 2169 support in the pwVcCepPerf...Table." 2170 ::= { pwVcCepConformanceCfgEntry 11 } 2172 -- End of CEP VC Conformance Configuration table 2174 -- Conformance Information 2176 -- Note: Conformance at the object access and values level is 2177 -- still FFS, therefore current conformance is defined at the 2178 -- object existence level only. 2180 pwVcCepGroups OBJECT IDENTIFIER ::= { pwVcCepConformance 1 } 2181 pwVcCepCompliances OBJECT IDENTIFIER ::= { pwVcCepConformance 2 } 2183 Danenberg et al Expires November 2002 41 2184 pwCepModuleCompliance MODULE-COMPLIANCE 2185 STATUS current 2186 DESCRIPTION 2187 "The compliance statement for agent that support PW 2188 over CEP PSN operation." 2190 MODULE -- this module 2191 MANDATORY-GROUPS { pwVcCepGroup, 2192 pwVcCepCfgGroup, 2193 pwVcCepPerfCurrentGroup, 2194 pwVcCepPerfIntervalGroup, 2195 pwVcCepPerfTotalGroup, 2196 pwVcCepEventGroup, 2197 pwVcCepConformanceCfgGroup 2198 } 2199 ::= { pwVcCepCompliances 1 } 2201 -- Units of conformance. 2203 pwVcCepGroup OBJECT-GROUP 2204 OBJECTS { 2205 pwVcCepType, 2206 pwVcCepSonetIfIndex, 2207 pwVcCepSonetTimeSlot, 2208 pwVcCepSonetConfigError, 2209 pwVcCepCfgIndex, 2210 pwVcCepTimeElapsed, 2211 pwVcCepValidIntervals, 2212 pwVcCepCurrentIndications, 2213 pwVcCepLatchedIndications, 2214 pwVcCepLastEsTimeStamp 2215 } 2216 STATUS current 2217 DESCRIPTION 2218 "Collection of objects for basic CEP VC config and 2219 status." 2220 ::= { pwVcCepGroups 1 } 2222 pwVcCepCfgGroup OBJECT-GROUP 2223 OBJECTS { 2224 pwVcCepCfgIndexNext, 2226 pwVcCepConfigError, 2228 pwVcCepCfgNormalPktLength, 2229 pwVcCepCfgMinPktLength, 2230 pwVcCepCfgPktReorder, 2231 pwVcCepCfgEnableDBA, 2233 pwVcCepCfgJtrBfrDepth, 2234 pwVcCepCfgJtrBfrRebuildOor, 2236 Danenberg et al Expires November 2002 42 2237 pwVcCepCfgJtrBfrRebuildOorCount, 2239 pwVcCepCfgConsecPktsInsync, 2240 pwVcCepCfgConsecMissingOutSync, 2242 pwVcCepCfgPktErrorPlayOutValue, 2244 pwVcCepCfgMissingPktsToSes, 2245 pwVcCepCfgSesToUas, 2246 pwVcCepCfgSecsToExitUas, 2248 pwVcCepCfgRowStatus, 2249 pwVcCepCfgStorageType 2250 } 2251 STATUS current 2252 DESCRIPTION 2253 "Collection of detailed objects needed to 2254 configure CEP VCs." 2255 ::= { pwVcCepGroups 2 } 2257 pwVcCepPerfCurrentGroup OBJECT-GROUP 2258 OBJECTS { 2259 pwVcCepPerfCurrentDbaInPacketsHC, 2260 pwVcCepPerfCurrentDbaOutPacketsHC, 2262 pwVcCepPerfCurrentInNegPtrAdjust, 2263 pwVcCepPerfCurrentInPosPtrAdjust, 2264 pwVcCepPerfCurrentInPtrAdjustSecs, 2265 pwVcCepPerfCurrentOutNegPtrAdjust, 2266 pwVcCepPerfCurrentOutPosPtrAdjust, 2267 pwVcCepPerfCurrentOutPtrAdjustSecs, 2268 pwVcCepPerfCurrentAbsPtrAdjust, 2270 pwVcCepPerfCurrentMissingPkts, 2271 pwVcCepPerfCurrentPktsOoseq, 2272 pwVcCepPerfCurrentPktsOoRngDropped, 2273 pwVcCepPerfCurrentJtrBfrUnderruns, 2274 pwVcCepPerfCurrentPktsBadLength, 2275 pwVcCepPerfCurrentSummaryErrors, 2277 pwVcCepPerfCurrentESs, 2278 pwVcCepPerfCurrentSESs, 2279 pwVcCepPerfCurrentUASs, 2280 pwVcCepPerfCurrentFC 2281 } 2282 STATUS current 2283 DESCRIPTION 2284 "Collection of statistics objects for CEP VCs." 2285 ::= { pwVcCepGroups 3 } 2287 pwVcCepPerfIntervalGroup OBJECT-GROUP 2288 OBJECTS { 2290 Danenberg et al Expires November 2002 43 2291 pwVcCepPerfIntervalValidData, 2292 pwVcCepPerfIntervalReset, 2293 pwVcCepPerfIntervalTimeElapsed, 2295 pwVcCepPerfIntervalDbaInPacketsHC, 2296 pwVcCepPerfIntervalDbaOutPacketsHC, 2298 pwVcCepPerfIntervalInNegPtrAdjust, 2299 pwVcCepPerfIntervalInPosPtrAdjust, 2300 pwVcCepPerfIntervalInPtrAdjustSecs, 2301 pwVcCepPerfIntervalOutNegPtrAdjust, 2302 pwVcCepPerfIntervalOutPosPtrAdjust, 2303 pwVcCepPerfIntervalOutPtrAdjustSecs, 2304 pwVcCepPerfIntervalAbsPtrAdjust, 2306 pwVcCepPerfIntervalMissingPkts, 2307 pwVcCepPerfIntervalPktsOoseq, 2308 pwVcCepPerfIntervalPktsOoRngDropped, 2309 pwVcCepPerfIntervalJtrBfrUnderruns, 2310 pwVcCepPerfIntervalPktsBadLength, 2311 pwVcCepPerfIntervalSummaryErrors, 2313 pwVcCepPerfIntervalESs, 2314 pwVcCepPerfIntervalSESs, 2315 pwVcCepPerfIntervalUASs, 2316 pwVcCepPerfIntervalFC, 2318 pwVcCepGlobalNotifyEnable 2319 } 2320 STATUS current 2321 DESCRIPTION 2322 "Collection of statistics objects for CEP VCs." 2323 ::= { pwVcCepGroups 4 } 2325 pwVcCepPerfTotalGroup OBJECT-GROUP 2326 OBJECTS { 2327 pwVcCepPerfTotalDbaInPacketsHC, 2328 pwVcCepPerfTotalDbaOutPacketsHC, 2330 pwVcCepPerfTotalInNegPtrAdjust, 2331 pwVcCepPerfTotalInPosPtrAdjust, 2332 pwVcCepPerfTotalInPtrAdjustSecs, 2333 pwVcCepPerfTotalOutNegPtrAdjust, 2334 pwVcCepPerfTotalOutPosPtrAdjust, 2335 pwVcCepPerfTotalOutPtrAdjustSecs, 2336 pwVcCepPerfTotalAbsPtrAdjust, 2338 pwVcCepPerfTotalMissingPkts, 2339 pwVcCepPerfTotalPktsOoseq, 2340 pwVcCepPerfTotalPktsOoRngDropped, 2341 pwVcCepPerfTotalJtrBfrUnderruns, 2342 pwVcCepPerfTotalPktsBadLength, 2343 pwVcCepPerfTotalSummaryErrors, 2345 Danenberg et al Expires November 2002 44 2346 pwVcCepPerfTotalESs, 2347 pwVcCepPerfTotalSESs, 2348 pwVcCepPerfTotalUASs, 2349 pwVcCepPerfTotalFC, 2350 pwVcCepPerfTotalDiscontinuityTime 2351 } 2352 STATUS current 2353 DESCRIPTION 2354 "Collection of statistics objects for CEP VCs." 2355 ::= { pwVcCepGroups 5 } 2357 pwVcCepEventGroup NOTIFICATION-GROUP 2358 NOTIFICATIONS { 2359 pwVcCepUp, 2360 pwVcCepDown 2361 } 2362 STATUS current 2363 DESCRIPTION 2364 "Collection of event objects for CEP VCs." 2365 ::= { pwVcCepGroups 7 } 2367 pwVcCepConformanceCfgGroup OBJECT-GROUP 2368 OBJECTS { 2369 pwVcCepPerfDbaInPacketsHCTruth, 2370 pwVcCepPerfDbaInPacketsHCDesc, 2372 pwVcCepPerfDbaOutPacketsHCTruth, 2373 pwVcCepPerfDbaOutPacketsHCDesc, 2375 pwVcCepPerfPktsOoseqTruth, 2376 pwVcCepPerfPktsOoseqDesc, 2378 pwVcCepPerfPktsOoRngDroppedTruth, 2379 pwVcCepPerfPktsOoRngDroppedDesc, 2381 pwVcCepPerfSummaryErrorsTruth, 2382 pwVcCepPerfSummaryErrorsDesc 2383 } 2384 STATUS current 2385 DESCRIPTION 2386 "Collection of objects declaring conformance to 2387 other objects." 2388 ::= { pwVcCepGroups 8 } 2390 END 2392 Danenberg et al Expires November 2002 45 2393 9 References 2395 [CEP] Malis, A., Jeremy Brayley, S., Martini, L., and 2396 Johnson, T., "SONET/SDH Circuit Emulation 2397 Over Packet (CEP)", Internet Draft 2398 , March 2399 2002. 2401 [LAYER] Bryant, S., Wood, L., Townsend, M., "Protocol 2402 Layering in PWE3", Internet Draft 2403 , 2404 February 2002. 2406 [TRANS] Martini et al, "Transport of Layer 2 Frames Over 2407 MPLS" , 2408 April 2002. 2410 [ENCAP] Martini et al, "Encapsulation Methods for Transport 2411 of Layer 2 Frames Over MPLS", , November 2001. 2414 [PWMIB] Zelig, D. , Feb 2002. 2416 [PWTC] Nadeau, T. , Feb 2417 2002. 2419 [SONETMIB] Tesink, K. "Definitions of Managed objects for the 2420 SONET/SDH Interface Type", RFC 2558. 2422 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 2423 RFC 1700, October 1994. See also: 2424 http://www.isi.edu/in-notes/iana/assignments/smi- 2425 numbers 2427 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 2428 FAMILY NUMBERS,(http://www.isi.edu/in- 2429 notes/iana/assignements/address-family-numbers), 2430 for MIB see: 2431 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 2433 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An 2434 Architecture for Describing SNMP Management 2435 Frameworks", RFC 2271, January 1998. 2437 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 2438 Identification of Management Information for TCP/IP- 2439 based Internets", RFC 1155, May 1990. 2441 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 2442 Definitions", RFC 1212, March 1991. 2444 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use 2445 with the SNMP", RFC 1215, March 1991. 2447 Danenberg et al Expires November 2002 46 2449 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2450 "Message Processing and Dispatching for the Simple 2451 Network Management Protocol (SNMP)", RFC 2572, 2452 April 1999. 2454 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 2455 Model (USM) for version 3 of the Simple Network 2456 Management Protocol (SNMPv3)", RFC 2574, April 2457 1999. 2459 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 2460 Waldbusser, "Protocol Operations for Version 2 of 2461 the Simple Network Management Protocol (SNMPv2)", 2462 RFC 1905, January 1996. 2464 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2465 Applications", RFC 2573, April 1999. 2467 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2468 based Access Control Model (VACM) for the Simple 2469 Network Management Protocol (SNMP)", RFC 2575, 2470 April 1999. 2472 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2473 "Introduction to Version 3 of the Internet-standard 2474 Network Management Framework", RFC 2570, April 2475 1999. 2477 [SMIv2] Case, J., McCloghrie, K., Rose, M., and S. 2478 Waldbusser, "Structure of Management Information 2479 for Version 2 of the Simple Network Management 2480 Protocol (SNMPv2)", RFC 1902, January 1996. 2482 [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. 2483 Waldbusser, "Textual Conventions for Version 2 of 2484 the Simple Network Management Protocol (SNMPv2)", 2485 RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 2486 January 1996. 2488 [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. 2489 Waldbusser, "Conformance Statements for Version 2 2490 of the Simple Network Management Protocol 2491 (SNMPv2)", RFC 1904, January 1996. 2492 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2493 "Simple Network Management Protocol", RFC 1157, May 2494 1990. 2496 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 2497 Waldbusser, "Introduction to Community-based 2498 SNMPv2", RFC 1901, January 1996. 2500 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 2501 Waldbusser, "Transport Mappings for Version 2 of 2503 Danenberg et al Expires November 2002 47 2504 the Simple Network Management Protocol (SNMPv2)", 2505 RFC 1906, January 1996. 2507 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2508 "Message Processing and Dispatching for the Simple 2509 Network Management Protocol (SNMP)", RFC 2272, 2510 January 1998. 2512 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security 2513 Model (USM) for version 3 of the Simple Network 2514 Management Protocol (SNMPv3)", RFC 2574, April 2515 1999. 2517 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 2518 Waldbusser, "Protocol Operations for Version 2 of 2519 the Simple Network Management Protocol (SNMPv2)", 2520 RFC 1905, January 1996. 2522 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2523 Applications", RFC 2273, January 1998. 2525 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2526 based Access Control Model (VACM) for the Simple 2527 Network Management Protocol (SNMP)", RFC 2575, 2528 April 1999. 2530 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 2531 for the Internet Protocol", RFC 2401, November 2532 1998. 2534 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces 2535 Group MIB using SMIv2", RFC 2233, Nov. 1997 2537 [ATOMMIB] Tesink, K., "Definitions of Managed Objects for ATM 2538 Management", RFC 2515, Feb. 1999 2540 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 2541 Requirement Levels", BCP 14, RFC 2119, March 1997. 2543 Danenberg et al Expires November 2002 48 2544 10 Author's Addresses 2546 Dave Danenberg 2547 Litchfield Communications, Inc. 2548 27 Princeton Rd 2549 Princeton Center West 2550 Watertown, CT 06795-2779 USA 2551 Email: dave_danenberg@litchfieldcomm.com 2553 David Zelig 2554 Corrigent Systems LTD. 2555 126, Yigal Alon st. 2556 Tel Aviv, ISRAEL 2557 Phone: +972-3-6945273 2558 Email: davidz@corrigent.com 2560 Thomas D. Nadeau 2561 Cisco Systems, Inc. 2562 250 Apollo Drive 2563 Chelmsford, MA 01824 USA 2564 Email: tnadeau@cisco.com 2566 Andrew G. Malis 2567 Vivace Networks, Inc. 2568 2730 Orchard Parkway 2569 San Jose, CA 95134 USA 2570 Email: Andy.Malis@vivacenetworks.com 2572 Scott C. Park 2573 Litchfield Communications, Inc. 2574 27 Princeton Rd 2575 Princeton Center West 2576 Watertown, CT 06795-2779 USA 2577 Email: scott_park@litchfieldcomm.com 2579 Danenberg et al Expires November 2002 49 2580 11 Full Copyright Statement 2582 "Copyright (C) The Internet Society (2001). All Rights Reserved. This 2583 document and translations of it may be copied and furnished to 2584 others, and derivative works that comment on or otherwise explain it 2585 or assist in its implementation may be prepared, copied, published 2586 and distributed, in whole or in part, without restriction of any 2587 kind, provided that the above copyright notice and this paragraph are 2588 included on all such copies and derivative works. However, this 2589 document itself may not be modified in any way, such as by removing 2590 the copyright notice or references to the Internet Society or other 2591 Internet organizations, except as needed for the purpose of 2592 developing Internet standards in which case the procedures for 2593 copyrights defined in the Internet Standards process must be 2594 followed, or as required to translate it into languages other than 2595 English. 2597 The limited permissions granted above are perpetual and will not be 2598 revoked by the Internet Society or its successors or assigns. 2600 This document and the information contained herein is provided on an 2601 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2602 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2603 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2604 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2605 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2607 Acknowledgement 2609 Funding for the RFC Editor function is currently provided by the 2610 Internet Society. 2612 Danenberg et al Expires November 2002 50