show l2vpn connections

Name of Layer 2 VPN instance.

For BGP autodiscovery, a globally unique Layer 2 VPN community identifier for the instance.

BGP local-address assigned to the local routing device.

Name of local site.

For FEC 129, the VPWS source attachment identifier. The point-to-point nature of VPWS requires that you specify the source access individual identifier (SAII) and the target access individual identifier (TAII). This SAII-TAII pair defines a unique pseudowire between two PE devices.

For FEC 129, the VPWS target attachment identifier. If the configured target identifier matches a source identifier advertised by a remote PE device by way of a BGP auto-discovery message, the pseudowire between that source-target pair is signaled. If there is no match between an advertised source identifier and the configured target identifier, the pseudowire is not established.

Name of interface.

Remote site ID.

Numbers within the label block that are skipped to find the next label base.

Advertises the first label in a block of labels. A remote PE router uses this first label when sending traffic toward the advertising PE router.

Advertises the label block size.

Bit vector advertising the state of local PE-CE circuits to remote PE routers. A bit value of 0 indicates that the local circuit and LSP tunnel to the remote PE router are up, whereas a value of 1 indicates either one or both are down.

Name of the connection site.

Type of connection: loc (local) or rmt (remote).

Status of the connection. (For a list of possible values, see the Legend for connection status (St) field.)

Time that the connection was last in the Up condition.

Number of transitions from Down to Up condition.

Address and status of local circuit.

Address and status of remote circuit.

Status of the Layer 2 VPN connection (corresponds with Legend for Connection Status):

• EI—The local Layer 2 VPN interface is configured with an encapsulation that is not supported.

• EM—The encapsulation type received on this Layer 2 VPN connection from the neighbor does not match the local Layer 2 VPN connection interface encapsulation type.

• VC-Dn—The virtual circuit is currently down.

• CM—The two routers do not agree on a control word, which causes a control word mismatch.

• CN—The virtual circuit is not provisioned properly.

• OR—The label associated with the virtual circuit is out of range.

• OL—No advertisement has been received for this virtual circuit from the neighbor. There is no outgoing label available for use by this virtual circuit.

• LD—All of the CE-facing interfaces to the local site are down. Therefore, the connection to the local site is signaled as down to the other PE routers. No pseudowires can be established.

• RD—All the interfaces to the remote neighbor are down. Therefore, the remote site has been signaled as down to the other PE routers. No pseudowires can be established.

• LN—The local site has lost path selection to the remote site and therefore no pseuduowires can be established from this local site.

• RN—The remote site has lost path selection to a local site or other remote site and therefore no pseudowires are established to this remote site.

• XX—The Layer 2 VPN connection is down for an unn reason. This is a programming error.

• NC—The interface encapsulation is not configured as an appropriate CCC, TCC, or Layer 2 VPN encapsulation.

• WE—The encapsulation configured for the interface does not match the encapsulation configured for the associated connection within the Layer 2 VPN routing instance.

• NP—The router detects that interface hardware is not present. The hardware might be offline, a PIC might not be of the desired type, or the interface might be configured in a different routing instance.

• ->—Only the outbound connection is up.

• <-—Only the inbound connection is up.

• Up—The Layer 2 VPN connection is operational.

• Dn—The Layer 2 VPN connection is down.

• CF—The router cannot find enough bandwidth to the remote router to satisfy the Layer 2 VPN connection bandwidth requirement.

• SC—The local site identifier matches the remote site identifier. No pseudowire can be established between these two sites. You should configure different values for the local and remote site identifiers.

• LM—The local site identifier is not the minimum designated, meaning it is not the lowest. There is another local site with a lower site identifier. Pseudowires are not being established to this local site. and the associated local site identifier is not being used to distribute Layer 2 VPN label blocks. However, this is not an error state. Traffic continues to be forwarded to the PE router interfaces connected to the local sites when the local sites are in this state.

• RM—The remote site identifier is not the minimum designated, meaning it is not the lowest. There is another remote site connected to the same PE router which has lower site identifier. The PE router cannot established a pseuduowire to this remote site and the associated remote site identifier cannot be used to distribute VPLS label blocks. However, this is not an error state. Traffic can continue to be forwarded to the PE router interface connected to this remote site when the remote site is in this state.

• IL—The incoming packets for the Layer 2 VPN connection have no MPLS label.

Address of the remote provider edge router.

Name of the incoming label.

Name of the outgoing label.

Whether the given PVC is protected by connection protection logic using egress protection for BGP signaled layer 2 services.

Capability to pop the flow label in the receive direction to the remote provider edge (PE) router

Capability to push the flow label in the transmit direction to the provider edge (PE) router

Date and time of Layer 2 VPN connection event.

Type of event.

Interface, label, or PE router.