H3C Technologies H3C SR8800 - Manual (Page 332)

321
[CE3-bgp] peer 100.1.1.2 as-number 100
[CE3-bgp] import-route direct
[CE3-bgp] quit
# Configure PE 3.
[PE3] ip vpn-instance vpn1
[PE3-vpn-instance-vpn1] route-distinguisher 100:1
[PE3-vpn-instance-vpn1] vpn-target 1:1
[PE3-vpn-instance-vpn1] quit
[PE3] interface GigabitEthernet 4/1/1
[PE3-GigabitEthernet4/1/1] ip binding vpn-instance vpn1
[PE3-GigabitEthernet4/1/1] ip address 100.1.1.2 24
[PE3-GigabitEthernet4/1/1] quit
[PE3] bgp 100
[PE3-bgp] ipv4-family vpn-instance vpn1
[PE3-bgp-vpn1] peer 100.1.1.1 as-number 65410
[PE3-bgp-vpn1] import-route direct
[PE3-bgp-vpn1] quit
[PE3-bgp] quit
NOTE:
The configurations for PE 4 and CE 4 are similar to those for PE 3 and CE 3. (Details not shown)
5. Configure an MP-IBGP peer relationship between the PEs of the customer carrier to exchange the
VPN routes of the end customers
# Configure PE 3.
[PE3] bgp 100
[PE3-bgp] peer 6.6.6.9 as-number 100
[PE3-bgp] peer 6.6.6.9 connect-interface loopback 0
[PE3-bgp] ipv4-family vpnv4
[PE3-bgp-af-vpnv4] peer 6.6.6.9 enable
[PE3-bgp-af-vpnv4] quit
[PE3-bgp] quit
NOTE:
The configurations for PE 4 are similar to those for PE 3. (Details not shown)
6. Verify your configurations
After completing all the configurations, issue the display ip routing-table command on PE 1 and PE
2. The output shows that only routes of the provider carrier network are present in the public
network routing table of PE 1 and PE 2. Take PE 1 as an example:
[PE1] display ip routing-table
Routing Tables: Public
Destinations : 7 Routes : 7
Destination/Mask Proto Pre Cost NextHop Interface
3.3.3.9/32 Direct 0 0 127.0.0.1 InLoop0
4.4.4.9/32 ISIS 15 10 30.1.1.2 POS2/1/2
30.1.1.0/24 Direct 0 0 30.1.1.1 POS2/1/2
30.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0