Traffic Engineering signaling protocols supported
by this device. More than one protocol may be
supported.
Parsed from file rfc3970-Traffic-Engineering-TE.mib.txt
Company: None
Module: TE-MIB
Table of Configured Traffic Tunnels.
Parsed from file TE-MIB.mib
Module: TE-MIB
Vendor: IETF RFCs
Module: TE-MIB (rfc3970-Traffic-Engineering-TE.mib)
Type: TABLE
Access: not-accessible
Syntax: SEQUENCE OF
Automatically extracted from www.mibdepot.com
teSignalingProto OBJECT-TYPE SYNTAX BITS { other(0), rsvpte(1), crldp(2), static(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "Traffic Engineering signaling protocols supported by this device. More than one protocol may be supported. " REFERENCE "For a description of RSVP-TE, see RFC 3209; for CR-LDP, see RFC 3212. " ::= { teInfo 2 }
teTunnelTable OBJECT-TYPE SYNTAX SEQUENCE OF TeTunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table of Configured Traffic Tunnels." ::= { teMIBObjects 2 }
Internet Assigned Numbers Authority
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.2.1.122.1.2.1 | teTunnelEntry | 25 | 25 | Entry containing information about a particular Traffic Tunnel. |
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.2.1.122.1.1 | teInfo, teDistProtocol | 9 | 21 | IGP used to distribute Traffic Engineering information and topology to each device for the purpose of automatic path computation.… |
1.3.6.1.2.1.122.1.3 | tePathTable, teAdminGroupTable, teNotificationEnable | 1 | 18 | tePathtable |
1.3.6.1.2.1.122.1.4 | tePathHopTable, teNextTunnelIndex, teConfiguredTunnels | 1 | 8 | Table of Tunnel Path Hops. |
1.3.6.1.2.1.122.1.5 | teActiveTunnels, teNextPathHopIndex | 0 | 0 | Number of active Tunnels. |
1.3.6.1.2.1.122.1.6 | tePrimaryTunnels | 0 | 0 | Number of active Tunnels running on their primary paths. |