Example For Configuring Mpls L3Vpns Using A Gre Tunnel - 3Com MSR 50 Series Configuration Manual

1508 C 79: MPLS L3VPN C
HAPTER
Example for Configuring
MPLS L3VPNs Using a
GRE Tunnel
ONFIGURATION
Routing Tables: vpn2
Destinations : 3
Destination/Mask Proto
10.2.1.0/24 Direct 0
10.2.1.2/32 Direct 0
10.4.1.0/24 BGP
CEs of the same VPN should be capable of pinging each other, whereas those of
different VPNs should not. For example, CE 1 should be capable of pinging CE 3
(10.3.1.1), but should not be capable of pinging CE 4 (10.4.1.1):
[CE1] ping 10.3.1.1
PING 10.3.1.1: 56
Reply from 10.3.1.1: bytes=56 Sequence=1 ttl=253 time=72 ms
Reply from 10.3.1.1: bytes=56 Sequence=2 ttl=253 time=34 ms
Reply from 10.3.1.1: bytes=56 Sequence=3 ttl=253 time=50 ms
Reply from 10.3.1.1: bytes=56 Sequence=4 ttl=253 time=50 ms
Reply from 10.3.1.1: bytes=56 Sequence=5 ttl=253 time=34 ms
--- 10.3.1.1 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 34/48/72 ms
[CE1] ping 10.4.1.1
PING 10.4.1.1: 56
Request time out
Request time out
Request time out
Request time out
Request time out
--- 10.4.1.1 ping statistics ---
5 packet(s) transmitted
0 packet(s) received
100.00% packet loss
Network requirements
CE 1 and CE 2 belong to VPN 1. On the service provider backbone, the PEs
■
support MPLS, while the P device does not support MPLS and provides pure IP
functions.
On the backbone, a GRE tunnel is used to encapsulate and forward VPN
■
packets to implement MPLS L3VPN.
This networking scheme requires that tunneling policies be configured on the PEs
and the tunnel type for VPN traffic be specified as GRE.
Routes : 3
Pre Cost
0
0
255 0
data bytes, press CTRL_C to break
data bytes, press CTRL_C to break
NextHop Interface
10.2.1.2 Eth1/1
127.0.0.1 InLoop0
3.3.3.9 NULL0