[c-nsp] IPv6 Deployment / 6PE

[Aaron]

Ah , interesting. with that said, you sort of make me believe that there is
a way to convert 6pe to 6vpe by config'ing send-label

 

Aaron

 

 

From: Ahmed Hilmy [mailto:hilmy.aa at gmail.com] 
Sent: Monday, June 24, 2013 1:47 PM
To: Aaron
Cc: Mikael Abrahamsson; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] IPv6 Deployment / 6PE

 

I think in 6vpe u dont need send-label because u already establish vpnv6
family.

in 6pe we need send-label because we establish ipv6 family.

This is what i have understood !!! 

 

 

On Mon, Jun 24, 2013 at 9:36 PM, Aaron <aaron1 at gvtc.com> wrote:

What if I do 6vpe and don't use the "send-lable" ?  what happens ?

 

Aaron

 

From: Ahmed Hilmy [mailto:hilmy.aa at gmail.com] 
Sent: Monday, June 24, 2013 1:05 PM
To: Aaron
Cc: Mikael Abrahamsson; cisco-nsp at puck.nether.net


Subject: Re: [c-nsp] IPv6 Deployment / 6PE

 

Hello Aaron,

 

Thanks for sharing info.

Regarding to send-lable command, Cisco call it a magic command, to make PE
router to advertise IPv6 prefix as a label.

I am working on 6PE deployment.

- PEs & IGW ----- MPBGP ----- RR

- add adress-family ipv6 at PEs & RR ( active & send-label )

It will work 

 

On Mon, Jun 24, 2013 at 5:27 PM, Aaron <aaron1 at gvtc.com> wrote:

(I'm looking at my ios xr asr9k doing this and sending notes about how I did
it, I didn't do the rr yet, but I understand this is how it's done on rr
too)

IGW....

- Vrf defined...enable ipv6 address family on this vrf...
- Add internet interface to this vrf...
- add ipv6 address to this internet interface
- under bgp, under vrf, enable the appropriate ipv6 native type stuff for
bgp neighboring, etc (JUST LIKE V4)...but I have no idea why you need
send-label.
- enable mpls on connection towards your internal mpls cloud (toward your
rr) ...for 6vpe only v4 is needed on your internal net
- on the internal side, enable mpibgp with address-family vpnv6 unicast from
the igw to the rr on both sides and of course from rr to other internal pe's

RR....
- I think the vpvn6 af for that mpibgp session towards igw and other
internal pe's is all that is required on rr in order to support 6vpe

other internal pe's...

- Vrf defined...enable ipv6 address family on this vrf...
- Add customer facing interface to this vrf...
- add ipv6 address to this customer facing interface
- under bgp, under vrf, enable the appropriate ipv6 native type stuff for
customer facing pe-ce routing...but I have no idea why you need send-label.
- enable mpls on connection towards your internal mpls cloud (toward your
rr) ...for 6vpe only v4 is needed on your internal net
- on the internal side, enable mpibgp with address-family vpnv6 unicast from
the igw to the rr on both sides and of course from rr to other internal pe's


Aaron




-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
Ahmed Hilmy
Sent: Saturday, June 22, 2013 5:00 AM
To: Mikael Abrahamsson
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] IPv6 Deployment / 6PE

 But i dont have MP-BGP between IGW & RR, I have pure BGP IPv4.
So ?


On Sat, Jun 22, 2013 at 12:05 PM, Mikael Abrahamsson
<swmike at swm.pp.se>wrote:

> On Sat, 22 Jun 2013, Ahmed Hilmy wrote:
>
>  Can i add address family IPv6 at IGW to advertise IPv6 routes to RR,
>> since it is directly connected ?
>>
>
> Sure. I would configure send-label there as well so that you do thing
> in a consistent manner, but that's a matter of opinion.
>
>
> --
> Mikael Abrahamsson    email: swmike at swm.pp.se
>

_______________________________________________
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/