smilint output for ./PW-MPLS-STD-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 2 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 1 |
| object-identifier-not-prefix (error) | 1 |
Messages:
PW-MPLS-STD-MIB
1: -- extracted from draft-ietf-pwe3-pw-mpls-mib-12.txt
2: -- at Fri May 25 06:08:23 2007
3:
4: PW-MPLS-STD-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, transmission
8: FROM SNMPv2-SMI -- [RFC2578]
9:
10: MODULE-COMPLIANCE, OBJECT-GROUP
11: FROM SNMPv2-CONF -- [RFC2580]
12:
13: StorageType
14: FROM SNMPv2-TC -- [RFC2579]
15:
16: InterfaceIndexOrZero
17: FROM IF-MIB -- [RFC2863]
18:
19: MplsTunnelIndex, MplsTunnelInstanceIndex,
20: MplsLdpIdentifier, MplsLsrIdentifier
21: FROM MPLS-TC-STD-MIB -- [RFC3811]
22:
23: MplsIndexType
24: FROM MPLS-LSR-STD-MIB -- [RFC3813]
25:
26: PwIndexType
27: FROM PW-TC-STD-MIB -- [PWTC]
28: -- RFC Editor: Please replace PWTC with the RFC number and remove
29: -- this note.
30:
31: pwIndex -- [PWMIB]
32: -- RFC Editor: Please replace PWMIB with the RFC number and remove
33: -- this note.
34: FROM PW-STD-MIB
35:
36: ;
37:
38: pwMplsStdMIB MODULE-IDENTITY
39: LAST-UPDATED "200705171200Z" -- 17 May 2007 12:00:00 GMT
40: ORGANIZATION "Pseudo Wire Edge-to-Edge Emulation (PWE3) Working
41: Group."
42: CONTACT-INFO
43: "
44: David Zelig, Editor
45: E-mail: davidz@corrigent.com
46:
47: Thomas D. Nadeau, Editor
48: Email: tnadeau@cisco.com
49:
50: The PWE3 Working Group (email distribution pwe3@ietf.org,
51: http://www.ietf.org/html.charters/pwe3-charter.html)
52: "
53: DESCRIPTION
54: "This MIB module complements the PW-STD-MIB module for PW
55: operation over MPLS.
56:
57: Copyright (C) The IETF Trust (2006). This version
58: of this MIB module is part of RFC yyyy; see the RFC
59: itself for full legal notices.
60: -- RFC Ed.: replace yyyy with actual RFC number & remove
61: -- this note
62: "
63: -- Revision history.
64: REVISION "200705171200Z" -- 17 May 2007 12:00:00 GMT
65: DESCRIPTION
66: "First published as RFCWXYZ. "
67: -- RFC Editor: Please replace WXYZ with the correct # and remove this
68: -- note
69:
70: ::= { transmission XXXX }
70: error -
`XXXX' should start with a lower case letter
70: error -
Object identifier element `XXXX' name only allowed as first element
71: -- RFC Editor: To be assigned by IANA. Please replace XXXX
72: -- with the assigned value and remove this note.
73:
74: -- Top-level components of this MIB.
75:
76: -- Notifications
77: pwMplsNotifications OBJECT IDENTIFIER
78: ::= { pwMplsStdMIB 0 }
79:
80: -- Tables, Scalars
81: pwMplsObjects OBJECT IDENTIFIER
82: ::= { pwMplsStdMIB 1 }
83: -- Conformance
84: pwMplsConformance OBJECT IDENTIFIER
85: ::= { pwMplsStdMIB 2 }
86:
87: -- PW MPLS table
88:
89: pwMplsTable OBJECT-TYPE
90: SYNTAX SEQUENCE OF PwMplsEntry
91: MAX-ACCESS not-accessible
92: STATUS current
93: DESCRIPTION
94: "This table controls MPLS specific parameters when the PW is
95: going to be carried over MPLS PSN."
96: ::= { pwMplsObjects 1 }
97:
98: pwMplsEntry OBJECT-TYPE
99: SYNTAX PwMplsEntry
100: MAX-ACCESS not-accessible
101: STATUS current
102: DESCRIPTION
103: "A row in this table represents parameters specific to MPLS
104: PSN for a pseudo-wire (PW). The row is created
105: automatically by the local agent if the pwPsnType is
106: mpls(1). It is indexed by pwIndex, which uniquely
107: identifying a singular PW.
108: Manual entries in this table SHOULD be preserved after a
109: re-boot, the agent MUST ensure the integrity of those
110: entries.
111: If the set of entries of a specific row were found to be
112: non consistent after reboot, the PW pwOperStatus MUST be
113: declared as down(2).
114: Any read-write object in this table MAY be changed at any
115: time, however change of some objects (for example
116: pwMplsMplsType) during PW forwarding state MAY cause traffic
117: disruption."
118:
119: INDEX { pwIndex }
120:
121: ::= { pwMplsTable 1 }
122:
123: PwMplsEntry ::= SEQUENCE {
124: pwMplsMplsType BITS,
125: pwMplsExpBitsMode INTEGER,
126: pwMplsExpBits Unsigned32,
127: pwMplsTtl Unsigned32,
128: pwMplsLocalLdpID MplsLdpIdentifier,
129: pwMplsLocalLdpEntityIndex Unsigned32,
130: pwMplsPeerLdpID MplsLdpIdentifier,
131: pwMplsStorageType StorageType
132: }
133:
134: pwMplsMplsType OBJECT-TYPE
135: SYNTAX BITS {
136: mplsTe (0),
137: mplsNonTe (1),
138: pwOnly (2)
139: }
140: MAX-ACCESS read-write
141: STATUS current
142: DESCRIPTION
143: "This object is set by the operator to indicate the outer
144: tunnel types, if exists. mplsTe(0) is used if the outer
145: tunnel is set up by MPLS-TE, and mplsNonTe(1) is used if the
146: outer tunnel is set up by LDP or manually. Combination of
147: mplsTe(0) and mplsNonTe(1) MAY exist together.
148: pwOnly(2) is used if there is no outer tunnel label, i.e.
149: in static provisioning without an MPLS tunnel. pwOnly(2)
150: cannot be combined with mplsNonTe(1) or mplsTe(0).
151: An implementation that can identify automatically that the
152: peer node is directly connected, MAY support the bit
153: pwOnly(2) as read-only.
154: "
155: DEFVAL { { mplsNonTe } }
156: ::= { pwMplsEntry 1 }
157:
158: pwMplsExpBitsMode OBJECT-TYPE
159: SYNTAX INTEGER {
160: outerTunnel (1),
161: specifiedValue (2),
162: serviceDependant (3)
163: }
164:
165: MAX-ACCESS read-write
166: STATUS current
167: DESCRIPTION
168: "This object is set by the operator to determine the PW shim
169: label EXP bits. The value of outerTunnel(1) is used where
170: there is an outer tunnel - pwMplsMplsType equals to
171: mplsTe(0) or mplsNonTe(1). Note that in this case there
172: is no need to mark the PW label with the EXP bits, since the
173: PW label is not visible to the intermediate nodes.
174: If there is no outer tunnel, specifiedValue(2) SHOULD be used
175: to indicate that the value is specified by pwMplsExpBits.
176: Setting serviceDependant(3) indicates that the EXP bits are
177: set based on a rule which is implementation specific."
178:
179: DEFVAL { outerTunnel }
180: ::= { pwMplsEntry 2 }
181:
182: pwMplsExpBits OBJECT-TYPE
183: SYNTAX Unsigned32 (0..7)
184: MAX-ACCESS read-write
185: STATUS current
186: DESCRIPTION
187: "This object is set by the operator operator if
188: pwMplsExpBitsMode is set to specifiedValue(2) to indicate
189: the MPLS EXP bits to be used on the PW shim label. Otherwise,
190: it SHOULD be set to zero."
191: DEFVAL { 0 }
192: ::= { pwMplsEntry 3 }
193:
194: pwMplsTtl OBJECT-TYPE
195: SYNTAX Unsigned32 (0..255)
196: MAX-ACCESS read-write
197: STATUS current
198: DESCRIPTION
199: "This object is set by the operator to indicate the PW TTL
200: value to be used on the PW shim label."
201: DEFVAL { 2 }
202: ::= { pwMplsEntry 4 }
203:
204: pwMplsLocalLdpID OBJECT-TYPE
205: SYNTAX MplsLdpIdentifier
206: MAX-ACCESS read-write
207: STATUS current
208: DESCRIPTION
209: "The LDP identifier of the LDP entity that creates
210: this PW in the local node. As the PW labels are always
211: set from the per-platform label space, the last two octets
212: in the LDP ID MUST always both be zeros."
213: REFERENCE
214: "'LDP specifications', RFC 3036 section 2.2.2."
215: ::= { pwMplsEntry 5 }
216:
217: pwMplsLocalLdpEntityIndex OBJECT-TYPE
218: SYNTAX Unsigned32 (1..4294967295)
219: MAX-ACCESS read-write
220: STATUS current
221: DESCRIPTION
222: "The local node LDP Entity Index of the LDP entity creating
223: this PW."
224: ::= { pwMplsEntry 6 }
225:
226: pwMplsPeerLdpID OBJECT-TYPE
227: SYNTAX MplsLdpIdentifier
228: MAX-ACCESS read-only
229: STATUS current
230: DESCRIPTION
231: "The peer LDP identifier of the LDP session. Thsi object
232: SHOULD return the value zero if LDP is not used or if the
233: value is not yet known."
234: ::= { pwMplsEntry 7 }
235:
236: pwMplsStorageType OBJECT-TYPE
237: SYNTAX StorageType
238: MAX-ACCESS read-write
239: STATUS current
240: DESCRIPTION
241: "This variable indicates the storage type for this row."
242: DEFVAL { nonVolatile }
243: ::= { pwMplsEntry 8 }
244:
245: -- End of PW MPLS Table
246:
247: -- Pseudo-Wire MPLS Outbound Tunnel Table
248:
249: pwMplsOutboundTable OBJECT-TYPE
250: SYNTAX SEQUENCE OF PwMplsOutboundEntry
251: MAX-ACCESS not-accessible
252: STATUS current
253: DESCRIPTION
254: "This table reports and configures the current outbound MPLS
255: tunnels (i.e. toward the PSN) or the physical interface in
256: the case of a PW label only that carries the PW traffic. It
257: also reports the current outer tunnel and LSP which forward
258: the PW traffic."
259: ::= { pwMplsObjects 2 }
260:
261: pwMplsOutboundEntry OBJECT-TYPE
262: SYNTAX PwMplsOutboundEntry
263: MAX-ACCESS not-accessible
264: STATUS current
265: DESCRIPTION
266: "A row in this table configures the outer tunnel used for
267: carrying the PW traffic toward the PSN.
268: In the case of PW labels only, it configures the interface
269: that will carry the PW traffic.
270:
271: An entry in this table augments the pwMplsEntry, and is
272: created automatically when the corresponding row has been
273: created by the agent in the pwMplsEntry.
274:
275: This table points to the appropriate MPLS MIB module:
276:
277: In the MPLS-TE case, the three objects relevant to the
278: indexing of a TE tunnel head-end (as used in the
279: MPLS-TE-STD-MIB) are to be configured, and the tunnel
280: instance indicates the LSP that is currently in use for
281: forwarding the traffic.
282:
283: In case of signaled Non-TE MPLS (an outer tunnel label
284: assigned by LDP) the table points to the XC entry in the
285: LSR-STD-MIB. If the Non-TE MPLS tunnel is manually
286: configured, the operator configures the XC pointer to this
287: tunnel.
288:
289: In case of PW label only (no outer tunnel) the ifIndex of
290: the port to carry the PW is configured here.
291:
292: It is possible to associate a PW to one TE tunnel head-end
293: and a non-TE tunnel together. An indication in this table
294: will report the currently active one. In addition, in the
295: TE case the table reports the active tunnel instance
296: (i.e. the specific LSP in use).
297: Any read-write object in this table MAY be changed at any
298: time, however change of some objects (for example
299: MPLS-TE indexes) during PW forwarding state MAY cause traffic
300: disruption."
301:
302: AUGMENTS { pwMplsEntry }
303:
304: ::= { pwMplsOutboundTable 1 }
305:
306: PwMplsOutboundEntry ::= SEQUENCE {
307: pwMplsOutboundLsrXcIndex MplsIndexType,
308: pwMplsOutboundTunnelIndex MplsTunnelIndex,
309: pwMplsOutboundTunnelInstance MplsTunnelInstanceIndex,
310: pwMplsOutboundTunnelLclLSR MplsLsrIdentifier,
311: pwMplsOutboundTunnelPeerLSR MplsLsrIdentifier,
312: pwMplsOutboundIfIndex InterfaceIndexOrZero,
313: pwMplsOutboundTunnelTypeInUse INTEGER
314: }
315:
316: pwMplsOutboundLsrXcIndex OBJECT-TYPE
317: SYNTAX MplsIndexType
318: MAX-ACCESS read-write
319: STATUS current
320: DESCRIPTION
321: "This object is applicable if pwMplsMplsType mplsNonTe(1)
322: bit is set, and MUST return a value zero otherwise.
323: If the outer tunnel is signaled, the object is read-only
324: and indicates the XC index in the MPLS-LSR-STD-MIB of the
325: outer tunnel toward the peer. Otherwise (tunnel is set up
326: manually) the operator defines the XC index of the manually-
327: created outer tunnel through this object.
328: "
329: ::= { pwMplsOutboundEntry 1 }
330:
331:
332: pwMplsOutboundTunnelIndex OBJECT-TYPE
333: SYNTAX MplsTunnelIndex
334: MAX-ACCESS read-write
335: STATUS current
336: DESCRIPTION
337: "This object is applicable if pwMplsMplsType mplsTe(0)
338: bit is set, and MUST return a value zero otherwise.
339: It is part of the set of indexes for the outbound tunnel.
340: The operator sets this object to represent the desired
341: tunnel head-end toward the peer for carrying the PW
342: traffic.
343: "
344: ::= { pwMplsOutboundEntry 2 }
345:
346: pwMplsOutboundTunnelInstance OBJECT-TYPE
347: SYNTAX MplsTunnelInstanceIndex
348: MAX-ACCESS read-only
349: STATUS current
350: DESCRIPTION
351: "This object is applicable if pwMplsMplsType mplsTe(0)
352: bit is set, and MUST return a value zero otherwise.
353: It indicates the actual tunnel instance that is currently
354: active and carrying the PW traffic. It SHOULD return the
355: value zero if the information from the MPLS-TE
356: application is not yet known.
357: "
358: ::= { pwMplsOutboundEntry 3 }
359:
360: pwMplsOutboundTunnelLclLSR OBJECT-TYPE
361: SYNTAX MplsLsrIdentifier
362: MAX-ACCESS read-write
363: STATUS current
364: DESCRIPTION
365: "This object is applicable if pwMplsMplsType mplsTe(0)
366: bit is set, and MUST return a value of all zeros otherwise.
367: It is part of the set of indexes for the outbound tunnel.
368: The operator sets this object to represent the desired
369: tunnel head-end toward the peer for carrying the PW
370: traffic.
371: "
372: ::= { pwMplsOutboundEntry 4 }
373:
374: pwMplsOutboundTunnelPeerLSR OBJECT-TYPE
375: SYNTAX MplsLsrIdentifier
376: MAX-ACCESS read-write
377: STATUS current
378: DESCRIPTION
379: "This object is applicable if pwMplsMplsType mplsTe(0)
380: bit is set, and MUST return a value zero otherwise.
381: It is part of the set of indexes for the outbound tunnel.
382: Note that in most cases it equals to pwPeerAddr.
383: "
384: ::= { pwMplsOutboundEntry 5 }
385:
386: pwMplsOutboundIfIndex OBJECT-TYPE
387: SYNTAX InterfaceIndexOrZero
388: MAX-ACCESS read-write
389: STATUS current
390: DESCRIPTION
391: "This object is applicable if pwMplsMplsType pwOnly(0)
392: bit is set, and MUST return a value zero otherwise.
393: The operator configures the ifIndex of the outbound port
394: in this case.
395: "
396: ::= { pwMplsOutboundEntry 6 }
397:
398: pwMplsOutboundTunnelTypeInUse OBJECT-TYPE
399: SYNTAX INTEGER {
400: notYetKnown (1),
401: mplsTe (2),
402: mplsNonTe (3),
403: pwOnly (4)
404: }
405: MAX-ACCESS read-only
406: STATUS current
407: DESCRIPTION
408: "This object indicates the current tunnel that is carrying
409: the PW traffic.
410: The value of notYetKnown(1) should be used if the agent is
411: currently unable to determine which tunnel or interface is
412: carrying the PW, for example because both tunnels are in
413: operational status down.
414: "
415: ::= { pwMplsOutboundEntry 7 }
416:
417: -- End of PW MPLS Outbound Tunnel table
418:
419: -- PW MPLS inbound table
420:
421: pwMplsInboundTable OBJECT-TYPE
422: SYNTAX SEQUENCE OF PwMplsInboundEntry
423: MAX-ACCESS not-accessible
424: STATUS current
425: DESCRIPTION
426: "This table indicates the PW LDP XC entry in the
427: MPLS-LSR-STD-MIB for signaled PWs.
428: "
429: ::= { pwMplsObjects 3 }
430:
431:
432: pwMplsInboundEntry OBJECT-TYPE
433: SYNTAX PwMplsInboundEntry
434: MAX-ACCESS not-accessible
435: STATUS current
436: DESCRIPTION
437: "A row in this table is created by the agent
438: for each signaled PW, and shows the XC index related to
439: the PW signaling in the inbound direction in the
440: MPLS-LSR-STD-MIB that controls and display the information
441: for all the LDP signaling processes in the local node.
442: "
443: INDEX { pwIndex }
444:
445: ::= { pwMplsInboundTable 1 }
446:
447: PwMplsInboundEntry ::= SEQUENCE {
448: pwMplsInboundXcIndex MplsIndexType
449: }
450:
451: pwMplsInboundXcIndex OBJECT-TYPE
452: SYNTAX MplsIndexType
453: MAX-ACCESS read-only
454: STATUS current
455: DESCRIPTION
456: "The XC index representing this PW in the inbound
457: direction. It MUST return the value zero if the
458: information is not yet known."
459: ::= { pwMplsInboundEntry 1 }
460:
461: -- End of PW MPLS inbound table
462:
463: -- PW to Non-TE mapping Table.
464:
465: pwMplsNonTeMappingTable OBJECT-TYPE
466: SYNTAX SEQUENCE OF PwMplsNonTeMappingEntry
467: MAX-ACCESS not-accessible
468: STATUS current
469: DESCRIPTION
470: "This table indicates the PW association to the outbound
471: Tunnel in non-TE applications, maps the PW to it's (inbound)
472: XC entry, and indicates the PW-to-physical interface mapping
473: for a PW without an outer tunnel.
474: "
475: ::= { pwMplsObjects 4 }
476:
477: pwMplsNonTeMappingEntry OBJECT-TYPE
478: SYNTAX PwMplsNonTeMappingEntry
479: MAX-ACCESS not-accessible
480: STATUS current
481: DESCRIPTION
482: "A row in this table displays the association
483: between the PW and
484: - its non-TE MPLS outbound outer Tunnel or,
485: - its XC entry in the MPLS-LSR-STD-MIB,
486: - its physical interface if there is no outer tunnel
487: (PW label only) and manual configuration.
488:
489: Rows are created in this table by the agent depending on
490: the setting of pwMplsMplsType:
491:
492: - If pwMplsMplsType mplsNonTe(1) bit is set, the agent
493: creates a row for the outbound direction
494: (pwMplsNonTeMappingDirection set to psnBound(1)).
495: The pwMplsNonTeMappingXcIndex holds the XC index in the
496: MPLS-LSR-STD-MIB of the PSN bound outer tunnel.
497: pwMplsNonTeMappingIfIndex MUST be zero for this row.
498:
499: - If pwMplsMplsType pwOnly(2) bit is set, the agent
500: creates a row for the outbound direction
501: (pwMplsNonTeMappingDirection set to psnBound(1)).
502: The pwMplsNonTeMappingIfIndex holds the ifIndex of the
503: physical port this PW will use in the outbound direction.
504: pwMplsNonTeMappingXcIndex MUST be zero for this row.
505:
506: - If the PW has been set up by a signaling protocol (i.e.
507: pwOwner equal pwIdFecSignaling(2) or
508: genFecSignaling(3)), the agent creates a row for the
509: inbound direction (pwMplsNonTeMappingDirection set to
510: fromPsn(2)).
511: The pwMplsNonTeMappingXcIndex holds the XC index in the
512: MPLS-LSR-STD-MIB of the PW LDP generated XC entry.
513: pwMplsNonTeMappingIfIndex MUST be zero for this row.
514:
515: An application can use this table to quickly retrieve the
516: PW carried over specific non-TE MPLS outer tunnel or
517: physical interface.
518: "
519:
520: INDEX { pwMplsNonTeMappingDirection,
521: pwMplsNonTeMappingXcIndex,
522: pwMplsNonTeMappingIfIndex,
523: pwMplsNonTeMappingPwIndex }
524:
525: ::= { pwMplsNonTeMappingTable 1 }
526:
527: PwMplsNonTeMappingEntry ::= SEQUENCE {
528: pwMplsNonTeMappingDirection INTEGER,
529: pwMplsNonTeMappingXcIndex MplsIndexType,
530: pwMplsNonTeMappingIfIndex InterfaceIndexOrZero,
531: pwMplsNonTeMappingPwIndex PwIndexType
532: }
533:
534: pwMplsNonTeMappingDirection OBJECT-TYPE
535: SYNTAX INTEGER {
536: psnBound (1),
537: fromPsn (2)
538: }
539: MAX-ACCESS not-accessible
540: STATUS current
541: DESCRIPTION
542: "Index for the conceptual XC row identifying the tunnel-to-PW
543: mappings, indicating the direction of the packet flow for
544: this entry.
545: psnBound(1) indicates that the entry is related to
546: packets toward the PSN.
547: fromPsn(2) indicates that the entry is related to
548: packets coming from the PSN.
549: "
550: ::= { pwMplsNonTeMappingEntry 1 }
551:
552: pwMplsNonTeMappingXcIndex OBJECT-TYPE
553: SYNTAX MplsIndexType
554: MAX-ACCESS not-accessible
555: STATUS current
556: DESCRIPTION
557: "See the description clause of pwMplsNonTeMappingEntry for
558: the usage guidelines of this object."
559: ::= { pwMplsNonTeMappingEntry 2 }
560:
561: pwMplsNonTeMappingIfIndex OBJECT-TYPE
562: SYNTAX InterfaceIndexOrZero
563: MAX-ACCESS not-accessible
564: STATUS current
565: DESCRIPTION
566: "See the description clause of pwMplsNonTeMappingEntry for
567: the usage guidelines of this object."
568: ::= { pwMplsNonTeMappingEntry 3 }
569:
570: pwMplsNonTeMappingPwIndex OBJECT-TYPE
571: SYNTAX PwIndexType
572: MAX-ACCESS read-only
573: STATUS current
574: DESCRIPTION
575: "The value that represent the PW in the pwTable."
576: ::= { pwMplsNonTeMappingEntry 4 }
577:
578: -- End of PW to Non-TE mapping Table.
579:
580:
581: -- PW to TE MPLS tunnels mapping Table.
582:
583: pwMplsTeMappingTable OBJECT-TYPE
584: SYNTAX SEQUENCE OF PwMplsTeMappingEntry
585: MAX-ACCESS not-accessible
586: STATUS current
587: DESCRIPTION
588: "This table reports the PW association to the
589: outbound MPLS tunnel for MPLS-TE applications."
590: ::= { pwMplsObjects 5 }
591:
592: pwMplsTeMappingEntry OBJECT-TYPE
593: SYNTAX PwMplsTeMappingEntry
594: MAX-ACCESS not-accessible
595: STATUS current
596: DESCRIPTION
597: "A row in this table represents the association
598: between a PW and its MPLS-TE outer (head-end) Tunnel.
599:
600: An application can use this table to quickly retrieve the
601: list of the PWs that are configured on a specific MPLS-TE
602: outer tunnel.
603:
604: The pwMplsTeMappingTunnelInstance reports the actual
605: LSP out of the tunnel head-end that is currently
606: forwarding the traffic.
607:
608: The table in indexed by the head-end indexes of a TE
609: tunnel and the PW index.
610: "
611:
612: INDEX { pwMplsTeMappingTunnelIndex,
613: pwMplsTeMappingTunnelInstance,
614: pwMplsTeMappingTunnelPeerLsrID,
615: pwMplsTeMappingTunnelLocalLsrID,
616: pwMplsTeMappingPwIndex }
617:
618: ::= { pwMplsTeMappingTable 1 }
619:
620: PwMplsTeMappingEntry ::= SEQUENCE {
621: pwMplsTeMappingTunnelIndex MplsTunnelIndex,
622: pwMplsTeMappingTunnelInstance MplsTunnelInstanceIndex,
623: pwMplsTeMappingTunnelPeerLsrID MplsLsrIdentifier,
624: pwMplsTeMappingTunnelLocalLsrID MplsLsrIdentifier,
625: pwMplsTeMappingPwIndex PwIndexType
626: }
627:
628: pwMplsTeMappingTunnelIndex OBJECT-TYPE
629: SYNTAX MplsTunnelIndex
630: MAX-ACCESS not-accessible
631: STATUS current
632: DESCRIPTION
633: "Primary index for the conceptual row identifying the
634: MPLS-TE tunnel that is carrying the PW traffic."
635: ::= { pwMplsTeMappingEntry 1 }
636:
637: pwMplsTeMappingTunnelInstance OBJECT-TYPE
638: SYNTAX MplsTunnelInstanceIndex
639: MAX-ACCESS not-accessible
640: STATUS current
641: DESCRIPTION
642: "This object identifies the MPLS-TE LSP that is carrying the
643: PW traffic. It MUST return the value zero if the
644: information of the specific LSP is not yet known.
645: Note that based on the recommendation in the
646: MPLS-TC-STD-MIB, instance index 0 should refer to the
647: configured tunnel interface."
648: ::= { pwMplsTeMappingEntry 2 }
649:
650: pwMplsTeMappingTunnelPeerLsrID OBJECT-TYPE
651: SYNTAX MplsLsrIdentifier
652: MAX-ACCESS not-accessible
653: STATUS current
654: DESCRIPTION
655: "This object identifies the Peer LSR when the outer tunnel
656: is MPLS-TE."
657: ::= { pwMplsTeMappingEntry 3 }
658:
659: pwMplsTeMappingTunnelLocalLsrID OBJECT-TYPE
660: SYNTAX MplsLsrIdentifier
661: MAX-ACCESS not-accessible
662: STATUS current
663: DESCRIPTION
664: "This object identifies the local LSR."
665: ::= { pwMplsTeMappingEntry 4 }
666:
667: pwMplsTeMappingPwIndex OBJECT-TYPE
668: SYNTAX PwIndexType
669: MAX-ACCESS read-only
670: STATUS current
671: DESCRIPTION
672: "This object returns the value that represents the PW in the
673: pwTable."
674: ::= { pwMplsTeMappingEntry 5 }
675:
676: -- End of PW to TE MPLS tunnels mapping Table.
677:
678: -- conformance information
679:
680: pwMplsGroups OBJECT IDENTIFIER ::= { pwMplsConformance 1 }
681: pwMplsCompliances OBJECT IDENTIFIER ::= { pwMplsConformance 2 }
682:
683: -- Compliance requirement for fully compliant implementations.
684:
685: pwMplsModuleFullCompliance MODULE-COMPLIANCE
686: STATUS current
687: DESCRIPTION
688: "The compliance statement for agents that provide full
689: support for PW-MPLS-STD-MIB Module. Such devices can
690: then be monitored and also be configured using
691: this MIB module."
692:
693: MODULE -- this module
694: MANDATORY-GROUPS { pwMplsGroup,
695: pwMplsOutboundMainGroup,
696: pwMplsInboundGroup,
697: pwMplsMappingGroup
698: }
699:
700: GROUP pwMplsOutboundTeGroup
701: DESCRIPTION "This group MUST be supported if the implementation
702: allows MPLS-TE tunnels to carry PW traffic.
703: "
704:
705: OBJECT pwMplsMplsType
706: DESCRIPTION "Support of pwOnly(2) is not required. At least one
707: of mplsTe(0) or mplsNonTe(1) MUST be supported if
708: signaling of PW is supported.
709: "
710:
711: OBJECT pwMplsExpBitsMode
712: DESCRIPTION "Support of specifiedValue(2) and
713: serviceDependant(3) is optional.
714: "
715:
716: OBJECT pwMplsLocalLdpID
717: MIN-ACCESS read-only
718: DESCRIPTION "A read-write access is required if the
719: implementation supports more than one LDP entity
720: identifier for PW signaling.
721: "
722:
723: OBJECT pwMplsLocalLdpEntityIndex
724: MIN-ACCESS read-only
725: DESCRIPTION "A read-write access is required if the
726: implementation supports more than one LDP entity
727: index for PW signaling.
728: "
729:
730: OBJECT pwMplsOutboundLsrXcIndex
731: MIN-ACCESS read-only
732: DESCRIPTION "A value other than zero MUST be supported if the
733: implementation supports non-TE signaling of the
734: outer tunnel.
735: A read-write access MUST be supported if the
736: implementation supports PW label manual setting
737: and carrying them over non-TE tunnels.
738: "
739:
740: OBJECT pwMplsOutboundIfIndex
741: MIN-ACCESS read-only
742: DESCRIPTION "A value other than zero and read-write operations
743: MUST be supported if the implementation supports
744: manually configured PW without MPLS outer tunnel.
745: "
746: ::= { pwMplsCompliances 1 }
747:
748: -- Compliance requirement for Read Only compliant implementations.
749:
750: pwMplsModuleReadOnlyCompliance MODULE-COMPLIANCE
751: STATUS current
752: DESCRIPTION
753: "The compliance statement for agents that provide read-
754: only support for the PW-MPLS-STD-MIB Module. Such
755: devices can then be monitored but cannot be configured
756: using this MIB module."
757:
758: MODULE -- this module
759: MANDATORY-GROUPS { pwMplsGroup,
760: pwMplsOutboundMainGroup,
761: pwMplsInboundGroup,
762: pwMplsMappingGroup
763: }
764:
765: GROUP pwMplsOutboundTeGroup
766: DESCRIPTION "This group MUST be supported if the implementation
767: allows MPLS-TE tunnels to carry PW traffic.
768: "
769:
770: OBJECT pwMplsMplsType
771: MIN-ACCESS read-only
772: DESCRIPTION "Write access is not required.
773: Support of pwOnly(2) is not required. At least one
774: of mplsTe(0) or mplsNonTe(1) MUST be supported if
775: signaling of PW is supported.
776: "
777:
778: OBJECT pwMplsExpBitsMode
779: MIN-ACCESS read-only
780: DESCRIPTION "Write access is not required.
781: Support of specifiedValue(2) and serviceDependant(3)
782: is optional.
783: "
784:
785: OBJECT pwMplsExpBits
786: MIN-ACCESS read-only
787: DESCRIPTION "Write access is not required.
788: "
789: OBJECT pwMplsTtl
790: MIN-ACCESS read-only
791: DESCRIPTION "Write access is not required.
792: "
793:
794: OBJECT pwMplsLocalLdpID
795: MIN-ACCESS read-only
796: DESCRIPTION "Write access is not required.
797: "
798:
799: OBJECT pwMplsLocalLdpEntityIndex
800: MIN-ACCESS read-only
801: DESCRIPTION "Write access is not required.
802: "
803:
804: OBJECT pwMplsStorageType
805: MIN-ACCESS read-only
806: DESCRIPTION "Write access is not required.
807: "
808:
809: OBJECT pwMplsOutboundLsrXcIndex
810: MIN-ACCESS read-only
811: DESCRIPTION "Write access is not required.
812: A value other than zero MUST be supported if the
813: implementation supports non-TE signaling of the
814: outer tunnel.
815: "
816:
817: OBJECT pwMplsOutboundTunnelIndex
818: MIN-ACCESS read-only
819: DESCRIPTION "Write access is not required.
820: "
821:
822: OBJECT pwMplsOutboundTunnelLclLSR
823: MIN-ACCESS read-only
824: DESCRIPTION "Write access is not required.
825: "
826:
827: OBJECT pwMplsOutboundTunnelPeerLSR
828: MIN-ACCESS read-only
829: DESCRIPTION "Write access is not required.
830: "
831:
832: OBJECT pwMplsOutboundIfIndex
833: MIN-ACCESS read-only
834: DESCRIPTION "Write access is not required.
835: A value other than zero MUST be supported if the
836: implementation supports manually configured PW
837: without MPLS outer tunnel.
838: "
839: ::= { pwMplsCompliances 2 }
840:
841: -- Units of conformance.
842:
843: pwMplsGroup OBJECT-GROUP
844: OBJECTS {
845: pwMplsMplsType,
846: pwMplsExpBitsMode,
847: pwMplsExpBits,
848: pwMplsTtl,
849: pwMplsLocalLdpID,
850: pwMplsLocalLdpEntityIndex,
851: pwMplsPeerLdpID,
852: pwMplsStorageType
853: }
854:
855: STATUS current
856: DESCRIPTION
857: "Collection of objects needed for PW over MPLS PSN
858: configuration."
859: ::= { pwMplsGroups 1 }
860:
861: pwMplsOutboundMainGroup OBJECT-GROUP
862: OBJECTS {
863: pwMplsOutboundLsrXcIndex,
864: pwMplsOutboundIfIndex,
865: pwMplsOutboundTunnelTypeInUse
866: }
867:
868: STATUS current
869: DESCRIPTION
870: "Collection of objects needed for outbound association of
871: PW and MPLS tunnel."
872: ::= { pwMplsGroups 2 }
873:
874: pwMplsOutboundTeGroup OBJECT-GROUP
875: OBJECTS {
876: pwMplsOutboundTunnelIndex,
877: pwMplsOutboundTunnelInstance,
878: pwMplsOutboundTunnelLclLSR,
879: pwMplsOutboundTunnelPeerLSR
880: }
881:
882: STATUS current
883: DESCRIPTION
884: "Collection of objects needed for outbound association of
885: PW and MPLS-TE tunnel."
886: ::= { pwMplsGroups 3 }
887:
888: pwMplsInboundGroup OBJECT-GROUP
889: OBJECTS {
890: pwMplsInboundXcIndex
891: }
892:
893: STATUS current
894: DESCRIPTION
895: "Collection of objects needed for inbound PW presentation.
896: This group MUST be supported if PW signaling through LDP is
897: used."
898: ::= { pwMplsGroups 4 }
899:
900: pwMplsMappingGroup OBJECT-GROUP
901: OBJECTS {
902: pwMplsNonTeMappingPwIndex,
903: pwMplsTeMappingPwIndex
904: }
905:
906: STATUS current
907: DESCRIPTION
908: "Collection of objects needed for mapping association of
909: PW and MPLS tunnel."
910: ::= { pwMplsGroups 5 }
911:
912: END
913:
914: --
915: -- Copyright (C) The IETF Trust (2007).
916: --
917: -- This document is subject to the rights, licenses and restrictions
918: -- contained in BCP 78, and except as set forth therein, the authors
919: -- retain all their rights.
920: --
921: -- This document and the information contained herein are provided on an
922: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
923: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
924: -- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
925: -- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
926: -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
927: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
928: --
929: --
930: -- Intellectual Property
931: --
932: -- The IETF takes no position regarding the validity or scope of any
933: -- Intellectual Property Rights or other rights that might be claimed to
934: -- pertain to the implementation or use of the technology described in
935: -- this document or the extent to which any license under such rights
936: -- might or might not be available; nor does it represent that it has
937: -- made any independent effort to identify any such rights. Information
938: -- on the procedures with respect to rights in RFC documents can be
939: -- found in BCP 78 and BCP 79.
940: --
941: -- Copies of IPR disclosures made to the IETF Secretariat and any
942: -- assurances of licenses to be made available, or the result of an
943: -- attempt made to obtain a general license or permission for the use of
944: -- such proprietary rights by implementers or users of this
945: -- specification can be obtained from the IETF on-line IPR repository at
946: -- http://www.ietf.org/ipr.
947: --
948: -- The IETF invites any interested party to bring to its attention any
949: -- copyrights, patents or patent applications, or other proprietary
950: -- rights that may cover technology that may be required to implement
951: -- this standard. Please address the information to the IETF at
952: -- ietf-ipr@ietf.org.
953: --
954: --
955: -- Acknowledgment
956: --
957: -- Funding for the RFC Editor function is provided by the IETF
958: -- Administrative Support Activity (IASA).
959: