Dell System E-Support Tool Version Release Notes

Transcription

1 Dell System E-Support Tool Version Release Notes

2 Release Notes Dell System E-Support Tool Dell System E-Support Tool (DSET) is a utility that collects configuration and log data from the target server for various chassis hardware, storage, and operating system components of a Dell PowerEdge server. DSET application generates a System Configuration Report, which consolidates the gathered data into a.zip file that can be automatically or manually uploaded to Dell Technical Support. Note: For the latest release notes, go to and click Dell System E- Support Tool Version Version DSET Release Date September 2014 Previous Version DSET Importance RECOMMENDED: Dell recommends applying this update during your next scheduled update cycle. The update contains feature enhancements or changes that will help keep your system software current and compatible with other system modules (firmware, BIOS, drivers and software). Platform(s) Affected Not applicable. What is Supported? Supported Devices DSET application supports the following systems: Storage Systems: PowerVault DL2000, DL2100, DL2200, and PowerVault NX. Rack Systems: PowerEdge R720, R720xd, R620, R320, R420, R520, R820, R200, R210, R210II, R300, R310, R410, R415, R510, R515, R610, R710, R715, R805, R810, R815, R900, R905, R910, 1950, 1955, 2950, 6950, and Blade Systems: PowerEdge M620, M420, M520, M820, M600, M605, M610, M610X, M710, M710HD, M805, M905, M910, M820, and M915. Tower Systems: PowerEdge T620, T320, T420, T100, T105, T110, T110II, T300,T310, T410, T605, T610, T710, 1900, and CloudEdge Systems: PowerEdge C1100, C2100, C6100, C6105, and C6145. PowerVault: MD1000, MD1120, MD1200, MD1220, MD1400, and MD1420.

3 Supported Web Browsers DSET supports the following Web browsers: Internet Explorer 7.0 and later versions for viewing the reports in windows platform. Supported Operating System List DSET and Remote Provider Installation and report collection (local and remote) is done from the following operating systems: DSET Microsoft Windows Server 2003 (32-bit and 64-bit) Microsoft Windows Server 2003 R2 (32-bit and 64-bit) Microsoft Windows Server 2008 (32-bit and 64-bit) Microsoft Windows Server 2008 R2 Microsoft Windows Small Business Server 2011 (64-bit) Microsoft Windows Server 2012 VMware ESX 4.0 VMware ESX 4.1 Red Hat Enterprise Linux 5 (32-bit and 64-bit) Red Hat Enterprise Linux 6 (64-bit) Red Hat Enterprise Linux 7 (64-bit) SUSE Linux Enterprise Server 10 (64-bit) SUSE Linux Enterprise Server 11 (64-bit) CentOS 6.2 (64-bit) CentOS 6.3 (64-bit) CentOS 6.4 (64-bit) Citrix Xen Server 6.2 (32-bit) Citrix Xen Server 6.2 (32-bit) Oracle Enterprise Linux 6.4 (64-bit) Oracle Virtual Machine 3.2 (64-bit) Installation and remote report collection is done from the following client operating systems: Microsoft Windows XP Microsoft Windows Vista Microsoft Windows 7 Microsoft Windows 8 Remote report collection from the following operating systems is done when DSET is installed in Windows/Linux: VMware ESXi 4.0 VMware ESXi 4.1 VMware ESXi 5.0

4 VMware ESXi 5.1 VMware ESXi 5.5 NOTE: 1. To collect hardware and storage data from ESXi remotely, install supported OpenManage Server Administrator version on the target system. 2. DSET application cannot be installed on a system with Server Administrator version lower than DSET application (64-bit) cannot be installed on a 64-bit Linux system with Server Administrator version lower than Only DSET application (32-bit) can be installed on ESX 4.x systems. What s New Support for Dell s 13th generation PowerEdge Express Flash Peripheral Component Interconnect Express (PCIe) solid-state device (SSD) for the following operating systems: - Red Hat Enterprise Linux Version Red Hat Enterprise Linux Version SUSE Linux Enterprise Server 11 Service Pack 3 (SP3) Support for the following new operating systems: - Red Hat Enterprise Linux Version VMware ESXi 5.5 U2 - Citrix XenServer 6.2 Service Pack 1 (SP1) Support for the following new hardware platforms: PowerEdge T630, R630, R730, and R730 XD. Support for the following PowerEdge RAID Controllers (PERCs): H330, H730, H730P, H830, and S130. Support for the following non-raid Serial Attached SCSI (SAS) controller: SAS 12 Gbps Host Bus Adapter (HBA). Support for PowerVault MD1400 and MD1420. Support for Integrated Dell Remote Access Controller 8 (idrac8) Version Support for OpenManage Server Administrator version Important Notes Report Collection Prerequisites For report collection from idrac7 (out of band), the idrac7 firmware version must be or later. For report collection from OpenManage Server Administrator namespace, the OpenManage Server Administrator services must be running. For remote report collection, SSH should be enabled on the target system on systems running Linux. Known Issues Issue 1 (DSET-47):

