3Com Switch 8800 Configuration Guide Chapter 37 BGP/MPLS VPN Configuration
37-91
III. Symptom 3
In Hub&Spoke networking mode, spoke PE cannot learn the private networking route of
Hub PE.
Solution:
z Check whether the LSP tunnel is established using the display mpls lsp
command.
z Check whether the BGP adjacent is established correctly.
z Check whether the routing import/export relation of the VPN-instance is correct.
z Check whether allow-as-loop is configured between spoke PE and hub PE.
IV. Symptom 4
Fall to specify the loopback interface at the peer end as the BGP neighbor.
Solution:
z Check whether the local routing table has learnt the loopback interface routing
information of the peer end using the display ip routing-table command.
z Check whether the address of the loopback interface at the peer end can be
pinged using the ping command.
z 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.
z 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.
V. Symptom 5
During ASBR configuration, VPN route interior label does not switch on the ASBR.
Solution:
z Check whether the VPN neighbor is created correctly using the display bgp
vpnv4 all peer command.
z Check whether ASBR is configured with the undo policy vpn-target command. If
not, configure this command.