Ports required for IMS
Table: Infrastructure Management Server (IMS)
|
Ports used |
Description |
For communication between |
Direction |
Protocol |
|---|---|---|---|---|
|
22 |
Used for Remote access to IMS Shell Console |
Client terminals to IMS |
In-bound |
TCP |
|
22 |
Used for remote deployment of the packages on remote Linux host from IMS |
IMS to hosts to be protected |
Out-bound |
TCP |
|
53 |
Used for DNS name resolution |
DNS server and IMS in the data center |
Out-bound |
TCP, UDP |
|
88 |
Used for authenticating DNS server with Kerberos keys |
DNS server and IMS |
Out-bound |
TCP, UDP |
|
123 |
Used for NTP synchronization |
IMS and the NTP server |
Out-bound |
UDP |
|
443 |
Used for communication with vCenter using vSphere SDK This is the default value for the port that will be used for accessing vcenter for discovery and operations. A non-default port must be configured on the vcenter first before it can be configured in IMS. |
IMS and VMware vCenter server |
Out-bound |
HTTPS, TCP |
|
750 |
Used for authenticating DNS server with Kerberos keys |
DNS server and IMS |
Out-bound |
TCP, UDP |
|
5634 |
Used for communication between IMS and the hosts that are added to Resiliency Platform |
IMS and the hosts |
Bi-directional |
HTTPS, TLS 1.2 |
|
14161 |
Used for adding IMS by providing username and password |
Resiliency Manager and IMS |
In-bound |
HTTPS, TLS 1.2 |
|
14176 |
Used for communication between the Resiliency Manager and IMS |
Resiliency Manager and IMS |
Out-bound |
HTTPS, TLS 1.2 |