5 On T110 II systems with Windows 2008 SP2 x64 bit operating system, the slot information for external controller (PERC 6E) is displayed as Embedded under Storage->Dell PERC 6E Controller. Issue 2 (DSET-50): Network information under Software -> Linux OS section may be missing for PowerEdge M910 systems running RHEL 6.1. Most networking information can be found under the Chassis -> Network section instead. Issue 3 (DSET-46): The NX4 configuration is not sent if you run a collection for NX4 without root credentials and the send full collection option is cleared. Make sure that the "send full collection" option is selected before running a collection for NX4 without root credentials. Issue 4 (DSET-51): Software -> Linux OS -> Display information is not available from a RHEL bit system due to changes in xorg.conf. Issue 5 (DSET-77): For Windows 2008 operating systems, the Hotfix Install date is not displayed correctly in the DSET report > Software section > Installed applications page. : Issue 6 (DSET-1117):

6 On modular server, CD/DVD ROM connected through external USB enumerates under Storage does not show proper device information like Device Location, Parent Location etc. Issue 7 (DSET-1124): Few attributes missing for the Storage Array Disk in idrac Namespace Report. Issue 8 (DSET-941): In the OpenManage Server Administrator namespace report, in the Error Summary Information table, data in the Location column is automatically generated by using a predefined format, which can be interpreted only by having prior knowledge about the format. The format used to display the location is: <Controller name> <Enclosure name> <PCIe slot number>:<global number>:<channel>: <Enclosure ID>: <Index> For example, PERC H810 Adapter MD :1:0:0:2 Issue 9 (DSET-2349): "Total Maximum Capacity" value is mismatch with OMSA report data on R820 running on ESX 4.1U3 Issue 10 (DSET-1597, 1598): During the silent installation mode, if a later version of DSET is present on the server, and if you try installing the earlier version of DSET on the server, the downgrade process will not get blocked, but two versions of DSET will exist on the server. DSET 3.4 to DSET 3.6

7 Issue 11 (DSET-1756): On systems running on Windows, Windows Activation status has been deleted from Software information page of DSET report, because it is being reported incorrectly. DSET 3.x Issue 12 (DSET-1759): NIC teaming information is not enumerated under Network class in DSET namespace report on Systems with Windows 2012 R2. Partial NIC teaming data is present on Network page under Software section of report. DSET 3.6, Win2k12 R2 Issue 13 (DSET-1950): In DSET namespace report,under Network page, Duplex value is showing as "Unknown" instead of "Full". DSET 3.6, R220/R920 Issue 14 (DSET-2031): Hardware logs are not displayed for idrac namespace report. DSET 3.6, M820 Issue 15 (DSET-2296): Incomplete remote report getting generated in case of Modular server with SLES 11 SP3. Provide root\dsetcim in namespace parameter explicitly from command line DSET 3.6, Modular Servers/SLES 11 SP3 Issue 16 (DSET-1925):

8 On Windows 2012 R2, Network IRQ and Base Memory Address values missing on DSET namespace report. DSET 3.6, Windows 2012 R2 Issue 17 (DSET-1767): In DSET namespace report, BIOS Setup page shows 'Error Command successful' when the system is debranded (without Dell & OEM BIOS). DSET 3.6 Issue 18 (DSET-2172): On Windows 2012 R2, S110 controller information may not get enumerated in DSET namespace report because of some limitation in communicating with controller drivers. DSET 3.6 Issue 19 (DSET-2347): If IPV6 kernel module is not enabled before DSET installation, then DSET display the following message: "Dell System E-Support Tool 3.x installed on this system, may not function properly as the system does not have the ipv6 kernel module enabled." This message does not have any impact on DSET functionality. ESX Issue 20 (DSET-2676): On Linux Operating Systems, if SELinux is in Enforced mode and DSET installation or report collection is attempted, "'cimprovagt' is killed by signal 11" messgae is displayed. DSET 3.7 Issue 21 (DSET-2847):

