ROSNG-VPN-PRIVATE-MIB

All MIBs › ROSNG-VPN-PRIVATE-MIB

Organization: ZTE Corporation

Last Updated: 2005-04-12

Category: Routing

Description: Manages ZTE ROSNG router VPN instance configuration, route targets, and forwarding tables.

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 ROSNG-VPN-PRIVATE-MIB?

ROSNG-VPN-PRIVATE-MIB is a ZTE Corporation vendor-specific MIB (under the zte/zxr10/zxr10RosngMIB enterprise tree) for ZXR10 ROSNG routers that supplements the standard MPLS-L3VPN-STD-MIB with private, ZTE-specific VPN status and capacity objects. Its rosngmplsVpnPrivateTable is indexed by mplsL3VpnVrfName (imported from the standard MPLS L3VPN MIB) and reports rosngmplsVpnPrivateVpnType (an enumeration covering BGP/MPLS IP VPNs, BGP/LDP-based Layer 2 VPNs, VPLS, L2 circuits, optical VPNs, and ATM-over-MPLS), rosngmplsVpnPrivateVpnIdType, per-VPN connect status for Layer 2 and Layer 3 service (rosngmplsVpnPrivateL2VpnConnectStatus/L3VpnConnectStatus), a VPN age counter, and a VRF route-count warning threshold percentage. A separate zxr10MplsVpnGlobalVrfCapacity scalar reports the number of VRFs configured on the device. This is a status/capacity companion MIB rather than a full VPN configuration MIB, so it depends on the standard MPLS-L3VPN-STD-MIB for the base VRF model and is deployed on ZTE ZXR10 routers acting as PE routers in MPLS/BGP VPN networks; network engineers consult the ROSNG-VPN-PRIVATE-MIB MIB when diagnosing whether a VRF's Layer 2 or Layer 3 VPN connectivity has dropped to limbo state.

IPNetwork Monitor allows you to monitor SNMP objects defined in ROSNG-VPN-PRIVATE-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

ZTE ZXR10 ROSNG series routers

Monitoring Examples

An operator polls rosngmplsVpnPrivateL3VpnConnectStatus for a VRF's rosngmplsVpnPrivateTable entry, and a transition from active(1) to limbo(2) would indicate that Layer 3 VPN connectivity for that VRF has been lost on the ZXR10 PE router.

What Can Be Monitored

VPN type and VPN identifier type per VRF
Layer 2/Layer 3 VPN connect status
VPN age
VRF route-count warning threshold
global configured VRF capacity

Imported Objects

From MPLS-L3VPN-STD-MIB

mplsL3VpnVrfName

OBJECT-TYPE

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-IDENTITY
OBJECT-TYPE
TimeTicks
Unsigned32
enterprises

From SNMPv2-TC

DisplayString

OIDs

OID symbolic	OID numeric	Type	Access	Description
zte	1.3.6.1.4.1.3902			ZXROS SMI MIB
zxr10	1.3.6.1.4.1.3902.3
zxr10RosngMIB	1.3.6.1.4.1.3902.3.6000
rosngmplsVpnPrivateMIB	1.3.6.1.4.1.3902.3.6000.105			ZTE Corporation Enterprise Structure of Management Information
rosngmplsVpnPrivateObjects	1.3.6.1.4.1.3902.3.6000.105.1
rosngmplsVpnPrivateTable	1.3.6.1.4.1.3902.3.6000.105.1.1		not-accessible	This rosngmplsVpnPrivateTable is .
rosngmplsVpnPrivateEntry	1.3.6.1.4.1.3902.3.6000.105.1.1.1		not-accessible	Entry containing information about a particular VPN.
INT rosngmplsVpnPrivateVpnType	1.3.6.1.4.1.3902.3.6000.105.1.1.1.1	INTEGER	read-only	Type of the VPN. The following types have been defined: bgpIpVpn: RFC 2547 VPNs (see draft-ietf-ppvpn-rfc2547bis); bgpL2Vpn: BGP-based Layer 2 VPNs (see draft-kompella-ppvpn-l2vpn); bgpVpls: BGP-based VPLS (see draft-kompella-ppvnp-vpls); l2Circuit: LDP-based point-to-point Layer 2 circuits (see draft-martini-l2circuit-trans-mpls); ldpVpls: LDP-based VPLS (see draft-lasserre-vkompella-ppvpn-vpls); opticalVpn: BGP-based Optical (port based) VPNs (see draft-ouldbrahim-bgpgmpls-ovpn); vpOxc: Virtual Private Optical Cross-Connect (see draft-ouldbrahim-ppvpn-vpoxc); ccc: proprietary Layer 2 circuit; bgpAtmVpn: ATM over MPLS (draft to be published).
INT rosngmplsVpnPrivateVpnIdType	1.3.6.1.4.1.3902.3.6000.105.1.1.1.2	INTEGER	read-only	Type of the VPN Identifier. This includes Route Distinguishers, Route Targets, and VC IDs.
INT rosngmplsVpnPrivateL2VpnConnectStatus	1.3.6.1.4.1.3902.3.6000.105.1.1.1.3	INTEGER	read-only	The connect status of Layer 2 VPNs.
INT rosngmplsVpnPrivateL3VpnConnectStatus	1.3.6.1.4.1.3902.3.6000.105.1.1.1.4	INTEGER	read-only	The connect status of Layer 3 VPNs.
TIK rosngmplsVpnPrivateVpnAge	1.3.6.1.4.1.3902.3.6000.105.1.1.1.5	TimeTicks	read-only	The age (i.e., time from creation till now) of this VPN in hundredths of a second.
U32 rosngmplsVpnPrivateVrfConfRouteWarningPercent	1.3.6.1.4.1.3902.3.6000.105.1.1.1.6	Unsigned32	read-only	The threshol value (%) at which to give a warning.
zxr10MplsVpnGlobalPara	1.3.6.1.4.1.3902.3.6000.105.2
U32 zxr10MplsVpnGlobalVrfCapacity	1.3.6.1.4.1.3902.3.6000.105.2.1	Unsigned32	read-only	The number of VRFs that are configured in the global.

RFC description

Manages MPLS L3 VPN private configuration and VRF information on ZTE ZXROS routers.

Start monitoring ZTE ZXR10 ROSNG series routers (private VPN status/capacity companion to MPLS-L3VPN-STD-MIB) 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.

Download ROSNG-VPN-PRIVATE-MIB

What Is ROSNG-VPN-PRIVATE-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description