Dell EMC iDRAC Service Module 3.4.
Notas, precauciones y avisos NOTA: Una NOTA indica información importante que le ayuda a hacer un mejor uso de su producto. PRECAUCIÓN: Una PRECAUCIÓN indica la posibilidad de daños en el hardware o la pérdida de datos, y le explica cómo evitar el problema. AVISO: Un mensaje de AVISO indica el riesgo de daños materiales, lesiones corporales o incluso la muerte. © 2019 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Introduction................................................................................................................................. 5 What’s New............................................................................................................................................................................5 Supported features—operating systems matrix...............................................................................................................
Support for idrac.local and drac.local as iDRAC FQDN............................................................................................. 21 4 Configuración del módulo de servicio del iDRAC ........................................................................... 22 Configuring the iDRAC Service Module from iDRAC Web Interface............................................................................22 Configuring the iDRAC Service Module from RACADM...............................................
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 yx3x servers or later. The iDRAC Service Module complements iDRAC interfaces – Graphical User Interface (GUI), RACADM CLI, Redfish, and Web Service Management (WSMan) with additional monitoring data.
Features Generation Operating Systems Prepare to Remove NVMe device through iDRAC.
yx5x servers yx4x servers yx3x servers R840 M630 R940 xa M630-VRTX MX740c M830 MX840c R230 R7425 R330 R7415 R430 R6415 R530 C6420 R630 FC 640 R730 M640 R730xd M640-VRTX R830 FD332 R930 R440 T130 R540 T330 R640 T430 R740 T630 R740xd R940 T440 T640 Coexistence of OpenManage Server Administrator and iDRAC Service Module In a system, both OpenManage Server Administrator (OMSA) and iDRAC Service Module can coexist.
Accessing documents from the Dell EMC support site You can access the required documents using the following links: • • • • • • • • For Dell EMC Enterprise Systems Management documents — www.dell.com/SoftwareSecurityManuals For Dell EMC OpenManage documents — www.dell.com/OpenManageManuals For Dell EMC Remote Enterprise Systems Management documents — www.dell.com/esmmanuals For iDRAC and Dell EMC Lifecycle Controller documents — www.dell.
2 Preinstallation setup Ensure that you assess the following before installing the iDRAC Service Module: • • yx3x servers or later. For the list of supported platforms, see Supported Platforms Minimum firmware version— • • • • • • For iDRAC 8 - 2.70.70.70 • For yx4x servers with iDRAC 9 - 3.36.36.36 • For yx5x servers with iDRAC 9 - 3.40.40.40 (For R6515 and R7515) and 3.42.42.42 (For R6525 and C6525) Administrator privileges. Read the installation instructions for the operating system.
Supported platforms on Linux operating systems The table lists the platforms that are supported by iDRAC Service Module 3.4.1 on Linux operating systems. Table 3. Supported platforms on Linux operating systems Dell EMC Devices Ubuntu 18.04.2 yx5x generation of PowerEdge Servers Yes yx4x generation of PowerEdge Servers X yx3x generation of PowerEdge Servers X RHEL 8.0 RHEL 7.6 Yes Yes X Yes X Yes Supported platforms iDRAC Service Module 3.4.1 supports yx3x, yx4x and yx5x servers.
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.
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. After the installation is complete, iDRAC shows that the Service Module as Installed and displays the last installed date. NOTE: The installer is available in the Host OS for 30 minutes.
NOTE: You can also create a custom group in the Application and Services Log folder by selecting the Custom option in the Lifecycle Controller Log Replication window. c) Select the authentication mode to enable WSMan remotely and also choose to install a self-signed certificate if the authentication certificate is not found. Provide a WINRM port number to establish the communication. By default, the port number is 5986. 5.
5. Especifique la ubicación donde necesita que se repliquen los registros de LC. De manera predeterminada, la opción Típica (Registros de Windows/Sistema) está seleccionada y los registros de LC se replican en el grupo Sistema de la carpeta Registros de Windows y en el Visor de sucesos. Haga clic en Siguiente.
NOTE: You can view the iDRAC Service Module logs in the Application group of the Windows Logs folder in the Windows Event Viewer. Installing iDRAC Service Module on supported Linux operating systems The complete iDRAC Service Module is packaged in a single Red Hat Package Manager (rpm). The package, accompanied by a shell script can install, uninstall, or enable/disable the features available. As the Installer on Linux is a single rpm install, there is no granular install support.
Executable Commands Package Name curl libcurl openssl libssl Installing The iDRAC Service Module on Linux operating system 1. The available features that can be installed are displayed on the screen.
Table 8.
The iDRAC Service module is available as a .zip file for installing on systems running VMware ESXi operating system. The .zip file follows the naming convention ISM-Dell-Web-3.4.1-.VIB-i-Live.zip, where is the supported ESXi version. The zip files for the supported ESXi versions are: • For ESXi – ISM-Dell-Web-3.4.1-.VIB-ESX6i-Live.zip NOTE: The feature configuration of iDRAC Service Module is not retained as is after a forced/ungraceful reboot.
13. Click Scan and select Patches and Extensions (if not selected by default) and click Scan. 14. Click Stage, select created Host Extension and follow the instructions. 15. Click Remediate and follow the instructions once the staging is completed. iDRAC Service Module installation is complete. NOTE: For more information on VMWare Update Manager, see the VMWare official website. NOTE: You can install iDRAC Service Module from the VUM repository https://vmwaredepot.dell.com/.
7. Copy the ESXi zip file on ESXi host to /vmfs/volumes/ISM-Dell-Web-3.4.1-.VIB-I directory. 8. Unzip the zip file in the above specified directory. 9. Run the following command in Power CLI. For ESXi 6.7 Install-VMHostPatch -VMHost - HostPath /vmfs/volumes/ name>/ISM-Dell-Web-3.4.1-.VIB-i/ cross_oem-dell-dciSMesxi_3.4.1.ESXi670-0000-metadata.zip . For ESXi 6.5 Install-VMHostPatch -VMHost
PAGE 224 Configuración del módulo de servicio del iDRAC Puede configurar el módulo de servicio del iDRAC mediante: • • • Interfaz web del iDRAC Comando de la CLI de RACADM Comando WSMAN Temas: • • • 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 yx3x servers, go to Overview >
Configuring the iDRAC Service Module from WSMan The iDRAC Service Module can be accessed and configured through WSMan using the command To configure the iDRAC Service Module use winrm i ApplyAttributes http://schemas.dmtf.
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.
Remote iDRAC hard reset iDRAC may become unresponsive due to various reasons. iSM can fully reset an unresponsive iDRAC8 or iDRAC9 controller by temporarily removing power to the iDRAC controller without affecting operating system production. This feature can only be disabled from the iDRAC Service Module page in iDRAC using any of the iDRAC interfaces. To reset iDRAC, use the following Windows PowerShell or Linux shell command: .
NOTE: You can use the In-band SNMP feature on yx3x Servers or later with a minimum iDRAC firmware version 2.30.30.30. For more information, see In-Band iDRAC SNMP Alerts whitepaper. Enable WSMan Remotely Currently with the WMI information feature, you can connect to the host Microsoft Windows WMI namespace to monitor the system hardware. The WMI interface on the host is enabled by default and you can access it remotely.
cable to reset the hardware running on auxiliary power. Forcing someone to physically unplug/plug the power cables leads to a significant cost and hassle for customers and support personnel. The FullPowerCycle feature enables the administrator to connect or disconnect the auxiliary power remotely without visiting the data center. This feature is supported on and after yx4x servers. When a Full Power Cycle Request is issued through this interface, the system power is not immediately affected.
• • • Open Closed Submitted Support Assist Overview You can view the Service Contract details such as Contract Type and Expiration Date and the Automatic Collection settings details in this session. On the Service Requests tab, you can also view the list of requests created and the status, description, source, service request ID, date opened, the date closed, and so on.
• • OS and Application Data Debug Logs You can also perform the SupportAssist collection function from an operating system shell to a specified file path using: ./ Invoke-SupportAssistCollection [--filepath/-f] NOTE: This shell command is only supported on iDRAC9 in the yx4x servers and later and if logged into the operating system as an administrator. NOTE: On Windows Core OS, user will have to go to the absolute path to execute the InvokeSupportAssistCollection.exe command.
• • Yes No You can also select the language preference. The available languages are: • • • • • • English German French Japanese Spanish Simplified Chinese Automatic Collection By default, the automatic collection feature is enabled.
7. Click iDRAC Service Module Setup. 8. Under Monitoring session, view that SNMP Get via Host OS option is enabled. 9. Open a new ‘PuTTY Configuration’ window, provide your Host Name IP address and click Open. 10. Click Yes, for the PuTTY Security Alert. 11. Log in to iDRAC using the proper credentials. 12. Type racadm get iDRAC.ServiceModule.HostSNMPGet and enter. You can view that HostSNMPGet is enabled.
Single sign-on (SSO) to iDRAC GUI from Host OS administrators desktop Overview Starting iSM 3.4, host administrators will have an option to launch iDRAC from within the host OS. iDRAC SSO launcher requires a desktop environment of the host OS. NOTE: Non-administrators cannot access this feature on the host OS. The single sign-on (SSO) feature enables an authenticated OS administrator to directly access the iDRAC web interface without requiring login of separate iDRAC administrator credentials.
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.
Both iDRAC and the Host TLS versions should be 1.1 or above. Communication between iSM and iDRAC fails if the TLS protocol version negotiation fails. If iSM with TLS capability is installed on an iDRAC firmware which does not support TLS communication over USBNIC, it will work with the non-TLS channel as in the older versions of iSM. NOTE: If iSM is installed or upgraded to version 3.4.0 or later before iDRAC is upgraded to version 3.30.30.
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.
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 yx3x or later server. Also make sure that you have a 64-bit system. I see the messageThe iDRAC Service Module is unable to communicate with iDRAC using the OS to iDRAC Pass-through channel in the OS log, even when the OS to iDRAC Pass-through over USBNIC is configured properly.
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.
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.
In case, the OS-to-iDRAC Passthru is disabled in iDRAC, the user will see a blank terminal when iDRAC GUI is launched from the Linux OS such as RHEL 7.6 and RHEL 8.0. Select y or Y, and press Enter to indicate configuration of USBNIC interface on the Host OS. Alternatively, you can enable the OS-to-iDRAC Passthru in iDRAC in USBNIC mode and re-run the iDRAC launcher from the Host OS.
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 7 SYSMGMT\iSM\linux\RHEL7\x86_64\dcism-3.4.1.el7.x86_64.rpm Red Hat Enterprise Linux 8 SYSMGMT\iSM\linux\RHEL8\x86_64\dcism-3.4.1.el8.x86_64.rpm Ubuntu 18 SYSMGMT\iSM\linux\Ubuntu18\x86_64\dcism-3.4.1.ubuntu18.
