Fri May 26, 2017 7:46 am
Did some more investigation and....this is very different behavior.
Did this on a Cisco, on a Juniper, and on a Mikrotik.
Change on Cisco or Juniper does *NOT* cause the adjacency to bounce. A change on Mikrotik <> Cisco does though, even if I am making the change on the Mikrotik side. So in theory, a change on the 'tik side should not elicit a neighborship teardown on the Cisco. However it does indeed go away, with all possible routing across that interface to go down. Mikrotik <> Mikrotik does not seem to have this problem.
This is highly problematic though as it does not follow standard behavior that Cisco and Juniper do when changing metrics. Not just Cisco and Juniper either, but Brocade and Force10 don't seem to do this as well.
I will do more testing and this time with traffic. I want to see if this causes packet loss. If it does then this is *very* bad. Metric changes should not cause adjacency bounces.