The following tables, groups, and variables are supported in this MIB:
|extremeMplsTunnelTable||mplsTunnelIndex||The mplsTunnelTable (see RFC3812) 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.|
|mplsTunnelInstance||Uniquely identifies a particular instance of a tunnel between a pair of ingress and egress LSRs. It is useful to identify multiple instances of tunnels for the purposes of backup and parallel tunnels.|
|mplsTunnelIngressLSRId||Identity of the ingress LSR associated with this tunnel instance.|
|mplsTunnelEgressLSRId||Identity of the egress LSR associated with this tunnel instance.|
|mplsTunnelRedundancyType||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.|
|mplsTunnelRedundancyStatus||Indicates the actual redundancy status of this tunnel. When the status is active, the tunnel is the preferred tunnel in the group.|
Indicates the type of traffic the tunnel group can be used for sending.
When the status is allowAllIp (0), IP traffic destined for all IPv4 routes is allowed over any tunnel in the group marked active.When the status is allowAssignedIpOnly (1), IP traffic destined only for IPv4 static routes that have been explicitly configured to use this tunnel group is allowed.When the status is allowAllLayer 2Vpn (2), Layer 2 VPN traffic for all Layer 2 VPNs is allowed over any tunnel in the group marked active.When the status is allowAssignedLayer 2VpnOnly (3), Layer 2 VPN traffic destined only for PWs that have been explicitly configured to use this tunnel group are allowed.