3Com MSR 50 Series Configuration Manual page 1512

1512 C 79: MPLS L3VPN C
HAPTER
n
ONFIGURATION
[PE1] bgp 100
[PE1-bgp] peer 2.2.2.9 as-number 100
[PE1-bgp] peer 2.2.2.9 connect-interface loopback 0
[PE1-bgp] ipv4-family vpnv4
[PE1-bgp-af-vpnv4] peer 2.2.2.9 enable
[PE1-bgp-af-vpnv4] quit
[PE1-bgp] quit
The configurations for PE 2 are similar to those for PE 1. The detailed configuration
steps are omitted.
After completing the above configuration, if you issue the display bgp peer
command or the display bgp vpnv4 all peer command on the PEs, you should
see that BGP peer relationship has been established between the PEs, and has
reached the state of Established.
[PE1] display bgp vpnv4 all peer
BGP local router ID : 1.1.1.9
Local AS number : 100
Total number of peers : 1
Peer V AS
2.2.2.9 4 100
6 Configure a GRE tunnel
# Configure PE 1.
[PE1] interface tunnel 0
[PE1-Tunnel0] tunnel-protocol gre
[PE1-Tunnel0] source loopback 0
[PE1-Tunnel0] destination 2.2.2.9
[PE1-Tunnel0] ip address 20.1.1.1 24
[PE1-Tunnel0] mpls
[PE1-Tunnel0] quit
# Configure PE 2.
[PE2] interface tunnel 0
[PE2-Tunnel0] tunnel-protocol gre
[PE2-Tunnel0] source loopback 0
[PE2-Tunnel0] destination 1.1.1.9
[PE2-Tunnel0] ip address 20.1.1.2 24
[PE2-Tunnel0] mpls
[PE2-Tunnel0] quit
7 Verify your configurations
After you complete the above configurations, the CEs should be able to learn the
interface routes from each other.
The following takes CE 1 as an example:
[CE1] display ip routing-table
Routing Tables: Public
Destinations : 5
Destination/Mask
10.1.1.0/24
10.1.1.1/32
10.2.1.0/24
Peers in established state : 1
MsgRcvd MsgSent OutQ
3 3 0
Routes : 5
Proto Pre Cost
Direct 0 0
Direct 0 0
BGP 255 0
PrefRcv Up/Down State
1 00:00:34 Established
NextHop Interface
10.1.1.1 Eth1/0
127.0.0.1 InLoop0
10.1.1.2 Eth1/0