CISCO-IETF-VPLS-BGP-EXT-MIB: View SNMP OID List / Download MIB

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.

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.

Each Entry represents a conceptual row in ciVplsBgpExtConfigTable and provides the information about BGP-specific information for VPLS in a packet network.

This object represents the Route Distingiusher for this VPLS.

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.

This table specifies information for the list of RTs imported or exported by BGP during auto-discovery of VPLS.

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.

This object represents the type of a RT usage. RTs can be specified to be imported, exported, or both.

The RT associated with the VPLS service.

This object indicates the storage type for this row.

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.

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.

Each Entry represents a conceptual row in ciVplsBgpExtVETable and provides the information about VPLS Edge devices.

This object identifies a VE associated with a VPLS.

This object represents the name of the site or u-PE associated with this VE.

This object represents the preference of the VE if the site is multi-homed and VE Id is used.

This object indicates the storage type for this row.

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.

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.

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.

This object represents the local VE this Pseudo Wire is associated with.

This object represents the remote VE this Pseudo Wire is associated with.

Compliance statement for the entities that implement the ciscoIetfVplsBgpExtMIB module.

This group of objects help to configure L2VPN VPLS using BGP.

The group of objects help to manage RTs for L2VPN VPLS using BGP.

The group of objects help to manage VE devices for L2VPN VPLS using BGP.

The group of objects help to manage Pseudo Wires for L2VPN VPLS using BGP.