smilint output for ./PW-CEP-DRAFT04-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| severe | 77 |
| error | 112 |
| minor error | 22 |
| warning | 60 |
| fyi | 1 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 42 |
| basetype-unknown (error) | 12 |
| defval-syntax (error) | 3 |
| description-missing (error) | 1 |
| group-unref (warning) | 7 |
| identifier-case-match (warning) | 1 |
| import-failed (error) | 1 |
| import-unused (warning) | 1 |
| index-element-no-range (error) | 1 |
| integer-misuse (warning) | 1 |
| internal-flushing (warning) | 38 |
| internal-other (severe) | 38 |
| module-identity-missing (error) | 1 |
| node-implicit (warning) | 6 |
| object-identifier-not-prefix (error) | 44 |
| object-identifier-unknown (severe) | 39 |
| parent-row (error) | 2 |
| previous-definition (fyi) | 1 |
| scalar-not-creatable (minor error) | 18 |
| sequence-no-column (minor error) | 4 |
| sequence-order (warning) | 4 |
| type-unknown (error) | 5 |
| type-without-format (warning) | 2 |
Messages:
PW-CEP-DRAFT04-MIB
1: -- extracted from draft-ietf-pwe3-cep-mib-05.txt
2: -- at Tue Jun 8 06:20:49 2004
3:
4: PW-CEP-DRAFT04-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE,
8: Integer32, Counter32, Unsigned32, Counter64
9: FROM SNMPv2-SMI
10:
11: MODULE-COMPLIANCE, OBJECT-GROUP
12: FROM SNMPv2-CONF
13:
14: TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType,
15: TimeStamp
16: FROM SNMPv2-TC
17:
18: InterfaceIndexOrZero, InterfaceIndex
19: FROM IF-MIB
20:
21: PerfCurrentCount, PerfIntervalCount
22: FROM PerfHist-TC-MIB
23:
24: pwStdMIB
24: warning -
warning: identifier `pwStdMIB' imported from module `PW-TC-DRAFT04-MIB' is never used
25: FROM PW-TC-DRAFT04-MIB
26:
27: pwVcIndex
28: FROM PW-DRAFT04-MIB
28: error -
identifier `pwVcIndex' cannot be imported from module `PW-DRAFT04-MIB'
29:
30: SnmpAdminString
31: FROM SNMP-FRAMEWORK-MIB;
32:
33:
34: -- The CEP MIB
35:
36: pwVcCepMIB MODULE-IDENTITY
37:
38: Danenberg et al Expires December 2004 7
38: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LAST_UPDATED
39: Internet Draft PW CEP MIB June 2004
40:
41: LAST-UPDATED "200311301200Z" -- November 30 2003 12:00:00 EST
42: ORGANIZATION "Pseudo-Wire Emulation Edge-to-Edge (PWE3)
43: Working Group"
44: CONTACT-INFO
45: " Dave Danenberg
46: Postal: Litchfield Communications, Inc.
47: 27 Princeton Rd
48: Princeton Center West
49: Watertown, CT 06795
50: Tel: 203-591-7062
51: Email: dave_danenberg@litchfieldcomm.com
52:
53: Thomas D. Nadeau
54: Postal: Cisco Systems, Inc.
55: 250 Apollo Drive
56: Chelmsford, MA 01824
57: Tel: 978-244-3051
58: Email: tnadeau@cisco.com
59:
60: David Zelig (Editor)
61: Postal: Corrigent Systems LTD.
62: 126, Yigal Alon St.
63: Tel Aviv, ISRAEL
64: Phone: +972-3-6945273
65: E-mail: davidz@corrigent.com
66:
67: Andrew G. Malis
68: Postal: Tellabs, Inc.
69: 2730 Orchard Parkway
70: San Jose, CA 95134
71: Email: Andy.Malis@tellabs.com
72:
73: Ron Cohen
74: Postal: Lycium Networks
75: 2480 Sand Hill Road,
76: Menlo-Park, CA 94025
77: Email: ronc@lyciumnetworks.com
78:
79: The PWE3 Working Group (email distribution pwe3@ietf.org,
80: http://www.ietf.org/html.charters/pwe3-charter.html)
81: "
82:
83: DESCRIPTION
84: "This MIB contains managed object definitions for Circuit
85: Emulation over Packet (CEP) as in: Malis, A., Prayson, P.,
86: Cohen, R. and Zelig, D. 'SONET/SDH Circuit Emulation
87: Over Packet (CEP) encapsulation', Internet Draft <draft-
88: ietf-pwe3-sonet>.
89:
90: This MIB reports to the PW-STD-MIB as in: Zelig, D., Nadeau,
91: T. 'Pseudo Wire (PW) Management Information Base'. The
92: PW-STD-MIB contains structures and MIB associations generic
93: to Pseudo-Wire (PW) emulation. PW-specific
94: MIBs (such as this) contain config and stats for specific
95:
96: Danenberg et al Expires December 2004 8
97: Internet Draft PW CEP MIB June 2004
98:
99: PW types.
100:
101: Copyright (C) The Internet Society (date). This version
102: of this MIB module is part of RFC yyyy; see the RFC
103: itself for full legal notices.
104: -- RFC Ed.: replace yyyy with actual RFC number & remove this note
105: "
106:
107:
108: -- Revision history.
109: REVISION
110: "200311301200Z" -- November 30 2003 12:00:00 EST
111: DESCRIPTION
112: "- Update description clause of main module.
113: - Module Identity adapted to PWE3 tree.
114: - Remove notifications (PW-STD-MIB now contains the
115: PW level up/down notification).
116: "
117:
118: REVISION
119: "200310261200Z" -- 26 Oct 2003 12:00:00 EST
120: DESCRIPTION
121: "- Change pwVcCepFractTable to be rowCreated, and indexed
122: by a virtual interface. Change the description in the
123: main table to reflect this.
124: "
125:
126: REVISION
127: "200210231200Z" -- 23 Oct 2002 12:00:00 EST
128: DESCRIPTION
129: "- Added RTP header suppression config object.
130: - Deleted jitter buffer rebuild objects.
131: - Add VT and fractional SPE support.
132: - Adding textual conventions.
133: - Adding types to pwVcCepType.
134: - Changind description of pwVcCepSonetIfIndex,
135: pwVcCepSonetTimeSlot.
136: - Adding badHdrStack as error code.
137: - Change pwVcCepCfgNormalPktLength to
138: pwVcCepSonetPayloadLength to more generally convey
139: fractional SPE modes and VT modes.
140: - Adding pwVcCepFracTable.
141: "
142:
143: REVISION
144: "200208161200Z" -- 16 Aug 2002 12:00:00 EST
145: DESCRIPTION
146: "- Updated to become IETF PWE3 working group doc.
147: - Updated references to CEP draft."
148:
149: REVISION
150: "200205291200Z" -- 29 May 2002 12:00:00 EST
151: DESCRIPTION
152: "- Renamed EsTimeStamp to LastErrorTimeStamp.
153:
154: Danenberg et al Expires December 2004 9
155: Internet Draft PW CEP MIB June 2004
156:
157: - Renamed LastDefectsAtEs to LatchedIndications.
158: - Renamed CurrentDefects to CurrentIndications.
159: - Renamed defect indications (cepAis, cepRdi).
160: - Renamed DBA bit settings (ais and unequipped).
161: - Added objects: CfgJtrBfrResetOorange and
162: CfgJtrBfrResetOorangeCnt.
163:
164: - Moved SONET Time Slot and Time Slot cfg error
165: to CEP table from SONET extension table. Deleted
166: SONET extension table.
167: - Added Failure Counts (FCs) to stats tables.
168: - Removed pwVcCepPerfCurrentTimeElapsed (it is
169: a duplicate of pwVcCepTimeElapsed).
170: - Removed 32-bit counters that were duplicates
171: of 64-bit (HC) counters.
172: - Other minor changes."
173:
174: REVISION
175: "200202271200Z" -- 27 February 2002 12:00:00 EST
176: DESCRIPTION
177: "- Added objects pwVcCepTimeElapsed and
178: pwVcCepValidIntervals for more accurate knowledge
179: of interval data.
180: - Changed pwVcCepCfgJtrBfrDepth units from packets
181: to microseconds, and updated description.
182: - Changed JtrBfrOoseqDropped to JtrBfrOoRngDropped
183: (i.e, 'out of sequence' to 'out of range').
184: - Removed JtrBfrOverruns counter objects. This info
185: is now contained within the JtrBfrOoRngDropped
186: object.
187: - Changed description of JtrBfrUnderrun.
188: - Moved LastDefectsAtEs, LastEsTimeStamp, and
189: DiscontinuityTime to the pwVcCepTable table.
190: Removed them as conformance config objects.
191: - Created new CurrentDefects in CepTable.
192: - Added cepAis to and changed rdi to cepRdi
193: (both are now in LastDefectsAtEs). Added note
194: to cepAis - it must not (in itself) cause a
195: cep down notification.
196: - Changed the pwVcCepSonetExtTable to augment
197: the sonetPathCurrentTable in RFC 2558. Imported
198: sonetPathCurrentTable from the SONET-MIB.
199: - Renamed PktResequence to PktReorder."
200:
201: REVISION
202: "200111161200Z" -- 16 November 2001 12:00:00 EST
203: DESCRIPTION
204: "- Changed CEM to CEP.
205: - Removed: 'unstructured' CEP type, ECC references,
206: and signaling (CEP options) references, multiple
207: VC instances references, and APS references.
208: - Improved descriptions and some improved object names.
209: - New conformance section. New ConformanceCfg table.
210: - PktResequence is now read-only.
211:
212: Danenberg et al Expires December 2004 10
213: Internet Draft PW CEP MIB June 2004
214:
215: - ConfMaxPktLength is now ConfNormalPktLength.
216: - Replaced User Error Action with PlayOutValue.
217: - New cfg object : consecutive non-SESs to exit UAS.
218: - New cfg objects : elapsed time for stats intervals.
219: - New stats object: summary packet error.
220: - New object : added ConfigError to SonetExt table.
221:
222: - NOTE: Many objects added, deleted, or moved - so many
223: OIDs have been re-ordered."
224:
225: REVISION
226: "200109071200Z" -- 07 September 2001 12:00:00 EST
227: DESCRIPTION
228: "- Separated Top level Cfg objects from Total CEM stats.
229: - Removed references to VC instances."
230:
231: REVISION
232: "200107191200Z" -- 19 July 2001 12:00:00 EST
233: DESCRIPTION
234: "Based on the PWE3 Requirements/Framework, the original
235: CEM MIB (draft-danenberg-sonet-ces-mpls-mib-00.txt) has
236: Been split into 3 drafts:
237:
238: - PW-STD-MIB (Zelig, et al). Service-independent MIB.
239: - PW-TC-STD-MIB (Nadeau, et al). Textual Conventions.
240: - PW-CEP-STD-MIB (Danenberg, et al). Service-specific MIB.
241:
242: Aside from the split, then PW-CEM-MIB has undergone
243: other changes:
244:
245: - Ability to define LOPS (loss of packet sync), SES
246: and UAS.
247: - Support for 'unstructured' operation.
248: - Support for CEM-RDI.
249: - Many more minor changes and clarifications."
250:
251: ::= { pwStdMIB 4 } --To be assigned by IANA
251: warning -
warning: flushing recent incorrect declaration, see previous error(s)
252:
253: -- Local Textual conventions
254: PwVcCepCfgIndex ::= TEXTUAL-CONVENTION
254: fyi -
info: previous definition of `PwVcCepCfgIndex'
254: warning -
warning: type `PwVcCepCfgIndex' has no format specification
255: STATUS current
256: DESCRIPTION
257: "Index into the pwVcCepCfgTable."
258: SYNTAX Unsigned32
259:
260:
261: PwVcCepSonetEbm ::= TEXTUAL-CONVENTION
261: warning -
warning: type `PwVcCepSonetEbm' has no format specification
262: STATUS current
263: DESCRIPTION
264: "Equipped Bit Mask (EBM) as defined in draft-ietf-pwe3-
265: sonet-vt used for fractional STS-1/VC-3. The EBM bits are
266: the 28 least significant bits out of the 32 bit value"
267: SYNTAX Unsigned32
268:
269:
270: Danenberg et al Expires December 2004 11
270: error -
`Danenberg' should start with a lower case letter
270: severe -
syntax error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT
271: Internet Draft PW CEP MIB June 2004
272:
273:
274: PwVcCepSdhVc4Ebm ::= TEXTUAL-CONVENTION
275: STATUS current
276: DESCRIPTION
277: "Equipped Bit Mask (EBM) as defined in draft-ietf-pwe3-
278: sonet-vt used for each TUG-3 in fractional VC-4 circuits.
279: The EBM bits are the 30 least significant bits out of the
280: 32 bit value "
281: SYNTAX Unsigned32
282:
283: PwVcCepSonetVtgMap ::= TEXTUAL-CONVENTION
284: STATUS current
285: DESCRIPTION
286: "The VT/VC types carried in the 7 VTG/TUG-2s. The format is
287: 28 bits in the form of an Equipped Bit Mask (EBM) as
288: defined in draft-ietf-pwe3-sonet-vt used for fractional
289: STS-1/VC-3. The mapping specifies the maximal occupancies
290: of VT/VC within each VTG/TUG-2. For example, all four bits
291: are set to 1 in this objects it represents a VTG carrying
292: VT1.5s, while only three are set when VT2 are carried
293: within this VTG.
294: The relevant bits are the 28 least significant bits out of
295: the 32 bit value."
296:
297: SYNTAX Unsigned32
298:
299: PwVcCepFracAsyncMap ::= TEXTUAL-CONVENTION
300: STATUS current
301: DESCRIPTION
302: "The type of Asynchronous mapping carried inside STS-1, VC-3
303: or TUG-3 containing TU-3 circuit. The value of 'other' MUST
304: be used if the Use of this object is not applicable."
305:
306: SYNTAX INTEGER {
307: other ( 0),
308: ds3 ( 1),
309: e3 ( 2)
310: }
310: warning -
warning: flushing recent incorrect declaration, see previous error(s)
311:
312:
313: -- Top level components of this MIB module.
314:
315:
316: -- Tables, Scalars
317: pwVcCepObjects OBJECT IDENTIFIER
318: ::= { pwVcCepMIB 1 }
318: severe -
unknown object identifier label `pwVcCepMIB'
319: -- Conformance
320: pwVcCepConformance OBJECT IDENTIFIER
321: ::= { pwVcCepMIB 2 }
322:
323: -- CEP PW table
324:
325: pwVcCepTable OBJECT-TYPE
326: SYNTAX SEQUENCE OF PwVcCepEntry
327:
328: Danenberg et al Expires December 2004 12
328: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
329: Internet Draft PW CEP MIB June 2004
330:
331: MAX-ACCESS not-accessible
332: STATUS current
333: DESCRIPTION
334: "This table contains the index to the entry SONET path
335: table for this CEP PW, and the index to the CEP config
336: table."
337: ::= { pwVcCepObjects 1 }
337: warning -
warning: flushing recent incorrect declaration, see previous error(s)
338:
339: pwVcCepEntry OBJECT-TYPE
339: error -
row's parent node must be a table node
340: SYNTAX PwVcCepEntry
341: MAX-ACCESS not-accessible
342: STATUS current
343: DESCRIPTION
344: "This MIB reports to the PW-STD-MIB. This table is indexed by
345: the same index that was created for the associated entry
346: in the PW Table (in the PW-STD-MIB).
347:
348: - The PwVcIndex.
349:
350: An entry is created in this table by the agent for every
351: entry in the pwVcTable with a pwVcType of 'cep'."
352:
353: INDEX { pwVcIndex }
353: severe -
unknown object identifier label `pwVcIndex'
354:
355: ::= { pwVcCepTable 1 }
355: severe -
unknown object identifier label `pwVcCepTable'
356:
357: PwVcCepEntry ::= SEQUENCE {
357: minor error -
SEQUENCE element #3 `pwVcCepSonetTimeSlot' is not a child node under `pwVcCepEntry'
357: warning -
warning: SEQUENCE element #4 `pwVcCepSonetConfigError' does not match order of columnar objects under `pwVcCepEntry'
358:
359: pwVcCepType INTEGER,
360: pwVcCepSonetIfIndex InterfaceIndexOrZero,
361: pwVcCepSonetTimeSlot Unsigned32,
361: severe -
unknown object identifier label `pwVcCepSonetTimeSlot'
362: pwVcCepSonetConfigError BITS,
363: pwVcCepCfgIndex PwVcCepCfgIndex,
364: pwVcCepTimeElapsed Integer32,
365: pwVcCepValidIntervals Integer32,
365: severe -
unknown object identifier label `pwVcCepValidIntervals'
366: pwVcCepCurrentIndications BITS,
367: pwVcCepLatchedIndications BITS,
367: severe -
unknown object identifier label `pwVcCepLatchedIndications'
368: pwVcCepLastEsTimeStamp TimeStamp,
369: pwVcCepPeerCepOption Unsigned32
370: }
371:
372: pwVcCepType OBJECT-TYPE
373: SYNTAX INTEGER {
374: spe (1),
375: vt (2),
376: fracSpe (3)
377: }
378: MAX-ACCESS read-write
379: STATUS current
380: DESCRIPTION
381: "Specifies the type of CEP PW. Currently only
382: structured types are supported. Other CEP Types
383: may be defined in the future.
384:
385:
386: Danenberg et al Expires December 2004 13
387: Internet Draft PW CEP MIB June 2004
388:
389: Currently supported CEP types are:
390:
391: 1 - spe : SONET STS-Nc signals.
392: 2 - vt : SONET VT-x (x=1.5,2,3,6) signals.
393: 3 - fracSpe : SONET fractional STS-1 or SDH fractional
394: VC-3 or VC-4 carrying tributaries or Asynchronous
395: signals.
396:
397: Support of vt and fracSpe is optional."
398:
399:
400: DEFVAL { spe }
401: ::= { pwVcCepEntry 1 }
402:
403:
404: pwVcCepSonetIfIndex OBJECT-TYPE
405: SYNTAX InterfaceIndexOrZero
406: MAX-ACCESS read-write
407: STATUS current
408: DESCRIPTION
409: "This is a unique index within the ifTable. It represents
410: the interface index for the SONET path for SPE emulation
411: (RFC2558 section 3.3), an interface index for the SONET
412: VT (RFC2558 section 3.4) if the VT to be emulated is
413: extracted a SONET signal, or the ifIndex of the physical
414: port emulated in VT mode if the VT to be emulated is
415: directly feeded from a physical interface. It may represent
416: an internal (virtual) interface if an NSP function exists
417: between the physical interface and the emulation process.
418:
419: A value of zero indicates an interface index that has yet
420: to be determined.
421: Once set, if the SONET ifIndex is (for some reason) later
422: removed, the agent MAY delete the associated PW rows
423: (e.g., this pwVcCep table entry). If the agent does not
424: delete the rows, it is recommended that the agent set this
425: object to zero."
426: ::= { pwVcCepEntry 2 }
427:
428: pwVcCepSonetTimeSlot OBJECT-TYPE
429: SYNTAX Unsigned32 (1..192)
430: MAX-ACCESS read-write
431: STATUS current
432: DESCRIPTION
433: "In structured SPE CEP, this object indicates the starting
434: time-slot for this SONET path within the SONET line
435: and section. For OC-48, this value could range from 1
436: to 48. The SONET path width must be taken into
437: consideration here. For example, in an OC-48, an
438: STS-3c could not start at time-slot 47.
439: In structured VT CEP, this object indicates the starting
440: time slot for this tributary within the SONET path.
441: For example, for VT1.5 tributary within STS-1, this value
442: could range from 1 to 28."
443:
444: Danenberg et al Expires December 2004 14
444: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
445: Internet Draft PW CEP MIB June 2004
446:
447:
448: REFERENCE "RFC 2558, sonetPathCurrentWidth."
449: ::= { pwVcCepEntry 3 }
449: warning -
warning: flushing recent incorrect declaration, see previous error(s)
450:
451: pwVcCepSonetConfigError OBJECT-TYPE
452: SYNTAX BITS {
453: other ( 0),
454: timeslotInUse ( 1),
455: timeslotMisuse ( 2),
456: peerDbaIncompatible ( 3),
457: peerEbmIncompatible ( 4),
458: peerRtpIncompatible ( 5),
459: peerPidIncompatible ( 6),
460: peerAsyncIncompatible ( 7)
461: }
462: MAX-ACCESS read-only
463: STATUS current
464: DESCRIPTION
465: "timeslotInUse is when another CEP PW (via SONET ifIndex)
466: has already reserved a timeslot(s) that this CEP PW
467: is attempting to reserved.
468: timeslotMisuse is set, for example, if specifying a
469: starting timeslot of 45 for a SONET path of an STS-12c
470: width.
471: peerIncompatible bits are set if the local configuration is
472: not compatible with the peer configuration as available from
473: the CEP option received from the peer. for example if the
474: remote is not capable of accepting DBA packets but the local
475: node is configured to send DBA packets for this PW,
476: peerDbaIncompatible will be set."
477: ::= { pwVcCepEntry 4 }
478:
479: pwVcCepCfgIndex OBJECT-TYPE
479: warning -
warning: identifier `pwVcCepCfgIndex' differs from `PwVcCepCfgIndex' only in case
480: SYNTAX PwVcCepCfgIndex
481: MAX-ACCESS read-write
482: STATUS current
483: DESCRIPTION
484: "Index to CEP configuration table below. It is likely that
485: multiple CEP PWs will share 1 CEP Cfg table entry."
486: ::= { pwVcCepEntry 5 }
487:
488: pwVcCepTimeElapsed OBJECT-TYPE
489: SYNTAX Integer32 (1..900)
490: MAX-ACCESS read-only
491: STATUS current
492: DESCRIPTION
493: "The number of seconds, including partial seconds,
494: that have elapsed since the beginning of the current
495: measurement period. If, for some reason, such as an
496: adjustment in the system's time-of-day clock, the
497: current interval exceeds the maximum value, the
498: agent will return the maximum value."
499: ::= { pwVcCepEntry 6 }
500:
501:
502: Danenberg et al Expires December 2004 15
502: error -
`Danenberg' should start with a lower case letter
502: severe -
syntax error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT
503: Internet Draft PW CEP MIB June 2004
504:
505: pwVcCepValidIntervals OBJECT-TYPE
506: SYNTAX Integer32 (0..96)
507: MAX-ACCESS read-only
508: STATUS current
509: DESCRIPTION
510: "The number of previous 15-minute intervals for which data
511: was collected.
512: An agent with CEP capability must be capable of supporting
513: at least n intervals. The minimum value of n is 4, The
514: default of n is 32 and the maximum value of n is 96.
515: The value will be <n> unless the measurement was (re-)
516: started within the last (<n>*15) minutes, in which case the
517: value will be the number of complete 15 minute intervals for
518: which the agent has at least some data. In certain cases
519: (e.g., in the case where the agent is a proxy) it is
520: possible that some intervals are unavailable. In this case,
521: this interval is the maximum interval number for which data
522: is available. "
523: ::= { pwVcCepEntry 7 }
523: warning -
warning: flushing recent incorrect declaration, see previous error(s)
524:
525: pwVcCepCurrentIndications OBJECT-TYPE
526: SYNTAX BITS {
527: missingPkt ( 0),
528: ooRngDropped( 1),
529: jtrBfrUnder ( 2),
530: pktBadLength( 3),
531: lops ( 4),
532: cepRdi ( 5),
533: cepAis ( 6),
534: badHdrStack ( 7)
535:
536: }
537: MAX-ACCESS read-only
538: STATUS current
539: DESCRIPTION
540: "Definitions:
541:
542: missingPkt - While playing out a sequence of packets, a
543: packet(s) was determined to be missing based on a gap in the
544: CEP sequence number. Note: If the implementation supports
545: packet re-ordering, detecting gaps should not take place as
546: packets arrive, only as they are played out - this gives
547: time for mis-ordered packets to arrive late.
548:
549: ooRngDropped - Packet(s) arrives that is outside the
550: range of the jitter buffer. This may be because the
551: jitter buffer is full, or the sequence number addresses
552: a buffer outside the current jitter buffer range, or
553: addresses an already occupied buffer within range.
554: Whether or not packet re-ordering is supported by the
555: implementation, this indication MUST be supported.
556:
557: jtrBfrUnder - The jitter buffer underflowed due to
558: not enough packets arriving as packets were being
559:
560: Danenberg et al Expires December 2004 16
561: Internet Draft PW CEP MIB June 2004
562:
563: played out.
564:
565: pktBadLength - Non-bandwidth-saving packet arrives
566: larger or smaller than pwVcCepCfgSonetPayloadLength, or when
567: a fractional SPE packet length does not match the extension
568: header or manual configuration indicating the number of
569: equipped VTs.
570:
571: lops - Loss Of Packet Sync. See draft-ietf-pwe3-sonet.
572:
573: cepRdi - Circuit Emulation over Packet Remote Defect
574: Indication. Generated by the remote CEP de-packetizer when
575: detecting LOPS. Note: not generated by the remote SONET
576: function. See draft-ietf-pwe3-sonet.
577:
578: cepAis - Remote CEP packetizer has detected AIS
579: on its incoming SONET stream. See draft-ietf-pwe3-
580: sonet. Note: cepAis MUST NOT (in itself) cause a CEP
581: down notification. This would be a layer violation.
582:
583: badHdrStack - This indication is set when the number of
584: CEP header extensions detected in incoming packets does
585: not match the expected number.
586:
587: Note: currently there is no hierarchy of CEP defects.
588:
589: Note: the algorithm used to capture these indications
590: is implementation specific."
591: ::= { pwVcCepEntry 8 }
592:
593: pwVcCepLatchedIndications OBJECT-TYPE
594: SYNTAX BITS {
595: missingPkt ( 0),
596: ooRngDropped( 1),
597: jtrBfrUnder ( 2),
598: pktBadLength( 3),
599: lops ( 4),
600: cepRdi ( 5),
601: cepAis ( 6),
602: badHdrStack ( 7)
603:
604: }
605: MAX-ACCESS read-only
606: STATUS current
607: DESCRIPTION
608: "The state of CEP indicators when the CEP PW last declared
609: an errored second (either as ES, SES or a second with
610: errors inside a UAS) condition. At this time, only LOPS
611: can create a failure. Since indicators other than LOPS are
612: useful, all are latched here. For bit definitions, see
613: pwVcCepCurrentIndications above.
614:
615: Note: the algorithm used to latch these indications when
616: entering an defect state is implementation specific."
617:
618: Danenberg et al Expires December 2004 17
618: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
619: Internet Draft PW CEP MIB June 2004
620:
621: ::= { pwVcCepEntry 9 }
621: warning -
warning: flushing recent incorrect declaration, see previous error(s)
622:
623: pwVcCepLastEsTimeStamp OBJECT-TYPE
624: SYNTAX TimeStamp
625: MAX-ACCESS read-only
626: STATUS current
627: DESCRIPTION
628: "The value of sysUpTime on the most recent occasion at
629: which the CEP PW entered the ES or SES state."
630: ::= { pwVcCepEntry 10 }
631:
632: pwVcCepPeerCepOption OBJECT-TYPE
633: SYNTAX Unsigned32
634: MAX-ACCESS read-only
635: STATUS current
636: DESCRIPTION
637: "The value of CEP option parameter as received from the peer
638: by the PW signaling protocol."
639: ::= { pwVcCepEntry 11 }
640:
641: -- End of CEP PW table
642:
643:
644: -- Obtain index for PW CEP Configuration table entries
645:
646: pwVcCepCfgIndexNext OBJECT-TYPE
647: SYNTAX PwVcCepCfgIndex
648: MAX-ACCESS read-only
649: STATUS current
650: DESCRIPTION
651: "This object contains an appropriate value to be used
652: for pwVcCepCfgIndex when creating entries in the
653: pwVcCepCfgTable. The value 0 indicates that no
654: unassigned entries are available. To obtain the
655: value of pwVcCepCfgIndex for a new entry in the
656: pwVcCepCfgTable, the manager issues a management
657: protocol retrieval operation to obtain the current
658: value of pwVcCepCfgIndex. After each retrieval
659: operation, the agent should modify the value to
660: reflect the next unassigned index. After a manager
661: retrieves a value the agent will determine through
662: its local policy when this index value will be made
663: available for reuse."
664: ::= { pwVcCepObjects 2 }
665:
666: -- PW CEP PW Configuration Table
667:
668: pwVcCepCfgTable OBJECT-TYPE
669: SYNTAX SEQUENCE OF PwVcCepCfgEntry
670: MAX-ACCESS not-accessible
671: STATUS current
672: DESCRIPTION
673: "This table contains a set of parameters that may be
674: referenced by 1 or more CEP PWs by pwVcCepTable."
675:
676: Danenberg et al Expires December 2004 18
676: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
677: Internet Draft PW CEP MIB June 2004
678:
679: ::= { pwVcCepObjects 3 }
679: warning -
warning: flushing recent incorrect declaration, see previous error(s)
680:
681: pwVcCepCfgEntry OBJECT-TYPE
681: error -
row's parent node must be a table node
682: SYNTAX PwVcCepCfgEntry
683: MAX-ACCESS not-accessible
684: STATUS current
685: DESCRIPTION
686: "These parameters define the characteristics of a
687: CEP PW. They are grouped here to ease NMS burden.
688: Once an entry is created here it may be re-used
689: by many PWs."
690:
691: INDEX { pwVcCepCfgTableIndex }
692:
693: ::= { pwVcCepCfgTable 1 }
693: severe -
unknown object identifier label `pwVcCepCfgTable'
694:
695: PwVcCepCfgEntry ::= SEQUENCE {
695: minor error -
SEQUENCE element #2 `pwVcCepConfigError' is not a child node under `pwVcCepCfgEntry'
695: warning -
warning: SEQUENCE element #3 `pwVcCepSonetPayloadLength' does not match order of columnar objects under `pwVcCepCfgEntry'
696: pwVcCepCfgTableIndex PwVcCepCfgIndex,
697: pwVcCepConfigError BITS,
697: severe -
unknown object identifier label `pwVcCepConfigError'
698:
699: pwVcCepSonetPayloadLength Unsigned32,
700: pwVcCepCfgMinPktLength Unsigned32,
701: pwVcCepCfgPktReorder TruthValue,
701: severe -
unknown object identifier label `pwVcCepCfgPktReorder'
702: pwVcCepCfgEnableDBA BITS,
703: pwVcCepCfgRtpHdrSuppress TruthValue,
703: severe -
unknown object identifier label `pwVcCepCfgRtpHdrSuppress'
704:
705: pwVcCepCfgJtrBfrDepth Unsigned32,
706:
707: pwVcCepCfgConsecPktsInsync Unsigned32,
708: pwVcCepCfgConsecMissingOutSync Unsigned32,
709:
710: pwVcCepCfgPktErrorPlayOutValue Unsigned32,
711:
712: pwVcCepCfgMissingPktsToSes Unsigned32,
713: pwVcCepCfgSesToUas Unsigned32,
714: pwVcCepCfgSecsToExitUas Unsigned32,
714: severe -
unknown object identifier label `pwVcCepCfgSecsToExitUas'
715:
716: pwVcCepCfgRowStatus RowStatus,
717: pwVcCepCfgStorageType StorageType
718: }
719:
720: pwVcCepCfgTableIndex OBJECT-TYPE
721: SYNTAX PwVcCepCfgIndex
722: MAX-ACCESS not-accessible
723: STATUS current
724: DESCRIPTION
725: "Primary index to this table"
726: ::= { pwVcCepCfgEntry 1 }
727:
728: pwVcCepConfigError OBJECT-TYPE
729: SYNTAX BITS {
730: other ( 0),
731: dba ( 1),
732: lopsPktCount ( 2),
733:
734: Danenberg et al Expires December 2004 19
734: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER
735: Internet Draft PW CEP MIB June 2004
736:
737: pktLength ( 3),
738: jtrBfrDepth ( 4)
739: }
739: warning -
warning: flushing recent incorrect declaration, see previous error(s)
740: MAX-ACCESS read-only
740: severe -
syntax error, unexpected MAX_ACCESS
741: STATUS current
742: DESCRIPTION
743: "Various configurations errors. Illegal settings within
744: the pwVcCepCfg or pwVcCepSonetExt tables."
745: ::= { pwVcCepCfgEntry 2 }
745: warning -
warning: flushing recent incorrect declaration, see previous error(s)
746:
747: pwVcCepSonetPayloadLength OBJECT-TYPE
748: SYNTAX Unsigned32
749: MAX-ACCESS read-create
750: STATUS current
751: DESCRIPTION
752: "The number of SONET bytes of the Path or VT carried as
753: payload within one packet. For example, for STS-1 SPE
754: circuits, value of 783 bytes indicates that each packet
755: carries payload equivalent to one frame. For VT1.5 circuits,
756: a payload length of 104 bytes indicates that each packet
757: carries payload equivalent to one VT1.5 super-frame. The
758: actual payload size may be different, due to bandwidth
759: reduction modes, e.g. DBA mode or dynamically assigned
760: fractional SPE. This length applies to
761: inbound and outbound packets carrying user payload.
762: Although there is no control over inbound packets, those
763: of illegal length are discarded and accounted for (see
764: pwVcCepPerf...PktsBadLength.) "
765:
766:
767: REFERENCE
768: "For use of payload bytes see Malis, A., et al, <draft-ietf-
769: pwe3-sonet>."
770: ::= { pwVcCepCfgEntry 3 }
771:
772: pwVcCepCfgMinPktLength OBJECT-TYPE
773: SYNTAX Unsigned32
774: MAX-ACCESS read-create
775: STATUS current
776: DESCRIPTION
777: "This is the minimum CEP packet length in number of
778: bytes (including CEP header and payload). It applies
779: to CEP's bandwidth-savings packets. Currently DBA is
780: the only bandwidth-savings packet type (in the future,
781: CEP may support compression). Minimum packet length is
782: necessary in some systems or networks.
783:
784: Setting Zero here indicates that there is no minimum
785: packet restriction."
786:
787: DEFVAL { 0 }
788: ::= { pwVcCepCfgEntry 4 }
789:
790:
791:
792: Danenberg et al Expires December 2004 20
792: error -
`Danenberg' should start with a lower case letter
792: severe -
syntax error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT
793: Internet Draft PW CEP MIB June 2004
794:
795: pwVcCepCfgPktReorder OBJECT-TYPE
796: SYNTAX TruthValue
797: MAX-ACCESS read-only
798: STATUS current
799: DESCRIPTION
800: "If set True: as inbound packets are queued in the
801: jitter buffer, out of order packets are re-ordered. The
802: maximum sequence number differential (i.e., the range in
803: which re-sequencing can occur) is dependant on the depth
804: of the jitter buffer. See pwVcCepCfgJtrBfrDepth.
805:
806: NOTE: Some implementations may not support this feature.
807: The agent is then required to set this False."
808: ::= { pwVcCepCfgEntry 5 }
808: warning -
warning: flushing recent incorrect declaration, see previous error(s)
809:
810:
811: pwVcCepCfgEnableDBA OBJECT-TYPE
812: SYNTAX BITS {
813: ais (0),
814: unequipped (1)
815: }
816: MAX-ACCESS read-create
817: STATUS current
818: DESCRIPTION
819: "Bits set here MUST enable the DBA (dynamic bandwidth
820: allocation) feature for the specified condition. Setting
821: 'ais' MUST cause CEP packet payload suppression
822: when AIS is detected on the associated SONET path.
823: Similarly, 'unequipped' MUST cause payload suppression
824: when an un-equipped condition is detected on the SONET
825: path. During these conditions, CEP packets will continue
826: to be sent, but with indicators set in the CEP header
827: instructing the remote to play all ones (for AIS) or all
828: zeros (for un-equipped) onto its SONET path.
829:
830: NOTE: Some implementations may not support this feature.
831: In these cases, if the 'ais' or 'unequipped' bits are set,
832: then 'dba' error code MUST be set in pwVcCepConfigError."
833:
834: REFERENCE
835: "See Malis, A., et al, <draft-ietf-pwe3-sonet>."
836:
837: DEFVAL { { unequipped } }
838:
839: ::= { pwVcCepCfgEntry 6 }
840:
841: pwVcCepCfgRtpHdrSuppress OBJECT-TYPE
842: SYNTAX TruthValue
843: MAX-ACCESS read-only
844: STATUS current
845: DESCRIPTION
846: "If set True: an RTP header is not pre-pended to the
847: CEP packet."
848:
849:
850: Danenberg et al Expires December 2004 21
850: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
851: Internet Draft PW CEP MIB June 2004
852:
853: REFERENCE
854: "See Malis, A., et al, <draft-ietf-pwe3-sonet>."
855: DEFVAL { false }
855: warning -
warning: flushing recent incorrect declaration, see previous error(s)
856:
857: ::= { pwVcCepCfgEntry 7 }
857: severe -
syntax error, unexpected COLON_COLON_EQUAL
857: warning -
warning: flushing recent incorrect declaration, see previous error(s)
858:
859: pwVcCepCfgJtrBfrDepth OBJECT-TYPE
860: SYNTAX Unsigned32
861: UNITS "micro-seconds"
862: MAX-ACCESS read-create
863: STATUS current
864: DESCRIPTION
865: "This setting configures the number of microseconds
866: of expected packet delay variation for this CEP PW
867: over the PSN.
868:
869: The actual jitter buffer MUST be at least twice this
870: value for proper operation, and is implementation
871: specific.
872:
873: If configured to a value not supported by the
874: implementation, the agent MUST return an error code
875: 'jtrBfrDepth' in 'pwVcCepConfigError '
876:
877: NOTE: Like bandwidth and time-slots, jitter buffers
878: are a limited resource to be managed."
879:
880: ::= { pwVcCepCfgEntry 8 }
881:
882: --
883: -- The following counters work together to integrate (filter)
884: -- errors and the lack of errors on the CEP PW. An error is
885: -- caused by a missing packet. Missing packet can be a result
886: -- of: packet loss in the network, (uncorrectable) packet out
887: -- of sequence, packet length error, jitter buffer overflow,
888: -- and jitter buffer underflow. The result is declaring whether
889: -- or not the CEP PW is in Loss of Packet Sync (LOPS) state.
890: --
891: pwVcCepCfgConsecPktsInsync OBJECT-TYPE
892: SYNTAX Unsigned32
893: MAX-ACCESS read-create
894: STATUS current
895: DESCRIPTION "Consecutive pkts with sequential sequence
896: numbers required to exit the LOPS state."
897: REFERENCE
898: "See Malis, A., et al, <draft-ietf-pwe3-sonet>."
899: DEFVAL { 2 }
900: ::= { pwVcCepCfgEntry 9 }
901:
902: pwVcCepCfgConsecMissingOutSync OBJECT-TYPE
903: SYNTAX Unsigned32
904: MAX-ACCESS read-create
905: STATUS current
906: DESCRIPTION "Consecutive missing pkts required to enter
907:
908: Danenberg et al Expires December 2004 22
909: Internet Draft PW CEP MIB June 2004
910:
911: the LOPS state."
912: REFERENCE
913: "See Malis, A., et al, <draft-ietf-pwe3-sonet>."
914: DEFVAL { 10 }
915: ::= { pwVcCepCfgEntry 10 }
916:
917: pwVcCepCfgPktErrorPlayOutValue OBJECT-TYPE
918: SYNTAX Unsigned32 (0..255)
919: MAX-ACCESS read-create
920: STATUS current
921: DESCRIPTION
922: "This is the value played when inbound packets have
923: over/underflowed the jitter buffer, or are missing
924: for any reason. This byte pattern is sent (played) on
925: the SONET path."
926: DEFVAL { 255 } -- Play all ones
927: ::= { pwVcCepCfgEntry 11 }
928:
929: pwVcCepCfgMissingPktsToSes OBJECT-TYPE
930: SYNTAX Unsigned32
931: UNITS "seconds"
932: MAX-ACCESS read-create
933: STATUS current
934: DESCRIPTION
935: "Number of missing packets detected (consecutive or not)
936: within a 1 second window to cause a Severely Errored
937: Second (SES) to be counted."
938: DEFVAL { 3 }
939: ::= { pwVcCepCfgEntry 12 }
940:
941: pwVcCepCfgSesToUas OBJECT-TYPE
942: SYNTAX Unsigned32
943: UNITS "seconds"
944: MAX-ACCESS read-create
945: STATUS current
946: DESCRIPTION
947: "Number of consecutive SESs before declaring PW in UAS
948: state (and at which point pwVcCepPerfUASs starts counting).
949: The SesToUas default value is 10 seconds.
950:
951: NOTE: Similar to RFC 3592, If the agent chooses to update
952: the various performance statistics in real time then it must
953: be prepared to retroactively reduce the ES, SES, counts by
954: this value and increase the UAS count by this value when it
955: determines that UAS state has been entered.
956:
957: NOTE: See pwVcCepPerfSESs and pwVcCepPerfUASs."
958: DEFVAL { 10 }
959: ::= { pwVcCepCfgEntry 13 }
960:
961: pwVcCepCfgSecsToExitUas OBJECT-TYPE
962: SYNTAX Unsigned32
963: UNITS "seconds"
964: MAX-ACCESS read-create
965:
966: Danenberg et al Expires December 2004 23
966: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
967: Internet Draft PW CEP MIB June 2004
968:
969: STATUS current
970: DESCRIPTION
971: "Number of consecutive nonSESs before declaring PW is NOT
972: in UAS state (and at which point pwVcCepPerfUASs stops
973: counting)."
974: DEFVAL { 10 }
974: warning -
warning: flushing recent incorrect declaration, see previous error(s)
975: ::= { pwVcCepCfgEntry 14 }
975: severe -
syntax error, unexpected COLON_COLON_EQUAL
975: warning -
warning: flushing recent incorrect declaration, see previous error(s)
976:
977: pwVcCepCfgRowStatus OBJECT-TYPE
978: SYNTAX RowStatus
979: MAX-ACCESS read-create
980: STATUS current
981: DESCRIPTION
982: "For creating, modifying, and deleting this row."
983: ::= { pwVcCepCfgEntry 16 }
984:
985: pwVcCepCfgStorageType OBJECT-TYPE
986: SYNTAX StorageType
987: MAX-ACCESS read-create
988: STATUS current
989: DESCRIPTION
990: "This variable indicates the storage type for this
991: row."
992: ::= { pwVcCepCfgEntry 15 }
993:
994: -- End of CEP PW Configuration Parameter Table
995:
996: -- Fractional CEP Configuration Table
997:
998: pwVcCepFracTable OBJECT-TYPE
999: SYNTAX SEQUENCE OF PwVcCepFracEntry
1000: MAX-ACCESS not-accessible
1001: STATUS current
1002: DESCRIPTION
1003: "This table contains a set of parameters for CEP PWs with
1004: pwVcCepType FRAC type."
1005: ::= { pwVcCepObjects 4 }
1006:
1007: pwVcCepFracEntry OBJECT-TYPE
1008: SYNTAX PwVcCepFracEntry
1009: MAX-ACCESS not-accessible
1010: STATUS current
1011: DESCRIPTION
1012: "An entry of this table can be created in two options:
1013: - By the EMS in advance for creating the PW.
1014: - By the agent automatically when the PW is set up.
1015:
1016: The first option is typically used when there is an NSP
1017: cross-connect option between the physical ports and the
1018: emulated (virtual ports), while the second MAY be used
1019: when there is a one-to-one mapping between the emulated
1020: signal and the incoming signal. "
1021:
1022: INDEX { pwVcCepFracIndex }
1023:
1024: Danenberg et al Expires December 2004 24
1024: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
1025: Internet Draft PW CEP MIB June 2004
1026:
1027:
1028:
1029: ::= { pwVcCepFracTable 1 }
1029: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1030:
1031: PwVcCepFracEntry ::= SEQUENCE {
1032:
1033: pwVcCepFracIndex InterfaceIndex,
1034: pwVcCepFracMode INTEGER,
1034: severe -
unknown object identifier label `pwVcCepFracMode'
1035: pwVcCepFracConfigError BITS,
1036: pwVcCepFracAsync PwVcCepFracAsyncMap,
1036: severe -
unknown object identifier label `pwVcCepFracAsync'
1036: error -
unknown type `PwVcCepFracAsyncMap'
1037: pwVcCepFracVtgMap PwVcCepSonetVtgMap,
1037: error -
unknown type `PwVcCepSonetVtgMap'
1038: pwVcCepFracEbm PwVcCepSonetEbm,
1039: pwVcCepFracPeerEbm PwVcCepSonetEbm,
1040: pwVcCepFracSdhVc4Mode INTEGER,
1041: pwVcCepFracSdhVc4Tu3Map1 PwVcCepFracAsyncMap,
1042: pwVcCepFracSdhVc4Tu3Map2 PwVcCepFracAsyncMap,
1043: pwVcCepFracSdhVc4Tu3Map3 PwVcCepFracAsyncMap,
1044: pwVcCepFracSdhVc4Tug2Map1 PwVcCepSonetVtgMap,
1044: severe -
unknown object identifier label `pwVcCepFracSdhVc4Tug2Map1'
1045: pwVcCepFracSdhVc4Tug2Map2 PwVcCepSonetVtgMap,
1046: pwVcCepFracSdhVc4Tug2Map3 PwVcCepSonetVtgMap,
1047: pwVcCepFracSdhVc4Ebm1 PwVcCepSdhVc4Ebm,
1047: error -
unknown type `PwVcCepSdhVc4Ebm'
1048: pwVcCepFracSdhVc4Ebm2 PwVcCepSdhVc4Ebm,
1049: pwVcCepFracSdhVc4Ebm3 PwVcCepSdhVc4Ebm,
1050: pwVcCepFracSdhVc4PeerEbm1 PwVcCepSdhVc4Ebm,
1051: pwVcCepFracSdhVc4PeerEbm2 PwVcCepSdhVc4Ebm,
1052: pwVcCepFracSdhVc4PeerEbm3 PwVcCepSdhVc4Ebm,
1053: pwVcCepFracRowStatus RowStatus,
1054: pwVcCepFracStorageType StorageType
1055: }
1055: severe -
unknown object identifier label `pwVcCepFracStorageType'
1056:
1057: pwVcCepFracIndex OBJECT-TYPE
1058: SYNTAX InterfaceIndex
1059: MAX-ACCESS not-accessible
1060: STATUS current
1061: DESCRIPTION
1062:
1063: "This is the primary index of this table. It is a unique
1064: index within the ifTable. It represents the interface index
1065: for the SONET path (RFC 3592 section 3.3) for fractional SPE
1066: emulation.
1067: It may represent an internal (virtual) interface if an NSP
1068: function exists between the physical interface and the
1069: emulation process."
1070:
1071: ::= { pwVcCepFracEntry 1 }
1071: severe -
unknown object identifier label `pwVcCepFracEntry'
1072:
1073:
1074: pwVcCepFracMode OBJECT-TYPE
1075: SYNTAX INTEGER {
1076: notApplicable ( 0),
1077: dynamic ( 1),
1078: static ( 2),
1079: staticWithEbm ( 3),
1080: staticAsync ( 4)
1081:
1082: Danenberg et al Expires December 2004 25
1082: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting '}' or ','
1083: Internet Draft PW CEP MIB June 2004
1084:
1085: }
1085: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1086: MAX-ACCESS read-create
1086: severe -
syntax error, unexpected MAX_ACCESS
1087: STATUS current
1088: DESCRIPTION
1089:
1090: "Fractional mode for STS-1/VC-3 circuits:
1091:
1092: notApplicable - When this is not STS-1/VC-3 signal.
1093: dynamic - EBM carried within the CEP header. Unequipped
1094: VTs are removed from the payload on the fly.
1095: static - EBM not carried within the CEP header. Only VTs
1096: defined in the EBM are carried within the payload.
1097: staticWithEbm - EBM carried within the CEP header. Only
1098: VTs defined in the EBM are carried within the
1099: payload.
1100: staticAsync - Asynchronous E3/T3 fixed byte removal only. "
1101:
1102: DEFVAL { dynamic }
1102: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1103: ::= { pwVcCepFracEntry 2 }
1103: severe -
syntax error, unexpected COLON_COLON_EQUAL
1103: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1104:
1105: pwVcCepFracConfigError OBJECT-TYPE
1106: SYNTAX BITS {
1107: other ( 0),
1108: vtgMapEbmconflict ( 1),
1109: vtgMapAsyncConflict ( 2)
1110: }
1111: MAX-ACCESS read-create
1112: STATUS current
1113: DESCRIPTION
1114:
1115: "vtgMapEbmConflict is set when the configured static EBM
1116: does not match the configured vtgMap for fractional
1117: STS-1/VC-3 circuits, or when the TUG2Map is in conflict with
1118: the static EBM for VC-4 circuits. For example, if the vtgMap
1119: specifies that VTG#1 carries VT2 VTs while the EBM indicate
1120: that four VTs are equipped within VTG#1.
1121: vtgMapAsyncConflict is set when there is a conflict between
1122: the mode, the async indication and the vtgMap fields. For
1123: example, fractional mode is set to Static Async while the
1124: VtgMap indicate that the STS-1/VC-3 carries VTs. Or in
1125: fractional VC-4 circuits both async1 and Tug2Map are set."
1126:
1127: ::= { pwVcCepFracEntry 3 }
1127: minor error -
scalar object must not have a `read-create' access value
1128:
1129: pwVcCepFracAsync OBJECT-TYPE
1130: SYNTAX PwVcCepFracAsyncMap
1131: MAX-ACCESS read-create
1132: STATUS current
1133: DESCRIPTION
1134: "The Asynchronous payload carried within the STS-1/VC-3.
1135: This variable should be set when 'staticAsync' Fractional
1136: STS-1/VC-3 pwVcCepFracMode is selected, and hold the value
1137: of 'other' otherwise."
1138:
1139:
1140: Danenberg et al Expires December 2004 26
1140: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
1141: Internet Draft PW CEP MIB June 2004
1142:
1143: DEFVAL { other }
1143: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1144: ::= { pwVcCepFracEntry 4 }
1144: severe -
syntax error, unexpected COLON_COLON_EQUAL
1144: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1145:
1146: pwVcCepFracVtgMap OBJECT-TYPE
1146: error -
type `PwVcCepSonetVtgMap' of node `pwVcCepFracVtgMap' does not resolve to a known base type
1147: SYNTAX PwVcCepSonetVtgMap
1148: MAX-ACCESS read-create
1149: STATUS current
1150: DESCRIPTION
1151: "The VT/VC types of the seven VTG/TUG-2 within the
1152: STS-1/VC-3.
1153: This variable should be set when 'dynamic', 'static'
1154: or 'staticWithEbm' Fractional STS-1/VC-3 pwVcCepFracMode
1155: is selected. "
1156:
1157: ::= { pwVcCepFracEntry 5 }
1157: minor error -
scalar object must not have a `read-create' access value
1158:
1159: pwVcCepFracEbm OBJECT-TYPE
1160: SYNTAX PwVcCepSonetEbm
1161: MAX-ACCESS read-create
1162: STATUS current
1163: DESCRIPTION
1164: "Static Equipped Bit Mask (EBM) for STS-1/VC-3 channel.
1165: This variable should be set when 'static' or
1166: 'staticWithEbm' Fractional STS-1/VC-3 pwVcCepFracMode is
1167: selected. "
1168:
1169: ::= { pwVcCepFracEntry 6 }
1169: minor error -
scalar object must not have a `read-create' access value
1170:
1171: pwVcCepFracPeerEbm OBJECT-TYPE
1172: SYNTAX PwVcCepSonetEbm
1173: MAX-ACCESS read-create
1174: STATUS current
1175: DESCRIPTION
1176: "Equipped Bit Mask (EBM) for STS-1/VC-3 channel received
1177: from the peer within the CEP extension header."
1178:
1179: ::= { pwVcCepFracEntry 7 }
1179: minor error -
scalar object must not have a `read-create' access value
1180:
1181:
1182: pwVcCepFracSdhVc4Mode OBJECT-TYPE
1183: SYNTAX INTEGER {
1184: notApplicable ( 0),
1185: dynamic ( 1),
1186: static ( 2),
1187: staticWithEbm ( 3)
1188: }
1189: MAX-ACCESS read-create
1190: STATUS current
1191: DESCRIPTION
1192:
1193: "Fractional mode for VC-4 circuits:
1194:
1195: notApllicable - When this is not VC-4 circuit.
1196: dynamic - EBM carried within the CEP header. Unequipped
1197:
1198: Danenberg et al Expires December 2004 27
1199: Internet Draft PW CEP MIB June 2004
1200:
1201: VTs are removed from the payload on the fly.
1202: static - EBM not carried within the CEP header. Only VTs
1203: defined in the EBM are carried within the payload.
1204: staticWithEbm - EBM carried within the CEP header. Only
1205: VTs defined in the EBM are carried within the
1206: payload. "
1207:
1208: DEFVAL { notApplicable }
1209: ::= { pwVcCepFracEntry 8 }
1209: minor error -
scalar object must not have a `read-create' access value
1210:
1211:
1212: pwVcCepFracSdhVc4Tu3Map1 OBJECT-TYPE
1212: error -
type `PwVcCepFracAsyncMap' of node `pwVcCepFracSdhVc4Tu3Map1' does not resolve to a known base type
1213: SYNTAX PwVcCepFracAsyncMap
1214: MAX-ACCESS read-create
1215: STATUS current
1216: DESCRIPTION
1217: "If the first TUG-3 within the VC-4 contains a TU-3, this
1218: variable must be set. "
1219:
1220: DEFVAL { other }
1220: error -
default value syntax does not match object syntax
1221: ::= { pwVcCepFracEntry 9 }
1221: minor error -
scalar object must not have a `read-create' access value
1222:
1223:
1224: pwVcCepFracSdhVc4Tu3Map2 OBJECT-TYPE
1224: error -
type `PwVcCepFracAsyncMap' of node `pwVcCepFracSdhVc4Tu3Map2' does not resolve to a known base type
1225: SYNTAX PwVcCepFracAsyncMap
1226: MAX-ACCESS read-create
1227: STATUS current
1228: DESCRIPTION
1229: "If the second TUG-3 within the VC-4 contains a TU-3, this
1230: variable must be set."
1231:
1232: DEFVAL { other }
1232: error -
default value syntax does not match object syntax
1233: ::= { pwVcCepFracEntry 10 }
1233: minor error -
scalar object must not have a `read-create' access value
1234:
1235: pwVcCepFracSdhVc4Tu3Map3 OBJECT-TYPE
1235: error -
type `PwVcCepFracAsyncMap' of node `pwVcCepFracSdhVc4Tu3Map3' does not resolve to a known base type
1236: SYNTAX PwVcCepFracAsyncMap
1237: MAX-ACCESS read-create
1238: STATUS current
1239: DESCRIPTION
1240: "If the third TUG-3 within the VC-4 contains a TU-3, this
1241: variable must be set. "
1242:
1243: DEFVAL { other }
1243: error -
default value syntax does not match object syntax
1244: ::= { pwVcCepFracEntry 11 }
1244: minor error -
scalar object must not have a `read-create' access value
1245:
1246:
1247: pwVcCepFracSdhVc4Tug2Map1 OBJECT-TYPE
1248: SYNTAX PwVcCepSonetVtgMap
1249: MAX-ACCESS read-create
1250: STATUS current
1251: DESCRIPTION
1252: "The VC types of the seven TUG-2 within the first
1253: TUG-3 of the VC-4. "
1254:
1255:
1256: Danenberg et al Expires December 2004 28
1256: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
1257: Internet Draft PW CEP MIB June 2004
1258:
1259: ::= { pwVcCepFracEntry 12 }
1259: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1260:
1261: pwVcCepFracSdhVc4Tug2Map2 OBJECT-TYPE
1261: error -
type `PwVcCepSonetVtgMap' of node `pwVcCepFracSdhVc4Tug2Map2' does not resolve to a known base type
1262: SYNTAX PwVcCepSonetVtgMap
1263: MAX-ACCESS read-create
1264: STATUS current
1265: DESCRIPTION
1266: "The VC types of the seven TUG-2 within the second
1267: TUG-3 of the VC-4. "
1268:
1269: ::= { pwVcCepFracEntry 13 }
1269: minor error -
scalar object must not have a `read-create' access value
1270:
1271: pwVcCepFracSdhVc4Tug2Map3 OBJECT-TYPE
1271: error -
type `PwVcCepSonetVtgMap' of node `pwVcCepFracSdhVc4Tug2Map3' does not resolve to a known base type
1272: SYNTAX PwVcCepSonetVtgMap
1273: MAX-ACCESS read-create
1274: STATUS current
1275: DESCRIPTION
1276: "The VC types of the seven TUG-2 within the third
1277: TUG-3 of the VC-4. "
1278:
1279: ::= { pwVcCepFracEntry 14 }
1279: minor error -
scalar object must not have a `read-create' access value
1280:
1281: pwVcCepFracSdhVc4Ebm1 OBJECT-TYPE
1281: error -
type `PwVcCepSdhVc4Ebm' of node `pwVcCepFracSdhVc4Ebm1' does not resolve to a known base type
1282: SYNTAX PwVcCepSdhVc4Ebm
1283: MAX-ACCESS read-create
1284: STATUS current
1285: DESCRIPTION
1286: "Static Equipped Bit Mask (EBM) for first TUG-3 within
1287: the VC-4.
1288: This variable should be set when 'static' or
1289: 'staticWithEbm' Fractional VC-4 pwVcCepFracMode is
1290: selected. "
1291:
1292: ::= { pwVcCepFracEntry 15 }
1292: minor error -
scalar object must not have a `read-create' access value
1293:
1294: pwVcCepFracSdhVc4Ebm2 OBJECT-TYPE
1294: error -
type `PwVcCepSdhVc4Ebm' of node `pwVcCepFracSdhVc4Ebm2' does not resolve to a known base type
1295: SYNTAX PwVcCepSdhVc4Ebm
1296: MAX-ACCESS read-create
1297: STATUS current
1298: DESCRIPTION
1299: "Static Equipped Bit Mask (EBM) for second TUG-3 within
1300: the VC-4.
1301: This variable should be set when 'static' or
1302: 'StaticWithEbm' Fractional VC-4 pwVcCepFracMode is
1303: selected. "
1304:
1305: ::= { pwVcCepFracEntry 16 }
1305: minor error -
scalar object must not have a `read-create' access value
1306:
1307: pwVcCepFracSdhVc4Ebm3 OBJECT-TYPE
1307: error -
type `PwVcCepSdhVc4Ebm' of node `pwVcCepFracSdhVc4Ebm3' does not resolve to a known base type
1308: SYNTAX PwVcCepSdhVc4Ebm
1309: MAX-ACCESS read-create
1310: STATUS current
1311: DESCRIPTION
1312: "Static Equipped Bit Mask (EBM) for third TUG-3 within
1313:
1314: Danenberg et al Expires December 2004 29
1315: Internet Draft PW CEP MIB June 2004
1316:
1317: the VC-4.
1318: This variable should be set when 'Static' or
1319: 'staticWithEbm' Fractional VC-4 pwVcCepFracMode is
1320: selected. "
1321:
1322: ::= { pwVcCepFracEntry 17 }
1322: minor error -
scalar object must not have a `read-create' access value
1323:
1324:
1325: pwVcCepFracSdhVc4PeerEbm1 OBJECT-TYPE
1325: error -
type `PwVcCepSdhVc4Ebm' of node `pwVcCepFracSdhVc4PeerEbm1' does not resolve to a known base type
1326: SYNTAX PwVcCepSdhVc4Ebm
1327: MAX-ACCESS read-create
1328: STATUS current
1329: DESCRIPTION
1330: "Equipped Bit Mask (EBM) for the first TUG-3 within
1331: the fractional VC-4 channel received from peer
1332: within the CEP extension header."
1333:
1334: ::= { pwVcCepFracEntry 18 }
1334: minor error -
scalar object must not have a `read-create' access value
1335:
1336: pwVcCepFracSdhVc4PeerEbm2 OBJECT-TYPE
1336: error -
type `PwVcCepSdhVc4Ebm' of node `pwVcCepFracSdhVc4PeerEbm2' does not resolve to a known base type
1337: SYNTAX PwVcCepSdhVc4Ebm
1338: MAX-ACCESS read-create
1339: STATUS current
1340: DESCRIPTION
1341: "Equipped Bit Mask (EBM) for the second TUG-3 within
1342: the fractional VC-4 channel received from peer
1343: within the CEP extension header."
1344:
1345: ::= { pwVcCepFracEntry 19 }
1345: minor error -
scalar object must not have a `read-create' access value
1346:
1347: pwVcCepFracSdhVc4PeerEbm3 OBJECT-TYPE
1347: error -
type `PwVcCepSdhVc4Ebm' of node `pwVcCepFracSdhVc4PeerEbm3' does not resolve to a known base type
1348: SYNTAX PwVcCepSdhVc4Ebm
1349: MAX-ACCESS read-create
1350: STATUS current
1351: DESCRIPTION
1352: "Equipped Bit Mask (EBM) for the third TUG-3 within
1353: the fractional VC-4 channel received from peer
1354: within the CEP extension header."
1355:
1356: ::= { pwVcCepFracEntry 20 }
1356: minor error -
scalar object must not have a `read-create' access value
1357:
1358: pwVcCepFracRowStatus OBJECT-TYPE
1359: SYNTAX RowStatus
1360: MAX-ACCESS read-create
1361: STATUS current
1362: DESCRIPTION
1363: "For creating, modifying, and deleting this row."
1364:
1365: ::= { pwVcCepFracEntry 21 }
1365: minor error -
scalar object must not have a `read-create' access value
1366:
1367: pwVcCepFracStorageType OBJECT-TYPE
1368: SYNTAX StorageType
1369: MAX-ACCESS read-create
1370: STATUS current
1371:
1372: Danenberg et al Expires December 2004 30
1372: error -
description missing in object definition
1372: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
1373: Internet Draft PW CEP MIB June 2004
1374:
1375: DESCRIPTION
1376: "This variable indicates the storage type for this
1377: object."
1378:
1379: ::= { pwVcCepFracEntry 22 }
1379: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1380:
1381:
1382: -- End Fractional CEP Configuration Table
1383:
1384:
1385: -- CEP PW Performance Current Interval Table.
1386:
1387: pwVcCepPerfCurrentTable OBJECT-TYPE
1388: SYNTAX SEQUENCE OF PwVcCepPerfCurrentEntry
1388: error -
unknown type `PwVcCepPerfCurrentEntry'
1389: MAX-ACCESS not-accessible
1390: STATUS current
1391: DESCRIPTION
1392: "CEP bridges the SONET and packet worlds. In the packet
1393: world, counts typically start from the time of service
1394: creation - and don't stop. In the SONET world, counts are
1395: kept in 15 minute intervals. The CEP-MIB supports both
1396: methods. The current 15 minute interval counts are in
1397: this table. The interval and total stats are in tables
1398: following this.
1399:
1400: This table provides per CEP PW performance information.
1401: HC (high capacity) counters are required for some counts
1402: due to the high speeds expected with CEP services. A SONET
1403: path of width 48 (STS-48c) can rollover non-HC counters in
1404: a few minutes."
1405: ::= { pwVcCepObjects 5 }
1405: minor error -
scalar object must not have a `read-create' access value
1406:
1407: pwVcCepPerfCurrentEntry OBJECT-TYPE
1408: SYNTAX PwVcCepPerfCurrentEntry
1409: MAX-ACCESS not-accessible
1410: STATUS current
1411: DESCRIPTION
1412: "An entry in this table is created by the agent for every
1413: pwVcCep entry. After 15 minutes, the contents of this table
1414: entry are copied to a new entry in the pwVcCepPerfInterval
1415: table and the counts in this entry are reset to zero."
1416:
1417: INDEX { pwVcIndex }
1418:
1419: ::= { pwVcCepPerfCurrentTable 1 }
1420:
1421: PwVcCepPerfCurrentEntry ::= SEQUENCE {
1422: pwVcCepPerfCurrentDbaInPacketsHC Counter64,
1423: pwVcCepPerfCurrentDbaOutPacketsHC Counter64,
1424:
1425: pwVcCepPerfCurrentInNegPtrAdjust Counter32,
1426: pwVcCepPerfCurrentInPosPtrAdjust Counter32,
1427: pwVcCepPerfCurrentInPtrAdjustSecs Counter32,
1427: severe -
unknown object identifier label `pwVcCepPerfCurrentInPtrAdjustSecs'
1428: pwVcCepPerfCurrentOutNegPtrAdjust Counter32,
1429:
1430: Danenberg et al Expires December 2004 31
1430: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER
1431: Internet Draft PW CEP MIB June 2004
1432:
1433: pwVcCepPerfCurrentOutPosPtrAdjust Counter32,
1434: pwVcCepPerfCurrentOutPtrAdjustSecs Counter32,
1435: pwVcCepPerfCurrentAbsPtrAdjust Integer32,
1436:
1437: pwVcCepPerfCurrentMissingPkts Counter32,
1438: pwVcCepPerfCurrentPktsOoseq Counter32,
1439: pwVcCepPerfCurrentPktsOoRngDropped Counter32,
1440: pwVcCepPerfCurrentJtrBfrUnderruns Counter32,
1441: pwVcCepPerfCurrentPktsBadLength Counter32,
1442: pwVcCepPerfCurrentSummaryErrors Counter32,
1443:
1444: pwVcCepPerfCurrentESs PerfCurrentCount,
1445: pwVcCepPerfCurrentSESs PerfCurrentCount,
1446: pwVcCepPerfCurrentUASs PerfCurrentCount,
1447: pwVcCepPerfCurrentFC PerfCurrentCount
1448: }
1448: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1449:
1450: pwVcCepPerfCurrentDbaInPacketsHC OBJECT-TYPE
1451: SYNTAX Counter64
1452: MAX-ACCESS read-only
1453: STATUS current
1454: DESCRIPTION
1455: "Number of DBA packets received."
1456: ::= { pwVcCepPerfCurrentEntry 1 }
1457:
1458: pwVcCepPerfCurrentDbaOutPacketsHC OBJECT-TYPE
1459: SYNTAX Counter64
1460: MAX-ACCESS read-only
1461: STATUS current
1462: DESCRIPTION
1463: "Number of DBA packets sent."
1464: ::= { pwVcCepPerfCurrentEntry 2 }
1465:
1466:
1467: -- Pointer adjustment stats
1468:
1469: pwVcCepPerfCurrentInNegPtrAdjust OBJECT-TYPE
1470: SYNTAX Counter32
1471: MAX-ACCESS read-only
1472: STATUS current
1473: DESCRIPTION
1474: "Number of negative pointer adjustments sent on the
1475: SONET path based on CEP pointer adjustments received."
1476: ::= { pwVcCepPerfCurrentEntry 3 }
1477:
1478: pwVcCepPerfCurrentInPosPtrAdjust OBJECT-TYPE
1479: SYNTAX Counter32
1480: MAX-ACCESS read-only
1481: STATUS current
1482: DESCRIPTION
1483: "Number of positive pointer adjustments sent on the
1484: SONET path based on CEP pointer adjustments received."
1485: ::= { pwVcCepPerfCurrentEntry 4 }
1486:
1487:
1488: Danenberg et al Expires December 2004 32
1488: error -
`Danenberg' should start with a lower case letter
1488: severe -
syntax error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT
1489: Internet Draft PW CEP MIB June 2004
1490:
1491: pwVcCepPerfCurrentInPtrAdjustSecs OBJECT-TYPE
1492: SYNTAX Counter32
1493: MAX-ACCESS read-only
1494: STATUS current
1495: DESCRIPTION
1496: "Number of seconds in which a pos or neg pointer
1497: adjustment was sent on the SONET path."
1498: ::= { pwVcCepPerfCurrentEntry 5 }
1498: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1499:
1500: pwVcCepPerfCurrentOutNegPtrAdjust OBJECT-TYPE
1501: SYNTAX Counter32
1502: MAX-ACCESS read-only
1503: STATUS current
1504: DESCRIPTION
1505: "Number of negative pointer adjustments seen on the
1506: SONET path and encoded onto sent CEP packets."
1507: ::= { pwVcCepPerfCurrentEntry 6 }
1508:
1509: pwVcCepPerfCurrentOutPosPtrAdjust OBJECT-TYPE
1510: SYNTAX Counter32
1511: MAX-ACCESS read-only
1512: STATUS current
1513: DESCRIPTION
1514: "Number of positive pointer adjustments seen on the
1515: SONET path and encoded onto sent CEP packets."
1516: ::= { pwVcCepPerfCurrentEntry 7 }
1517:
1518: pwVcCepPerfCurrentOutPtrAdjustSecs OBJECT-TYPE
1519: SYNTAX Counter32
1520: MAX-ACCESS read-only
1521: STATUS current
1522: DESCRIPTION
1523: "Number of seconds in which a pos or neg pointer
1524: adjustment was seen on the SONET path."
1525: ::= { pwVcCepPerfCurrentEntry 8 }
1526:
1527: pwVcCepPerfCurrentAbsPtrAdjust OBJECT-TYPE
1528: SYNTAX Integer32
1529: MAX-ACCESS read-only
1530: STATUS current
1531: DESCRIPTION
1532: "Absolute Pointer adjustments is relative adjustment
1533: drifts between inbound and outbound streams. It is
1534: calculated as absolute value of :
1535: ( InPosPtrAdjust - InNegPtrAdjust ) -
1536: (OutPosPtrAdjust - OutNegPtrAdjust) "
1537: ::= { pwVcCepPerfCurrentEntry 9 }
1538:
1539: pwVcCepPerfCurrentMissingPkts OBJECT-TYPE
1540: SYNTAX Counter32
1541: MAX-ACCESS read-only
1542: STATUS current
1543: DESCRIPTION
1544: "Number of missing packets (as detected via CEP header
1545:
1546: Danenberg et al Expires December 2004 33
1547: Internet Draft PW CEP MIB June 2004
1548:
1549: sequence number gaps)."
1550: ::= { pwVcCepPerfCurrentEntry 10 }
1551:
1552: pwVcCepPerfCurrentPktsOoseq OBJECT-TYPE
1553: SYNTAX Counter32
1554: MAX-ACCESS read-only
1555: STATUS current
1556: DESCRIPTION
1557: "Number of packets detected out of sequence (via CEP
1558: header sequence numbers), but successfully re-ordered.
1559: Note: some implementations may not support this
1560: feature (see pwVcCepCfgPktReorder)."
1561: ::= { pwVcCepPerfCurrentEntry 11 }
1562:
1563: pwVcCepPerfCurrentPktsOoRngDropped OBJECT-TYPE
1564: SYNTAX Counter32
1565: MAX-ACCESS read-only
1566: STATUS current
1567: DESCRIPTION
1568: "Number of packets detected out of range (via CEP
1569: header sequence numbers), and could not be re-
1570: ordered, or could not fit in the jitter buffer."
1571: ::= { pwVcCepPerfCurrentEntry 12 }
1572:
1573: pwVcCepPerfCurrentJtrBfrUnderruns OBJECT-TYPE
1574: SYNTAX Counter32
1575: MAX-ACCESS read-only
1576: STATUS current
1577: DESCRIPTION
1578: "Number of times a packet needed to be played
1579: out and the jitter buffer was empty."
1580: ::= { pwVcCepPerfCurrentEntry 13 }
1581:
1582:
1583: pwVcCepPerfCurrentPktsBadLength OBJECT-TYPE
1584: SYNTAX Counter32
1585: MAX-ACCESS read-only
1586: STATUS current
1587: DESCRIPTION
1588: "Number of normal (non-bandwidth-saving packets received)
1589: larger or smaller than pwVcCepCfgNormalPktLength."
1590: ::= { pwVcCepPerfCurrentEntry 14 }
1591:
1592: pwVcCepPerfCurrentSummaryErrors OBJECT-TYPE
1593: SYNTAX Counter32
1594: MAX-ACCESS read-only
1595: STATUS current
1596: DESCRIPTION
1597: "A summary of all the packet error types above (from
1598: missing packets to bad length packets)."
1599: ::= { pwVcCepPerfCurrentEntry 15 }
1600:
1601: pwVcCepPerfCurrentESs OBJECT-TYPE
1602: SYNTAX PerfCurrentCount
1603:
1604: Danenberg et al Expires December 2004 34
1604: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
1605: Internet Draft PW CEP MIB June 2004
1606:
1607: MAX-ACCESS read-only
1608: STATUS current
1609: DESCRIPTION
1610: "The counter associated with the number of Errored
1611: Seconds encountered."
1612: ::= { pwVcCepPerfCurrentEntry 16 }
1612: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1613:
1614: pwVcCepPerfCurrentSESs OBJECT-TYPE
1615: SYNTAX PerfCurrentCount
1616: MAX-ACCESS read-only
1617: STATUS current
1618: DESCRIPTION
1619: "The counter associated with the number of
1620: Severely Errored Seconds encountered."
1621: ::= { pwVcCepPerfCurrentEntry 17 }
1622:
1623: pwVcCepPerfCurrentUASs OBJECT-TYPE
1624: SYNTAX PerfCurrentCount
1625: MAX-ACCESS read-only
1626: STATUS current
1627: DESCRIPTION
1628: "The counter associated with the number of
1629: Unavailable Seconds encountered."
1630: ::= { pwVcCepPerfCurrentEntry 18 }
1631:
1632: pwVcCepPerfCurrentFC OBJECT-TYPE
1633: SYNTAX PerfCurrentCount
1634: MAX-ACCESS read-only
1635: STATUS current
1636: DESCRIPTION
1637: "CEP Failure Counts (FC-CEP). The number of CEP failure
1638: events. A failure event begins when the LOPS failure
1639: is declared, and ends when the failure is cleared. A
1640: failure event that begins in one period and ends in
1641: another period is counted only in the period in which
1642: it begins."
1643: ::= { pwVcCepPerfCurrentEntry 19 }
1644:
1645: -- End CEP PW Performance Current Interval Table
1646:
1647:
1648: -- CEP PW Performance Interval Table.
1649:
1650: pwVcCepPerfIntervalTable OBJECT-TYPE
1651: SYNTAX SEQUENCE OF PwVcCepPerfIntervalEntry
1652: MAX-ACCESS not-accessible
1653: STATUS current
1654: DESCRIPTION
1655: "This table provides per CEP PW performance information
1656: much like the pwVcCepPerfCurrentTable above. However,
1657: these counts represent historical 15 minute intervals.
1658: Typically, this table will have a maximum of 96 entries
1659: for a 24 hour period, but is not limited to this.
1660: NOTE: Counter64 objects are used here, Counter32 is
1661:
1662: Danenberg et al Expires December 2004 35
1663: Internet Draft PW CEP MIB June 2004
1664:
1665: too small for OC-768 CEP PWs."
1666: ::= { pwVcCepObjects 6 }
1667:
1668: pwVcCepPerfIntervalEntry OBJECT-TYPE
1669: SYNTAX PwVcCepPerfIntervalEntry
1670: MAX-ACCESS not-accessible
1671: STATUS current
1672: DESCRIPTION
1673: "An entry in this table is created by the agent for
1674: every pwVcCepPerfCurrentEntry that is 15 minutes old.
1675: The contents of the Current entry are copied to the new
1676: entry here. The Current entry, then resets its counts
1677: to zero for the next current 15 minute interval.
1678: pwVcCepIndex is found in the pwVcCepCfg table."
1679:
1680: INDEX { pwVcIndex, pwVcCepPerfIntervalNumber }
1680: severe -
unknown object identifier label `pwVcCepPerfIntervalNumber'
1681:
1682: ::= { pwVcCepPerfIntervalTable 1 }
1683:
1684: PwVcCepPerfIntervalEntry ::= SEQUENCE {
1684: minor error -
SEQUENCE element #1 `pwVcCepPerfIntervalNumber' is not a child node under `pwVcCepPerfIntervalEntry'
1684: warning -
warning: SEQUENCE element #2 `pwVcCepPerfIntervalValidData' does not match order of columnar objects under `pwVcCepPerfIntervalEntry'
1685: pwVcCepPerfIntervalNumber Unsigned32,
1686: pwVcCepPerfIntervalValidData TruthValue,
1687: pwVcCepPerfIntervalReset INTEGER,
1688: pwVcCepPerfIntervalTimeElapsed Integer32,
1689:
1690: pwVcCepPerfIntervalDbaInPacketsHC Counter64,
1691: pwVcCepPerfIntervalDbaOutPacketsHC Counter64,
1691: severe -
unknown object identifier label `pwVcCepPerfIntervalDbaOutPacketsHC'
1692:
1693: pwVcCepPerfIntervalInNegPtrAdjust Counter32,
1694: pwVcCepPerfIntervalInPosPtrAdjust Counter32,
1695: pwVcCepPerfIntervalInPtrAdjustSecs Counter32,
1696: pwVcCepPerfIntervalOutNegPtrAdjust Counter32,
1697: pwVcCepPerfIntervalOutPosPtrAdjust Counter32,
1698: pwVcCepPerfIntervalOutPtrAdjustSecs Counter32,
1698: severe -
unknown object identifier label `pwVcCepPerfIntervalOutPtrAdjustSecs'
1699: pwVcCepPerfIntervalAbsPtrAdjust Integer32,
1700:
1701: pwVcCepPerfIntervalMissingPkts Counter32,
1702: pwVcCepPerfIntervalPktsOoseq Counter32,
1703: pwVcCepPerfIntervalPktsOoRngDropped Counter32,
1704: pwVcCepPerfIntervalJtrBfrUnderruns Counter32,
1704: severe -
unknown object identifier label `pwVcCepPerfIntervalJtrBfrUnderruns'
1705: pwVcCepPerfIntervalPktsBadLength Counter32,
1706: pwVcCepPerfIntervalSummaryErrors Counter32,
1707:
1708: pwVcCepPerfIntervalESs PerfIntervalCount,
1709: pwVcCepPerfIntervalSESs PerfIntervalCount,
1710: pwVcCepPerfIntervalUASs PerfIntervalCount,
1711: pwVcCepPerfIntervalFC PerfIntervalCount
1712: }
1712: severe -
unknown object identifier label `pwVcCepPerfIntervalFC'
1713:
1714: pwVcCepPerfIntervalNumber OBJECT-TYPE
1715: SYNTAX Unsigned32
1716: MAX-ACCESS not-accessible
1717: STATUS current
1718: DESCRIPTION
1719:
1720: Danenberg et al Expires December 2004 36
1720: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting QUOTED_STRING
1721: Internet Draft PW CEP MIB June 2004
1722:
1723: "A number (normally between 1 and 96 to cover a 24 hour
1724: period) which identifies the interval for which the set
1725: of statistics is available. The interval identified by 1
1726: is the most recently completed 15 minute interval, and
1727: the interval identified by N is the interval immediately
1728: preceding the one identified by N-1. The minimum range of
1729: N is 1 through 4. The default range is 1 through 32. The
1730: maximum value of N is 1 through 96."
1731: ::= { pwVcCepPerfIntervalEntry 1 }
1731: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1732:
1733:
1734: pwVcCepPerfIntervalValidData OBJECT-TYPE
1735: SYNTAX TruthValue
1736: MAX-ACCESS read-only
1737: STATUS current
1738: DESCRIPTION
1739: "This variable indicates if the data for this interval
1740: is valid."
1741: ::= { pwVcCepPerfIntervalEntry 2 }
1742:
1743: pwVcCepPerfIntervalReset OBJECT-TYPE
1744: SYNTAX INTEGER {
1745: reset (1),
1746: normal(2)
1747: }
1748: MAX-ACCESS read-create
1749: STATUS current
1750: DESCRIPTION
1751: "Used in cases where the user knows that the errors
1752:
1753: within this interval should not be counted. Writing
1754: 'reset' sets all error counts to zero."
1755: ::= { pwVcCepPerfIntervalEntry 3 }
1756:
1757: pwVcCepPerfIntervalTimeElapsed OBJECT-TYPE
1758: SYNTAX Integer32
1759: MAX-ACCESS read-only
1760: STATUS current
1761: DESCRIPTION
1762: "The duration of a particular interval in seconds,
1763: Adjustments in the system's time-of-day clock, may
1764: cause the interval to be greater or less than, the
1765: normal value. Therefore this actual interval value
1766: is provided."
1767: ::= { pwVcCepPerfIntervalEntry 4 }
1768:
1769: pwVcCepPerfIntervalDbaInPacketsHC OBJECT-TYPE
1770: SYNTAX Counter64
1771: MAX-ACCESS read-only
1772: STATUS current
1773: DESCRIPTION
1774: "Number of DBA packets received."
1775: ::= { pwVcCepPerfIntervalEntry 5 }
1776:
1777:
1778: Danenberg et al Expires December 2004 37
1778: error -
`Danenberg' should start with a lower case letter
1778: severe -
syntax error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT
1779: Internet Draft PW CEP MIB June 2004
1780:
1781: pwVcCepPerfIntervalDbaOutPacketsHC OBJECT-TYPE
1782: SYNTAX Counter64
1783: MAX-ACCESS read-only
1784: STATUS current
1785: DESCRIPTION
1786: "Number of DBA packets sent."
1787: ::= { pwVcCepPerfIntervalEntry 6 }
1787: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1788:
1789:
1790: -- Pointer adjustment stats
1791: pwVcCepPerfIntervalInNegPtrAdjust OBJECT-TYPE
1792: SYNTAX Counter32
1793: MAX-ACCESS read-only
1794: STATUS current
1795: DESCRIPTION
1796: "Number of negative pointer adjustments sent on the
1797: SONET path based on CEP pointer adjustments received."
1798: ::= { pwVcCepPerfIntervalEntry 7 }
1799:
1800: pwVcCepPerfIntervalInPosPtrAdjust OBJECT-TYPE
1801: SYNTAX Counter32
1802: MAX-ACCESS read-only
1803: STATUS current
1804: DESCRIPTION
1805: "Number of positive pointer adjustments sent on the
1806: SONET path based on CEP pointer adjustments received."
1807: ::= { pwVcCepPerfIntervalEntry 8 }
1808:
1809: pwVcCepPerfIntervalInPtrAdjustSecs OBJECT-TYPE
1810: SYNTAX Counter32
1811: MAX-ACCESS read-only
1812: STATUS current
1813: DESCRIPTION
1814: "Number of seconds in which a pos or neg pointer
1815: adjustment was sent on the SONET path."
1816: ::= { pwVcCepPerfIntervalEntry 9 }
1817:
1818: pwVcCepPerfIntervalOutNegPtrAdjust OBJECT-TYPE
1819: SYNTAX Counter32
1820: MAX-ACCESS read-only
1821: STATUS current
1822: DESCRIPTION
1823: "Number of negative pointer adjustments seen on the
1824: SONET path and encoded onto sent CEP packets."
1825: ::= { pwVcCepPerfIntervalEntry 10 }
1826:
1827: pwVcCepPerfIntervalOutPosPtrAdjust OBJECT-TYPE
1828: SYNTAX Counter32
1829: MAX-ACCESS read-only
1830: STATUS current
1831: DESCRIPTION
1832: "Number of positive pointer adjustments seen on the
1833: SONET path and encoded onto sent CEP packets."
1834: ::= { pwVcCepPerfIntervalEntry 11 }
1835:
1836: Danenberg et al Expires December 2004 38
1836: error -
`Danenberg' should start with a lower case letter
1836: severe -
syntax error, unexpected LOWERCASE_IDENTIFIER, expecting OBJECT
1837: Internet Draft PW CEP MIB June 2004
1838:
1839:
1840: pwVcCepPerfIntervalOutPtrAdjustSecs 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: ::= { pwVcCepPerfIntervalEntry 12 }
1847: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1848:
1849: pwVcCepPerfIntervalAbsPtrAdjust OBJECT-TYPE
1850: SYNTAX Integer32
1851: MAX-ACCESS read-only
1852: STATUS current
1853: DESCRIPTION
1854: "Absolute Pointer adjustments is relative adjustment
1855: drifts between inbound and outbound streams. It is
1856: calculated as absolute value of :
1857: ( InPosPtrAdjust - InNegPtrAdjust) -
1858: (OutPosPtrAdjust - OutNegPtrAdjust) "
1859: ::= { pwVcCepPerfIntervalEntry 13 }
1860:
1861: pwVcCepPerfIntervalMissingPkts OBJECT-TYPE
1862: SYNTAX Counter32
1863: MAX-ACCESS read-only
1864: STATUS current
1865: DESCRIPTION
1866: "Number of missing packets (as detected via CEP header
1867: sequence number gaps)."
1868: ::= { pwVcCepPerfIntervalEntry 14 }
1869:
1870: pwVcCepPerfIntervalPktsOoseq OBJECT-TYPE
1871: SYNTAX Counter32
1872: MAX-ACCESS read-only
1873: STATUS current
1874: DESCRIPTION
1875: "Number of packets detected out of sequence (via CEP
1876: header sequence numbers), but successfully re-ordered.
1877: Note: some implementations mat not support this
1878: feature (see pwVcCepCfgPktReorder)."
1879: ::= { pwVcCepPerfIntervalEntry 15 }
1880:
1881: pwVcCepPerfIntervalPktsOoRngDropped OBJECT-TYPE
1882: SYNTAX Counter32
1883: MAX-ACCESS read-only
1884: STATUS current
1885: DESCRIPTION
1886: "Number of packets detected out of range (via CEP
1887: header sequence numbers), and could not be re-
1888: ordered, or could not fit in the jitter buffer."
1889: ::= { pwVcCepPerfIntervalEntry 16 }
1890:
1891: pwVcCepPerfIntervalJtrBfrUnderruns OBJECT-TYPE
1892: SYNTAX Counter32
1893:
1894: Danenberg et al Expires December 2004 39
1894: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
1895: Internet Draft PW CEP MIB June 2004
1896:
1897: MAX-ACCESS read-only
1898: STATUS current
1899: DESCRIPTION
1900: "Number of times a packet needed to be played
1901: out and the jitter buffer was empty."
1902: ::= { pwVcCepPerfIntervalEntry 17 }
1902: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1903:
1904: pwVcCepPerfIntervalPktsBadLength OBJECT-TYPE
1905: SYNTAX Counter32
1906: MAX-ACCESS read-only
1907: STATUS current
1908: DESCRIPTION
1909: "Number of packets received larger or smaller than
1910: pwVcCepCfgNormalPktLength."
1911: ::= { pwVcCepPerfIntervalEntry 18 }
1912:
1913: pwVcCepPerfIntervalSummaryErrors 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: ::= { pwVcCepPerfIntervalEntry 19 }
1921:
1922: pwVcCepPerfIntervalESs OBJECT-TYPE
1923: SYNTAX PerfIntervalCount
1924: MAX-ACCESS read-only
1925: STATUS current
1926: DESCRIPTION
1927: "The counter associated with the number of Errored
1928: Seconds encountered."
1929: ::= { pwVcCepPerfIntervalEntry 20 }
1930:
1931: pwVcCepPerfIntervalSESs OBJECT-TYPE
1932: SYNTAX PerfIntervalCount
1933: MAX-ACCESS read-only
1934: STATUS current
1935: DESCRIPTION
1936: "The counter associated with the number of
1937: Severely Errored Seconds encountered."
1938: ::= { pwVcCepPerfIntervalEntry 21 }
1939:
1940: pwVcCepPerfIntervalUASs OBJECT-TYPE
1941: SYNTAX PerfIntervalCount
1942: MAX-ACCESS read-only
1943: STATUS current
1944: DESCRIPTION
1945: "The counter associated with the number of
1946: Unavailable Seconds encountered."
1947: ::= { pwVcCepPerfIntervalEntry 22 }
1948:
1949: pwVcCepPerfIntervalFC OBJECT-TYPE
1950: SYNTAX PerfIntervalCount
1951:
1952: Danenberg et al Expires December 2004 40
1952: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
1953: Internet Draft PW CEP MIB June 2004
1954:
1955: MAX-ACCESS read-only
1956: STATUS current
1957: DESCRIPTION
1958: "CEP Failure Counts (FC-CEP). The number of CEP failure
1959: events. A failure event begins when the LOPS failure
1960: is declared, and ends when the failure is cleared. A
1961: failure event that begins in one period and ends in
1962: another period is counted only in the period in which
1963: it begins."
1964: ::= { pwVcCepPerfIntervalEntry 23 }
1964: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1965:
1966: -- End CEP PW Performance Interval Table
1967:
1968:
1969: -- CEP PW Total Performance Table
1970:
1971: pwVcCepPerfTotalTable OBJECT-TYPE
1972: SYNTAX SEQUENCE OF PwVcCepPerfTotalEntry
1972: error -
unknown type `PwVcCepPerfTotalEntry'
1973: MAX-ACCESS not-accessible
1974: STATUS current
1975: DESCRIPTION
1976: "This table provides per CEP PW performance information
1977: much like the pwVcCepPerfIntervalTable above. However,
1978: these counts represent complete historical information.
1979: NOTE: Counter64 objects are used here, Counter32 is
1980: too small for OC-768 CEP PWs."
1981: ::= { pwVcCepObjects 7 }
1982:
1983: pwVcCepPerfTotalEntry OBJECT-TYPE
1984: SYNTAX PwVcCepPerfTotalEntry
1985: MAX-ACCESS not-accessible
1986: STATUS current
1987: DESCRIPTION
1988: "An entry is created in this table by the agent for
1989: every entry in the pwVcCep table."
1990:
1991: INDEX { pwVcIndex }
1992:
1993: ::= { pwVcCepPerfTotalTable 1 }
1994:
1995: PwVcCepPerfTotalEntry ::= SEQUENCE {
1996:
1997: pwVcCepPerfTotalDbaInPacketsHC Counter64,
1998: pwVcCepPerfTotalDbaOutPacketsHC Counter64,
1999:
2000: pwVcCepPerfTotalInNegPtrAdjust Counter32,
2001: pwVcCepPerfTotalInPosPtrAdjust Counter32,
2002: pwVcCepPerfTotalInPtrAdjustSecs Counter32,
2002: severe -
unknown object identifier label `pwVcCepPerfTotalInPtrAdjustSecs'
2003: pwVcCepPerfTotalOutNegPtrAdjust Counter32,
2004: pwVcCepPerfTotalOutPosPtrAdjust Counter32,
2005: pwVcCepPerfTotalOutPtrAdjustSecs Counter32,
2006: pwVcCepPerfTotalAbsPtrAdjust Integer32,
2007:
2008: pwVcCepPerfTotalMissingPkts Counter32,
2009:
2010: Danenberg et al Expires December 2004 41
2010: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting LOWERCASE_IDENTIFIER
2011: Internet Draft PW CEP MIB June 2004
2012:
2013: pwVcCepPerfTotalPktsOoseq Counter32,
2014: pwVcCepPerfTotalPktsOoRngDropped Counter32,
2015: pwVcCepPerfTotalJtrBfrUnderruns Counter32,
2016: pwVcCepPerfTotalPktsBadLength Counter32,
2017: pwVcCepPerfTotalSummaryErrors Counter32,
2018:
2019: pwVcCepPerfTotalESs Counter32,
2020: pwVcCepPerfTotalSESs Counter32,
2021: pwVcCepPerfTotalUASs Counter32,
2022: pwVcCepPerfTotalFC Counter32,
2023: pwVcCepPerfTotalDiscontinuityTime TimeStamp
2024: }
2024: warning -
warning: flushing recent incorrect declaration, see previous error(s)
2025:
2026: pwVcCepPerfTotalDbaInPacketsHC OBJECT-TYPE
2027: SYNTAX Counter64
2028: MAX-ACCESS read-only
2029: STATUS current
2030: DESCRIPTION
2031: "Number of DBA packets received."
2032: ::= { pwVcCepPerfTotalEntry 1 }
2033:
2034: pwVcCepPerfTotalDbaOutPacketsHC OBJECT-TYPE
2035: SYNTAX Counter64
2036: MAX-ACCESS read-only
2037: STATUS current
2038: DESCRIPTION
2039: "Number of DBA packets sent."
2040: ::= { pwVcCepPerfTotalEntry 2 }
2041:
2042:
2043: -- Pointer adjustment stats
2044: pwVcCepPerfTotalInNegPtrAdjust OBJECT-TYPE
2045: SYNTAX Counter32
2046: MAX-ACCESS read-only
2047: STATUS current
2048: DESCRIPTION
2049: "Number of negative pointer adjustments sent on the
2050: SONET path based on CEP pointer adjustments received."
2051: ::= { pwVcCepPerfTotalEntry 3 }
2052:
2053: pwVcCepPerfTotalInPosPtrAdjust OBJECT-TYPE
2054: SYNTAX Counter32
2055: MAX-ACCESS read-only
2056: STATUS current
2057: DESCRIPTION
2058: "Number of positive pointer adjustments sent on the
2059: SONET path based on CEP pointer adjustments received."
2060: ::= { pwVcCepPerfTotalEntry 4 }
2061:
2062: pwVcCepPerfTotalInPtrAdjustSecs OBJECT-TYPE
2063: SYNTAX Counter32
2064: MAX-ACCESS read-only
2065: STATUS current
2066: DESCRIPTION
2067:
2068: Danenberg et al Expires December 2004 42
2068: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting QUOTED_STRING
2069: Internet Draft PW CEP MIB June 2004
2070:
2071: "Number of seconds in which a pos or neg pointer
2072: adjustment was sent on the SONET path."
2073: ::= { pwVcCepPerfTotalEntry 5 }
2073: warning -
warning: flushing recent incorrect declaration, see previous error(s)
2074:
2075: pwVcCepPerfTotalOutNegPtrAdjust OBJECT-TYPE
2076: SYNTAX Counter32
2077: MAX-ACCESS read-only
2078: STATUS current
2079: DESCRIPTION
2080: "Number of negative pointer adjustments seen on the
2081: SONET path and encoded onto sent CEP packets."
2082: ::= { pwVcCepPerfTotalEntry 6 }
2083:
2084: pwVcCepPerfTotalOutPosPtrAdjust OBJECT-TYPE
2085: SYNTAX Counter32
2086: MAX-ACCESS read-only
2087: STATUS current
2088: DESCRIPTION
2089: "Number of positive pointer adjustments seen on the
2090: SONET path and encoded onto sent CEP packets."
2091: ::= { pwVcCepPerfTotalEntry 7 }
2092:
2093: pwVcCepPerfTotalOutPtrAdjustSecs OBJECT-TYPE
2094: SYNTAX Counter32
2095: MAX-ACCESS read-only
2096: STATUS current
2097: DESCRIPTION
2098: "Number of seconds in which a pos or neg pointer
2099: adjustment was seen on the SONET path."
2100: ::= { pwVcCepPerfTotalEntry 8 }
2101:
2102: pwVcCepPerfTotalAbsPtrAdjust OBJECT-TYPE
2103: SYNTAX Integer32
2104: MAX-ACCESS read-only
2105: STATUS current
2106: DESCRIPTION
2107: "Absolute Pointer adjustments is relative adjustment
2108: drifts between inbound and outbound streams. It is
2109: calculated as absolute value of :
2110: ( InPosPtrAdjust - InNegPtrAdjust) -
2111: (OutPosPtrAdjust - OutNegPtrAdjust) "
2112: ::= { pwVcCepPerfTotalEntry 9 }
2113:
2114: pwVcCepPerfTotalMissingPkts OBJECT-TYPE
2115: SYNTAX Counter32
2116: MAX-ACCESS read-only
2117: STATUS current
2118: DESCRIPTION
2119: "Number of missing packets (as detected via CEP header
2120: sequence number gaps)."
2121: ::= { pwVcCepPerfTotalEntry 10 }
2122:
2123: pwVcCepPerfTotalPktsOoseq OBJECT-TYPE
2124: SYNTAX Counter32
2125:
2126: Danenberg et al Expires December 2004 43
2126: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
2127: Internet Draft PW CEP MIB June 2004
2128:
2129: MAX-ACCESS read-only
2130: STATUS current
2131: DESCRIPTION
2132: "Number of packets detected out of sequence (via CEP
2133: header sequence numbers), but successfully re-ordered.
2134: Note: some implementations may not support this feature
2135: (see pwVcCepCfgPktReorder)."
2136: ::= { pwVcCepPerfTotalEntry 11 }
2136: warning -
warning: flushing recent incorrect declaration, see previous error(s)
2137:
2138: pwVcCepPerfTotalPktsOoRngDropped OBJECT-TYPE
2139: SYNTAX Counter32
2140: MAX-ACCESS read-only
2141: STATUS current
2142: DESCRIPTION
2143: "Number of packets detected out of range (via CEP
2144: header sequence numbers), and could not be re-
2145: ordered, or could not fit in the jitter buffer."
2146: ::= { pwVcCepPerfTotalEntry 12 }
2147:
2148: pwVcCepPerfTotalJtrBfrUnderruns OBJECT-TYPE
2149: SYNTAX Counter32
2150: MAX-ACCESS read-only
2151: STATUS current
2152: DESCRIPTION
2153: "Number of times a packet needed to be played
2154: out and the jitter buffer was empty."
2155: ::= { pwVcCepPerfTotalEntry 13 }
2156:
2157: pwVcCepPerfTotalPktsBadLength OBJECT-TYPE
2158: SYNTAX Counter32
2159: MAX-ACCESS read-only
2160: STATUS current
2161: DESCRIPTION
2162: "Number of packets received larger or smaller than
2163: pwVcCepCfgNormalPktLength."
2164: ::= { pwVcCepPerfTotalEntry 14 }
2165:
2166: pwVcCepPerfTotalSummaryErrors OBJECT-TYPE
2167: SYNTAX Counter32
2168: MAX-ACCESS read-only
2169: STATUS current
2170: DESCRIPTION
2171: "A summary of all the packet error types above (from
2172: missing packets to bad length packets)."
2173: ::= { pwVcCepPerfTotalEntry 15 }
2174:
2175: pwVcCepPerfTotalESs OBJECT-TYPE
2176: SYNTAX Counter32
2177: MAX-ACCESS read-only
2178: STATUS current
2179: DESCRIPTION
2180: "The counter associated with the number of Errored
2181: Seconds encountered. See draft-ietf-pwe3-sonet for
2182: definition of ES."
2183:
2184: Danenberg et al Expires December 2004 44
2184: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
2185: Internet Draft PW CEP MIB June 2004
2186:
2187: ::= { pwVcCepPerfTotalEntry 16 }
2187: warning -
warning: flushing recent incorrect declaration, see previous error(s)
2188:
2189: pwVcCepPerfTotalSESs OBJECT-TYPE
2190: SYNTAX Counter32
2191: MAX-ACCESS read-only
2192: STATUS current
2193: DESCRIPTION
2194: "The counter associated with the number of Severely
2195: Errored Seconds. See pwVcCepCfgMissingPktsToSes.
2196: Also see draft-ietf-pwe3-sonet for definition."
2197: ::= { pwVcCepPerfTotalEntry 17 }
2198:
2199: pwVcCepPerfTotalUASs OBJECT-TYPE
2200: SYNTAX Counter32
2201: MAX-ACCESS read-only
2202: STATUS current
2203: DESCRIPTION
2204: "The counter associated with the number of
2205: UnAvailable Seconds. See pwVcCepCfgSesToUAS.
2206:
2207: NOTE: When first entering the UAS state, the number
2208: of SesToUas is added to this object, then as each
2209: additional UAS occurs, this object increments by one.
2210:
2211: NOTE: Similar to RFC 2558, If the agent chooses to update
2212: the various performance statistics in real time then it must
2213: be prepared to retroactively reduce the ES, SES, counts (by
2214: the value of pwVcCepCfgSesToUas) and increase the UAS
2215: count (by that same value) when it determines that UAS
2216: state has been entered."
2217: ::= { pwVcCepPerfTotalEntry 18 }
2218:
2219: pwVcCepPerfTotalFC OBJECT-TYPE
2220: SYNTAX Counter32
2221: MAX-ACCESS read-only
2222: STATUS current
2223: DESCRIPTION
2224: "CEP Failure Counts (FC-CEP). The number of CEP failure
2225: events. A failure event begins when the LOPS failure
2226: is declared, and ends when the failure is cleared."
2227: ::= { pwVcCepPerfTotalEntry 19 }
2228:
2229: pwVcCepPerfTotalDiscontinuityTime OBJECT-TYPE
2230: SYNTAX TimeStamp
2231: MAX-ACCESS read-only
2232: STATUS current
2233:
2234: DESCRIPTION
2235: "The value of sysUpTime on the most recent occasion at
2236: which any one or more of this segment's Counter32 or
2237: Counter64 suffered a discontinuity. If no such
2238: discontinuities have occurred since the last re-
2239: initialization of the local management subsystem, then
2240: this object contains a zero value."
2241:
2242: Danenberg et al Expires December 2004 45
2242: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
2243: Internet Draft PW CEP MIB June 2004
2244:
2245: ::= { pwVcCepPerfTotalEntry 20 }
2245: warning -
warning: flushing recent incorrect declaration, see previous error(s)
2246:
2247: -- End of PW CEP Total Performance table
2248:
2249:
2250: -- Conformance Configuration table
2251:
2252: pwVcCepConformanceCfgTable OBJECT-TYPE
2253: SYNTAX SEQUENCE OF PwVcCepConformanceCfgEntry
2254: MAX-ACCESS not-accessible
2255: STATUS current
2256: DESCRIPTION
2257: "This table provides the means for the agent to
2258: declare whether certain CEP PW statistics objects
2259: are supported (conformed to) or not. If not
2260: supported, then the object MUST be return 0."
2261: ::= { pwVcCepObjects 9 }
2262:
2263: pwVcCepConformanceCfgEntry OBJECT-TYPE
2264: SYNTAX PwVcCepConformanceCfgEntry
2265: MAX-ACCESS not-accessible
2266: STATUS current
2267: DESCRIPTION
2268: "The agent MUST create a single entry in this table."
2269:
2270: INDEX { pwVcCepConformanceCfgIndex }
2270: severe -
unknown object identifier label `pwVcCepConformanceCfgIndex'
2270: error -
index element `pwVcCepConformanceCfgIndex' of row `pwVcCepConformanceCfgEntry' must have a range restriction
2271:
2272: ::= { pwVcCepConformanceCfgTable 1 }
2273:
2274: PwVcCepConformanceCfgEntry ::= SEQUENCE {
2274: minor error -
SEQUENCE element #1 `pwVcCepConformanceCfgIndex' is not a child node under `pwVcCepConformanceCfgEntry'
2274: warning -
warning: SEQUENCE element #2 `pwVcCepPerfDbaInPacketsHCTruth' does not match order of columnar objects under `pwVcCepConformanceCfgEntry'
2275: pwVcCepConformanceCfgIndex INTEGER,
2276:
2277: pwVcCepPerfDbaInPacketsHCTruth TruthValue,
2278: pwVcCepPerfDbaInPacketsHCDesc SnmpAdminString,
2279:
2280: pwVcCepPerfDbaOutPacketsHCTruth TruthValue,
2281: pwVcCepPerfDbaOutPacketsHCDesc SnmpAdminString,
2282:
2283: pwVcCepPerfPktsOoseqTruth TruthValue,
2284: pwVcCepPerfPktsOoseqDesc SnmpAdminString,
2285:
2286: pwVcCepPerfPktsOoRngDroppedTruth TruthValue,
2287: pwVcCepPerfPktsOoRngDroppedDesc SnmpAdminString,
2288:
2289: pwVcCepPerfSummaryErrorsTruth TruthValue,
2290: pwVcCepPerfSummaryErrorsDesc SnmpAdminString
2291:
2292: }
2293:
2294: pwVcCepConformanceCfgIndex OBJECT-TYPE
2295: SYNTAX INTEGER (0..128)
2295: warning -
warning: use Integer32 instead of INTEGER in SMIv2
2296: MAX-ACCESS not-accessible
2297: STATUS current
2298: DESCRIPTION
2299:
2300: Danenberg et al Expires December 2004 46
2300: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting QUOTED_STRING
2301: Internet Draft PW CEP MIB June 2004
2302:
2303: "Any arbitrary number"
2304: ::= { pwVcCepConformanceCfgEntry 1 }
2304: warning -
warning: flushing recent incorrect declaration, see previous error(s)
2305:
2306: pwVcCepPerfDbaInPacketsHCTruth OBJECT-TYPE
2307: SYNTAX TruthValue
2308: MAX-ACCESS read-only
2309: STATUS current
2310: DESCRIPTION
2311: "Tells whether the pwVcCepPerf...DbaInPacketsHC
2312: in the pwVcCepPerf...Table is supported."
2313: ::= { pwVcCepConformanceCfgEntry 2 }
2314:
2315: pwVcCepPerfDbaInPacketsHCDesc OBJECT-TYPE
2316: SYNTAX SnmpAdminString
2317: MAX-ACCESS read-only
2318: STATUS current
2319: DESCRIPTION
2320: "Explanation for pwVcCepPerf...DbaInPacketsHC
2321: support in the pwVcCepPerf...Table."
2322: ::= { pwVcCepConformanceCfgEntry 3 }
2323:
2324: pwVcCepPerfDbaOutPacketsHCTruth OBJECT-TYPE
2325: SYNTAX TruthValue
2326: MAX-ACCESS read-only
2327: STATUS current
2328: DESCRIPTION
2329: "Tells whether the pwVcCepPerf...DbaOutPacketsHC
2330: in the pwVcCepPerf...Table is supported."
2331: ::= { pwVcCepConformanceCfgEntry 4 }
2332:
2333: pwVcCepPerfDbaOutPacketsHCDesc OBJECT-TYPE
2334: SYNTAX SnmpAdminString
2335: MAX-ACCESS read-only
2336: STATUS current
2337: DESCRIPTION
2338: "Explanation for pwVcCepPerf...DbaOutPacketsHC
2339: support in the pwVcCepPerf...Table."
2340: ::= { pwVcCepConformanceCfgEntry 5 }
2341:
2342: pwVcCepPerfPktsOoseqTruth OBJECT-TYPE
2343: SYNTAX TruthValue
2344: MAX-ACCESS read-only
2345: STATUS current
2346: DESCRIPTION
2347: "Tells whether the pwVcCepPerf...PktsOoseq
2348: in the pwVcCepPerf...Table is supported."
2349: ::= { pwVcCepConformanceCfgEntry 6 }
2350:
2351: pwVcCepPerfPktsOoseqDesc OBJECT-TYPE
2352: SYNTAX SnmpAdminString
2353: MAX-ACCESS read-only
2354: STATUS current
2355: DESCRIPTION
2356: "Explanation for pwVcCepPerf...PktsOoseq
2357:
2358: Danenberg et al Expires December 2004 47
2359: Internet Draft PW CEP MIB June 2004
2360:
2361: support in the pwVcCepPerf...Table."
2362: ::= { pwVcCepConformanceCfgEntry 7 }
2363:
2364: pwVcCepPerfPktsOoRngDroppedTruth OBJECT-TYPE
2365: SYNTAX TruthValue
2366: MAX-ACCESS read-only
2367: STATUS current
2368: DESCRIPTION
2369: "Tells whether the pwVcCepPerf...PktsOoRngDropped
2370: in the pwVcCepPerf...Table is supported."
2371: ::= { pwVcCepConformanceCfgEntry 8 }
2372:
2373: pwVcCepPerfPktsOoRngDroppedDesc OBJECT-TYPE
2374: SYNTAX SnmpAdminString
2375: MAX-ACCESS read-only
2376: STATUS current
2377: DESCRIPTION
2378: "Explanation for pwVcCepPerf...PktsOoRngDropped
2379: support in the pwVcCepPerf...Table."
2380: ::= { pwVcCepConformanceCfgEntry 9 }
2381:
2382:
2383: pwVcCepPerfSummaryErrorsTruth OBJECT-TYPE
2384: SYNTAX TruthValue
2385: MAX-ACCESS read-only
2386: STATUS current
2387: DESCRIPTION
2388: "Tells whether the pwVcCepPerf...SummaryError
2389: in the pwVcCepPerf...Table is supported."
2390: ::= { pwVcCepConformanceCfgEntry 10 }
2391:
2392: pwVcCepPerfSummaryErrorsDesc OBJECT-TYPE
2393: SYNTAX SnmpAdminString
2394: MAX-ACCESS read-only
2395: STATUS current
2396: DESCRIPTION
2397: "Explanation for pwVcCepPerf...SummaryError
2398: support in the pwVcCepPerf...Table."
2399: ::= { pwVcCepConformanceCfgEntry 11 }
2400:
2401: -- End of CEP PW Conformance Configuration table
2402:
2403:
2404: -- Conformance Information
2405:
2406: -- Note: Conformance at the object access and values level is
2407: -- still FFS, therefore current conformance is defined at the
2408: -- object existence level only.
2409:
2410: pwVcCepGroups OBJECT IDENTIFIER ::= { pwVcCepConformance 1 }
2411: pwVcCepCompliances OBJECT IDENTIFIER ::= { pwVcCepConformance 2 }
2412:
2413:
2414: pwCepModuleCompliance MODULE-COMPLIANCE
2415:
2416: Danenberg et al Expires December 2004 48
2416: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
2417: Internet Draft PW CEP MIB June 2004
2418:
2419: STATUS current
2420: DESCRIPTION
2421: "The compliance statement for agent that support PW
2422: over CEP PSN operation."
2423:
2424: MODULE -- this module
2425: MANDATORY-GROUPS { pwVcCepGroup,
2426: pwVcCepCfgGroup,
2427: pwVcCepPerfCurrentGroup,
2428: pwVcCepPerfIntervalGroup,
2429: pwVcCepPerfTotalGroup,
2430: pwVcCepConformanceCfgGroup
2431: }
2431: warning -
warning: flushing recent incorrect declaration, see previous error(s)
2432: ::= { pwVcCepCompliances 1 }
2432: severe -
syntax error, unexpected COLON_COLON_EQUAL
2432: warning -
warning: flushing recent incorrect declaration, see previous error(s)
2433:
2434: -- Units of conformance.
2435:
2436: pwVcCepGroup OBJECT-GROUP
2436: warning -
warning: current group `pwVcCepGroup' is not referenced in this module
2437: OBJECTS {
2438: pwVcCepType,
2439: pwVcCepSonetIfIndex,
2440: pwVcCepSonetTimeSlot,
2441: pwVcCepSonetConfigError,
2442: pwVcCepCfgIndex,
2443: pwVcCepTimeElapsed,
2444: pwVcCepValidIntervals,
2445: pwVcCepCurrentIndications,
2446: pwVcCepLatchedIndications,
2447: pwVcCepLastEsTimeStamp,
2448: pwVcCepPeerCepOption
2449: }
2450: STATUS current
2451: DESCRIPTION
2452: "Collection of objects for basic CEP PW config and
2453: status."
2454: ::= { pwVcCepGroups 1 }
2455:
2456:
2457: pwVcCepCfgGroup OBJECT-GROUP
2457: warning -
warning: current group `pwVcCepCfgGroup' is not referenced in this module
2458: OBJECTS {
2459: pwVcCepCfgIndexNext,
2460:
2461: pwVcCepConfigError,
2462:
2463: pwVcCepSonetPayloadLength,
2464: pwVcCepCfgMinPktLength,
2465: pwVcCepCfgPktReorder,
2466: pwVcCepCfgEnableDBA,
2467:
2468: pwVcCepCfgRtpHdrSuppress,
2469:
2470: pwVcCepCfgJtrBfrDepth,
2471:
2472: pwVcCepCfgConsecPktsInsync,
2473:
2474: Danenberg et al Expires December 2004 49
2474: error -
`Danenberg' should start with a lower case letter
2474: error -
Object identifier element `et' name only allowed as first element
2474: error -
Object identifier element `al' name only allowed as first element
2474: error -
`Expires' should start with a lower case letter
2474: error -
Object identifier element `Expires' name only allowed as first element
2474: error -
`December' should start with a lower case letter
2474: error -
Object identifier element `December' name only allowed as first element
2474: severe -
unknown object identifier label `Danenberg'
2474: severe -
unknown object identifier label `et'
2474: severe -
unknown object identifier label `al'
2474: severe -
unknown object identifier label `Expires'
2474: severe -
unknown object identifier label `December'
2474: warning -
warning: implicit node definition
2474: warning -
warning: implicit node definition
2475: Internet Draft PW CEP MIB June 2004
2475: error -
`Internet' should start with a lower case letter
2475: error -
Object identifier element `Internet' name only allowed as first element
2475: error -
`Draft' should start with a lower case letter
2475: error -
Object identifier element `Draft' name only allowed as first element
2475: error -
`PW' should start with a lower case letter
2475: error -
Object identifier element `PW' name only allowed as first element
2475: error -
`CEP' should start with a lower case letter
2475: error -
Object identifier element `CEP' name only allowed as first element
2475: error -
`MIB' should start with a lower case letter
2475: error -
Object identifier element `MIB' name only allowed as first element
2475: error -
`June' should start with a lower case letter
2475: error -
Object identifier element `June' name only allowed as first element
2475: severe -
unknown object identifier label `Internet'
2475: severe -
unknown object identifier label `Draft'
2475: severe -
unknown object identifier label `PW'
2475: severe -
unknown object identifier label `CEP'
2475: severe -
unknown object identifier label `MIB'
2475: severe -
unknown object identifier label `June'
2475: warning -
warning: implicit node definition
2476:
2477: pwVcCepCfgConsecMissingOutSync,
2477: error -
Object identifier element `pwVcCepCfgConsecMissingOutSync' name only allowed as first element
2478:
2479: pwVcCepCfgPktErrorPlayOutValue,
2480:
2481: pwVcCepCfgMissingPktsToSes,
2482: pwVcCepCfgSesToUas,
2483: pwVcCepCfgSecsToExitUas,
2484:
2485: pwVcCepCfgRowStatus,
2486: pwVcCepCfgStorageType
2487: }
2488: STATUS current
2489: DESCRIPTION
2490: "Collection of detailed objects needed to
2491: configure CEP PWs."
2492: ::= { pwVcCepGroups 2 }
2493:
2494:
2495: pwVcCepPerfCurrentGroup OBJECT-GROUP
2495: warning -
warning: current group `pwVcCepPerfCurrentGroup' is not referenced in this module
2496: OBJECTS {
2497: pwVcCepPerfCurrentDbaInPacketsHC,
2498: pwVcCepPerfCurrentDbaOutPacketsHC,
2499:
2500: pwVcCepPerfCurrentInNegPtrAdjust,
2501: pwVcCepPerfCurrentInPosPtrAdjust,
2502: pwVcCepPerfCurrentInPtrAdjustSecs,
2503: pwVcCepPerfCurrentOutNegPtrAdjust,
2504: pwVcCepPerfCurrentOutPosPtrAdjust,
2505: pwVcCepPerfCurrentOutPtrAdjustSecs,
2506: pwVcCepPerfCurrentAbsPtrAdjust,
2507:
2508: pwVcCepPerfCurrentMissingPkts,
2509: pwVcCepPerfCurrentPktsOoseq,
2510: pwVcCepPerfCurrentPktsOoRngDropped,
2511: pwVcCepPerfCurrentJtrBfrUnderruns,
2512: pwVcCepPerfCurrentPktsBadLength,
2513: pwVcCepPerfCurrentSummaryErrors,
2514:
2515: pwVcCepPerfCurrentESs,
2515: severe -
unknown object identifier label `pwVcCepPerfCurrentESs'
2516: pwVcCepPerfCurrentSESs,
2517: pwVcCepPerfCurrentUASs,
2518: pwVcCepPerfCurrentFC
2519: }
2520: STATUS current
2521: DESCRIPTION
2522: "Collection of statistics objects for CEP PWs."
2523: ::= { pwVcCepGroups 3 }
2524:
2525:
2526: pwVcCepPerfIntervalGroup OBJECT-GROUP
2526: warning -
warning: current group `pwVcCepPerfIntervalGroup' is not referenced in this module
2527: OBJECTS {
2528: pwVcCepPerfIntervalValidData,
2529: pwVcCepPerfIntervalReset,
2530: pwVcCepPerfIntervalTimeElapsed,
2531:
2532: Danenberg et al Expires December 2004 50
2532: error -
`Danenberg' should start with a lower case letter
2532: error -
Object identifier element `et' name only allowed as first element
2532: error -
Object identifier element `al' name only allowed as first element
2532: error -
`Expires' should start with a lower case letter
2532: error -
Object identifier element `Expires' name only allowed as first element
2532: error -
`December' should start with a lower case letter
2532: error -
Object identifier element `December' name only allowed as first element
2532: warning -
warning: implicit node definition
2533: Internet Draft PW CEP MIB June 2004
2533: error -
`Internet' should start with a lower case letter
2533: error -
Object identifier element `Internet' name only allowed as first element
2533: error -
`Draft' should start with a lower case letter
2533: error -
Object identifier element `Draft' name only allowed as first element
2533: error -
`PW' should start with a lower case letter
2533: error -
Object identifier element `PW' name only allowed as first element
2533: error -
`CEP' should start with a lower case letter
2533: error -
Object identifier element `CEP' name only allowed as first element
2533: error -
`MIB' should start with a lower case letter
2533: error -
Object identifier element `MIB' name only allowed as first element
2533: error -
`June' should start with a lower case letter
2533: error -
Object identifier element `June' name only allowed as first element
2534:
2535:
2536: pwVcCepPerfIntervalDbaInPacketsHC,
2536: error -
Object identifier element `pwVcCepPerfIntervalDbaInPacketsHC' name only allowed as first element
2537: pwVcCepPerfIntervalDbaOutPacketsHC,
2538:
2539: pwVcCepPerfIntervalInNegPtrAdjust,
2540: pwVcCepPerfIntervalInPosPtrAdjust,
2541: pwVcCepPerfIntervalInPtrAdjustSecs,
2542: pwVcCepPerfIntervalOutNegPtrAdjust,
2543: pwVcCepPerfIntervalOutPosPtrAdjust,
2544: pwVcCepPerfIntervalOutPtrAdjustSecs,
2545: pwVcCepPerfIntervalAbsPtrAdjust,
2546:
2547: pwVcCepPerfIntervalMissingPkts,
2548: pwVcCepPerfIntervalPktsOoseq,
2549: pwVcCepPerfIntervalPktsOoRngDropped,
2550: pwVcCepPerfIntervalJtrBfrUnderruns,
2551: pwVcCepPerfIntervalPktsBadLength,
2552: pwVcCepPerfIntervalSummaryErrors,
2553:
2554: pwVcCepPerfIntervalESs,
2555: pwVcCepPerfIntervalSESs,
2556: pwVcCepPerfIntervalUASs,
2557: pwVcCepPerfIntervalFC
2558:
2559: }
2560: STATUS current
2561: DESCRIPTION
2562: "Collection of statistics objects for CEP PWs."
2563: ::= { pwVcCepGroups 4 }
2564:
2565:
2566: pwVcCepPerfTotalGroup OBJECT-GROUP
2566: warning -
warning: current group `pwVcCepPerfTotalGroup' is not referenced in this module
2567: OBJECTS {
2568: pwVcCepPerfTotalDbaInPacketsHC,
2569: pwVcCepPerfTotalDbaOutPacketsHC,
2570:
2571: pwVcCepPerfTotalInNegPtrAdjust,
2572: pwVcCepPerfTotalInPosPtrAdjust,
2573: pwVcCepPerfTotalInPtrAdjustSecs,
2574: pwVcCepPerfTotalOutNegPtrAdjust,
2575: pwVcCepPerfTotalOutPosPtrAdjust,
2576: pwVcCepPerfTotalOutPtrAdjustSecs,
2577: pwVcCepPerfTotalAbsPtrAdjust,
2578:
2579: pwVcCepPerfTotalMissingPkts,
2580: pwVcCepPerfTotalPktsOoseq,
2580: severe -
unknown object identifier label `pwVcCepPerfTotalPktsOoseq'
2581: pwVcCepPerfTotalPktsOoRngDropped,
2582: pwVcCepPerfTotalJtrBfrUnderruns,
2583: pwVcCepPerfTotalPktsBadLength,
2584: pwVcCepPerfTotalSummaryErrors,
2585:
2586: pwVcCepPerfTotalESs,
2586: severe -
unknown object identifier label `pwVcCepPerfTotalESs'
2587: pwVcCepPerfTotalSESs,
2588: pwVcCepPerfTotalUASs,
2589:
2590: Danenberg et al Expires December 2004 51
2590: error -
`Danenberg' should start with a lower case letter
2590: error -
Object identifier element `et' name only allowed as first element
2590: error -
Object identifier element `al' name only allowed as first element
2590: error -
`Expires' should start with a lower case letter
2590: error -
Object identifier element `Expires' name only allowed as first element
2590: error -
`December' should start with a lower case letter
2590: error -
Object identifier element `December' name only allowed as first element
2590: warning -
warning: implicit node definition
2591: Internet Draft PW CEP MIB June 2004
2591: error -
`Internet' should start with a lower case letter
2591: error -
Object identifier element `Internet' name only allowed as first element
2591: error -
`Draft' should start with a lower case letter
2591: error -
Object identifier element `Draft' name only allowed as first element
2591: error -
`PW' should start with a lower case letter
2591: error -
Object identifier element `PW' name only allowed as first element
2591: error -
`CEP' should start with a lower case letter
2591: error -
Object identifier element `CEP' name only allowed as first element
2591: error -
`MIB' should start with a lower case letter
2591: error -
Object identifier element `MIB' name only allowed as first element
2591: error -
`June' should start with a lower case letter
2591: error -
Object identifier element `June' name only allowed as first element
2592:
2593: pwVcCepPerfTotalFC,
2593: error -
Object identifier element `pwVcCepPerfTotalFC' name only allowed as first element
2594: pwVcCepPerfTotalDiscontinuityTime
2595: }
2595: severe -
unknown object identifier label `pwVcCepPerfTotalDiscontinuityTime'
2596: STATUS current
2597: DESCRIPTION
2598: "Collection of statistics objects for CEP PWs."
2599: ::= { pwVcCepGroups 5 }
2600:
2601:
2602: pwVcCepFracGroup OBJECT-GROUP
2602: warning -
warning: current group `pwVcCepFracGroup' is not referenced in this module
2603: OBJECTS {
2604: pwVcCepFracMode,
2605: pwVcCepFracConfigError,
2606: pwVcCepFracAsync,
2607: pwVcCepFracVtgMap,
2608: pwVcCepFracEbm,
2609: pwVcCepFracPeerEbm,
2610: pwVcCepFracSdhVc4Mode,
2611: pwVcCepFracSdhVc4Tu3Map1,
2612: pwVcCepFracSdhVc4Tu3Map2,
2613: pwVcCepFracSdhVc4Tu3Map3,
2614: pwVcCepFracSdhVc4Tug2Map1,
2615: pwVcCepFracSdhVc4Tug2Map2,
2616: pwVcCepFracSdhVc4Tug2Map3,
2617: pwVcCepFracSdhVc4Ebm1,
2618: pwVcCepFracSdhVc4Ebm2,
2619: pwVcCepFracSdhVc4Ebm3,
2620: pwVcCepFracSdhVc4PeerEbm1,
2621: pwVcCepFracSdhVc4PeerEbm2,
2622: pwVcCepFracSdhVc4PeerEbm3,
2623: pwVcCepFracRowStatus,
2624: pwVcCepFracStorageType
2625: }
2626: STATUS current
2627: DESCRIPTION
2628: "Collection of fractional SPE groups. These objects are
2629: optional and should be supported only if fractional SPE
2630: is supported within the network element. "
2631: ::= { pwVcCepGroups 6 }
2632:
2633: pwVcCepConformanceCfgGroup OBJECT-GROUP
2633: warning -
warning: current group `pwVcCepConformanceCfgGroup' is not referenced in this module
2634: OBJECTS {
2635: pwVcCepPerfDbaInPacketsHCTruth,
2636: pwVcCepPerfDbaInPacketsHCDesc,
2637:
2638: pwVcCepPerfDbaOutPacketsHCTruth,
2639: pwVcCepPerfDbaOutPacketsHCDesc,
2640:
2641: pwVcCepPerfPktsOoseqTruth,
2642: pwVcCepPerfPktsOoseqDesc,
2643:
2644: pwVcCepPerfPktsOoRngDroppedTruth,
2645: pwVcCepPerfPktsOoRngDroppedDesc,
2646:
2647:
2648: Danenberg et al Expires December 2004 52
2648: error -
`Danenberg' should start with a lower case letter
2648: error -
Object identifier element `et' name only allowed as first element
2648: error -
Object identifier element `al' name only allowed as first element
2648: error -
`Expires' should start with a lower case letter
2648: error -
Object identifier element `Expires' name only allowed as first element
2648: error -
`December' should start with a lower case letter
2648: error -
Object identifier element `December' name only allowed as first element
2648: warning -
warning: implicit node definition
2649: Internet Draft PW CEP MIB June 2004
2649: error -
`Internet' should start with a lower case letter
2649: error -
Object identifier element `Internet' name only allowed as first element
2649: error -
`Draft' should start with a lower case letter
2649: error -
Object identifier element `Draft' name only allowed as first element
2649: error -
`PW' should start with a lower case letter
2649: error -
Object identifier element `PW' name only allowed as first element
2649: error -
`CEP' should start with a lower case letter
2649: error -
Object identifier element `CEP' name only allowed as first element
2649: error -
`MIB' should start with a lower case letter
2649: error -
Object identifier element `MIB' name only allowed as first element
2649: error -
`June' should start with a lower case letter
2649: error -
Object identifier element `June' name only allowed as first element
2650:
2651: pwVcCepPerfSummaryErrorsTruth,
2651: error -
Object identifier element `pwVcCepPerfSummaryErrorsTruth' name only allowed as first element
2652: pwVcCepPerfSummaryErrorsDesc
2653: }
2654: STATUS current
2655: DESCRIPTION
2656: "Collection of objects declaring conformance to
2657: other objects."
2658: ::= { pwVcCepGroups 7 }
2659:
2660:
2661: END
2661: error -
missing MODULE-IDENTITY clause in SMIv2 MIB
2662:
2663: --
2664: -- "Copyright (C) The Internet Society (2001). All Rights Reserved. This
2665: -- document and translations of it may be copied and furnished to
2666: -- others, and derivative works that comment on or otherwise explain it
2667: -- or assist in its implementation may be prepared, copied, published
2668: -- and distributed, in whole or in part, without restriction of any
2669: -- kind, provided that the above copyright notice and this paragraph are
2670: -- included on all such copies and derivative works. However, this
2671: -- document itself may not be modified in any way, such as by removing
2672: -- the copyright notice or references to the Internet Society or other
2673: -- Internet organizations, except as needed for the purpose of
2674: -- developing Internet standards in which case the procedures for
2675: -- copyrights defined in the Internet Standards process must be
2676: -- followed, or as required to translate it into languages other than
2677: -- English.
2678: --
2679: -- The limited permissions granted above are perpetual and will not be
2680: -- revoked by the Internet Society or its successors or assigns.
2681: --
2682: -- This document and the information contained herein is provided on an
2683: -- "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
2684: -- TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
2685: -- BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
2686: -- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
2687: -- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
2688: --
2689: