![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
|||||||||||||||||
Solution Type Technical Instruction Sure Solution 1588140.1 : Sun Storage 7000 Unified Storage System: How to perform a Diagnostic Reboot
In this Document
Created from <SR 3-7841928245> Applies to:Sun Storage 7410 Unified Storage System - Version All Versions and laterSun ZFS Storage 7420 - Version All Versions and later Sun ZFS Storage 7320 - Version All Versions and later Sun ZFS Storage 7120 - Version All Versions and later Sun Storage 7210 Unified Storage System - Version All Versions and later 7000 Appliance OS (Fishworks) GoalEnter the goal of the document. What does the customer want to accomplish? During the analysis phase of your service request, Oracle Support may ask you to perform a Diagnostic Reboot. A diagnostic reboot will collect diagnostic data, like system core dump, which may cause the system to take more time to boot, as compared to regular reboot.
Do not perform diagnostic reboot if system is being modified in some manner like during firmware upgrades, configuring/unconfiguring storage pool.
This activity has to be done "only" if asked by Oracle Support Engineer. A preferred method to generate system dump is mentioned in below document : Sun Storage 7000 Unified Storage System: How to Generate Non-Maskable Interrupt (NMI) to Collect a System Core Dump
SolutionCLI method : 7000: maintenance system > diagreboot
BUI method : Open BUI and locate reboot button. You will have to select diagnostic reboot from the popup dialog box.
An Automated SR will be generated as part this reboot.
The support bundle generated for diagnostic reboot will be bigger than a regular bundle as it contains the system dump. References<NOTE:1173064.1> - Sun Storage 7000 Unified Storage System: How to Generate Non-Maskable Interrupt (NMI) to Collect a System Core DumpAttachments This solution has no attachment |
|||||||||||||||||
|