MPLS-DSTE-MIB: View SNMP OID List / Download MIB

VENDOR: INTERNET-STANDARD


 Home MIB: MPLS-DSTE-MIB
Download as:   
SNMPv2-CONF, MPLS-TE-MIB, SNMPv2-SMI, MPLS-TC-MIB, MPLS-LSR-MIB, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 mplsDsTeMIB 1.3.6.1.2.1.10.9999.8
This MIB contains managed object definitions for Diff-Serv-aware MPLS Traffic Engineering as described in [DSTE-REQ][DSTE-PROTO].
     mplsDsTeObjects 1.3.6.1.2.1.10.9999.8.1
         mplsDsTeScalarObjects 1.3.6.1.2.1.10.9999.8.1.1
             mplsDsTeBwConstraintModel 1.3.6.1.2.1.10.9999.8.1.1.1
Bandwidth Constraint Model currently in use by this LSR. The bandwidth constraint model used by LSRs in a single DS-TE domain, must be same. As per the specification of the [DSTE-REQ] draft, the value of the bandwidth constraint model specified in this variable will determine the relationship between the Class-Types and Bandwidth Bandwidth Constraint (defined else where in this MIB). TBD: Latest [DSTE-REQ] allows the network operator to configure the BC Model on a per-link configuration. Will need to update the MIB to reflect this new requirement.
         mplsDsTeIfBCTable 1.3.6.1.2.1.10.9999.8.1.3
This table specifies bandwidth constraints associated with DS-TE enabled interfaces. This table AUGMENTS the mplsInterfaceConfTable [LSR-MIB].
             mplsDsTeIfBCEntry 1.3.6.1.2.1.10.9999.8.1.3.1
A row is created in this table automatically by an LSR for every interface capable of supporting MPLS DS-TE if this MIB is implemented. This relationship exists because each MPLS-enabled interface must participate in DS-TE. Therefore, this table AUGMENTS corresponding entries in the mplsInterfaceConfTable. Each entry in this table corresponds specified the bandwidth constraint associated with the corresponding MPLS interface, in Kbps. [However, if the mplsInterfaceConfTable has a conceptual row with index 0, all of the bandwidth constraints corresponding to that row will be no significance and will can not be modified] By default, all the bandwidth constraint other than BC0 is set to 0 Kbps. The BC0 by default is set to the maximum link bandwidth. Bandwidth constraints defined in this table are significant only if the corresponding Class-Type is defined in the mplsDsTeClassTable. Furthermore, the relationship of the Class-Types with the bandwidth constraints defined in this table is determined by the Bandwidth Constraint Model indicated in mplsDsTeBandwidthConstraintModel. For example, if the Russian Dolls Bandwidth Constraint Model [DSTE-RUSSIAN] is used then the LSR must ensure that BCi is configured smaller or equal to BCj, where i is greater than j, for all significant BCs. On the other hand Maximum Allocation Model [DSTE-MAM] does not have any such restrictions. MIB implementor need to refer to the document describing the BC Models for specific details. Bandwidth Constraints defined in this table are significant only if their corresponding CTs appear in the mplsDsTeClassTable.
                 mplsDsTeIfBC0MaxBw 1.3.6.1.2.1.10.9999.8.1.3.1.1
The maximum reservable bandwidth on this interface. As per the [DSTE-PROT0] draft, this also can be interpreted as the Bandwidth Constraint 0 (BC0). By default, the maximum reservable bandwidth associated with this interface can be initialized to the link bandwidth. Modification of this variable, should be reflected in mplsInterfaceTotalBandwidth defined in the [LSRMIB].
                 mplsDsTeIfBC1MaxBw 1.3.6.1.2.1.10.9999.8.1.3.1.2
The maximum reservable bandwidth for Bandwidth Constraint 1 (BC1) on this interface, in Kbps.
                 mplsDsTeIfBC2MaxBw 1.3.6.1.2.1.10.9999.8.1.3.1.3
The maximum reservable bandwidth for Bandwidth Constraint 2 (BC2) on this interface, in Kbps.
                 mplsDsTeIfBC3MaxBw 1.3.6.1.2.1.10.9999.8.1.3.1.4
The maximum reservable bandwidth for Bandwidth Constraint 3 (BC3) on this interface, in Kbps.
                 mplsDsTeIfBC4MaxBw 1.3.6.1.2.1.10.9999.8.1.3.1.5
The maximum reservable bandwidth for Bandwidth Constraint 4 (BC4) on this interface, in Kbps.
                 mplsDsTeIfBC5MaxBw 1.3.6.1.2.1.10.9999.8.1.3.1.6
The maximum reservable bandwidth for Bandwidth Constraint 5 (BC5) on this interface, in Kbps.
                 mplsDsTeIfBC6MaxBw 1.3.6.1.2.1.10.9999.8.1.3.1.7
