Users Guide

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 congures 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 conguration 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 le ISM_Win.BAT from
the iDRAC exposed logical partition "SMINST" on
Microsoft Windows OS, I see a console message
saying "The system cannot nd the le specied."
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.
If dependent packages for iSM are not present on
Ubuntu OS, then installation through OS DUP installs
iSM in install+unpacked state. You can verify this
using the below command:
#dpkg -s dcism
Package: dcism
Status: install ok unpacked
To x this issue, run the command apt-get install -f. This will install dependent packages.
When I install iSM 3.4.0 on Linux operating systems
such as RedHat Enterprise Linux, I see some
messages in OS logs such as
G_IS_SIMPLE_ACTION
(simple)' failed: failed to rescan: Failed to parse /usr/
share/applications/iDRACGUILauncher.desktop le:
cannot process le of type application/x-desktop
.
The messages are related to the GNOME desktop manager. Various OS groups have Bugzilla items for this scenario to be addressed. For
example: https://bugzilla.redhat.com/show_bug.cgi?id=1594177. No action is required by the user.
Frequently asked questions
51