EXTREME-MPLS-TE-MIB
File:
EXTREME-MPLS-TE-MIB.mib (5739 bytes)
Imported modules
Imported symbols
Defined Types
| ExtremeMplsTunnelEntry |
|
| SEQUENCE |
|
|
|
| |
mplsTunnelRedundancyType |
INTEGER |
|
| |
mplsTunnelRedundancyStatus |
INTEGER |
|
| |
mplsTunnelTransportStatus |
BITS |
|
Defined Values
| extremeMplsTeMIB |
1.3.6.1.4.1.1916.1.37.2 |
| Extreme extensions to mplsTeStdMIB |
| MODULE-IDENTITY |
|
|
|
| extremeMplsTunnelTable |
1.3.6.1.4.1.1916.1.37.2.2.1 |
| The mplsTunnelTable (see RFC 3812) allows new MPLS tunnels
to be created between an LSR and a remote endpoint, and
existing tunnels to be reconfigured or removed.
Note that only point-to-point tunnel segments are
supported, although multipoint-to-point and point-
to-multipoint connections are supported by an LSR
acting as a cross-connect. Each MPLS tunnel can
thus have one out-segment originating at this LSR
and/or one in-segment terminating at this LSR.
Extreme Networks MPLS implementation allows tunnel instances
with a common endpoint to be grouped at the ingress LSR to
provide redundancy. The role of each tunnel in the group must
be configured and is indicated by extremeMplsTunnelRedundancyType.
The failover to a redundant tunnel is implementation dependent. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
ExtremeMplsTunnelEntry |
|
| extremeMplsTunnelEntry |
1.3.6.1.4.1.1916.1.37.2.2.1.1 |
| An entry in this table represents an extension to an MPLS tunnel
reported in the mplsTunnelTable (see RFC 3812). An entry can be
created by a network administrator or by an SNMP agent as
instructed by an MPLS signalling protocol.
An entry in this table displays an ingress tunnel only since
the tunnel type is a configured value at the local node and
is not exchanged by the signalling protocol. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
ExtremeMplsTunnelEntry |
|
|
| mplsTunnelRedundancyType |
1.3.6.1.4.1.1916.1.37.2.2.1.1.1 |
| Identifies the tunnel redundancy type associated with this
tunnel instance. A value of primary(1) or secondary(2)
MAY be assigned by the network administrator or by an
SNMP manager at the time of setting up the tunnel. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
primary(1), secondary(2) |
|
| mplsTunnelRedundancyStatus |
1.3.6.1.4.1.1916.1.37.2.2.1.1.2 |
| Indicates the actual redundancy status of this tunnel. When
the status is active, the tunnel is the preferred tunnel
in the group. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
active(1), standby(2) |
|
| mplsTunnelTransportStatus |
1.3.6.1.4.1.1916.1.37.2.2.1.1.3 |
| Indicates the type of traffic the tunnel group can be used for
sending.
When the allowAllIp(0) bit is set, IP traffic destined for
all IPv4 routes will be allowed over any tunnel in the group
marked active.
When the allowAssignedIpOnly(1) bit is set, IP traffic
destined only for IPv4 static routes that have been explicitly
configured to use this tunnel group will be allowed.
When the allowAllLayer2Vpn(2) bit is set, layer 2 VPN traffic
for all layer 2 VPNs will be allowed over any tunnel in the
group marked active.
When the allowAssignedLayer2VpnOnly(3) bit is set, layer 2 VPN
traffic destined only for pseudo-wires that have been explicitly
configured to use this tunnel group will be allowed. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
BITS |
allowAllIp(0), allowAssignedIpOnly(1), allowAllLayer2Vpn(2), allowAsignedLayer2VpnOnly(3) |
|