IPv6 BGP network advertisement
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-16-2016 04:03 PM
Hi Experts
Getting error while trying to advertise IPv6 routes in BGP peering. IPv4 works fine, but getting error in IPv6. The below network is preset in IPv6 routing table and shows as being directly connected.
(vr Test) SwitchA # configure bgp add network address-family ipv6-unicast fd01:976a:14fd:e7c0::/68
Error: vr Test: IPv6 network is not valid, must be a global unicast address and not a unique local address
Getting error while trying to advertise IPv6 routes in BGP peering. IPv4 works fine, but getting error in IPv6. The below network is preset in IPv6 routing table and shows as being directly connected.
(vr Test) SwitchA # configure bgp add network address-family ipv6-unicast fd01:976a:14fd:e7c0::/68
Error: vr Test: IPv6 network is not valid, must be a global unicast address and not a unique local address
9 REPLIES 9
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-18-2016 10:35 AM
Hi Sumanta, we are in touch with our engineering team regarding this topic and will update this thread as soon as we have more details.
We know (based on the RFC) that there are some restrictions when exchanging ULA prefixed between sites. However, since we are talking about iBGP, my guess is that it should work.
We know (based on the RFC) that there are some restrictions when exchanging ULA prefixed between sites. However, since we are talking about iBGP, my guess is that it should work.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-18-2016 07:17 AM
Hi Ed
So is this default behavior as per RFC? Extreme doesn't allow LUA to be used in BGP advertisement, even if it's within internal network (not globally routable) ?
So is this default behavior as per RFC? Extreme doesn't allow LUA to be used in BGP advertisement, even if it's within internal network (not globally routable) ?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-17-2016 06:42 AM
This is clearly stated in RFC4193:
The default behavior of exterior routing protocol sessions between administrative routing regions must be to ignore receipt of and not advertise prefixes in the FC00::/7 block. A network operator may specifically configure prefixes longer than FC00::/7 for inter-site communication.
If BGP is being used at the site border with an ISP, the default BGP configuration must filter out any Local IPv6 address prefixes, both incoming and outgoing. It must be set both to keep any Local IPv6 address prefixes from being advertised outside of the site as well as to keep these prefixes from being learned from another site. The exception to this is if there are specific /48 or longer routes created for one or more Local IPv6 prefixes.
The default behavior of exterior routing protocol sessions between administrative routing regions must be to ignore receipt of and not advertise prefixes in the FC00::/7 block. A network operator may specifically configure prefixes longer than FC00::/7 for inter-site communication.
If BGP is being used at the site border with an ISP, the default BGP configuration must filter out any Local IPv6 address prefixes, both incoming and outgoing. It must be set both to keep any Local IPv6 address prefixes from being advertised outside of the site as well as to keep these prefixes from being learned from another site. The exception to this is if there are specific /48 or longer routes created for one or more Local IPv6 prefixes.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-16-2016 06:41 PM
what version of EXOS are you running, btw?
