[rbak-nsp] mBGP / non 6PE / mapped v4 address next-hop

Tomas Lynch tomas.lynch at gmail.com
Fri Jun 22 11:12:12 EDT 2012


On Fri, Jun 22, 2012 at 11:46 AM, Florian Lohoff <f at zz.de> wrote:
> On Fri, Jun 22, 2012 at 04:14:26PM +0200, Olivier Benghozi wrote:
>> Hi,
>>
>> you wrote:
>> > i fail to see how to configure an SE600 with mBGP announcing local routes
>> > (pools) without them resulting in a 6PE announcement - read: ipv4 mapped
>> > address next-hop.
>>
>> >  peer-group IBGP internal
>> >    password encrypted <deleted>
>> >    update-source LOOPBACK0
>> >   address-family ipv4 unicast
>> >   address-family ipv6 unicast
>>
>>
>> You are trying to announce pure IPv6 routes within an IPv4 BGP session, which is not what you want, I guess :)
>> You want 6PE, so you want to exchange labeled IPv6 routes.
>
> Our iBGP is pure IPv4 although it carrys all prefixes - BGP transport should be seperate from the userplane transport.
>
>> On the SE, you must add "send label" under "address-family ipv6 unicast" at the peer-group level.
>
> I DONT want to do 6PE - so why would i want to create labels?

1) Check the redistribution route-maps to see if you are adding the
right prefixes.
2) If you are not doing 6PE than you will need to setup IPv6 sessions
on you BGP apart from the existing ipv4 ones and exchange updates
through those sessions. i.e. neigh 2001::1 internal, etc. etc.

Tomas Lynch

>
>> > The neighbor ASR9k sees the route as:
>>
>> On the Cisco IOSXR, you must use "address-family ipv6 labeled-unicast" for
>> the neighbor/peergroup, and "address-family ipv6 unicast" with
>> "allocate-label all" under in the BGP router global level.
>
> I DONT want 6PE - Our core is dual stacked so i'd do everything native.
>
> Flo
> --
> Florian Lohoff                                                 f at zz.de
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQIVAwUBT+SFQpDdQSDLCfIvAQgpxBAAhF74QhoTJTUKkDRVSqb/oXUKymaqvEED
> PO88PqxrM44nG5xpqHKZWvQY+YjLknxIWLCzOsTvekf/BiSjNCCDjp/6aPxsJQIr
> M58ee5pBs2B4cjdLaf7htxJCu4ZedJtPxsti4yoeHcE4McexsQNkshVZiiBDYt7A
> VZZokVgsG8asLAeNg/KSR16bEMCk43XSrVesy+meOP20h3LzrPkwYE2A2l7lQK95
> OF1hEjYGv12gn9LHlKhaADd5ofBjkln6XRhH6oL3uVHLB57a3fnOfXCdt3VvqL3C
> fisTjf64LJ1MZVK3ZNVrFDaXc3DaMdnbyisPYEqB+MF5ugZEq5F5qPlT+yBLr/jh
> T+ZBgw4eo3iegEhwyiuTPvbE36kfUL3eXXw3oXg6Ulr+BKyT7k7/KHGa1lnHZrvF
> uYC/ZZc4TVE+pspo5nZaLCJE2fFUqQf9cr2QALErgmTUYBvcUHitcoUJh/s7TYDV
> qemE/96Vnct45WrCW69NdLce30I9ogrdGBUixOJuEoodLfFRZIng1Gq7+2uRt7c8
> oq6aIhUgSvFOrFqJ4Ij4GT3LWVyWmXf3w3pqZUFkITIY8h8y7aw3SKkqtElu0JnO
> XwYIfEZg3ZwgkhFbtRpNzNAWnigBWDIqe9u/+LeKlIxEJx81SWLai4dp9HsxzDXn
> 3ujwdANYX+s=
> =jBh0
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> redback-nsp mailing list
> redback-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp
>



More information about the redback-nsp mailing list