smilint output for ./PW-MPLS-DRAFT04-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| severe | 22 |
| error | 10 |
| minor error | 4 |
| change recommended | 7 |
| warning | 13 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 5 |
| group-membership (change recommended) | 7 |
| import-failed (error) | 1 |
| import-unused (warning) | 1 |
| internal-flushing (warning) | 10 |
| internal-other (severe) | 11 |
| module-identity-missing (error) | 1 |
| object-identifier-not-prefix (error) | 1 |
| object-identifier-unknown (severe) | 11 |
| parent-row (error) | 1 |
| sequence-no-column (minor error) | 4 |
| sequence-order (warning) | 2 |
| type-unknown (error) | 1 |
Messages:
PW-MPLS-DRAFT04-MIB
1: -- extracted from draft-ietf-pwe3-pw-mpls-mib-04.txt
2: -- at Wed Dec 24 06:16:16 2003
3:
4: PW-MPLS-DRAFT04-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: InterfaceIndexOrZero
18: FROM IF-MIB
19:
20: MplsTunnelIndex, MplsTunnelInstanceIndex,
21: MplsLdpIdentifier, MplsLsrIdentifier
22: FROM MPLS-TC-STD-MIB
23:
24: PwVcIndexType, pwStdMIB
24: warning -
warning: identifier `pwStdMIB' imported from module `PW-TC-DRAFT04-MIB' is never used
25: FROM PW-TC-DRAFT04-MIB
26:
27: pwVcIndex
28: FROM PW-DRAFT04-MIB
28: error -
identifier `pwVcIndex' cannot be imported from module `PW-DRAFT04-MIB'
29:
30: ;
31:
32: pwVcMplsMIB MODULE-IDENTITY
33: LAST-UPDATED "200311301200Z" -- 30 November 2003 12:00:00 EST
34: ORGANIZATION "Pseudo Wire Edge to Edge Emulation (PWE3) Working
35: Group"
36: CONTACT-INFO
37: "
38: David Zelig
39: Postal: Corrigent Systems
40: 126, Yigal Alon St.
41: Tel Aviv, ISRAEL
42: Phone: +972-3-6945273
43: E-mail: davidz@corrigent.com
44:
45: Thomas D. Nadeau
46: Postal: Cisco Systems, Inc.
47: 250 Apollo Drive
48: Chelmsford, MA 01824
49: Tel: +1-978-497-3051
50: Email: tnadeau@cisco.com
51:
52: Dave Danenberg
53: Pseudo Wire (PW) Over MPLS December 2003
54: Management Information Base
55:
56:
57: Postal: Litchfield Communications, Inc.
58: 76 Westbury Park Rd
59: Princeton Building East
60: Watertown, CT 06795
61: Tel: +1-860-945-1573 x3180
62: Email: dave_danenberg@litchfieldcomm.com
63:
64: Sharon Mantin
65: Postal: AxONLink (Israel) Ltd
66: 9 Bareket St.
67: Petah Tikva 49517, Israel
68: Tel: +972-3-9263972
69: Email: sharon.mantin@axonlink.com
70:
71: The PWE3 Working Group (email distribution pwe3@ietf.org,
72: http://www.ietf.org/html.charters/pwe3-charter.html)
73: "
74: DESCRIPTION
75: "This MIB complements the PW-STD-MIB for PW operation
76: over MPLS.
77:
78: Copyright (C) The Internet Society (date). This version
79: of this MIB module is part of RFC yyyy; see the RFC
80: itself for full legal notices.
81: -- RFC Ed.: replace yyyy with actual RFC number & remove this note
82: "
83:
84: -- Revision history.
85:
86: REVISION
87: "200311301200Z" -- 30 November 2003 12:00:00 EST
88: DESCRIPTION
89: "Draft-ietf-pwe3-pw-mpls-mib-04 version. Changes from
90: previous version:
91: 1) Adapting description to MIB boilerplate.
92: 2) Module OID changed to PWE3 tree.
93: 3) Sync descriptions of various items to table structure and
94: removing unnecessary references.
95: "
96: REVISION
97: "200307291200Z" -- 29 July 2003 12:00:00 EST
98: DESCRIPTION
99: "Draft-ietf-pwe3-pw-mpls-mib-02 version. Changes from
100: previous version:
101: 1) Removing inbound table (no strict mode and no knowledge
102: of inbound tunnel).
103: 2) Provisioning (i.e. RowCreate) done via mapping tables.
104: Outbound table is now read only for sorted search for
105: pwVcIndex.
106: "
107: Pseudo Wire (PW) Over MPLS December 2003
107: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
108: Management Information Base
109:
110:
111: REVISION
112: "200206021200Z" -- 02 June 2002 12:00:00 EST
113: DESCRIPTION
114: "Draft-ietf-pwe3-pw-mpls-mib-00 version. Changes from
115: previous version:
116: 1) Spliting the mapping table into two tables, one for
117: Non TE application and one for TE application.
118: 2) Object types alignment with MPLS MIBs.
119: "
120: REVISION
121: "200201291200Z" -- 29 January 2002 12:00:00 EST
122: DESCRIPTION
123: "Changes from previous version:
124: 1) Add LDP entity association.
125: 2) Clarify inbound/outbound directions.
126: 3) Simplify indexing of outbound and inbound tables
127: and providing get next variables.
128: "
129: REVISION
130: "200111071200Z" -- 7 November 2001 12:00:00 EST
131: DESCRIPTION
132: "Changes from previous version:
133: 1) Remove Vc instance from table indexing.
134: 2) Update descriptions of indexing and protection.
135: 3) Remove the need for MPLS-LSR in case of VC only.
136: 4) Change pwVcMplsMplsType to BITS in order to enable
137: multiple types of outer tunnel.
138: 5) Add ifindex to outer tunnel tables to support vcOnly
139: option.
140: 6) change naming of outbound, inbound and mapping tables to
141: reflect addition of VC only port ifindexes.
142: 7) Adapt order of items in mapping table to SNMP convention.
143: "
144: REVISION
145: "200107111200Z" -- July 11 2001 12:00:00 EST
146: DESCRIPTION
147: "draft-zelig-pw-mib-00.txt - initial version"
148:
149: ::= { pwStdMIB 3 } -- To be assigned by IANA
149: warning -
warning: flushing recent incorrect declaration, see previous error(s)
150:
151: -- Top-level components of this MIB.
152:
153: -- Tables, Scalars
154: pwVcMplsObjects OBJECT IDENTIFIER
155: ::= { pwVcMplsMIB 1 }
155: severe -
unknown object identifier label `pwVcMplsMIB'
156: -- Conformance
157: pwVcMplsConformance OBJECT IDENTIFIER
158: ::= { pwVcMplsMIB 2 }
159:
160: -- PW MPLS table
161: Pseudo Wire (PW) Over MPLS December 2003
161: error -
`Pseudo' should start with a lower case letter
161: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
162: Management Information Base
163:
164:
165: pwVcMplsTable OBJECT-TYPE
166: SYNTAX SEQUENCE OF PwVcMplsEntry
167: MAX-ACCESS not-accessible
168: STATUS current
169: DESCRIPTION
170: "This table controls MPLS specific parameters when the PW is
171: going to be carried over MPLS PSN."
172: ::= { pwVcMplsObjects 1 }
172: warning -
warning: flushing recent incorrect declaration, see previous error(s)
173:
174: pwVcMplsEntry OBJECT-TYPE
174: error -
row's parent node must be a table node
175: SYNTAX PwVcMplsEntry
176: MAX-ACCESS not-accessible
177: STATUS current
178: DESCRIPTION
179: "A row in this table represents parameters specific to MPLS
180: PSN for a pseudo wire (PW). The row is created
181: automatically by the local agent if the pwVcPsnType is
182: MPLS. It is indexed by pwVcIndex, which uniquely
183: identifying a singular PW.
184: "
185:
186: INDEX { pwVcIndex }
186: severe -
unknown object identifier label `pwVcIndex'
187:
188: ::= { pwVcMplsTable 1 }
188: severe -
unknown object identifier label `pwVcMplsTable'
189:
190: PwVcMplsEntry ::= SEQUENCE {
190: minor error -
SEQUENCE element #5 `pwVcMplsLocalLdpID' is not a child node under `pwVcMplsEntry'
190: warning -
warning: SEQUENCE element #6 `pwVcMplsLocalLdpEntityID' does not match order of columnar objects under `pwVcMplsEntry'
191: pwVcMplsMplsType BITS,
192: pwVcMplsExpBitsMode INTEGER,
193: pwVcMplsExpBits Unsigned32,
194: pwVcMplsTtl Unsigned32,
195: pwVcMplsLocalLdpID MplsLdpIdentifier,
195: severe -
unknown object identifier label `pwVcMplsLocalLdpID'
196: pwVcMplsLocalLdpEntityID Unsigned32,
197: pwVcMplsPeerLdpID MplsLdpIdentifier,
198: pwVcMplsStorageType StorageType
199: }
200:
201: pwVcMplsMplsType OBJECT-TYPE
201: change recommended -
warning: node `pwVcMplsMplsType' must be contained in at least one conformance group
202: SYNTAX BITS {
203: mplsTe (0),
204: mplsNonTe (1),
205: vcOnly (2)
206: }
207: MAX-ACCESS read-write
208: STATUS current
209: DESCRIPTION
210: "Set by the operator to indicate the outer tunnel types, if
211: exists. mplsTe is used if the outer tunnel was set-up by
212: MPLS-TE, and mplsNonTe is used the outer tunnel was set up
213: by LDP or manually. Combination of mplsTe and mplsNonTe
214: may exist in case of outer tunnel protection.
215: vcOnly is used if there is no outer tunnel label, i.e. in
216: Pseudo Wire (PW) Over MPLS December 2003
217: Management Information Base
218:
219:
220: static provisioning without MPLS tunnel. vcOnly
221: cannot be combined with mplsNonTe or mplsTe."
222: ::= { pwVcMplsEntry 1 }
223:
224:
225: pwVcMplsExpBitsMode OBJECT-TYPE
225: change recommended -
warning: node `pwVcMplsExpBitsMode' must be contained in at least one conformance group
226: SYNTAX INTEGER {
227: outerTunnel (1),
228: specifiedValue (2),
229: serviceDependant (3)
230: }
231:
232: MAX-ACCESS read-write
233: STATUS current
234: DESCRIPTION
235: "Set by the operator to indicate the way the PW shim label
236: EXP bits are to be determined. The value of outerTunnel(1)
237: is used where there is an outer tunnel - pwVcMplsMplsType
238: is mplsTe or mplsNonTe. Note that in this case there is no
239: need to mark the PW label with the EXP bits since the PW
240: label is not visible to the intermediate nodes.
241: If there is no outer tunnel, specifiedValue(2) indicate
242: that the value is specified by pwVcMplsExpBits, and
243: serviceDependant(3) indicate that the EXP bits are setup
244: based on a rule specified in the emulated service specific
245: tables, for example when the EXP bits are a function of
246: 802.1p marking for Ethernet emulated service."
247:
248: DEFVAL { outerTunnel }
249: ::= { pwVcMplsEntry 2 }
250:
251: pwVcMplsExpBits OBJECT-TYPE
251: change recommended -
warning: node `pwVcMplsExpBits' must be contained in at least one conformance group
252: SYNTAX Unsigned32 (0..7)
253: MAX-ACCESS read-write
254: STATUS current
255: DESCRIPTION
256: "Set by the operator to indicate the MPLS EXP bits to be
257: used on the PW shim label if pwVcMplsExpBitsMode is
258: specifiedValue(2), zero otherwise."
259: DEFVAL { 0 }
260: ::= { pwVcMplsEntry 3 }
261:
262: pwVcMplsTtl OBJECT-TYPE
262: change recommended -
warning: node `pwVcMplsTtl' must be contained in at least one conformance group
263: SYNTAX Unsigned32 (0..255)
264: MAX-ACCESS read-write
265: STATUS current
266: DESCRIPTION
267: "Set by the operator to indicate the PW TTL bits to be used
268: on the PW shim label."
269: DEFVAL { 2 }
270: ::= { pwVcMplsEntry 4 }
271: Pseudo Wire (PW) Over MPLS December 2003
271: error -
`Pseudo' should start with a lower case letter
271: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
272: Management Information Base
273:
274:
275:
276: pwVcMplsLocalLdpID OBJECT-TYPE
277: SYNTAX MplsLdpIdentifier
278: MAX-ACCESS read-write
279: STATUS current
280: DESCRIPTION
281: "The local LDP identifier of the LDP entity creating
282: this PW in the local node. As the PW labels are always
283: set from the per platform label space, the last two octets
284: in the LDP ID MUST be always both zeros."
285: REFERENCE
286: "'LDP specifications', RFC 3036 section 2.2.2."
287: ::= { pwVcMplsEntry 5 }
287: warning -
warning: flushing recent incorrect declaration, see previous error(s)
288:
289: pwVcMplsLocalLdpEntityID OBJECT-TYPE
289: change recommended -
warning: node `pwVcMplsLocalLdpEntityID' must be contained in at least one conformance group
290: SYNTAX Unsigned32
291: MAX-ACCESS read-write
292: STATUS current
293: DESCRIPTION
294: "The local node LDP Entity index of the LDP entity creating
295: this PW. Should be set to all zeros if not used."
296: ::= { pwVcMplsEntry 6 }
297:
298: pwVcMplsPeerLdpID OBJECT-TYPE
298: change recommended -
warning: node `pwVcMplsPeerLdpID' must be contained in at least one conformance group
299: SYNTAX MplsLdpIdentifier
300: MAX-ACCESS read-only
301: STATUS current
302: DESCRIPTION
303: "The peer LDP identifier as identified from the LDP
304: session. Should be zero if not relevant or not known yet."
305: ::= { pwVcMplsEntry 7 }
306:
307: pwVcMplsStorageType OBJECT-TYPE
307: change recommended -
warning: node `pwVcMplsStorageType' must be contained in at least one conformance group
308: SYNTAX StorageType
309: MAX-ACCESS read-write
310: STATUS current
311: DESCRIPTION
312: "This variable indicates the storage type for this row."
313: ::= { pwVcMplsEntry 8 }
314:
315: -- End of PW MPLS table
316:
317: -- Pseudo Wire MPLS Outbound Tunnel table
318:
319: pwVcMplsOutboundTable OBJECT-TYPE
320: SYNTAX SEQUENCE OF PwVcMplsOutboundEntry
321: MAX-ACCESS not-accessible
322: STATUS current
323: DESCRIPTION
324: "This table reports the association between PWs and the
325: outbound MPLS tunnels (i.e. toward the PSN) or the physical
326: Pseudo Wire (PW) Over MPLS December 2003
327: Management Information Base
328:
329:
330: interface in case of PW label only. The configuration of
331: the association is done in other tables."
332: ::= { pwVcMplsObjects 2 }
333:
334: pwVcMplsOutboundEntry OBJECT-TYPE
335: SYNTAX PwVcMplsOutboundEntry
336: MAX-ACCESS not-accessible
337: STATUS current
338: DESCRIPTION
339: "A row in this table indicate association between a PW (that
340: require MPLS tunnels) and MPLS tunnel toward the PSN.
341: In the case of PW only, it associates the PW with the
342: interface that shall carry the PW.
343: This table is indexed by the pwVcIndex and an additional
344: index enabling multiple rows (i.e. tunnels) for the same
345: pwVcindex.
346:
347: At least one entry is created in this table by the agent
348: for each PW that requires MPLS PSN.
349:
350: This table points to the appropriate MPLS MIB. In the case
351: of MPLS-TE, the 4 variables relevant to the indexing of
352: a TE MPLS tunnel are set as in Srinivasan, et al, <draft-
353: ietf-mpls-te-mib>.
354: In case of Non-TE MPLS (an outer tunnel label assigned by
355: LDP or manually) the table points to the XC entry in the
356: LSR MIB as in Srinivasan, et al, <draft-ietf-mpls-lsr-mib>.
357: In case of PW label only (no outer tunnel) the ifIndex of
358: the port to carry the PW is configured.
359:
360: Each PW may have multiple rows in this tables if protection
361: is available at the outer tunnel level. For a specific PW,
362: each row may be of different type except for PW lable only,
363: on which only rows with ifIndex of the port are allowed.
364: "
365:
366: INDEX { pwVcIndex, pwVcMplsOutboundIndex }
366: severe -
unknown object identifier label `pwVcMplsOutboundIndex'
367:
368: ::= { pwVcMplsOutboundTable 1 }
369:
370: PwVcMplsOutboundEntry ::= SEQUENCE {
370: minor error -
SEQUENCE element #1 `pwVcMplsOutboundIndex' is not a child node under `pwVcMplsOutboundEntry'
370: warning -
warning: SEQUENCE element #2 `pwVcMplsOutboundLsrXcIndex' does not match order of columnar objects under `pwVcMplsOutboundEntry'
371: pwVcMplsOutboundIndex Unsigned32,
372: pwVcMplsOutboundLsrXcIndex Unsigned32,
373: pwVcMplsOutboundTunnelIndex MplsTunnelIndex,
374: pwVcMplsOutboundTunnelInstance MplsTunnelInstanceIndex,
375: pwVcMplsOutboundTunnelLclLSR MplsLsrIdentifier,
376: pwVcMplsOutboundTunnelPeerLSR MplsLsrIdentifier,
376: severe -
unknown object identifier label `pwVcMplsOutboundTunnelPeerLSR'
377: pwVcMplsOutboundIfIndex InterfaceIndexOrZero
378: }
379:
380: pwVcMplsOutboundIndex OBJECT-TYPE
381: Pseudo Wire (PW) Over MPLS December 2003
381: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting SYNTAX
382: Management Information Base
383:
384:
385: SYNTAX Unsigned32 (0..4294967295)
386: MAX-ACCESS not-accessible
387: STATUS current
388: DESCRIPTION
389: "Arbitrary index for enabling multiple rows per PW in
390: this table. The numbering method is implementation
391: specific.
392: "
393: ::= { pwVcMplsOutboundEntry 1 }
393: warning -
warning: flushing recent incorrect declaration, see previous error(s)
394:
395: pwVcMplsOutboundLsrXcIndex OBJECT-TYPE
396: SYNTAX Unsigned32
397: MAX-ACCESS read-only
398: STATUS current
399: DESCRIPTION
400: "This object will be set by the operator. If the outer
401: label is defined in the MPLS-LSR-STD-MIB, i.e. set by LDP
402: or manually, this object points to the XC index
403: of the outer tunnel. Otherwise, it returns the value zero."
404: ::= { pwVcMplsOutboundEntry 2 }
405:
406:
407: pwVcMplsOutboundTunnelIndex OBJECT-TYPE
408: SYNTAX MplsTunnelIndex
409: MAX-ACCESS read-only
410: STATUS current
411: DESCRIPTION
412: "Part of set of indexes for outbound tunnel in the case of
413: MPLS-TE outer tunnel, otherwise returns the value zero."
414: ::= { pwVcMplsOutboundEntry 3 }
415:
416: pwVcMplsOutboundTunnelInstance OBJECT-TYPE
417: SYNTAX MplsTunnelInstanceIndex
418: MAX-ACCESS read-only
419: STATUS current
420: DESCRIPTION
421: "Part of set of indexes for outbound tunnel in the case of
422: MPLS-TE outer tunnel, otherwise returns the value zero."
423: ::= { pwVcMplsOutboundEntry 4 }
424:
425: pwVcMplsOutboundTunnelLclLSR OBJECT-TYPE
426: SYNTAX MplsLsrIdentifier
427: MAX-ACCESS read-only
428: STATUS current
429: DESCRIPTION
430: "Part of set of indexes for outbound tunnel in the case of
431: MPLS-TE outer tunnel, otherwise returns the value zero."
432: ::= { pwVcMplsOutboundEntry 5 }
433:
434: pwVcMplsOutboundTunnelPeerLSR OBJECT-TYPE
435: SYNTAX MplsLsrIdentifier
436: Pseudo Wire (PW) Over MPLS December 2003
436: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting STATUS
437: Management Information Base
438:
439:
440: MAX-ACCESS read-only
441: STATUS current
442: DESCRIPTION
443: "Part of set of indexes for outbound tunnel in the case of
444: MPLS-TE outer tunnel, otherwise returns the value zero."
445: ::= { pwVcMplsOutboundEntry 6 }
445: warning -
warning: flushing recent incorrect declaration, see previous error(s)
446:
447: pwVcMplsOutboundIfIndex OBJECT-TYPE
448: SYNTAX InterfaceIndexOrZero
449: MAX-ACCESS read-only
450: STATUS current
451: DESCRIPTION
452: "In case of PW label only (no outer tunnel), this object
453: holds the ifIndex of the outbound port, otherwise returns
454: the value zero."
455: ::= { pwVcMplsOutboundEntry 7 }
456:
457: -- End of Pseudo Wire MPLS Outbound Tunnel table
458:
459: -- PW to Non-TE MPLS tunnels configuration Table.
460: pwVcMplsNonTeMappingTable OBJECT-TYPE
461: SYNTAX SEQUENCE OF PwVcMplsNonTeMappingEntry
462: MAX-ACCESS not-accessible
463: STATUS current
464: DESCRIPTION
465: "This table maps an outbound Tunnel to a PW in non-
466: TE applications."
467: ::= { pwVcMplsObjects 3 }
468:
469: pwVcMplsNonTeMappingEntry OBJECT-TYPE
470: SYNTAX PwVcMplsNonTeMappingEntry
471: MAX-ACCESS not-accessible
472: STATUS current
473: DESCRIPTION
474: "A row in this table configure the association
475: between the PW and it's non TE MPLS outer Tunnel or
476: it's physical interface if there is no outer tunnel
477: (PW label only).
478:
479: If the operator (or the agent, based on local policy)
480: want to associate the PW with a non TE tunnel, it create
481: a row in this table with the tunnel parameters and the
482: relevant pwVcIndex.
483:
484: An application can use this table to quickly retrieve the
485: PW carried over specific non-TE MPLS outer tunnel or
486: physical interface.
487:
488: The table in indexed by the XC index for MPLS Non-TE
489: tunnel, or ifIndex of the port in PW label only case, and
490: the PW index.
491: Pseudo Wire (PW) Over MPLS December 2003
492: Management Information Base
493:
494:
495: "
496:
497: INDEX { pwVcMplsNonTeMappingXcTunnelIndex,
498: pwVcMplsNonTeMappingIfIndex,
499: pwVcMplsNonTeMappingVcIndex }
500:
501: ::= { pwVcMplsNonTeMappingTable 1 }
502:
503: PwVcMplsNonTeMappingEntry ::= SEQUENCE {
503: minor error -
SEQUENCE element #4 `pwVcMplsNonTeMappingRowStatus' is not a child node under `pwVcMplsNonTeMappingEntry'
503: minor error -
SEQUENCE element #5 `pwVcMplsNonTeMappingStorageType' is not a child node under `pwVcMplsNonTeMappingEntry'
504: pwVcMplsNonTeMappingXcTunnelIndex Unsigned32,
505: pwVcMplsNonTeMappingIfIndex InterfaceIndexOrZero,
506: pwVcMplsNonTeMappingVcIndex PwVcIndexType,
507: pwVcMplsNonTeMappingRowStatus RowStatus,
507: severe -
unknown object identifier label `pwVcMplsNonTeMappingRowStatus'
508: pwVcMplsNonTeMappingStorageType StorageType
509: }
510:
511: pwVcMplsNonTeMappingXcTunnelIndex OBJECT-TYPE
512: SYNTAX Unsigned32 (0..4294967295)
513: MAX-ACCESS not-accessible
514: STATUS current
515: DESCRIPTION
516: "Index for the conceptual XC row identifying Tunnel to PW
517: mappings when the outer tunnel is created by the MPLS-LSR-
518: STD-MIB, zero otherwise."
519: ::= { pwVcMplsNonTeMappingEntry 1 }
520:
521: pwVcMplsNonTeMappingIfIndex OBJECT-TYPE
522: SYNTAX InterfaceIndexOrZero
523: MAX-ACCESS not-accessible
524: STATUS current
525: DESCRIPTION
526: "In cases where there is PW label without outer tunnel,
527: this item indicate the ifIndex of the interface this PW
528: would use. In all other cases, this object should be set to
529: zero."
530: ::= { pwVcMplsNonTeMappingEntry 2 }
531:
532: pwVcMplsNonTeMappingVcIndex OBJECT-TYPE
533: SYNTAX PwVcIndexType
534: MAX-ACCESS not-accessible
535: STATUS current
536: DESCRIPTION
537: "The value that represent the PW in the pwVcTable."
538: ::= { pwVcMplsNonTeMappingEntry 3 }
539:
540: pwVcMplsNonTeMappingRowStatus OBJECT-TYPE
541: SYNTAX RowStatus
542: MAX-ACCESS read-create
543: STATUS current
544: DESCRIPTION
545: "For creating, modifying, and deleting this row."
546: Pseudo Wire (PW) Over MPLS December 2003
546: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting COLON_COLON_EQUAL
547: Management Information Base
548:
549:
550: ::= { pwVcMplsNonTeMappingEntry 4 }
550: warning -
warning: flushing recent incorrect declaration, see previous error(s)
551:
552: pwVcMplsNonTeMappingStorageType OBJECT-TYPE
553: SYNTAX StorageType
554: MAX-ACCESS read-create
555: STATUS current
556: DESCRIPTION
557: "This variable indicates the storage type for this object."
558: ::= { pwVcMplsNonTeMappingEntry 5 }
559:
560: -- End of PW to Non-TE MPLS tunnels configuration Table.
561:
562: -- PW to TE MPLS tunnels configuration Table.
563:
564: pwVcMplsTeMappingTable OBJECT-TYPE
565: SYNTAX SEQUENCE OF PwVcMplsTeMappingEntry
565: error -
unknown type `PwVcMplsTeMappingEntry'
566: MAX-ACCESS not-accessible
567: STATUS current
568: DESCRIPTION
569: "This table enable the configuration and retrieval of a PW
570: association to and outbound MPLS tunnel for MPLS-TE
571: applications."
572: ::= { pwVcMplsObjects 4 }
573:
574: pwVcMplsTeMappingEntry OBJECT-TYPE
575: SYNTAX PwVcMplsTeMappingEntry
576: MAX-ACCESS not-accessible
577: STATUS current
578: DESCRIPTION
579: "A row in this table represents the association
580: between a PW and it's MPLS-TE outer Tunnel.
581:
582: If the operator (or the agent, based on local policy)
583: want to associate the PW with a TE tunnel, it create
584: a row in this table with the tunnel parameters and the
585: relevant pwVcIndex.
586:
587: An application can use this table to quickly retrieve the
588: PW carried over specific TE MPLS outer tunnel.
589:
590: The table in indexed by the 4 indexes of a TE tunnel
591: and the PW index.
592: "
593:
594: INDEX { pwVcMplsTeMappingTunnelIndex,
595: pwVcMplsTeMappingTunnelInstance,
596: pwVcMplsTeMappingTunnelPeerLsrID,
597: pwVcMplsTeMappingTunnelLocalLsrID,
598: pwVcMplsTeMappingVcIndex }
598: severe -
unknown object identifier label `pwVcMplsTeMappingVcIndex'
599:
600: ::= { pwVcMplsTeMappingTable 1 }
601: Pseudo Wire (PW) Over MPLS December 2003
601: error -
`Pseudo' should start with a lower case letter
601: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting OBJECT
602: Management Information Base
603:
604:
605:
606: PwVcMplsTeMappingEntry ::= SEQUENCE {
607: pwVcMplsTeMappingTunnelIndex MplsTunnelIndex,
608: pwVcMplsTeMappingTunnelInstance MplsTunnelInstanceIndex,
609: pwVcMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier,
610: pwVcMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier,
611: pwVcMplsTeMappingVcIndex PwVcIndexType,
612: pwVcMplsTeMappingRowStatus RowStatus,
613: pwVcMplsTeMappingStorageType StorageType
614:
615: }
615: warning -
warning: flushing recent incorrect declaration, see previous error(s)
616:
617: pwVcMplsTeMappingTunnelIndex OBJECT-TYPE
618: SYNTAX MplsTunnelIndex
619: MAX-ACCESS not-accessible
620: STATUS current
621: DESCRIPTION
622: "Primary index for the conceptual row identifying the
623: MPLS-TE tunnel."
624: ::= { pwVcMplsTeMappingEntry 1 }
625:
626: pwVcMplsTeMappingTunnelInstance OBJECT-TYPE
627: SYNTAX MplsTunnelInstanceIndex
628: MAX-ACCESS not-accessible
629: STATUS current
630: DESCRIPTION
631: "Identifies an instance of the MPLS-TE tunnel."
632: ::= { pwVcMplsTeMappingEntry 2 }
633:
634: pwVcMplsTeMappingTunnelPeerLsrID OBJECT-TYPE
635: SYNTAX MplsLsrIdentifier
636: MAX-ACCESS not-accessible
637: STATUS current
638: DESCRIPTION
639: "Identifies the Peer LSR when the outer tunnel is MPLS-TE
640: based."
641: ::= { pwVcMplsTeMappingEntry 3 }
642:
643: pwVcMplsTeMappingTunnelLocalLsrID OBJECT-TYPE
644: SYNTAX MplsLsrIdentifier
645: MAX-ACCESS not-accessible
646: STATUS current
647: DESCRIPTION
648: "Identifies the local LSR."
649: ::= { pwVcMplsTeMappingEntry 4 }
650:
651: pwVcMplsTeMappingVcIndex OBJECT-TYPE
652: SYNTAX PwVcIndexType
653: MAX-ACCESS not-accessible
654: STATUS current
655: DESCRIPTION
656: Pseudo Wire (PW) Over MPLS December 2003
656: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting QUOTED_STRING
657: Management Information Base
658:
659:
660: "The value that represent the PW in the pwVcTable."
661: ::= { pwVcMplsTeMappingEntry 5 }
661: warning -
warning: flushing recent incorrect declaration, see previous error(s)
662:
663: pwVcMplsTeMappingRowStatus OBJECT-TYPE
664: SYNTAX RowStatus
665: MAX-ACCESS read-create
666: STATUS current
667: DESCRIPTION
668: "For creating, modifying, and deleting this row."
669: ::= { pwVcMplsTeMappingEntry 6 }
670:
671: pwVcMplsTeMappingStorageType OBJECT-TYPE
672: SYNTAX StorageType
673: MAX-ACCESS read-create
674: STATUS current
675: DESCRIPTION
676: "This variable indicates the storage type for this object."
677: ::= { pwVcMplsTeMappingEntry 7 }
678:
679:
680: -- End of PW to TE MPLS tunnels configuration Table.
681:
682:
683: -- conformance information
684:
685: -- Note: Conformance at the object access and values level is
686: -- still FFS, therefore current conformance is defined at the
687: -- object existence level only.
688:
689: pwVcMplsGroups OBJECT IDENTIFIER ::= { pwVcMplsConformance 1 }
690: pwVcMplsCompliances OBJECT IDENTIFIER ::= { pwVcMplsConformance 2 }
691:
692:
693: pwMplsModuleCompliance MODULE-COMPLIANCE
694: STATUS current
695: DESCRIPTION
696: "The compliance statement for agent that support PW
697: over MPLS PSN operation."
698:
699: MODULE -- this module
700: MANDATORY-GROUPS { pwVcMplsGroup,
700: severe -
unknown object identifier label `pwVcMplsGroup'
701: pwVcMplsOutboundGroup,
702: pwVcMplsMappingGroup
703: }
704:
705: ::= { pwVcMplsCompliances 1 }
706:
707: -- Units of conformance.
708:
709: pwVcMplsGroup OBJECT-GROUP
710: OBJECTS {
711: Pseudo Wire (PW) Over MPLS December 2003
711: error -
`Pseudo' should start with a lower case letter
711: error -
`Wire' should start with a lower case letter
711: error -
Object identifier element `Wire' name only allowed as first element
711: severe -
syntax error, unexpected '(', expecting '}' or ','
711: severe -
unknown object identifier label `Pseudo'
711: severe -
unknown object identifier label `Wire'
712: Management Information Base
713:
714:
715: pwVcMplsMplsType,
716: pwVcMplsExpBitsMode,
717: pwVcMplsExpBits,
718: pwVcMplsTtl,
719: pwVcMplsLocalLdpID,
720: pwVcMplsLocalLdpEntityID,
721: pwVcMplsPeerLdpID,
722: pwVcMplsStorageType
723: }
723: warning -
warning: flushing recent incorrect declaration, see previous error(s)
724:
725: STATUS current
725: severe -
syntax error, unexpected STATUS
726: DESCRIPTION
727: "Collection of objects needed for PW
728: over MPLS PSN configuration."
729: ::= { pwVcMplsGroups 1 }
729: warning -
warning: flushing recent incorrect declaration, see previous error(s)
730:
731:
732:
733: pwVcMplsOutboundGroup OBJECT-GROUP
734: OBJECTS {
735: pwVcMplsOutboundLsrXcIndex,
736: pwVcMplsOutboundTunnelIndex,
737: pwVcMplsOutboundTunnelInstance,
738: pwVcMplsOutboundTunnelLclLSR,
739: pwVcMplsOutboundTunnelPeerLSR,
740: pwVcMplsOutboundIfIndex
741: }
742:
743: STATUS current
744: DESCRIPTION
745: "Collection of objects needed for outbound association of
746: PW and MPLS tunnel."
747: ::= { pwVcMplsGroups 2 }
748:
749: pwVcMplsMappingGroup OBJECT-GROUP
750: OBJECTS {
751: pwVcMplsNonTeMappingRowStatus,
752: pwVcMplsNonTeMappingStorageType,
753: pwVcMplsTeMappingRowStatus,
754: pwVcMplsTeMappingStorageType
755: }
756:
757: STATUS current
758: DESCRIPTION
759: "Collection of objects used for mapping of tunnels and PW
760: labels to PW index."
761: ::= { pwVcMplsGroups 4 }
762:
763: END -- of PW-MPLS-STD-MIB
763: error -
missing MODULE-IDENTITY clause in SMIv2 MIB
764:
765: 8 Security Considerations
765: severe -
syntax error, unexpected NUMBER, expecting $end
766: Pseudo Wire (PW) Over MPLS December 2003
767: Management Information Base
768:
769:
770:
771: It is clear that this MIB module is potentially useful for
772: monitoring of PW capable PEs. This MIB module can also be used for
773: configuration of certain objects, and anything that can be
774: configured can be incorrectly configured, with potentially
775: disastrous results.
776:
777: There are a number of management objects defined in this MIB module
778: with a MAX-ACCESS clause of read-write and/or read-create. Such
779: objects may be considered sensitive or vulnerable in some network
780: environments. The support for SET operations in a non-secure
781: environment without proper protection can have a negative effect on
782: network operations. These are the tables and objects and their
783: sensitivity/vulnerability:
784:
785: o the pwVcMplsTable, pwVcMplsNonTeMappingTable and
786: pwVcMplsTeMappingTable collectively contain objects to
787: provision PW over MPLS tunnels. Unauthorized access to
788: objects in these tables, could result in disruption of
789: traffic on the network. The use of stronger mechanisms
790: such as SNMPv3 security should be considered where
791: possible. Specifically, SNMPv3 VACM and USM MUST be used
792: with any v3 agent which implements this MIB module.
793: Administrators should consider whether read access to these
794: objects should be allowed, since read access may be
795: undesirable under certain circumstances.
796:
797: Some of the readable objects in this MIB module "i.e., objects with
798: a MAX-ACCESS other than not-accessible" may be considered sensitive
799: or vulnerable in some network environments. It is thus important
800: to control even GET and/or NOTIFY access to these objects and
801: possibly to even encrypt the values of these objects when sending
802: them over the network via SNMP. These are the tables and objects
803: and their sensitivity/vulnerability:
804:
805: o the pwVcMplsTable, pwVcMplsNonTeMappingTable,
806: pwVcMplsTeMappingTable and pwVcMplsOutboundTable
807: collectively show the PW over MPLS association.
808: If an Administrator does not want to reveal this
809: information, then these tables should be
810: considered sensitive/vulnerable.
811:
812: SNMP versions prior to SNMPv3 did not include adequate security.
813: Even if the network itself is secure "for example by using IPSec",
814: even then, there is no control as to who on the secure network is
815: allowed to access and GET/SET "read/change/create/delete" the
816: objects in this MIB module.
817:
818: It is RECOMMENDED that implementers consider the security features
819: as provided by the SNMPv3 framework "see [RFC3410], section 8",
820: Pseudo Wire (PW) Over MPLS December 2003
821: Management Information Base
822:
823:
824: including full support for the SNMPv3 cryptographic mechanisms "for
825: authentication and privacy".
826:
827: Further, deployment of SNMP versions prior to SNMPv3 is NOT
828: RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
829: enable cryptographic security. It is then a customer/operator
830: responsibility to ensure that the SNMP entity giving access to an
831: instance of this MIB module, is properly configured to give access
832: to the objects only to those principals "users" that have
833: legitimate rights to indeed GET or SET "change/create/delete" them.
834:
835: 9 IANA considerations
836:
837: As requested in the PW-TC-STD-MIB [PWTCMIB], PWE3 related standards
838: track MIB modules should be rooted under the pwStdMIB subtree. The
839: IANA is requested to assign { pwStdMIB 3 } to the PW-MPLS-STD-MIB
840: module specified in this document.
841:
842:
843: 10 References
844:
845: 10.1 Normative references
846:
847: [PWARCH] Bryant, S., et al, "PWE3 Architecture", work-in-
848: progress.
849:
850: [PWREQ] Xiao, X., et al, "Requirements for Pseudo Wire
851: Emulation Edge-to-Edge (PWE3)", work-in-progress.
852:
853: [PWTC] Nadeau, T., et al, "Definitions for Textual Conventions
854: and OBJECT-IDENTITIES for Pseudo-Wires Management",
855: work-in-progress.
856:
857: [PW-MIB] Zelig, D., et al, "Pseudo Wire (PW) Management
858: Information Base", work-in-progress.
859:
860: [IF-MIB] McCloghrie, K., Kastenholz, F., ôThe Interfaces Group
861: MIBö, RFC 2863, June 2000.
862:
863: [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon,
864: "Multiprotocol Label Switching Architecture", RFC 3031,
865: Jan 2001.
866:
867: [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D.,
868: Federokow, G., Li, T., and A. Conta, "MPLS Label Stack
869: Encoding", RFC 3032, January 2001.
870:
871: [LSRMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T., "MPLS
872: Label Switch Router Management Information Base Using
873: SMIv2", work-in-progress.
874: Pseudo Wire (PW) Over MPLS December 2003
875: Management Information Base
876:
877:
878: [TEMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T., "MPLS
879: Traffic Engineering Management Information Base Using
880: SMIv2", work-in-progress.
881:
882: [MPLSTCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C., Viswanathan,
883: A., Sjostrand, H. and K. Kompella, "Definition of
884: Textual Conventions and OBJECT-IDENTITIES for Multi-
885: Protocol Label Switching (MPLS) Management", work-in-
886: progress.
887:
888: [LDP] Andersson, L., et al, "LDP specificationö, RFC 3036,
889: January 2001.
890:
891: [BCP14] Bradner, S., "Key words for use in RFCs to Indicate
892: requirement Levels", BCP 14, RFC 2119, March 1997.
893:
894: [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
895: J.,Rose, M. and S. Waldbusser, "Structure of Management
896: Information Version 2 (SMIv2)", STD 58, RFC 2578, April
897: 1999.
898:
899: [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
900: J., Rose, M. and S. Waldbusser, "Textual Conventions
901: for SMIv2", STD 58, RFC 2579, April 1999.
902:
903: [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
904: J., Rose, M. and S. Waldbusser, "Conformance Statements
905: for SMIv2", STD 58, RFC 2580, April 1999.
906:
907: 10.2 Informative references
908:
909:
910: [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
911: Introduction and Applicability Statements for Internet-
912: Standard Management Framework", RFC 3410, December
913: 2002.
914:
915:
916: 11 Author's Addresses
917:
918: David Zelig
919: Corrigent Systems
920: 126, Yigal Alon st.
921: Tel Aviv, ISRAEL
922: Phone: +972-3-6945273
923: Email: davidz@corrigent.com
924:
925: Thomas D. Nadeau
926: Cisco Systems, Inc.
927: 250 Apollo Drive
928: Pseudo Wire (PW) Over MPLS December 2003
929: Management Information Base
930:
931:
932: Chelmsford, MA 01824
933: Email: tnadeau@cisco.com
934:
935:
936: Dave Danenberg
937: Litchfield Communications, Inc.
938: 76 Westbury Park Rd
939: Princeton Building East
940: Watertown, CT 06795
941: Email: dave_danenberg@litchfieldcomm.com
942:
943: Andrew G. Malis
944: Tellabs, Inc.
945: 2730 Orchard Parkway
946: San Jose, CA 95134
947: Email: Andy.Malis@tellabs.com
948:
949: Sharon Mantin
950: AxONLink (Israel) Ltd
951: 9 Bareket St.
952: Petah Tikva 49517, Israel
953: Phone: +972-3-9263972
954: Email: sharon.mantin@axonlink.com
955:
956: 12 Full Copyright Statement
957:
958: Copyright (C) The Internet Society (2000). All Rights Reserved.
959:
960: This document and translations of it may be copied and furnished to
961: others, and derivative works that comment on or otherwise explain
962: it or assist in its implementation may be prepared, copied,
963: published and distributed, in whole or in part, without restriction
964: of any kind, provided that the above copyright notice and this
965: paragraph are included on all such copies and derivative works.
966: However, this document itself may not be modified in any way, such
967: as by removing the copyright notice or references to the Internet
968: Society or other Internet organizations, except as needed for the
969: purpose of developing Internet standards in which case the
970: procedures for copyrights defined in the Internet Standards process
971: must be followed, or as required to translate it into languages
972: other than English.
973:
974: The limited permissions granted above are perpetual and will not be
975: revoked by the Internet Society or its successors or assigns. This
976: document and the information contained herein is provided on an "AS
977: IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
978: TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
979: BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
980: HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
981: MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
982: Pseudo Wire (PW) Over MPLS December 2003
983: Management Information Base
984:
985:
986:
987: 13 Intellectual Property Notice
988:
989: The IETF takes no position regarding the validity or scope of any
990: intellectual property or other rights that might be claimed to
991: pertain to the implementation or use of the technology described in
992: this document or the extent to which any license under such rights
993: might or might not be available; neither does it represent that it
994: has made any effort to identify any such rights. Information on
995: the IETF's procedures with respect to rights in standards-track and
996: standards-related documentation can be found in BCP-11 [RFC2028].
997: Copies of claims of rights made available for publication and any
998: assurances of licenses to be made available, or the result of an
999: attempt made to obtain a general license or permission for the use
1000: of such proprietary rights by implementors or users of this
1001: specification can be obtained from the IETF Secretariat.
1002: The IETF invites any interested party to bring to its attention any
1003: copyrights, patents or patent applications, or other proprietary
1004: rights that may cover technology that may be required to practice
1005: this standard. Please address the information to the IETF
1006: Executive Director.