3Com S7906E Configuration Manual page 1600

[PE3-bgp] quit
Configurations on PE 4, CE 4 and CE 6 are similar to those on PE 3, CE 3 and CE5 respectively, and
are thus omitted here.
5) Establish MP-EBGP peer relationship between service provider PEs and their CEs to exchange
user VPNv4 routes.
# Configure PE 1, enabling nested VPN.
[PE1] bgp 100
[PE1-bgp] ipv4-family vpnv4
[PE1-bgp-af-vpnv4] nesting-vpn
[PE1-bgp-af-vpnv4] peer 11.1.1.1 vpn-instance vpn1 enable
[PE1-bgp-af-vpnv4] quit
[PE1-bgp] quit
# Configure CE 1, enabling VPNv4 capability and establishing VPNv4 neighbor relationship between
CE 1 and PE 1.
[CE1] bgp 200
[CE1-bgp] ipv4-family vpnv4
[CE1-bgp-af-vpnv4] peer 11.1.1.2 enable
# Specify to allow the local AS number to appear in the AS-PATH attribute of the routes received.
[CE1-bgp-af-vpnv4] peer 11.1.1.2 allow-as-loop 2
# Specify to receive all VPNv4 routes.
[CE1-bgp-af-vpnv4] undo policy vpn-target
[CE1-bgp-af-vpnv4] quit
[CE1-bgp] quit
Configurations on PE 2 and CE 2 are similar to those on PE 1 and CE 1 respectively, and are thus
omitted here.
6) Establish MP-IBGP peer relationship between sub-VPN PEs and CEs of the customer VPN to
exchange VPNv4 routes of sub-VPNs.
# Configure PE 3.
[PE3] bgp 200
[PE3-bgp] peer 2.2.2.9 as-number 200
[PE3-bgp] peer 2.2.2.9 connect-interface loopback 0
[PE3-bgp] ipv4-family vpnv4
[PE3-bgp-af-vpnv4] peer 2.2.2.9 enable
1-85