3Com 8807 Configuration Manual page 598

598 C 49: BGP/MPLS VPN C
HAPTER ONFIGURATION
[CE3] vlan 210
[CE3-vlan210] interface vlan-interface 210
[CE3-Vlan-interface210] ip address 20.3.1.1 24
[CE3-Vlan-interface210] quit
[CE3] bgp 65430
[CE3-bgp] import-route direct
[CE3-bgp] group 10 external
[CE3-bgp] peer 20.3.1.2 group 10 as-number 100
[CE3-bgp] quit
# Configure PE1: Configure PE1 to be the IBGP peer of PE2 in BGP-VPNv4
sub-address family view. Configure PE1 to be the EBGP peer of CE1 in the BGP
VPN1 instance view. Configure a static route between CE2 and PE1 to enable
them to communicate with each other. Import a static route in BGP VPN2 instance
view to advertise it to the remote PE.
[PE1] bgp 100
[PE1-bgp] group 10
[PE1-bgp] peer 2.2.2.9 group 10
[PE1-bgp] peer 2.2.2.9 connect-interface loopback 0
[PE1-bgp] ipv4-family vpnv4
[PE1-bgp-af-vpn] peer 10 enable
[PE1-bgp-af-vpn] peer 2.2.2.9 group 10
[PE1-bgp-af-vpn] quit
[PE1-bgp] ipv4-family vpn-instance vpn1
[PE1-bgp-af-vpn-instance] import-route direct
[PE1-bgp-af-vpn-instance] group 20 external
[PE1-bgp-af-vpn-instance] peer 20.2.1.1 group 20 as-number 65410
[PE1-bgp-af-vpn-instance] quit
[PE1-bgp] ipv4-family vpn-instance vpn2
[PE1-bgp-af-vpn-instance] import-route direct
[PE1-bgp-af-vpn-instance] import-route static
# Configure PE2: set up IBGP peer relation with PE1 in BGP-VPNv4 sub-address
family view; set up EBGP peer relation with CE3 in BGP-VPN instance view.
[PE2] bgp 100
[PE2-bgp] group 10
[PE2-bgp] peer 1.1.1.9 group 10
[PE2-bgp] peer 1.1.1.9 connect-interface loopback 0
[PE2-bgp] ipv4-family vpnv4
[PE2-bgp-af-vpn] peer 10 enable
[PE2-bgp-af-vpn] peer 1.1.1.9 group 10
[PE2-bgp-af-vpn] quit
[PE2-bgp] ipv4-family vpn-instance vpn1
[PE2-bgp-af-vpn-instance] import-route direct
[PE2-bgp-af-vpn-instance] group 20 external
[PE2-bgp-af-vpn-instance] peer 20.3.1.1 group 20 as-number 65430
[PE2-bgp-af-vpn-instance] quit
[PE2-bgp] quit
Configure multi-role host feature: If a routing protocol is employed between CE2
and PE1, configure PE1 not to advertise any route information to CE2 to avoid
route loops. Following depicts a way to achieve this. You can also avoid route
loops in other ways. Directly configure a static route to PC2 on PE1 if no routing
protocol is employed between PE1 and CE2.