A:SRC_R1>config>service>vprn# info
----------------------------------------------
router-id 10.10.10.1
route-distinguisher 65100:10
auto-bind ldp
vrf-target target:65100:10
interface "r5" create
address 30.1.1.1/24
sap 1/1/4 create
exit
exit
rip
group "tor5"
neighbor "r5"
export "bgptorip"
exit
exit
exit
no shutdown
----------------------------------------------
Policy is required to export MPBGP routes received from the remote end to the CE routers:-
A:SRC_R1>config>router>policy-options# info
----------------------------------------------
policy-statement "bgptorip"
entry 10
from
protocol bgp-vpn
exit
to
protocol rip
exit
action accept
exit
exit
exit
----------------------------------------------
On the CE if the direct routes needs to be advertised then a policy is required on the CE also:-
ie from protocol direct
to rip
A:SRC_R2>config>router>ospf# show router 1 route-table
===============================================================================
Route Table (Service: 1)
===============================================================================
Dest Prefix Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
10.10.10.5/32 Remote BGP VPN 00h47m48s 170
10.10.10.1 (tunneled) 0
10.10.10.6/32 Remote RIP 00h52m41s 100
35.1.1.2 2
30.1.1.0/24 Remote BGP VPN 01h31m55s 170
10.10.10.1 (tunneled) 0
35.1.1.0/24 Local Local 01h32m53s 0
r6 0
-------------------------------------------------------------------------------
No. of Routes: 4
===============================================================================
VPRN Ping:-
A:SRC_R1>config>service>vprn# oam vprn-trace 1 source 30.1.1.1 destination 35.1.1.2
TTL Seq Rcvd-on Reply-Path RTT
----------------------------------------------------------------------------
[Send request TTL: 1, Seq. 1.]
1 1 cpm In-Band 0.474ms
Node-Id 10.10.10.2
Requestor 10.10.10.1
Route: 35.1.1.0/24
Vpn Label: 131070 Metrics 0 Pref 170 Owner bgpVpn
Next Hops: [1] ldp tunnel
Route Targets: [1]: target:65100:10
Responder 10.10.10.2
Route: 35.1.1.0/24
Vpn Label: 0 Metrics 0 Pref 0 Owner local
Next Hops: [1] ifIdx 2 nextHopIp 35.1.1.2
[Send request TTL: 2, Seq. 1.]
2 1 sap:1/1/4 In-Band 1.47ms
Node-Id 10.10.10.2
Requestor 10.10.10.1
Route: 35.1.1.0/24
Vpn Label: 131070 Metrics 0 Pref 170 Owner bgpVpn
Next Hops: [1] ldp tunnel
Route Targets: [1]: target:65100:10
Responder 10.10.10.2
Route: 35.1.1.0/24
Vpn Label: 0 Metrics 0 Pref 0 Owner local
Next Hops: [1] ifIdx 2 nextHopIp 35.1.1.2
----------------------------------------------------------------------------
VPRN Ping:-
*A:SRC_R1# ping 35.1.1.1 router 1
PING 35.1.1.1 56 data bytes
64 bytes from 35.1.1.1: icmp_seq=1 ttl=64 time=0.905ms.
64 bytes from 35.1.1.1: icmp_seq=2 ttl=64 time=1.59ms.
64 bytes from 35.1.1.1: icmp_seq=3 ttl=64 time=1.57ms.
64 bytes from 35.1.1.1: icmp_seq=4 ttl=64 time=0.833ms.
64 bytes from 35.1.1.1: icmp_seq=5 ttl=64 time=1.47ms.
---- 35.1.1.1 PING Statistics ----
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 0.833ms, avg = 1.27ms, max = 1.59ms, stddev = 0.333ms
*A:SRC_R1#
VPRN tracroute:-
*A:SRC_R1# traceroute 35.1.1.1 router 1
traceroute to 35.1.1.1, 30 hops max, 40 byte packets
1 35.1.1.1 (35.1.1.1) 1.12 ms 1.74 ms 1.43 ms
*A
A:SRC_R5# show router route-table
===============================================================================
Route Table (Router: Base)
===============================================================================
Dest Prefix Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
10.10.10.5/32 Local Local 01h37m56s 0
system 0
10.10.10.6/32 Remote RIP 00h24m41s 100
30.1.1.1 2
30.1.1.0/24 Local Local 01h01m25s 0
r1 0
35.1.1.0/24 Remote RIP 01h01m16s 100
30.1.1.1 2
-------------------------------------------------------------------------------
No. of Routes: 4
===============================================================================
*A:SRC_R5#
Normal pings and traceoute can be done from CE1 to CE2 to achieve this purpose.
No comments:
Post a Comment