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

188

[Hub-PE-bgp] peer 1.1.1.9 as-number 100

[Hub-PE-bgp] peer 1.1.1.9 connect-interface loopback 0

[Hub-PE-bgp] peer 3.3.3.9 as-number 100

[Hub-PE-bgp] peer 3.3.3.9 connect-interface loopback 0

[Hub-PE-bgp] ipv4-family vpnv4

[Hub-PE-bgp-af-vpnv4] peer 1.1.1.9 enable

[Hub-PE-bgp-af-vpnv4] peer 3.3.3.9 enable

[Hub-PE-bgp-af-vpnv4] quit

[Hub-PE-bgp] quit

# Execute the display bgp peer command or the display bgp vpnv4 all peer command on the PEs.

This example uses Spoke-PE 1 to verify that a BGP peer relationship has been established between

the PEs.

[Spoke-PE1] display bgp peer

BGP local router ID : 1.1.1.9

Local AS number : 100

Total number of peers : 1 Peers in established state : 1

Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State

2.2.2.9 100 6 5 0 0 00:00:32 Established

6. Verify the configuration:

# Execute the display ip routing-table vpn-instance command on a PE. This example uses Spoke-PE

1 to verify that the PE has learned routes to each CE, and for a spoke-PE, the next hop of the route

to the peer spoke-CE is the Hub-PE.

[Spoke-PE1] display ip routing-table vpn-instance vpn1

Routing Tables: vpn1

Destinations : 8 Routes : 8

Destination/Mask Proto Pre Cost NextHop Interface

10.0.0.0/24 BGP 255 0 2.2.2.9 NULL0

10.1.1.0/24 Direct 0 0 10.1.1.2 Eth1/1

10.1.1.2/32 Direct 0 0 127.0.0.1 InLoop0

10.2.1.0/24 BGP 255 0 2.2.2.9 NULL0

10.3.1.0/24 BGP 255 0 2.2.2.9 NULL0

10.4.1.0/24 BGP 255 0 2.2.2.9 NULL0

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 Spoke-CE 1 and Spoke-CE 2 can ping each other. The TTL value indicates that traffic

from Spoke-CE 1 to Spoke-CE 2 passes six hops (255-250+1) and is forwarded through the