All MIBs › RBN-MPLS-L3VPN-STD-EXT-MIB
Organization: RedBack Networks, Inc.
Last Updated: 2009-05-30
Category: MPLS and Traffic Engineering, Routing, Vendor: Ericsson
Description: Extends the IETF MPLS L3VPN standard MIB with Redback-specific VRF and PE router management objects.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is RBN-MPLS-L3VPN-STD-EXT-MIB?
RBN-MPLS-L3VPN-STD-EXT-MIB is a Redback Networks (RBN) vendor extension to the IETF standard MPLS Layer-3 VPN MIB (RFC 4382), adding Redback-specific objects for managing VRF route-target and PE (provider-edge) router configuration on Redback/Ericsson SmartEdge platforms. It exposes configuration data describing per-VRF route-target entries, including address family, route-target type, index, the route-target value itself, and a descriptive label, layered on top of the standard L3VPN VRF model. Its monitoring value is primarily configuration-state visibility rather than fault/performance counters: operators can audit rbnMplsL3VpnVrfRTTable to confirm VRFs have the correct import/export route-targets configured, catching VPN route-leaking or connectivity problems caused by mismatched or missing route-target entries. As its name and description state, it explicitly extends RFC 4382 (MPLS/BGP L3VPN MIB) and depends on that standard MIB (and the underlying MPLS/VRF MIBs) for the base VRF and VPN topology objects it augments. It is deployed on Redback SmartEdge/Ericsson router platforms acting as PE routers in service-provider MPLS L3VPN networks, where this RBN-MPLS-L3VPN-STD-EXT-MIB reference helps audit route-target configuration across VRFs.
IPNetwork Monitor allows you to monitor SNMP objects defined in RBN-MPLS-L3VPN-STD-EXT-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Redback SmartEdge / Ericsson MPLS provider-edge (PE) router
Monitoring Examples
An operator walks rbnMplsL3VpnVrfRTTable, keyed by rbnMplsL3VpnVrfRTAddrFamily and rbnMplsL3VpnVrfRTIndex, to read rbnMplsL3VpnVrfRTType and rbnMplsL3VpnVrfRT for each VRF, comparing the configured route-target values and their rbnMplsL3VpnVrfRTDescr labels against the intended VPN design. A route-target entry that is missing or set to an unexpected value would explain why a customer VPN site cannot reach other sites in the same VPN, pointing to a provisioning error on that PE router.
What Can Be Monitored
- VRF route-target entries
- route-target address family
- route-target type (import/export)
- VRF route-target description labels
Imported Objects
From IANA-ADDRESS-FAMILY-NUMBERS-MIB
| AddressFamilyNumbers |
From MPLS-L3VPN-STD-MIB
| MplsL3VpnRouteDistinguisher | |
| MplsL3VpnRtType | |
| mplsL3VpnVrfName | OBJECT-TYPE |
From RBN-SMI
| rbnMgmt | OBJECT-IDENTITY |
From SNMP-FRAMEWORK-MIB
| SnmpAdminString |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
OIDs
RFC description
Extension to the standard MPLS Layer 3 VPN MIB for Redback Networks (acquired by Ericsson) SmartEdge routers, providing vendor-specific L3VPN management objects.
Start monitoring Redback SmartEdge / Ericsson MPLS provider-edge (PE) router (VRF route-target configuration audit) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.