Static routing table does not match across cluster members for Radware




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 Radware API to extract the configured routes for the device by running /config/IpCurCfgStaticRouteTable.

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 and run a CLI command or view the static routes over the GUI. However, they would have to manually compare the routing tables of each device to ensure that the cluster does not have any mismatches.

View Source Code