smilint output for ./PW-MPLS-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| severe | 1 |
| error | 2 |
| minor error | 2 |
| change recommended | 2 |
| warning | 8 |
| Message Types |
|---|
| Type | Count |
|---|
| date-in-past (change recommended) | 2 |
| date-value (error) | 2 |
| date-year-2digits (warning) | 4 |
| index-element-accessible (warning) | 2 |
| index-element-not-column (warning) | 2 |
| internal-other (severe) | 1 |
| revision-not-descending (minor error) | 2 |
Messages:
PW-MPLS-MIB
1: -- extracted from draft-ietf-pwe3-pw-mpls-mib-03.txt
2: -- at Tue Oct 28 06:14:44 2003
3:
4: PW-MPLS-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE,
8: experimental, 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-MIB
23:
24: PwVcIndexType
25: FROM PW-TC-MIB
26:
27: pwVcIndex
28: FROM PW-MIB
29:
30: ;
31:
32: pwVcMplsMIB MODULE-IDENTITY
33: LAST-UPDATED "200307291200Z" -- 29 July 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: Postal: Litchfield Communications, Inc.
54: 76 Westbury Park Rd
55: Princeton Building East
56: Watertown, CT 06795
57: Tel: +1-860-945-1573 x3180
58: Email: dave_danenberg@litchfieldcomm.com
59:
60: Sharon Mantin
61: Postal: AxONLink (Israel) Ltd
62: 9 Bareket St.
63: Petah Tikva 49517, Israel
64: Tel: +972-3-9263972
65: Email: sharon.mantin@axonlink.com
66:
67: The PWE3 Working Group (email distribution pwe3@ietf.org) "
68:
69: DESCRIPTION
70: "This MIB complements the PW-MIB for PW operation over MPLS.
71: "
72:
73: -- Revision history.
74: REVISION
75: "200307291200Z" -- 29 July 2003 12:00:00 EST
76: DESCRIPTION
77: "Draft-ietf-pwe3-pw-mpls-mib-02 version. Changes from
78: previous version:
79: 1) Removing inbound table (no srict mode and no knowledge
80: of inbound tunnel).
81: 2) Provisoning (i.e. RowCreate) done via mapping tables.
82: Outbound table is now read only for sorted search for
83: pwVcIndex.
84: "
85:
86: REVISION
87: "0206021200Z" -- 02 June 2002 12:00:00 EST
87: warning -
warning: date specification `0206021200Z' contains a two-digit year representing `1902'
87: change recommended -
warning: date specification `0206021200Z' predates the SMI standard
88: DESCRIPTION
89: "Draft-ietf-pwe3-pw-mpls-mib-00 version. Changes from
90: previous version:
91: 1) Spliting the mapping table into two tables, one for
92: Non TE application and one for TE application.
93: 2) Object types alignment with MPLS MIBs.
94: "
95: REVISION
96: "0201291200Z" -- 29 January 2002 12:00:00 EST
96: warning -
warning: date specification `0201291200Z' contains a two-digit year representing `1902'
96: change recommended -
warning: date specification `0201291200Z' predates the SMI standard
97: DESCRIPTION
98: "Changes from previous version:
99: 1) Add LDP entity association.
100: 2) Clarify inbound/outbound directions.
101: 3) Simplify indexing of outbound and inbound tables
102: and providing get next variables.
103: "
104: REVISION
105: "0107111200Z" -- 7 November 2001 12:00:00 EST
105: warning -
warning: date specification `0107111200Z' contains a two-digit year representing `1901'
105: error -
date specification `0107111200Z' contains an illegal value
105: minor error -
revision not in reverse chronological order
106: DESCRIPTION
107: "Changes from previous version:
108: 1) Remove Vc instance from table indexing.
109: 2) Update descriptions of indexing and protection.
110: 3) Remove the need for MPLS-LSR in case of VC only.
111: 4) Change pwVcMplsMplsType to BITS in order to enable
112: multiple types of outer tunnel.
113: 5) Add ifindex to outer tunnel tables to support vcOnly
114: option.
115: 6) change naming of outbound, inbound and mapping tables to
116: reflect addition of VC only port ifindexes.
117: 7) Adapt order of items in mapping table to SNMP convention.
118: "
119: REVISION
120: "0107111200Z" -- July 11 2001 12:00:00 EST
120: warning -
warning: date specification `0107111200Z' contains a two-digit year representing `1901'
120: error -
date specification `0107111200Z' contains an illegal value
120: minor error -
revision not in reverse chronological order
121: DESCRIPTION
122: "draft-zelig-pw-mib-00.txt - initial version"
123:
124: ::= { experimental 888 } -- To be assigned by IANA
125:
126: -- Top-level components of this MIB.
127:
128: -- Traps
129: pwVcMplsNotifications OBJECT IDENTIFIER
130: ::= { pwVcMplsMIB 0 }
131: pwVcMplsNotifyPrefix OBJECT IDENTIFIER
132: ::= { pwVcMplsNotifications 0 }
133: -- Tables, Scalars
134: pwVcMplsObjects OBJECT IDENTIFIER
135: ::= { pwVcMplsMIB 1 }
136:
137: -- Conformance
138: pwVcMplsConformance OBJECT IDENTIFIER
139: ::= { pwVcMplsMIB 2 }
140:
141: -- PW VC MPLS table
142:
143: pwVcMplsTable OBJECT-TYPE
144: SYNTAX SEQUENCE OF PwVcMplsEntry
145: MAX-ACCESS not-accessible
146: STATUS current
147: DESCRIPTION
148: "This table specifies information for VC to be carried over
149: MPLS PSN."
150: ::= { pwVcMplsObjects 1 }
151:
152: pwVcMplsEntry OBJECT-TYPE
153: SYNTAX PwVcMplsEntry
154: MAX-ACCESS not-accessible
155: STATUS current
156: DESCRIPTION
157: "A row in this table represents parameters specific to MPLS
158: PSN for a pseudo wire connection (VC). The row is created
159: automatically by the local agent if the pwVcPsnType is
160: MPLS. It is indexed by pwVcIndex, which uniquely
161: identifying a singular connection.
162: "
163:
164: INDEX { pwVcIndex }
165:
166: ::= { pwVcMplsTable 1 }
167:
168: PwVcMplsEntry ::= SEQUENCE {
169: pwVcMplsMplsType BITS,
170: pwVcMplsExpBitsMode INTEGER,
171: pwVcMplsExpBits Unsigned32,
172: pwVcMplsTtl Unsigned32,
173: pwVcMplsLocalLdpID MplsLdpIdentifier,
174: pwVcMplsLocalLdpEntityID Unsigned32,
175: pwVcMplsPeerLdpID MplsLdpIdentifier,
176: pwVcMplsStorageType StorageType
177: }
178:
179: pwVcMplsMplsType OBJECT-TYPE
180: SYNTAX BITS {
181: mplsTe (0),
182: mplsNonTe (1),
183: vcOnly (2)
184: }
185: MAX-ACCESS read-write
186: STATUS current
187: DESCRIPTION
188: "Set by the operator to indicate the outer tunnel types, if
189: exists. mplsTe is used if the outer tunnel was set-up by
190: MPLS-TE, and mplsNonTe is used the outer tunnel was set up
191: by LDP or manually. Combination of mplsTe and mplsNonTe
192: may exist in case of outer tunnel protection.
193: vcOnly is used if there is no outer tunnel label. vcOnly
194: cannot be combined with mplsNonTe or mplsTe."
195: ::= { pwVcMplsEntry 1 }
196:
197:
198: pwVcMplsExpBitsMode OBJECT-TYPE
199: SYNTAX INTEGER {
200: outerTunnel (1),
201: specifiedValue (2),
202: serviceDependant (3)
203: }
204:
205: MAX-ACCESS read-write
206: STATUS current
207: DESCRIPTION
208: "Set by the operator to indicate the way the VC shim label
209: EXP bits are to be determined. The value of outerTunnel(1)
210: is used where there is an outer tunnel - pwVcMplsMplsType
211: is mplsTe or mplsNonTe. Note that in this case there is no
212: need to mark the VC label with the EXP bits since the VC
213: label is not visible to the intermediate nodes.
214: If there is no outer tunnel, specifiedValue(2) indicate
215: that the value is specified by pwVcMplsExpBits, and
216: serviceDependant(3) indicate that the EXP bits are setup
217: based on a rule specified in the emulated service specific
218: tables, for example when the EXP bits are a function of
219: 802.1p marking for Ethernet emulated service."
220: REFERENCE
221: "martini et al, <draft-martini-l2circuit-encap-mpls.txt>"
222: DEFVAL { outerTunnel }
223: ::= { pwVcMplsEntry 2 }
224:
225: pwVcMplsExpBits OBJECT-TYPE
226: SYNTAX Unsigned32 (0..7)
227: MAX-ACCESS read-write
228: STATUS current
229: DESCRIPTION
230: "Set by the operator to indicate the MPLS EXP bits to be
231: used on the VC shim label if pwVcMplsExpBitsMode is
232: specifiedValue(2), zero otherwise."
233: DEFVAL { 0 }
234: ::= { pwVcMplsEntry 3 }
235:
236: pwVcMplsTtl OBJECT-TYPE
237: SYNTAX Unsigned32 (0..255)
238: MAX-ACCESS read-write
239: STATUS current
240: DESCRIPTION
241: "Set by the operator to indicate the VC TTL bits to be used
242: on the VC shim label."
243: REFERENCE
244: "martini et al, <draft-martini-l2circuit-encap-mpls> "
245: DEFVAL { 2 }
246: ::= { pwVcMplsEntry 4 }
247:
248: pwVcMplsLocalLdpID OBJECT-TYPE
249: SYNTAX MplsLdpIdentifier
250: MAX-ACCESS read-write
251: STATUS current
252: DESCRIPTION
253: "The local LDP identifier of the LDP entity creating
254: this VC in the local node. As the VC labels are always
255: set from the per platform label space, the last two octets
256: in the LDP ID MUST be always both zeros."
257: REFERENCE
258: "<draft-ietf-ldp-mib>,
259: <draft-martini-l2circuit-encap-mpls>.
260: "
261: ::= { pwVcMplsEntry 5 }
262:
263: pwVcMplsLocalLdpEntityID OBJECT-TYPE
263: warning -
warning: index element `pwVcIndex' of row `pwVcMplsEntry' must be a column
263: warning -
warning: index element `pwVcIndex' of row `pwVcMplsOutboundEntry' must be a column
264: SYNTAX Unsigned32
265: MAX-ACCESS read-write
266: STATUS current
267: DESCRIPTION
268: "The local LDP Entity index of the LDP entity to be used
269: for this VC on the local node. Should be set to all zeros
270: if not used."
271: REFERENCE
272: "<draft-ietf-ldp-mib>
273: "
274: ::= { pwVcMplsEntry 6 }
275:
276: pwVcMplsPeerLdpID OBJECT-TYPE
277: SYNTAX MplsLdpIdentifier
278: MAX-ACCESS read-only
279: STATUS current
280: DESCRIPTION
281: "The peer LDP identifier as identified from the LDP
282: session. Should be zero if not relevant or not known yet."
283: REFERENCE
284: "<draft-ietf-ldp-mib>,
285: <draft-martini-l2circuit-encap-mpls>.
286: "
287: ::= { pwVcMplsEntry 7 }
288:
289: pwVcMplsStorageType OBJECT-TYPE
290: SYNTAX StorageType
291: MAX-ACCESS read-write
292: STATUS current
293: DESCRIPTION
294: "This variable indicates the storage type for this row."
295: ::= { pwVcMplsEntry 8 }
296:
297: -- End of PW MPLS VC table
298:
299: -- Pseudo Wire VC MPLS Outbound Tunnel table
300:
301: pwVcMplsOutboundTable OBJECT-TYPE
302: SYNTAX SEQUENCE OF PwVcMplsOutboundEntry
303: MAX-ACCESS not-accessible
304: STATUS current
305: DESCRIPTION
306: "This table associates VCs using MPLS PSN with the outbound
307: MPLS tunnels (i.e. toward the PSN) or the physical
308: interface in case of VC only."
309: ::= { pwVcMplsObjects 2 }
310:
311: pwVcMplsOutboundEntry OBJECT-TYPE
312: SYNTAX PwVcMplsOutboundEntry
313: MAX-ACCESS not-accessible
314: STATUS current
315: DESCRIPTION
316: "A row in this table represents a link between PW VC (that
317: require MPLS tunnels) and MPLS tunnel toward the PSN.
318: In the case of VC only, it associate the VC with the
319: interface that shall carry the VC.
320: This table is indexed by the pwVcIndex and an additional
321: index enabling multiple rows for the same VC index.
322:
323: At least one entry is created in this table by the agent
324: for each PW VC that requires MPLS PSN. Note that the first
325: entry for each VC can be indexed by pwVcMplsOutboundIndex
326: equal zero without a need for retrieval of
327: pwVcMplsOutboundIndexNext.
328:
329: This table points to the appropriate MPLS MIB. In the case
330: of MPLS-TE, the 4 variables relevant to the indexing of
331: a TE MPLS tunnel are set as in Srinivasan, et al, <draft-
332: ietf-mpls-te-mib>.
333: In case of Non-TE MPLS (an outer tunnel label assigned by
334: LDP or manually) the table points to the XC entry in the
335: LSR MIB as in Srinivasan, et al, <draft-ietf-mpls-lsr-mib>.
336: In case of VC only (no outer tunnel) the ifIndex of the
337: port to carry the VC is configured.
338:
339: Each VC may have multiple rows in this tables if protection
340: is available at the outer tunnel level, each row may be of
341: different type except for VC only, on which only rows with
342: ifIndex of the port are allowed.
343: "
344:
345: INDEX { pwVcIndex, pwVcMplsOutboundIndex }
346:
347: ::= { pwVcMplsOutboundTable 1 }
348:
349: PwVcMplsOutboundEntry ::= SEQUENCE {
350: pwVcMplsOutboundIndex Unsigned32,
351: pwVcMplsOutboundLsrXcIndex Unsigned32,
352: pwVcMplsOutboundTunnelIndex MplsTunnelIndex,
353: pwVcMplsOutboundTunnelInstance MplsTunnelInstanceIndex,
354: pwVcMplsOutboundTunnelLclLSR MplsLsrIdentifier,
355: pwVcMplsOutboundTunnelPeerLSR MplsLsrIdentifier,
356: pwVcMplsOutboundIfIndex InterfaceIndexOrZero
357: }
358:
359: pwVcMplsOutboundIndex OBJECT-TYPE
360: SYNTAX Unsigned32 (0..4294967295)
361: MAX-ACCESS not-accessible
362: STATUS current
363: DESCRIPTION
364: "Arbitrary index for enabling multiple rows per VC in
365: this table. Next available free index can be retrieved
366: using pwVcMplsOutboundIndexNext.
367: "
368: ::= { pwVcMplsOutboundEntry 1 }
369:
370: pwVcMplsOutboundLsrXcIndex OBJECT-TYPE
371: SYNTAX Unsigned32
372: MAX-ACCESS read-only
373: STATUS current
374: DESCRIPTION
375: "This object will be set by the operator. If the outer
376: label is defined in the MPL-LSR-MIB, i.e. set by LDP
377: or manually, this object points to the XC index
378: of the outer tunnel. Otherwise, it is set to zero."
379: ::= { pwVcMplsOutboundEntry 2 }
380:
381:
382: pwVcMplsOutboundTunnelIndex OBJECT-TYPE
383: SYNTAX MplsTunnelIndex
384: MAX-ACCESS read-only
385: STATUS current
386: DESCRIPTION
387: "Part of set of indexes for outbound tunnel in the case of
388: MPLS-TE outer tunnel, otherwise set to zero."
389: ::= { pwVcMplsOutboundEntry 3 }
390:
391: pwVcMplsOutboundTunnelInstance OBJECT-TYPE
392: SYNTAX MplsTunnelInstanceIndex
393: MAX-ACCESS read-only
394: STATUS current
395: DESCRIPTION
396: "Part of set of indexes for outbound tunnel in the case of
397: MPLS-TE outer tunnel, otherwise set to zero."
398: ::= { pwVcMplsOutboundEntry 4 }
399:
400: pwVcMplsOutboundTunnelLclLSR OBJECT-TYPE
401: SYNTAX MplsLsrIdentifier
402: MAX-ACCESS read-only
403: STATUS current
404: DESCRIPTION
405: "Part of set of indexes for outbound tunnel in the case of
406: MPLS-TE outer tunnel, otherwise set to zero."
407: ::= { pwVcMplsOutboundEntry 5 }
408:
409: pwVcMplsOutboundTunnelPeerLSR OBJECT-TYPE
410: SYNTAX MplsLsrIdentifier
411: MAX-ACCESS read-only
412: STATUS current
413: DESCRIPTION
414: "Part of set of indexes for outbound tunnel in the case of
415: MPLS-TE outer tunnel, otherwise set to zero."
416: ::= { pwVcMplsOutboundEntry 6 }
417:
418: pwVcMplsOutboundIfIndex OBJECT-TYPE
419: SYNTAX InterfaceIndexOrZero
420: MAX-ACCESS read-only
421: STATUS current
422: DESCRIPTION
423: "In case of VC only (no outer tunnel), this object holds
424: the ifIndex of the outbound port, otherwise set to zero."
425: ::= { pwVcMplsOutboundEntry 7 }
426:
427: -- End of Pseudo Wire VC MPLS Outbound Tunnel table
428:
429: -- MPLS to VC Mapping Tables.
430:
431: pwVcMplsNonTeMappingTable OBJECT-TYPE
432: SYNTAX SEQUENCE OF PwVcMplsNonTeMappingEntry
433: MAX-ACCESS not-accessible
434: STATUS current
435: DESCRIPTION
436: "This table maps an outbound Tunnel to a VC in non-
437: TE applications."
438: ::= { pwVcMplsObjects 3 }
439:
440: pwVcMplsNonTeMappingEntry OBJECT-TYPE
440: warning -
warning: index element `pwVcMplsNonTeMappingVcIndex' of row `pwVcMplsNonTeMappingEntry' should be not-accessible in SMIv2 MIB
441: SYNTAX PwVcMplsNonTeMappingEntry
442: MAX-ACCESS not-accessible
443: STATUS current
444: DESCRIPTION
445: "A row in this table represents the association
446: between the PW VC and it's non TE MPLS outer Tunnel
447: it's physical interface if there is no outer tunnel
448: (VC only).
449:
450: If the operator (or the agent, based on local policy)
451: want to associate the PW with a non TE tunnel, it
452: create
453: a row in this table with the tunnel parameters and the
454: relevant pwVcIndex.
455:
456: An application can use this table to quickly retrieve the
457: PW carried over specific non-TE MPLS outer tunnel or
458: physical interface.
459:
460: The table in indexed by the XC index for MPLS Non-TE
461: tunnel, or ifIndex of the port in VC only case, the
462: direction of the VC in the specific entry and the VCIndex.
463: "
464:
465: INDEX { pwVcMplsNonTeMappingXcTunnelIndex,
466: pwVcMplsNonTeMappingIfIndex,
467: pwVcMplsNonTeMappingVcIndex }
468:
469: ::= { pwVcMplsNonTeMappingTable 1 }
470:
471: PwVcMplsNonTeMappingEntry ::= SEQUENCE {
472: pwVcMplsNonTeMappingXcTunnelIndex Unsigned32,
473: pwVcMplsNonTeMappingIfIndex
474: InterfaceIndexOrZero,
475: pwVcMplsNonTeMappingVcIndex PwVcIndexType,
476: pwVcMplsNonTeMappingRowStatus RowStatus,
477: pwVcMplsNonTeMappingStorageType StorageType
478: }
479:
480: pwVcMplsNonTeMappingXcTunnelIndex OBJECT-TYPE
481: SYNTAX Unsigned32 (0..4294967295)
482: MAX-ACCESS not-accessible
483: STATUS current
484: DESCRIPTION
485: "Index for the conceptual XC row identifying Tunnel to VC
486: mappings when the outer tunnel is created by the MPLS-LSR-
487: MIB, Zero otherwise."
488: ::= { pwVcMplsNonTeMappingEntry 1 }
489:
490: pwVcMplsNonTeMappingIfIndex OBJECT-TYPE
491: SYNTAX InterfaceIndexOrZero
492: MAX-ACCESS not-accessible
493: STATUS current
494: DESCRIPTION
495: "In cases where there is only VC label without outer tunnel,
496: this item indicate the ifIndex of the interface this VC
497: would use. In all other cases, this object shgould be set to
498: zero."
499: ::= { pwVcMplsNonTeMappingEntry 2 }
500:
501: pwVcMplsNonTeMappingVcIndex OBJECT-TYPE
502: SYNTAX PwVcIndexType
503: MAX-ACCESS read-create
504: STATUS current
505: DESCRIPTION
506: "The value that represent the VC in the pwVcTable."
507: ::= { pwVcMplsNonTeMappingEntry 3 }
508:
509: pwVcMplsNonTeMappingRowStatus OBJECT-TYPE
510: SYNTAX RowStatus
511: MAX-ACCESS read-create
512: STATUS current
513: DESCRIPTION
514: "For creating, modifying, and deleting this row."
515: ::= { pwVcMplsNonTeMappingEntry 4 }
516:
517: pwVcMplsNonTeMappingStorageType OBJECT-TYPE
518: SYNTAX StorageType
519: MAX-ACCESS read-create
520: STATUS current
521: DESCRIPTION
522: "This variable indicates the storage type for this object."
523: ::= { pwVcMplsNonTeMappingEntry 5 }
524:
525: -- End of Non-TE MPLS Tunnel to VC Mapping Table
526:
527: pwVcMplsTeMappingTable OBJECT-TYPE
528: SYNTAX SEQUENCE OF PwVcMplsTeMappingEntry
529: MAX-ACCESS not-accessible
530: STATUS current
531: DESCRIPTION
532: "This table maps an inbound/outbound Tunnel to a VC in
533: MPLS-TE applications."
534: ::= { pwVcMplsObjects 4 }
535:
536: pwVcMplsTeMappingEntry OBJECT-TYPE
536: warning -
warning: index element `pwVcMplsTeMappingVcIndex' of row `pwVcMplsTeMappingEntry' should be not-accessible in SMIv2 MIB
537: SYNTAX PwVcMplsTeMappingEntry
538: MAX-ACCESS not-accessible
539: STATUS current
540: DESCRIPTION
541: "A row in this table represents the association
542: between a PW VC and it's MPLS-TE outer Tunnel.
543:
544: If the operator (or the agent, based on local policy)
545: want to associate the PW with a non TE tunnel, it
546: create
547: a row in this table with the tunnel parameters and the
548: relevant pwVcIndex.
549:
550: An application can use this table to quickly retrieve the
551: PW carried over specific TE MPLS outer tunnel.
552:
553: The table in indexed by the 4 indexes of a TE tunnel,
554: the direction of the VC specific entry and the VcIndex.
555: "
556:
557: INDEX { pwVcMplsTeMappingTunnelIndex,
558: pwVcMplsTeMappingTunnelInstance,
559: pwVcMplsTeMappingTunnelPeerLsrID,
560: pwVcMplsTeMappingTunnelLocalLsrID,
561: pwVcMplsTeMappingVcIndex }
562:
563: ::= { pwVcMplsTeMappingTable 1 }
564:
565: PwVcMplsTeMappingEntry ::= SEQUENCE {
566: pwVcMplsTeMappingTunnelIndex MplsTunnelIndex,
567: pwVcMplsTeMappingTunnelInstance MplsTunnelInstanceIndex,
568: pwVcMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier,
569: pwVcMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier,
570: pwVcMplsTeMappingVcIndex PwVcIndexType,
571: pwVcMplsTeMappingRowStatus RowStatus,
572: pwVcMplsTeMappingStorageType StorageType
573:
574: }
575:
576: pwVcMplsTeMappingTunnelIndex OBJECT-TYPE
577: SYNTAX MplsTunnelIndex
578: MAX-ACCESS not-accessible
579: STATUS current
580: DESCRIPTION
581: "Primary index for the conceptual row identifying the
582: MPLS-TE tunnel."
583: ::= { pwVcMplsTeMappingEntry 1 }
584:
585: pwVcMplsTeMappingTunnelInstance OBJECT-TYPE
586: SYNTAX MplsTunnelInstanceIndex
587: MAX-ACCESS not-accessible
588: STATUS current
589: DESCRIPTION
590: "Identifies an instance of the MPLS-TE tunnel."
591: ::= { pwVcMplsTeMappingEntry 2 }
592:
593: pwVcMplsTeMappingTunnelPeerLsrID OBJECT-TYPE
594: SYNTAX MplsLsrIdentifier
595: MAX-ACCESS not-accessible
596: STATUS current
597: DESCRIPTION
598: "Identifies an Peer LSR when the outer tunnel is MPLS-TE
599: based."
600: ::= { pwVcMplsTeMappingEntry 3 }
601:
602: pwVcMplsTeMappingTunnelLocalLsrID OBJECT-TYPE
603: SYNTAX MplsLsrIdentifier
604: MAX-ACCESS not-accessible
605: STATUS current
606: DESCRIPTION
607: "Identifies the local LSR."
608: ::= { pwVcMplsTeMappingEntry 4 }
609:
610: pwVcMplsTeMappingVcIndex OBJECT-TYPE
611: SYNTAX PwVcIndexType
612: MAX-ACCESS read-create
613: STATUS current
614: DESCRIPTION
615: "The value that represent the VC in the pwVcTable."
616: ::= { pwVcMplsTeMappingEntry 5 }
617:
618: pwVcMplsTeMappingRowStatus OBJECT-TYPE
619: SYNTAX RowStatus
620: MAX-ACCESS read-create
621: STATUS current
622: DESCRIPTION
623: "For creating, modifying, and deleting this row."
624: ::= { pwVcMplsTeMappingEntry 6 }
625:
626: pwVcMplsTeMappingStorageType OBJECT-TYPE
627: SYNTAX StorageType
628: MAX-ACCESS read-create
629: STATUS current
630: DESCRIPTION
631: "This variable indicates the storage type for this object."
632: ::= { pwVcMplsTeMappingEntry 7 }
633:
634:
635: -- End of TE MPLS Tunnel to VC Mapping Table
636:
637:
638: -- conformance information
639:
640: -- Note: Conformance at the object access and values level is
641: -- still FFS, therefore current conformance is defined at the
642: -- object existence level only.
643:
644: pwVcMplsGroups OBJECT IDENTIFIER ::= { pwVcMplsConformance 1 }
645: pwVcMplsCompliances OBJECT IDENTIFIER ::= { pwVcMplsConformance 2 }
646:
647:
648: pwMplsModuleCompliance MODULE-COMPLIANCE
649: STATUS current
650: DESCRIPTION
651: "The compliance statement for agent that support PW
652: over MPLS PSN operation."
653:
654: MODULE -- this module
655: MANDATORY-GROUPS { pwVcMplsGroup,
656: pwVcMplsOutboundGroup,
657: pwVcMplsMappingGroup
658: }
659:
660: ::= { pwVcMplsCompliances 1 }
661:
662: -- Units of conformance.
663:
664: pwVcMplsGroup OBJECT-GROUP
665: OBJECTS {
666: pwVcMplsMplsType,
667: pwVcMplsExpBitsMode,
668: pwVcMplsExpBits,
669: pwVcMplsTtl,
670: pwVcMplsLocalLdpID,
671: pwVcMplsLocalLdpEntityID,
672: pwVcMplsPeerLdpID,
673: pwVcMplsStorageType
674: }
675:
676: STATUS current
677: DESCRIPTION
678: "Collection of objects needed for PW VC
679: over MPLS PSN configuration."
680: ::= { pwVcMplsGroups 1 }
681:
682:
683:
684: pwVcMplsOutboundGroup OBJECT-GROUP
685: OBJECTS {
686: pwVcMplsOutboundLsrXcIndex,
687: pwVcMplsOutboundTunnelIndex,
688: pwVcMplsOutboundTunnelInstance,
689: pwVcMplsOutboundTunnelLclLSR,
690: pwVcMplsOutboundTunnelPeerLSR,
691: pwVcMplsOutboundIfIndex
692: }
693:
694: STATUS current
695: DESCRIPTION
696: "Collection of objects needed for outbound association of
697: VC and MPLS tunnel."
698: ::= { pwVcMplsGroups 2 }
699:
700: pwVcMplsMappingGroup OBJECT-GROUP
701: OBJECTS {
702: pwVcMplsNonTeMappingVcIndex,
703: pwVcMplsNonTeMappingRowStatus,
704: pwVcMplsNonTeMappingStorageType,
705: pwVcMplsTeMappingVcIndex,
706: pwVcMplsTeMappingRowStatus,
707: pwVcMplsTeMappingStorageType
708: }
709:
710: STATUS current
711: DESCRIPTION
712: "Collection of objects used for mapping of tunnels and VC
713: labels to VC index."
714: ::= { pwVcMplsGroups 4 }
715:
716: END -- of PW-MPLS-MIB
717:
718:
719: 8 Security Considerations
719: severe -
syntax error, unexpected NUMBER, expecting $end
720:
721: There are a number of management objects defined in this MIB that
722: have a MAX-ACCESS clause of read-write and/or read-create. Such
723: objects may be considered sensitive or vulnerable in some network
724: environments. The support for SET operations in a non-secure
725: environment without proper protection can have a negative effect on
726: network operations.
727:
728: SNMPv1 by itself is not a secure environment. Even if the network
729: itself is secure (for example by using IPSec), even then, there is
730: no control as to who on the secure network is allowed to access and
731: GET/SET (read/change/create/delete) the objects in this MIB.
732:
733: It is recommended that the implementers consider the security
734: features as provided by the SNMPv3 framework. Specifically, the
735: use of the User-based Security Model RFC 2574 [RFC2574] and the
736: View-based Access Control Model RFC 2575 [RFC2575] is recommended.
737:
738: It is then a customer/user responsibility to ensure that the SNMP
739: entity giving access to an instance of this MIB, is properly
740: configured to give access to the objects only to those principals
741: (users) that have legitimate rights to indeed GET or SET
742: (change/create/delete) them.
743:
744: The use of strict inbound VC lookup the security problems related
745: to a global VC space in a node is greatly reduced, by limiting the
746: accepted packets to a small set of controlled tunnels.
747:
748:
749: 9 References
750:
751: [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon,
752: "Multiprotocol Label Switching Architecture", RFC 3031,
753: Jan 2001.
754:
755: [CEP] Malis, A., et al, "SONET/SDH Circuit Emulation over
756: Packet (CEP)", work-in-progress.
757:
758:
759: [PWREQ] Xiao et al, "Requirements for Pseudo Wire Emulation
760: Edge-to-Edge (PWE3)", <draft-ietf-pwe3-requirements-
761: 02.txt>, November 2001.
762:
763: [PW-MIB] Zelig et al, "Pseudo Wire (PW) Management Information
764: Base", <draft-ietf-pwe3-pw-mib-00.txt>, June 2002.
765:
766: [CEPMIB] Danenberg et al, "SONET/SDH Circuit Emulation Service
767: Over MPLS (CEP) Management Information Base Using
768: SMIv2", work-in-progress.
769:
770: [LSRMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T. "MPLS
771: Label Switch Router Management Information Base Using
772: SMIv2", work-in-progress.
773:
774: [PWTC] Nadeau, T., et al, "Definitions for Textual Conventions
775: and OBJECT-IDENTITIES for Pseudo-Wires Management",
776: work-in-progress.
777:
778: [TEMIB] Srinivasan, C., Viswanathan, A., and Nadeau, T. "MPLS
779: Traffic Engineering Management Information Base Using
780: SMIv2", work-in-progress.
781:
782: [LDPMIB] J. Cucchiara et al, "Definitions of Managed Objects for
783: the Multiprotocol Label Switching, Label Distribution
784: Protocol (LDP), work-in-progress.
785:
786: [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D.,
787: Federokow, G., Li, T., and A. Conta, "MPLS Label Stack
788: Encoding", RFC 3032, January 2001.
789:
790: [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", RFC
791: 1700, October 1994. See also: http://www.isi.edu/in-
792: notes/iana/assignments/smi-numbers
793:
794: [IANAFamily]Internet Assigned Numbers Authority (IANA), ADDRESS
795: FAMILY NUMBERS,(http://www.isi.edu/in-
796: notes/iana/assignements/address-family-numbers), for
797: MIB see:
798: ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib
799:
800: [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces
801: Group MIB using SMIv2", RFC 2863, January 2000.
802:
803: [BCP14] Bradner, S., "Key words for use in RFCs to Indicate
804: requirement Levels", BCP 14, RFC 2119, March 1997.
805:
806: [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
807: Architecture for Describing SNMP Management
808: Frameworks", RFC 2571, April 1999.
809:
810: [RFC1155] Rose, M., and K. McCloghrie, "Structure and
811: Identification of Management Information for TCP/IP-
812: based Internets", STD 16, RFC 1155, May 1990.
813:
814: [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions",
815: STD 16, RFC 1212, March 1991.
816:
817: [RFC1215] M. Rose, "A Convention for Defining Traps for use with
818: the SNMP", RFC 1215, March 1991.
819:
820: [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
821: J, Rose, M., and S. Waldbusser, "Structure of
822: Management Information Version 2 (SMIv2)", STD 58, RFC
823: 2578, April 1999.
824:
825: [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
826: J, Rose, M., and S. Waldbusser, "Textual Conventions
827: for SMIv2", STD 58, RFC 2579, April 1999.
828:
829: [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
830: J, Rose, M., and S. Waldbusser, "Conformance Statements
831: for SMIv2", STD 58, RFC 2580, April 1999.
832:
833: [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
834: "Simple Network Management Protocol", STD 15, RFC 1157,
835: May 1990.
836:
837: [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
838: "Introduction to Community-based SNMPv2", RFC 1901,
839: January 1996.
840:
841: [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
842: "Transport Mappings for Version 2 of the Simple Network
843: Management Protocol (SNMPv2)", RFC 1906, January 1996.
844:
845: [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
846: "Message Processing and Dispatching for the Simple
847: Network Management Protocol (SNMP)", RFC 2572, April
848: 1999.
849:
850: [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security
851: Model (USM) for version 3 of the Simple Network
852: Management Protocol (SNMPv3)", RFC 2574, April 1999.
853:
854: [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
855: "Protocol Operations for Version 2 of the Simple
856: Network Management Protocol (SNMPv2)", RFC 1905,
857: January 1996.
858:
859: [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
860: Applications", RFC 2573, April 1999.
861:
862: [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
863: Access Control Model (VACM) for the Simple Network
864: Management Protocol (SNMP)", RFC 2575, April 1999.
865:
866: [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
867: "Introduction to Version 3 of the Internet-standard
868: Network Management Framework", RFC 2570, April 1999.
869:
870: 10 Author's Addresses
871:
872: David Zelig
873: Corrigent Systems
874: 126, Yigal Alon st.
875: Tel Aviv, ISRAEL
876: Phone: +972-3-6945273
877: Email: davidz@corrigent.com
878:
879: Thomas D. Nadeau
880: Cisco Systems, Inc.
881: 250 Apollo Drive
882: Chelmsford, MA 01824
883: Email: tnadeau@cisco.com
884:
885:
886: Dave Danenberg
887: Litchfield Communications, Inc.
888: 76 Westbury Park Rd
889: Princeton Building East
890: Watertown, CT 06795
891: Email: dave_danenberg@litchfieldcomm.com
892:
893: Andrew G. Malis
894: Tellabs, Inc.
895: 2730 Orchard Parkway
896: San Jose, CA 95134
897: Email: Andy.Malis@tellabs.com
898:
899: Sharon Mantin
900: AxONLink (Israel) Ltd
901: 9 Bareket St.
902: Petah Tikva 49517, Israel
903: Phone: +972-3-9263972
904: Email: sharon.mantin@axonlink.com
905:
906: 11 Full Copyright Statement
907:
908: Copyright (C) The Internet Society (2000). All Rights Reserved.
909:
910: This document and translations of it may be copied and furnished to
911: others, and derivative works that comment on or otherwise explain
912: it or assist in its implementation may be prepared, copied,
913: published and distributed, in whole or in part, without restriction
914: of any kind, provided that the above copyright notice and this
915: paragraph are included on all such copies and derivative works.
916: However, this document itself may not be modified in any way, such
917: as by removing the copyright notice or references to the Internet
918: Society or other Internet organizations, except as needed for the
919: purpose of developing Internet standards in which case the
920: procedures for copyrights defined in the Internet Standards process
921: must be followed, or as required to translate it into languages
922: other than English.
923:
924: The limited permissions granted above are perpetual and will not be
925: revoked by the Internet Society or its successors or assigns. This
926: document and the information contained herein is provided on an "AS
927: IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
928: TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
929: BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
930: HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
931: MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.