Load balancer services being set to absent

[johanalande]

Hi,

Since about a month ago we have an issue with some of the Load balancer services being set to Status=Absent.

This happens to load balancer services (cmdb_ci_lb_service) that have not been discovered, which means to me that CI deletion strategy should not apply. (I thought.)

Have been reading up on deletion strategy (https://www.servicenow.com/docs/bundle/xanadu-it-operations-management/page/product/discovery/concep...) and thought that it raises some questions (example;
Discovery puts an entry into the Related CI Types [sa_ci_to_pattern] table for each relation between the main CI a related CI type;
Nope nothing is put there by Discovery.)

I think my Deletion strategy is OOTB.

I have another suspect: Update Entry Point Candidates (BR on cmdb_ci_lb_service/ on inserts or updates). But can't really prove that either.

So basically I have
- some Load balancer services that are retired (no more Discovery) => set to Absent

- some Load balancer services that are retired (no more Discovery) => not affected
- some Load balancer services that are retired (never Discovered) => set to Absent

- some Load balancer services that are retired (never Discovered) => not affected

Version: Washington Patch 8
Anyone else has this? What is the process behind this behaviour and how is that process supposed to work? What tables are used?

Thanks, /Johan

[johanalande · Accepted solution]

We have now solved the issue internally. By setting the field "Load Balancer" (in cmdb_ci_lb_service) the status is no longer updated to Absent. This was needed only for the records being updated to Absent (about 30 out of 2500 active ones), and only setting this field made a difference, independently on the relation. What got me on track was that the Discovery time and Absent-time differed slighty.

We hade a case with the support and after a while the clearified how the Deletions strategy works, so it is using the payload (sa_payload_snapshot) for make a comparison between previous Discovery and current Discovery (the payload is being used).

BR, /Johan

[SupriyaR4553017]

Hi @johanalande i have the similar issue but problem is when i am trying to add load balancer in the load balancer service page (cmdb_ci_lb_service), it just wont come up in the list. But if i check separately on page cmdb_ci_lb there i see two entries , one with install status as Installed and other with status as retired. Not sure why its happening this way.

Can you suggest

[johanalande]

Check the class of the LB Hardware that you see/cannot see. Make sure you connect LB services and hardware of the same "type". For LB services based on F5, I can only add LB hardware based on F5 (F5 BIG IP is the table).