Users Guide

I am seeing 169.254.0.2 as the source IP address in the

iDRAC SNMP trap received via iSM. How do I troubleshoot

the issue?

On Linux OS, the iDRAC SNMP traps received via Host OS displays the hostname or source IP address as 169.254.0.2 instead of

the actual Host OS name or IP address. This is decided by the OS to populate the entry before rendering the trap to the user.

I have configured OS to iDRAC pass-through to LOM and

when I try to run dcism-sync, the update operation fails.

What can be done?

OS to iDRAC pass-through should be configured to USB-NIC mode. This is a pre-requisite for iDRAC Service Module installation

and update.

I am able to enable or disable the WMIInfo feature of iSM on

Linux and VMware ESXi Operating Systems using racadm

and WSMan commands. Does this impact my iSM

configuration on the Host OS?

The WMIInfo feature of iSM is applicable only for Microsoft Windows Operating Systems. However, enabling or disabling this

feature from any of the iDRAC interfaces on any Operating System other than Microsoft Windows does not impact the iSM

configuration on the Host OS.

If I delete the IP address of the USBNIC interface on the

Host OS, then iSM is unable to communicate with iDRAC.

Starting iSM version 3.3, iSM configures the Host OS USBNIC interface only once. Subsequently, if you bring down the USBNIC

interface on the Host OS by deleting the IP address, making the interface link down or disabling the IPV4 or IPV6 address on

this interface, then iSM will retain the user configuration and does not override the interface settings. To restore the

communication between iSM and iDRAC, please restart the iSM service on the Host OS.

After installing iSM using the Batch file ISM_Win.BAT from

the iDRAC exposed logical partition "SMINST" on Microsoft

Windows OS, I see a console message saying "The system

cannot find the file specified."

After iSM is installed successfully, the logical partition SMINST gets unmounted from the Host OS. This message appears if the

BAT script is invoked from the SMINST partition itself. The installation is successful. No action is required by the user.

Frequently asked questions