4 Posts

1263

May 8th, 2021 12:00

Powervault MD3220 second controller showing alerts.

Hi,

I have attached the log during boot process. Can anyone let me know what steps to take. Thank you. Please note all cables are disconnected. 

Reset, Power-Up Diagnostics - Loop 1 of 1
3600 Processor DRAM
01 Data lines Passed
02 Address lines Passed
3300 NVSRAM
01 Data lines Passed
4410 Ethernet 82574 1
01 Register read Passed
02 Register address lines Passed
6D40 Bobcat
02 Flash Test Passed
3700 PLB SRAM
01 Data lines Passed
02 Address lines Passed
6D50 LSISAS2008 IOC 1
01 Register Read Test Passed
02 Register Address Lines Test Passed
03 Register Data Lines Test Passed
3900 Real-Time Clock
01 RT Clock Tick Passed
Diagnostic Manager exited normally.


Current date: 05/09/21 time: 00:26:06

NetApp, Inc. RAID Controller
Copyright 2008-2014, NetApp, Inc. All Rights Reserved.
Copyright 1984-2006 Wind River Systems, Inc.
VxWorks: VxWorks 6.5 Kernel: WIND version 2.10
Model: 2660 Firmware version: 07.8405/08/21-18:38:28 (tRAID): NOTE: Set Powerup State
.56.6005/08/21-18:38:29 (tRAID): SOD Sequence is Normal, 0 on controller B


->
Serial Port shell started.
ERROR: Remap entry not found for ssid=0x82.
05/08/21-18:38:29 (tRAID): NOTE: Turning on tray summary fault LED
05/08/21-18:38:29 (tRAID): WARN: In getExpectedMdplVpdData, unknown SubsystemID of 130 was found - may result in controller lockdown
05/08/21-18:38:29 (tRAID): WARN: In verifySBBEnclosure, validation failed - expected boardProductName of len:0 'Unknown' but read len:30 '24-Slot SAS 6G BackPlane 2U A '
05/08/21-18:38:29 (tRAID): WARN: Suspending Ctlr: "SBB_Ctlr_Validation_Failed"
05/08/21-18:38:29 (tRAID): NOTE: Flashing tray summary fault LED
05/08/21-18:38:29 (tRAID): WARN: Controller entering ClientErr lockdown state...
0xee8ff8 (tNetCfgInit): miiPhyInit check cable connection
05/08/21-18:38:58 (tNetCfgInit): NOTE: eth0: LinkDown event
05/08/21-18:38:59 (tNetCfgInit): NOTE: Network Ready

->
->
->
-> lemClearLockdown

-=<###>=-
Instantiating /ram as rawFs, device = 0x1
Formatting /ram for DOSFS
Instantiating /ram as rawFs, device = 0x1
Formatting...Retrieved old volume params with %38 confidence:
Volume Parameters: FAT type: FAT32, sectors per cluster 0
0 FAT copies, 0 clusters, 0 sectors per FAT
Sectors reserved 0, hidden 0, FAT sectors 0
Root dir entries 0, sysId (null) , serial number 10000
Label:" " ...
Disk with 1024 sectors of 512 bytes will be formatted with:
Volume Parameters: FAT type: FAT12, sectors per cluster 1
2 FAT copies, 1010 clusters, 3 sectors per FAT
Sectors reserved 1, hidden 0, FAT sectors 6
Root dir entries 112, sysId VXDOS12 , serial number 10000
Label:" " ...
Instantiating /ram as rawFs, device = 0x1
OK.

RTC Error: Real-time clock device is not working

Adding 13891 symbols for standalone.
.Length: 0x13c Bytes
.Version ver03.0A


Current date: 05/09/21 time: 00:36:58

NetApp, Inc. RAID Controller
Copyright 2008-2014, NetApp, Inc. All Rights Reserved.
Copyright 1984-2006 Wind River Systems, Inc.
VxWorks: VxWorks 6.5 Kernel: WIND version 2.10
Model: 2660 Firmware version: 07.8405/08/21-18:49:21 (tRAID): SOD Sequence is Normal, 0 on controller B
.56.60

->
Serial Port shell started.
ERROR: Remap entry not found for ssid=0x82.
05/08/21-18:49:22 (tRAID): NOTE: Turning on tray summary fault LED
05/08/21-18:49:22 (tRAID): WARN: In getExpectedMdplVpdData, unknown SubsystemID of 130 was found - may result in controller lockdown
05/08/21-18:49:22 (tRAID): WARN: In verifySBBEnclosure, validation failed - expected boardProductName of len:0 'Unknown' but read len:30 '24-Slot SAS 6G BackPlane 2U A '
05/08/21-18:49:22 (tRAID): WARN: Suspending Ctlr: "SBB_Ctlr_Validation_Failed"
05/08/21-18:49:22 (tRAID): NOTE: Flashing tray summary fault LED
05/08/21-18:49:22 (tRAID): WARN: Controller entering ClientErr lockdown state...
0xd8b920 (tNetCfgInit): miiPhyInit check cable connection
05/08/21-18:49:51 (tNetCfgInit): NOTE: eth0: LinkDown event
05/08/21-18:49:52 (tNetCfgInit): NOTE: Network Ready

 

Moderator

 • 

9.6K Posts

May 10th, 2021 09:00

Ylaval,

 

The system is in a lockdown state and it needs to be cleared in order to see what else is wrong and causing the issue.
If you need to know how to clear the lockdown then you can look online for the steps or if the system is still under warranty you can call in & support can assist with clearing the lockdown for you.
Let me know if this helps.

4 Posts

May 10th, 2021 16:00

Thank you,

The system is out of warranty since 2018. I have tried logging via the vxWorks shell to no avail. The three passwords I've tried seem to be wrong.

Does this step have to be done via the CLI and a serial cable or can it be done via the MDSS?

Thank you.

Moderator

 • 

9.4K Posts

May 10th, 2021 17:00

Hi,

Unfortunately, it has to be done via the CLI.

4 Posts

May 10th, 2021 20:00

Will we be able to complete this by ourselves?

 

Moderator

 • 

4.7K Posts

May 11th, 2021 06:00

Hello ylaval,

 

See if this similar post can assist you:

 

https://dell.to/3uF50gK

 

4 Posts

May 11th, 2021 14:00

Thank you, will have a look.
No Events found!

Top