Neighbor adjacency flaps at the same time on all routers
Posted: Sat Sep 22, 2018 6:33 pm
Hello,
I've been using EVE the community edition for a while now. I have it deployed on my windows laptop and on my windows desktop running vmware workstation. I've noticed since I upgraded to 2.0.3-92 that all neighbor adjacencies bounce at the same time in a large topology. This happens with directly connected routers and with switches in between. This is across the board with EIGRP, OSPF, and LDP. BGP is stable but I believe that is because of it using TCP. The adjacency is down for milliseconds, but it's just annoying because I can't tell if it's my configuration or if it's EVE. This happens to all routers running the dynamic protocol at the same time in the topology.
The weird thing is, on my laptop I experience no such issues and that is also running 2.0.3-92. Here's the hardware differences between my desktop and laptop.
Laptop:
VMware workstation 12 Player
i7 4 core
16GBs of RAM
Desktop
VMware workstation 12 pro
AMD FX 8 core
24GBs of RAM
I adjusted the dead timer intervals to 90 seconds and the issue still persists. From my perspective, pre 2.0.3-92 this issue didn't exist. So is there anything that changed between the version pre 2.0.3-92 that could cause this? Let me know if there is more information I can get to help narrow this down.
Thanks
I've been using EVE the community edition for a while now. I have it deployed on my windows laptop and on my windows desktop running vmware workstation. I've noticed since I upgraded to 2.0.3-92 that all neighbor adjacencies bounce at the same time in a large topology. This happens with directly connected routers and with switches in between. This is across the board with EIGRP, OSPF, and LDP. BGP is stable but I believe that is because of it using TCP. The adjacency is down for milliseconds, but it's just annoying because I can't tell if it's my configuration or if it's EVE. This happens to all routers running the dynamic protocol at the same time in the topology.
The weird thing is, on my laptop I experience no such issues and that is also running 2.0.3-92. Here's the hardware differences between my desktop and laptop.
Laptop:
VMware workstation 12 Player
i7 4 core
16GBs of RAM
Desktop
VMware workstation 12 pro
AMD FX 8 core
24GBs of RAM
I adjusted the dead timer intervals to 90 seconds and the issue still persists. From my perspective, pre 2.0.3-92 this issue didn't exist. So is there anything that changed between the version pre 2.0.3-92 that could cause this? Let me know if there is more information I can get to help narrow this down.
Thanks