Sun Storagetek 6140: Une Brève Introduction Aux Baies
Sun Storagetek 6140: Une Brève Introduction Aux Baies
Sun Storagetek 6140: Une Brève Introduction Aux Baies
A short introduction to
AGR 2017
Overview
• Dual controller
• 1GB cache (2 FC host ports) or 2 GB cache (4 FC host ports) per controller
• 5 to 16 drives (FC or SATA) per tray
• Up to 7 trays (controller tray + 6 expansion trays)
• Up to 112 drives (112 TB raw capacity)
• RAID 0, 1, 1+0, 3, 5 and 6
• Multipathing
• 2 main firmware versions :
• 06.xx
• 07.xx
• Optional functionalities (Premium Features)
2
Front view
3
Front LED
4
Rear view
5
Controller
(FC)
(FC)
6
Rear LED
7
Expansion trays
Tray ID
I/O module (ESM) 2GB controller : up to 6 expansion trays (7x16 = 112 disks)
P/N 375-3336 1GB controller : up to 3 expansion trays (4x16 = 64 disks)
8
Disks
P/N 541-1406
SATA bracket with interposer SATA/FC board
9
Batteries
• Non-SMART batteries
• To be replaced once expired
• Life expectancy : 1170 days (> 3 years)
• Age can be reset
• No learn cycle
• Hot-swappable
• Externally accessible
• No need to offline/remove the controller
• CAM / SANtricity / Storage Manager are software that must be installed on a host
• Serial connection :
• Menu for configuration (controller IP, array password)
11 • Full shell access (not documented by Sun/Oracle)
Management Interfaces (2)
• Management methods :
• Out-of-band (network)
• Both controllers must be accessible for some operations
• The same CAM / SANtricity management station can manage several arrays
• Preferred method
• In-band
• Using the direct SCSI connection between host and array
• Requires special LUN (Universal X-port, usually target 31) to be mapped to the host
• Using a special agent, an in-band managed array can be
manage by a remote CAM / SANtricity management station
12
CAM : BUI
13
SANtricity : GUI
14
Diagnostic : Support Data (1)
• Collecting Support Data
• CAM (BUI)
https://xxxxxxx:6789
--> Sun StorageTek Common Array Manager
--> select the array (left pane)
--> Service Advisor button (FR: Grille de Service)
--> (new window) Array Troubleshooting and Recovery
(FR: Procédures de dépannage et de reprise de baie)
--> Collecting Support Data (FR: Collecte des données de support)
Then follow the instructions
• CAM (CLI)
--> Identify the array : # ras_admin device_list
--> Collect the Data : # supportData -d <identifier> -p <path> -o <filename>
where <identifier> may be the array name or the IP of one of the controllers
Solaris : /opt/SUNWsefms/bin/
Linux : /opt/sun/cam/private/fms/bin/
Windows (CAM <= 5.0.2) : C:\Program Files\Sun_Microsystems\StorageTek_Mgmt\Component\fms\bin\
15 Windows (CAM >= 5.1) : C:\Program Files\Sun\Common Array Manager\Component\fms\bin\
Diagnostic : Support Data (2)
• Collecting Support Data
• SANtricity / Storage Manager GUI
--> double-click on the array to launch the Array Management window
--> Advanced menu
--> Troubleshooting
--> Collect All Support Data
--> Specify a directory and a filename
--> Start
17
Troubleshooting : listing failures (2)
• Support Data from CAM
• File alarms.txt
• Always an alarm when installed firmwares do not match the ones expected by the version of CAM (harmless, can be ignored)
Alarm ID : alarm1
Description: Tray.00.Controller.B is at revision "06.60.11.11" baseline version is "06.60.22.10"
Tray.01.IOM.B is at revision "98C1" baseline version is "98D3"
Tray.01.Drive.16 is at revision "3092" baseline version is "3292"
Severity : Major
Element : SUN.54065460150.0716AWF00B
GridCode : 57.75.42
Date : 2014-12-03 00:19:37
Alarm ID : alarm14
Description: A hot spare is in use. The affected virtual disk is vdisk.1, failed drive(s) Tray.00.Drive.03,
spare(s) used Tray.01.Drive.16, the affected volume(s) Volume_tray:0.vdisk:1.lun:0
Severity : Major
Element : t0drive3
GridCode : 57.66.1021
Date : 2017-02-03 00:45:48
19
TS : storageArrayProfile.txt
• Setting :
• Baud rate = 38400
• Data bits = 8 Stop bits=1
• Parity = None Flow Control = None
• Establishing a connection :
• Send BREAK until you get the message
Press the space bar within 5 seconds: <S> for Service Interface. <BREAK> for baud rate
• Password : kra16wen
• Service Interface :
• Showing/setting controller IP address
• Resetting array password (SYMbol password, used for communication between
CAM/SANtricity and the array)
24
Usual interventions
25
Usual interventions : batteries (1)
• Info about batteries in Support Data :
Battery: Tray.85.Battery.B
Status: Optimal
Age in days: 1034
Days until replacement: 136
• File stateCaptureData.dmp :
• Fw 06.xx : look for « BATTERY »
26 • Fw 07.xx : look for « bmgrShow »
Usual interventions : batteries (2)
• Non-SMART batteries : to be replaced when they are Failed, Near Expiration or Expired
• No downtime nor controller failover required
• CAM : follow instructions from Service Advisor (FR: Grille de service)
• SANtricity : follow instructions from Recovery Guru
• Reset the age once replaced
27
Usual interventions : batteries (3)
28
Usual interventions : batteries (4)
• Resetting the age (CLI) :
• CAM CLI :
service -d arrayname -c reset -t tXbatY
X : tray ID (usually 85) ; Y : slot ID (1 = Ctler A ; 2 = Ctler B)
Solaris: /opt/SUNWsefms/bin
Linux: /opt/sun/cam/private/fms/bin
Windows: c:\Program Files\Sun\Common Array Manager\Component\fms\bin
• SANtricity SMcli :
smcli -n arrayname [-p password] -c "reset storageArray batteryInstallDate controller=X;“
smcli @IP_A [@IP_B][-p password] -c "reset storageArray batteryInstallDate controller=X;“
X : either A or B
Solaris, Linux : /opt/SMgr/client/
Windows : C:\Program Files\StorageManager\client\
29
Usual interventions : batteries (5)
• Resetting the age (serial shell) :
• Serial shell :
• menu « M » (Boot Operation Menu) -> 8) Special Services Menu -> 6) Install Battery
BOOT SPECIAL OPERATIONS MENU
-> M
1) Change Board Serial Number
NOTICE: The BOOT OPERATIONS MENU has been invoked too late for 2) Reinitialize All NVSRAM
proper operation of some activities, including Isolation Diagnostics. 3) Change Password
You may wish to restart this controller again and press Control-B 4) Change Ethernet Node Address
IMMEDIATELY after seeing the start-up indicator ("-=<###>=-"). 5) Change Subsystem Name
6) Install Battery
BOOT OPERATIONS MENU 7) Reserved
Q) Quit Menu
1) Perform Isolation Diagnostics 10) Serial Interface Mode Menu
2) Download Permanent File 11) Display Hardware Configuration Enter Selection: 6
3) Reserved 12) Change Hardware Configuration Menu Please enter battery number to set installation date(0 or 1):0
4) Dump NVSRAM Group 13) Development Options Menu
5) Patch NVSRAM Group 14) Display Memory Error Log Current date: 09/28/2017
6) Set Real Time Clock 15) Manufacturing Setup Menu Current battery 0 installation date: 09/15/2015
7) Display Board Configuration R) Restart Controller
8) Special Services Menu Q) Quit Menu Use this operation to inform the controller that the batteries for the
9) Display Exception Message cache memory have been replaced, and to identify the date the new
batteries were installed. (Avoid using this function if the batteries
Enter Selection: 8 have not been replaced; otherwise, data still remaining in cache may be lost.)
• File stateCaptureData.dmp :
• Fw 06.xx : look for « cfgPhyList »
31
• Fw 07.xx : look for « vdmShowDriveList »
Usual interventions : disks (2)
32
Usual interventions : disks (3)
• CAM CLI :
service -d arrayname -c fail -t tXdriveY
X : tray ID (usually 85) ; Y : slot ID
Solaris: /opt/SUNWsefms/bin
Linux: /opt/sun/cam/private/fms/bin
Windows: c:\Program Files\Sun\Common Array Manager\Component\fms\bin
• SANtricity SMcli :
smcli -n arrayname [-p password] -c "set physicalDisk [TrayID,slotID] operationalState=failed;“
smcli @IP_A [@IP_B][-p password] -c "set physicalDisk [TrayID,slotID] operationalState=failed;“
Solaris, Linux : /opt/SMgr/client/
Windows : C:\Program Files\StorageManager\client\
33
Usual interventions : controllers (1)
• File stateCaptureData.dmp :
• Fw 06.xx : look for « getObjectGraph_MT 99 »
• Fw 07.xx : look for « [Controller] »
34
Usual interventions : controllers (2)
35
Usual interventions : controllers (3)
36
Usual interventions : controllers (4)
• SANtricity SMcli :
smcli -n arrayname [-p password] -c “set controller [a] availability=offline;”
smcli @IP_A [@IP_B][-p password] -c “set controller [a] availability=offline;”
X : a or b
Solaris, Linux : /opt/SMgr/client/
Windows : C:\Program Files\StorageManager\client\
37
Usual interventions : controllers (5)
38
Advanced topics, questions, …
• Issues :
• Controller lockdown
• Controller held in reset
• Unreadable sectors
• RDAC / AVT
• Volume recovery
• …
• Questions
39
On https://cloud.evernex.com/url/gtscuslh5wvh
40