Users Guide
Table Of Contents
- Dell EMC iDRAC Service Module 3.4 User’s Guide
- Contents
- Introduction
- Preinstallation setup
- Installing iDRAC Service Module
- Initial installation of iDRAC Service Module through iDRAC for Windows
- Initial installation of iSM through iDRAC Express
- Initial installation of iDRAC Service Module via iDRAC for Linux
- Installing iDRAC Service Module on Microsoft Windows operating systems
- Installing iDRAC Service Module on supported Linux operating systems
- Installing the iDRAC Service Module on VMware ESXi
- Installing iDRAC Service Module when the System Configuration Lock Down Mode is enabled
- Configuring the iDRAC Service Module
- iDRAC Service Module monitoring features
- Operating system information
- Lifecycle Controller log replication into operating system
- Automatic System Recovery
- Windows Management Instrumentation Providers
- Prepare to remove NVMe PCIe SSD device
- Remote iDRAC hard reset
- iDRAC access via Host OS
- Accessing iDRAC Via GUI, WS-man, Redfish, Remote RACADM
- In-band support for iDRAC SNMP alerts
- Enable WSMAN Remotely
- Auto-updating iDRAC Service Module
- FullPowerCycle
- SupportAssist on the Box
- Enabling the In-band SNMP Get feature—Linux
- Enabling the In-band SNMP Get feature—Windows
- iDRAC GUI Launcher
- Single sign-on (SSO) to iDRAC GUI from Host OS administrators desktop
- IPv6 communication between iSM and iDRAC over OS-BMC Passthru
- Enhanced security between iSM and iDRAC communication using TLS protocol
- Frequently asked questions
- Linux and Ubuntu installer packages
NOTE: When browsers are not installed on the Host OS or Invoke-iDRACLauncher is not able to launch iDRAC due to
browser issue, a session is created in iDRAC already. An iDRAC admin user can log in to iDRAC and delete the sessions.
Following are the iDRAC GUI Launcher behavior with different OS-to-iDRAC Passthrustates:
● When OS-to-iDRAC Passthru setting in iDRAC is disabled, Invoke-iDRACLauncher prompts if you want to enable OSBMC-
Passthru in USBNIC mode.
● When OS-to-iDRAC Passthru setting is already configured in LOM mode, the iDRAC Launcher does not launch the iDRAC
GUI.
● When OS-to-iDRAC Passthru setting is disabled in iDRAC and Disable iDRAC Local Configuration using Settings is
also disabled or lockdown mode is enabled in iDRAC, iDRAC GUI is not launched.
NOTE: When Local Configuration using Settings or Local Configuration using RACADM is disabled in iDRAC, iDRAC
login screen is displayed.
NOTE: When an iDRAC SSO session is active on the Host OS, closing the related terminal closes the browser with SSO
session as well.
NOTE: Ensure to invoke iDRAC GUI Launcher from a GUI supported and capable interface.
NOTE: iDRAC GUI Launcher does not open the iDRAC UI when the USBNIC interface on the Host OS is configured with
IPv6 address.
Prerequisites
Linux packages:
1. Browser such as Mozilla firefox.
2. Sudo.
3. 14
the
generations of PowerEdge servers.
4. iDRAC firmware versions 3.30.30.30 and above.
Limitations for Linux operating systems
The limitations of the iDRAC SSO Launcher for Linux operating systems are:
1. iSM does not support desktop utilities other than GNOME.
2. iSM does not support browsers other than Mozilla firefox.
NOTE: When local configuration over KCS/racadm is disabled in iDRAC, then iDRAC login screen will be displayed.
IPv6 communication between iSM and iDRAC over
OS-BMC Passthru
Starting iSM 3.4, iSM supports both IPv4 and IPv6 modes of communication. Once you install iSM, iSM service attempts to
connect to iDRAC using IPv4 link-local address. If there is no IP address on the Host USBNIC interface, iSM tries to configure
IPv4 address on the Host side. This USBNIC interface configuration on the Host OS from iSM is done only once. iSM remains
disconnected from iDRAC if there is any subsequent scenario of incomplete configuration of USBNIC on the Host OS. In case
the connection fails even after configuring IPv4 address, iSM tries to connect to iDRAC using IPv6.
NOTE: This feature is supported only on Linux operating systems.
NOTE: If IPv6 network stack is disabled on the Host OS, then iSM retries to communicate with iDRAC using IPv4.
If either of the protocols are disabled, then iSM will not try to connect to iDRAC using the disabled protocol.
NOTE:
If the iDRAC firmware version does not support IPv6 on USBNIC, the connection between iSM and iDRAC is
established using IPv4.
Respective audit messages are logged by iSM indicating the protocol version using which iSM connected with iDRAC.
40
iDRAC Service Module monitoring features