9 On Linux Operating Systems, when higher version of srvadmin-hapi, srvadmin-storelib-sysfs, or sblimsfcb is installed by DSET, OMSA will not be installed if it is having lower version of either of the above packages. DSET 3.7 Issue 22 (DSET-2714): Unable to install DSET if OMSA is already present on Red Hat Enterprise Linux 7.0 Operating Systems. DSET 3.7 Issue 23 (DSET-2172): On Windows 2008 Operating Systems, Software Raid S110 & S130 Controller is not enumerating in DSET report. DSET 3.7 Limitations Issue 1 On Linux operating system (RedHat Enterprise Linux 5.x and 6.x), if SFCB package rpm is installed using "Dell Systems Management Tools and Documentation DVD", then DSET installation is unsuccessful. Upgrade to the SFCB from Operating System media, using the command "rpm -Uvh sblim-sfcb-*.*" and re-install DSET and then generate the Report Issue 2: On Linux machines if the root user is not configured to use remote network (HTTP or HTTPS service) for OpenPegasus, hardware and storage information is not collected in the report.

10 Issue 3: DSET on Linux cannot collect a remote report through the OpenManage Server Administrator namespace. Issue 4: On Linux systems, if SFCB is installed using Open Manage Server Administrator DVD and then DSET application is installed, DSET report collection fails. Restart SFCB service on the system, and then generate the report. Issue 5: Bios -> Bios Setup page will not be available when a normal user under root group attempts to collect Windows to Linux remote DSET application report from OpenManage Server Administrator Snamespace. : Issue 6: When only DSET is installed, the report is not collected when using Start menu > Create Advanced DSET Report or Create Basic DSET Report. Issue 7: On ESX 4.1 Operating System, less firmware data is collected. To collect full firmware data, usbarbitrator service should be stopped.

11 Issue 8: On Windows 2008 operating system (standard, enterprise, and core), if DSET application version 3.3 and above is currently in the system, it cannot be upgraded to a later version. Uninstall the already installed version of DSET and install the later version. Issue 9: In the DSET namespace report, the System Location is not displayed in the Main System Chassis page, if the location is modified. Issue 10: On Linux target system, more than one simultaneous report collection is not supported. Issue 11: On 12G Platforms, CSIOR (Collect System Inventory On Restart) must be enabled to get modified attributes after last restart. Issue 12: For OpenManage System Administrator report collected from any system having System Administrator version 6.5 or lower, the Array Disks page is not displayed correctly under the corresponding Enclosure. However, it is displayed under the Connector to which the Enclosure is connected.

12 Issue 13: In the DSET namespace report, the value of "System Reset Timer" attribute in "Auto Recovery" class modified in OpenManage Server Administrator is not displayed. Issue 14: On 9G and 10G Servers, Remote Access Logs are not collected when OpenManage Server Administrator Remote Access Controller (RAC) Component is not present. Issue 15: Windows Unified Data Storage Server 2003 R2 Enterprise 64-Bit is displayed as Windows 2003 Enterprise 64-Bit, as Unified Data Storage Server information is not available through any WMI class or through any registry entry. Issue 16: Fewer Dell logs are collected on the ESXi Operating System. Issue 17: Attribute collection data will vary in the report when DSET version and Remote Provider version are different. Issue 18 (DSET-959):

13 An unexpected error message is displayed while extracting a Linux-based report. MS-Windows is unable to process the request because the file name has a colon (:). Install either 7-zip or WinRAR, and then save the file. These software applications convert a colon (:) to an underscore (_). Issue 19: idrac namespace report collection is not supported for idrac 7 with Basic Management license. Issue 20: In the report collected using DSET namespace for any system with Red Hat enterprise Linux 6.2, the Broadcom BCM GB NIC is enumerated as Broadcom BCM GB Port 10 GB NIC Issue 21 (DSET-696): On OEM Server, DSET may not support collection of Remote Access Log as part of report collection Only OEM Servers. Issue 22 (DSET-1099): DSET report from idrac will have fewer data when PERC H800 card is connected on 12G systems. Issue 23 (DSET-1133):

