HP 10500 SERIES Configuration Manual page 349

10.2.1.0/24
10.2.1.1/32
10.2.1.2/32
127.0.0.0/8
127.0.0.1/32
200.1.1.0/24
200.1.1.1/32
Execute the display ip routing-table vpn-instance command on the PEs. You can see the route to
the VPN behind the peer CE. Take PE 2 as an example:
<PE2> display ip routing-table vpn-instance vpn1
Routing Tables: vpn1
Destinations : 7
Destination/Mask
10.1.1.0/24
10.1.1.1/32
10.2.1.0/24
10.2.1.1/32
10.2.1.2/32
100.1.1.1/32
200.1.1.1/32
Enabling BGP update packet debugging on PE 2, you can see that PE 2 advertises the route to
100.1.1.1/32, and the AS_PATH is 100 600.
<PE2> terminal monitor
<PE2> terminal debugging
<PE2> debugging bgp update vpn-instance vpn1 verbose
<PE2> refresh bgp vpn-instance vpn1 all export
*0.4402392 PE2 RM/7/RMDEBUG:
BGP.vpn1: Send UPDATE to 10.2.1.1 for following destinations :
Origin
AS Path
Next Hop
100.1.1.1/32,
Execute the display bgp routing-table peer received-routes command on CE 2. You can see that
CE 2 has not received the route to 100.1.1.1/32.
<CE2> display bgp routing-table peer 10.2.1.2 received-routes
Total Number of Routes: 4
BGP Local router ID is 10.2.1.1
Status codes: * - valid, ^ - VPN best, > - best, d - damped,
Network
*> 10.1.1.0/24
*> 10.1.1.1/32
* 10.2.1.0/24
* 10.2.1.1/32
Configure BGP AS number substitution:
2.
# Configure BGP AS number substitution on PE 2.
<PE2> system-view
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
Routes : 7
Proto Pre Cost
BGP 255 0
BGP 255 0
Direct 0 0
Direct 0 0
Direct 0 0
BGP 255 0
BGP 255 0
: Incomplete
: 100 600
: 10.2.1.2
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
NextHop
10.2.1.2
10.2.1.2
10.2.1.2
10.2.1.2
341
10.2.1.1
127.0.0.1
10.2.1.2
127.0.0.1
127.0.0.1
200.1.1.1
127.0.0.1
NextHop
1.1.1.9
1.1.1.9
10.2.1.2
10.2.1.1
127.0.0.1
1.1.1.9
10.2.1.1
MED LocPrf PrefVal Path/Ogn
0
0
Vlan11
InLoop0
Vlan11
InLoop0
InLoop0
InLoop0
InLoop0
Interface
NULL0
NULL0
Vlan11
Vlan11
InLoop0
NULL0
Vlan11
0 100?
0 100?
0 100?
0 100?