Last Modified: Feb 15, 2019
See more info
Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 13.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 13.1.1, 220.127.116.11, 18.104.22.168, 22.214.171.124
14.1.0, 126.96.36.199, 12.1.4
Opened: Feb 09, 2018
ZebOS may repeatedly add and delete the routes from protocol daemons. This may cause the protocol daemons to delete and re-advertise the default route.
Route flapping may cause instability in the network, including inability to reach the default network advertised by the BIG-IP.
- Dynamic routing in use - Kernel routes redistributed into a routing protocol - Static route configure in TMOS - Route advertisement enabled on the virtual-address that's the same as the static route
Since the static route will be redistributed in the same way as the virtual-address, there is no need to enable route-advertisement on the VIP virtual-address. Disabling this will resolve the problem. The problem will also be resolved by moving the route from tmsh into ZebOS. - In imish config mode, "ip route <route> <gateway>" - In tmsh, "delete net route <route>"
Configuring a static route in TMOS and enabling route-advertisement on the same virtual-address no longer causes route flapping in ZebOS.