TE-MIB

        The Traffic Engineering MIB module.
        
Copyright (C) The Internet Society (2005).  This
version of this MIB module is part of RFC 3970;
see the RFC itself for full legal notices.
    
Source file
TE-MIB
Last revised
Identity
teMIB
Base OID
1.3.6.1.2.1.122
Imported Objects
MPLS-TC-STD-MIB MplsBitRate TeHopAddress TeHopAddressType
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 Integer32 mib-2 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) TimeTicks Unsigned32
SNMPv2-TC RowStatus StorageType 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 'TE-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TE-MIB::teMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'TE-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TE-MIB::teMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (75)
.1.3.6.1.2.1.122
.1.3.6.1.2.1.122.0
.1.3.6.1.2.1.122.1
.1.3.6.1.2.1.122.1.1
Bits
.1.3.6.1.2.1.122.1.1.1
Bits
.1.3.6.1.2.1.122.1.1.2
.1.3.6.1.2.1.122.1.1.3
.1.3.6.1.2.1.122.1.1.4
.1.3.6.1.2.1.122.1.1.5
.1.3.6.1.2.1.122.1.1.6
.1.3.6.1.2.1.122.1.1.7
.1.3.6.1.2.1.122.1.1.8
.1.3.6.1.2.1.122.1.1.9
.1.3.6.1.2.1.122.1.1.9.1
Integer32
.1.3.6.1.2.1.122.1.1.9.1.1
OctetString
.1.3.6.1.2.1.122.1.1.9.1.2
.1.3.6.1.2.1.122.1.1.9.1.3
.1.3.6.1.2.1.122.1.2
.1.3.6.1.2.1.122.1.2.1
Unsigned32
.1.3.6.1.2.1.122.1.2.1.1
Enumeration
.1.3.6.1.2.1.122.1.2.1.10
.1.3.6.1.2.1.122.1.2.1.11
.1.3.6.1.2.1.122.1.2.1.12
.1.3.6.1.2.1.122.1.2.1.13
.1.3.6.1.2.1.122.1.2.1.14
.1.3.6.1.2.1.122.1.2.1.15
.1.3.6.1.2.1.122.1.2.1.16
.1.3.6.1.2.1.122.1.2.1.17
.1.3.6.1.2.1.122.1.2.1.18
.1.3.6.1.2.1.122.1.2.1.19
OctetString
.1.3.6.1.2.1.122.1.2.1.2
.1.3.6.1.2.1.122.1.2.1.20
.1.3.6.1.2.1.122.1.2.1.21
.1.3.6.1.2.1.122.1.2.1.22
.1.3.6.1.2.1.122.1.2.1.23
.1.3.6.1.2.1.122.1.2.1.24
.1.3.6.1.2.1.122.1.2.1.25
.1.3.6.1.2.1.122.1.2.1.3
.1.3.6.1.2.1.122.1.2.1.4
.1.3.6.1.2.1.122.1.2.1.5
.1.3.6.1.2.1.122.1.2.1.6
.1.3.6.1.2.1.122.1.2.1.7
.1.3.6.1.2.1.122.1.2.1.8
.1.3.6.1.2.1.122.1.2.1.9
.1.3.6.1.2.1.122.1.3
.1.3.6.1.2.1.122.1.3.1
Unsigned32
.1.3.6.1.2.1.122.1.3.1.1
.1.3.6.1.2.1.122.1.3.1.10
Integer32
.1.3.6.1.2.1.122.1.3.1.11
Integer32
.1.3.6.1.2.1.122.1.3.1.12
Bits
.1.3.6.1.2.1.122.1.3.1.13
Enumeration
.1.3.6.1.2.1.122.1.3.1.14
Enumeration
.1.3.6.1.2.1.122.1.3.1.15
.1.3.6.1.2.1.122.1.3.1.16
.1.3.6.1.2.1.122.1.3.1.17
OctetString
.1.3.6.1.2.1.122.1.3.1.2
.1.3.6.1.2.1.122.1.3.1.3
.1.3.6.1.2.1.122.1.3.1.4
Enumeration
.1.3.6.1.2.1.122.1.3.1.5
.1.3.6.1.2.1.122.1.3.1.6
Kilobits per secondMPLS-TC-STD-MIBMplsBitRate
.1.3.6.1.2.1.122.1.3.1.7
.1.3.6.1.2.1.122.1.3.1.8
.1.3.6.1.2.1.122.1.3.1.9
.1.3.6.1.2.1.122.1.4
.1.3.6.1.2.1.122.1.4.1
Unsigned32
.1.3.6.1.2.1.122.1.4.1.1
Unsigned32
.1.3.6.1.2.1.122.1.4.1.2
.1.3.6.1.2.1.122.1.4.1.3
.1.3.6.1.2.1.122.1.4.1.4
.1.3.6.1.2.1.122.1.4.1.5
.1.3.6.1.2.1.122.1.4.1.6
Enumeration
.1.3.6.1.2.1.122.1.4.1.7
.1.3.6.1.2.1.122.2
.1.3.6.1.2.1.122.2.1
.1.3.6.1.2.1.122.2.2
Dependencies (5) 5 direct 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
  1. SNMPv2-SMIrfc
  2. SNMPv2-TCrfc
  3. MPLS-TC-STD-MIBrfc
  4. SNMPv2-CONFrfc
  5. SNMP-FRAMEWORK-MIBrfc
  6. TE-MIBrfcselected
