Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

show evpn vpws-instance

Syntax

Description

Display the details of the VPWS instance of the EVPN.

Options

evpn-vpws-instance-name

(Optional) Name of the VPWS instance of the EVPN.

Required Privilege Level

view

Output Fields

Table 1 describes the output fields for the show evpn vpws-instance command. Output fields are listed in the approximate order in which they appear.

Table 1: show evpn vpws-instance Output Fields

Field Name

Field Description

Instance

Name of the routing instance.

Route Distinguisher

Route distinguisher as configured for the routing instance on the node.

Number of local interfaces

Number of interfaces configured to be part of the routing instance.

Interface name

Name of the interface.

ESI

Ethernet segment identifier (ESI) configured for the interface.

Mode

Single-homed, single-active, or all-active form of multihoming.

Role

Primary or backup, depending on the role. The role, depending on the mode, is as follows:

  • Single-active multihoming–Role is primary if the interface is the designated forwarder(DF) and backup if the interface is the non-DF.

  • All-active multihoming–Role is always primary.

  • Single-homed–Role is always primary.

Status

Status of the interface is either Up or Down. Interface is available if the status is Up and interface is not available if the interface is Down.
Control-Word Whether the device has negotiated to use the control word for MPLS pseudowire traffic (Yes) or not (No, the default).
Flow-Label-Tx Flow-aware transport of pseudowires (FAT) flow labels is enabled (Yes) or is not enabled (No, the default) in the routing instance to push flow labels in pseudowire packets sent to a remote provider edge (PE) router.
Flow-Label-Rx Flow-aware transport of pseudowires (FAT) flow labels is enabled (Yes) or is not enabled (No, the default) in the routing instance to pop flow labels from pseudowire packets from a remote PE router.

Local SID

Local service identifier configured on the interface.

Advertised Label

Label advertised for the service identifier as part of the autodiscovery route per the EVPN instance (EVI).

PE routers hosting the local service identifier as configured on the interface

  

PE addr

IP address of the PE router advertising the autodiscovered route per the EVI.

ESI

ESI encoded in the autodiscovered route per the EVI.

Label

Label as encoded in the autodiscovered route per the EVI.

Mode

Single-homed, single-active, or all-active form of multihoming.

Role

Primary or backup depending on the role. The role depending on the mode is as follows:

  • Single-active multihoming–Role is primary if the interface is designated forwarder(DF) and backup if the interface is non-DF.

  • All-active multihoming–Role is always primary.

  • Single-homed–Role is always primary.

TS

Timestamp of the receipt of the autodiscovered route per the EVI. This is used as tie breaker in case there are two PE routers advertising the autodiscovered route per the EVI with the P bit set.

Status

The status can be as follows:

  • Resolved—The autodiscovered route per the ESI was received for the ESI from the PE router.

  • Unresolved—The autodiscovered route per the ESI was not received for the ESI from the PE router.

PE routers hosting the remote service identifier as configured on the interface

  

Remote SID

Remote service identifier configured on the interface.

PE addr

IP address of the PE router advertising the autodiscovered route per the EVI.

ESI

ESI encoded in the autodiscovered route per the EVI.

Label

Label as encoded in the autodiscovery route per the EVI.

Mode

Single-homed, single-active, or all-active form of multihoming.

Role

Primary or backup depending on the role. The role depending on the mode is as follows:

  • Single-active multihoming–Role is primary if the interface is designated forwarder(DF) and backup if the interface is non-DF.

  • All-active multihoming–Role is always primary.

  • Single-homed–Role is always primary.

TS

Timestamp of the receipt of the autodiscovered route per the EVI. This is used as tie breaker in case there are two PE routers advertising the autodiscovered route per the EVI with the P bit set.

Status

The status can be as follows:

  • Resolved—The autodiscovered route per the ESI was received for the ESI from the PE router.

  • Unresolved—The autodiscovered route per the ESI was not received for the ESI from the PE router.

Fast Convergence Information

Details of the ESI, the PE router, and the advertised service identifier used during fast convergence.

ESI

ESI as advertised in the autodiscovered route per the ESI.

Number of PE nodes

Number of PE nodes available.

PE

IP address of the PE router advertising the autodiscovered route per the ESI.

Advertised SID

List of service identifiers that get impacted if the PE router withdraws the autodiscovered route per the ESI.

DF Election Information for Single-Active ESI

Details of the DF election information for the single-active ESI.

ESI

ESI as advertised in the Ethernet segment route.

SID used for DF Election

Minimum service identifier configured for the ESI in the EVI.

ESI granularity

Type: Per ESI.

LACP OOS on NDF

Enabled or Disabled

Primary PE

PE router that is the DF for the ESI.

Backup PE

PE router that is the backup DF for the ESI.
   

Last DF Election

Last time when the DF election algorithm was executed on the PE router.

Sample Output

show evpn vpws-instance instance-name

show evpn vpws-instance instance-name

show evpn vpws-instance instance-name(Per ESI)

show evpn vpws-instance instance-name (with FAT flow label load balancing enabled)

Release Information

Statement introduced in Junos OS Release 17.1.

Related Documentation