Business service map displays a wrong load balancer in Service Mapping - Support and Troubleshooting

Business service map displays a wrong load balancer in Service Mapping Description  Symptoms The business service map shows a different load balancer from the one expected to see in the selected business service.

Cause A load balancer may not be in operational status, or it was not configured for redundancy and its mode was left as non-operational.

Horizontal discovery sets the operational status of a load balancer using an SNMP query. Many deployments use load balancers as redundant pairs (active/passive). In this scenario, load balancers are configured identically, where one is operational and the other is a failover. The failover load balancer becomes operational when its counterpart goes down. In some cases, horizontal discovery does not retrieve the correct operational status value, causing the Service Mapping to not initiate discovery on the load balancer.

Resolution Verify that the information retrieved by horizontal discovery is accurate by navigating to Discovery Definition > Probes . Search the table for the relevant load balancer probe, for example, SNMP - F5 BIG-IP – System. Click the the SNMP Fields tab. Verify that there are two failover fields (failover1, failover2), and reconfigure if required. If the load balancer is configured as non-operational, change the status to operational: Key = sa.active_operational_status Value = 1,2