Support Live Image
Version 2.0 User's Guide
Notes, Cautions, and Warnings
NOTE: A NOTE indicates important information that helps you make better use of your computer.
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.
Copyright © 2014 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property
laws.
mentioned herein may be trademarks of their respective companies.
2014 - 1
Rev. A01
™
and the Dell logo are trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names
Dell
Contents
1 Overview.......................................................................................................................................5
New In This Release.................................................................................................................................................5
Supported Devices................................................................................................................................................... 5
Minimum Hardware Requirements...........................................................................................................................6
Tools Available......................................................................................................................................................... 6
Other Documents You May Need............................................................................................................................. 6
2 Using Support Live Image..........................................................................................................7
Creating A Bootable Support Live Image USB Key On Systems Running Windows................................................7
Creating A Bootable Support Live Image DVD On Systems Running Windows.......................................................7
Starting The Server...................................................................................................................................................8
Starting From a DVD Or an USB drive Key......................................................................................................... 8
Booting To The Virtual Drive.............................................................................................................................. 8
Boot Options............................................................................................................................................................. 9
Using The MS-DOS-Based Tools..............................................................................................................................9
Running The MP Memory Test...........................................................................................................................9
Running The GUI–based 32-Bit Diagnostics.................................................................................................... 10
Running The Loop Memory Test...................................................................................................................... 10
Setting The Asset Tag...................................................................................................................................... 10
Clearing The Single-Bit Memory Error Log...................................................................................................... 11
Using The Linux-Based Tools And Utilities.............................................................................................................11
Starting OpenManage Server Administrator................................................................................................... 11
Running Dell Systems E-Support Tool..............................................................................................................12
Installing the Dell 12th Generation iDRAC7 Evaluation License.......................................................................14
Dell PowerEdge C System Management Pack................................................................................................ 15
Running PE-C Support Logs Script...................................................................................................................16
Starting Dell OpenManage Server Update Utility............................................................................................ 17
Sharing Files Using Samba Share Service.......................................................................................................17
Testing Network Connectivity..........................................................................................................................18
Assigning A Static IP Address And Default Gateway......................................................................................18
Generating The PCI Devices List......................................................................................................................19
Clearing ESM Logs (Dell 9th Generation And Later Servers Only)...................................................................19
Clearing The SBE Log.......................................................................................................................................19
Accessing And Remounting The Local File System.........................................................................................20
Mounting A USB Drive..................................................................................................................................... 20
Copying Files To A USB Drive.......................................................................................................................... 21
Starting The Vim Editor.....................................................................................................................................21
Starting gedit....................................................................................................................................................21
Starting The Hex Editor.................................................................................................................................... 22
Using TightVNC................................................................................................................................................ 22
Using WinSCP.................................................................................................................................................. 22
Useful Commands............................................................................................................................................ 23
1
Overview
Support Live Image (SLI) is a CentOS 6.2 image that packages a collection of utilities and diagnostic tools for Dell
PowerEdge servers, Dell PowerEdge C servers, and Dell PowerVault storage systems. It provides an environment for the
tools to run to troubleshoot hardware-related issues and gather system configuration information. The results of the
diagnostic tests and configuration information are sent to the technical support team to identify and resolve an issue.
Support Live Image is primarily used by Dell Service Providers (DSP), and in some cases, customers instructed by the
Dell Technical Support.
If a Dell customer contacts Dell Technical Support for a hardware issue that requires a part replacement, the
replacement part is dispatched to the customer through the DSP. After replacing the part, if the DSP finds that the issue
is not fixed, the DSP works with technical support to troubleshoot and resolve an issue.
New In This Release
The following are new in this release:
• Dell OpenManage Server Administrator version 7.3
• Dell System E-Support Tool version 3.5.1
• Dell 12th Generation iDRAC7 Evaluation License Tool version 1.50.50
• Support for Dell Poweredge C platforms
• System Management Pack for PowerEdge C platforms
– setupbios
– bmc tool
– ldstate
• PE-C logs for PowerEdge C platforms
• Support for Dell OpenManage Server Update Utility (SUU) version 7.3
• Support for Using Samba Share
• Removed support for 8G platforms and Dell Online Diagnostics
Supported Devices
Support Live Image supports the following devices:
• Dell 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, 2970, M620, M420, M520, M820, M600,
M605, M610, M610X, M710, M710HD, M805, M905, M910, M820, M915, T620, T320, T420, T100, T105, T110, T110II, T300,
T310, T410, T605, T610, T710, 1900, and 2900) and PowerEdge C (C1100, C2100, C5220, C6100, C6105, C6145, C6220,
C6220II, C8220, C5125, and C6105) servers
• Dell PowerVault NX and PowerVault MD SCSI (DL2000, DL2100, and DL2200) direct-attached storage arrays
NOTE: Support Live Image provides limited support for Dell PowerEdge C servers.
5
Minimum Hardware Requirements
To use Support Live Image, the system should have a minimum of 6 GB RAM. For optimal use or functionality, at least 8
GB of RAM is recommended.
Tools Available
The following table lists the diagnostic and configuration tools available on Support Live Image.
Table 1. Tools Available on Support Live Image
MS-DOS-Based Tools Linux-Based Tools
• Dell 32–Bit Diagnostics
• Dell MP Memory
• Dell Asset Tag Utility
• Dell OpenManage Server Administrator (OMSA)
– Version 7.3 for Dell 9G and later servers
• Dell System E-Support Tool (DSET)
– Version 3.5.1 for Dell 9G and later servers
• Dell 12G iDRAC7 Evaluation License Tool version 1.50.50
• Dell PowerEdge C System Management Pack
– setupbios
– bmc tool
– ldstate
• PEC-logs for PowerEdge C servers
Other Documents You May Need
The User’s Guide and release notes related to Dell OpenManage Server Administrator, Dell System E-Support Tool, Dell
OpenManage Server Update Utility, MS-DOS-Based Tools, iDRAC Evaluation License, and PowerEdge C System
Management Pack is available in the User_Guides_and_Release_Notes folder that is available on the Support Live
Image desktop.
The
Support Live Image Release Notes
tools available on the image.
In addition to this guide, you can access the following guides available at support.dell.com. On the Support page, click
Software & Security and then click Remote Enterprise Systems Management or Serviceability Toolsor Enterprise
System Management. Click the appropriate product link to access the documents.
available on the SLI desktop, provides details about the supported devices and
6
Using Support Live Image
This chapter provides information about using the Support Live Image to run diagnostic tools and gather configuration
information.
To use the Support Live Image to start the server and run the diagnostic tools, you must create a bootable DVD or USB
key. For more information about using a bootable DVD or USB, see:
• Creating a Bootable Support Live Image USB Key On Systems Running Windows
• Creating a Bootable Support Live Image DVD On Systems Running Windows
Creating A Bootable Support Live Image USB Key On Systems Running Windows
It is recommended that you create the Support Live Image bootable USB key using Fedora Live USB Creator. However,
you can also use any other tool available for creating a bootable USB key.
To create a bootable Support Live Image USB key:
1. Download Fedora LiveUSB Creator available at https://fedorahosted.org/liveusb-creator/ and install it on your
system.
2. Insert a USB key with a minimum capacity of 4 GB into an available USB port on your system.
3. Click Start → All Programs → LiveUSB Creator.
4. Right-click LiveUSB Creator and select Run as administrator.
The Fedora LiveUSB Creator dialog box is displayed.
5. Under Use existing Live CD, click Browse.
The Select Live ISO dialog box is displayed.
6. Browse through and then select the Support Live Image (*.iso) file, and then click Open.
7. Under Target Device, select the USB key drive.
8. Click Create Live USB.
2
Creating A Bootable Support Live Image DVD On Systems Running Windows
You can use any image-burning tool available for creating a bootable DVD. The section provides instructions for creating
a bootable DVD using ImgBurn.
To create a bootable Support Live Image DVD:
1. Download ImgBurn available at http://imgburn.com and install it on your system.
2. Insert a writable DVD with a minimum capacity of 4.7 GB into the optical drive.
3. Click Start → All Programs → ImgBurn.
4. Right-click ImgBurn and select Run as administrator.
The ImgBurn dialog box is displayed.
7
5. Click Write image file to disc.
6. Under Source, click the browse icon.
7. In the Open dialog box, browse through to select the Support Live Image (*.iso) file, and then click Open.
8. Under Destination, select the appropriate DVD drive.
9. Click the write icon that is displayed at the bottom of the dialog box.
Starting The Server
To run the diagnostic tools and gather configuration information, you must start the server using the Support Live Image
USB drive key or DVD that you created. The methods of starting a server are:
• Starting from the USB drive key or DVD. For more information, see Starting From a DVD Or an USB drive Key.
• Starting by using a virtual media. For more information, see Booting To The Virtual Drive.
Starting From a DVD Or an USB drive Key
To start from a DVD or an USB drive key:
1. Insert the Support Live Image DVD or an USB drive key in the server.
2. Turn on the server.
3. When the F11 prompt is displayed on the screen, press the <F11> key.
The BIOS Boot Manager screen is displayed.
4. Select one of the following on the basis of the device you want to boot to:
– To boot to the DVD, select Optical Drive in the menu, and then press <Enter>.
– To boot to the USB key:
1. Select Hard Drive C: in the menu.
2. In the menu that is displayed, select the appropriate USB port, and then press <Enter>.
The server boots to the Support Live Image DVD or USB key and displays the automatic boot countdown timer.
5. Press any key before the automatic boot countdown timer reaches zero (0).
The Support Live Image welcome screen is displayed with a list of options. For more information, see Boot Options.
NOTE: If you do not press any key before the countdown timer reaches 0, the Support Live Image automatically
boots to the Linux-Based Diagnostic Tools (Dell 9G–12G servers) option.
Booting To The Virtual Drive
NOTE: The method of using virtual media varies across systems, depending on the DRAC or iDRAC and the version
of the firmware. For more information, see the DRAC or iDRAC User's Guide at dell.com/support/manuals.
1. Perform one of the following as applicable:
– Mount the Support Live Image (*.iso) file to the virtual media.
– If the Support Live Image DVD or an USB drive key is available, insert the DVD or an USB drive key into the local
system, and then mount the image to the DRAC on the remote system.
2. When the F11 prompt is displayed on the screen, press <F11>.
The BIOS Boot Manager screen is displayed.
3. Select Virtual CD and press <Enter>.
The server boots to the Support Live Image on the virtual media, displays the automatic boot countdown timer.
8
4. Press any key before the automatic boot countdown timer reaches 0.
The Support Live Image welcome screen is displayed with a list of options. For more information, see Boot Options.
NOTE: If you do not press any key before the countdown timer reaches 0, the Support Live Image automatically
boots to the Linux-Based Diagnostic Tools (Dell 9G–12G servers) option.
Boot Options
NOTE: When the system boots to the Support Live Image, the automatic boot countdown timer is displayed. To
view the boot options menu, you must press any key before the countdown timer reaches 0. If you do not press
any key before the countdown timer reaches 0, the Support Live Image automatically boots to the
Diagnostic Tools (Dell 9G–12G servers) option.
The following are the list of boot options:
• Linux-Based Diagnostic Tools (Dell 9G–12G servers) — Boots to the Community ENTerprise Operating System
(CentOS), an Enterprise-class Linux distribution.
• DOS-Based Diagnostics Tools (Dell 9G–10G servers) — Boots to MS-DOS and you can run MP Memory test, Loop
Memory test, Dell 32-Bit Diagnostics, and the Asset tool.
• DOS-Based Diagnostics Tools (Dell 11G servers) — Boots to MS-DOS and you can run MP Memory test, Loop
Memory test, Dell 32-Bit Diagnostics, and the Asset tool.
• DOS-Based Diagnostics Tools (Dell 12G servers) — Boots to MS-DOS and you can run the Asset tool.
NOTE: Dell 32-Bit Diagnostics, MP Memory test, and Loop Memory test is not supported on Dell 12G servers.
For more information on the diagnostic tools that you can run in the Linux and DOS environments, see Tools Available.
Linux-Based
Using The MS-DOS-Based Tools
This section provides information about using the MS-DOS-based tools included in the Support Live Image.
To use the MS-DOS-based tools and options available on the image, see:
• Running The MP Memory Test
• Running The GUI-Based 32-Bit Diagnostics
• Running The Loop Memory Test
• Setting The Asset Tag
• Clearing The Single Bit Error Log
Running The MP Memory Test
MP Memory is a Dell-developed, DOS-based memory test tool. Running MP Memory test, it tests the processors cache
memory and physical memory.
This tool is efficient for memory configurations greater than 4 GB. The tool supports single processor or multiprocessor
configurations and processors using Intel Hyper-Threading Technology. MP Memory operates only on Dell PowerEdge
servers that run on Intel processors.
NOTE: The MP Memory test may not be supported on some PowerEdge C servers.
9
To run the MP Memory test:
1. Boot the system using the DOS-Based Diagnostic Tools (Dell 9G-10G servers) or DOS-Based Diagnostic Tools (Dell
11G servers) option.
The Customer Diagnostic Menu Ver 1.6 message is displayed.
2. When the Enter option or letter is displayed, then press <1> key.
The MP Memory test is run. Follow the instructions on the screen to select the method of execution.
Running The GUI–based 32-Bit Diagnostics
Dell 32-Bit Diagnostics is an executable tool consisting of a graphical user interface (GUI) and test modules for
individual server subsystems. In addition to the GUI, Dell 32-Bit Diagnostics also offers a command-line interface (CLI) to
enable administrators to execute diagnostics using scripts or batch files
Dell 32-Bit Diagnostics can determine whether individual devices and subsystems are operating as expected. However,
the diagnostics provide only local control and output.
To run the 32-Bit Diagnostics:
1. Boot the system using the DOS–Based Diagnostic Tools (Dell 9G-10G servers) or DOS-Based Diagnostic Tools (Dell
11G servers)
The Customer Diagnostic Menu Ver 1.6 message is displayed.
2. When the Enter option or letter is displayed, then press the <2> key.
The 32-Bit Diagnostics is executed. Follow the instructions on the screen to select the type of test you want to
execute.
option.
Running The Loop Memory Test
The Loop memory test is to run the MP Memory test on loop to stress test the memory
To run the loop memory diagnostic test:
1. Boot the system using the DOS-Based Diagnostic Tools (Dell 9G-10G servers) or DOS-Based Diagnostic Tools (Dell
11G servers) option.
The Customer Diagnostic Menu Ver 1.6 message is displayed.
2. At the Enter option or letter prompt, press <3>.
3. At the Enter loops to test 0..254 prompt, type a value between 0 and 254.
The loop memory diagnostic test is executed.
Setting The Asset Tag
To set the asset tag:
1. Boot the system using the DOS-Based Diagnostic Tools (Dell 9G-10G servers), DOS-Based Diagnostic Tools (Dell
11G servers), or DOS-Based Diagnostic Tools (Dell 12G servers) option.
The Customer Diagnostic Menu Ver 1.6 is displayed.
2. At the Enter option or letter prompt, press <4>.
The MS-DOS prompt is displayed.
3. Type C:, and press <Enter>.
The working drive changes to C:\.
10
4. Type CD Util, and press <Enter>.
The working directory changes to C:\Util.
5. Type asset new_asset_tag, where new_asset_tag is the tag you want to assign to the system.
6. At the confirmation prompt, press <y>.
Clearing The Single-Bit Memory Error Log
You can clear or reset the Single-Bit Memory Error (SBE) log during and after troubleshooting. Clearing the SBE log
during troubleshooting enables you to capture new errors.
NOTE: Clearing the SBE log also clears the Embedded System Management (ESM) logs.
To clear the SBE log:
1. Boot the system using the DOS-Based Diagnostic Tools (Dell 9G-10G servers) or DOS-Based Diagnostic Tools (Dell
11G servers)
The Customer Diagnostic Menu Ver 1.6 is displayed.
2. When the Enter option or letter is displayed, then press the <4> key.
The MS-DOS prompt is displayed.
3. Type C:, and then press <Enter>.
The current drive changes to C:\.
4. Type mpmemory –ptech -tlogclr, and then press <Enter>.
option.
Using The Linux-Based Tools And Utilities
This section provides information about using the Linux-based tools included in the Support Live Image.
• Starting OpenManage Server Administrator
• Running Dell Systems E-Support Tool
• Installing The 12th Generation iDRAC7 Evaluation License
• Dell PowerEdge C System Management Tools
• Running PE-C Support Logs Script
This section provides information about using the Linux-based utilities included in the Support Live Image.
• Starting The Dell OpenManage Server Update Utility
• Using Samba Share
• Testing Network Connectivity
• Assigning A Static IP Address And Default Gateway
• Generating The PCI Devices List
• Clearing ESM Logs (Dell 9th Generation And Later Servers Only)
• Clearing The SBE Log
Starting OpenManage Server Administrator
Dell OpenManage Server Administrator (OMSA) provides a comprehensive, one-to-one systems management solution in
two ways: from an integrated, web browser-based graphical user interface (GUI) and from a command line interface
(CLI) through the operating system. Server Administrator enables system administrators to manage systems locally and
remotely on a network. It enables system administrators to focus on managing their entire network by providing
comprehensive one-to-one systems management.
11
To start OpenManage Server Administrator (OMSA):
1. Boot the system using the Linux-Based Diagnostic Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
2. Double-click the Launch Server Administrator icon. If you have already added OMSA to the web browser's security
exception, then go to step 6.
A new web browser window is displayed with the message: This Connection is Untrusted.
3. Click I Understand the Risks.
A disclaimer is displayed at the bottom of the page.
4. Click Add Exception.
The Add Security Exception dialog box is displayed.
5. Click Get Certificate, and then click Confirm Security Exception.
The OMSA login page is displayed.
6. In the Username field, type root.
7. In the Password field, type dell.
8. Click Submit.
The OMSA dashboard is displayed.
NOTE: For more information about using OMSA, see the
available in the User-Guides_and_Release-Notes folder that is available on the Support Live Image desktop.
NOTE: OMSA is not supported on PowerEdge C servers.
Dell OpenManage Server Administrator User's Guide
Running Dell Systems E-Support Tool
Dell System E-Support Tool (DSET) is a utility that collects configuration and log data for various chassis hardware,
storage, software, and operating system components of a Dell PowerEdge server and consolidates the data into a .zip
file.
You can run DSET using one of the following methods:
NOTE: For ease of copying the DSET collection report to a USB key, it is recommended that you run DSET using
the desktop icon.
• Running DSET Using The Desktop Icon
• Running DSET Using The Gnome Terminal
NOTE: For more information about DSET, see the
Guides_and_Release_Notes folder that is available on the Support Live Image desktop.
NOTE: DSET is not supported on PowerEdge C servers.
Running DSET Using The Desktop Icon
To run DSET:
Dell Systems E-Support Tool User's Guide
available in the User-
1. Boot the system using the Linux-Based Diagnostics Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
2. Double-click the DSET icon.
The DSET tool starts, the report is collected, and the message Press ENTER to exit is displayed.
3. Press <Enter>.
The DSET tool exits and the report is saved in /tmp/data folder.
12
4. To copy and paste the DSET collection report to a USB key:
a. Insert the USB drive. See Mounting An USB Drive.
b. Copy the DSET collection report to the USB drive. See Copying Files To An USB Drive.
5. To share the collection report with Dell technical support, use TightVNC or WinSCP. For more information, see
Using TightVNC or Using WinSCP.
Running DSET Using The GNOME Terminal
To run DSET:
1. Boot the system using the Linux-Based Diagnostics Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
2. Double-click the gnome-terminal icon.
The GNOME terminal window is displayed.
3. At the command prompt, type su –, and press <Enter>.
The Password prompt is displayed.
4. Type dell, and press <Enter>.
The root user command prompt is displayed.
5. Type dellsysteminfo and press <Enter>.
To collect the DSET report with report filtering, type dellsysteminfo –v yes /tmp/data.
To collect the DSET report from specific devices, use the -d hw,st,lg option, where hw indicates server, st
indicates storage, and lg indicates logs. For example, type dellsysteminfo -v yes -d hw, st,
lg /tmp/data
For more information about report filtering, see Report Filtering (Command Line Only).
The Please enter “root” password prompt is displayed.
6. Type dell and press <Enter>.
The DSET tool is executed and the collection report is saved in the /root folder.
7. To copy the DSET collection report to a USB key:
.
a. Mount the USB key. See Mounting An USB Drive.
b. Copy the DSET collection report to the USB key. See Copying Files To An USB Drive.
8. To share the collection report with Dell technical support, use TightVNC or WinSCP. For more information, see
Using TightVNC or Using WinSCP.
Report Filtering (Command Line Interface Only)
You can use the privacy option while executing DSET from the command line interface to filter the following data from
the DSET collection report:
• Host Name
• IP Address
• Subnet Mask
• Default Gateway
• MAC Address
• DHCP Server
• DNS Server
• Processes
• Environment variables
13
• Registry
• Logs
• iSCSI Data
• Fibre Channel data (host WWN and port WWN)
If you want to include any of the data to the report, specify ’no’ in the privacy_presetlist.cfg file available at /opt/dell/
advdiags/dset/config/.
Installing the Dell 12th Generation iDRAC7 Evaluation License
iDRAC7 is a systems management hardware and software solution that provides remote management capabilities,
crashed system recovery, and power control functions for Dell PowerEdge systems.
The Dell 12th Generation iDRAC7 evaluation license allows you to try and test certain Enterprise features for 30 days
before you purchase a permanent license. A status icon in the iDRAC graphical user interface (GUI) changes from green
color to yellow color five days before the license expires. Customers who require additional time to complete an
evaluation can obtain an extension of 30 days by contacting their account representative.
NOTE: Installing the Dell 12th Generation iDRAC7 evaluation license in a production environment is not
recommended.
You can install the 12th Generation iDRAC7 evaluation license by:
• Installing The Dell 12th Generation iDRAC7 Evaluation License Using The Desktop Icon
• Installing The Dell 12th Generation iDRAC7 Evaluation License Using The GNOME Terminal
NOTE: For more information about using Dell 12th Generation iDRAC7 evaluation license, see the
Remote Access Controller User’s Guide
the Support Live Image desktop.
NOTE: The Dell 12th Generation iDRAC7 evaluation license is not supported on PowerEdge C servers.
available in the User Guides and Release Notes folder that is available on
Integrated Dell
Installing The Dell 12th Generation iDRAC7 Evaluation License Using The Desktop Icon
To install the Dell 12th Generation iDRAC7 evaluation license:
1. Boot the system using the Linux-Based Diagnostic Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
2. Double-click the 12G_iDRAC7_Demo_License icon.
The following prompt is displayed on the GNOME terminal window: Do you want to install an
enterprise evaluation license that is valid for 30 days [Y/N]?
3. Press <Y> to install the license.
The license is imported and a warning message prompting to install a permanent license in 30 days is displayed.
4. At the, Press ENTER to exit prompt, press <Enter>.
The GNOME terminal is exited.
Installing The Dell 12th Generation iDRAC7 Evaluation License Using The GNOME Terminal
To install the Dell 12th Generation iDRAC7 evaluation license:
1. Boot the system using the Linux-Based Diagnostic Tools (Dell 9G–12G servers) option.
The CentOS desktop is displayed.
2. Double-click the gnome-terminal icon.
The GNOME terminal window is displayed.
14
3. At the command prompt, type su –, and press <Enter>.
The Password prompt is displayed.
4. Type dell, and press <Enter>.
The root user command prompt is displayed.
5. Type /usr/iDrac7EvalLicense/uploadEvalLicense.sh.
The following prompt is displayed: Do you want to install an enterprise evaluation
license that is valid for 30 days [Y/N]?
6. Press <Y> to install the license.
The license is imported and a warning message prompting to install a permanent license in 30 days is displayed.
7. At the Press ENTER to exit prompt, press <Enter>.
The GNOME terminal prompt is displayed.
Dell PowerEdge C System Management Pack
The PowerEdge C line of servers uses a baseboard management controller (BMC) to provide system monitoring and
administration, including remote power-on.
Dell provides the following Linux command-line tools to assist managing PowerEdge C servers (all tools work with all
PowerEdge C offerings).
NOTE: Dell PowerEdge C System Management Pack is officially supported to work on PowerEdge C servers only.
The tools available are:
• PEC-logs
• setupbios
• bmc tool
• Idstate
Running setupbios
setupbios is a BIOS configuration tool. It provides a number of ways to setup and replicate BIOS settings on PowerEdge
C servers.
It is used to confirm or change BIOS settings.
To run setupbios:
1. Boot the PowerEdge C server using the Linux-Based Diagnostics Tools (Dell 9G-12G servers) option.
The CentOS desktop window is displayed.
2. Double-click the gnome-terminal icon.
The GNOME terminal window is displayed.
3. At the command prompt, type setupbios.
The list of options is displayed.
The output from setupbios is included in PEC-logs report for troubleshooting.
Running bmc-tool (bmc)
The bmc software application enables you to manage and configure PowerEdge C Baseboard Management Controller
by using command line interface (CLI). BMC abstracts some of the complicated IPMI commands and provides simple,
Linux-type of interface. It works with all PowerEdge C formats and attempts to provide the most-commonly used
commands in an easy format.
15
To run bmc:
1. Boot the PowerEdge C server using the Linux-Based Diagnostics Tools (Dell 9G-12G servers) option.
The CentOS desktop window is displayed.
2. Double-click the gnome-terminal icon.
The GNOME terminal window is displayed.
3. At the command prompt, type bmc.
The list of options is displayed.
The output from BMC is included in PEC-logs report for troubleshooting.
Running ldstate
ldstate is a front-end tool for subordinate tools to monitor storage arrays.
It provides storage monitoring for single-disk, chipset RAID, and MegaRAID controllers.
To run ldstate;
1. Boot the PowerEdge C server using the Linux-Based Diagnostics Tools (Dell 9G-12G servers) option.
The CentOS desktop window is displayed.
2. Double-click the gnome-terminal icon.
The GNOME terminal window is displayed.
3. At the command prompt, type ldstate.
The list of options is displayed.
The output from ldstate is included in PEC-logs report for troubleshooting.
Running PE-C Support Logs Script
PE-C Support Script (pec-logs) is a utility that collects configuration and log data from the target server for various
chassis hardware, storage, and operating system components on Dell PE-C servers. It uses OS specific built-in report
tools and/or individual OS commands to pull operating system logs and configuration.
You can run PE-C Support Logs Script using one of the following methods:
• Running PE-C Support Logs Script Using The Desktop Icon
• Running PE-C Support Logs Script Using The GNOME Terminal
Running PE-C Support Logs Script Using The Desktop Icon
To run PE-C Support Logs Script:
1. Boot the PowerEdge C server using the Linux-Based Diagnostics Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
2. Double-click the PEC-Logs icon.
The PE-C support logs tool starts, the report is collected, and close the terminal.
3. The PE-C support logs tool exits and the report is saved in /tmp/data folder.
16
Running PE-C Support Logs Script Using The GNOME Terminal
To run PE-C Support Logs Script using GNONE terminal:
1. Boot the PowerEdge C server using the Linux-Based Diagnostics Tools (Dell 9G-12G servers) option.
The CentOS desktop window is displayed.
2. Double-click the gnome-terminal icon.
The GNOME terminal window is displayed.
3. At the command prompt, type su –, and press <Enter>.
The Password prompt is displayed.
4. Enter dell, and press <Enter>.
The root user command prompt is displayed.
5. Enter cd /opt/dell/pec/pec-logs/ and press <Enter>.
6. Execute the script ./pec-logs.
PE-C Support Logs Script is executed and the output is saved in /tmp/data.
NOTE: PE-C Support Logs Script is used only for PowerEdge C systems.
Starting Dell OpenManage Server Update Utility
Dell OpenManage Server Update Utility (SUU) is a DVD-based application for identifying and applying updates to the
system.
You can use SUU to update the Dell PowerEdge system or to view the updates available for systems supported by SUU.
SUU compares the versions of components currently installed on the system with update components packaged on the
Dell PowerEdge Server Update Utility media.
SUU displays a comparison report of the versions and provides various options for updating the components.
To start the Server Update Utility (SUU) application:
1. Start the server using the Linux-Based Diagnostic Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
2. Start the Server Update Utility stored in the USB drive or by inserting a DVD.
3. Right-click the SUU icon on the desktop and select Open in Terminal.
4. Enter sudo ./suu —g and press Enter.
The SUU window is displayed.
NOTE:
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to
avoid the problem.
Sharing Files Using Samba Share Service
Samba share is used to share the files between systems running on Linux and Windows.
17
To use the Samba share service:
1. Start the server using the Linux-Based Diagnostic Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed. By default, the Samba services running on the on-boot folder and /tmp/data folder
is shared.
2. By running the ifconfig command, check the IP address of Support Live Image.
3. On a Windows server, on the taskbar, click Start → Run. In the Open box, type the IP address of the Support Live
Image , and then press
4. Enter the username (root), password (dell), and then click OK.
The Samba shared folder data is displayed.
Enter.
Testing Network Connectivity
To test the network connectivity:
1. On the server, connect the network cable to either the network port that is having issues or to NIC1.
2. Boot the system using the Linux-Based Diagnostic Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
3. Double-click the gnome-terminal icon
The GNOME terminal window is displayed.
4. At the command prompt:
– Type ifconfig, and then press <Enter> to display the network interface parameters, such as the IP address.
– Type route, and then press <Enter> to determine the default gateway.
– Type ping ip_address —b, and then press <Enter> to verify if you can ping the default gateway.
Assigning A Static IP Address And Default Gateway
To assign a static IP address and default gateway:
1. Boot the system using the Linux-Based Diagnostics Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
2. Double-click the gnome-terminal icon.
The GNOME terminal window is displayed.
3. At the command prompt, type su —, and then press <Enter>.
The Password prompt is displayed.
4. Type dell, and then press <Enter>.
The root user command prompt is displayed.
5. Type service NetworkManager stop, and press <Enter>.
6. To assign a static IP, type ifconfig <eth0> <ip_address> netmask <subnet> , and then press
<Enter>.
7. To assign a default gateway, type route add default gw <ip_address>, and then press <Enter>.
8. Type service NetworkManager start, and then press <Enter>.
18
Generating The PCI Devices List
To generate the PCI devices list connected to your system:
1. Boot the system using the Linux-Based Diagnostic Tools (Dell 9G–12G servers) option.
The CentOS desktop is displayed.
2. Double-click the gnome-terminal icon.
The GNOME terminal window is displayed.
3. At the command prompt, type lspci , and press <Enter>.
The PCI devices list is displayed.
4. To export the PCI devices list to a file, at the command prompt:
– Type lspci > /tmp/data/lspci.txt
– Type lspci > /mnt/disc/folder_name/lspci.txt to copy to the local file system after remount,
folder_name is the folder on the local file system. For instructions to remount, see Accessing And
where
Remounting The Local File System.
Clearing ESM Logs (Dell 9th Generation And Later Servers Only)
To clear ESM logs:
1. Start the system using the Linux-Based Diagnostic Tools (Dell 9G–12G servers) option.
The CentOS desktop is displayed.
2. Double-click the gnome-terminal icon.
The GNOME terminal window is displayed.
3. At the command prompt, type su-, and press <Enter>.
The password prompt is displayed.
4. Type dell and press <Enter>.
The root user command prompt is displayed.
5. At the command prompt, type /opt/dell/advdiags/dset/bin/./ClearESMLog , and press <Enter>.
6. At the Do you want to continue? Y/N prompt, press <Y>.
Clearing The SBE Log
To clear SBE logs:
1. Boot the system using the Linux-Based Diagnostic Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
2. Double-click the gnome-terminal icon.
The GNOME terminal window is displayed.
3. At the command prompt, type su –, and then press <Enter>.
The Password prompt is displayed.
4. Type dell, and then press <Enter>.
The root user command prompt is displayed.
5. Type dcicfg command=clearmemfailures, and then press <Enter>.
19
Accessing And Remounting The Local File System
To access and mount the local file system:
NOTE: By default, the local hard disk drives are mounted as read-only.
1. Boot the system using the Linux-Based Diagnostic Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
2. Double-click the Local Hard Drives icon.
3. Double-click the disc folder.
The local hard drives are represented as folders named sde1, sde2, sde3, and so on.
4. To identify where the C: drive is mounted, open and check each folder.
The C: drive may be mounted at /mnt/disc/sde2.
5. To remount the local file system as read/write NTFS:
a. Close all windows that may be accessing the local file system.
b. Double-click the gnome-terminal icon.
c. In the CentOS terminal window, type unmount /dev/sde2, where /dev/sde2 is the location of the
device or partition you want to unmount.
d. Type mount -t ntfs /dev/sde2 /mnt/disc/sde2, where /dev/sde2 is the actual location
/mnt/disc/sde2 is the new mount location.
and
The local file system is now available in read/write format.
Mounting A USB Drive
To mount an USB drive:
1. Boot the system using the Linux-Based Diagnostics Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
2. Double-click the gnome-terminal icon.
The GNOME terminal window is displayed.
3. At the command prompt, type su –, and then press <Enter>.
The Password prompt is displayed.
4. Type dell, and then press <Enter>.
The root user command prompt is displayed.
5. Type mount, and then press <Enter>.
The available storage devices are listed. The USB drive is usually listed as type vfat (ro). For example, the
USB drive may be listed as
6. Type mount -o remount,rw /dev/<device_name>, where <device_name> is the name of the USB
device.
/dev/sda1 on /mnt/disc/sda1 type vfat (ro).
20
Copying Files To A USB Drive
To copy files to an USB drive:
1. Boot the system using the Linux-Based Diagnostics Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
2. Double-click the gnome-terminal icon.
The GNOME terminal window is displayed.
3. At the command prompt, type sudo nautilus, and then press <Enter>.
The Nautilus browser is displayed.
4. Under Places, click File System.
5. In the right pane, navigate to the /tmp/data folder, and locate the file (for example, DSET collection report) you want
to copy.
6. Right-click the file you want to copy, and then select Copy.
7. Under Places, click File System.
8. In the right pane, navigate to the /mnt/disc/ folder, and open the folder that corresponds to the mounted USB drive.
9. Right-click and select Paste.
Starting The Vim Editor
Vim Editor is a text editing tool used to open the
To start the vim editor:
1. Boot the system using the Linux-Based Diagnostics Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
2. Double-click the gnome-terminal icon.
The GNOME terminal window is displayed.
3. At the command prompt, type vim file_name, where file_name is the name of the file.
The vim editor is displayed.
4. To insert text, type i.
5. Type the required information.
6. To exit the insert mode, press <Esc>.
7. To save the file, type :wq.
The file is saved in the current folder.
.txt
files.
Starting gedit
gedit is a Gui–based text editing tool.
To start gedit:
1. Boot the system using the Linux-Based Diagnostic Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
2. Click Applications → Accessories → gedit Text Editor.
The gedit window is displayed.
21
Starting The Hex Editor
Hex Editor is a GUI–based text editing tool.
To start the hex editor:
1. Boot the system using the Linux-Based Diagnostic Tools (Dell 9G-12G servers) option.
The CentOS desktop is displayed.
2. Click Applications → Programming → Hex Editor.
The GHex window is displayed.
Using TightVNC
You can establish a remote desktop session using TightVNC. After a remote connection is established, you can copy and
paste the configuration files from the remote system to a local system at Dell technical support.
Ensure that TightVNC is installed on the local system (Dell technical support) and that the remote system is booted to
CentOS.
To use TightVNC:
1. Launch TightVNC on the local system.
The New TightVNC Connection dialog box is displayed.
2. In the TightVNC server box, type the IP address of the remote system.
3. In the User name field, type root.
4. In the Password field, type dell.
5. Click Connect.
The desktop of the remote system is displayed.
Using WinSCP
WinSCP is a Windows–based tool. You can securely transfer files between a local and a remote system using WinSCP.
You can use WinSCP to securely transfer the configuration reports to Dell technical support. WinSCP is available for
download at winscp.net.
To use WinSCP:
1. Ensure that WinSCP is installed on the local system (Dell technical support) and that the remote system is booted to
CentOS.
2. Launch WinSCP on the local system.
The WinSCP Login dialog box is displayed.
3. In the Host name box, type the ip address of the remote system.
4. In the User name field, type root.
5. In the Password field, type dell.
6. Click Login.
The WinSCP window is displayed with the directory structure of the local and remote systems. You can securely
drag the files between the local and remote system.
22
Useful Commands
This section provides the Linux commands you can use to start, stop, or restart the OMSA and network service. At the
terminal command prompt, type the commands listed in the following tables to perform the required functions.
Table 2. OMSA Service Commands
Command Description
srvadmin-services.sh start
srvadmin-services.sh stop
srvadmin-services.sh restart
srvadmin-services.sh status
Table 3. Network Service Commands
Command Description
service network start
service network stop
service network restart
Start the OMSA service.
Stop the OMSA service.
Restart the OMSA service.
Status of the OMSA service.
Start the network service.
Stop the network service.
Restart the network service.
23
Loading...