Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1511868.1
Update Date:2018-04-06
Keywords:

Solution Type  Technical Instruction Sure

Solution  1511868.1 :   Pillar Axiom: How to manually reset a Brick RAID Controller  


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




In this Document
Goal
Solution


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: support cli commands

Applies to:

Pillar Axiom 500 Storage System - Version All Versions and later
Pillar Axiom 300 Storage System - Version All Versions and later
Pillar Axiom 600 Storage System - Version All Versions and later
All Platforms

Goal

 How to reset a Brick RAID controller using Supporttool (R4) or PCLI (R5)

Solution

Examples listed below on how to reset Brick002 RC0. Note that the command also uses SimulateFault=0 which instructes the active pilot not to generate a callhome.

Best Practice is to restart the controller from its companion (useful in case of a controller stuck in booting condition).

 

Release 5 Example:

This command will be sent to BRICK-002 RC0 to restart itself

pcli sub -u pillar -H <InsertManagementIPAddress> PerformRestartRaidController BrickIdentity="/BRICK-002" RaidController="CONTROLLER_0" PassRestartToCompanion="0" SimulateFault="0"

 

This command will be sent to BRICK-002 RC1 to restart BRICK-002 RC0:

pcli sub -u pillar -H <InsertManagementIPAddress> PerformRestartRaidController BrickIdentity="/BRICK-002" RaidController="CONTROLLER_1" PassRestartToCompanion="1" SimulateFault="0"

 

NOTE: When the PassRestartToCompanion = 0, the RaidController specified will be reset. When the PassRestartToCompanion = 1, the companion RaidController specified will be reset

 

Additionally the supported interface in r5 is axiomcli  - here is the syntax.

  axiomcli brick -restartRaidController -brick brick-id-or-fqn

            -controller {cu0 | cu1 | both} [-restartCompanion]

            [-verify]

            [{-outputformat | -o} {text | xml}]

            [-sessionKey session-key]

            [-timeout timeout-in-seconds]

The below command issues a companion restart to CU1 from CU0 – best used if FC2 of the controller you want to reset is offline.

Axiomcli brick –restartRaidController –brick BRICK-002 –controller cu0 –restartCompanion

The below command resets cu0 directly

Axiomcli brick –restartRaidController –brick BRICK-002 –controller cu0

The below command resets both controllers.

Axiomcli brick –restartRaidController –brick BRICK-002 –controller both

 

Release 4 Example:

The below command will be sent to RC0 to restart itself

supporttool sub -H 10.126.10.212 RestartRAIDController Brick=/Brick002 RAIDControllerNumber=0 Force=1 SimulateFault=0 

The below command will be sent to RC1 to restart RC0

supporttool sub -H 10.126.10.212 RestartRAIDController Brick=/Brick002 RAIDControllerNumber=1 Force=1 Buddy=true SimulateFault=0  

         

Reset in either R4 or R5 from within the console: (Do not run unless instructed)

rst 1234 <-- Resets the controller you are logged into

crst 1234 <- Resets the partner (buddy) controller of the controller you are logged into


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback