Sun Fire B1600 Blade System Chassis Administration Guide
|
   
|
This chapter documents contains the following sections:
11.1 Introduction
This chapter tells you how to perform basic troubleshooting on your Sun Fire B1600 blade system chassis, and how to gather the information you need to supply to a Sun engineer if you call Sun support.
For information about contacting Sun support in your area, contact your local Sun service representative.
11.2 Things to Check Before You Phone Sun
Before contacting a Sun engineer, check that:
- All power, network, and serial cables are correctly fitted in to their connectors and they all lead to the devices you intend them to lead to.
- All cables have the correct pin connections for the connectors they are inserted into. To check the pin-outs of the different connectors, refer to the Sun Fire B1600 Blade System Chassis Hardware Installation Guide.
- All components of the blade system chassis are configured to use the correct netmask and default gateway for the subnets you are introducing them into.
- All components that require an IP address have one correctly configured.
- All VLANs are correctly configured.
- The switch is running; try logging in to its console. If it is not running, you will not be able to log in.
- You are not unknowingly logged into one of the switch or blade consoles. Type the #. escape sequence to see whether this returns you to the sc> prompt.
- None of the ports you are using on the switch has been disabled.
If you are:
- Trying to access the System Controller using a serial connection, make sure you are using the correct baud rate (9600), parity setting (no), stop bits (1) and data bits (8) settings.
- Trying unsuccessfully to access the System Controller using a telnet connection, try logging into it using a serial connection, then run the showsc command to check that the telnet interface is enabled. If it is not, run the setupsc command, and when prompted, enable the telnet interface.
- Unable to access the System Controller from the management network, make sure that cable from the management network is connected to the NETMGT port on the correct Switch and System Controller. (Note that there is no network connection between the two System Controllers. Therefore, you must have network cable from the management network to the NETMGT port of the System Controller you want to reach.)
- Using VLANs and you have removed any blades from their slots, make sure that you replaced the blades in their correct slots. Otherwise you might find that server blades intended for one VLAN are inserted in to ports configured for another VLAN.
- Using tagged VLANs, make sure that the interfaces on the server blades are correctly named. For information about naming the interfaces, refer to the Sun Fire B1600 Blade System Chassis Software Setup Guide.
11.3 Assembling Information to Provide to a Sun Support Engineer
This section tells you how to gather the information that will help the Sun engineer to diagnose and fix your problem. As well as passing to the engineer the system output from the commands mentioned later in this section, please tell the engineer whether it is possible to ping the malfunctioning components of the chassis. Attempt to perform the ping operation from a workstation on the same subnet as each malfunctioning component.
11.3.1 Gathering Information About the Whole Chassis
You need to capture output from the following System Controller commands:
where n is the number of the slot containing the blade that is not operating properly.
It will also be useful to the Sun engineer you talk to if you can tell him or her which serial port, if any, you are receiving output from the System Controller on.
11.3.2 Gathering Information About a Switch
You need to capture output from the following switch console commands:
console#show mac-address-table
|
console#show interface status
|
console#show interface switchport
|
console#show interface counters
|
console#show running-config
|
console#show startup-config
|
console#show logging flash
|
console#show spanning-tree
|
11.3.3 Gathering Information About a Server Blade by Using Sun Explorer
The Sun support engineer you talk to about a malfunctioning server blade will need to see output from the Sun Explorer diagnostic tool. This section tells you how to obtain this tool and how to run it.
For information about performing preliminary diagnostics on a server blade, refer to the chapter on blade setup in the Sun Fire B1600 Blade System Chassis Software Setup Guide.
1. Download a copy of Sun Explorer either to the server blade or to a location on the network that is accessible from the server blade.
To obtain the Explorer software, visit the following web site:
http://sunsolve.sun.com
2. After downloading the SUNWexplo.tar.Z file from sunsolve.sun.com, copy it to the /var/tmp directory on the server blade.
3. Log into the server blade's console as root.
4. Extract the contents of the Explorer package.
Type:
#cd /var/tmp
#uncompress SUNWexplo.tar.Z
#tar xvf SUNWexplo.tar
|
Alternatively, if you have gzip installed on the server blade, type:
#zcat SUNWexplo.tar.Z | tar xvf -
|
5. Add the Explorer package to the server blade.
6. Run Explorer on the server blade.
Type:
# /opt/SUNWexplo/bin/explorer
|
7. Submit the Explorer output to Sun by E-mail using the following e-mail addresses:
- The Americas
explorer-database-americas@sun.com
- Asia and the Pacific
explorer-database-apac@sun.com
- Europe, the Middle East, Africa
explorer-database-emea@sun.com
| Sun Fire B1600 Blade System Chassis Administration Guide
|
817-3432-12
|
|
Copyright © 2004, Sun Microsystems, Inc. All rights reserved.