[c-nsp] IPv6 Transition - IP/MPLS Backbone
Luis Anzola
anzolex at gmail.com
Tue May 21 22:00:50 EDT 2013
Hi Guys,
It's important to keep in mind what type of IPv6 service will be transported over the MPLS domain, whether it is a Corporate L3VPN Service or an Internet Access since there is some overhead on the 6VPE implementation that should be considered when carrying all Internet routes, e.g. it's important to understand how the memory is used on the routers if you are running a full-bgp table at the PEs on a BGP-free Core model, considering the labels and RD.
- 192bits Address (24 Byte) including the 64 bits route distinguisher (8 Bytes) and the 128 bits IPv6 address (16 Bytes) <RD:IPv6
Best regards,
Luis
On May 19, 2013, at 4:48 PM, Ahmed Hilmy <hilmy.aa at gmail.com> wrote:
> Hello Aaron,
>
> I hope you are doing great.
> I am working on IPv6 deployment.
> i am trying to configure my PE as a dual-stack toward CE, i have already
> establish EBGPv4 session with my customer.both PE end CE are dual-stack
> I have set ipv4 and ipv6 address on the interface( directly connected to CE
> ).
> i enabled ipv6 unicast-routing
> i enabled mls ipv6 vrf
> I enabled vrf and upgrade to vrf-cli
>
> i have tried with 6PE and 6VPE but i was failed.
> So, here are my questions:
>
> 1- if PE and CE are dual-stack, so i have to use 6VPE, right ? at CE side
> what is the required configuration ?
> 2- IOS version is 12.2(33) SRD3 - 7606- SUP720 , is it supported for
> Dual-Stack ?
> 3- at PE toward CE, shall i configure address-family ipv6 or vpn ipv6 or
> ipv6 vrf ? at CE only ipv6 ?
> 4- my Topology is like this CE-------PE-----IGW .....Would you please guide
> me in that ..
> =====================================
> At PE:
> ===============================
> vrf definition IPv6
> rd 6500:1
> !
> address-family ipv4
> route-target export 6500:1
> route-target import 6500:1
> exit-address-family
> !
> address-family ipv6
> route-target export 6500:1
> route-target import 6500:1
> exit-address-family
> =========================
> interface GigabitEthernet1/18
> description IPv6-test
> vrf forwarding IPv6
> ip address 10.10.10.1 255.255.255.0
>
> ipv6 address 2A03:4700::FFFF:0:1/64
> ==================================
> router bgp 6501
> neighbor 10.10.10.2 remote-as 6500
> neighbor 10.10.10.2 update-source GigabitEthernet1/18
> neighbor 2A03:4700::FFFF:0:2 remote-as 6500
> neighbor 2A03:4700::FFFF:0:2 update-source GigabitEthernet1/18
> address-family ipv4 vrf IPv6
> no synchronization
> neighbor 10.10.10.2 remote-as 6500
> neighbor 10.10.10.2 activate
> exit-address-family
> !
> address-family ipv6 vrf IPv6
> no synchronization
> neighbor 2A03:4700::FFFF:0:2 remote-as 6500
> neighbor 2A03:4700::FFFF:0:2 activate
> exit-address-family
> ==============
>
>
>
> Thanks
>
>
> On Tue, Apr 16, 2013 at 9:58 PM, Aaron <aaron1 at gvtc.com> wrote:
>
>> It was in my live network, later I removed it for preferring L3VPN vice
>> L2VPN…****
>>
>> ** **
>>
>> I think on the route reflector the thing(s) you need to do is add vpnv6 to
>> global bgp and to the neighbor session….neighbor session will bounce when
>> you activate another address family to a pre-existing neighbor….it’s quick
>> as I recall, loose a couple pings and that’s it****
>>
>> ** **
>>
>> Aaron****
>>
>> ** **
>>
>> *From:* Ahmed Hilmy [mailto:hilmy.aa at gmail.com]
>> *Sent:* Tuesday, April 16, 2013 1:47 PM
>> *To:* Aaron
>> *Cc:* Harold 'Buz' Dale; cisco-nsp at puck.nether.net; aaron.gould at gvtc.net
>>
>> *Subject:* Re: [c-nsp] IPv6 Transition - IP/MPLS Backbone****
>>
>> ** **
>>
>> Hello Aaron,****
>>
>> ** **
>>
>> That is great and so happy to hear that, is it real deployment at your
>> live network ?****
>>
>> MP-BGP between PE- Route Reflector, shall i modify it to allow IPv6 packet
>> to carry ? or only at PE to work as dual stack ?****
>>
>> ** **
>>
>> ** **
>>
>> ** **
>>
>> On Tue, Apr 16, 2013 at 12:19 AM, Aaron <aaron1 at gvtc.com> wrote:****
>>
>>
>> Sounds like a good use for 6VPE...as I understand it, I've had to do the
>> following in my network to get 6vpe working...
>>
>> - enable local vrf ipv6 data structure which may include you upgrading the
>> vrf cli to the vrf definition to support ipv6
>> - enable/activate vpnv6 neighbors within the MP-iBGP core...PE bgp
>> neighbors
>> or PE to Route Refelctor(s)
>> - enable the ipv6 vrf within bgp
>> - enable the pe-ce routing to be ipv6 capable
>> - enable the ipv6 protocol stack in the interfaces facing CE
>>
>> ...i had to do nothing ipv6-related to my mpls/igp core routing
>> environment.
>> Nothing. I think that's nice thing about 6vpe is that providers don't have
>> to do anything to the core in order to enable ipv6 over pre-existing ipv4
>> (vpvn4) mpls l3vpn's...
>>
>> When you are done, a traceroute from a client transiting the 6vpe mpls
>> l3vpn
>> will look like this... notice hops 2 and 3....i think they are ipv6
>> compatible ipv6 addresses (but unsure about what they are called)...anyway,
>> it shows the loopback router id of the mpls transit hop via the 6vpe (the
>> mpls l3vpn that is ipv6 enabled)
>>
>> C:\>tracert -d www.cisco.com
>>
>> Tracing route to e144.dscb.akamaiedge.net [2600:1404:8:1:9200::90]
>> over a maximum of 30 hops:
>>
>> 1 <1 ms <1 ms <1 ms 1234:5678:1111::1
>> 2 1 ms 1 ms <1 ms ::ffff:12.34.0.3
>> 3 1 ms 1 ms <1 ms ::ffff:123.123108.3
>> 4 1 ms <1 ms <1 ms 2468:1234:0:8::f:8001
>> 5 <1 ms <1 ms <1 ms 2468:1234:0:8::f:8000
>> 6 11 ms 7 ms 7 ms 2468:1234:0:4::f:bb56
>> 7 9 ms 7 ms 7 ms 2468:1234:0:4::3:0
>> 8 15 ms 15 ms 15 ms 2468:1234:0:4::22
>> 9 10 ms 15 ms 15 ms 1369:2468:0:8::e
>> 10 8 ms 8 ms 8 ms 1369:2468:0:4::83
>> 11 9 ms 8 ms 8 ms 2610:18:10e::45
>> 12 77 ms * 104 ms 2610:18:17:3000::2e
>> 13 32 ms 32 ms 32 ms 2400:8800:7f04:6::2
>> 14 32 ms 32 ms 32 ms 2600:1404:8:1:9200::90
>>
>> Trace complete.
>>
>> C:\>
>>
>>
>> Aaron****
>>
>>
>> -----Original Message-----
>> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
>> Ahmed Hilmy****
>>
>> Sent: Monday, April 15, 2013 2:28 PM
>> To: Harold 'Buz' Dale
>> Cc: cisco-nsp at puck.nether.net
>> Subject: Re: [c-nsp] IPv6 Transition - IP/MPLS Backbone
>>
>> I have IPv4/ MPLS Backbone, i want to deploy IPv6 by using exist Backbone.
>> Yes, dual stack at PE only which it is facing to CE, but PE will face my
>> core as IPv4.
>> Please let me know if it is not clear yet ?
>>
>> Regards,
>> Ahmed
>>
>>
>> On Mon, Apr 15, 2013 at 8:00 PM, Harold 'Buz' Dale <buz.dale at usg.edu>
>> wrote:
>>
>>> Are you planning on providing native v6 via dual stack at the edges
>>> and then using 6PE to traverse your core? Maybe I am a little slow but
>>> it isn't clear to me exactly what you are trying to do.
>>> Thanks,
>>> Buz
>>>
>>> -----Original Message-----
>>> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf
>>> Of Ahmed Hilmy
>>> Sent: Sunday, April 14, 2013 15:56
>>> To: cisco-nsp at puck.nether.net
>>> Subject: [c-nsp] IPv6 Transition - IP/MPLS Backbone
>>>
>>> Hello Expert,
>>>
>>> We are planning to deploy IPv6 at our IPv4 Backbone, our PE to as Dual
>>> Stack and carry IPv6 packet through MPLS label.
>>> There are different scenarios, one of them is 6PE.
>>> Would you please guide me from where can i start ?
>>>
>>> Thanks,
>>>
>>> Ahmed
>>> _______________________________________________
>>> 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/****
>>
>> ** **
> _______________________________________________
> 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/
More information about the cisco-nsp
mailing list