ESX discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2024 07:11 AM
Hi ITOM specialists,
I have a funny scenario, I have some ESX servers that are not being discovered, the timeline is as follow:
-Until a few weeks ago, they were being discovered by the VMWare credentials that I setup, then suddenly , discovery couldnt update them anymore.
- When I test credentials against the IP, it fails, saying that credentials are invalid.
- I deleted the ESX record from CMDB, and let the schedule run by itslef, the ESX was created again,
Did anyone have this issue and if yes, how did you solve it because I am not going to delete all the other records as well.
- Labels:
-
Discovery
-
Orchestration (ITOM)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2024 09:22 PM
To Start with ..
Open Discovered ESX record ..Look for the IP in Credential Affinity Table and See which CREDS was used for its discovery.
dscy_credentials_affinity- In this table u can see the SYS ID of Credential Record which is used for Discovery.
Now Using Same Credential try a quick Discovery of ESX .
I just searched and below is a VMWARE Credential record.
Regards
RP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2024 12:06 AM
Hi Rahul,
I did exactly what you suggested and i found out that the credentials in this case are for something completely different, they are credentials we use for something which has no relationship with Discovery