- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
BGP Routing Disabled
I've looking into this for a while now, and seen it a few places..
Eventhough BGP routing is disabled, any idea on why my Hub MX in concentrator mode, keeps insisting on negotiating BGP, even though it is disabled on the Routing page?
Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂
All code examples are provided as is. Responsibility for Code execution lies solely your own.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ipv6 , guessing you are running MX17++ ?
If you take a packet capture , do you see the tcp syns being sent ? I would open a case with that pcap and ask support what is going on.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
MX18.107.2 actually, but yeah.. Guess I'll have to ask support..
Oddly enogh I don't have any IPv6 prefixes configured. Also the IPv6 settings in the uplink is set to Auto(Stateless), with the MX not getting anything assigned. To my knowledge, there's noting upstream that does IPv6.
Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂
All code examples are provided as is. Responsibility for Code execution lies solely your own.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is a known issue that occurred at some point in MX17.X - not entirely sure which version, we jumped from 15.X to 17.X a few months ago and this started spamming our syslog. I opened a case with support, and to quote:
"We do not yet have a full fix for this in versions of MX firmware that have support for IPv6 (namely 17 and above) but version 16 does not have this issue."
The last update to that case was in February, haven't heard anything since.
