Dell EMC OpenManage Version Port Information Guide Version 9.4

PDF

OpenManage Integration for VMware vCenter

Virtual Appliance

NOTE: : When deploying the Server Administrator agent using the Fix non-compliant vSphere hosts link available from the Compliance window in the Dell Management Center, the OpenManage Integration for VMware vCenter starts the http Client service and enables port 8080 on and releases after ESXi 5.0 to download OMSA VIB and install it. Once the OMSA installation is completed, the service automatically stops and the port is closed.

Table 1. Supported Protocols and Ports on Virtual ApplianceThe following table describes the ports in the order of the port number, the protocol, the port type, the maximum encryption level, the direction, the destination, the usage of the port, and the description.
Port Number Protocols Port Type Maximum Encryption Level Direction DestinationUsage Description
53 DNS TCP None Out OMIVV appliance to DNS serverDNS client Connectivity to the DNS server or resolving the host names.
69 TFTP UDP None Out OMIVV appliance to TFTP serverTFTP Client Used for firmware update on 11G servers with old firmware.
80/443 HTTP/HTTPS TCP None Out OMIVV appliance to internetDell Online Data Access Connectivity to the online (Internet) warranty, firmware, and latest RPM information.
80 HTTP TCP None In ESXi server to OMIVV applianceHTTP server Used in operating system deployment flow for post installation scripts to communicate with the OMIVV appliance.
162 SNMP Agent UDP None In iDRAC/ESXi to OMIVV applianceSNMP Agent (server) To receive SNMP traps from managed nodes.
443 HTTPS TCP 128-bit In OMIVV UI to OMIVV applianceHTTPS server Web services offered by OMIVV. These Web services are consumed by vCenter Web Client and Dell Admin portal.
443 WSMan TCP 128-bit In/Out OMIVV appliance to/from iDRAC/OMSAiDRAC/OMSA communication iDRAC, OMSA, and CMC or Management Module communication, used to manage and monitor the managed nodes.
445 SMB TCP 128-bit Out OMIVV appliance to CIFSCIFS communication To communicate with Windows share.
4433 HTTPS TCP 128-bit In iDRAC to OMIVV applianceAuto Discovery Provisioning server that is used for auto discovering managed nodes.
2049 NFS UDP/TCP None In/Out OMIVV appliance to NFSPublic Share NFS public share that is exposed by OMIVV appliance to the managed nodes and used in firmware update and operating system deployment flows.
4001 to 4004 NFS UDP/TCP None In/Out OMIVV appliance to NFSPublic Share These ports must be kept open to run the statd, quotd, lockd, and mountd services by the V2 and V3 protocols of the NFS server.
11620 SNMP Agent UDP None In iDRAC to OMIVV applianceSNMP Agent (server) Port used to receive the standard SNMP alerts by using UDP: 162. Data from iDRAC, OMSA, and CMC or Management Module are received to manage and monitor the managed nodes.
User-definedAnyUDP/TCPNoneOutOMIVV appliance to proxy serverProxyTo communicate with the proxy server.

Managed Nodes (ESXi)

Table 2. Supported Protocols and Ports on Managed NodesThe following table describes the ports, the protocol, the port type, the maximum encryption level, the direction, the destination, the usage of the port, and the description.
Port Number Protocols Port Type Maximum Encryption Level Direction DestinationUsage Description
162, 11620 SNMP UDP None Out ESXi to OMIVV applianceHardware Events Asynchronous SNMP traps sent from ESXi. This port has to open from ESXi.
443 WSMan TCP 128-bit In OMIVV appliance to ESXi(OMSA)iDRAC/OMSA communication Used to provide information to the management station. This port has to open from ESXi.
443 HTTPS TCP 128-bit In OMIVV appliance to ESXiHTTPS server Used to provide information to the management station. This port has to open from ESXi.
8080 HTTP TCP 128-bit Out ESXi to OMIVV applianceHTTP server; downloads the OMSA VIB and fixes non-compliant vSphere hosts. Helps ESXi to download the OMSA/driver VIB.

Managed Nodes (iDRAC or CMC or Management Module)

Table 3. Supported Protocols and Ports on Managed NodesThe following table describes the ports, the protocol, the port type, the maximum encryption level, the direction, the destination, the usage of the port, and the description.
Port Number Protocols Port Type Maximum Encryption Level Direction DestinationUsage Description
443 WSMan/HTTPS, REST/HTTPS TCP 128-bit In OMIVV appliance to iDRAC or CMC or Management ModuleiDRAC communication Used to provide information to the management station and communicate to MX chassis by using REST or HTTPS protocols. This port has to open from iDRAC and CMC or Management Module.
4433 HTTPS TCP 128-bit Out iDRAC to OMIVV applianceAuto Discovery For auto discovering iDRAC (managed nodes) in the management station.
2049 NFS UDP None In/Out iDRAC to/from OMIVVPublic Share For iDRAC to access NFS public share that is exposed by OMIVV appliance. That is used for operating system deployment and firmware update.

To access the iDRAC configurations from the OMIVV used in deployment flow.

4001 to 4004 NFS UDP None In/Out iDRAC to/from OMIVVPublic Share For iDRAC to access NFS public share that is exposed by OMIVV appliance. This is used for operating system deployment and firmware update.

To access the iDRAC configurations from the OMIVV used in deployment flow.

69TFTPUDP128-bitIn/OutiDRAC to/from OMIVVTrivial File TransferUsed for managing the iDRAC successfully from the management station.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\