Sun Fire E2900 Server
 
Sun Fire V1280 Server
 
Sun Fire 3800 Server
 
Sun Fire 6800 Server
 
Sun Fire 4810 Server
 
Sun Fire 4800 Server
 
Sun Netra 1290 Server
 
Sun Netra 1280 Server
 
Sun Fire E4900 Server
 
Sun Fire E6900 Server
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Exx00
 
.Old GCS Categories>Sun Microsystems>Servers>Midrange Servers
 
.Old GCS Categories>Sun Microsystems>Servers>Midrange V and Netra Servers
 

Applies to:

Goal

This document provides a procedure to collect Sun Fire[TM] Midrange Server System Controller (SC) Data when it is not possible to capture scextended or 1280extended Explorer data.

Manual SC command output, as documented in this article, is important from a troubleshooting perspective to have available, but is only a subset of commands which would be collected by Explorer, the preferred data set for this server family.  Please collect extended Explorer if able to do so utilizing Document 1019066.1 as a guide.

That said, if you are unable to execute Explorer for some reason, please use the following information to make sure to collect the most useful command data.

Click on the type of server you need information on and you will skip to the specific instructions for that server:

• Sun Fire 3800, 4800, 4810, 6800, E4900, or E6900 Servers
• Sun Fire v1280, E2900, or Netra 1280, 1290 Servers

Fix

Sun Fire 3800-E6900 System Controller (SC) Data Collection

1) Log into a system which has access to the Main System Controller (SC) and open a terminal window.

2) Open a script session so the following SC command output will be captured.

$ script -a /tmp/scdatafile

3) Connect to the platform shell of the Main SC per your configuration's requirements (telnet, console, ssh, tip, etc):

$ console main-sc
$ telnet main-sc
$ ssh main-sc
$ tip main-sc

NOTE: Do not reboot the main SC before collecting this data. Doing so may erase critical troubleshooting information in the SC's log buffer.

Note – At 5.18.0, you will be offered the option of connecting with a secure shell (ssh) only if you have an SC V2 in the IB/SSC. In this case only SSH will work not telnet

4) From the platform shell, execute the following commands which will be captured in the script session that you opened previously:

The platform shell of the current master SC will have a prompt of
schostname:SC>  <--- note the uppercase SC

showdate
showsc -v
connections
showescape
showkeyswitch
showfailover -v

showcodlicense -v
showcodlicense -rv
showcodusage -v

showplatform -v
showplatform -vda
showplatform -vdb
showplatform -vdc
showplatform -vdd

showboards -ev
showcomponent
showfru -r manr

showchs -b  (will fail for fw below 5.20.15)
And for each suspect or faulty component
showchs -vc /N0/IB6    (for example)

showdate -v
showdate -v -d a
showdate -v -d b
showdate -v -d c
showdate -v -d d

showlogs -v
showlogs -vp  (the -vp* commands will fail for systems with older SCs)
showlogs -v -d a
showlogs -vp -d a
showlogs -v -d b
showlogs -vp -d b
showlogs -v -d c
showlogs -vp -d c
showlogs -v -d d
showlogs -vp -d d

showerrorbuffer
showerrorbuffer -p

showenvironment -ltuv

history
showdate -v



Commands to issue from the platform shell of the current slave SC.
(For those systems which have both SC0 and SC1.)

The platform shell of a slave SC will have a prompt of
schostname:sc>  <--- note the lowercase sc

showdate
showenvironment -ltuv
showfailover -v
showfru -r manr
showlogs -v
showlogs -vp
showplatform -v
showsc -v
showdate -v
history

NOTE:  You might need to use a "Control right bracket" ("']") to disconnect, depending on how you have connected to the SC.

5) Exit the script session to save the collected data:

• Hit <control> D and you should get the message "script /tmp/scdatafile closed", "script done" or a similar message.

• Alternatively, you can also type "exit" at the prompt to close the script session.

6) Upload the data file (scdatafile in this example) utilizing the instructions in Document 1020199.1.

• It is suggested that the SR Number be apended to the beginning of the file, for example "SR_Number_scdatafile".

Sun Fire v1280, E2900, n1280, and n1290 System Controller (SC) Data Collection

1) Log into a system which has access to the System Controller (SC) Network Management Port (lom> prompt) and open a terminal window.

2) Open a script session so the following SC command output will be captured.

$ script -a /tmp/scdatafile

3) Connect to the lom> prompt on the SC per your configuration's requirements (telnet, console, ssh, tip, etc):

$ console sc_name$ telnet sc_name$ ssh sc_name

NOTE:  After initial connection, you may need to issue a "#." to get into the lom> prompt where the following commands are available.

Note – At 5.18.0, you will be offered the option of connecting with a secure shell (ssh) only if you have an SC V2 in the IB/SSC. In this case only SSH will work not telnet 

ADDITIONAL NOTE: Do not reboot the SC before collecting this data. Doing so may erase critical troubleshooting information in the SC's log buffer.

4) From the lom> prompt, execute the following commands which will be captured in the script session that you opened previously:

showdate -v
showsc -v
bootmode
showeventreporting
showescape
showhostname
shownetwork -v
showmodel

showcodlicense -rv
showcodusage -vp all

showlogs -v
showlogs -vp  (will fail on older 1280 models)

showcomponent -v
showresetstate -v  (typically returns nothing)
showfault
showlocator
showalarm 1
showalarm 2
showalarm 3
showalarm system

showchs -b  (will fail for fw below 5.20.15)
And for each suspect or faulty component
showchs -vc /N0/IB6    (for example)

showerrorbuffer
showerrorbuffer -p   (will fail on older 1280 models)

showenvironment -ltuv
showboards -ev
inventory
history
showdate

NOTE:  You might need to use a "Control right bracket" ("']") to disconnect or just type "logout", depending on how you have connected to the SC.

5) Exit the script session to save the collected data:

• Hit <control> D and you should get the message "script /tmp/scdatafile closed", "script done" or a similar message.
• Alternatively, you can also type "exit" at the prompt to close the script session.

6) Upload the data file (scdatafile in this example) utilizing the instructions in Document 1020199.1.

• It is suggested that the SR Number be appended to the beginning of the file, for example "SR_Number_scdatafile".

Loghost Information

The amount of failure data recorded on the SC itself is limited, so a loghost should have been setup to collect all errors observed remotely (Sun Fire 3800, 4800, 4810, 6800, E4900, E6900 servers only).

• Please see Document 1008676.1 for 'Best Practices' and configuring loghost on Sun Fire[TM] 3800,4800,4900,6800, and E6900 servers.
• If a loghost is configured, data may be available on it that is relevant to this issue and should be provided to support as well.

Internal section

Keywords: collect, data, manual, system controller, network hang, sc, explorer, normalized
Previously Published As 78156 & 204962

References

This solution has no attachment