Static routing table does not match across cluster members-f5-all
Indeni will identify when two devices are part of a cluster and alert if their static routing tables are different.
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”.
name: f5-rest-net-interface-route description: Extract configured static routes, and count them to match against routes-limit type: monitoring monitoring_interval: 30 minutes requires: vendor: f5 product: load-balancer rest-api: 'true' comments: static-routing-table: why: | 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. how: | This alert uses the F5 iControl REST API to extract the configured routes for the device. can-with-snmp: true can-with-syslog: false routes-usage: why: | If maximum route entries route has been configured and the limit is reached no more route entries can be added to the system. This alert tracks the number of added routes and warns if the limit is about to, or has been reached. how: | This alert logs into the F5 unit via iControl REST and retrieves the configured routes. can-with-snmp: true can-with-syslog: false steps: - run: type: HTTP command: /mgmt/tm/net/route?$select=network,gw parse: type: JSON file: rest-mgmt-tm-net-route.parser.1.json.yaml
Failed to fetch the data: https://bitbucket.org/indeni/indeni-knowledge/src/master/rules/templatebased/crossvendor/static_routing_table_comparison_vsx.scala