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-71-1443820.1
Update Date:2012-06-19
Keywords:

Solution Type  Technical Instruction Sure

Solution  1443820.1 :   Pillar Axiom: How to run ClearFailureHistory on R3 and R4  


Related Items
  • Pillar Axiom 300 Storage System
  •  
  • Pillar Axiom 600 Storage System
  •  
  • Pillar Axiom 500 Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Pillar Axiom>SN-DK: Ax600
  •  
  • .Old GCS Categories>Sun Microsystems>Storage - Disk>Pillar Axiom
  •  




In this Document
Goal
Fix


Applies to:

Pillar Axiom 600 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 500 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 300 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.
For systems running R3 or R4


Goal

To Recover a Disabled Slammer Control Unit

Fix


1. Clear failure count:
- Download the file ClearFailureHist.exe (Provided by Support) to a 32 bit Windows client.
- Run ClearFailureHist.exe script from a Windows command prompt.
- When prompted for an IP address enter the shared pilot IP (GUI IP).

OR

-Run CLI command ReenableAllSlammers

2. Cold boot the impacted slammer control unit:
- Remove the two power cords from the impacted control unit (1 power cord if the Axiom is an AX300 model), wait 10 seconds, re-insert.
- Wait patiently as it may take 5-20 minutes to come back up.


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