[afnog] Cisco MPLS VPNV4 issue

[Meftah Tayeb]

mark,
ok, awesome!
[admin at MikroTik] /routing bgp vpnv4-route> print detail
Flags: L - label-present
 0 L route-distinguisher=1:1 dst-address=10.216.0.1/32 gateway=10.10.10.3
interface=lan1 in-label=21 out-label=21 bgp-local-pref=100 bgp-med=0
bgp-origin=incomplete bgp-ext-communities="RT:1:1"
 1 L route-distinguisher=1:1 dst-address=41.221.20.8/30 interface=ctibridge
in-label=20 bgp-ext-communities="RT:1:1"
[admin at MikroTik] /routing bgp vpnv4-route>
Pe-2851#show ip bgp vpnv4 all
BGP table version is 8, local router ID is 10.10.10.3
Status codes: s suppressed, d damped, h history, * valid, > best, i - 
internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 1:1 (default for vrf inet)
*> 10.216.0.1/32    0.0.0.0                  0         32768 ?
*>i41.221.20.8/30   10.10.10.2                    100      0 ?
Pe-2851#
so, i see that the VPNV4 is up now!
how can i ping from Pe1 to Pe2 ?
like from cisco to Mikrotik ?
i can't specify the loopback address on the cisco, due to this:
ping 41.221.20.9 source 10.216.0.1
% Invalid source address- IP address not on any of our up interfaces
the 10.216.0.1 is a loopback participating on that vrf.
thank you
----- Original Message ----- 
From: "Mark Tinka" <mark.tinka at seacom.mu>
To: "Meftah Tayeb" <tayeb.meftah at gmail.com>
Cc: <afnog at afnog.org>
Sent: Tuesday, May 22, 2012 11:27 PM
Subject: Re: [afnog] Cisco MPLS VPNV4 issue


> On Monday, May 21, 2012 08:34:37 PM Meftah Tayeb wrote:
>
>> so, i do the pe-pe routing directly using bgp, through
>> the P?
>
> Yes, the MP-iBGP session will run directly (or via a route
> reflector) between the PE routers. The P router doesn't need
> to know about BGP in an MPLS network, only the IGP and MPLS.
>
> Once l3vpn (VPNv4) routes are exchanged between the PE
> routers, forwarding of the l3vpn traffic between them via
> the P router will be handled by MPLS.
>
>> and the vrf would flow using bgp?
>
> The VRF is just a routing instance attached to an interface
> that defines where the incoming VPN traffic should go, on
> the PE routers.
>
> Yes, VRF information is advertised using BGP (in this case,
> the RD and RT associated with the VPN).
>
>> so the P will only take the PE2851 to the RB493G?
>
> That's right. All the P router needs is an IGP and MPLS
> capabilities. It is service-unaware, and simply forwards
> MPLS traffic regardless of the payload.
>
> Mark.
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus 
> signature database 6830 (20120126) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
> 


__________ Information from ESET NOD32 Antivirus, version of virus signature database 6830 (20120126) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com