H3C S9500 Series Operation Manual page 948

Operation Manual – MPLS L3VPN
H3C S9500 Series Routing Switches
[PE3-bgp-af-vpn-instance] import-route direct
[PE3-bgp-af-vpn-instance] import-route static
[PE3-bgp-af-vpn-instance] group 192 external
[PE3-bgp-af-vpn-instance] peer 192.168.13.2 group 192 as-number 65003
[PE3-bgp-af-vpn-instance] quit
[PE3-bgp] quit
# Set up EBGP adjacency between PE3 and CE4 in VPN-instance3.2, import intra-CE4
VPN routes learned into VPN-instance3.2.
[PE3-bgp] ipv4-family vpn-instance vpn-instance3.2
[PE3-bgp-af-vpn-instance] import-route direct
[PE3-bgp-af-vpn-instance] import-route static
[PE3-bgp-af-vpn-instance] group 232 external
[PE3-bgp-af-vpn-instance] peer 192.168.23.2 group 232 as-number 65004
[PE3-bgp-af-vpn-instance] quit
[PE3-bgp] quit
# Bind the interface connecting PE3 and CE3 to VPN-instance3.1 and the interface
connecting PE3 and CE4 to VPN-instance 3.2.
[PE3] vlan 311
[PE3-vlan311] port gigabitethernet 3/1/1
[PE3-vlan311] quit
[PE3] interface Vlan-interface 311
[PE3-Vlan-interface311] ip binding vpn-instance vpn-instance3.1
[PE3-Vlan-interface311] ip address 192.168.13.1 255.255.255.0
[PE3-Vlan-interface311] quit
[PE3] vlan 314
[PE3-vlan314] port gigabitethernet 3/1/4
[PE3-vlan314] quit
[PE3] interface Vlan-interface 314
[PE3-Vlan-interface314] ip binding vpn-instance vpn-instance3.2
[PE3-Vlan-interface314] ip address 192.168.23.1 255.255.255.0
[PE3-Vlan-interface314] quit
1.4.5 Cross-domain MPLS L3VPN Configuration Example
I. Network requirements
A VPN subscriber has sites in both city A and B. Because of the geographical reason,
site in City A accesses to the MPLS/VPN network of service provider in City A, and gets
AS100 as the AS number; site in City B accesses to the MPLS/VPN network of service
provider in City B, and gets AS200 as the AS number. The VPN goes through two ASs.
CE1 and CE2 belong to VPN-A, while CE3 and CE4 belong to VPN-B.
Chapter 1 MPLS L3VPN Configuration
1-51