Juniper ACX1000 Configuration Manual page 1370

ACX Series Universal Access Router Configuration Guide
Configuration
CLI Quick
Configuration
Device PE1
1312
The pseudowire between Device PE1 and Device PE3 is the primary or working path. The
pseudowire between Device PE1 and Device PE2 is the backup path.
To support VLANs with H-VPLS, you must include the
in the configuration of the MTU device as a workaround to prevent a VLAN ID mismatch.
Otherwise, the PE-r devices report a VLAN ID mismatch, as shown here:
user@PE2> show vpls connections
Layer-2 VPN connections:
Legend for connection status (St)
EI -- encapsulation invalid
EM -- encapsulation mismatch
VC-Dn -- Virtual circuit down
CM -- control-word mismatch
CN -- circuit not provisioned
OR -- out of range
OL -- no outgoing label
LD -- local site signaled down
RD -- remote site signaled down
LN -- local site not designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status
MM -- MTU mismatch
BK -- Backup connection
PF -- Profile parse failure
RS -- remote site standby
LB -- Local site not best-site
VM -- VLAN ID mismatch
Legend for interface status
Up -- operational
Dn -- down
Instance: customer
VPLS-id: 601
Neighbor
10.255.14.217(vpls-id 601) rmt
"CLI Quick Configuration" on page 1312
Figure 68 on page 1311. The section
steps on Device PE1 and Device PE2.
To quickly configure this example, copy the following commands, paste them into a text
file, remove any line breaks, change any details necessary to match your network
configuration, and then copy and paste the commands into the CLI at the
level.
set interfaces ge-2/0/5 vlan-tagging
set interfaces ge-2/0/5 encapsulation vlan-ccc
set interfaces ge-2/0/5 unit 601 encapsulation vlan-ccc
set interfaces ge-2/0/5 unit 601 vlan-id 601
set interfaces ge-2/0/5 unit 601 output-vlan-map swap
set interfaces ge-2/0/5 unit 601 family ccc
output-vlan-map swap
NC -- interface encapsulation not CCC/TCC/VPLS
WE -- interface and instance encaps not same
NP -- interface hardware not present
-> -- only outbound connection is up
<- -- only inbound connection is up
Up -- operational
Dn -- down
CF -- call admission control failure
SC -- local and remote site ID collision
LM -- local site ID not minimum designated
IL -- no incoming label
MI -- Mesh-Group ID not available
ST -- Standby connection
PB -- Profile busy
SN -- Static Neighbor
RB -- Remote site not best-site
Type St Time last up
VM
shows the configuration for all of the devices in
"Step-by-Step Procedure" on page 1314
Copyright © 2017, Juniper Networks, Inc.
statement
# Up trans
describes the
[edit] hierarchy