Users Guide

Table 28. Managed nodes (iDRAC or CMC or OME-Modular) (continued)
Port
Number
Protoco
ls
Port
Type
Maximum
Encryptio
n Level
Direction Destination Usage Description
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 OMIVV
Public 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.
69 TFTP UDP 128-bit In/Out iDRAC to/
from OMIVV
Trivial File
Transfer
Used for managing the iDRAC
successfully from the management
station.
NOTE: For 14th generation PowerEdge servers, iDRAC mounts the NFS through TCP on port 2049.
Password is not changed for user used for bare-metal discovery
after successfully applying system profile that has same user with
new changed credentials in iDRAC user list
The password of the user who is used from discovery is not changed to the new credential if only System Profile (Configuration
of the hardware) is selected for deployment. This is done intentionally so that the plug-in can communicate with the iDRAC for
future use in deployment needs.
Unable to view new iDRAC version details listed on vCenter hosts
and clusters page
Resolution: After successful completion of a firmware update task in the vSphere web client, refresh the Firmware Update
page and verify the firmware versions. If the page displays the old versions, go to the Host Compliance page in OpenManage
Integration for VMware vCenter, and check the CSIOR status of that host. If CSIOR is not enabled, enable CSIOR and reboot
host. If CSIOR is already enabled, log in to the iDRAC console, reset iDRAC, wait for few minutes, and then refresh the
Firmware Update page.
Can OMIVV support ESXi with lockdown mode enabled
Yes, lockdown mode is supported in this Release on hosts ESXi 6.0 and later.
When I tried to use lockdown mode, it fails
When I added a host to the host credential profile in lockdown mode, the inventory started, but failed stating that “No Remote
Access Controller was found or Inventory is not supported on this host.”
If you put the host in lockdown mode or remove a host from lockdown mode, ensure that you wait for 30–minutes before
performing the next operation in OMIVV.
Frequently Asked Questions-FAQ
141