The maximum reservable bandwidth for Bandwidth Constraint 6 (BC6) on this interface, in Kbps.
                 mplsDsTeIfBC7MaxBw 1.3.6.1.2.1.10.9999.8.1.3.1.8
The maximum reservable bandwidth for Bandwidth Constraint 7 (BC7) on this interface, in Kbps.
         mplsDsTeIfLOMTable 1.3.6.1.2.1.10.9999.8.1.4
This table allows administrator to configure a local overbooking multiplier on a per link per class-type basis.
             mplsDsTeIfLOMEntry 1.3.6.1.2.1.10.9999.8.1.4.1
100 indicates overbooking in use. By default, all the overbooking multipliers defined in this table will be initialized to 100 (i.e. no overbooking).
                 mplsDsTeIfLOMCT0 1.3.6.1.2.1.10.9999.8.1.4.1.1
This value represents the bandwidth overbooking multiplier for the class-type 0, on the specified interface, in percentage.
                 mplsDsTeIfLOMCT1 1.3.6.1.2.1.10.9999.8.1.4.1.2
This value represents the bandwidth overbooking multiplier for the class-type 1, on the specified interface, in percentage.
                 mplsDsTeIfLOMCT2 1.3.6.1.2.1.10.9999.8.1.4.1.3
This value represents the bandwidth overbooking multiplier for the class-type 2, on the specified interface, in percentage.
                 mplsDsTeIfLOMCT3 1.3.6.1.2.1.10.9999.8.1.4.1.4
This value represents the bandwidth overbooking multiplier for the class-type 3, on the specified interface, in percentage.
                 mplsDsTeIfLOMCT4 1.3.6.1.2.1.10.9999.8.1.4.1.5
This value represents the bandwidth overbooking multiplier for the class-type 4, on the specified interface, in percentage.
                 mplsDsTeIfLOMCT5 1.3.6.1.2.1.10.9999.8.1.4.1.6
This value represents the bandwidth overbooking multiplier for the class-type 5, on the specified interface, in percentage.
                 mplsDsTeIfLOMCT6 1.3.6.1.2.1.10.9999.8.1.4.1.7
This value represents the bandwidth overbooking multiplier for the class-type 6, on the specified interface, in percentage.
                 mplsDsTeIfLOMCT7 1.3.6.1.2.1.10.9999.8.1.4.1.8
This value represents the bandwidth overbooking multiplier for the class-type 7, on the specified interface, in percentage.
         mplsDsTeClassTable 1.3.6.1.2.1.10.9999.8.1.5
pair.
             mplsDsTeClassEntry 1.3.6.1.2.1.10.9999.8.1.5.1
pair. An administrator must defined the TE-Class he wants to support in the domain by creating appropriate entries in this table. All the LSRs in the domain, must have the same set of entries. Besides defining the TE-Classes, the entries in this table also indicate the active Class-Types within the LSR and the connection priorities it can support. More specifically:- The LSR is considered to support a particular Class-Type only if it appears in the definition of the 8 possible TE-Classes. A (setup/holding) priority associated with a LSP, on a LSR is consider to be valid only if it appears as a pair with the class-type of the connection. An empty mplsDsTeClassTable effectively disables DSTE and TE on the LSR and no (DSTE/TE) LSPs can be established on the LSR. There are no other restrictions on how any of the 8 Class-Types can be paired up with any of the 8 preemption priorities to form a TE- class[DSTE-PROTO].
                 mplsDsTeClassIndex 1.3.6.1.2.1.10.9999.8.1.5.1.1
This value represents the index of the TE-Class being configured on the LSR.
                 mplsDsTeClassType 1.3.6.1.2.1.10.9999.8.1.5.1.2
This value represents a Class-Type supported on the LSR.
                 mplsDsTeClassPriority 1.3.6.1.2.1.10.9999.8.1.5.1.3
This value represents the preemption priority (setup or holding) supported for a particular class-type, on the LSR.
                 mplsDsTeClassDescription 1.3.6.1.2.1.10.9999.8.1.5.1.4
Textual description of the TE-Class defined by this row.
                 mplsDsTeClassRowStatus 1.3.6.1.2.1.10.9999.8.1.5.1.5
The row status for a row in this table.
                 mplsDsTeClassStorageType 1.3.6.1.2.1.10.9999.8.1.5.1.6
The storage type for this entry.
         mplsDsTeIfUnresBwTable 1.3.6.1.2.1.10.9999.8.1.6
This table presents the unreserved bandwidth available on each interface for each TE-Class.
             mplsDsTeIfUnresBwEntry 1.3.6.1.2.1.10.9999.8.1.6.1
