ESX server operational status changed by discovery

[thebananek]

I am trying to find out why operational status has been changed by discovery in the following sequence
original state set manually: Operational

next set manually: NonOperational

next set manually: Operational

next set by discovery user: Retired

next set by discovery user: NonOperational

the status remains NonOperational after next discovery.

Any idea is it OOTB behavior or something customized or how to investigate?

[Rahul Priyadars]

So CI update done by Discovery based on Identification Key but for ESX it does not go thru IRE.

During vCenter discovery, the identification process for ESX server doesn’t go through IRE CI identifier, it goes through "VCenterESXHostsSensor" script include where there are 3 identification indexes.

Refer Below KB for more details how its getting Updated as i can see even HOST name is also updated by Discovery.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1123141

Regards

RP

[AJ-TechTrek]

Hi @thebananek ,

The status is set through script include VCenterSensor. This issue is also highlighted in the below post, Might be below resource will help.

https://www.servicenow.com/community/itom-forum/discovery-changing-the-status-of-the-esx-servers/m-p...

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1217508

Please appreciate the efforts of community contributors by marking appropriate response as correct answer and helpful, this may help other community users to follow correct solution in future.

Thanks

Ajay Kumar