Dell iDRAC Service Module 5.0.1.0 User’s Guide

Host administrators can launch iDRAC from within the host operating system using IPv6. iDRAC SSO launcher requires a desktop environment like GNOME or K Desktop Environment(KDE) on the host operating system.

The single sign-on (SSO) feature enables an authenticated operating system administrator to directly access the iDRAC web interface without requiring log in using separate iDRAC administrator credentials. After installing this feature, a Program Menu shortcut called Invoke-iDRACLauncher on Microsoft Windows operating systems is created. On the Linux operating system, iSM creates a shortcut under Applications which you can double-click to launch the iDRAC dashboard. iSM provides a command-line interface that is called Invoke-iDRACLauncher on Microsoft Windows operating systems and Invoke-iDRACLauncher.sh on Linux operating systems.

You can configure the iDRAC Service Module using the IPv6 address. By default, communication is established through IPv4. Upon failure, the communication is reattempted over IPv6. An error message is audited when the communication fails.

fde1:53ba:e9a0:de12::/64
fde1:53ba:e9a0:de13::/64
fde1:53ba:e9a0:de14::/64
fde1:53ba:e9a0:de15::/64
fde1:53ba:e9a0:de16::/64

You can choose from two types of privileges to log in to iDRAC.

• Read-Only account: An express or basic install of iSM installs iDRAC SSO launcher, enabling the administrator to log in to iDRAC as a Read-Only account. In addition to the ability to view component health status, logs, and inventory, a few more SupportAssist operations that are required by the service personnel are enabled.
• Administrative account: Installing this feature by selecting the Administrator privilege enables the host operating system administrator to log in to iDRAC as an operator user. Using this account, you can perform all the operations that an iDRAC root user can perform, except configuring or deleting iDRAC users or clearing the Lifecycle Log.

Disable SSO to iDRAC from host operating system: You can also opt to Disable this feature completely. When iSM is installed by disabling this feature, launching the iDRAC GUI launcher launches the iDRAC log in page with the default browser.

Invoke-iDRACLauncher is independent of the iSM service and can be invoked even if iSM service is stopped.

When browsers are not installed on the host operating system or Invoke-iDRACLauncher is not able to launch iDRAC due to a browser issue, a session is still created in iDRAC. Using an iDRAC administrator account, you can login to iDRAC and delete the sessions.

The iDRAC GUI Launcher behaves differently depending on the state of the OS to iDRAC Pass-through setting.

• When the OS to iDRAC Pass-through setting in iDRAC is disabled, Invoke-iDRACLauncher prompts you to enable OS to iDRAC Pass-through in USBNIC mode.
• When the OS to iDRAC Pass-through setting is already configured in LOM mode, the iDRAC GUI Launcher does not launch the iDRAC UI.
• When the OS to iDRAC Pass-through setting is disabled in iDRAC and Disable iDRAC Local Configuration using Settings is also disabled or Lockdown mode is enabled in iDRAC, the iDRAC UI is not launched.
  NOTE When Local Configuration using Settings or Local Configuration using RACADM is disabled in iDRAC, the iDRAC login screen is displayed.

When an iDRAC SSO session is active on the host operating system, closing the related terminal closes the browser with SSO session as well.