Specify an alternate port for the VMware - vCenter datacenters
probe.
Before you begin
Role required: Discovery admin or VMware admin responsible for vCenter and ESXi hosts
About this task
To establish proper connectivity for Discovery to vCenter, alternate ports are required if default ports are unavailable or customized.
By default, vCenter discovery initiates on these ports:
When these ports are detected, the VMWare - vCenter datacenters probe is
triggered.
Procedure
-
Hard code the port from your ServiceNow instance.
-
Navigate to .
-
Select the specific instance from the list of instances.
-
Edit the URL field and include the port.
For example, https://10.0.0.1:444
-
Select Update.
-
Specify an alternate port number for vCenter in the VMWare - vCenter datacenters
probe.
-
Navigate to .
-
Open the
VMware
- vCenter
Datacenters
probe record.
-
In the
Probe
Parameters
related list, select New.
-
In the Name field of the Probe parameter record, enter
vcenter_port.
-
In the Value field, enter your alternate port
number.
-
Select Submit.
-
Activate the VMWare - vCenter Classify probe.
Important: This configuration is only required when vCenter is on port 443.
-
Navigate to .
-
Open the
http
port probe record.
-
In the
Trigger
Probes
related list, select the false link for the
VMWare
- vCenter
Classify
classification probe.
-
Select the Active check box.
-
Select Update.
The VMWare - vCenter Classify probe establishes a connection between the MID Server and the vCenter instance. If the connection is
successful, it triggers the VMWare - vCenter datacenters probe.