14 On Windows 64 bit System DSET Upload fails when System wide proxy is set using netsh command. Run the netsh command to set the system wide proxy "netsh winhttp set proxy x.x.x.x" from 32bit command prompt (c:\windows\syswow64\cmd.exe) and then try the upload operation. Windows 64 bit Issue 24: When DSET is installed in a linux System then even if the dset providers are registered to tog-pegasus cimom, the providers show the dependency to the sfcb cimom due to which the uninstallation of sfcb would fail. Uninstall sfcb with --nodeps option "rpm -e --nodeps sblim-sfcb-*.rpm". Issue 25: In idrac namespace report, under Storage > Controller > Battery page, "Predicted Capacity Status" is always displayed as "Unknown". Issue 26: On Oracle Virtual Machine Server OS, if you collect advanced logs, Remote Access Controller logs will not be available. DSET 3.6.0, Oracle Virtual Machine OS Issue 27: On systems running on Linux, where only OpenManage Server Administrator and DSET client are installed, DSET report collection will prompt for root password if no namespace is mentioned. Issue 28 (DSET-2186):

15 Fewer firmware data is displayed in DSET report on Oracle virtual machine operating system. Issue 29: Storage data will not available in DSET report collected from ESX-SMASH namespace. Issue 30: On all supported servers and operating systems, if only DSET component is installed and advanced logs are gathered, then Remote Access Controller logs will be missing. Issue 31: On systems having Citrix Xen Server operating system, sfcb is not present by default. If the Dell OpenManage Server Administrator is present, sfcb is installed from OpenManage Server Administrator DVD with which DSET is non-functional. While trying to upgrade existing sfcb (sblim-sfcb-1.3.7) to sfcb from Red Hat Enterprise Linux 5.x operating system media, sfcb upgrades, but causes an error while installing or collecting DSET report because of known IPV6 issue in sfcb. Uninstall existing sfcb gracefully and install DSET. Issue 32: On ESXi 5.5 PCiE SSD is not supported because the micron driver blocks management command. Issue 33:

16 On Linux operating system, when DSET namespace report is collected on 11G or later, a message "Unable to mount MAS001" is displayed on the GUI. This message is displayed because, during the report collection DSET mounts and later unmounts the idrac partition to get the firmware data. Issue 34: Downgrade check is not present in DSET version and lower if only DSET Provider is installed. Issue number DSET-1101 fixed in DSET release. Issue 35 (DSET-2443): Citirix XenServer will not display the service pack information. Issue 36: In RHEL7 with tog-pegasus version remote access for the root user is not allowed. Issue 37: In RHEL7 with tog-pegasus version , the tog-pegasus service is not started after system restart. Issue 38: In RHEL7 tog-pegasus service may fail to start displaying the message "unable to access trust store /etc/pegasus/cimserver_trust".

17 Installation Prerequisites For windows You need to be logged in as a local or Domain Administrator. To Install DSET on Microsoft Windows Server 2008 or later, Microsoft Windows Vista or newer, run the DSET installer with elevated privileges using "Run As" option. To install Remote Provider, Windows Management Instrumentation (WMI) service must be running. For Linux If WMI is stopped, DSET starts WMI automatically and continues with installation. If WMI is disabled, installation of DSET terminates with an error message. You need to be logged in as the root user. Enable SSH services for remote report collection from Linux systems. Make sure that the user credentials supplied for remote report collection can initiate SSH connection and have root privileges. NOTE: For Linux CIMOM, the default port 5988 (for http) or 5989 (for https) is used by the system to install Remote Provider. If custom ports are used, update the configuration file available at /opt/dell/advdiags/dset/config/dset.cfg. For silent installation: On Linux Operating system for Silent installation of DSET application, CIMOM (SFCB or Open Pegasus) should already be installed. To install SFCB: 1. Locate the SFCB rpm from the Operating System Media. 2. Install SFCB rpm using "rpm -ivh sblim-sfcb-*.rpm" 3. Try to perform DSET silent installation. To install Top-Pegasus: 1. Locate the Tog-Pegasus rpm from the Operating System Media. 2. Install Tog-Pegasus using "rpm -ivh tog-pegasus-*.rpm" 3. Start the Pegasus services. 4. Try to perform DSET silent installation. Probable reasons for provider installation failure The DSET installation or collection is blocked on Red Hat Enterprise Linux operating system and CentOS, because the SELinux option is enabled by default. Modify the security enforce feature using the command, setenforce 0. Credential-less CIMOM authentication

