smilint output for ./MPLS-TE-P2MP-STD-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 2 |
| minor error | 5 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 1 |
| group-member-invalid (minor error) | 5 |
| object-identifier-not-prefix (error) | 1 |
Messages:
MPLS-TE-P2MP-STD-MIB
1: -- extracted from draft-ietf-mpls-p2mp-te-mib-05.txt
2: -- at Tue Sep 25 06:09:21 2007
3:
4: MPLS-TE-P2MP-STD-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
8: Unsigned32, Counter32, Counter64, TimeTicks
9: FROM SNMPv2-SMI -- RFC 2578
10: MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
11: FROM SNMPv2-CONF -- RFC 2580
12: TruthValue, RowStatus, StorageType, TimeStamp
13: FROM SNMPv2-TC -- RFC 2579
14: mplsStdMIB, MplsPathIndexOrZero
15: FROM MPLS-TC-STD-MIB -- RFC 3811
16: MplsIndexType
17: FROM MPLS-LSR-STD-MIB -- RFC 3813
18: mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId,
19: mplsTunnelEgressLSRId
20: FROM MPLS-TE-STD-MIB -- RFC 3812
21: IndexInteger, IndexIntegerNextFree
22: FROM DIFFSERV-MIB -- RFC 3289
23: InetAddress, InetAddressType
24: FROM INET-ADDRESS-MIB -- RFC 4001
25: ;
26:
27: mplsTeP2mpStdMIB MODULE-IDENTITY
28: LAST-UPDATED "200709170000Z" -- Setember 17, 2007
29: ORGANIZATION
30: "Multiprotocol Label Switching (MPLS) Working Group"
31: CONTACT-INFO
32: " Adrian Farrel
33: Old Dog Consulting
34: Email: adrian@olddog.co.uk
35:
36: Seisho Yasukawa
37: NTT Corporation
38: Email: s.yasukawa@hco.ntt.co.jp
39:
40: Thomas D. Nadeau
41: British Telecom
42: Email: thomas.nadeau@bt.com
43:
44: Comments about this document should be emailed
45: directly to the MPLS working group mailing list at
46: mpls@lists.ietf.org"
47:
48: DESCRIPTION
49: "Copyright (C) The IETF Trust (2007). The initial version of
50: this MIB module was published in RFC XXXX. For full legal
51: notices see the RFC itself or see:
52: http://www.ietf.org/copyrights/ianamib.html
53: -- RFC Editor. Please replace XXXX with the RFC number for this
54: -- document and remove this note.
55:
56: This MIB module contains managed object definitions
57: for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE)
58: defined in:
59: 1. Signaling Requirements for Point-to-Multipoint
60: Traffic-Engineered MPLS Label Switched Paths (LSPs),
61: S. Yasukawa, RFC 4461, April 2006.
62: 2. Extensions to Resource Reservation Protocol - Traffic
63: Engineering (RSVP-TE) for Point-to-Multipoint TE Label
64: Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D.,
65: and Yasukawa, S., RFC 4875, May 2007."
66:
67: -- Revision history.
68:
69: REVISION
70: "200709170000Z" -- Setember 17, 2007
71: DESCRIPTION
72: "Initial version issued as part of RFC XXXX."
73: -- RFC Editor. Please replace XXXX with the RFC number for this
74: -- document and remove this note.
75:
76: ::= { mplsStdMIB YYY }
76: error -
`YYY' should start with a lower case letter
76: error -
Object identifier element `YYY' name only allowed as first element
77:
78: -- RFC Editor. Please replace YYY with the codepoint issued by IANA
79: -- and remove this note.
80:
81: -- Top level components of this MIB module.
82:
83: -- notifications
84: mplsTeP2mpNotifications OBJECT IDENTIFIER ::= { mplsTeP2mpStdMIB 0 }
85: -- tables, scalars
86: mplsTeP2mpScalars OBJECT IDENTIFIER ::= { mplsTeP2mpStdMIB 1 }
87: mplsTeP2mpObjects OBJECT IDENTIFIER ::= { mplsTeP2mpStdMIB 2 }
88: -- conformance
89: mplsTeP2mpConformance OBJECT IDENTIFIER ::= { mplsTeP2mpStdMIB 3 }
90: -- MPLS P2MP Tunnel scalars.
91:
92: mplsTeP2mpTunnelConfigured OBJECT-TYPE
93: SYNTAX Unsigned32
94: MAX-ACCESS read-only
95: STATUS current
96: DESCRIPTION
97: "The number of P2MP tunnels configured on this device. A
98: tunnel is considered configured if the mplsTunnelRowStatus
99: in MPLS-TE-STD-MIB is active(1)."
100: REFERENCE
101: "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
102: Engineering (TE) Management Information Base (MIB),
103: Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
104: ::= { mplsTeP2mpScalars 1 }
105:
106: mplsTeP2mpTunnelActive OBJECT-TYPE
107: SYNTAX Unsigned32
108: MAX-ACCESS read-only
109: STATUS current
110: DESCRIPTION
111: "The number of P2MP tunnels active on this device. A
112: tunnel is considered active if the mplsTunnelOperStatus
113: in MPLS-TE-STD-MIB is up(1)."
114: REFERENCE
115: "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
116: Engineering (TE) Management Information Base (MIB),
117: Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
118: ::= { mplsTeP2mpScalars 2 }
119:
120: mplsTeP2mpTunnelTotalMaxHops OBJECT-TYPE
121: SYNTAX Unsigned32
122: MAX-ACCESS read-only
123: STATUS current
124: DESCRIPTION
125: "The maximum number of hops that can be specified for an
126: entire P2MP tunnel on this device. This object should be
127: used in conjunction with mplsTunnelMaxHops in
128: MPLS-TE-STD-MIB that is used in the context of P2MP tunnels
129: to express the maximum number of hops to any individual
130: destination of a P2MP tunnel that can be configured on this
131: device. mplsTeP2mpTunnelTotalMaxHops would normally be set
132: larger than or equal to mplsTunnelMaxHops."
133: REFERENCE
134: "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
135: Engineering (TE) Management Information Base (MIB),
136: Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
137: ::= { mplsTeP2mpScalars 3 }
138:
139: -- End of MPLS Tunnel scalars.
140: -- MPLS P2MP tunnel table.
141:
142: mplsTeP2mpTunnelTable OBJECT-TYPE
143: SYNTAX SEQUENCE OF MplsTeP2mpTunnelEntry
144: MAX-ACCESS not-accessible
145: STATUS current
146: DESCRIPTION
147: "The mplsTeP2mpTunnelTable allows new P2MP MPLS tunnels to be
148: created between an LSR and one or more remote end-points,
149: and existing P2MP tunnels to be reconfigured or removed.
150:
151: This table sparse augments mplsTunnelTable in
152: MPLS-TE-STD-MIB such that entries in that table can be
153: flagged as point-to-multipoint, and can be configured and
154: monitored appropriately."
155: REFERENCE
156: "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
157: Engineering (TE) Management Information Base (MIB),
158: Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
159: ::= { mplsTeP2mpObjects 1 }
160:
161: mplsTeP2mpTunnelEntry OBJECT-TYPE
162: SYNTAX MplsTeP2mpTunnelEntry
163: MAX-ACCESS not-accessible
164: STATUS current
165: DESCRIPTION
166: "An entry in this table represents a P2MP MPLS tunnel.
167: An entry can be created by a network administrator or by an
168: SNMP agent as instructed by an MPLS signaling protocol.
169:
170: An entry in this table MUST correspond to an entry in the
171: mplsTunnelTable in MPLS-TE-STD-MIB. This table shares index
172: objects with that table and sparse augments that table.
173:
174: Thus, an entry in this table can only be created at the same
175: time as or after a corresponding entry in mplsTunnelTable,
176: and an entry in mplsTunnelTable cannot be deleted while a
177: corresponding entry exists in this table.
178:
179: This table entry includes a row status object, but
180: administrative and operational statuses should be taken from
181: mplsTunnelAdminStatus and mplsTunnelOperStatus in the
182: corresponding entry in mplsTunnelTable."
183: REFERENCE
184: "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
185: Engineering (TE) Management Information Base (MIB),
186: Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
187:
188: INDEX { mplsTunnelIndex,
189: mplsTunnelInstance,
190: mplsTunnelIngressLSRId,
191: mplsTunnelEgressLSRId
192: }
193: ::= { mplsTeP2mpTunnelTable 1 }
194:
195: MplsTeP2mpTunnelEntry ::= SEQUENCE {
196: mplsTeP2mpTunnelP2mpIntegrity TruthValue,
197: mplsTeP2mpTunnelBranchRole INTEGER,
198: mplsTeP2mpTunnelSubGroupOriginType InetAddressType,
199: mplsTeP2mpTunnelSubGroupOrigin InetAddress,
200: mplsTeP2mpTunnelSubGroupID Unsigned32,
201: mplsTeP2mpTunnelRowStatus RowStatus,
202: mplsTeP2mpTunnelStorageType StorageType
203: }
204:
205: mplsTeP2mpTunnelP2mpIntegrity OBJECT-TYPE
206: SYNTAX TruthValue
207: MAX-ACCESS read-create
208: STATUS current
209: DESCRIPTION
210: "Denotes whether or not P2MP Integrity is required for this
211: tunnel.
212: If P2MP integrity is operational on a P2MP tunnel then the
213: failure of the path to any of the tunnel destinations should
214: cause the teardown of the entire P2MP tunnel."
215: REFERENCE
216: "RFC 4875 - Extensions to Resource Reservation Protocol -
217: Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
218: Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
219: and S. Yasukawa, May 2007."
220: DEFVAL { false }
221: ::= { mplsTeP2mpTunnelEntry 2 }
222:
223: mplsTeP2mpTunnelBranchRole OBJECT-TYPE
224: SYNTAX INTEGER { notBranch(1),
225: branch(2),
226: bud(3) }
227: MAX-ACCESS read-create
228: STATUS current
229: DESCRIPTION
230: "This value supplements the value in the object
231: mplsTunnelRole in MPLS-TE-STD-MIB that indicates the role
232: of this LSR in the tunnel represented by this entry in
233: mplsTeP2mpTunnelTable.
234: mplsTunnelRole may take any of the values:
235: head(1),
236: transit(2),
237: tail(3),
238: headTail(4)
239:
240: If this LSR is an ingress and there is exactly one
241: out-segment, mplsTunnelRole should contain the value
242: head(1), and mplsTeP2mpTunnelBranchRole should have the
243: value notBranch(1).
244:
245: If this LSR is an ingress with more than one out segment,
246: mplsTunnelRole should contain the value head(1), and
247: mplsTeP2mpTunnelBranchRole should have the value branch(2).
248:
249: If this LSR is an ingress, an egress, and there is one or
250: more out-segments, mplsTunnelRole should contain the value
251: headTail(4), and mplsTeP2mpTunnelBranchRole should have the
252: value bud(3).
253:
254: If this LSR is a transit with exactly one out-segment,
255: mplsTunnelRole should contain the value transit(2), and
256: mplsTeP2mpTunnelBranchRole should have the value
257: notBranch(1).
258:
259: If this LSR is a transit with more than one out-segment,
260: mplsTunnelRole should contain the value transit(2), and
261: mplsTeP2mpTunnelBranchRole should have the value branch(2).
262:
263: If this LSR is a transit with one or more out-segments and
264: is also an egress, mplsTunnelRole should contain the value
265: transit(2), and mplsTeP2mpTunnelBranchRole should have the
266: value bud(3).
267:
268: If this LSR is an egress with no out-segment and is not the
269: ingress, mplsTunnelRole should contain the value tail(3),
270: and mplsTeP2mpTunnelBranchRole should have the value
271: notBranch(1).
272:
273: If this LSR is an egress and has one or more out-segments,
274: mplsTunnelRole should contain the value transit(1), and
275: mplsTeP2mpTunnelBranchRole should have the value bud(3)."
276: REFERENCE
277: "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
278: Engineering (TE) Management Information Base (MIB),
279: Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
280: DEFVAL { notBranch }
281: ::= { mplsTeP2mpTunnelEntry 3 }
282:
283: mplsTeP2mpTunnelSubGroupOriginType OBJECT-TYPE
284: SYNTAX InetAddressType
285: MAX-ACCESS read-only
286: STATUS current
287: DESCRIPTION
288: "This object identifies the type of address carried in
289: mplsTeP2mpTunnelSubGroupOrigin.
290:
291: Since the object mplsTeP2mpTunnelSubGroupOrigin must conform
292: to the protocol specification, this object must return
293: either ipv4(1) or ipv6(2) at a transit or egress LSR.
294:
295: At an ingress LSR, mplsTeP2mpTunnelSubGroupOrigin should not
296: be used, and this object should return the value
297: unknown(0)."
298: ::= { mplsTeP2mpTunnelEntry 4 }
299:
300: mplsTeP2mpTunnelSubGroupOrigin OBJECT-TYPE
301: SYNTAX InetAddress (SIZE(0|4|16))
302: MAX-ACCESS read-only
303: STATUS current
304: DESCRIPTION
305: "The TE Router ID (reachable and stable IP address) of the
306: originator of the P2MP sub-group as received on a Path
307: message by a transit or egress LSR.
308:
309: This object is interpreted in the context of
310: mplsTeP2mpTunnelSubGroupOriginType.
311:
312: The value of the sub-group originator used on outgoing Path
313: messages is found in mplsTeP2mpTunnelDestSubGroupOrigin and
314: is copied from this object unless this LSR is responsible
315: for changing the sub-group ID.
316:
317: At an ingress LSR this object is not used because there is
318: no received Path message. mplsTeP2mpTunnelSubGroupOriginType
319: should return unknown(0), and this object should return a
320: zero-length string, or should be absent."
321: REFERENCE
322: "RFC 4875 - Extensions to Resource Reservation Protocol -
323: Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
324: Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
325: and S. Yasukawa, May 2007."
326: ::= { mplsTeP2mpTunnelEntry 5 }
327:
328: mplsTeP2mpTunnelSubGroupID OBJECT-TYPE
329: SYNTAX Unsigned32 (1..4294967295)
330: MAX-ACCESS read-only
331: STATUS current
332: DESCRIPTION
333: "The unique identifier assigned by the sub-group originator
334: for this sub-group of this P2MP tunnel as received on a Path
335: message by a transit or egress LSR.
336:
337: The value of the sub-group identifier used on outgoing Path
338: messages is found in mplsTeP2mpTunnelDestSubGroupID and is
339: copied from this object unless this LSR is responsible for
340: changing the sub-group ID.
341:
342: At an ingress LSR this object is not used because there is
343: no received Path message, and the object should be absent or
344: should return zero."
345: REFERENCE
346: "RFC 4875 - Extensions to Resource Reservation Protocol -
347: Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
348: Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
349: and S. Yasukawa, May 2007."
350: ::= { mplsTeP2mpTunnelEntry 6 }
351:
352: mplsTeP2mpTunnelRowStatus OBJECT-TYPE
353: SYNTAX RowStatus
354: MAX-ACCESS read-create
355: STATUS current
356: DESCRIPTION
357: "This variable is used to create, modify, and/or delete a row
358: in this table. When a row in this table is in active(1)
359: state, no objects in that row can be modified by the agent
360: except mplsTeP2mpTunnelRowStatus and
361: mplsTeP2mpTunnelStorageType.
362:
363: This object and mplsTunnelRowStatus in the corresponding
364: entry in mplsTunnelTable in MPLS-TE-STD-MIB should be
365: managed together. No objects in a row in this table can be
366: modified when the mplsTunnelRowStatus object in the
367: corresponding row in mplsTunnelTable has value active(1).
368:
369: Note that no admin or oper status objects are provided in
370: this table. The administrative and operational status of
371: P2MP tunnels is taken from the values of
372: mplsTunnelAdminStatus and mplsTunnelOperStatus in the
373: corresponding row mplsTunneltable."
374: REFERENCE
375: "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
376: Engineering (TE) Management Information Base (MIB),
377: Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
378: ::= { mplsTeP2mpTunnelEntry 7 }
379:
380: mplsTeP2mpTunnelStorageType OBJECT-TYPE
381: SYNTAX StorageType
382: MAX-ACCESS read-create
383: STATUS current
384: DESCRIPTION
385: "The storage type for this tunnel entry.
386: Conceptual rows having the value 'permanent' need not allow
387: write-access to any columnar objects in the row."
388: DEFVAL { volatile }
389: ::= { mplsTeP2mpTunnelEntry 8 }
390:
391: -- End of mplsTeP2mpTunnelTable
392:
393: -- MPLS P2MP tunnel destination table.
394:
395: mplsTeP2mpTunnelSubGroupIDNext OBJECT-TYPE
396: SYNTAX IndexIntegerNextFree
397: MAX-ACCESS read-only
398: STATUS current
399: DESCRIPTION
400: "This object contains an unused value for
401: mplsTeP2mpTunnelDestSubGroupID, or a zero to indicate that
402: none exists. Negative values are not allowed, as they do not
403: correspond to valid values of
404: mplsTeP2mpTunnelDestSubGroupID.
405:
406: Note that this object offers an unused value for an
407: mplsTeP2mpTunnelDestSubGroupID value at the local LSR when
408: it is a sub-group originator. In other cases, the value of
409: mplsTeP2mpTunnelDestSubGroupID SHOULD be taken from the
410: received value signaled by the signaling protocol and
411: corresponds to the value in mplsTeP2mpTunnelSubGroupID."
412: ::= { mplsTeP2mpObjects 2 }
413:
414: mplsTeP2mpTunnelDestTable OBJECT-TYPE
415: SYNTAX SEQUENCE OF MplsTeP2mpTunnelDestEntry
416: MAX-ACCESS not-accessible
417: STATUS current
418: DESCRIPTION
419: "The mplsTeP2mpTunnelDestTable allows new destinations of
420: P2MP MPLS tunnels to be added to and removed from P2MP
421: tunnels."
422: REFERENCE
423: "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
424: Engineering (TE) Management Information Base (MIB),
425: Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
426: ::= { mplsTeP2mpObjects 3 }
427:
428: mplsTeP2mpTunnelDestEntry OBJECT-TYPE
429: SYNTAX MplsTeP2mpTunnelDestEntry
430: MAX-ACCESS not-accessible
431: STATUS current
432: DESCRIPTION
433: "An entry in this table represents a destination of a P2MP
434: MPLS tunnel. An entry can be created by a network
435: administrator or by an SNMP agent as instructed by an MPLS
436: signaling protocol.
437:
438: Entries in this table share some index fields with the
439: mplsTeP2mpTunnelTable and the mplsTunnelTable in
440: MPLS-TE-STD-MIB. Entries in this table have no meaning
441: unless there is a corresponding entry in
442: mplsTeP2mpTunnelTable (which, itself, depends on a
443: corresponding entry in mplsTunnelTable).
444:
445: Note that the same destination may be present more than once
446: if it is in more than one sub-group as reflected by the
447: mplsTeP2mpTunnelDestSubGroupOriginType,
448: mplsTeP2mpTunnelDestSubGroupOrigin, and
449: mplsTeP2mpTunnelDestSubGroupID, index objects.
450:
451: Entries in this table may be created at any time. If created
452: before an entry in the mplsTeP2mpTunnelTable the entries
453: have no meaning, but may be kept ready for the creation of
454: the P2MP tunnel. If created after the entry in
455: mplsTeP2mpTunnelTable, entries in this table may reflect the
456: addition of destinations to active P2MP tunnels. For this
457: reason, entries in this table are equipped with row, admin,
458: and oper status objects. "
459: REFERENCE
460: "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
461: Engineering (TE) Management Information Base (MIB),
462: Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
463: INDEX { mplsTunnelIndex,
464: mplsTunnelInstance,
465: mplsTunnelIngressLSRId,
466: mplsTunnelEgressLSRId,
467: mplsTeP2mpTunnelDestSubGroupOriginType,
468: mplsTeP2mpTunnelDestSubGroupOrigin,
469: mplsTeP2mpTunnelDestSubGroupID,
470: mplsTeP2mpTunnelDestDestinationType,
471: mplsTeP2mpTunnelDestDestination
472: }
473: ::= { mplsTeP2mpTunnelDestTable 1 }
474:
475: MplsTeP2mpTunnelDestEntry ::= SEQUENCE {
476: mplsTeP2mpTunnelDestSubGroupOriginType InetAddressType,
477: mplsTeP2mpTunnelDestSubGroupOrigin InetAddress,
478: mplsTeP2mpTunnelDestSubGroupID IndexInteger,
479: mplsTeP2mpTunnelDestDestinationType InetAddressType,
480: mplsTeP2mpTunnelDestDestination InetAddress,
481: mplsTeP2mpTunnelDestBranchOutSegment MplsIndexType,
482: mplsTeP2mpTunnelDestHopTableIndex MplsPathIndexOrZero,
483: mplsTeP2mpTunnelDestPathInUse MplsPathIndexOrZero,
484: mplsTeP2mpTunnelDestCHopTableIndex MplsPathIndexOrZero,
485: mplsTeP2mpTunnelDestARHopTableIndex MplsPathIndexOrZero,
486: mplsTeP2mpTunnelDestTotalUpTime TimeTicks,
487: mplsTeP2mpTunnelDestInstanceUpTime TimeTicks,
488: mplsTeP2mpTunnelDestPathChanges Counter32,
489: mplsTeP2mpTunnelDestLastPathChange TimeTicks,
490: mplsTeP2mpTunnelDestCreationTime TimeStamp,
491: mplsTeP2mpTunnelDestStateTransitions Counter32,
492: mplsTeP2mpTunnelDestDiscontinuityTime TimeStamp,
493: mplsTeP2mpTunnelDestAdminStatus INTEGER,
494: mplsTeP2mpTunnelDestOperStatus INTEGER,
495: mplsTeP2mpTunnelDestRowStatus RowStatus,
496: mplsTeP2mpTunnelDestStorageType StorageType
497: }
498:
499: mplsTeP2mpTunnelDestSubGroupOriginType OBJECT-TYPE
500: SYNTAX InetAddressType
501: MAX-ACCESS not-accessible
502: STATUS current
503: DESCRIPTION
504: "This object identifies the type of address carried in
505: mplsTeP2mpTunnelDestSubGroupOrigin.
506:
507: This object forms part of the index of this table and can,
508: therefore, not return the value unknown(0). Similarly, since
509: the object mplsTeP2mpTunnelDestSubGroupOrigin must conform
510: to the protocol specification, this object must return
511: either ipv4(1) or ipv6(2)."
512: ::= { mplsTeP2mpTunnelDestEntry 1 }
513:
514: mplsTeP2mpTunnelDestSubGroupOrigin OBJECT-TYPE
515: SYNTAX InetAddress (SIZE(4|16))
516: MAX-ACCESS not-accessible
517: STATUS current
518: DESCRIPTION
519: "The TE Router ID (reachable and stable IP address) of the
520: originator of the P2MP sub-group. In many cases, this will
521: be the ingress LSR of the P2MP tunnel and will be the
522: received signaled value as available in
523: mplsTeP2mpTunnelSubGroupOrigin.
524: When a signaling protocol is used, this object corresponds
525: to the Sub-Group Originator field in the SENDER_TEMPLATE
526: object.
527:
528: This object is interpreted in the context of
529: mplsTeP2mpTunnelDestSubGroupOriginType."
530: REFERENCE
531: "RFC 4875 - Extensions to Resource Reservation Protocol -
532: Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
533: Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
534: and S. Yasukawa, May 2007."
535: ::= { mplsTeP2mpTunnelDestEntry 2 }
536:
537: mplsTeP2mpTunnelDestSubGroupID OBJECT-TYPE
538: SYNTAX IndexInteger
539: MAX-ACCESS not-accessible
540: STATUS current
541: DESCRIPTION
542: "The unique identifier assigned by the sub-group originator
543: for this sub-group of this P2MP tunnel.
544:
545: An appropriate value for this object during row creation
546: when the sub-group origin in
547: mplsTeP2mpTunnelDestSubGroupOrigin is the local LSR can
548: be obtained by reading mplsTeP2mpTunnelSubGroupIDNext."
549: REFERENCE
550: "RFC 4875 - Extensions to Resource Reservation Protocol -
551: Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
552: Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
553: and S. Yasukawa, May 2007."
554: ::= { mplsTeP2mpTunnelDestEntry 3 }
555:
556: mplsTeP2mpTunnelDestDestinationType OBJECT-TYPE
557: SYNTAX InetAddressType
558: MAX-ACCESS not-accessible
559: STATUS current
560: DESCRIPTION
561: "This object identifies the type of address carried in
562: mplsTeP2mpTunnelDestDestination.
563:
564: This object forms part of the index of this table and can,
565: therefore, not return the value unknown(0). Similarly, since
566: the object mplsTeP2mpTunnelDestDestination must conform to
567: the protocol specification, this object must return either
568: ipv4(1) or ipv6(2)."
569: ::= { mplsTeP2mpTunnelDestEntry 4 }
570:
571: mplsTeP2mpTunnelDestDestination OBJECT-TYPE
572: SYNTAX InetAddress (SIZE(4|16))
573: MAX-ACCESS not-accessible
574: STATUS current
575: DESCRIPTION
576: "A single destination of this P2MP tunnel. That is, a
577: routable TE address of a leaf. This will often be the TE
578: Router ID of the leaf, but can be any interface address.
579:
580: When a signaling protocol is used, this object corresponds
581: to the S2L Sub-LSP destination address field in the
582: S2L_SUB_LSP object.
583:
584: This object is interpreted in the context of
585: mplsTeP2mpTunnelDestDestinationType."
586: REFERENCE
587: "RFC 4875 - Extensions to Resource Reservation Protocol -
588: Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
589: Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
590: and S. Yasukawa, May 2007."
591: ::= { mplsTeP2mpTunnelDestEntry 5 }
592:
593: mplsTeP2mpTunnelDestBranchOutSegment OBJECT-TYPE
594: SYNTAX MplsIndexType
595: MAX-ACCESS read-only
596: STATUS current
597: DESCRIPTION
598: "This object identifies the outgoing branch from this LSR
599: towards the destination represented by this table entry. It
600: must be a unique identifier within the scope of this tunnel.
601:
602: If MPLS-LSR-STD-MIB is implemented, this object should
603: contain an index into mplsOutSegmentTable.
604:
605: If MPLS-LSR-STD-MIB is not implemented, the LSR should
606: assign a unique value to each branch of the tunnel.
607:
608: The value of this object is also used as an index into
609: mplsTeP2mpTunnelBranchPerfTable."
610: ::= { mplsTeP2mpTunnelDestEntry 6 }
611:
612: mplsTeP2mpTunnelDestHopTableIndex OBJECT-TYPE
613: SYNTAX MplsPathIndexOrZero
614: MAX-ACCESS read-create
615: STATUS current
616: DESCRIPTION
617: "Index into the mplsTunnelHopTable entry that specifies the
618: explicit route hops for this destination of the P2MP tunnel.
619:
620: This object represents the configured route for the branch
621: of the P2MP tree to this destination and is meaningful only
622: at the head-end (ingress or root) of the P2MP tunnel. Note
623: that many such paths may be configured within the
624: mplsTunnelHopTable for each destination, and that the object
625: mplsTeP2mpTunnelDestPathInUse identifies which path has been
626: selected for use."
627: DEFVAL { 0 }
628: ::= { mplsTeP2mpTunnelDestEntry 7 }
629:
630: mplsTeP2mpTunnelDestPathInUse OBJECT-TYPE
631: SYNTAX MplsPathIndexOrZero
632: MAX-ACCESS read-create
633: STATUS current
634: DESCRIPTION
635: "This value denotes the configured path that was chosen as
636: the explicit path to this destination of this P2MP tunnel.
637: This value reflects the secondary index into
638: mplsTunnelHopTable where the primary index comes from
639: mplsTeP2mpTunnelDestHopTableIndex.
640:
641: The path indicated by this object might not exactly match
642: the one signaled and recorded in mplsTunnelCHopTable as
643: specific details of the path might be computed locally.
644:
645: Similarly, the path might not match the actual path in use
646: as recorded in mplsTunnelARHopTable due to the fact that
647: some details of the path may have been resolved within the
648: network.
649:
650: A value of zero denotes that no path is currently in use or
651: available."
652: DEFVAL { 0 }
653: ::= { mplsTeP2mpTunnelDestEntry 8 }
654:
655: mplsTeP2mpTunnelDestCHopTableIndex OBJECT-TYPE
656: SYNTAX MplsPathIndexOrZero
657: MAX-ACCESS read-only
658: STATUS current
659: DESCRIPTION
660: "Index into the mplsTunnelCHopTable that identifies the
661: explicit path for this destination of the P2MP tunnel.
662:
663: This path is based on the chosen configured path identified
664: by mplsTeP2mpTunnelDestHopTableIndex and
665: mplsTeP2mpTunnelDestPathInUse, but may have been modified
666: and automatically updated by the agent when computed hops
667: become available or when computed hops get modified.
668:
669: If this destination is the destination of the 'first S2L
670: sub-LSP' then this path will be signaled in the Explicit
671: Route Object. If this destination is the destination of a
672: 'subsequent S2L sub-LSP' then this path will be signaled in
673: a Secondary Explicit Route Object."
674: REFERENCE
675: "RFC 4875 - Extensions to Resource Reservation Protocol -
676: Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
677: Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
678: and S. Yasukawa, May 2007."
679: ::= { mplsTeP2mpTunnelDestEntry 9 }
680:
681: mplsTeP2mpTunnelDestARHopTableIndex OBJECT-TYPE
682: SYNTAX MplsPathIndexOrZero
683: MAX-ACCESS read-only
684: STATUS current
685: DESCRIPTION
686: "Index into the mplsTunnelARHopTable that identifies the
687: actual hops traversed to this destination of the P2MP
688: tunnel. This is automatically updated by the agent when the
689: actual hops becomes available.
690:
691: If this destination is the destination of the 'first S2L
692: sub-LSP' then this path will be signaled in the Recorded
693: Route Object. If this destination is the destination of a
694: 'subsequent S2L sub-LSP' then this path will be signaled in
695: a Secondary Recorded Route Object."
696:
697: REFERENCE
698: "RFC 4875 - Extensions to Resource Reservation Protocol -
699: Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE
700: Label Switched Paths (LSPs), R. Aggarwal, D. Papadimitriou,
701: and S. Yasukawa, May 2007."
702: ::= { mplsTeP2mpTunnelDestEntry 10 }
703:
704: mplsTeP2mpTunnelDestTotalUpTime OBJECT-TYPE
705: SYNTAX TimeTicks
706: MAX-ACCESS read-only
707: STATUS current
708: DESCRIPTION
709: "This value represents the aggregate up time for all
710: instances of this tunnel to this destination, if this
711: information is available.
712:
713: If this information is not available, this object MUST
714: return a value of 0."
715: ::= { mplsTeP2mpTunnelDestEntry 11 }
716:
717: mplsTeP2mpTunnelDestInstanceUpTime OBJECT-TYPE
718: SYNTAX TimeTicks
719: MAX-ACCESS read-only
720: STATUS current
721: DESCRIPTION
722: "This value identifies the total time that the currently
723: active tunnel instance to this destination has had its
724: operational status (mplsTeP2mpTunnelDestOperStatus) set to
725: up(1) since it was last previously not up(1)."
726: ::= { mplsTeP2mpTunnelDestEntry 12 }
727:
728: mplsTeP2mpTunnelDestPathChanges OBJECT-TYPE
729: SYNTAX Counter32
730: MAX-ACCESS read-only
731: STATUS current
732: DESCRIPTION
733: "This object counts the number of times the actual path for
734: this destination of this P2MP tunnel instance has changed.
735: This object should be read in conjunction with
736: mplsTeP2mpTunnelDestDiscontinuityTime."
737: ::= { mplsTeP2mpTunnelDestEntry 13 }
738:
739: mplsTeP2mpTunnelDestLastPathChange OBJECT-TYPE
740: SYNTAX TimeTicks
741: MAX-ACCESS read-only
742: STATUS current
743: DESCRIPTION
744: "Specifies the time since the last change to the actual path
745: for this destination of this P2MP tunnel instance."
746: ::= { mplsTeP2mpTunnelDestEntry 14 }
747:
748: mplsTeP2mpTunnelDestCreationTime OBJECT-TYPE
749: SYNTAX TimeStamp
750: MAX-ACCESS read-only
751: STATUS current
752: DESCRIPTION
753: "Specifies the value of sysUpTime when the first instance of
754: this tunnel came into existence for this destination. That
755: is, when the value of mplsTeP2mpTunnelDestOperStatus was
756: first set to up(1)."
757: ::= { mplsTeP2mpTunnelDestEntry 15 }
758:
759: mplsTeP2mpTunnelDestStateTransitions OBJECT-TYPE
760: SYNTAX Counter32
761: MAX-ACCESS read-only
762: STATUS current
763: DESCRIPTION
764: "This object counts the number of times the status
765: (mplsTeP2mpTunnelDestOperStatus) of this tunnel instance to
766: this destination has changed.
767: This object should be read in conjunction with
768: mplsTeP2mpTunnelDestDiscontinuityTime."
769: ::= { mplsTeP2mpTunnelDestEntry 16 }
770:
771: mplsTeP2mpTunnelDestDiscontinuityTime OBJECT-TYPE
772: SYNTAX TimeStamp
773: MAX-ACCESS read-only
774: STATUS current
775: DESCRIPTION
776: "The value of sysUpTime on the most recent occasion at which
777: any one or more of this row's Counter32 objects experienced
778: a discontinuity. If no such discontinuity has occurred since
779: the last re-initialization of the local management
780: subsystem, then this object contains a zero value."
781: ::= { mplsTeP2mpTunnelDestEntry 17 }
782:
783: mplsTeP2mpTunnelDestAdminStatus OBJECT-TYPE
784: SYNTAX INTEGER {
785: up(1), -- ready to pass data
786: down(2), -- out of service
787: testing(3) -- in some test mode
788: }
789: MAX-ACCESS read-create
790: STATUS current
791: DESCRIPTION
792: "Indicates the desired operational status of this
793: destination of this P2MP tunnel."
794: DEFVAL { up }
795: ::= { mplsTeP2mpTunnelDestEntry 18 }
796:
797: mplsTeP2mpTunnelDestOperStatus OBJECT-TYPE
798: SYNTAX INTEGER {
799: up(1), -- ready to pass data
800: down(2), -- out of service
801: testing(3), -- in some test mode
802: unknown(4), -- status cannot be determined
803: lowerLayerDown(7) -- down due to the state of
804: -- lower layer interfaces
805: }
806: MAX-ACCESS read-only
807: STATUS current
808: DESCRIPTION
809: "Indicates the actual operational status of this destination
810: of this P2MP tunnel. This object may be compared to
811: mplsTunnelOperStatus that includes two other values:
812: dormant(5) -- some component is missing
813: notPresent(6) -- down due to the state of
814: -- lower layer interfaces.
815: These states do not aply to an individual destinaton of a
816: P2MP MPLS-TE LSP and so are not included in this object."
817:
818: REFERENCE
819: "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
820: Engineering (TE) Management Information Base (MIB),
821: Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
822: ::= { mplsTeP2mpTunnelDestEntry 19 }
823:
824: mplsTeP2mpTunnelDestRowStatus OBJECT-TYPE
825: SYNTAX RowStatus
826: MAX-ACCESS read-create
827: STATUS current
828: DESCRIPTION
829: "This object is used to create, modify, and/or delete a row
830: in this table. When a row in this table is in active(1)
831: state, no objects in that row can be modified by SET
832: operations except mplsTeP2mpTunnelDestAdminStatus and
833: mplsTeP2mpTunnelDestStorageType."
834: ::= { mplsTeP2mpTunnelDestEntry 20 }
835:
836: mplsTeP2mpTunnelDestStorageType OBJECT-TYPE
837: SYNTAX StorageType
838: MAX-ACCESS read-create
839: STATUS current
840: DESCRIPTION "The storage type for this table entry.
841:
842: Conceptual rows having the value 'permanent' need
843: not allow write-access to any columnar objects in
844: the row."
845: DEFVAL { volatile }
846: ::= { mplsTeP2mpTunnelDestEntry 21 }
847:
848: -- End of mplsTeP2mpTunnelDestTable
849:
850: -- MPLS Tunnel Branch Performance Table.
851:
852: mplsTeP2mpTunnelBranchPerfTable OBJECT-TYPE
853: SYNTAX SEQUENCE OF MplsTeP2mpTunnelBranchPerfEntry
854: MAX-ACCESS not-accessible
855: STATUS current
856: DESCRIPTION
857: "This table provides per-tunnel branch MPLS performance
858: information.
859:
860: This table is not valid for switching types other than
861: packet."
862: ::= { mplsTeP2mpObjects 4 }
863:
864: mplsTeP2mpTunnelBranchPerfEntry OBJECT-TYPE
865: SYNTAX MplsTeP2mpTunnelBranchPerfEntry
866: MAX-ACCESS not-accessible
867: STATUS current
868: DESCRIPTION
869: "An entry in this table is created by the LSR for each
870: downstream branch (out-segment) from this LSR for this P2MP
871: tunnel.
872:
873: More than one destination as represented by an entry in the
874: mplsTeP2mpTunnelDestTable may be reached through a single
875: out-segment. More than one out-segment may belong to a
876: single P2MP tunnel represented by an entry in
877: mplsTeP2mpTunnelTable.
878:
879: Each entry in the table is indexed by the four identifiers
880: of the P2MP tunnel, and the out-segment that identifies the
881: outgoing branch."
882: INDEX { mplsTunnelIndex,
883: mplsTunnelInstance,
884: mplsTunnelIngressLSRId,
885: mplsTunnelEgressLSRId,
886: mplsTeP2mpTunnelBranchPerfBranch
887: }
888: ::= { mplsTeP2mpTunnelBranchPerfTable 1 }
889:
890: MplsTeP2mpTunnelBranchPerfEntry ::= SEQUENCE {
891: mplsTeP2mpTunnelBranchPerfBranch MplsIndexType,
892: mplsTeP2mpTunnelBranchPerfPackets Counter32,
893: mplsTeP2mpTunnelBranchPerfHCPackets Counter64,
894: mplsTeP2mpTunnelBranchPerfErrors Counter32,
895: mplsTeP2mpTunnelBranchPerfBytes Counter32,
896: mplsTeP2mpTunnelBranchPerfHCBytes Counter64,
897: mplsTeP2mpTunnelBranchDiscontinuityTime TimeStamp
898: }
899:
900: mplsTeP2mpTunnelBranchPerfBranch OBJECT-TYPE
901: SYNTAX MplsIndexType
902: MAX-ACCESS not-accessible
903: STATUS current
904: DESCRIPTION
905: "This object identifies an outgoing branch from this LSR
906: for this tunnel. Its value is unique within the context of
907: the tunnel.
908:
909: If MPLS-LSR-STD-MIB is implemented, this object should
910: contain an index into mplsOutSegmentTable.
911:
912: Under all circumstances, this object should contain
913: the same value as mplsTeP2mpTunnelDestBranchOutSegment for
914: destinations reached on this branch."
915: ::= { mplsTeP2mpTunnelBranchPerfEntry 1 }
916:
917: mplsTeP2mpTunnelBranchPerfPackets OBJECT-TYPE
918: SYNTAX Counter32
919: MAX-ACCESS read-only
920: STATUS current
921: DESCRIPTION
922: "Number of packets forwarded by the tunnel onto this branch.
923: This object should represents the 32-bit value of the least
924: significant part of the 64-bit value if both
925: mplsTeP2mpTunnelBranchPerfHCPackets is returned.
926: This object should be read in conjunction with
927: mplsTeP2mpTunnelBranchDiscontinuityTime."
928: ::= { mplsTeP2mpTunnelBranchPerfEntry 2 }
929:
930: mplsTeP2mpTunnelBranchPerfHCPackets OBJECT-TYPE
931: SYNTAX Counter64
932: MAX-ACCESS read-only
933: STATUS current
934: DESCRIPTION
935: "High capacity counter for number of packets forwarded by the
936: tunnel onto this branch.
937: This object should be read in conjunction with
938: mplsTeP2mpTunnelBranchDiscontinuityTime."
939: ::= { mplsTeP2mpTunnelBranchPerfEntry 3 }
940:
941: mplsTeP2mpTunnelBranchPerfErrors OBJECT-TYPE
942: SYNTAX Counter32
943: MAX-ACCESS read-only
944: STATUS current
945: DESCRIPTION
946: "Number of packets dropped because of errors or for other
947: reasons, that were supposed to be forwarded onto this
948: branch for this tunnel. This object should be read in
949: conjunction with mplsTeP2mpTunnelBranchDiscontinuityTime."
950: ::= { mplsTeP2mpTunnelBranchPerfEntry 4 }
951:
952: mplsTeP2mpTunnelBranchPerfBytes OBJECT-TYPE
953: SYNTAX Counter32
954: MAX-ACCESS read-only
955: STATUS current
956: DESCRIPTION
957: "Number of bytes forwarded by the tunnel onto this branch.
958: This object should represents the 32-bit value of the least
959: significant part of the 64-bit value if both
960: mplsTeP2mpTunnelBranchPerfHCBytes is returned.
961: This object should be read in conjunction with
962: mplsTeP2mpTunnelBranchDiscontinuityTime."
963: ::= { mplsTeP2mpTunnelBranchPerfEntry 5 }
964:
965: mplsTeP2mpTunnelBranchPerfHCBytes OBJECT-TYPE
966: SYNTAX Counter64
967: MAX-ACCESS read-only
968: STATUS current
969: DESCRIPTION
970: "High capacity counter for number of bytes forwarded
971: by the tunnel onto this branch.
972: This object should be read in conjunction with
973: mplsTeP2mpTunnelBranchDiscontinuityTime."
974: ::= { mplsTeP2mpTunnelBranchPerfEntry 6 }
975:
976: mplsTeP2mpTunnelBranchDiscontinuityTime OBJECT-TYPE
977: SYNTAX TimeStamp
978: MAX-ACCESS read-only
979: STATUS current
980: DESCRIPTION
981: "The value of sysUpTime on the most recent occasion at which
982: any one or more of this row's Counter32 or Counter64 objects
983: experienced a discontinuity. If no such discontinuity has
984: occurred since the last re-initialization of the local
985: management subsystem, then this object contains a zero
986: value."
987: ::= { mplsTeP2mpTunnelBranchPerfEntry 7 }
988:
989: -- End of mplsTeP2mpTunnelBranchPerfTable
990:
991: -- Notifications.
992:
993: mplsTeP2mpTunnelNotificationEnable OBJECT-TYPE
994: SYNTAX TruthValue
995: MAX-ACCESS read-write
996: STATUS current
997: DESCRIPTION
998: "If this object is true(1), then it enables the generation of
999: mplsTeP2mpTunnelDestUp and mplsTeP2mpTunnelDestDown
1000: notifications. Otherwise these notifications are not
1001: emitted.
1002:
1003: Note that whn tunnels have large numbers of destinations,
1004: setting this object to true(1) may result in the generation
1005: of large numbers of notifications."
1006: DEFVAL { false }
1007: ::= { mplsTeP2mpObjects 5 }
1008:
1009: mplsTeP2mpTunnelDestUp NOTIFICATION-TYPE
1010: OBJECTS {
1011: mplsTeP2mpTunnelDestAdminStatus,
1012: mplsTeP2mpTunnelDestOperStatus
1013: }
1014: STATUS current
1015: DESCRIPTION
1016: "This notification is generated when a
1017: mplsTeP2mpTunnelDestOperStatus object for one of the
1018: destinations of one of the configured tunnels is about to
1019: leave the down(2) state and transition into some other
1020: state. This other state is indicated by the included value
1021: of mplsTeP2mpTunneldestOperStatus.
1022:
1023: This reporting of state transitions mirrors mplsTunnelUp."
1024: REFERENCE
1025: "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
1026: Engineering (TE) Management Information Base (MIB),
1027: Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
1028: ::= { mplsTeP2mpNotifications 1 }
1029:
1030: mplsTeP2mpTunnelDestDown NOTIFICATION-TYPE
1031: OBJECTS {
1032: mplsTeP2mpTunnelDestAdminStatus,
1033: mplsTeP2mpTunnelDestOperStatus
1034: }
1035: STATUS current
1036: DESCRIPTION
1037: "This notification is generated when a
1038: mplsTeP2mpTunnelDestOperStatus object for one of the
1039: destinations of one of the configured tunnels is about to
1040: enter the down(2) state from some other state. This other
1041: state is indicated by the included value of
1042: mplsTeP2mpTunnelDestOperStatus.
1043:
1044: This reporting of state transitions mirrors mplsTunnelDown."
1045: REFERENCE
1046: "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic
1047: Engineering (TE) Management Information Base (MIB),
1048: Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004."
1049: ::= { mplsTeP2mpNotifications 2 }
1050:
1051: -- End of notifications.
1052:
1053:
1054: --****************************************************************
1055: -- Module Conformance Statement
1056: --****************************************************************
1057:
1058: mplsTeP2mpGroups
1059: OBJECT IDENTIFIER ::= { mplsTeP2mpConformance 1 }
1060:
1061: mplsTeP2mpCompliances
1062: OBJECT IDENTIFIER ::= { mplsTeP2mpConformance 2 }
1063:
1064: --
1065: -- Full Compliance
1066: -- Compliance requirement for fully compliant implementations.
1067: -- Such implementations allow configuration of P2MP tunnels at
1068: -- head-end LSRs via SNMP, and monitoring of P2MP tunnels at all
1069: -- LSRs via SNMP.
1070: --
1071:
1072: mplsTeP2mpModuleFullCompliance MODULE-COMPLIANCE
1073: STATUS current
1074: DESCRIPTION
1075: "Compliance statement for agents that provide full support
1076: for MPLS-TE-P2MP-STD-MIB. Such devices can be monitored and
1077: also be configured using this MIB module.
1078: The Module is implemented with support for read-create and
1079: read-write. In other words, both monitoring and
1080: configuration are available when using this
1081: MODULE-COMPLIANCE."
1082:
1083: MODULE -- this module
1084:
1085: MANDATORY-GROUPS {
1086: mplsTeP2mpGeneralGroup,
1087: mplsTeP2mpNotifGroup
1088: }
1089:
1090: -- mplsTeP2mpTunnelTable
1091:
1092: OBJECT mplsTeP2mpTunnelSubGroupOriginType
1093: SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2)}
1094: DESCRIPTION
1095: "An implementation is only required to support
1096: unknown(0), IPv4(1) and IPv6(2) addresses."
1097:
1098: OBJECT mplsTeP2mpTunnelRowStatus
1099: SYNTAX RowStatus { active(1) }
1100: WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
1101: DESCRIPTION
1102: "Support for createAndWait and notInService is not
1103: required."
1104:
1105: ::= { mplsTeP2mpCompliances 1 }
1106: mplsTeP2mpModuleReadOnlyCompliance MODULE-COMPLIANCE
1107: STATUS current
1108: DESCRIPTION
1109: "Compliance statement for agents that provide read-only
1110: support for MPLS-TE-P2MP-STD-MIB. Such devices can only be
1111: monitored using this MIB module.
1112: The Module is implemented with support for read-only. In
1113: other words, only monitoring is available by implementing
1114: this MODULE-COMPLIANCE."
1115:
1116: MODULE -- this module
1117:
1118: MANDATORY-GROUPS {
1119: mplsTeP2mpGeneralGroup,
1120: mplsTeP2mpNotifGroup
1121: }
1122:
1123: -- mplsTeP2mpTunnelTable
1124:
1125: OBJECT mplsTeP2mpTunnelP2mpIntegrity
1126: MIN-ACCESS read-only
1127: DESCRIPTION "Write access is not required."
1128:
1129: OBJECT mplsTeP2mpTunnelBranchRole
1130: MIN-ACCESS read-only
1131: DESCRIPTION "Write access is not required."
1132:
1133: OBJECT mplsTeP2mpTunnelSubGroupOriginType
1134: SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2)}
1135: DESCRIPTION
1136: "An implementation is only required to support
1137: unknown(0), IPv4(1) and IPv6(2) addresses."
1138:
1139: OBJECT mplsTeP2mpTunnelRowStatus
1140: SYNTAX RowStatus { active(1) }
1141: MIN-ACCESS read-only
1142: DESCRIPTION
1143: "Write access is not required, and active(1) is the
1144: only status that needs to be supported."
1145:
1146: OBJECT mplsTeP2mpTunnelStorageType
1147: MIN-ACCESS read-only
1148: DESCRIPTION "Write access is not required."
1149:
1150: -- mplsTeP2mpTunnelDestTable
1151:
1152: OBJECT mplsTeP2mpTunnelDestHopTableIndex
1153: MIN-ACCESS read-only
1154: DESCRIPTION "Write access is not required."
1155: OBJECT mplsTeP2mpTunnelDestPathInUse
1156: MIN-ACCESS read-only
1157: DESCRIPTION "Write access is not required."
1158:
1159: OBJECT mplsTeP2mpTunnelDestAdminStatus
1160: MIN-ACCESS read-only
1161: DESCRIPTION "Write access is not required."
1162:
1163: OBJECT mplsTeP2mpTunnelDestRowStatus
1164: SYNTAX RowStatus { active(1) }
1165: MIN-ACCESS read-only
1166: DESCRIPTION
1167: "Write access is not required, and active(1) is the
1168: only status that needs to be supported."
1169:
1170: OBJECT mplsTeP2mpTunnelDestStorageType
1171: MIN-ACCESS read-only
1172: DESCRIPTION "Write access is not required."
1173:
1174: ::= { mplsTeP2mpCompliances 2 }
1175:
1176: -- Units of conformance.
1177:
1178: mplsTeP2mpGeneralGroup OBJECT-GROUP
1178: minor error -
node `mplsTeP2mpTunnelDestSubGroupOriginType' is an invalid member of group `mplsTeP2mpGeneralGroup'
1178: minor error -
node `mplsTeP2mpTunnelDestSubGroupOrigin' is an invalid member of group `mplsTeP2mpGeneralGroup'
1178: minor error -
node `mplsTeP2mpTunnelDestSubGroupID' is an invalid member of group `mplsTeP2mpGeneralGroup'
1178: minor error -
node `mplsTeP2mpTunnelDestDestinationType' is an invalid member of group `mplsTeP2mpGeneralGroup'
1178: minor error -
node `mplsTeP2mpTunnelDestDestination' is an invalid member of group `mplsTeP2mpGeneralGroup'
1179: OBJECTS {
1180: mplsTeP2mpTunnelConfigured,
1181: mplsTeP2mpTunnelActive,
1182: mplsTeP2mpTunnelTotalMaxHops,
1183: mplsTeP2mpTunnelP2mpIntegrity,
1184: mplsTeP2mpTunnelBranchRole,
1185: mplsTeP2mpTunnelSubGroupOriginType,
1186: mplsTeP2mpTunnelSubGroupOrigin,
1187: mplsTeP2mpTunnelSubGroupID,
1188: mplsTeP2mpTunnelRowStatus,
1189: mplsTeP2mpTunnelStorageType,
1190: mplsTeP2mpTunnelSubGroupIDNext,
1191: mplsTeP2mpTunnelDestSubGroupOriginType,
1192: mplsTeP2mpTunnelDestSubGroupOrigin,
1193: mplsTeP2mpTunnelDestSubGroupID,
1194: mplsTeP2mpTunnelDestDestinationType,
1195: mplsTeP2mpTunnelDestDestination,
1196: mplsTeP2mpTunnelDestBranchOutSegment,
1197: mplsTeP2mpTunnelDestHopTableIndex,
1198: mplsTeP2mpTunnelDestPathInUse,
1199: mplsTeP2mpTunnelDestCHopTableIndex,
1200: mplsTeP2mpTunnelDestARHopTableIndex,
1201: mplsTeP2mpTunnelDestTotalUpTime,
1202: mplsTeP2mpTunnelDestInstanceUpTime,
1203: mplsTeP2mpTunnelDestPathChanges,
1204: mplsTeP2mpTunnelDestLastPathChange,
1205: mplsTeP2mpTunnelDestCreationTime,
1206: mplsTeP2mpTunnelDestStateTransitions,
1207: mplsTeP2mpTunnelDestDiscontinuityTime,
1208: mplsTeP2mpTunnelDestAdminStatus,
1209: mplsTeP2mpTunnelDestOperStatus,
1210: mplsTeP2mpTunnelDestRowStatus,
1211: mplsTeP2mpTunnelDestStorageType,
1212: mplsTeP2mpTunnelBranchPerfPackets,
1213: mplsTeP2mpTunnelBranchPerfHCPackets,
1214: mplsTeP2mpTunnelBranchPerfErrors,
1215: mplsTeP2mpTunnelBranchPerfBytes,
1216: mplsTeP2mpTunnelBranchPerfHCBytes,
1217: mplsTeP2mpTunnelBranchDiscontinuityTime,
1218: mplsTeP2mpTunnelNotificationEnable
1219: }
1220: STATUS current
1221: DESCRIPTION
1222: "Collection of objects needed for MPLS P2MP."
1223: ::= { mplsTeP2mpGroups 1 }
1224:
1225: mplsTeP2mpNotifGroup NOTIFICATION-GROUP
1226: NOTIFICATIONS {
1227: mplsTeP2mpTunnelDestUp,
1228: mplsTeP2mpTunnelDestDown
1229: }
1230: STATUS current
1231: DESCRIPTION
1232: "Notifications implemented in this module."
1233: ::= { mplsTeP2mpGroups 2 }
1234:
1235: END
1236:
1237: --
1238: -- Copyright (C) The IETF Trust (2007).
1239: --
1240: -- This document is subject to the rights, licenses and restrictions
1241: -- contained in BCP 78, and except as set forth therein, the authors
1242: -- retain all their rights.
1243: --
1244: -- This document and the information contained herein are provided on an
1245: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1246: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
1247: -- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
1248: -- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
1249: -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1250: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1251: