Relationship cmdb_ci_lb_service and cmdb_ci_lb_pool not created by discovery

[lucaslopesm]

Hello Guys, 

We are currently implementing discovery over our BIG IP f5 nodes and I noticed that the relationship between cmdb_ci_lb_service and cmdb_ci_lb_pool isn't created by default. 

This way I can't relate a pool IP adress (which is stored in the cmdb_ci_lb_service) with the corresponding nodes and therefore servicemapping isn't useful showing the dependency of the nodes for applications that are balanced using f5

We are using SS\H

[pr8172510]

Hi @lucaslopesm,

By default, ServiceNow Discovery creates only the relationships defined in the F5 BIG-IP Discovery Pattern.

If the relationship between cmdb_ci_lb_service and cmdb_ci_lb_pool is not being created, it is likely because the OOTB pattern does not populate that relationship.

 check

• Verify you're using the latest F5 BIG-IP Discovery Pattern and Pattern Library version.
• Run Pattern Debug to confirm that pools, pool members, and virtual servers are being discovered successfully.
• Ensure the SSH account has sufficient permissions to retrieve the F5 configuration.
• Review Discovery Pattern Logs to see whether relationship creation is skipped or if data is missing.
• If the required relationship is not created by the OOTB pattern, you will need to extend the Discovery Pattern (or use a post-processing pattern/script) to create the cmdb_ci_lb_service ↔ cmdb_ci_lb_pool relationship.

CI relationships are created only when the discovery pattern explicitly identifies and maps them. Service Mapping relies on these discovered relationships and does not infer missing dependencies automatically.

[SK Chand Basha]

Hi @lucaslopesm 

Can you please verify in related BIG IP f5 Load Balancer patterns in that you have step to create a relation/reference step?