Steps to setup VMware vCenter discovery in ServiceNow

[Swarnarghya]

I need to setup discovery of vCenter instance using the discovery process. I have around 20 different IP address of the vCenter instance. In order to discover them do I need to setup credentials for all the 20 different IP addresses? And How many midservers are required to discover them. In which host do I need to install the midserver? Can you please explain the steps to configure this.

[pratik0306]

Hi @Swarnarghya If its a separate credential for each Vcenter then yes you need to create all of them in Credential section under Discovery.

Single MID server will suffice unless its already doing discovery of many CIs. 

You can install the MID on the VM has less latency towards the Vcenters.

high level steps:

1. Configure the MID server.

2. Verify the Vcenters are accessible from MID server and all ports are open

3. Create the credentials- read only account on Vcenter level which should have visibility to its child members.

4. Create Discovery schedule and have all the Vcenter IPs configured in it. If it takes too much time then you can split them into 2 schedules.

[Rahul Priyadars]

See if This Article helps you in general- https://www.servicenow.com/community/itom-articles/vmware-vcenter-discovery-quick-and-crisp/ta-p/231...

 I have around 20 different IP address of the vCenter instance. In order to discover them do I need to setup credentials for all the 20 different IP addresses? And How many midservers are required to discover them.---> to Answer these questions it depends on Configuration and placement of Vcenters. Are all are in Same Data Center?

Technically you may need 20 Credentials records but your Vcenter Admin can guide you on more.

Where to Place Mid Server- Choose a Subnet from where your Vcenter setups is accessible and required Ports are opened <20 Mid Server on high level.

Regards

RP

[khaires750]

Hi Community,

I have a question regarding VMware Virtual Machine Instance in ServiceNow. Currently, I have records in the VMware Virtual Machine Instance table, but I now need to import data from IH-ETL. The incoming data contains virtualized machine details, which I’ve classified into respective classes based on the OS values.

After reviewing the data, I noticed that the data in both classes (e.g., cmdb_ci_vmware_instance and OS-related classes like cmdb_ci_win_server) seems very similar for common attributes, with the only difference being class-specific attributes.

My Question:
Is it appropriate to create new devices in these classes, even though the virtual machine instance already exists in the CMDB?
Should I consider the new records as duplicates, or is it acceptable to represent the same device in different classes, each with additional class-specific attributes?
I’d appreciate your thoughts on whether this approach is advisable.

Thanks!