Compliance Statements (4)

OID .1.3.6.1.2.1.122.2.2.1
When this MIB module is implemented without support
for read-create (i.e., in read-only mode), then such
an implementation can claim read-only compliance.
Such a device can be monitored but cannot be
configured with this MIB module.
Required groups
mandatory teTrafficEngineeringGroup
optional teNotificationGroup Implementation of this group is optional.
Object refinements
ObjectAccessSyntaxDescription
teNotificationEnable readonly
Write access is not required.
teAdminGroupName readonly
Write access is not required.
teAdminGroupRowStatus readonly
active(1)
Write access is not required.
teTunnelName readonly
Write access is not required.
teTunnelRowStatus readonly
active(1)
Write access is not required.
teTunnelStorageType readonly
Write access is not required.
teTunnelSourceAddressType readonly
ipv4(1), ipv6(2)
Write access is not required. An
implementation is only required to support
IPv4 and IPv6 host addresses.
teTunnelSourceAddress readonly
Write access is not required.
teTunnelDestinationAddressType readonly
Write access is not required.
teTunnelDestinationAddress readonly
Write access is not required.
tePathName readonly
Write access is not required.
tePathRowStatus readonly
active(1)
Write access is not required.
tePathStorageType readonly
Write access is not required.
tePathType readonly
Write access is not required.
tePathConfiguredRoute readonly
Write access is not required.
tePathBandwidth readonly
Write access is not required.
tePathIncludeAny readonly
Write access is not required.
tePathIncludeAll readonly
Write access is not required.
tePathExclude readonly
Write access is not required.
tePathSetupPriority readonly
Write access is not required.
tePathHoldPriority readonly
Write access is not required.
tePathProperties readonly
Write access is not required.
tePathAdminStatus readonly
Write access is not required.
tePathHopRowStatus readonly
active(1)
Write access is not required.
tePathHopStorageType readonly
Write access is not required.
tePathHopAddrType readonly
Write access is not required.
tePathHopAddress readonly
Write access is not required.

OID .1.3.6.1.2.1.122.2.2.2
When this MIB module is implemented with support for
read-create, then the implementation can claim
full compliance. Such devices can be both

monitored and configured with this MIB module.
Required groups
mandatory teTrafficEngineeringGroup
optional teNotificationGroup Implementation of this group is optional.
Object refinements
ObjectAccessSyntaxDescription
teAdminGroupRowStatus
active(1)
Support for notInService, createAndWait and
notReady is not required.
teTunnelRowStatus
active(1), notInService(2)
Support for createAndWait and notReady is not
required.
teTunnelSourceAddressType
ipv4(1), ipv6(2)
Write access is required. An implementation is
only required to support IPv4 and IPv6 host
addresses.
tePathRowStatus
active(1), notInService(2)
Support for createAndWait and notReady is not
required.
tePathHopRowStatus
active(1), notInService(2)
Support for createAndWait and notReady is not
required.

