Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


show vpls connections



(T Series and M Series routers, except for the M160 router) Display virtual private LAN service (VPLS) connection information.



Display information about all VPLS connections for all routing instances.

brief | extensive

(Optional) Display the specified level of output.

down | up | up-down

(Optional) Display nonoperational, operational, or both types of connections.


(Optional) Display information about connection history.

instance instance-name

(Optional) Display the VPLS connections for the specified routing instance only.


(Optional) Display information about connection history for a particular instance.

local-site local-site-name

(Optional) Display the VPLS connections for the specified local site name or ID only.

remote-site remote-site-name

(Optional) Display the VPLS connections for the specified remote site name or ID only. Label block size information is always shown as 0 when using this option.

logical-system (all | logical-system-name)

(Optional) Perform this operation on all logical systems or on a particular logical system.


(Optional) Display information about the connection and interface status.


(Optional) Display summary of all VPLS connections information.

Required Privilege Level


Output Fields

Table 1 lists the output fields for the show vpls connections command. Output fields are listed in the approximate order in which they appear.

Table 1: show vpls connections Output Fields

Field Name

Field Description


Name of the VPLS instance.

Local site

Name of the local site.


Identifier for the VPLS site.

Number of local interfaces

Number of interfaces configured for the local site.

Number of local interfaces up

Number of interfaces configured for the local site that are currently up.

IRB interface present

Indicates whether or not an integrated routing and bridging (IRB) interface is present (yes or no).


List of all of the interfaces configured for the local site. The types of interfaces can include VPLS virtual loopback tunnel interfaces and label-switched interfaces. Any interface that supports VPLS could be listed here.

Virtual loopback tunnel interfaces are displayed using the vt-fpc/pic/port.nnnnn format. Label-switched interfaces are displayed using the lsi.nnnnn format. In both cases, nnnnn is a dynamically generated virtual port used to transport and receive packets from other provider edge (PE) routers in the VPLS domain.

Each interface might include the following information:

  • Identification as a VPLS interface

  • Name of the associated VPLS routing instance

  • Local site number

  • Remote site number

  • VPLS neighbor address

  • VPLS identifier

Interface flags

Flag associated with the interface. Can include the following:

  • VC-Down—The virtual circuit associated with this interface is down.


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


Displays the VPLS Edge (VE) block offset in the Layer 2 VPN NLRI. The VE block offset is used to identify a label block from which a particular label value is selected to setup a pseduowire for a remote site. The block offset value itself indicates the starting VE ID that maps to the label base contained in the VPLS NLRI advertisement.


Label block size. A configurable value that represents the number of label blocks required to cover all the pseudowires for the remote peer. Acceptable configuration values are: 2, 4, 8 and 16. The default value is 2. A value of 0 will be displayed when using the remote-site option.


Label block range. A value that keeps track of the numbers of remote sites discovered within each label block.


Preference value advertised for a VPLS site. When multiple PE routers are assigned the same VE ID for multihoming, you might need to specify that a particular PE router acts as the designated forwarder by configuring the site preference value. The site preference indicates the degree of preference for a particular customer site. The site preference is one of the tie-breaking criteria used in a designated forwarder election.


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.


IP address and VPLS identifier for the VPLS neighbor. If multiple pseudowires have been configured, the IP address will also show the PW-specific vpls-id-list, for example, (vpls-id 200).


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


Status of the VPLS connection (corresponds with Legend for Connection Status):

  • EI—The local VPLS interface is configured with an encapsulation that is not supported.

  • EM—The encapsulation type received on this VPLS connection from the neighbor does not match the local VPLS 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 pseduowires 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.

    In a multihoming configuration, one multihomed PE site displays the state LN, and the other multihomed PE site displays the state RN in the following circumstances:

    • The multihomed links are both configured to be the backup site.

    • The two multihomed PE routers have the same site ID, but have a peering relationship with a route reflector (RR) that has a different site ID.

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

  • MM—The MTU for the local site and the remote site do not match.

  • BK—The router is using a backup connection.

  • PF—Profile parse failure.

  • RS—The remote site is in a standby state.

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

  • WE—The encapsulation configured for the interface does not match the encapsulation configured for the associated connection within the VPLS 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 VPLS connection is operational.

  • Dn—The VPLS connection is down.

  • CF—The router cannot find enough bandwidth to the remote router to satisfy the VPLS 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 VPLS 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 pseudowire 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 VPLS connection have no MPLS label.

  • MI—The configured mesh group identifier is in use by another system in the network.

  • ST—The router has switched to a standby connection.

  • PB—Profile busy.

  • SN—The VPLS neighbor is static.

Time last up

Time connection was last in the Up condition.

# Up trans

Number of transitions from Down to Up condition.


Status of the (local or remote circuit) local interface:

  • Up—Operational

  • Dn—Down

  • NP—Not present

  • DS—Disabled

  • WE—Wrong encapsulation

  • UN—Uninitialized


Type of encapsulation: VPLS.

Remote PE

Address of the remote provider edge router.

Negotiated control-word

Whether a control word has been negotiated: Yes or No.

Incoming label

Name of the incoming label.

Outgoing label

Name of the outgoing label.

Negotiated PW status TLV

Indicates whether or not the pseudowire status TLV has been negotiated for the VPLS connection.

Local interface

Provides the following information about the local interface configured for the VPLS neighbor:

  • Name of the local interface

  • Status—Interface status (Up or Down)

  • Encapsulation—Interface encapsulation (for example, ETHERNET)

  • Description—Includes the VPLS instance name, the VPLS neighbor address, and the VPLS identifier


Date and time of VPLS connection event.


Type of event.


Interface, label, or PE router.

Connection History

Each entry can include the date, time, year, and the connection event. Connection events include any of a variety of events related to VPLS connections, such as route changes, label updates, and interfaces going down or coming up.

Sample Output

show vpls connections

show vpls connections (with FEC128 and FEC129 in the same routing-instance)

show vpls connections (with multiple pseudowires)

show vpls connections extensive (Static VPLS Neighbors)


Release Information

Command introduced before Junos OS Release 7.4.

instance-history option introduced in Junos OS Release 12.3R2.