Prerequisites check name
|
Category (Manual or Auto fix)
|
Applies to (Gateway OS/Node OS/iDRAC)
|
Recommendation
|
Proxy is configured
|
Auto fix
|
Target node OS
|
If node has network proxy configured, click
Resolve to add the Remote NDIS network adapter IP (169.254.* series IPs) of that node to the proxy exclusion list. These IPs are used to communicate with iDRAC.
NOTE: If this issue is not resolved, check if the
Proxy in the Network and Internet settings page on the iDRAC OS or server OS of that node is open. If it is open, close the page and try to resolve the issue again.
|
Redfish is enabled
|
Auto fix
|
iDRAC
|
If Redfish is disabled, click
Resolve to enable the Redfish service in the iDRAC of the target node. Redfish is used to retrieve target node inventory.
|
Remote NDIS adapter is enabled
|
Auto fix
|
Target node OS
|
If remote NDIS adapter is disabled, click
Resolve to enable the adapter as it is used to communicate with iDRAC.
|
Lockdown is disabled
|
Auto fix
|
iDRAC (Applicable to iDRACs with firmware version lower than 4.40)
|
If infrastructure lock is enabled, click
Resolve to unlock the infrastructure.
|
OS-iDRAC passthrough IPs are unique across cluster nodes
|
Manual fix
|
Target node OS
|
Each cluster node host OS should have a unique remote NDIS network adapter IPV4 IP. Otherwise, this may cause IP-conflict for the cluster.
NOTE: Change OS to iDRAC passthrough IP address only from iDRAC. After the IP is changed on iDRAC, Remote NDIS network adapter IP on host OS is automatically set.
|
OS-iDRAC passthrough IPs are unique across OS and iDRAC
|
Manual fix
|
iDRAC
|
The remote NDIS network adapter IP in host OS and OS to iDRAC passthrough IP in iDRAC should be different in a node. Otherwise, it can cause failure in inventory retrieval.
NOTE: Change OS to iDRAC passthrough IP address only from iDRAC. After the IP is changed on iDRAC, Remote NDIS network adapter IP on host OS is automatically set.
|
SMB 445 Port is enabled
|
Manual fix
|
Target node OS
|
On the target node, enable File and Printer Sharing (SMB-In) from the Windows Admin Center Firewall tool. OpenManage Integration extension uses SMB port 445 to copy files to the target node.
|
iDRAC has one empty slot
|
Manual fix
|
iDRAC (Applicable to iDRACs with firmware version lower than 4.40)
|
Ensure one empty slot is available on iDRAC. If all slots are full in iDRAC8, run the RACADM command to create one empty slot. Refer
Integrated Dell Remote Access Controller 9 RACADM CLI Guide.
|
Execution Policy is configured
|
Manual fix
|
Gateway OS, Node OS
|
Ensure that the PowerShell execution policy on the target node and gateway is not set as "Restricted". When the policy is restricted, it can prevent the execution of necessary PowerShell scripts to manage the node.
|
Node is up and reachable
|
Manual fix
|
Target node OS
|
Ensure the node is powered on and reachable from the Windows Admin Center gateway.
|
Remote NDIS adapter IPV4 is enabled
|
Manual fix
|
Target node OS
|
Enable IPv4 on host OS in "Remote NDIS Compatible Device" from network settings.
|
OS-iDRAC passthrough IP should be 169.254.0.1
|
Manual fix
|
iDRAC8 and below,
|
Recommended to change that to '169.254.0.1'
|
IPMI driver is running
|
Manual fix
|
Target node OS
|
Install or enable the IPMI driver. For more information, see
https://www.dell.com/support/kbdoc/en-in/000150763/dell-emc-openmanage-integration-with-microsoft-windows-admin-center-omimswac-fails-to-query-host-information
|
Powershell remoting is enabled
|
Manual fix
|
Target node OS
|
Enable PowerShell remoting and then set the firewall rules as per Microsoft recommendations. For more information, see
https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_remote_requirements?view=powershell-5.1#windows-network-locations
|
Smb Share is enabled
|
Manual fix
|
Target node OS
|
Enable or add administrative share. For more information, see
https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/problems-administrative-shares-missing
|
User Access Control (UAC) is disabled
|
Manual fix
|
Target node OS
|
If UAC is enabled, ensure to disable the UAC. For more information, see
https://docs.microsoft.com/en-us/troubleshoot/windows-server/windows-security/user-account-control-and-remote-restriction
|