Panasonic NN46240-710 - Manual (Page 176)

Nortel Secure Router 8000 Series
Troubleshooting - VPN___________ 5 VPLS troubleshooting
Summary
The differences between VPLS configuration in BGP signaling mode and that in LDP signaling
mode are: the BGP mode requires that the VPLS address family be configured and the remote
peer be enabled in the address family.
When you use BGP signaling, check that the BGP VPLS peer is specified and the remote label
block is received. Whether a VSI can be Up is also affected by the status of the AC and that of
PW as well as the encapsulation type and the MTU.
5.4 FAQs
Q: Why can the VSI not be up after a tunnel and an AC are established in VPLS
configuration?
A: When you configure VPLS, note that:
The VSI ID is consistent at both ends in LDP mode.
The AC interface is bound with the VSI and the AC is in Up state.
A tunnel to the remote end is available.
The MTU and the encapsulation type are consistent at both ends.
The status of the VSI peer is normal.
In BGP mode, the VPN target matches at both ends.
The ID of the local site falls in the range of the remote label block.
Enable the remote peer in the BGP VPLS address family view.
Q: Why can the VPLS not be configured successfully on the VLAN interface?
A: Possible causes are:
• Other services are configured on the VLAN interface, such as MPLS/BGP VPN, multicast,
or Virtual Leased Line (VLL).
• The status of the VLAN is Down.
• The Ethernet subinterface connects PE and P. (The Ethernet subinterface cannot be used to
connect PE and P.)
• The site IDs of the VSI instances conflict with each other. For the same VPLS, site IDs of
different sites must be different.
• No corresponding VSI instance is bound with PE.
Q: What are the requirements for the PW to be up in the configuration of VPLS?
A: The requirements are as follows:
• The parameters such as the encapsulation mode and MTU must be consistent on both
ends.
• The status of AC is Up.
• The status of the tunnel is Up.
• The LDP session or the BGP remote peer exists between PEs.
Issue 5.3 (30 March 2009) Nortel Networks Inc. 5-17