Sun Blade X8400 Server Module
 
Sun Blade X8450 Server Module
 
Sun Blade X8420 Server Module
 
Sun Blade 8000 P System
 
Sun Blade 8000 System
 
Sun Blade X8440 Server Module
 

GCS>Sun Microsystems>Servers>x64 Servers
 
GCS>Sun Microsystems>Servers>Blade Servers
 

Applies to:

Goal

Description

This document describes techniques for gathering information on components of the Sun Blade [TM] 8000/8000P System.

Solution

Steps to follow for gathering data from a Sun Blade[TM] 8000/8000P Modular System.

The Sun Blade 8000/8000P system can be split into four areas from where data can be collected:

• Chassis LEDs

• Chassis Management Module (CMM)

• Blade Server Service Processor (SP)

• Blade Server Modules (which are capable of running a number of operating systems)

Chassis LEDs:

To obtain a chassis wide list of configuration and sensors, the output of the following commands can be logged with the Unix command "script" of by some other means. This does not display much individual information about the Blades themselves.

Perform the following commands from the CMM ILOM instance:

-> show / -l all

Note: The status of the various chassis LEDs. This output is extremely long and can take several minutes to display.

See How to check Fault/warning LEDs on Blade 8000/8000P Systems (Doc ID 1019531.1)

Chassis Management Module (CMM):

To view CMM event log:

-> show /CMM/logs/event/list

 Make sure a key is depressed when prompted to obtain all the log.

To get the ILOM version type:

-> version

For CMMs with ILOM version 2.0.1.5 or later ipmitool commands can used to interrogate the CMM.

From any machine that has ipmitool, the following commands should be run:

# ipmitool -I lan -U root -H sel elist
# ipmitool -I lan -U root -H sensor list
# ipmitool -I lan -U root -H fru
# ipmitool -I lan -U root -H sunoem sbled get all
# ipmitool -I lan -H -U root -f passwd sel info

Note the above command will prompt for the root password.

The following technique can be used to avoid this:

# ipmitool -I lan -H -U root -f CMM_pw sunoem sbled get all

NOTE: CMM_pw is a file with the CMM root password in it.

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:

    -    Use ssh to connect 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

There is a LINUX version of FMA called FDD running on the CMM. Note this is different to FMA running on Solaris[TM]

The FMA messages are displayed in the CMM event log. The CMM System Monitoring tab of the GUI can be used to display the chassis sensors indicators and event log.
If single sign on is enabled then it also allows the ability to examine the Blade specific information. By selecting the particular blade on the left hand side of the GUI and looking at the System Monitoring tab.
For further information on using the GUI or CLI of the CMM please see the Sun[TM] Integrated Lights Out Manager User's Guide at:

http://download.oracle.com/docs/cd/E19045-01/blade.8000mod/820-4198-12/index.html

Blade Server Service Processors (SP):

Each Blade within the Sun Blade 8000 chassis has its own Service Processor running an instance of ILOM.
ipmitool commands can used to interrogate the Service Processor (SP) from any machine that has ipmitool installed.

# ipmitool -I lan -U root -H < SP address> sel elist
# ipmitool -I lan -U root -H < SP address> sensor list
# ipmitool -I lan -U root -H < SP address> fru
# ipmitool -I lan -U root -H < SP address> sunoem sbled get all
# ipmitool -I lan -U root -H < SP address> sel info

The same technique as outlined above of using the -f option can be used to avoid being prompted for the root password.
From the CLI, the directory structure of the ILOM can be displayed which will include the state of sensors and other information.

# ssh -l root <SP_IP_ADDRESS>
Password:

Sun(TM) Integrated Lights Out Manager Version 2.0.1.1 Copyright 2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.

-> show / -l all

The above command will produce a large output. If this technique is used the output should be logged using the Unix command "script" or some other method.

To display the event log:

-> show /SP/logs/event/list

If single sign on is enabled, the Blade event log can also be displayed from the CMM CLI by the following command.

-> show /CH/BLx/SP/logs/event/list

Where x is the Blade number.

To get ILOM version:

-> version

The System Monitoring tab of the Blade SP GUI can also be used to view sensors, indicators and the event log.There will be chassis components and events also displayed here such as fans and power supplies.

How to run the script collectDebugInfo.sh on an SP:

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

    -    Use ssh to connect to the SP 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 Oracle Global Support

Blade Server Modules:

Methods for gathering data are dependent on which operating system is running.

• Solaris

Run Explorer to obtain Blade O/S information.

• Red Hat

Run the Red Hat sysreport utility:

/usr/sbin/sysreport

Then provide the file created to Oracle Global Support.

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

Then provide the file created to Oracle Global Support.

As with Red Hat, /var/log files are not collected, so collect:

Collect the following file:

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

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

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

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

• Windows

See the following documents:

Microsoft Windows and Linux operating systems: How to obtain troubleshooting information (Doc ID 1010936.1)

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

• VMware

See the following document:

Collecting diagnostic information for VMware ESX 2.5, 3.0, 3.5 and 4.x/588/653_f.SAL_Public.html

References:

Sun Blade 8000 Modular System Documentation
Sun Blade 8000P Modular System Documentation

Previously Published As 87643

This solution has no attachment