3Com S7906E Configuration Manual page 1618

127.0.0.0/8 Direct 0
127.0.0.1/32 Direct 0
200.1.1.0/24 Direct 0
200.1.1.1/32 Direct 0
Issuing the display ip routing-table vpn-instance command on the PEs, you should see the route to
the VPN behind the peer CE. Takes PE 2 as an example:
<PE2> display ip routing-table vpn-instance vpn1
Routing Tables: vpn1
Destinations : 7
Destination/Mask Proto
10.1.1.0/24 BGP
10.1.1.1/32 BGP
10.2.1.0/24 Direct 0
10.2.1.1/32 Direct 0
10.2.1.2/32 Direct 0
100.1.1.1/32 BGP
200.1.1.1/32 BGP
Enabling BGP update packet debugging on PE 2, you should 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 : Incomplete
AS Path : 100 600
Next Hop : 10.2.1.2
100.1.1.1/32,
Issuing the display bgp routing-table peer received-routes command on CE 2, you should see that
CE 2 did not receive 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, > - best, d - damped,
h - history,
Origin : i - IGP, e - EGP, ? - incomplete
Network
*> 10.1.1.0/24
*> 10.1.1.1/32
* 10.2.1.0/24
* 10.2.1.1/32
2) Configure BGP AS number substitution
# Configure BGP AS number substitution on PE 2.
<PE2> system-view
[PE2] bgp 100
0 127.0.0.1
0 127.0.0.1
0 200.1.1.1
0 127.0.0.1
Routes : 7
Pre Cost NextHop
255 0 1.1.1.9
255 0 1.1.1.9
0 10.2.1.2
0 10.2.1.1
0 127.0.0.1
255 0 1.1.1.9
255 0 10.2.1.1
i - internal, s - suppressed, S - Stale
NextHop MED
10.2.1.2
10.2.1.2
10.2.1.2 0
10.2.1.2 0
1-103
InLoop0
InLoop0
InLoop0
InLoop0
Interface
NULL0
NULL0
Vlan11
Vlan11
InLoop0
NULL0
Vlan11
LocPrf PrefVal Path/Ogn
0 100?
0 100?
0 100?
0 100?