18 When installing the DSET or collecting DSET report using DSET version and earlier, you must enter password at the command line interface on systems running Linux. If the credentials are correct and the CIMOM (SFCB or OpenPegasus) authenticates, the installation or report collection process is successfully completed. From DSET version and later, DSET supports single sign-on for the logged-in user. That is, DSET does not anymore require a password for its functioning. CIMOM accepts a client certificate while establishing the HTTPS connection. If the certificate is signed by a trusted authority, a network connection is started. During installation, DSET generates and deploys its own certificate and key which is used later. The access to these files is limited only to the root user. A brief description about the DSET installation or report collection process: 1. Collecting DSET report without providing any username or password: DSET tries for CIMOM connections through certificates. 1. If the connection is successful, the report collection continues without prompting for a password. 2. If the connection is unsuccessful, DSET asks whether or not you want to provide password and continue. If you choose to continue, DSET prompts you to enter root password and proceed. If you decide not to proceed, credential-based authentication is not performed. 2. Collecting DSET report by providing username and/or password, DSET will not try for a certificate-based connection and prompts for a password (if not entered). Note: The tasks mentioned earlier in Credential-less CIMOM Authentication On Systems Running Linux section are also applicable for DSET installation only when CIMOMs are pre-installed and operational. Possible Reasons For Unsuccessful Certificate Connection The following are the possible reasons for unsuccessful certificate connection: DSET client certificate has expired. By default, the certificate is valid for one year from the time of generation. A particular version of operating system or CIMOM does not support certificate-based Authentication. DSET does not perform the certificate-based connections because there are known issues with a particular version of operating system or CIMOM for certificate-based authentication. DSET client certificate or CIMOM Trust Store is corrupted. Limitations The following are the limitations: The credential-less authentication does not work on ESX. Therefore, DSET requires the credentials to run on ESX. For credential-less authentication, the minimum supported version of Tog-pegasus is and that of SFCB is In case, the server has CIMOM versions earlier than the versions specified, you will be prompted for a password. Installation Instructions For instructions on installation, advanced command-line installation, and error codes refer to the DSET Installation Guide. The PDF format is available at:

19 The text format is available at: <INSTALLEDDIRECTORY>\AdvDiags\DSET\ Open Source Library The lists of open source libraries used are: Python OpenSSL 0.9 PyWBEM Zip 4.65 Plink for Windows Plink for Linux Pscp 0.62 Libxml Libxslt sblim-sfcb python cmpi-bindings sblim-indication_helper sblim-cmpi-base cim-schema 2.19 The modified open source libraries are available at the following location: Upgrade Not applicable Uninstallation Not applicable Contacting Dell Note: If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog. Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer service issues: 1. Visit 2. Select your support category. 3. Verify your country or region in the Choose a Country/Region drop-down menu at the top of page. 4. Select the appropriate service or support link based on your need. Accessing Documents From Dell Support Site You can access the required documents in one of the following ways: From the following links:

20 a. For all Systems Management documents dell.com/softwaresecuritymanuals b. For Remote Enterprise Systems Management documents dell.com/esmmanuals c. For Enterprise Systems Management documents dell.com/openmanagemanuals d. For Client Systems Management documents dell.com/omconnectionsclient e. For Serviceability Tools documents dell.com/serviceabilitytools f. For OpenManage Connections Enterprise Systems Management documents dell.com/omconnectionsenterprisesystemsmanagement g. For OpenManage Connections Client Systems Management documents dell.com/omconnectionsclient From the Dell Support site: a. Go to dell.com/support/manuals. b. Under section, click Software & Security. c. In the Software & Security group box, click the required link from the following: - Serviceability Tools - Enterprise System Management - Client System Management - Remote Enterprise System Management d. To view a document, click the required product version. Using search engines: - Type the name and version of the document in the Search box Copyright 2014 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. Dell and the Dell logo are trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.