Example For Configuring Inter-Provider Vpn Option C - 3Com MSR 50 Series Configuration Manual

1524 C 79: MPLS L3VPN C
HAPTER
Example for Configuring
Inter-Provider VPN
Option C
ONFIGURATION
[PE2-vpn-instance-vpn1] vpn-target 3:3 export-extcommunity
[PE2-vpn-instance-vpn1] quit
# Bind the interface connected with CE 1 to the created VPN instance.
[PE2] interface ethernet 1/1
[PE2-Ethernet1/1] ip binding vpn-instance vpn1
[PE2-Ethernet1/1] ip address 20.0.0.1 8
[PE2-Ethernet1/1] quit
# Start BGP on PE 2.
[PE2] bgp 600
# Configure IBGP peer 4.4.4.9 as a VPNv4 peer.
[PE2-bgp] peer 4.4.4.9 as-number 600
[PE2-bgp] peer 4.4.4.9 connect-interface loopback 0
[PE2-bgp] ipv4-family vpnv4
[PE2-bgp-af-vpnv4] peer 4.4.4.9 enable
[PE2-bgp-af-vpnv4] quit
# Specify to inject direct routes to the VPN routing table of vpn1.
[PE2-bgp] ipv4-family vpn-instance vpn1
[PE2-bgp-vpn1] import-route direct
[PE2-bgp-vpn1] quit
[PE2-bgp] quit
5 Verify your configurations
After you complete the above configurations, PE 1 and PE 2 should be able to ping
each other.
Network requirements
Site 1 and Site 2 belong to the same VPN. Site 1 accesses the network through
■
PE 1 in AS 100 and Site 2 accesses the network through PE 2 in AS 600.
PEs in the same AS runs IS-IS between them.
■
PE 1 and ASBR-PE 1 exchange labeled IPv4 routes by MP-IBGP.
■
PE 2 and ASBR-PE 2 exchange labeled IPv4 routes by MP-IBGP.
■
PE 1 and PE 2 are MP-EBGP peers.
■
ASBR-PE 1 and ASBR-PE 2 use their respective routing policies and label the
■
routes received from each other.
ASBR-PE 1 and ASBR-PE 2 use MP-EBGP to exchange labeled IPv4 routes.
■