Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I couple of times I neglect to see that a physical interface is part of a port channel while adding a "vlan allowed" to a trunk interface. This causes the interface to go down into suspend mode after a few seconds, as the "vlan allowed" command needs...
So I get this BGP log message ie: (%BGP-4-vpnv4NH_IF:next-hop x.x.x.x may not be reachable from neighbor x.x.x.x - not a loopback.) on XE 17.9.5a, (the rest of network is 17.9.4a)Its MPLSoDMVPN, and all the iBGP peers on this DMVPN are the interface ...
How would I go about making that suggestion to the Cisco Team as a feature enhancement? As I also would suggest having more than a 10 command "history" in IOS as well.
MHM, This is true, ie: not using mpls core. Also, RR and next-hop-self are both employed. Network has been operational several months with now real big issues or problems, just the message, and I'll look to use Loopbacks per your recommendation. Than...
Thanks very much, there is actually an L3 encryptor pair in the middle of the Hub and Spoke. Thanks for the recommendation, I think all is good, I'll look to using Loopbacks and get rid of the message. Thanks, Again
MHM,Thanks, yes it appears all traffic flows well, it's a production network for 10s of thousands of users, and I'm not aware of any problems. Traffic must traverse Hubs, as it is Phase 1 I guess, each spoke has only two DMVPN connections, ie: one to...
Everything works, to the best of my knowledge, it's just that I receive this log message on the one device running 17.9.5a code, the other devices do not get this log message, and they are running 17.9.4a. The topology is DMVPN with DUAL Hubs and Spo...