3Com 8807 Configuration Manual page 600

600 C 49: BGP/MPLS VPN C
HAPTER ONFIGURATION
Check whether the BGP adjacent is established correctly.
■
Check whether the routing import/export relation of the VPN-instance is
■
correct.
Check whether allow-as-loop is configured between spoke PE and hub PE.
■
Symptom 4
Fall to specify the Loopback interface at the peer end as the BGP neighbor.
Solution:
Check whether the local routing table has learnt the Loopback interface
■
routing information of the peer end using the display ip routing-table
command.
Check whether the address of the Loopback interface at the peer end can be
■
pinged using the ping command.
Check whether the configuration information is correct using the display
■
current-configuration bgp command; confirm that you have specified the
local loopback interface as the interface to create adjacent interface with the
peer end by using the peer peer-address connect-interface command;
confirm that you have activate the neighbor in VPNv4 sub-address family view.
Check whether the BGP information is correct on the PE at the peer end; check
■
whether specified the local Loopback interface as the interface to create
adjacent with the peer end; and check whether you have configured VPN
capacity.
Symptom 5
During ASBR configuration, VPN route interior label does not switch on the ASBR.
Solution:
Check whether the VPN neighbor is created correctly using the display bgp
■
vpnv4 all peer command.
Check whether ASBR is configured with the undo policy vpn-target
■
command. If not, configure this command.