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

Asset ID: 1-75-1020884.1
Update Date:2012-10-03
Keywords:

Solution Type  Troubleshooting Sure

Solution  1020884.1 :   How to Collect a Forced Crash Dump of a Hanging Solaris Guest Domain  


Related Items
  • SPARC T3-4
  •  
  • Sun Netra T5440 Server
  •  
  • Sun Fire T1000 Server
  •  
  • Sun Blade T6300 Server Module
  •  
  • Sun SPARC Enterprise T5440 Server
  •  
  • Sun Fire T2000 Server
  •  
  • Sun SPARC Enterprise T5120 Server
  •  
  • Sun Netra T2000 Server
  •  
  • Sun SPARC Enterprise T5220 Server
  •  
  • Sun SPARC Enterprise T5240 Server
  •  
  • Sun SPARC Enterprise T1000 Server
  •  
  • Sun Blade T6320 Server Module
  •  
  • Solaris SPARC Operating System
  •  
  • Sun Blade T6340 Server Module
  •  
  • Sun Netra T5220 Server
  •  
  • Sun SPARC Enterprise T2000 Server
  •  
  • Sun SPARC Enterprise T5140 Server
  •  
  • SPARC T4-4
  •  
Related Categories
  • PLA-Support>Sun Systems>SAND>Operating System>SN-SND: Sun OS Virtualization LDOM
  •  
  • .Old GCS Categories>Sun Microsystems>Servers>Blade Servers
  •  
  • .Old GCS Categories>Sun Microsystems>Servers>CMT Servers
  •  
  • .Old GCS Categories>Sun Microsystems>Operating Systems>Solaris Operating System
  •  
  • .Old GCS Categories>Sun Microsystems>Servers>NEBS-Certified Servers
  •  

PreviouslyPublishedAs
266628


Applies to:

Sun SPARC Enterprise T5240 Server - Version Not Applicable and later
Sun Blade T6320 Server Module - Version Not Applicable and later
Sun Blade T6300 Server Module - Version Not Applicable and later
Solaris SPARC Operating System - Version 10 3/05 and later
Sun SPARC Enterprise T2000 Server - Version Not Applicable and later
SPARC

Purpose

This Document refers the Steps to collect the crash dump of a hanging Guest domain.

Purpose/Scope:
___________

This document refers to steps to collect forced crash dump for a hanging Domain .

Symptom:

Guest LDOM not responding or Guest LDOM Hanging.

Troubleshooting Steps

Resolution
1. ldm panic/panic-domain [Guest Domain Name]

 

2. Another way to do this is through VNTSD options. Please see vntsd(1M)

~#

Send break.

~^B

Send alternate break 
(If "KEYBOARD_ABORT=alternate" has been set in the /etc/default/kbd file within the guest domain)

 

Debugging requested; hardware watchdog suspended.

c)ontinue, s)ync, r)eset? s

By selecting 'sync' option this will help to create the crash dump.

 

Once the crash dump is collected please follow 1020212.1 to collect LDOM related logs.

 

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community, Oracle Solaris System Administration Community.


Product
Sun Fire T2000 Server
Sun Fire T1000 Server
Sun Netra T2000 Server
Sun Netra T5220 Server
Sun Netra T5440 Server
Netra T5220 AC
Sun SPARC Enterprise T5220 Server
Sun SPARC Enterprise T5240 Server
Sun Blade T6300 Server Module
Sun Blade T6320 Server Module
Sun SPARC Enterprise T5120 Server
Sun SPARC Enterprise T5140 Server
Sun Blade T6340 Server Module
Sun SPARC Enterprise T2000 Server
Sun SPARC Enterprise T5440 Server
Sun SPARC Enterprise T1000 Server
Sun SPARC T3 Series
Sun SPARC T4 Series

Internal Comments
This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the "Document Feedback" alias(es) listed below:

Normalization Lead: [email protected]


Normalized, ldom, ldm, Hanging


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