[c-nsp] Inter AS MPLS hybrid thingy...

[Christian Meutes]

That's why I suggested to give the L3VPN customer also MPLS on the PE-CE
link. So that just the L3VPN CE needs to have the CsC-customers eBGP nexthop
tag.

It's a while back when I played with CsC, but enabling tagging of just the 
CsC-PE prefix on the BGP session between the Parent_net-PE and the L3VPN-CE,
then enabling MPLS without LDP and create eBGP session through Parent_net
between both customers should do the trick without downtime, not?

On Sep 13, 2012, at 1:06 PM, Oliver Boehmer (oboehmer) <oboehmer at cisco.com> wrote:

> Yes, so I read it as well.. But I guess the question is how Child_net1
> wants to interconnect with a L3VPN (not CsC) customer on Parent_net.. If
> Parent_net just imports the L3VPN customer's Routes into the CsC VRF
> towards Child_net (and vice versa), this would provide connectivity
> between Child_net's global table and the L3VPN customer. But not (and this
> is how I read it) between a Child_net L3VPN customer and the L3VPN
> customer on parent_net..
> So enough speculating, let's wait for JC to clarify the requirements :-)
> 
> 	oli
> 
> On 13/09/2012 12:54, "Christian Meutes" <christian at errxtx.net> wrote:
> 
>> Hey Oli,
>> 
>> I read it as Child_net1 is L3VPN with MPLS enabled (CsC) but I may be
>> wrong...
>> 
>> On 13.09.2012, at 11:53, "Oliver Boehmer (oboehmer)" <oboehmer at cisco.com>
>> wrote:
>> 
>>> Don't think this is going to work Christian. Child_net1's interface to
>>> Parent_net is actually in the global table, so any addresses visible
>>> there
>>> are being treated as global devices in remote parts of Child_net1, not
>>> any
>>> vpnv4/VRF addresses.
>>> JC, you need to setup InterAS-MPLS-VPN (whichever flavor meets your
>>> need,
>>> I guess 10a or 10b would do it) on another link (which could also be a
>>> subinterface of the existing one, of course).
>>> 
>>>   oli
>>> 
>>> On 13/09/2012 11:17, "Christian Meutes" <christian at errxtx.net> wrote:
>>> 
>>>> Import&Export between the RDs and give the L3VPN-only customer also
>>>> MPLS
>>>> and eBGP session between them.
>>>> 
>>>> On 13.09.2012, at 10:44, "JC Cockburn" <ccie15385 at gmail.com> wrote:
>>>> 
>>>>> Hi All,
>>>>> 
>>>>> We have a weird setup/requirement as following and I need some advise
>>>>> please:
>>>>> 
>>>>> 
>>>>> 
>>>>> Working MPLS network serving L3 VPNs (lets call it Parent_net). On
>>>>> this
>>>>> network we have one of the VPN's as CsC serving another "provider"
>>>>> (call it
>>>>> Child_net1).
>>>>> 
>>>>> Now this provider (Child_net1) needs to communicate with another L3VPN
>>>>> also
>>>>> on Parent_net.
>>>>> 
>>>>> Can this be done by some means using the same existing links between
>>>>> Parent_net and Child_net1 (so the CsC links)? Or do we have to create
>>>>> another link/s with ASBR routers between Parent_net and Child_net1?
>>>>> 
>>>>> 
>>>>> 
>>>>> Any experience/tips and/or advise would be appreciated
>>>>> 
>>>>> Ciao & enjoy!
>>>>> 
>>>>> 
>>>>> 
>>>>> JC
>>>>> 
>>>>> _______________________________________________
>>>>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>>>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>> 
>>>> _______________________________________________
>>>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>> 
>