Unable to discover route domains for F5 BIG-IP Load Balancer Discovery

skp
Tera Expert
Hi guys,
 
I am working on Normal Discovery and I need to discover F5 LB/WAF devices. I have the SNMP Community credentials and Basic Authentication properly configured, validates and tested in ServiceNow.
 
I was given a specific IP to discover and the F5 device was successfully discovered and a CI was created in table F5 BIG-IP "cmdb_ci_lb_bigip". In addition to this record 'CI IPs' and 'Network Adapters' data should also be discovered and right now the list in ServiceNow is incomplete. I received the list of 'CI IPs' that should be discovered but they have the % sign appended to them and the customer said that they are F5 specific (route domains for network traffic isolation). Please check the screenshot.
 
You can see in the screenshot that the last 4 IPs have the % sign appended to them and they haven't been discovered by ServiceNow. The first 4 IPs without the % sign have been successfully discovered. The customer insists that we should discover all IPs but I am not sure if' this is possible.
 
Have you encountered anything like this before and can you help me discover the route domains if this is possible?
 
I tried to debug the "F5 Load Balancer SNMP Discovery" pattern and step "Get IPv4 Table" returns those IPs without the % sign, the step "Get IPv6 Table" does not return anything.
 
I also attached a screenshot of all "CI IPs" that I need to discover and you can see the % sign at the end of the IPs.
 
Do you know if ServiceNow OOTB Discovery is capable of discovering the route domains and if not can you help me modify the pattern to discover those "special" IPs?
 
List if CI IPs and Route Domains that we need to discover
skp_1-1695888750739.png

 

 
 
skp_0-1695888005404.png

 

1 REPLY 1

Niklas Peterson
Mega Sage
Mega Sage

Hi,

Route Domains are routes to isolated networks behind the Load Balancer. Mening the same network, like 10.0.0.3 can exist multiple times. In the F5 these networks are given an ID so that they can be separated. The ID is what you see after the %. So you could have 10.0.0.3%1 and 10.0.0.3%2 pointing to 2 different networks and the Load Balancer is able to send traffic to the right network. This is a Load Balancer functionality.

 

Are you looking to discover devices within those isolated networks? Then I would say you need a MID server in each network.

 

Regards,
Niklas