3Com MSR 50 Series Configuration Manual page 1506

1506 C 79: MPLS L3VPN C
HAPTER
n
n
ONFIGURATION
# Configure IP addresses for the CEs as required in
configuration steps are omitted.
After completing the above configurations, you can issue the display ip
vpn-instance command on the PEs to view the configuration of the VPN instance.
The PEs should be capable of pinging their respective CEs. The following takes PE
1 and CE 1 as an example:
[PE1] display ip vpn-instance
Total VPN-Instances configured : 2
VPN-Instance Name
vpn1
vpn2
[PE1] ping -vpn-instance vpn1 10.1.1.1
PING 10.1.1.1: 56
Reply from 10.1.1.1: bytes=56 Sequence=1 ttl=255 time=56 ms
Reply from 10.1.1.1: bytes=56 Sequence=2 ttl=255 time=4 ms
Reply from 10.1.1.1: bytes=56 Sequence=3 ttl=255 time=4 ms
Reply from 10.1.1.1: bytes=56 Sequence=4 ttl=255 time=52 ms
Reply from 10.1.1.1: bytes=56 Sequence=5 ttl=255 time=3 ms
--- 10.1.1.1 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 3/23/56 ms
4 Establish EBGP peer relationship between PEs and CEs to allow VPN routes to be
injected
# Configure CE 1.
<CE1> system-view
[CE1] bgp 65410
[CE1-bgp] peer 10.1.1.2 as-number 100
[CE1-bgp] import-route direct
[CE1-bgp] quit
The configurations for the other three CEs (CE 2 through CE 4) are similar to the
above. The detailed configuration steps are omitted.
# Configure PE 1.
[PE1] bgp 100
[PE1-bgp] ipv4-family vpn-instance vpn1
[PE1-bgp-vpn1] peer 10.1.1.1 as-number 65410
[PE1-bgp-vpn1] import-route direct
[PE1-bgp-vpn1] quit
[PE1-bgp] ipv4-family vpn-instance vpn2
[PE1-bgp-vpn2] peer 10.2.1.1 as-number 65420
[PE1-bgp-vpn2] import-route direct
[PE1-bgp-vpn2] quit
[PE1-bgp] quit
The configurations for PE 2 are similar to those for P E1. The detailed configuration
steps are omitted.
RD Create Time
100:1 2006/08/13 09:32:45
100:2 2006/08/13 09:42:59
data bytes, press CTRL_C to break
Figure 422. The detailed