Goal

Description

Symptoms

•  CMM hangs
•  Chassis issues – fans power,supplies
•  Warning LEDs on
•  Failure to log in to CMM
  
•  Can't login to blade

Purpose/Scope

Solution

The Sun Blade 6000/6048 systems can be split into four areas from where
data can be collected:

Light Emittring Diodes LEDs
Chassis Management Module (CMM)
Service Processors (SPs) for Blades and certain Network Express Modules (NEM)
Blade Server Modules (which are capable of running a number of operating systems)

LEDs

Note the status of the various chassis LEDS.
Refer to < Document: 1019321.1 > Procedure to check Fault/warning LEDs on Blade 6000/6048 Systems

Chassis Management Module (CMM)

If the Chassis Management Module is responding then collect the following data using one of the following methods.

Method 1 - ipmitool is often considered the preferable as it provides the data in a text format which is compact.

ipmitool -U root -H -I lan sel elist
ipmitool -U root -H -I lan fru
ipmitool -U root -H -I lan sdr elist

Method 2 - using ILOM CMM CLI

Connect to CMM by ssh with the user root. Record the following output by using a logging terminal or a utility like the Unix script command.

-> show /CMM/logs/event/list

(make sure the entire log is collected by pressing any key when prompted)

-> show / -l all

(NOTE: this output is very long)

Method 3 - using ILOM Web GUI.

Connect with a browser to the CMM. Put the CMM ip address in the browser; it will return an address similar to the following:

https://CMM_ip_addr/iPages/i_login.asp

Login and proceed as follows

Select CMM on left hand of Page
Select System Monitoring Tab , and sub tab Indicators and note or snap display.

Select System Monitoring Tab, and sub tab Event Logs and snap display - this will typically be several pages long and it is important all output is collected.

Select System Monitoring Tab and sub tab Sensor Readings and note or snap display.

Select System Information Tab and sub tab Versions and note or snap display.

How to run the script collectDebugInfo.sh on a CMM

This is normally requested if there is a problem suspected with the firmware or functioning of the CMM. If requested to run collectDebugInfo.sh by Sun Support, follow these steps.

• ssh to the cmm as user sunservice using the same password as root.

• Run the command collectDebugInfo.sh

• use scp to copy off created dbginfo_x.x.x.x file in /dev/shm

• provide file to Sun Support

Service Processors (SPs)

Gather the following data from each Blade Server's SP:

ipmitool -I lan -U root -H sel elist
ipmitool -I lan -U root -H sensor list
ipmitool -I lan -U root -H fru

NOTE: You can not run ipmitool commands against on a T6300 blade service processor

Blade Server Modules

Methods for gathering data are dependent on which OS is running.

• Solaris[TM]

Run explorer to obtain Blade OS information.
Refer to "How to Run Sun[TM] Explorer and Forward the Data to a Sun Engineer"

• Red Hat

Run the Red Hat utility /usr/sbin/sysreport and provide the file created.

NOTE: Sysreport does not collect various files in the /var/log directory which may be useful ( such as old messages files).

Collect the following file:

cd /var/log
tar -cf /tmp/log.tar *

• SUSE

Run SIGA (System information GAthering) (/usr/bin/siga)
As with Red Hat, /var/log files are not collected, so collect:

cd /var/log
tar -cf /tmp/log.tar *

As well as SIGA, supportconfig is a tool which collects more data. Supportconfig documented at:

Novell

http://www.novell.com/coolsolutions/tools/16106.html

NOTE: SIGA, supportconfig and syreport are the official tools of the respective companies.

• Windows

See Microsoft Windows and Linux operating systems: How to obtain troubleshooting information

Microsoft Windows(R) operating system: How to obtain troubleshooting information for storage issues

for information on the Microsoft Product Support Reporting Tool

• VMware

See http://kb.vmware.com/KanisaPlatform/Publishing/588/653_f.SAL_Public.html

Additional Information


For information on Linux data gathering see:

http://systems-tsc/twiki/bin/view/Teams/LinuxDataGathering#Data_Gathering

 

This solution has no attachment