Loading...
Loading...
As a result of a known issue TMM may crash in some specific scenarios if there is an overlapping and more specific route to the floating self-IP range configured on the unit.
Traffic disrupted while tmm restarts.
- Unit configured with a floating self-IP and allow-service != none. - More specific route exists via GW to the self-IP. - Configured gateway for the overlapping route is unreachable. - Ingress traffic to the floating self-IP.
Avoid the use of routes overlapping with configured floating self-IPs.
TMM no longer crashes when floating self IPs are configured with more specific overlapping routes.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.