Pivotal Knowledge Base

Follow

For DH code 13.11001, the reported Physical Disk slot number may not be correct

Environment 

  • DCA v2 
  • DCA software version 2.0.3.0 and below

Problem 

In some cases, on DCA v2, Dial Home messages for drive related events (DH code 13.11001) may not report the correct slot location. This issue is observed on segment servers with 24 drives aka "Dragon-24". See snippet of Dial Home below :

For more information regarding Symptom Code 13.11001
Clarify Id: APM00131305219
Vendor: EMC
DeviceType: DCA1
SerialNumber: APM00131305219
Platform: 2.0.2.0
OS: Linux
OS_VER: 2.6.32-358.18.1.el6.x86_64
EmbedLevel: 2
InternalMaxSize: 51200
Ucode_Ver: 4.2.6.3DT4 build 1
UNIFIED_PRODUCT: 0
IP_Address: Not Available
SymptomCode: 13.11001
Category: Status
Severity: Warning
Status: OK
Component: sdw63 : sdw63
ComponentID: DCA2-SS
FirstTime: 03/26/2014 18:03:13
Description: Physical Disk 21 Status: Dev Id 18 : Adp Id 1 : CONFIGURED-SHIELDED

Now, from the snippet of the command 'CmdTool2 -PDlist -a#' 

Slot Number: 10 <----- drive in slot 
Enclosure position: 0
Firmware state: Unconfigured(bad) <---- 
Enclosure Device ID: 20
Slot Number: 11
Enclosure position: 0
Firmware state: Online, Spun Up

On a DCA v2, for Dragon-24 server, the mapping to physical slot location to that enumerated by each of the RAID controllers is illustrated below :

From the above diagram, note that for controller a1, controller "Slot Number" 10 maps to Physical Slot 22 as per the server diagram in the maintenance guide. However, Dial Home is reporting physical slot 21, which is incorrect. 

Cause

At this time, this issue is being investigated via internal JIRA DCA-8337

Note that this issue does not affect all of the install base of Dragon-24 servers

Solution

Workaround procedure to identify the correct physical slot location :

1. Run the following command : CmdTool2 -PDList a# 

From the above output, note the "Slot Number" for the drive that is faulty.

Slot Number: 10 <----- drive in slot 
Enclosure position: 0
Firmware state: Unconfigured(bad) <---- 
Enclosure Device ID: 20
Slot Number: 11
Enclosure position: 0
Firmware state: Online, Spun Up

2. Map the Physical Slot location based on the table below

Raid Controller a0    Raid Controller a1
Physical Slot Controller Slot Physical Slot Controller Slot
0 0 12 0
1 1 13 1
2 2 14 2
3 3 15 3
4 4 16 4
5 5 17 5
6 6 18 6
7 7 19 7
8 8 20 8
9 9 21 9
10 10 22 10
11 11 23 11

3. Update the action plan for drive dispatch deduced from the table above.  Final fix will be available in a future DCA s/w release

Notes

Before dispatching a drive on DCA V2 Dragon-server, always note the correct physical drive based on the output from 'CmdTool2 -PDlist -a#' , where "#" is the controller number while updating the Action Plan template.

If the drive is marked as "Configured(bad)" or "Unconfigured(good)", the amber LED on the drive will be blinking. Always have the CE verify the blinking amber disk slot to the one in the Action Plan.

Comments

Powered by Zendesk