CISCO-IETF-VPLS-BGP-EXT-MIB

All MIBs › CISCO-IETF-VPLS-BGP-EXT-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2008-10-24

Category: Cisco Devices, MPLS and Traffic Engineering, VPN and Security

Description: Extends the IETF VPLS BGP MIB for Virtual Private LAN Service BGP signaling management on Cisco devices.

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 CISCO-IETF-VPLS-BGP-EXT-MIB?

CISCO-IETF-VPLS-BGP-EXT-MIB is a Cisco extension of the IETF VPLS MIB for managing BGP-based Virtual Private LAN Service instances over an underlying pseudowire/MPLS network on Cisco provider-edge (PE) routers. It exposes configuration tables for VPLS instance route distinguishers and VE-ID range sizing (ciVplsBgpExtConfigTable), route-target import/export policy (civplsBgpExtRTTable), and virtual-edge (VE) identifiers (ciVplsBgpExtVETable), along with row-status and storage-type controls for provisioning. Its role is primarily configuration/software-state monitoring for the VPLS control plane - verifying that route distinguishers, route targets, and VE ranges are correctly provisioned and that BGP signaling for a VPLS instance is set up consistently across PE routers, rather than exposing physical hardware sensors. It explicitly extends the IETF VPLS MIB (RFC 4188-lineage) and depends on underlying BGP/MPLS/pseudowire MIBs for the transport layer. It is deployed by service providers running Cisco PE routers to deliver BGP auto-discovered/signaled VPLS Ethernet services to enterprise customers. Engineers can download the CISCO-IETF-VPLS-BGP-EXT-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-IETF-VPLS-BGP-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

Cisco provider-edge routers (e.g. ASR 9000, 7600 series) running BGP-signalled VPLS

Monitoring Examples

A provider engineer would check ciVplsBgpExtConfigTable's ciVplsBgpExtConfigRouteDistinguisher and ciVplsBgpExtConfigVERangeSize to confirm a VPLS instance's BGP identifiers are consistent across all participating PEs. civplsBgpExtRTTable (ciVplsBgpExtRTType/ciVplsBgpExtRT) is polled to verify the correct route-target import/export policy is attached, which if wrong would prevent BGP auto-discovery of remote PEs. ciVplsBgpExtVETable's entries and their ciVplsBgpExtRTRowStatus reveal whether a given VE has been successfully provisioned (active) or is stuck in a notReady state.

What Can Be Monitored

route distinguisher configuration
VE-ID range size
route-target import/export policy
VE entry provisioning/row status

Imported Objects

From CISCO-IETF-VPLS-GENERIC-MIB

cvplsConfigIndex	OBJECT-TYPE
cvplsPwBindIndex	OBJECT-TYPE

From CISCO-SMI

ciscoExperiment

OBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
StorageType
TEXTUAL-CONVENTION

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoIetfVplsBgpExtMIB	1.3.6.1.4.1.9.10.140			This MIB module enables the use of any underlying Pseudo Wire network. This MIB extends the MIB module published in the RFC 4188 to manage object definitions for BGP signalled VPLS. GLOSSARY PE The term PE refers to Provider-Edge devices. Pseudo Wire An emulation of a native service over a Packet Switched Network. RD (Route Distinguisher) They are used to create VPN-IPv4 addresses, as specified in [RFC4364]. RT (Route Target) A Route Target attribute can be thought of as identifying a set of sites. More description specified in [RFC4364]. u-PE A Layer 2 PE device used for Layer 2 aggregation. The notion of u-PE is described further in [RFC4761]. VE The term VE refers to a VPLS Edge device, which could be either a PE or a u-PE. VPLS Virtual private LAN service. A type of layer 2 VPN.
ciscoIetfVplsBgpExtMIBNotifs	1.3.6.1.4.1.9.10.140.0
ciscoIetfVplsBgpExtMIBObjects	1.3.6.1.4.1.9.10.140.1
ciVplsBgpExtConfigTable	1.3.6.1.4.1.9.10.140.1.1		not-accessible	This table specifies information for configuring and monitoring BGP-specific parameters for VPLS. A row is automatically created when a VPLS is configured using BGP signalling. None of the read-write objects values can be changed when cvplsConfigRowStatus is in the active(1) state. Changes are allowed when the cvplsConfigRowStatus is in notInService(2) or notReady(3) states only. If the operator need to change one of the values for an active row the cvplsConfigRowStatus should be first changed to notInService(2), the objects may be changed now, and later to active(1) in order to re-initiate the signaling process with the new values in effect.
ciVplsBgpExtConfigEntry	1.3.6.1.4.1.9.10.140.1.1.1		not-accessible	Each Entry represents a conceptual row in ciVplsBgpExtConfigTable and provides the information about BGP-specific information for VPLS in a packet network.
CIV ciVplsBgpExtConfigRouteDistinguisher	1.3.6.1.4.1.9.10.140.1.1.1.1	CiVplsBgpExtRouteDistinguisher	read-write	This object represents the Route Distingiusher for this VPLS.
U32 ciVplsBgpExtConfigVERangeSize	1.3.6.1.4.1.9.10.140.1.1.1.4	Unsigned32	read-write	This object represents the size of the range of VE identifiers in this VPLS. This number controls the size of the label block advertised for this VE by the PE. A value of 0 indicates that the range is not configured and the PE derives the range value from received advertisements from other PEs.
civplsBgpExtRTTable	1.3.6.1.4.1.9.10.140.1.2		not-accessible	This table specifies information for the list of RTs imported or exported by BGP during auto-discovery of VPLS.
civplsBgpExtRTEntry	1.3.6.1.4.1.9.10.140.1.2.1		not-accessible	Each Entry represents a conceptual row in civplsBgpExtRTTable and provides the information about the value of the RT being used by BGP. Depending on the value of civplsBgpExtRTType, an RT might be exported or imported or both. Every VPLS, which uses auto-discovery for finding peer nodes, can import and export multiple RTs. This representation allows support for hierarchical VPLS. A row is created by the operator or agent prior to autodiscovery.
CIV ciVplsBgpExtRTType	1.3.6.1.4.1.9.10.140.1.2.1.1	CiVplsBgpExtRouteTargetType	read-create	This object represents the type of a RT usage. RTs can be specified to be imported, exported, or both.
CIV ciVplsBgpExtRT	1.3.6.1.4.1.9.10.140.1.2.1.2	CiVplsBgpExtRouteTarget	read-create	The RT associated with the VPLS service.
STO ciVplsBgpExtRTStorageType	1.3.6.1.4.1.9.10.140.1.2.1.3	StorageType	read-create	This object indicates the storage type for this row.
ROW ciVplsBgpExtRTRowStatus	1.3.6.1.4.1.9.10.140.1.2.1.4	RowStatus	read-create	This object is used to create, modify, and/or delete a row in this table. When a row in this table is in active(1) state, no objects in that row can be modified.
ciVplsBgpExtVETable	1.3.6.1.4.1.9.10.140.1.3		not-accessible	This table associates VPLS Edge devices to a VPLS. The VEs assigned to a VPLS can be configured on a PE. This table has an expansion dependant relationship with cvplsConfigTable. For each row identified by cvplsConfigIndex, there may exist one or more rows in this table. ciVplsBgpExtVEId is the expansion index. None of the read-create objects values can be changed when ciVplsBgpExtVERowStatus is in the active(1) state. Changes are allowed when the ciVplsBgpExtVERowStatus is in notInService(2) or notReady(3) states only. If the operator need to change one of the values for an active row the ciVplsBgpExtVERowStatus should be first changed to notInService(2), the objects may be changed now, and later to active(1) in order to re-initiate the signaling process with the new values in effect.
ciVplsBgpExtVEEntry	1.3.6.1.4.1.9.10.140.1.3.1		not-accessible	Each Entry represents a conceptual row in ciVplsBgpExtVETable and provides the information about VPLS Edge devices.
CIV ciVplsBgpExtVEId	1.3.6.1.4.1.9.10.140.1.3.1.1	CiVplsBgpExtVEID	not-accessible	This object identifies a VE associated with a VPLS.
STR ciVplsBgpExtVEName	1.3.6.1.4.1.9.10.140.1.3.1.2	SnmpAdminString	read-create	This object represents the name of the site or u-PE associated with this VE.
U32 ciVplsBgpExtVEPreference	1.3.6.1.4.1.9.10.140.1.3.1.3	Unsigned32	read-create	This object represents the preference of the VE if the site is multi-homed and VE Id is used.
STO ciVplsBgpExtVEStorageType	1.3.6.1.4.1.9.10.140.1.3.1.5	StorageType	read-create	This object indicates the storage type for this row.
ROW ciVplsBgpExtVERowStatus	1.3.6.1.4.1.9.10.140.1.3.1.6	RowStatus	read-create	This object is used to create, modify, and/or delete a row in this table. When a row in this table is in active(1) state, no objects in that row can be modified.
ciVplsBgpExtPwBindTable	1.3.6.1.4.1.9.10.140.1.4		not-accessible	This table provides BGP-specific information for an association between a VPLS and the corresponding Pseudo Wires. A service can have more than one Pseudo Wire association. Pseudo Wires are defined in the cpwvcTable. Each row represents an association between a VPLS instance and one or more Pseudo Wires defined in the cpwVcTable in CISCO-IETF-PW-MIB. An Entry in this table in instantiated only when BGP signalling is used to configure VPLS.
ciVplsBgpExtPwBindEntry	1.3.6.1.4.1.9.10.140.1.4.1		not-accessible	Each Entry represents a conceptual row in ciVplsBgpExtPwBindTable and provides the information about BGP-specific information for an association between a VPLS and the corresponding Pseudo Wires.
CIV ciVplsBgpExtPwBindLocalVEId	1.3.6.1.4.1.9.10.140.1.4.1.1	CiVplsBgpExtVEID	read-only	This object represents the local VE this Pseudo Wire is associated with.
CIV ciVplsBgpExtPwBindRemoteVEId	1.3.6.1.4.1.9.10.140.1.4.1.2	CiVplsBgpExtVEID	read-only	This object represents the remote VE this Pseudo Wire is associated with.
ciscoIetfVplsBgpExtMIBConform	1.3.6.1.4.1.9.10.140.2
ciscoIetfVplsBgpExtMIBCompliances	1.3.6.1.4.1.9.10.140.2.1
ciscoIetfVplsBgpExtMIBCompliance	1.3.6.1.4.1.9.10.140.2.1.1			Compliance statement for the entities that implement the ciscoIetfVplsBgpExtMIB module.
ciscoIetfVplsBgpExtMIBGroups	1.3.6.1.4.1.9.10.140.2.2
ciVplsBgpExtConfigGroup	1.3.6.1.4.1.9.10.140.2.2.1			This group of objects help to configure L2VPN VPLS using BGP.
ciVplsBgpExtRTGroup	1.3.6.1.4.1.9.10.140.2.2.2			The group of objects help to manage RTs for L2VPN VPLS using BGP.
ciVplsBgpExtVEGroup	1.3.6.1.4.1.9.10.140.2.2.3			The group of objects help to manage VE devices for L2VPN VPLS using BGP.
ciVplsBgpExtPwBindGroup	1.3.6.1.4.1.9.10.140.2.2.4			The group of objects help to manage Pseudo Wires for L2VPN VPLS using BGP.

RFC description

Cisco extension MIB for BGP-signaled VPLS (Virtual Private LAN Service) management.

Start monitoring Cisco provider-edge routers 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 CISCO-IETF-VPLS-BGP-EXT-MIB

What Is CISCO-IETF-VPLS-BGP-EXT-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description