Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1001920.1
Update Date:2009-11-05
Keywords:

Solution Type  Technical Instruction Sure

Solution  1001920.1 :   Tech Tip: Initial Data collection when opening a Sun Support call for Sun Fire[TM] V210, V240, V250, V440 or Netra[TM] 240, 440 Server  


Related Items
  • Sun Fire V240 Server
  •  
  • Sun Fire V250 Server
  •  
  • Sun Fire V440 Server
  •  
  • Sun Fire V210 Server
  •  
  • Sun Netra 440 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>NEBS-Certified Servers
  •  
  • GCS>Sun Microsystems>Servers>Entry-Level Servers
  •  

PreviouslyPublishedAs
202662


Description
This Document provides:

1) A listing of the initial data, a customer should collect and provide to a Sun Technical Support Engineer, when opening a call to troubleshoot a Sun Fire[TM] V210, Sun Fire[TM] v240, Sun Fire[TM] V250, Sun Fire[TM] V440, Netra[TM] V240 and Netra[TM] V440 system failure.

2) The commands the customer should run, in order to collect this initial data.

The information requested, is to enable quick determination of root cause, in the event one of the noted servers experiences a failure. The data collected will assist the Sun Technical Support Engineer in the Customer Care Center, in the expedient and quality identification of the failing component. In some cases, additional information may be requested, such as core files and explorer output. You will be advised by the Sun Technical Support Engineer when this determination is made.


Steps to Follow
Tech Tip: Initial Data collection when opening a Sun Support call for Sun Fire[TM] V210, V240, V250, V440 or Netra[TM] 240, 440 Server

The following commands will output the data needed by a Sun Technical Support
Engineer, to assist in determining the probable cause of a system failure in a:

  • Sun Fire[TM] V210,
  • Sun Fire[TM] V240,
  • Sun Fire[TM] V250,
  • Sun Fire[TM] V440,
  • Netra[TM] 240
  • Netra[TM] 440

So, once the data below is collected, it should be sent to the Sun Technical Support Engineer working the case.

NOTE: The engineer may ask for more information (for example, core files, explorers), as needed.

  1. Connect to ALOM serial port. To know how to connect to LOM/ALOM SERIAL Management Port please see <Document: 1010563.1> . For general information on serial port parameter settings and pinouts please see <Document: 1003374.1> .
  2. From the ALOM Shell "hostname: sc>" prompt, execute the following:
    • showlogs -v
    • consolehistory -v
    • showfru
    • showenvironment
      Cut and Paste the outputs from the above commands, and email them to the engineer working your case. If you are on a terminal and are not able to "cut and paste" the data, you can use the Solaris[TM] "script" command to capture all console activity into a file. The script command creates a file named "typescript" in the directory where the "script" command was executed. Read the Solaris[TM] manpage on the command "script" for more information and usage options.
  3. If the system is unable to boot please collect output of the following commands from the OBP prompt
    • show-post-results
    • .asr
    • probe-scsi-all
    • probe-ide
    • devaliases
    • printenv
  4. From the Solaris[TM] level or OS level, the /var/adm/messages* file(s) from the affected system are also needed.
    • /var/adm/messages /var/adm/messages.0 /var/adm/messages.1
  5. If the system generated a corefile, then run the following commands from the OS substituting number of the corefile generated by latest panic in place of (x) and provide resulting files to Sun Technical Support Engineer:
    • echo '$<msgbuf' | adb -k unix.(x) vmcore.(x) > msgbuf(x).out
    • echo '$c' | adb -k unix.(x) vmcore.(x) > stack(x).out
  6. From the command line prompt, execute the following commands and collect output:
    • usr/platform/sun4u/sbin/prtdiag -v
    • cat /etc/release
    • uname -a
  7. Provide answers to the following questions:
    • When did this start?
    • Had any hardware been added, changed or removed at that time?
    • Had any software been added, changed or removed at that time?
    • Can you ping or telnet to the system?
    • Is the system rebooting or hard hanging?


Product
Sun Fire V210 Server
Sun Fire V440 Server
Sun Fire V250 Server
Sun Fire V240 Server
Netra 440 Server
Netra 440 (AC) Server
Netra 240 Server (AC)
Netra 240 Server

Internal Comments
Audited/updated 11/04/09 - Dencho.Kojucharov@Sun.COM, Entry Level SPARC Content Team Lead



In case of any hardware issues it may be a good idea to collect log of the POST in the diagnostic mode and run some appropriate obdiag tests.


v440, v240, v250, v210, Netra 440, Netra 240
Previously Published As
74368

Change History
Date: 2007-11-12
User Name: 29589
Action: Approved
Comment: update complete
Version: 6
Date: 2007-11-12
User Name: 29589
Action: Update Started
Comment: Need to update an invalid link.
IBIS pre-migration work.
Version: 0
Date: 2006-03-31
User Name: 31620
Action: Approved
Comment: Verified Metadata - ok
Verified Keywords - ok
Verified still correct for audience - currently set to contract
Audience left at contract as per FvF http://kmo.central/howto/FvF.html
Checked review date - currently set to 2006-09-23
Checked for TM - no new ones needed
Publishing under the current publication rules of 18 Apr 2005:
Version: 5
Date: 2006-03-29
User Name: 31620
Action: Accept
Comment:
Version: 0




Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback