Static routing table does not match across cluster members for F5

Vendor

F5

Description

Indeni will identify when two devices are part of a cluster and alert if their static routing tables are different.

Remediation Steps

Ensure the static routing table matches across devices in a cluster.

How does this work?

This alert uses the F5 iControl REST API to extract the configured routes for the device.

Why is this important?

It is important that the routing is configured the same for all cluster members of the same cluster. Otherwise there can be downtime in the event of a failover.

Without Indeni how would you find this?

An administrator could log into the device, enter TMSH and run the command "show net route". The routing information is also available via the web interface in "Network" -> "Routes".

View Source Code
single