Dell EMC iDRAC Service Module 3.4 User’s Guide March 2019 Rev.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2018 - 2019 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: Introduction................................................................................................................. 5 What’s New.......................................................................................................................................................................... 5 Supported features—operating systems matrix.........................................................................................................
Chapter 4: Configuring the iDRAC Service Module...................................................................... 28 Configuring the iDRAC Service Module from iDRAC Web Interface....................................................................28 Configuring the iDRAC Service Module from RACADM.......................................................................................... 28 Configuring the iDRAC Service Module from WSMan......................................................................
1 Introduction This guide provides information and step-by-step instructions on how to install iDRAC Service Module on the supported operating systems. The Integrated Dell Remote Access Controller(iDRAC) Service Module is a lightweight optional software application that can be installed on Dell’s 12th generation of PowerEdge servers or later.
Table 1.
NOTE: The overlapping features are AutoSystemRecovery and Lifecycle Log Replication. Software availability The iDRAC Service Module software is available on: ● Dell EMC OpenManage Systems Management Tools and Documentation DVD ● Support site—dell.com/support Downloading iDRAC Service Module You can download the iDRAC Service Module software from dell.com/support.
Other documents you may need You can access the following guides available at dell.com/support. ● The Integrated Dell Remote Access Controller (iDRAC) User’s Guide provides detailed information about configuring, and using the iDRAC. ● The Dell Remote Access Controller Racadm User's Guide provides information about using the RACADM command-line utility. ● The Dell Update Packages User's Guide provides information about obtaining and using Dell Update Packages as part of your system update strategy.
2 Preinstallation setup Ensure that you assess the following before installing the iDRAC Service Module: ● ● ● ● ● ● ● 12th generation or later of Dell PowerEdge servers. For the list of supported platforms, see Supported Platforms Minimum firmware version—For iDRAC 8 – 2.61.60.60 and for iDRAC 9 – 3.21.21.21. Administrator privileges. Read the installation instructions for the operating system. Read the applicable release notes files and the Systems Software Support Matrix.
Supported platforms on Microsoft Windows operating systems The table lists the platforms that are supported by iDRAC Service Module 3.4 on Microsoft Windows operating systems. Table 2.
Table 2.
Table 3. Supported platforms on Linux operating systems (continued) Dell Systems SLES 15 Ubuntu 18.04.2 RHEL 7.6 RHEL 6.
Table 3. Supported platforms on Linux operating systems (continued) Dell Systems SLES 15 Ubuntu 18.04.2 RHEL 7.6 RHEL 6.
Table 4. Supported platforms on Virtualization operating systems (continued) Dell Systems VMware vSphere 6.5 U2 vSphere 6.
Table 4. Supported platforms on Virtualization operating systems (continued) Dell Systems VMware vSphere 6.5 U2 vSphere 6.
System requirements ● One of the supported operating systems. For more information on supported operating systems, see Supported operating systems. ● Minimum 2 GB RAM. ● Minimum 512 MB of hard drive space. ● Administrator rights. ● The Remote Network Driver Interface Specification (RNDIS) capability for discovering a network device over USB.
3 Installing iDRAC Service Module The iDRAC Service Module can be installed in any of the following operating systems: ● Microsoft Windows operating systems. ● Supported Linux operating systems. ● VMware ESXi.
2. For Microsoft Windows OS, RDP to the server or go to the physical server console. For Linux OS, SSH to the host IP or go to the physical server console. 3. Find the mounted volume in your device list labeled SMINST, and click the appropriate script to start the installation. For Microsoft Windows OS, run the ISM-Win.bat script. For Linux OS, run the script ISM-Lx.sh from the shell. 4.
a. Choose the program features you want to install and click Next. The Lifecycle Controller Log Replication window is displayed. b. Specify the location where the LC logs are to be replicated. By default, Typical (Windows Logs/System) option is selected and the LC logs are replicated in the System group of the Windows Logs folder in the Event Viewer. Click Next.
Modifying the iDRAC Service Module components on Microsoft Windows operating systems To modify iDRAC Service Module components: 1. Browse to SYSMGMT > iSM > Windows, and then run iDRACSvcMod.msi. The iDRAC Service Module ˗ InstallShield Wizard is displayed. 2. Click Next. 3. Select Modify. 4. Enable or disable the features as required and then click Next. The Lifecycle Controller Log Replication window is displayed. 5. Specify the location where you need the LC logs to be replicated.
Unattended uninstall using the product ID Type msiexec /x {BE762CE4-B8D4-4BFC-BA12-16360808DCF3} /qn to uninstall the iDRAC Service Module using the product ID. Uninstalling using the add or remove feature The iDRAC Service Module can be uninstalled by using the Add or Remove option from the control panel. To do so, go to Start > Control Panel > Programs and Features . NOTE: You can also uninstall by selecting Uninstall after you run the iDRACSvcMod.msi.
Table 7. Linux install dependency (continued) Executable Commands Package Name find findutils Shell Script commands bash ifconfig net-tools ping Iputils chkconfig RedHat Enterprise Linux ● chkconfig SUSE Linux Enterprise Server ● aaa_base install_initd RedHat Enterprise Linux ● redhat-lsb-core SUSE Linux Enterprise Server ● insserv Systemctl systemd curl libcurl openssl libssl Installing The iDRAC Service Module on Linux operating system 1.
NOTE: You must provide a unique port number between the range 1024 to 65535 if you chose to install iDRAC access via Host OS feature. If you do not provide a port number, port number 1266 or a previously configured port (if any) is assigned by default. NOTE: if OpenManage Server Administrator (OMSA) is already installed on 1311, the same port could not be utilized for iDRAC Service module. NOTE: When iSM 3.4.
Uninstalling the iDRAC Service Module using the uninstall script The script used for uninstalling the iDRAC Service Module is dcism-setup.sh. Run the shell script and select d to uninstall the iDRAC Service Module. Uninstalling the iDRAC Service Module using the RPM command The iDRAC Service Module can be uninstalled using the RPM command rpm -e dcism in the command line. Installing the iDRAC Service Module on VMware ESXi VMware ESXi is factory-installed on some systems.
4. Right-click New Datacenter and click Add Host. Provide information for the ESXi server per online instructions. 5. Right-click the ESXi host added in step 4 and click Maintenance Mode. 6. From Plug-ins, select Manage Plug-ins > download VMware Update Manager. (The status is enabled if the download is successful.) Follow the instructions to install the VUM client. 7. Select the ESXi host.
NOTE: You can upgrade iDRAC Service Module from the VMware Update Manager repository https:// vmwaredepot.dell.com/. Using the Power CLI To install the iDRAC Service Module using Power CLI: 1. Install the supported PowerCLI of ESXi on the supported Microsoft Windows operating system. 2. Copy the ISM-Dell-Web-3.4.0-.VIB-i-Live.zip file to the ESXi host. 3. Navigate to the bin directory. 4. Run Connect-VIServer and provide the server and other credentials. 5.
Support for iDRAC URI to get iSM installer Starting from 14th generation of servers, you can download the iSM web packs by using the following URL:https:// /software/ism/package.xml. You can download the packages only when iSM LC DUP is uploaded and available in iDRAC. You can also load it in iDRAC by enabling the iDRAC LC autoupdate. To download the packages, use the filename present in the xml to append to the URL. Example: PAGE 284 Configuring the iDRAC Service Module You can configure the iDRAC Service Module using the: ● iDRAC web interface ● RACADM CLI command ● WSMAN command Topics: • • • Configuring the iDRAC Service Module from iDRAC Web Interface Configuring the iDRAC Service Module from RACADM Configuring the iDRAC Service Module from WSMan Configuring the iDRAC Service Module from iDRAC Web Interface To use the iDRAC Service Module from the iDRAC Web interface for 12 th and 13 th generations of servers, go to Overview >
CreationClassName=DCIM_iDRACCardService+Name=DCIM:iDRACCardService+SystemCreationClassName= DCIM_ComputerSystem+SystemName=DCIM:ComputerSystem -u:root -p:calvin -r:https:///wsman -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic @{Target="iDRAC.Embedded.1";AttributeName="AgentLite.
5 iDRAC Service Module monitoring features The services provided are: ● OS information ● Lifecycle Controller Log replication into operating system ● Automatic system recovery ● Windows Management Instrumentation providers inclusive of storage data ● Prepare to remove NVMe SSD device ● Remote iDRAC hard reset ● iDRAC access via Host OS ● In-band support for iDRAC SNMP alerts ● Enable WSMAN remotely ● Auto-updation of iDRAC Service Module ● FullPowerCycle ● Support Assist on the Box NOTE: FullPowerCycle and
NOTE: If the network configuration on the Host OS is configured using netplan, then iSM will be unable to monitor the network interfaces' change in states, DHCP configuration of an interface for instance. Hence you may not be able to view the change of the Host OS network interface details in the iDRAC interfaces. Lifecycle Controller log replication into operating system Replicates the Lifecycle Controller (LC) logs to the OS logs.
Prepare to remove NVMe PCIe SSD device You can remove a Non-Volatile Memory Express (NVMe) Pheripheral Component Interconnect Express (PCIe) Solid State Device (SSD) without shutting down or rebooting the system. When you are removing a device, all the activities associated with the device must be stopped to prevent data loss. To prevent loss of data use the Prepare to Remove option, which stops all the device-associated background activities, after which you can remove the NVMe PCIe SSD physically.
received from the host OS than the traps received from iDRAC. When an SNMP alert is received from iDRAC, it would be challenging to determine the source of the alert as it is from an iDRAC IP and not the system IP. Starting from 14 th generation of servers, all events that have the SNMP Trap option as the target (in the Alerts page or in the equivalent RACADM or WSMAN interfaces) can be received as SNMP trap through the OS using the iDRAC Service Module. For iDRAC firmware 3.0.
● To do silent install or update, type––silent/-s. ● To uninstall the current version and install the update package available in LC, type ––force/-f. NOTE: This option overwrites the previous configuration. ● To get details about the update package version and the installed version of iDRAC Service Module, type ––get— version/-v. ● To download the iDRAC Service Module update packages to the user specified directory, type ––get—update/-g.
SupportAssist on the Box SupportAssist saves time and streamlines the technical support cases. A collection based on an event creates an open service request with SupportAssist. Scheduled collections helps to monitor and maintain your environment. These collections include the hardware data, RAID controller logs, OS, and Application Data. The features supported are : ● SupportAssist Registration — iSM supports the SupportAssist Registration. This is a one time activity.
NOTE: It might take few minutes to complete the registration process. After the registration is completed successfully, you will get a welcome email from SupportAssist to the email address being registered. 6. On the Summary tab, view the Registration ID and Automatic Features current setting details. 7. To close the SupportAssist Registration wizard, click Close. In the SupportAssist page, if you navigate to the bottom you can view the contact information. 8.
The supported iDRAC firmware for the anonymous collection is iDRAC 3.15.15.15 in the 14 th generation of PowerEdge servers and 2.60.60.60 in the 12 th and 13 th generations of PowerEdge servers. NOTE: You can perform Anonymous SupportAssist Collection upload using blank username or password in proxy environment on the 13 th generation of PowerEdge servers.
iSM SupportAssist Disk Auto Dispatch Starting iSM 3.4, if the server hits one of the following SNMP events: PDR16 and PDR63, then you get a recommendation from Dell EMC support via email regarding the dispatch of the predictive failure or a bad disk block such as SSDs subject to the prevailing licensing terms and conditions. Once you receive the email, you need to follow up and provide the service address to Dell EMC support for the delivery of the dispatched parts.
Enabling the In-band SNMP Get feature—Windows The In-band SNMP Get feature allows you to query the system management data over the SNMP service on the host operating system. The host SNMP services should be enabled and configured s a prerequisite for this feature. The SNMP service on the iDRAC should be enabled. If it is not enabled, then iDRAC Service Module will enable and configure the SNMP service on the iDRAC. This feature can be enabled or disabled using any of the iDRAC interfaces or the installer.
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 OSBMCPassthru in USBNIC mode.
NOTE: When iDRAC USBNIC is already configured with only IPv6 address on the Host OS and then iSM is installed on the Host, then iSM communication with iDRAC will start using IPv4 protocol. Unsupported features with IPv6 protocol The features that are not supported when iSM is configured with IPv6 protocol and IPv4 configuration is not available on the USBNIC interface are: ● ● ● ● ● InBand iDRAC Access iDRAC GUI Launcher iDRAC SSO Launcher idrac.local and drac.
6 Frequently asked questions This section lists some frequently asked questions about the iDRAC Service Module. Do I need to uninstall OpenManage Server Administrator before installing or running the iDRAC Service Module? No. Before you install or run the iDRAC Service Module, ensure that you have stopped the features of OpenManage Server Administrator that the iDRAC Service Module provide. NOTE: Uninstalling the OpenManage Server Administrator is not required.
Consult the User Guide for additional information about the supported servers. What should I do now? Before installing the iDRAC Service Module, ensure that the server or the system on which the iDRAC Service Module is to be installed is a Dell’s 12 th generation PowerEdge server or later. Also make sure that you have a 64-bit system.
I used the remote iDRAC hard reset feature to reset the iDRAC. However, the IPMI is unresponsive and I am not able to troubleshoot. If you try to use the remote iDRAC hard reset feature on VMware ESXi 5.5 U3 or ESXi 6.0 U1, the IPMI drivers becomes unresponsive, because of this the iDRAC Service Module communication is stopped. You may have to reboot the server and load the IPMI driver again to resolve the issue.
I created a custom folder in Windows Event Viewer, but the LC logs are not replicated in my custom folder. What do I have to do now to replicate the LC logs? Ensure to close the Windows Event Viewer after creating the custom folder. Open the Windows Event Viewer again to view the replicated LC logs. I chose custom install option from the Graphical User Interface during iDRAC Service Module installation and disabled a feature, but I am not able to enable the feature using any of the other interfaces.
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.
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. If dependent packages for iSM are not present on Ubuntu OS, then installation through OS DUP installs iSM in install+unpacked state.
7 Linux and Ubuntu installer packages The installer packages for the supported Linux and Ubuntu OS are as follows: Table 12. Linux installer packages Supported Linux Operating System Installer Packages Red Hat Enterprise Linux 6 SYSMGMT\iSM\linux\RHEL6\x86_64\dcism-3.4.0.el6.x86_64.rpm Red Hat Enterprise Linux 7 SYSMGMT\iSM\linux\RHEL7\x86_64\dcism-3.4.0.el7.x86_64.rpm SUSE Linux Enterprise Server 15 SYSMGMT\iSM\linux\SLES15\x86_64\dcism-3.4.0.sles15.x86_64.
