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