Data Center LAN Migration Guide - Juniper Networks

Data Center LAN Migration Guide
VPLS Troubleshooting
This section provides a logical approach to take when determining the root cause of a problem in a VPLS network. A good
place to start is to verify the configuration setup. Following is a brief configuration snippet with corresponding descriptor.
routing-instance {
vpls_vpn1 { #arbitrary name
instance-type vpls; #VPLS type
vlan-tags outer 4094 inner 4093; #VLAN Normalization
must match if configured
interface ge-1/0/0.3001; # int.unit
route-distinguisher 65000:1001; # RD carried in MPGP
vrf-target target:65000:1001; # VPN RT must match on all PEs in this
VPLS
protocols {
vpls {
mac-table-size {
100; # max mac table size
}
interface-mac-limit { # max mac that may be
learned from all CE
50; facing interfaces
}
no-tunnel-services; # lsi interfaces for tunneling
site site-1 { # arbitrary name
site-identifier 1001; # unique site ID
interface ge-1/0/0.3001; # list of int.unit in this
VPN
The next step is to verify the control plane with the following operation commands:
• show route receive-protocol bgp table detail displays BGP routes received from an MPiBGP
peer for a VPLS instance. Use the detail/extensive option to see other BGP attributes such as route-target RT,
label base, and site-ID. The BGP next hop must have a route in the routing table for the mapping to a transport MPLS
LSP.
• show vpls connections is an excellent command to verify the VPLS connection status and to aid in troubleshooting.
After the control plane has been validated as fully functional, the forwarding plane should be checked next by issuing
the following commands. Note that the naming of devices maps to a private MPLS network, as opposed to using a
service provider MPLS network.
On local switch:
• show arp
• show interfaces ge-0/0/0
On MPLS edge router
• show vpls mac-table
• show route forwarding-table
On MPLS core router
• show route table mpls
60 Copyright © 2012, Juniper Networks, Inc.