3Com S7906E Configuration Manual page 1601

# Specify to allow the local AS number to appear in the AS-PATH attribute of the routes received.
[PE3-bgp-af-vpnv4] peer 2.2.2.9 allow-as-loop 2
[PE3-bgp-af-vpnv4] quit
[PE3-bgp] quit
# Configure CE 1.
[CE1] bgp 200
[CE1-bgp] peer 1.1.1.9 as-number 200
[CE1-bgp] peer 1.1.1.9 connect-interface loopback 0
[CE1-bgp] ipv4-family vpnv4
[CE1-bgp-af-vpnv4] peer 1.1.1.9 enable
[CE1-bgp-af-vpnv4] undo policy vpn-target
[CE1-bgp-af-vpnv4] quit
[CE1-bgp] quit
Configurations on PE 4 and CE 2 are similar to those on PE 3 and CE 1 respectively, and are thus
omitted here.
7) Verify the configurations.
After completing all the configurations above, execute the display ip routing-table command on PE 1
and PE 2 to verify that the public routing tables contain only routes on the service provider network. The
following takes PE 1 for illustration.
[PE1] display ip routing-table
Routing Tables: Public
Destinations : 7
Destination/Mask Proto
3.3.3.9/32 Direct 0
4.4.4.9/32 ISIS
30.1.1.0/24 Direct 0
30.1.1.1/32 Direct 0
30.1.1.2/32 Direct 0
127.0.0.0/8 Direct 0
127.0.0.1/32 Direct 0
Execute the display ip routing-table vpn-instance command on PE 1 and PE 2 to verify that the VPN
routing tables contain sub-VPN routes. The following takes PE 1 for illustration.
[PE1] display ip routing-table vpn-instance vpn1
Routing Tables: vpn1
Destinations : 9
Routes : 7
Pre Cost NextHop
0 127.0.0.1
15 10 30.1.1.2
0 30.1.1.1
0 127.0.0.1
0 30.1.1.2
0 127.0.0.1
0 127.0.0.1
Routes : 9
1-86
Interface
InLoop0
Vlan12
Vlan12
InLoop0
Vlan12
InLoop0
InLoop0