GMPLS-TE-STD-MIB
Copyright (C) The IETF Trust (2007). This version of
this MIB module is part of RFC 4802; see the RFC itself for
full legal notices.
This MIB module contains managed object definitions
for GMPLS Traffic Engineering (TE) as defined in:
1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, Berger, L. (Editor),
RFC 3471, January 2003.
2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
L. (Editor), RFC 3473, January 2003.
- Source file
GMPLS-TE-STD-MIB- Last revised
- Identity
gmplsTeStdMIB- Base OID
1.3.6.1.2.1.10.166.13
Imported Objects
| IANA-GMPLS-TC-MIB | IANAGmplsAdminStatusInformationTC IANAGmplsGeneralizedPidTC IANAGmplsLSPEncodingTypeTC IANAGmplsSwitchingTypeTC |
| INET-ADDRESS-MIB | InetAddress InetAddressType |
| MPLS-TC-STD-MIB | mplsStdMIB |
| MPLS-TE-STD-MIB | mplsTunnelAdminStatus mplsTunnelARHopIndex mplsTunnelARHopListIndex mplsTunnelCHopIndex mplsTunnelCHopListIndex mplsTunnelEgressLSRId mplsTunnelEntry mplsTunnelGroup (no object page) mplsTunnelHopIndex mplsTunnelHopListIndex mplsTunnelHopPathOptionIndex mplsTunnelIndex mplsTunnelIngressLSRId mplsTunnelInstance mplsTunnelOperStatus mplsTunnelScalarGroup (no object page) |
| SNMP-FRAMEWORK-MIB | SnmpAdminString |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | Counter32 Counter64 Gauge32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32 zeroDotZero |
| SNMPv2-TC | RowPointer TimeStamp TruthValue |
Net-SNMP examples using the rfc MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'GMPLS-TE-STD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'GMPLS-TE-STD-MIB::gmplsTeStdMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'GMPLS-TE-STD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'GMPLS-TE-STD-MIB::gmplsTeStdMIB'
Objects (69)
Showing 69 of 69 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.2.1.10.166.13 |
||
.1.3.6.1.2.1.10.166.13.0 |
||
.1.3.6.1.2.1.10.166.13.1 |
||
.1.3.6.1.2.1.10.166.13.1.1 |
||
.1.3.6.1.2.1.10.166.13.1.2 |
||
.1.3.6.1.2.1.10.166.13.2 |
||
.1.3.6.1.2.1.10.166.13.2.1 |
||
.1.3.6.1.2.1.10.166.13.2.1.1 |
||
.1.3.6.1.2.1.10.166.13.2.1.1.1 |
||
.1.3.6.1.2.1.10.166.13.2.1.1.10 |
||
.1.3.6.1.2.1.10.166.13.2.1.1.11 |
||
.1.3.6.1.2.1.10.166.13.2.1.1.12 |
||
.1.3.6.1.2.1.10.166.13.2.1.1.13 |
||
.1.3.6.1.2.1.10.166.13.2.1.1.14 |
||
.1.3.6.1.2.1.10.166.13.2.1.1.15 |
||
.1.3.6.1.2.1.10.166.13.2.1.1.16 |
||
.1.3.6.1.2.1.10.166.13.2.1.1.17 |
||
.1.3.6.1.2.1.10.166.13.2.1.1.18 |
||
.1.3.6.1.2.1.10.166.13.2.1.1.19 |
||
|
Bits
|
.1.3.6.1.2.1.10.166.13.2.1.1.2 |
|
.1.3.6.1.2.1.10.166.13.2.1.1.3 |
||
.1.3.6.1.2.1.10.166.13.2.1.1.4 |
||
|
Bits
|
.1.3.6.1.2.1.10.166.13.2.1.1.5 |
|
|
|
.1.3.6.1.2.1.10.166.13.2.1.1.6 |
|
.1.3.6.1.2.1.10.166.13.2.1.1.7 |
||
|
Enumeration
|
.1.3.6.1.2.1.10.166.13.2.1.1.8 |
|
|
Enumeration
|
.1.3.6.1.2.1.10.166.13.2.1.1.9 |
|
.1.3.6.1.2.1.10.166.13.2.2 |
||
.1.3.6.1.2.1.10.166.13.2.2.1 |
||
|
Bits
|
.1.3.6.1.2.1.10.166.13.2.2.1.1 |
|
.1.3.6.1.2.1.10.166.13.2.2.1.2 |
||
.1.3.6.1.2.1.10.166.13.2.2.1.3 |
||
.1.3.6.1.2.1.10.166.13.2.2.1.4 |
||
.1.3.6.1.2.1.10.166.13.2.2.1.5 |
||
.1.3.6.1.2.1.10.166.13.2.3 |
||
.1.3.6.1.2.1.10.166.13.2.3.1 |
||
|
Bits
|
.1.3.6.1.2.1.10.166.13.2.3.1.1 |
|
.1.3.6.1.2.1.10.166.13.2.3.1.2 |
||
.1.3.6.1.2.1.10.166.13.2.3.1.3 |
||
.1.3.6.1.2.1.10.166.13.2.3.1.4 |
||
.1.3.6.1.2.1.10.166.13.2.3.1.5 |
||
|
Bits
|
.1.3.6.1.2.1.10.166.13.2.3.1.6 |
|
.1.3.6.1.2.1.10.166.13.2.4 |
||
.1.3.6.1.2.1.10.166.13.2.4.1 |
||
|
Bits
|
.1.3.6.1.2.1.10.166.13.2.4.1.1 |
|
.1.3.6.1.2.1.10.166.13.2.4.1.2 |
||
.1.3.6.1.2.1.10.166.13.2.4.1.3 |
||
.1.3.6.1.2.1.10.166.13.2.4.1.4 |
||
.1.3.6.1.2.1.10.166.13.2.4.1.5 |
||
.1.3.6.1.2.1.10.166.13.2.5 |
||
.1.3.6.1.2.1.10.166.13.2.5.1 |
||
.1.3.6.1.2.1.10.166.13.2.5.1.1 |
||
.1.3.6.1.2.1.10.166.13.2.5.1.2 |
||
.1.3.6.1.2.1.10.166.13.2.5.1.3 |
||
.1.3.6.1.2.1.10.166.13.2.5.1.4 |
||
.1.3.6.1.2.1.10.166.13.2.5.1.5 |
||
.1.3.6.1.2.1.10.166.13.2.6 |
||
.1.3.6.1.2.1.10.166.13.2.6.1 |
||
|
Enumeration
|
.1.3.6.1.2.1.10.166.13.2.6.1.1 |
|
.1.3.6.1.2.1.10.166.13.2.6.1.2 |
||
.1.3.6.1.2.1.10.166.13.2.6.1.3 |
||
.1.3.6.1.2.1.10.166.13.2.6.1.4 |
||
.1.3.6.1.2.1.10.166.13.2.6.1.5 |
||
.1.3.6.1.2.1.10.166.13.2.6.1.6 |
||
|
OctetString
|
.1.3.6.1.2.1.10.166.13.2.6.1.7 |
|
.1.3.6.1.2.1.10.166.13.2.6.1.8 |
||
.1.3.6.1.2.1.10.166.13.3 |
||
.1.3.6.1.2.1.10.166.13.3.1 |
||
.1.3.6.1.2.1.10.166.13.3.2 |
Dependencies (14) 8 direct · 6 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- SNMPv2-TCrfc
- IANA-GMPLS-TC-MIBrfc
- INET-ADDRESS-MIBrfc
- MPLS-TC-STD-MIBrfc
- DIFFSERV-DSCP-TCrfc
- IANAifType-MIBrfc
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- INTEGRATED-SERVICES-MIBrfc
- DIFFSERV-MIBrfc
- SNMP-FRAMEWORK-MIBrfc
- MPLS-TE-STD-MIBrfc
- GMPLS-TE-STD-MIBrfcselected
Conformance Groups (5)
Compliance Statements (2)
OID
.1.3.6.1.2.1.10.166.13.3.2.1Compliance statement for agents that provide full support for
GMPLS-TE-STD-MIB. Such devices can then be monitored and also
be configured using this MIB module.
The mandatory group has to be implemented by all LSRs that
originate, terminate, or act as transit for TE-LSPs/tunnels.
In addition, depending on the type of tunnels supported, other
groups become mandatory as explained below.
GMPLS-TE-STD-MIB. Such devices can then be monitored and also
be configured using this MIB module.
The mandatory group has to be implemented by all LSRs that
originate, terminate, or act as transit for TE-LSPs/tunnels.
In addition, depending on the type of tunnels supported, other
groups become mandatory as explained below.
Required groups
| mandatory | MPLS-TE-STD-MIB::mplsTunnelGroup | |
| mandatory | MPLS-TE-STD-MIB::mplsTunnelScalarGroup | |
| mandatory | gmplsTunnelGroup | |
| mandatory | gmplsTunnelScalarGroup | |
| optional | gmplsTunnelSignaledGroup |
This group is mandatory for devices that support signaled tunnel set up, in addition to gmplsTunnelGroup. The following constraints apply: mplsTunnelSignallingProto should be at least read-only returning a value of ldp(2) or rsvp(3). |
| optional | gmplsTunnelOptionalGroup | Objects in this group are optional. |
| optional | gmplsTeNotificationGroup |
This group is mandatory for those implementations that can implement the notifications contained in this group. |
OID
.1.3.6.1.2.1.10.166.13.3.2.2Compliance requirement for implementations that only provide
read-only support for GMPLS-TE-STD-MIB. Such devices can then be
monitored but cannot be configured using this MIB module.
read-only support for GMPLS-TE-STD-MIB. Such devices can then be
monitored but cannot be configured using this MIB module.
Required groups
| mandatory | gmplsTunnelGroup | |
| mandatory | gmplsTunnelScalarGroup | |
| optional | gmplsTunnelSignaledGroup |
This group is mandatory for devices that support signaled tunnel set up, in addition to gmplsTunnelGroup. The following constraints apply: mplsTunnelSignallingProto should be at least read-only returning a value of ldp(2) or rsvp(3). |
| optional | gmplsTunnelOptionalGroup | Objects in this group are optional. |
| optional | gmplsTeNotificationGroup |
This group is mandatory for those implementations that can implement the notifications contained in this group. |
Object refinements
| Object | Access | Syntax | Description |
|---|---|---|---|
| gmplsTunnelUnnumIf | readonly | Write access is not required. | |
| gmplsTunnelAttributes | readonly | Write access is not required. | |
| gmplsTunnelLSPEncoding | readonly | Write access is not required. | |
| gmplsTunnelSwitchingType | readonly | Write access is not required. | |
| gmplsTunnelLinkProtection | readonly | Write access is not required. | |
| gmplsTunnelGPid | readonly | Write access is not required. | |
| gmplsTunnelSecondary | readonly | Write access is not required. | |
| gmplsTunnelDirection | readonly | Only forward(0) is required. | |
| gmplsTunnelPathComp | readonly | Only explicit(2) is required. | |
| gmplsTunnelUpstreamNotifyRecipientType | readonly |
unknown(0), ipv4(1), ipv6(2)
|
Only unknown(0), ipv4(1), and ipv6(2) support is required. |
| gmplsTunnelUpstreamNotifyRecipient | readonly | An implementation is only required to support unknown(0), ipv4(1), and ipv6(2) sizes. |
|
| gmplsTunnelSendResvNotifyRecipientType | readonly |
unknown(0), ipv4(1), ipv6(2)
|
Only unknown(0), ipv4(1), and ipv6(2) support is required. |
| gmplsTunnelSendResvNotifyRecipient | readonly | An implementation is only required to support unknown(0), ipv4(1), and ipv6(2) sizes. |
|
| gmplsTunnelDownstreamNotifyRecipientType | readonly |
unknown(0), ipv4(1), ipv6(2)
|
Only unknown(0), ipv4(1), and ipv6(2) support is required. |
| gmplsTunnelDownstreamNotifyRecipient | readonly | An implementation is only required to support unknown(0), ipv4(1), and ipv6(2) sizes. |
|
| gmplsTunnelSendPathNotifyRecipientType | readonly |
unknown(0), ipv4(1), ipv6(2)
|
Only unknown(0), ipv4(1), and ipv6(2) support is required. |
| gmplsTunnelSendPathNotifyRecipient | readonly | An implementation is only required to support unknown(0), ipv4(1), and ipv6(2) sizes. |
|
| gmplsTunnelAdminStatusFlags | readonly | Write access is not required. | |
| gmplsTunnelExtraParamsPtr | readonly | Write access is not required. | |
| gmplsTunnelHopExplicitForwardLabel | readonly | Write access is not required. | |
| gmplsTunnelHopExplicitForwardLabelPtr | readonly | Write access is not required. | |
| gmplsTunnelHopExplicitReverseLabel | readonly | Write access is not required. | |
| gmplsTunnelHopExplicitReverseLabelPtr | readonly | Write access is not required. | |
| gmplsTunnelErrorReporterType |
unknown(0), ipv4(1), ipv6(2)
|
Only unknown(0), ipv4(1), and ipv6(2) support is required. |
|
| gmplsTunnelErrorReporter | An implementation is only required to support unknown(0), ipv4(1), and ipv6(2). |
Notifications / Traps (1)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.2.1.10.166.13.0.1 |
This notification is generated when an mplsTunnelOperStatus
object for a tunnel in the gmplsTunnelTable is about to enter the down state from some other state (but not from the notPresent state). This other state is indicated by the included value of mplsTunnelOperStatus. The objects in this notification provide additional error information that indicates the reason why the tunnel has transitioned to down(2). Note that an implementation MUST only issue one of mplsTunnelDown and gmplsTunnelDown for any single event on a single tunnel. If the tunnel has an entry in the gmplsTunnelTable, an implementation SHOULD use gmplsTunnelDown for all tunnel-down events and SHOULD NOT use mplsTunnelDown. This notification is subject to the control of mplsTunnelNotificationEnable. When that object is set to false(2), then the notification must not be issued. Further, this notification is also subject to mplsTunnelNotificationMaxRate. That object indicates the maximum number of notifications issued per second. If events occur more rapidly, the implementation may simply fail to emit some notifications during that period, or may queue them until an appropriate time. The notification rate applies to the sum of all notifications in the MPLS-TE-STD-MIB and GMPLS-TE-STD-MIB modules applied across the whole of the reporting device. mplsTunnelOperStatus, mplsTunnelAdminStatus, mplsTunnelDown, mplsTunnelNotificationEnable, and mplsTunnelNotificationMaxRate objects are found in MPLS-TE-STD-MIB. |