Goal

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.

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

Solution

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

$ script -a /tmp/scdatafile

$ 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.

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

showdate
showsc -v
showescape
showkeyswitch

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 -vda
showlogs -vpda
showlogs -vdb
showlogs -vpdb
showlogs -vdc
showlogs -vpdc
showlogs -vdd
showlogs -vpda

showerrorbuffer
showerrorbuffer -p

showenvironment -ltuv

history
showdate

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

$ script -a /tmp/scdatafile

$ 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.

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
showeventreporting
showescape
showhostname
shownetwork -v
showmodel

showcodlicense -rv
showcodusage -vp all

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

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
showcomponent -v
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.

• 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.
  

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

This solution has no attachment