Sun Blade 6000 System
 
Sun Blade X6450 Server Module
 
Sun Blade X6240 Server Module
 
Sun Blade X6220 Server Module
 
Sun Blade T6300 Server Module
 
Sun Blade X6440 Server Module
 
Sun Blade X6270 Server Module
 
Sun Blade 6048 System
 
Sun Blade X6250 Server Module
 
Sun Blade X6275 M2 Server Module
 
Sun Blade X6270 M2 Server Module
 
Sun Blade T6340 Server Module
 
Sun Blade X6420 Server Module
 
Sun Blade T6320 Server Module
 

PLA-Support>Sun Systems>x86>Blades>SN-x64: BLADE
 

Applies to:

Goal

Description

This document describes how to gather data from a Sun Blade[TM] 6000 and a Sun Blade[TM] 6048 chassis.

Symptoms

•   Chassis Management Module(CMM) hangs
•   Chassis issues, fans power supplies
•   Warning Light Emitting Diodes (LEDs) on
•   Failure to log in to CMM
•   Cannot log in to blade

Purpose/Scope

This document details gathering data from all components in a Blade 6000/6048 system.

This will include the chassis LEDs, CMM, Service Processors (SPs) and the blades themselves.

Solution

Steps to follow for gathering data from a Sun Blade[TM] 6000/6048 Modular System

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

• LEDS
• CMM
• SPs
• Blades

LED:

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 Integrated Lights Out Manager (ILOM) running on the CMM is at version 3.0 or above then collect a "normal snapshot"

Type "version" on ILOM CLI

On GUI interface CMM > System Information > Versions

ILOM Web GUI

Point a web browser at 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

Log in and proceed as follows:

1. Select CMM from left hand column
2. Select Maintenance
3. Select Snapshot
4. Select desired Data Set: Normal
5. Do NOT tick "Collect Only Log Files From Data Set:" box
6. Select transfer method : Browser
7. Click Run
8. A "Save As" dialogue box appears.

In the dialog box, specify the directory to which to save the file and the file name.

Click OK.

The file is saved to the specified directory.

ILOM CLI

1. Perform an ssh as root to ILOM

2. A header similar to the following should appear.

Oracle(R) Integrated Lights Out Manager 3.0.12.11.a r63765 Copyright (c)2011, Oracle and/or its affiliates...

3 Perform a change directory to /CMM/diag/snapshot "cd /CMM/diag/snapshot"

4 Then perform a "set dump_uri=sftp://user:password@10.195.65.29/tmp/directory_name"

5. Type show to check that snapshot is running:

-> show /CMM/diag/snapshot Targets: Properties: dataset=normal dump_uri=xxxx encrypt_output=false result=Running

If the CMM ILOM version is below 3.0 then use ipmitool to collect information.

Refer to section "Collecting Configuration, status and event information" in <Document: 1009698.1>

Service Processors (SPs)

As above if the ILOM version is at 3.0 or above then collect a normal snapshot from the SP and do not select "logs only"

See <Document: 1020204.1> for a discussion on data available in snapshot and methods of collecting it.

If the version is below 3.0 then refer to the document below to gather information:

How to verify platform health on a Sun X64 Server <Document: 1008409.1>

Blade Server Modules

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

• Solaris[TM]

Run Solaris Explorer to obtain Blade OS information:
Refer to the Sun Explorer Product Information Center <Document: 1312847.1>

• Red Hat

Refer to the following document:
How to Gather Information on Red Hat Enterprise Linux Systems <Document: 1010058.1>

• SUSE

Refer to the following document:
How to gather information on SuSE Linux Enterprise Systems <Document: 1010057.1>

• Windows

Refer to the following documents:
Microsoft Windows(R) and Linux operating systems: How to obtain troubleshooting information <Document: 1010936.1>

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

• VMware

Refer to the following URL:

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

This solution has no attachment