Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

show l2vpn connections

Syntax

show l2vpn connections <brief | extensive><down | up | up-down> <history><instance instance><instance-history><local-site local-site><logical-system (all | logical-system-name)><remote-site remote-site><status><summary>

Release Information

Command introduced before Junos OS Release 7.4.

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

Description

Display Layer 2 virtual private network (VPN) connections.

Options

none
—

Display all Layer 2 VPN connections for all routing instances.

brief | extensive
—

(Optional) Display the specified level of output.

down | up | up-down
—

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

history
—

(Optional) Display information about connection history.

instance instance
—

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

instance-history
—

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

local-site local-site
—

(Optional) Display connections for the specified Layer 2 VPN local site name or ID only.

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

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

remote-site remote-site
—

(Optional) Display connection for the specified Layer 2 VPN remote site ID only.

status
—

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

summary
—

(Optional) Display summary of all Layer 2 VPN connections information.

Required Privilege Level

view

List of Sample Output

show l2vpn connections
show l2vpn connections extensive
show l2vpn connections extensive (VPWS)

Output Fields

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

Table 1: show l2vpn connections Output Fields

Field Name

Field Description

Instance

Name of Layer 2 VPN instance.

L2vpn-id

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

Local-ID

BGP local-address assigned to the local routing device.

Local site

Name of local site.

Local source-attachment-id

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.

Target-attachment-id

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.

Interface name

Name of interface.

Remote Site ID

Remote site ID.

Label Offset

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

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.

Range

Advertises the label block size.

status-vector

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.

connection-site

Name of the connection site.

Type

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

St

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

Time last up

Time that the connection was last in the Up condition.

# Up trans

Number of transitions from Down to Up condition.

Local circuit

Address and status of local circuit.

Remote circuit

Address and status of remote circuit.

St

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 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.
  • 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 pseduowire 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.

Remote PE

Address of the remote provider edge router.

Incoming label

Name of the incoming label.

Outgoing label

Name of the outgoing label.

Time

Date and time of Layer 2 VPN connection event.

Event

Type of event.

Interface/Lbl/PE

Interface, label, or PE router.

Sample Output

show l2vpn connections

user@host> show l2vpn connections 
L2VPN Connections :
Instance : vpna
Local site: 2 (ce-2)
offset: 1, range: 3, label-base: 32768
    connection-site           Type  St  Time last up          # Up trans
    3 (3)                     loc   Up  Jul 18 20:45:46 2001           1
      Local circuit: fe-0/0/0.1, Status: Up
      Remote circuit: fe-0/0/3.0, Status: Up
    1                         rmt   Up  Jul 18 21:47:25 2001           1
      Local circuit: fe-0/0/0.0, Status: Up
      Remote PE: 192.0.2.1
      Incoming label: 32768, Outgoing label: 32769
Local site: 3 (ce-3)
offset: 1, range: 2, label-base: 33792
    connection-site           Type  St  Time last up          # Up trans
    2 (ce-b)                  loc   Up  Jul 18 20:45:46 2001           1
      Local circuit: fe-0/0/0.1, Status: Up
      Remote circuit: fe-0/0/3.0, Status: Up
    1                         rmt   Up  Jul 18 21:47:25 2001           1
      Local circuit: fe-0/0/3.1, Status: Up
      Remote PE: 192.0.2.1
      Incoming label: 33792, Outgoing label: 32770

show l2vpn connections extensive

user@host> show l2vpn connections extensive 
L2VPN Connections:

Legend for connection status (St)   
EI -- encapsulation invalid      NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch     WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down    NP -- interface hardware not present 
CM -- control-word mismatch      -> -- only outbound connection is up
CN -- circuit not provisioned    <- -- only inbound connection is up
OR -- out of range               Up -- operational
OL -- no outgoing label          Dn -- down                      
LD -- local site signaled down   CF -- call admission control failure      
RD -- remote site signaled down  SC -- local and remote site ID collision
LN -- local site not designated  LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status  IL -- no incoming label

Instance: vpn1
  Local site: SITE-A (1)
    Number of local interfaces: 1
    Number of local interfaces up: 1
    ge-1/0/0.517        2         
    Label-base        Offset     Size  Range     Preference
    800000            1          2      2         100   
      status-vector:  0 
    connection-site           Type  St     Time last up          # Up trans
    2                         rmt   Up     Mar  5 18:24:30 2014           1
      Remote PE: 192.0.2.34, Negotiated control-word: Yes (Null)
      Incoming label: 800001, Outgoing label: 800000
      Local interface: ge-0/0/1.517, Status: Up, Encapsulation: VLAN
    Connection History:
        Apr  25 11:18:09 2014  PE route changed     
        Apr  25 11:18:09 2014  Out lbl Update                    800000
        Apr  25 11:18:09 2014  In lbl Update                     800001
        Apr  25 11:18:09 2014  loc intf up                 ge-0/0/1.517

show l2vpn connections extensive (VPWS)

user@host> show l2vpn connections 
Layer-2 VPN connections:

Legend for connection status (St)   
EI -- encapsulation invalid      NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch     WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down    NP -- interface hardware not present 
CM -- control-word mismatch      -> -- only outbound connection is up
CN -- circuit not provisioned    <- -- only inbound connection is up
OR -- out of range               Up -- operational
OL -- no outgoing label          Dn -- down                      
LD -- local site signaled down   CF -- call admission control failure      
RD -- remote site signaled down  SC -- local and remote site ID collision
LN -- local site not designated  LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status  IL -- no incoming label
MM -- MTU mismatch               MI -- Mesh-Group ID not available
BK -- Backup connection          ST -- Standby connection
PF -- Profile parse failure      PB -- Profile busy
RS -- remote site standby        SN -- Static Neighbor
LB -- Local site not best-site   RB -- Remote site not best-site
VM -- VLAN ID mismatch

Legend for interface status 
Up -- operational           
Dn -- down

Instance: FEC129-VPWS
  L2vpn-id: 100:100
    Number of local interfaces: 1
    Number of local interfaces up: 1
    ge-2/0/5.0         
  Local source-attachment-id: 1 (ONE)
    Target-attachment-id      Type  St     Time last up          # Up trans
    2                         rmt   Up     Nov 28 16:16:14 2012           1
      Remote PE: 198.51.100.2, Negotiated control-word: No
      Incoming label: 299792, Outgoing label: 299792
      Local interface: ge-2/0/5.0, Status: Up, Encapsulation: ETHERNET
    Connection History:
        Nov 28 16:16:14 2012  status update timer  
        Nov 28 16:16:14 2012  PE route changed     
        Nov 28 16:16:14 2012  Out lbl Update                    299792
        Nov 28 16:16:14 2012  In lbl Update                     299792
        Nov 28 16:16:14 2012  loc intf up                   ge-2/0/5.0

Published: 2014-04-24

Supported Platforms

Published: 2014-04-24

Previous Page Next Page