1CISCO-IETF-MPLS-TE-EXT-STD-03-MIB DEFINITIONS ::= BEGIN
2
3IMPORTS
4    MODULE-IDENTITY,
5    OBJECT-TYPE,
6    Unsigned32,
7    Counter32,
8    Counter64,
9    Gauge32,
10    zeroDotZero,
11    NOTIFICATION-TYPE
12        FROM SNMPv2-SMI
13    MODULE-COMPLIANCE,
14    OBJECT-GROUP,
15    NOTIFICATION-GROUP
16        FROM SNMPv2-CONF
17    TruthValue,
18    RowStatus,
19    RowPointer,
20    StorageType
21        FROM SNMPv2-TC
22    mplsStdMIB,
23    MplsTunnelIndex,
24    MplsTunnelInstanceIndex
25        FROM MPLS-TC-STD-MIB
26    mplsTunnelIndex,
27    mplsTunnelInstance,
28    mplsTunnelIngressLSRId,
29    mplsTunnelEgressLSRId
30        FROM MPLS-TE-STD-MIB
31    CMplsLocalId,
32    CMplsGlobalId,
33    CMplsNodeId,
34    CMplsIccId
35        FROM CISCO-MPLS-TC-EXT-STD-MIB
36    ciscoExperiment
37        FROM CISCO-SMI;
38
39
40cmplsTeExtStdMIB MODULE-IDENTITY
41    LAST-UPDATED    "201206060000Z"
42    ORGANIZATION    "Multiprotocol Label Switching (MPLS) Working Group"
43    CONTACT-INFO
44            "Venkatesan Mahalingam
45            Dell Inc,
46            350 Holger way, San Jose, CA, USA
47            Email: venkat.mahalingams@gmail.com
48
49            Kannan KV Sampath
50            Aricent,
51            India
52            Email: Kannan.Sampath@aricent.com
53
54            Sam Aldrin
55            Huawei Technologies
56            2330 Central Express Way,
57            Santa Clara, CA 95051, USA
58            Email:  aldrin.ietf@gmail.com
59
60            Thomas D. Nadeau
61            Juniper Networks
62            10 Technology Park Drive, Westford, MA 01886
63            Email: tnadeau@juniper.net"
64    DESCRIPTION
65        "Copyright (c) 2012 IETF Trust and the persons identified
66        as the document authors.  All rights reserved.
67        This MIB module contains generic object definitions for
68        MPLS Traffic Engineering in transport networks.This module is a
69        cisco-ized version of the IETF draft:
70        draft-ietf-mpls-tp-te-mib-03"
71    REVISION        "201204080000Z"
72    DESCRIPTION
73        "MPLS TE mib objects extension"
74    ::= { ciscoExperiment 146 }
75
76
77-- Top level components of this MIB module.
78--
79-- traps
80
81cmplsTeExtNotifications  OBJECT IDENTIFIER
82    ::= { cmplsTeExtStdMIB 0 }
83
84-- tables, scalars
85
86cmplsTeExtObjects  OBJECT IDENTIFIER
87    ::= { cmplsTeExtStdMIB 1 }
88
89-- conformance
90
91cmplsTeExtConformance  OBJECT IDENTIFIER
92    ::= { cmplsTeExtStdMIB 2 }
93
94-- Start of MPLS Transport Profile Node configuration table
95
96cmplsNodeConfigTable OBJECT-TYPE
97    SYNTAX          SEQUENCE OF CmplsNodeConfigEntry
98    MAX-ACCESS      not-accessible
99    STATUS          current
100    DESCRIPTION
101        "This table allows the administrator to map a node or
102        LSR Identifier (IP compatible [Global_Node_ID] or ICC)
103        with a local identifier.
104
105
106        This table is created to reuse the existing
107        mplsTunnelTable for MPLS based transport network
108        tunnels also.
109        Since the MPLS tunnel's Ingress/Egress LSR identifiers'
110        size (Unsigned32) value is not compatible for
111        MPLS-TP tunnel i.e. Global_Node_Id of size 8 bytes and
112        ICC of size 6 bytes, there exists a need to map the
113        Global_Node_ID or ICC with the local identifier of size
114        4 bytes (Unsigned32) value in order
115        to index (Ingress/Egress LSR identifier)
116        the existing mplsTunnelTable."
117    ::= { cmplsTeExtObjects 1 }
118
119cmplsNodeConfigEntry OBJECT-TYPE
120    SYNTAX          CmplsNodeConfigEntry
121    MAX-ACCESS      not-accessible
122    STATUS          current
123    DESCRIPTION
124        "An entry in this table represents a mapping
125        identification for the operator or service provider
126        with node or LSR.
127
128        As per [RFC6370], this mapping is
129
130        represented as Global_Node_ID or ICC.
131
132        Note: Each entry in this table should have a unique
133        Global_ID and Node_ID combination."
134    INDEX           { cmplsNodeConfigLocalId }
135    ::= { cmplsNodeConfigTable 1 }
136
137CmplsNodeConfigEntry ::= SEQUENCE {
138        cmplsNodeConfigLocalId     CMplsLocalId,
139        cmplsNodeConfigGlobalId    CMplsGlobalId,
140        cmplsNodeConfigNodeId      CMplsNodeId,
141        cmplsNodeConfigIccId       CMplsIccId,
142        cmplsNodeConfigRowStatus   RowStatus,
143        cmplsNodeConfigStorageType StorageType
144}
145
146cmplsNodeConfigLocalId OBJECT-TYPE
147    SYNTAX          CMplsLocalId
148    MAX-ACCESS      not-accessible
149    STATUS          current
150    DESCRIPTION
151        "This object allows the administrator to assign a unique
152        local identifier to map Global_Node_ID or ICC."
153    ::= { cmplsNodeConfigEntry 1 }
154
155cmplsNodeConfigGlobalId OBJECT-TYPE
156    SYNTAX          CMplsGlobalId
157    MAX-ACCESS      read-write
158    STATUS          current
159    DESCRIPTION
160        "This object indicates the Global Operator Identifier.
161        This object value should be zero when
162        mplsNodeConfigIccId is configured with non-null value."
163    REFERENCE       "MPLS-TP Identifiers [RFC6370]."
164    ::= { cmplsNodeConfigEntry 2 }
165
166cmplsNodeConfigNodeId OBJECT-TYPE
167    SYNTAX          CMplsNodeId
168    MAX-ACCESS      read-write
169    STATUS          current
170    DESCRIPTION
171        "This object indicates the Node_ID within the operator.
172        This object value should be zero when mplsNodeConfigIccId
173        is configured with non-null value."
174    REFERENCE       "MPLS-TP Identifiers [RFC6370]."
175    ::= { cmplsNodeConfigEntry 3 }
176
177cmplsNodeConfigIccId OBJECT-TYPE
178    SYNTAX          CMplsIccId
179    MAX-ACCESS      read-write
180    STATUS          current
181    DESCRIPTION
182        "This object allows the operator or service provider to
183        configure a unique MPLS-TP ITU-T Carrier Code (ICC)
184        either for Ingress ID or Egress ID.
185
186        This object value should be zero when
187        mplsNodeConfigGlobalId and mplsNodeConfigNodeId are
188        assigned with non-zero value."
189    REFERENCE       "MPLS-TP Identifiers [RFC6370]."
190    ::= { cmplsNodeConfigEntry 4 }
191
192cmplsNodeConfigRowStatus OBJECT-TYPE
193    SYNTAX          RowStatus
194    MAX-ACCESS      read-write
195    STATUS          current
196    DESCRIPTION
197        "This object allows the administrator to create, modify,
198        and/or delete a row in this table."
199    ::= { cmplsNodeConfigEntry 5 }
200
201cmplsNodeConfigStorageType OBJECT-TYPE
202    SYNTAX          StorageType
203    MAX-ACCESS      read-write
204    STATUS          current
205    DESCRIPTION
206        "This variable indicates the storage type for this
207        object.
208        Conceptual rows having the value 'permanent'
209        need not allow write-access to any columnar
210        objects in the row."
211    DEFVAL          { volatile }
212    ::= { cmplsNodeConfigEntry 6 }
213
214
215-- End of MPLS Transport Profile Node configuration table
216--
217-- Start of MPLS Transport Profile Node IP compatible
218-- mapping table
219
220cmplsNodeIpMapTable OBJECT-TYPE
221    SYNTAX          SEQUENCE OF CmplsNodeIpMapEntry
222    MAX-ACCESS      not-accessible
223    STATUS          current
224    DESCRIPTION
225        "This read-only table allows the administrator to retrieve
226        the local identifier for a given Global_Node_ID in an IP
227        compatible operator environment.
228
229        This table MAY be used in on-demand and/or proactive
230        OAM operations to get the Ingress/Egress LSR identifier
231        (Local Identifier) from Src-Global_Node_ID
232        or Dst-Global_Node_ID and the Ingress and Egress LSR
233        identifiers are used to retrieve the tunnel entry.
234
235        This table returns nothing when the associated entry
236        is not defined in mplsNodeConfigTable."
237    ::= { cmplsTeExtObjects 2 }
238
239cmplsNodeIpMapEntry OBJECT-TYPE
240    SYNTAX          CmplsNodeIpMapEntry
241    MAX-ACCESS      not-accessible
242    STATUS          current
243    DESCRIPTION
244        "An entry in this table represents a mapping of
245        Global_Node_ID with the local identifier.
246
247        An entry in this table is created automatically when
248        the Local identifier is associated with Global_ID and
249        Node_Id in the mplsNodeConfigTable.
250        Note: Each entry in this table should have a unique
251        Global_ID and Node_ID combination."
252    INDEX           {
253                        cmplsNodeIpMapGlobalId,
254                        cmplsNodeIpMapNodeId
255                    }
256    ::= { cmplsNodeIpMapTable 1 }
257
258CmplsNodeIpMapEntry ::= SEQUENCE {
259        cmplsNodeIpMapGlobalId CMplsGlobalId,
260        cmplsNodeIpMapNodeId   CMplsNodeId,
261        cmplsNodeIpMapLocalId  CMplsLocalId
262}
263
264cmplsNodeIpMapGlobalId OBJECT-TYPE
265    SYNTAX          CMplsGlobalId
266    MAX-ACCESS      not-accessible
267    STATUS          current
268    DESCRIPTION
269        "This object indicates the Global_ID."
270    ::= { cmplsNodeIpMapEntry 1 }
271
272cmplsNodeIpMapNodeId OBJECT-TYPE
273    SYNTAX          CMplsNodeId
274    MAX-ACCESS      not-accessible
275    STATUS          current
276    DESCRIPTION
277        "This object indicates the Node_ID within the
278        operator."
279    ::= { cmplsNodeIpMapEntry 2 }
280
281cmplsNodeIpMapLocalId OBJECT-TYPE
282    SYNTAX          CMplsLocalId
283    MAX-ACCESS      read-only
284    STATUS          current
285    DESCRIPTION
286        "This object contains an IP compatible local identifier
287        which is defined in mplsNodeConfigTable."
288    ::= { cmplsNodeIpMapEntry 3 }
289
290
291-- End MPLS Transport Profile Node IP compatible table
292--
293-- Start of MPLS Transport Profile Node ICC based table
294
295cmplsNodeIccMapTable OBJECT-TYPE
296    SYNTAX          SEQUENCE OF CmplsNodeIccMapEntry
297    MAX-ACCESS      not-accessible
298    STATUS          current
299    DESCRIPTION
300        "This read-only table allows the administrator to retrieve
301        the local identifier for a given ICC operator in an ICC
302        operator environment.
303
304        This table MAY be used in on-demand and/or proactive
305        OAM operations to get the Ingress/Egress LSR
306        identifier (Local Identifier) from Src-ICC
307        or Dst-ICC and the Ingress and Egress LSR
308        identifiers are used to retrieve the tunnel entry.
309        This table returns nothing when the associated entry
310        is not defined in mplsNodeConfigTable."
311    ::= { cmplsTeExtObjects 3 }
312
313cmplsNodeIccMapEntry OBJECT-TYPE
314    SYNTAX          CmplsNodeIccMapEntry
315    MAX-ACCESS      not-accessible
316    STATUS          current
317    DESCRIPTION
318        "An entry in this table represents a mapping of ICC with
319        the local identifier.
320
321        An entry in this table is created automatically when
322        the Local identifier is associated with ICC in
323        the mplsNodeConfigTable."
324    INDEX           { cmplsNodeIccMapIccId }
325    ::= { cmplsNodeIccMapTable 1 }
326
327CmplsNodeIccMapEntry ::= SEQUENCE {
328        cmplsNodeIccMapIccId   CMplsIccId,
329        cmplsNodeIccMapLocalId CMplsLocalId
330}
331
332cmplsNodeIccMapIccId OBJECT-TYPE
333    SYNTAX          CMplsIccId
334    MAX-ACCESS      not-accessible
335    STATUS          current
336    DESCRIPTION
337        "This object allows the operator or service provider to
338        configure a unique MPLS-TP ITU-T Carrier Code (ICC)
339        either for Ingress or Egress LSR ID.
340
341        The ICC is a string of one to six characters, each
342        character being either alphabetic (i.e.  A-Z) or
343        numeric (i.e. 0-9) characters. Alphabetic characters
344        in the ICC should be represented with upper case
345        letters."
346    ::= { cmplsNodeIccMapEntry 1 }
347
348cmplsNodeIccMapLocalId OBJECT-TYPE
349    SYNTAX          CMplsLocalId
350    MAX-ACCESS      read-only
351    STATUS          current
352    DESCRIPTION
353        "This object contains an ICC based local identifier
354        which is defined in mplsNodeConfigTable."
355    ::= { cmplsNodeIccMapEntry 2 }
356
357
358-- End MPLS Transport Profile Node ICC based table
359--
360-- Start of MPLS Tunnel table extension
361
362cmplsTunnelExtTable OBJECT-TYPE
363    SYNTAX          SEQUENCE OF CmplsTunnelExtEntry
364    MAX-ACCESS      not-accessible
365    STATUS          current
366    DESCRIPTION
367        "This table represents MPLS-TP specific extensions to
368        mplsTunnelTable.
369
370        As per MPLS-TP Identifiers [RFC6370], LSP_ID for IP based
371        co-routed bidirectional tunnel,
372
373        A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID::
374        Node_ID::Tunnel_Num}::LSP_Num
375
376        LSP_ID for IP based associated bidirectional tunnel,
377        A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}::
378        Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}
379
380        mplsTunnelTable is reused for forming the LSP_ID
381        as follows,
382
383        Source Tunnel_Num is mapped with mplsTunnelIndex,
384        Source Node_ID is mapped with
385        mplsTunnelIngressLSRId, Destination Node_ID is
386        mapped with mplsTunnelEgressLSRId LSP_Num is mapped with
387        mplsTunnelInstance.
388
389        Source Global_Node_ID and/or ICC and Destination
390        Global_Node_ID and/or ICC are maintained in the
391        mplsNodeConfigTable and mplsNodeConfigLocalId is
392        used to create an entry in mplsTunnelTable."
393    REFERENCE       "MPLS-TP Identifiers [RFC6370]."
394    ::= { cmplsTeExtObjects 4 }
395
396cmplsTunnelExtEntry OBJECT-TYPE
397    SYNTAX          CmplsTunnelExtEntry
398    MAX-ACCESS      not-accessible
399    STATUS          current
400    DESCRIPTION
401        "An entry in this table represents MPLS-TP
402        specific additional tunnel configurations."
403    INDEX           {
404                        mplsTunnelIndex,
405                        mplsTunnelInstance,
406                        mplsTunnelIngressLSRId,
407                        mplsTunnelEgressLSRId
408                    }
409    ::= { cmplsTunnelExtTable 1 }
410
411CmplsTunnelExtEntry ::= SEQUENCE {
412        cmplsTunnelOppositeDirPtr         RowPointer,
413        cmplsTunnelExtOppositeDirTnlValid TruthValue,
414        cmplsTunnelExtDestTnlIndex        MplsTunnelIndex,
415        cmplsTunnelExtDestTnlLspIndex     MplsTunnelInstanceIndex,
416        cmplsTunnelExtDestTnlValid        TruthValue
417}
418
419cmplsTunnelOppositeDirPtr OBJECT-TYPE
420    SYNTAX          RowPointer
421    MAX-ACCESS      read-create
422    STATUS          current
423    DESCRIPTION
424        "This object is applicable only for the bidirectional
425        tunnel that has the forward and reverse LSPs in the
426        same tunnel or in the different tunnels.
427
428        This object holds the opposite direction tunnel entry
429        if the bidirectional tunnel is setup by configuring two
430        tunnel entries in mplsTunnelTable.
431
432        The value of zeroDotZero indicates single tunnel entry
433        is used for bidirectional tunnel setup."
434    DEFVAL          { zeroDotZero }
435    ::= { cmplsTunnelExtEntry 1 }
436
437cmplsTunnelExtOppositeDirTnlValid OBJECT-TYPE
438    SYNTAX          TruthValue
439    MAX-ACCESS      read-create
440    STATUS          current
441    DESCRIPTION
442        "Denotes whether or not this tunnel uses
443        mplsTunnelOppositeDirPtr for identifying the opposite
444        direction tunnel information. Note that if this variable
445        is set to true then the mplsTunnelOppositeDirPtr should
446        point to the first accessible row of the opposite
447        direction tunnel."
448    DEFVAL          { false }
449    ::= { cmplsTunnelExtEntry 2 }
450
451cmplsTunnelExtDestTnlIndex OBJECT-TYPE
452    SYNTAX          MplsTunnelIndex
453    MAX-ACCESS      read-create
454    STATUS          current
455    DESCRIPTION
456        "This object is applicable only for the bidirectional
457        tunnel that has the forward and reverse LSPs in the
458        same tunnel or in the different tunnels.
459
460        This object holds the same value as that of the
461        mplsTunnelIndex of mplsTunnelEntry if the forward and
462        reverse LSPs are in the same tunnel. Otherwise,
463        this object holds the value of the other direction
464        associated LSP's mplsTunnelIndex from a different
465        tunnel.
466
467        The values of this object and the
468        mplsTunnelExtDestTnlLspIndex object together can be used
469        to identify an opposite direction LSP i.e. if the
470        mplsTunnelIndex and mplsTunnelInstance hold the value
471        for forward LSP, this object and
472        mplsTunnelExtDestTnlLspIndex can be used to retrieve
473        the reverse direction LSP and vice versa.
474
475        This object and mplsTunnelExtDestTnlLspIndex values
476        provide the first two indices of tunnel entry and
477        the remaining indices can be derived as follows,
478        if both the forward and reverse LSPs are present in
479        the same tunnel, the opposite direction LSP's Ingress
480        and Egress Identifier will be same for both the LSPs,
481        else the Ingress and Egress Identifiers should be
482        swapped in order to index the other direction tunnel."
483    ::= { cmplsTunnelExtEntry 3 }
484
485cmplsTunnelExtDestTnlLspIndex OBJECT-TYPE
486    SYNTAX          MplsTunnelInstanceIndex
487    MAX-ACCESS      read-create
488    STATUS          current
489    DESCRIPTION
490        "This object is applicable only for the bidirectional
491        tunnel that has the forward and reverse LSPs in the
492        same tunnel or in the different tunnels.
493
494        This object should contain different value if both the
495        forward and reverse LSPs present in the same tunnel.
496
497        This object can contain same value or different values
498        if the forward and reverse LSPs present in the different
499        tunnels."
500    ::= { cmplsTunnelExtEntry 4 }
501
502cmplsTunnelExtDestTnlValid OBJECT-TYPE
503    SYNTAX          TruthValue
504    MAX-ACCESS      read-create
505    STATUS          current
506    DESCRIPTION
507        "Denotes whether or not this tunnel uses
508        mplsTunnelExtDestTnlIndex and
509        mplsTunnelExtDestTnlLspIndex for identifying
510        the opposite direction tunnel information. Note that if
511        this variable is set to true then the
512        mplsTunnelExtDestTnlIndex and
513        mplsTunnelExtDestTnlLspIndex objects should have
514        the valid opposite direction tunnel indices."
515    DEFVAL          { false }
516    ::= { cmplsTunnelExtEntry 5 }
517
518
519-- End of MPLS Tunnel table extension
520
521cmplsTunnelReversePerfTable OBJECT-TYPE
522    SYNTAX          SEQUENCE OF CmplsTunnelReversePerfEntry
523    MAX-ACCESS      not-accessible
524    STATUS          current
525    DESCRIPTION
526        "This table extends the mplsTunnelTable to provide
527        per-tunnel packet performance information for the reverse
528        direction of a bidirectional tunnel.  It can be seen as
529        supplementing the mplsTunnelPerfTable, which augments the
530        mplsTunnelTable.
531
532        For links that do not transport packets, these packet
533        counters cannot be maintained.  For such links, attempts
534        to read the objects in this table will return
535        noSuchInstance."
536    REFERENCE
537        "1. Multiprotocol Label Switching (MPLS) Traffic
538         Engineering (TE)Management Information Base (MIB),
539         RFC 3812."
540    ::= { cmplsTeExtObjects 5 }
541
542cmplsTunnelReversePerfEntry OBJECT-TYPE
543    SYNTAX          CmplsTunnelReversePerfEntry
544    MAX-ACCESS      not-accessible
545    STATUS          current
546    DESCRIPTION
547        "An entry in this table is created by the LSR for every
548        bidirectional MPLS tunnel where packets are visible to the
549        LSR."
550    INDEX           {
551                        mplsTunnelIndex,
552                        mplsTunnelInstance,
553                        mplsTunnelIngressLSRId,
554                        mplsTunnelEgressLSRId
555                    }
556    ::= { cmplsTunnelReversePerfTable 1 }
557
558CmplsTunnelReversePerfEntry ::= SEQUENCE {
559        cmplsTunnelReversePerfPackets   Counter32,
560        cmplsTunnelReversePerfHCPackets Counter64,
561        cmplsTunnelReversePerfErrors    Counter32,
562        cmplsTunnelReversePerfBytes     Counter32,
563        cmplsTunnelReversePerfHCBytes   Counter64
564}
565
566cmplsTunnelReversePerfPackets OBJECT-TYPE
567    SYNTAX          Counter32
568    MAX-ACCESS      read-only
569    STATUS          current
570    DESCRIPTION
571        "Number of packets forwarded on the tunnel in the reverse
572        direction if it is bidirectional.
573
574        This object represents the 32-bit value of the least
575        significant part of the 64-bit value if both
576        mplsTunnelReversePerfHCPackets and this object
577        are returned.
578
579        For links that do not transport packets, this packet
580        counter cannot be maintained.  For such links, this value
581        will return noSuchInstance."
582    ::= { cmplsTunnelReversePerfEntry 1 }
583
584cmplsTunnelReversePerfHCPackets OBJECT-TYPE
585    SYNTAX          Counter64
586    MAX-ACCESS      read-only
587    STATUS          current
588    DESCRIPTION
589        "High-capacity counter for number of packets forwarded on
590        the tunnel in the reverse direction if it is
591        bidirectional.
592
593        For links that do not transport packets, this packet
594        counter cannot be maintained.  For such links, this value
595        will return noSuchInstance."
596    ::= { cmplsTunnelReversePerfEntry 2 }
597
598cmplsTunnelReversePerfErrors OBJECT-TYPE
599    SYNTAX          Counter32
600    MAX-ACCESS      read-only
601    STATUS          current
602    DESCRIPTION
603        "Number of errored packets received on the tunnel in
604        the reverse direction if it is bidirectional.  For links
605        that do not transport packets, this packet counter cannot
606        be maintained.  For such links, this value will return
607        noSuchInstance."
608    ::= { cmplsTunnelReversePerfEntry 3 }
609
610cmplsTunnelReversePerfBytes OBJECT-TYPE
611    SYNTAX          Counter32
612    MAX-ACCESS      read-only
613    STATUS          current
614    DESCRIPTION
615        "Number of bytes forwarded on the tunnel in the reverse
616        direction if it is bidirectional.
617
618        This object represents the 32-bit value of the least
619        significant part of the 64-bit value if both
620        mplsTunnelReversePerfHCBytes and this object are returned.
621
622        For links that do not transport packets, this packet
623        counter cannot be maintained.  For such links, this value
624        will return noSuchInstance."
625    ::= { cmplsTunnelReversePerfEntry 4 }
626
627cmplsTunnelReversePerfHCBytes OBJECT-TYPE
628    SYNTAX          Counter64
629    MAX-ACCESS      read-only
630    STATUS          current
631    DESCRIPTION
632        "High-capacity counter for number of bytes forwarded on the
633        tunnel in the reverse direction if it is bidirectional.
634
635        For links that do not transport packets, this packet
636        counter cannot be maintained.  For such links, this value
637        will return noSuchInstance."
638    ::= { cmplsTunnelReversePerfEntry 5 }
639
640
641-- Notifications.
642-- Notifications objects need to be added here.
643-- End of notifications.
644--
645-- Module compliance.
646
647cmplsTeExtGroups  OBJECT IDENTIFIER
648    ::= { cmplsTeExtConformance 1 }
649
650cmplsTeExtCompliances  OBJECT IDENTIFIER
651    ::= { cmplsTeExtConformance 2 }
652
653
654-- Compliance requirement for fully compliant implementations.
655
656cmplsTeExtModuleFullCompliance MODULE-COMPLIANCE
657    STATUS          current
658    DESCRIPTION
659        "Compliance statement for agents that provide full
660        support the MPLS-TE-EXT-STD-MIB module."
661    MODULE          -- this module
662    MANDATORY-GROUPS { cmplsTunnelExtGroup }
663
664    GROUP           cmplsTunnelExtIpOperatorGroup
665    DESCRIPTION
666        "This group is mandatory for devices which support
667        configuration of IP based identifier tunnels."
668
669    GROUP           cmplsTunnelExtIccOperatorGroup
670    DESCRIPTION
671        "This group is mandatory for devices which support
672        configuration of ICC based tunnels."
673    ::= { cmplsTeExtCompliances 1 }
674
675-- Compliance requirement for read-only implementations.
676
677cmplsTeExtModuleReadOnlyCompliance MODULE-COMPLIANCE
678    STATUS          current
679    DESCRIPTION
680        "Compliance statement for agents that provide full
681        support the MPLS-TE-EXT-STD-MIB module."
682    MODULE          -- this module
683    MANDATORY-GROUPS { cmplsTunnelExtGroup }
684
685    GROUP           cmplsTunnelExtIpOperatorGroup
686    DESCRIPTION
687        "This group is mandatory for devices which support
688        configuration of IP based identifier tunnels."
689
690    GROUP           cmplsTunnelExtIccOperatorGroup
691    DESCRIPTION
692        "This group is mandatory for devices which support
693        configuration of ICC based tunnels."
694    ::= { cmplsTeExtCompliances 2 }
695
696-- Units of conformance.
697
698cmplsTunnelExtGroup OBJECT-GROUP
699    OBJECTS         {
700                        cmplsTunnelOppositeDirPtr,
701                        cmplsTunnelExtOppositeDirTnlValid,
702                        cmplsTunnelExtDestTnlIndex,
703                        cmplsTunnelExtDestTnlLspIndex,
704                        cmplsTunnelExtDestTnlValid,
705                        cmplsTunnelReversePerfPackets,
706                        cmplsTunnelReversePerfHCPackets,
707                        cmplsTunnelReversePerfErrors,
708                        cmplsTunnelReversePerfBytes,
709                        cmplsTunnelReversePerfHCBytes
710                    }
711    STATUS          current
712    DESCRIPTION
713        "Necessary, but not sufficient, set of objects to
714        implement tunnels.  In addition, depending on the
715        operating environment, the following groups are
716        mandatory."
717    ::= { cmplsTeExtGroups 1 }
718
719cmplsTunnelExtIpOperatorGroup OBJECT-GROUP
720    OBJECTS         {
721                        cmplsNodeConfigGlobalId,
722                        cmplsNodeConfigNodeId,
723                        cmplsNodeConfigRowStatus,
724                        cmplsNodeConfigStorageType,
725                        cmplsNodeIpMapLocalId
726                    }
727    STATUS          current
728    DESCRIPTION
729        "Object(s) needed to implement IP compatible tunnels."
730    ::= { cmplsTeExtGroups 2 }
731
732cmplsTunnelExtIccOperatorGroup OBJECT-GROUP
733    OBJECTS         {
734                        cmplsNodeConfigIccId,
735                        cmplsNodeConfigRowStatus,
736                        cmplsNodeConfigStorageType,
737                        cmplsNodeIccMapLocalId
738                    }
739    STATUS          current
740    DESCRIPTION
741        "Object(s) needed to implement ICC based tunnels."
742    ::= { cmplsTeExtGroups 3 }
743
744END
745
746
747
748
749
750
751