A row is created in this table automatically by an LSR for every interface capable of supporting MPLS and is enable to do so, since it AUGMENTs the mplsInterfaceConfTable. Each entry in this table presents the unreserved / available bandwidth for different TE-Classes on this interface. [However, if the mplsInterfaceConfTable has a conceptual row with index 0, all of the LOMs corresponding to that row will be no significance and will can not be modified] When the TE-Class is not supported on the LSR, the corresponding unreserved bandwidth will be set to zero.
                 mplsDsTeIfUnresBwTEClass0 1.3.6.1.2.1.10.9999.8.1.6.1.1
This value represents the unreserved bandwidth for the TE-Class 0, on the specified interface.
                 mplsDsTeIfUnresBwTEClass1 1.3.6.1.2.1.10.9999.8.1.6.1.2
This value represents the unreserved bandwidth for the TE-Class 1, on the specified interface
                 mplsDsTeIfUnresBwTEClass2 1.3.6.1.2.1.10.9999.8.1.6.1.3
This value represents the unreserved bandwidth for the TE-Class 2, on the specified interface
                 mplsDsTeIfUnresBwTEClass3 1.3.6.1.2.1.10.9999.8.1.6.1.4
This value represents the unreserved bandwidth for the TE-Class 3, on the specified interface
                 mplsDsTeIfUnresBwTEClass4 1.3.6.1.2.1.10.9999.8.1.6.1.5
This value represents the unreserved bandwidth for the TE-Class 4, on the specified interface
                 mplsDsTeIfUnresBwTEClass5 1.3.6.1.2.1.10.9999.8.1.6.1.6
This value represents the unreserved bandwidth for the TE-Class 5, on the specified interface
                 mplsDsTeIfUnresBwTEClass6 1.3.6.1.2.1.10.9999.8.1.6.1.7
This value represents the unreserved bandwidth for the TE-Class 6, on the specified interface
                 mplsDsTeIfUnresBwTEClass7 1.3.6.1.2.1.10.9999.8.1.6.1.8
This value represents the unreserved bandwidth for the TE-Class 7, on the specified interface
         mplsDsTeTunTable 1.3.6.1.2.1.10.9999.8.1.7
This table indicates which DiffServ Class-Type the particular Traffic Engineering tunnels have been assigned to. This table extends the mplsTunnelTable from the MPLS-TE-MIB[TE-MIB], by augmenting it.
             mplsDsTeTunEntry 1.3.6.1.2.1.10.9999.8.1.7.1
An entry in this table is created by an LSR for every traffic engineering tunnel instance capable of supporting MPLS DiffServ-Aware Traffic Engineering.
                 mplsDsTeTunTunnelClassType 1.3.6.1.2.1.10.9999.8.1.7.1.5
This object indicates the DiffServ-Aware TE class to which this tunnel instance has been assigned. If the specified class-type does not appear in the mplsDsTeClassTable, the tunnel instance corresponding to this row will remain down. When user does not specify a specific class-type, a default value representing CT0 is assumed.
         mplsDsTeLspTable 1.3.6.1.2.1.10.9999.8.1.8
This table indicates which DiffServ-Aware TE class particular LSPs. This table AUGMENTS the mplsXCTable.
             mplsDsTeLspEntry 1.3.6.1.2.1.10.9999.8.1.8.1
An entry in this table is created by an LSR for every LSP capable of supporting MPLS DiffServ-Aware Traffic Engineering. Specifically, an entry in this table must correspond to an entry in the mplsXCTable from the MPLS-LSR-MIB [MPLS-LSR-MIB].
                 mplsDsTeLspClassType 1.3.6.1.2.1.10.9999.8.1.8.1.1
This object indicates the DiffServ-Aware TE class to which this LSP has been assigned.
     mplsDsTeNotifications 1.3.6.1.2.1.10.9999.8.2
     mplsDsTeConformance 1.3.6.1.2.1.10.9999.8.3
         mplsDsTeGroups 1.3.6.1.2.1.10.9999.8.3.1
             mplsDsTeScalarGroup 1.3.6.1.2.1.10.9999.8.3.1.1
Collection of scalar objects required for DS TE management.
             mplsDsTeIfBCGroup 1.3.6.1.2.1.10.9999.8.3.1.2
Collection of objects needed for managing the Bandwidth constraints on a per MPLS Interface basis.
             mplsDsTeIfLOMGroup 1.3.6.1.2.1.10.9999.8.3.1.3
Collection of objects needed for managing the Local Overbooking Multiplier on a per Class-Type per MPLS interface basis.
             mplsDsTeClassGroup 1.3.6.1.2.1.10.9999.8.3.1.4
Collection of objects needed for managing the TE-Class definitions within the DSTE LSR.
             mplsDsTeTunGroup 1.3.6.1.2.1.10.9999.8.3.1.5
Collection of objects needed for MPLS DS TE Tunnel management.
         mplsDsTeCompliances 1.3.6.1.2.1.10.9999.8.3.2
             mplsDsTeModuleCompliance 1.3.6.1.2.1.10.9999.8.3.2.1
Compliance statement for agents that support MPLS Diff-Serv Aware Traffic Engineering.