OID .1.3.6.1.2.1.122.2.2.3
When this MIB module is implemented by a path
computation server without support for read-create
(i.e., in read-only mode), then the implementation
can claim read-only compliance. Such
a device can be monitored but cannot be
configured with this MIB module.
Required groups
mandatory teTrafficEngineeringGroup
optional teNotificationGroup Implementation of this group is optional.
Object refinements
ObjectAccessSyntaxDescription
teNotificationEnable readonly
Write access is not required.
teAdminGroupName readonly
Write access is not required.
teAdminGroupRowStatus readonly
active(1)
Write access is not required.
teTunnelName readonly
Write access is not required.
teTunnelRowStatus readonly
active(1)
Write access is not required.
teTunnelStorageType readonly
Write access is not required.
teTunnelSourceAddressType readonly
Write access is not required. A path
computation server SHOULD implement all types
of tunnel source address types.
teTunnelSourceAddress readonly
Write access is not required.
teTunnelDestinationAddressType readonly
Write access is not required.
teTunnelDestinationAddress readonly
Write access is not required.
tePathName readonly
Write access is not required.
tePathRowStatus readonly
active(1)
Write access is not required.
tePathStorageType readonly
Write access is not required.
tePathType readonly
Write access is not required.
tePathConfiguredRoute readonly
Write access is not required.
tePathBandwidth readonly
Write access is not required.
tePathIncludeAny readonly
Write access is not required.
tePathIncludeAll readonly
Write access is not required.
tePathExclude readonly
Write access is not required.
tePathSetupPriority readonly
Write access is not required.
tePathHoldPriority readonly
Write access is not required.
tePathProperties readonly
Write access is not required.
tePathAdminStatus readonly
Write access is not required.
tePathHopRowStatus readonly
active(1)
Write access is not required.
tePathHopStorageType readonly
Write access is not required.
tePathHopAddrType readonly
Write access is not required.
tePathHopAddress readonly
Write access is not required.

OID .1.3.6.1.2.1.122.2.2.4
When this MIB module is implemented by a path
computation server with support for read-create,
then the implementation can claim full
compliance.
Required groups
mandatory teTrafficEngineeringGroup
optional teNotificationGroup Implementation of this group is optional.
Object refinements
ObjectAccessSyntaxDescription
teAdminGroupRowStatus
active(1)
Support for notInService, createAndWait, and
notReady is not required.
teTunnelRowStatus
active(1), notInService(2)
Support for createAndWait and notReady is not
required.
teTunnelSourceAddressType
Write access is required. An implementation
of a path computation server SHOULD support all
types of tunnel source address types.
tePathRowStatus
active(1), notInService(2)
Support for createAndWait and notReady is not
required.
tePathHopRowStatus
active(1), notInService(2)
Support for createAndWait and notReady is not
required.
Notifications / Traps (4)
NameOIDDescription
.1.3.6.1.2.1.122.0.1
A teTunnelUp notification is generated when the
Tunnel indexed by teTunnelName transitions to the
'up' state.

A tunnel is up when at least one of its paths is up.
The tePathName is the name of the path whose
transition to up made the tunnel go up.

This notification MUST be limited to at most one
every minute, in case the tunnel flaps up and down.
.1.3.6.1.2.1.122.0.2
A teTunnelDown notification is generated when the
Tunnel indexed by teTunnelName transitions to the
'down' state.

A tunnel is up when at least one of its paths is up.
The tePathName is the name of the path whose
transition to down made the tunnel go down.

This notification MUST be limited to at most one
every minute, in case the tunnel flaps up and down.
.1.3.6.1.2.1.122.0.3
A teTunnelChanged notification is generated when an
active path on the Tunnel indexed by teTunnelName
changes or a new path becomes active. The value
of tePathName is the new active path.

This notification MUST be limited to at most one
every minute, in case the tunnel changes quickly.
.1.3.6.1.2.1.122.0.4
A teTunnelRerouted notification is generated when
an active path for the Tunnel indexed by
teTunnelName stays the same, but its route changes.

This notification MUST be limited to at most one
every minute, in case the tunnel reroutes quickly.