smilint output for ./PW-SATOP-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| severe | 1 |
| error | 5 |
| minor error | 1 |
| Message Types |
|---|
| Type | Count |
|---|
| basetype-unknown (error) | 2 |
| import-failed (error) | 1 |
| index-illegal-basetype (severe) | 1 |
| object-identifier-not-prefix (error) | 1 |
| revision-missing (minor error) | 1 |
| type-unknown (error) | 1 |
Messages:
PW-SATOP-MIB
1: -- extracted from draft-ietf-pwe3-satop-mib-03.txt
2: -- at Tue Apr 12 06:24:19 2005
3:
4: PW-SATOP-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE,
8: Unsigned32
9: FROM SNMPv2-SMI
10:
11: MODULE-COMPLIANCE, OBJECT-GROUP
12: FROM SNMPv2-CONF
13:
14: RowStatus, StorageType
15: FROM SNMPv2-TC
16:
17: pwStdMIB
18: FROM PW-TC-DRAFT04-MIB
19:
20: PwVcTDMCfgIndex
21: FROM PW-TDM-MIB;
21: error -
identifier `PwVcTDMCfgIndex' cannot be imported from module `PW-TDM-MIB'
22:
23:
24: -- The SAToP MIB
25: pwVcSatopMIB MODULE-IDENTITY
26:
27: LAST-UPDATED "200407180000Z"
28: ORGANIZATION "Pseudo-Wire Emulation Edge-to-Edge (PWE3)
29: Working Group"
30: CONTACT-INFO
31: " Orly Nicklass
32: Postal: RAD Data Communications
33: 24 Raoul Wallenberg St., Bldg C
34: Tel Aviv 69719, Israel
35: Email: orly_n@rad.com
36:
37: The PWE3 Working Group (email distribution pwe3@ietf.org,
38: http://www.ietf.org/html.charters/pwe3-charter.html)
39: "
40:
41: DESCRIPTION
42: "This MIB contains managed object definitions for
43: encapsulating TDM bit-streams (T1,E1, T3, E3) as
44: pseudo-wires over packet-switching networks (PSN).
45: as in: Structure- Agnostic TDM over Packet [SATOP].
46:
47: This MIB reports to the PW-STD-MIB as in: Zelig, D., Nadeau,
48: T. 'Pseudo Wire (PW) Management Information Base'. The
49: PW-STD-MIB contains structures and MIB associations generic
50: to Pseudo-Wire (PW) emulation. PW-specific
51: MIBs (such as this) contain config and stats for specific
52: PW types.
53:
54: Copyright (C) The Internet Society (2004). This version
55: of this MIB module is part of RFC yyyy; see the RFC
56: itself for full legal notices.
57: -- RFC Ed.: replace yyyy with actual RFC number & remove this note
58: "
59: ::= { pwStdMIB x } --To be assigned by IANA
59: minor error -
revision for last update is missing
59: error -
Object identifier element `x' name only allowed as first element
60: -- we request to assign value 6
61:
62: -- Tables, Scalars
63: pwVcSatopObjects OBJECT IDENTIFIER
64: ::= { pwVcSatopMIB 1 }
65: -- Notifications
66: pwVcSatopTraps OBJECT IDENTIFIER
67: ::= { pwVcSatopMIB 2 }
68:
69: -- Conformance
70: pwVcSatopConformance OBJECT IDENTIFIER
71: ::= { pwVcSatopMIB 3 }
72:
73: -- Obtain index for PW SAToP Configuration table entries
74:
75: pwVcSatopCfgIndexNext OBJECT-TYPE
75: error -
type `PwVcTDMCfgIndex' of node `pwVcSatopCfgIndexNext' does not resolve to a known base type
76: SYNTAX PwVcTDMCfgIndex
77: MAX-ACCESS read-only
77: error -
unknown type `PwVcTDMCfgIndex'
78: STATUS current
79: DESCRIPTION
80: "This object contains the value to be used for
81: pwVcSatopCfgIndex when creating entries in the
82: pwVcSatopCfgTable. The value 0 indicates that no
83: unassigned entries are available. To obtain the
84: value of pwVcSatopCfgIndex for a new entry in the
85: pwVcSatopCfgTable, the manager issues a management
86: protocol retrieval operation to obtain the current
87: value of pwVcSatopCfgIndex. After each retrieval
88: operation, the agent should modify the value to
89: reflect the next unassigned index. After a manager
90: retrieves a value the agent will determine through
91: its local policy when this index value will be made
92: available for reuse."
93: ::= { pwVcSatopObjects 1 }
94:
95: -- PW SAToP PW Configuration Table
96:
97: pwVcSatopCfgTable OBJECT-TYPE
98: SYNTAX SEQUENCE OF PwVcSatopCfgEntry
99: MAX-ACCESS not-accessible
100: STATUS current
101: DESCRIPTION
102: "This table contains a set of parameters that may be
103: referenced by one or more SAToP PWs in pwVcTDMTable."
104: REFERENCE
105: "See [PWTDMMIB]"
106:
107: ::= { pwVcSatopObjects 2 }
108:
109: pwVcSatopCfgEntry OBJECT-TYPE
109: severe -
illegal base type `PwVcTDMCfgIndex' in index element `pwVcSatopCfgIndex' of row pwVcSatopCfgEntry
110: SYNTAX PwVcSatopCfgEntry
111: MAX-ACCESS not-accessible
112: STATUS current
113: DESCRIPTION
114: "These parameters define the characteristics of a
115: SAToP PW. They are grouped here to ease NMS burden.
116: Once an entry is created here it may be re-used
117: by many PWs."
118:
119: INDEX { pwVcSatopCfgIndex }
120: ::= { pwVcSatopCfgTable 1 }
121:
122: PwVcSatopCfgEntry ::= SEQUENCE {
123: pwVcSatopCfgIndex PwVcTDMCfgIndex,
124: pwVcSatopCfgRowStatus RowStatus,
125:
126: pwVcSatopCfgConsecPktsLoss2Normal Unsigned32,
127: pwVcSatopCfgConsecMissPktNorma2Loss Unsigned32,
128:
129: pwVcSatopCfgPktReplacePolicy INTEGER,
130: pwVcSatopCfgTDMDataSetUp2Synch Unsigned32,
131: pwVcSatopCfgSetUp2SynchTimeOut Unsigned32,
132: pwVcSatopCfgAlarmThreshold Unsigned32,
133: pwVcSatopCfgClearAlarmThreshold Unsigned32,
134: pwVcSatopCfgExcessivePktLossThreshold Unsigned32,
135:
136: pwVcSatopCfgMissingPktsToSes Unsigned32,
137: pwVcSatopCfgTimestampMode INTEGER,
138: pwVcSatopCfgStorageType StorageType
139: }
140:
141: pwVcSatopCfgIndex OBJECT-TYPE
141: error -
type `PwVcTDMCfgIndex' of node `pwVcSatopCfgIndex' does not resolve to a known base type
142: SYNTAX PwVcTDMCfgIndex
143: MAX-ACCESS not-accessible
144: STATUS current
145: DESCRIPTION
146: "Primary index inthis table"
147: ::= { pwVcSatopCfgEntry 1 }
148:
149: pwVcSatopCfgRowStatus OBJECT-TYPE
150: SYNTAX RowStatus
151: MAX-ACCESS read-create
152: STATUS current
153: DESCRIPTION
154: "Object used for creating, modifying, and deleting
155: a row from this table."
156: ::= { pwVcSatopCfgEntry 2 }
157:
158: -- The following counters work together to integrate
159: -- errors and the lack of errors on the SAToP PW. An error is
160: -- caused by a missing packet. Missing packet can be a result
161: -- of: packet loss in the network, (uncorrectable) packet out
162: -- of sequence, packet length error, jitter buffer overflow,
163: -- and jitter buffer underflow. The result is declaring whether
164: -- or not the SAToP PW is in Loss of Packet (LOPS) state.
165: --
166: pwVcSatopCfgConsecPktsLoss2Normal OBJECT-TYPE
167: SYNTAX Unsigned32
168: MAX-ACCESS read-create
169: STATUS current
170: DESCRIPTION
171: "The number of consecutive packets with sequential
172: sequence numbers that are required to exit the
173: LOPS state."
174: REFERENCE
175: "See [SATOP]"
176: DEFVAL { 2 }
177: ::= { pwVcSatopCfgEntry 3 }
178:
179: pwVcSatopCfgConsecMissPktNorma2Loss OBJECT-TYPE
180: SYNTAX Unsigned32
181: MAX-ACCESS read-create
182: STATUS current
183: DESCRIPTION
184: " The number of consecutive missing packets that are
185: required to enter the LOPS state."
186: REFERENCE
187: "See [SATOP]"
188: DEFVAL { 10 }
189: ::= { pwVcSatopCfgEntry 4 }
190:
191: pwVcSatopCfgPktReplacePolicy OBJECT-TYPE
192: SYNTAX INTEGER
193: {
194: allOnes (1),
195: implementationSpecific(2)
196: }
197: MAX-ACCESS read-create
198: STATUS current
199: DESCRIPTION
200: "This is the value to be played when CE bound packets
201: have over/underflow the jitter buffer, or are missing
202: for any reason. This byte pattern is sent (played) on
203: the TDM line."
204: DEFVAL { 1 } -- Play all ones
205: ::= { pwVcSatopCfgEntry 5 }
206:
207: pwVcSatopCfgTDMDataSetUp2Synch OBJECT-TYPE
208: SYNTAX Unsigned32
209: MAX-ACCESS read-create
210: STATUS current
211: DESCRIPTION
212: "The SAToP IWF is in an intermediate state until this
213: amount of TDM data bytes (usually half of the jitter
214: buffer) has been received in consecutive SAToP packets.
215: default value is set for E1 line."
216:
217: DEFVAL {1400 }
218: ::= { pwVcSatopCfgEntry 6 }
219:
220: pwVcSatopCfgSetUp2SynchTimeOut OBJECT-TYPE
221: SYNTAX Unsigned32
222: MAX-ACCESS read-create
223: STATUS current
224: DESCRIPTION
225: "The intermediate state timer is set to this value. The SAToP
226: IWF is in an intermediate state until
227: pwVcSatopCfgTDMDataSetUp2Synch amount of TDM data bytes
228: has been received in consecutive SAToP packets or until this
229: timer expires. The timer units are (millisec)"
230: DEFVAL { 5}
231: ::= { pwVcSatopCfgEntry 7 }
232:
233: pwVcSatopCfgAlarmThreshold OBJECT-TYPE
234: SYNTAX Unsigned32
235: MAX-ACCESS read-create
236: STATUS current
237: DESCRIPTION
238: "Alarms are only reported when the defect state persists
239: for the length of time specified by this object.
240: The object's unit is millisec"
241: DEFVAL { 2500 }
242: ::= { pwVcSatopCfgEntry 8 }
243:
244: pwVcSatopCfgClearAlarmThreshold OBJECT-TYPE
245: SYNTAX Unsigned32
246: MAX-ACCESS read-create
247: STATUS current
248: DESCRIPTION
249: "Alarm MUST be cleared after the corresponding defect is
250: undetected for the amount of time specified by this object.
251: The object's unit is millisec"
252: DEFVAL { 10000 }
253: ::= { pwVcSatopCfgEntry 9 }
254:
255:
256: pwVcSatopCfgExcessivePktLossThreshold OBJECT-TYPE
257: SYNTAX Unsigned32
258: MAX-ACCESS read-create
259: STATUS current
260: DESCRIPTION
261: "Excessive packet loss rate is detected by computing the
262: average packetloss rate over a pwVcSatopCfgAvePktLossTimeWindow
263: amount of time and comparing it with this threshold value. "
264: ::= { pwVcSatopCfgEntry 10 }
265:
266: pwVcSatopCfgMissingPktsToSes OBJECT-TYPE
267: SYNTAX Unsigned32
268: UNITS "seconds"
269: MAX-ACCESS read-create
270: STATUS current
271: DESCRIPTION
272: "Number of missing packets detected (consecutive or not)
273: within a 1 second window to cause a Severely Error
274: Second (SES) to be counted."
275: DEFVAL { 3 }
276: ::= { pwVcSatopCfgEntry 11 }
277:
278: pwVcSatopCfgTimestampMode OBJECT-TYPE
279: SYNTAX INTEGER
280: {
281: notApplicable (1),
282: absolute (2),
283: differential (3)
284: }
285:
286: MAX-ACCESS read-create
287: STATUS current
288: DESCRIPTION
289: "Timestamp generation MAY be used in one of the following
290: modes:
291: 1. Absolute mode: the PSN-bound IWF sets timestamps
292: using the clock recovered from the incoming TDM attachment
293: circuit. As a consequence, the timestamps are closely
294: correlated with the sequence numbers. All SAToP implementations
295: that support usage of the RTP header MUST support this mode.
296: 2. Differential mode: Both IWFs have access to a common high-
297: quality timing source, and this source is used for timestamp
298: generation. Support of this mode is OPTIONAL. "
299:
300: ::= { pwVcSatopCfgEntry 12 }
301:
302: pwVcSatopCfgStorageType OBJECT-TYPE
303: SYNTAX StorageType
304: MAX-ACCESS read-create
305: STATUS current
306: DESCRIPTION
307: "This variable indicates the storage type for this
308: row."
309: ::= { pwVcSatopCfgEntry 13 }
310:
311: -- End of SAToP PW Configuration Parameter Table
312:
313: -- Conformance Information
314: pwVcSatopGroups OBJECT IDENTIFIER ::= { pwVcSatopConformance 1 }
315: pwVcSatopCompliances OBJECT IDENTIFIER ::= { pwVcSatopConformance 2 }
316:
317:
318: pwSatopModuleCompliance MODULE-COMPLIANCE
319: STATUS current
320: DESCRIPTION
321: "The compliance statement for agent that support Structure-
322: Agnostic TDM over PSN."
323:
324: MODULE -- this module
325: MANDATORY-GROUPS {
326: pwVcSatopCfgGroup
327: }
328:
329:
330: OBJECT pwVcSatopCfgConsecPktsLoss2Normal
331: MIN-ACCESS read-only
332: DESCRIPTION
333: "The ability to set this object is not
334: required."
335:
336:
337: OBJECT pwVcSatopCfgConsecMissPktNorma2Loss
338: MIN-ACCESS read-only
339: DESCRIPTION
340: "The ability to set this object is not
341: required."
342:
343: OBJECT pwVcSatopCfgPktReplacePolicy
344: MIN-ACCESS read-only
345: DESCRIPTION
346: "The ability to set this object is not
347: required."
348:
349: OBJECT pwVcSatopCfgTDMDataSetUp2Synch
350: MIN-ACCESS read-only
351: DESCRIPTION
352: "The ability to set this object is not
353: required."
354:
355: OBJECT pwVcSatopCfgSetUp2SynchTimeOut
356: MIN-ACCESS read-only
357: DESCRIPTION
358: "The ability to set this object is not
359: required."
360:
361: OBJECT pwVcSatopCfgExcessivePktLossThreshold
362: MIN-ACCESS read-only
363: DESCRIPTION
364: "The ability to set this object is not
365: required."
366:
367: OBJECT pwVcSatopCfgMissingPktsToSes
368: MIN-ACCESS read-only
369: DESCRIPTION
370: "The ability to set this object is not
371: required."
372:
373: OBJECT pwVcSatopCfgTimestampMode
374: MIN-ACCESS read-only
375: DESCRIPTION
376: "The ability to set this object is not
377: required."
378:
379:
380: ::= { pwVcSatopCompliances 1 }
381:
382: -- Units of conformance.
383:
384:
385: pwVcSatopCfgGroup OBJECT-GROUP
386: OBJECTS {
387: pwVcSatopCfgIndexNext,
388: pwVcSatopCfgRowStatus,
389:
390: pwVcSatopCfgConsecPktsLoss2Normal,
391: pwVcSatopCfgConsecMissPktNorma2Loss,
392:
393: pwVcSatopCfgPktReplacePolicy,
394: pwVcSatopCfgTDMDataSetUp2Synch,
395: pwVcSatopCfgSetUp2SynchTimeOut,
396: pwVcSatopCfgAlarmThreshold,
397: pwVcSatopCfgClearAlarmThreshold,
398: pwVcSatopCfgExcessivePktLossThreshold,
399:
400: pwVcSatopCfgMissingPktsToSes,
401: pwVcSatopCfgTimestampMode,
402: pwVcSatopCfgStorageType
403: }
404: STATUS current
405: DESCRIPTION
406: "Collection of detailed objects needed to
407: configure SAToP PWs."
408: ::= { pwVcSatopGroups 1 }
409:
410: END
411:
412: --
413: -- Copyright (C) The Internet Society (2005). This document is subject
414: -- to the rights, licenses and restrictions contained in BCP 78, and
415: -- except as set forth therein, the authors retain all their rights.
416: --
417: --
418: -- Acknowledgment
419: --
420: -- Funding for the RFC Editor function is currently provided by the
421: -- Internet Society.
422: