R2511-HP MSR Router Series MPLS Configuration Guide(V5)

209
[PE3-Ethernet1/1] ip binding vpn-instance vpn1
[PE3-Ethernet1/1] ip address 100.1.1.2 24
[PE3-Ethernet1/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
# Configure PE 4 and CE 4 in the same way that PE 3 and CE 3 are configured. (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
# Configure PE 4 in the same way that PE 3 is configured. (Details not shown.)
6. Verify the configuration:
# Verify that only routes of the provider carrier network are present in the public network routing
table on PEs, for example, on PE 1.
[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 POS5/1
30.1.1.0/24 Direct 0 0 30.1.1.1 POS5/1
30.1.1.1/32 Direct 0 0 127.0.0.1 InLoop0
30.1.1.2/32 Direct 0 0 30.1.1.2 POS5/1
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
# Verify that the internal routes of the customer carrier network are present in the VPN routing
tables, but the VPN routes that the customer carrier maintains are not on PEs, for example, on PE
1.
[PE1] display ip routing-table vpn-instance vpn1
Routing Tables: vpn1
Destinations : 11 Routes : 11
Destination/Mask Proto Pre Cost NextHop Interface
1.1.1.9/32 ISIS 15 20 11.1.1.1 POS5/0
2.2.2.9/32 ISIS 15 10 11.1.1.1 POS5/0
5.5.5.9/32 BGP 255 0 4.4.4.9 NULL0
6.6.6.9/32 BGP 255 0 4.4.4.9 NULL0