lockdown MD3200i

Hi

The easiest way to get you unit out of lockdown when you have changed the hard drives is to do the following

1. remove 1 controller and have the serial cable connected to the other controller

2. when you see ### press ctrl and b

3. you will have a menu appear, select 10 for serial interface, 1 for console only then q to quit and r to reboot

4. when the controller has rebooted and you see the lockdown message press enter for console prompt and type LemClearLockdown (note case sensitive)

5. let the controller reboot

6. repeat with the alternative controller, removing the controller you have just worked on

7. insert both controllers and see if MDSN can detect the unit, it may still be marked as needs attention, this is due to being in recovery mode, follow the recovery guru's instructions to clear the recovery mode

Hope this helps you

Dave

@trodai0080 
I know it’s been a long time, but could you give more detailed step by step instructions?

1. I have established a putty connection to controller 1/2.

2. I enter Crtrl+B (^B) which opens the BOOT OPERATIONS MENU.

3. I type 10 (Enter Selection:10) but then where do I type 1 Q R if following your previous instructions? Striking the enter key after typing 10 starts the Reset, Power-Up Diagnostics - Loop 1 of 1. And after all of that plays through the console sits for a minute or so and then the fans spin up and a controller lockdown warning appears but I can’t type anything.

Hello @R1-matte,

You are asking on a post 4 years old. I am not sure if you will receive any response from the same person who wrote it.

Regarding your question, which lockdown state are your controllers in as there are many different states and each has a different fix?

Regards.

@DiegoLopez 

-=<###>=-
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 f10000
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 f10000
Label:" " ...

RTC Error: Real-time clock device is not working
OK.

Adding 14607 symbols for standalone.

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
7000 SE iSCSI BE2 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.
11/25/20-13:48:14 (tSystem): ERROR: FPGA FW is out of date
"Rhone03 rev17" currently in use
"Rhone03 rev20" available for update
11/25/20-13:48:18 (tNetCfgInit): NOTE: eth0: LinkUp event
11/25/20-13:48:19 (tNetCfgInit): NOTE: Acquiring network parameters for interface gei0 using DHCP
11/25/20-13:48:23 (ipdhcpc): NOTE: netCfgDhcpReplyCallback :: received OFFER on interface gei0, unit 0
11/25/20-13:48:24 (ipdhcpc): WARN: **WARNING** The DHCP Server did not assign a permanent IP for gei0.
11/25/20-13:48:24 (ipdhcpc): WARN: Network access to this controller may eventually fail.
11/25/20-13:48:24 (ipdhcpc): NOTE: DHCP server: 10.10.0.11
11/25/20-13:48:24 (ipdhcpc): NOTE: Client IP routers: 10.10.0.1
11/25/20-13:48:24 (ipdhcpc): NOTE: Client DNS name servers: 10.10.0.11
11/25/20-13:48:24 (ipdhcpc): NOTE: DNS domain name: radio1inc.net
11/25/20-13:48:24 (ipdhcpc): NOTE: Assigned IP address: 10.10.2.253
11/25/20-13:48:24 (ipdhcpc): NOTE: Assigned subnet mask: 255.255.252.0
11/25/20-13:48:24 (tNetReset): NOTE: Network Ready
Current date: 11/25/20 time: 13:48:39

Send for Service Interface or baud rate change
11/25/20-13:48:38 (tRAID): NOTE: Set Powerup State
11/25/20-13:48:39 (tRAID): SOD Sequence is Normal, 0 on controller A
11/25/20-13:48:39 (tRAID): NOTE: loading flash file: ECTDell
11/25/20-13:48:39 (tRAID): NOTE: unloading flash file: ECTDell
11/25/20-13:48:40 (tRAID): NOTE: I2C transaction returned 0x8012b001
11/25/20-13:48:40 (tRAID): NOTE: I2C transaction returned 0x8012b101
11/25/20-13:48:40 (tRAID): NOTE: Turning on tray summary fault LED
11/25/20-13:48:40 (tRAID): NOTE: Installed Protocols:
11/25/20-13:48:40 (tRAID): NOTE: Required Protocols:
11/25/20-13:48:40 (tRAID): NOTE: loading flash file: iSCSI
11/25/20-13:48:41 (tRAID): NOTE: loading flash file: MTLSEBET1G
*** Disabled FULL TRACE ***
11/25/20-13:48:42 (tRAID): WARN: MTLSE: before mtl_create_pool:IO task size: 0x140
11/25/20-13:48:42 (tRAID): NOTE: I2C transaction returned 0x8012b004
11/25/20-13:48:43 (tRAID): NOTE: DSM: Current revision 7
11/25/20-13:48:43 (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
11/25/20-13:48:43 (tRAID): NOTE: cmgrCtlr: Board Manager HostBoardData Model Name for slot 0: 0501
11/25/20-13:48:43 (tRAID): NOTE: RCBBitmapManager total RPA size = 1761607680
11/25/20-13:48:43 (tRAID): NOTE: init: ioc: 0, PLVersion: 13-075-70-00
11/25/20-13:48:43 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=0
11/25/20-13:48:43 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=1
11/25/20-13:48:43 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=2
11/25/20-13:48:43 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=3
11/25/20-13:48:43 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=4
11/25/20-13:48:43 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=5
11/25/20-13:48:43 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=6
11/25/20-13:48:43 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=7
11/25/20-13:48:44 (IOSched): NOTE: SAS Expander Added: expDevHandle:x11 enclHandle:x2 numPhys:25 port:2 ioc:0 channel:0 numEntries:22
11/25/20-13:48:44 (IOSched): NOTE: SAS Expander Added: expDevHandle:x12 enclHandle:x3 numPhys:25 port:3 ioc:0 channel:1 numEntries:22
11/25/20-13:48:45 (tSasEvtWkr): NOTE: Alt controller path up on channel:0 devH:x14 expDevH:x11 phy:16 itn:1
11/25/20-13:48:45 (tSasExpChk): NOTE: Local Expander Firmware Version: 00.00.80.16
11/25/20-13:48:45 (tSasExpChk): NOTE: Enabling this controller's expander phys, channel=0
11/25/20-13:48:45 (tSasExpChk): NOTE: sasExpanderCheck send icon connection up event channel:0
11/25/20-13:48:45 (sasEnPhys): NOTE: sasEnableDrivePhysTask: 12 phys enabled on channel 0
11/25/20-13:48:46 (tRAID): NOTE: CrushMemoryPoolMgr: platform and memory (CPU MemSize:2048), adjusted allocating size to 65536 for CStripes
11/25/20-13:48:46 (tSasEvtWkr): NOTE: Alt controller path up on channel:1 devH:x13 expDevH:x12 phy:12 itn:4
11/25/20-13:48:48 (tRAID): SOD: Instantiation Phase Complete
11/25/20-13:48:47 (tSasExpChk): NOTE: Alternate Expander Firmware Version: 00.00.80.16
11/25/20-13:48:47 (tRAID): WARN: sodLockdownCheck: sodSequence update: CtlrLockdown
11/25/20-13:48:47 (tRAID): NOTE: Inter-Controller Communication Channels Opened
11/25/20-13:48:47 (tRAID): NOTE: LockMgr Role is Master
11/25/20-13:48:47 (tSasExpChk): NOTE: Enabling alternate controller's expander phys, channel=1
11/25/20-13:48:47 (tSasExpChk): NOTE: sasExpanderCheck send icon connection up event channel:1
11/25/20-13:48:47 (sasEnPhys): NOTE: sasEnableDrivePhysTask: 0 phys enabled on channel 1
11/25/20-13:48:48 (tHckReset): NOTE: Firmware running line - OFF
11/25/20-13:48:49 (tHckReset): NOTE: HealthCheck: Alt Ctl: 1 Reset_Failure, state: 0 Start
11/25/20-13:48:51 (tSasDiscCom): NOTE: SAS: Initial Discovery Complete Time: 43 seconds since last power on/reset, 10 seconds since sas instantiated
11/25/20-13:48:51 (tSasDiscCom): NOTE: sasDiscoveryCompleteFirstTime send icon connection up event channel:0
11/25/20-13:48:51 (tSasDiscCom): NOTE: sasDiscoveryCompleteFirstTime send icon connection up event channel:1
11/25/20-13:49:21 (tRAID): NOTE: WWN baseName 0008782b-cb15f8f6 (valid==>SigMatch)
11/25/20-13:49:21 (tRAID): NOTE: spmEarlyData: No data available
11/25/20-13:49:21 (tRAID): NOTE: sebeReadEEPROMChecksum: EEPROM checksum match: 0x81986278
11/25/20-13:49:21 (tRAID): NOTE: ServerEngines BladeEngine 2 Firmware Update Utility v2.901.242.0
Copyright 2009 ServerEngines Corpo
11/25/20-13:49:21 (tRAID): NOTE:
11/25/20-13:49:21 (tRAID): NOTE: Found BE card 0x0 at 2.0 bar1-base 0xf0200000 bar2-base 0xf0220000 dev 0x323164c
11/25/20-13:49:21 (tRAID): NOTE: flash_rbver = 2.0.3.768
11/25/20-13:49:21 (tRAID): NOTE: flash_armfwver = 2.901.326.0
11/25/20-13:49:23 (tRAID): NOTE: ufi_rbver = 2.0.3.768
11/25/20-13:49:23 (tRAID): NOTE: ufi_armfwver = 2.901.326.0
11/25/20-13:49:23 (tRAID): NOTE: Flash on BladeEngine at 02 : 00 matches UFI SEBE2T1G
11/25/20-13:49:23 (tRAID): NOTE: Target:irq_ptr:0x0xe3aeb0, func:0x0, bcmId:0x0
11/25/20-13:49:23 (tRAID): NOTE: VendorID 0x19a2 DeviceId 0x210 bcmId 0 BDF 2.0.0
11/25/20-13:49:23 (tRAID): NOTE: Target:VKI_INT_CONNECT success:status:0x0
11/25/20-13:49:23 (tRAID): ERROR: Target:ISR registered:irq_ptr:0xe3aeb0, phba:0x322eb80, func:0x0
11/25/20-13:49:23 (tRAID): NOTE: BcmId [0] PCI [2.0.0]
11/25/20-13:49:23 (tRAID): NOTE: DevId 0x0210 VendId 0x19a2
11/25/20-13:49:23 (tRAID): NOTE: BAR0 IO base 0x00000000 size 0
11/25/20-13:49:23 (tRAID): NOTE: BAR1 MEM base 0xf0200000 size 1
11/25/20-13:49:23 (tRAID): NOTE: BAR2 MEM base 0xf0220000 size 1
11/25/20-13:49:23 (tRAID): NOTE: BAR4 MEM base 0xf0240000 size 1
11/25/20-13:49:23 (tRAID): NOTE: MPU_EP_SEMAPHORE 0x0000c000
Driver Build Date:Apr 13 2017, Time:18:13:48
ServerEngines iSCSI Target Driver loaded
iSCSI Firmware Version:2.901.326.0
iSCSI Driver Version:2.901.242.0
Found BladeEngine2 in Gen2 x8 PCIe slot
11/25/20-13:49:24 (tRAID): NOTE: RPA memory region : start 0x471977e00 size 16777216 (ConIO-size 16777216) registered for pre-post data buffers on port 0
11/25/20-13:49:24 (tRAID): NOTE: sebeReadEEPROMChecksum: EEPROM checksum match: 0x81986278
11/25/20-13:49:25 (tRAID): NOTE: Target:irq_ptr:0x0xe3ad68, func:0x1, bcmId:0x1
11/25/20-13:49:25 (tRAID): NOTE: VendorID 0x19a2 DeviceId 0x210 bcmId 1 BDF 2.0.1
11/25/20-13:49:25 (tRAID): NOTE: Target:VKI_INT_CONNECT success:status:0x0
11/25/20-13:49:25 (tRAID): ERROR: Target:ISR registered:irq_ptr:0xe3ad68, phba:0x322f2a0, func:0x1
11/25/20-13:49:25 (tRAID): NOTE: BcmId [1] PCI [2.0.1]
11/25/20-13:49:25 (tRAID): NOTE: DevId 0x0210 VendId 0x19a2
11/25/20-13:49:25 (tRAID): NOTE: BAR0 IO base 0x00000000 size 0
11/25/20-13:49:25 (tRAID): NOTE: BAR1 MEM base 0xf0260000 size 1
11/25/20-13:49:25 (tRAID): NOTE: BAR2 MEM base 0xf0280000 size 1
11/25/20-13:49:25 (tRAID): NOTE: BAR4 MEM base 0xf02a0000 size 1
11/25/20-13:49:25 (tRAID): NOTE: MPU_EP_SEMAPHORE 0x0000c000
Driver Build Date:Apr 13 2017, Time:18:13:48
ServerEngines iSCSI Target Driver loaded
iSCSI Firmware Version:2.901.326.0
iSCSI Driver Version:2.901.242.0
Found BladeEngine2 in Gen2 x8 PCIe slot
11/25/20-13:49:26 (tRAID): NOTE: RPA memory region : start 0x472977e00 size 16777216 (ConIO-size 16777216) registered for pre-post data buffers on port 1
11/25/20-13:49:26 (tRAID): NOTE: sebeReadEEPROMChecksum: EEPROM checksum match: 0x81986278
11/25/20-13:49:27 (tRAID): NOTE: Target:irq_ptr:0x0xe3ac20, func:0x2, bcmId:0x2
11/25/20-13:49:27 (tRAID): NOTE: VendorID 0x19a2 DeviceId 0x210 bcmId 2 BDF 2.0.2
11/25/20-13:49:27 (tRAID): NOTE: Target:VKI_INT_CONNECT success:status:0x0
11/25/20-13:49:27 (tRAID): ERROR: Target:ISR registered:irq_ptr:0xe3ac20, phba:0x322f9c0, func:0x2
11/25/20-13:49:27 (tRAID): NOTE: BcmId [2] PCI [2.0.2]
11/25/20-13:49:27 (tRAID): NOTE: DevId 0x0210 VendId 0x19a2
11/25/20-13:49:27 (tRAID): NOTE: BAR0 IO base 0x00000000 size 0
11/25/20-13:49:27 (tRAID): NOTE: BAR1 MEM base 0xf02c0000 size 1
11/25/20-13:49:27 (tRAID): NOTE: BAR2 MEM base 0xf02e0000 size 1
11/25/20-13:49:27 (tRAID): NOTE: BAR4 MEM base 0xf0300000 size 1
11/25/20-13:49:27 (tRAID): NOTE: MPU_EP_SEMAPHORE 0x0000c000
Driver Build Date:Apr 13 2017, Time:18:13:48
ServerEngines iSCSI Target Driver loaded
iSCSI Firmware Version:2.901.326.0
iSCSI Driver Version:2.901.242.0
Found BladeEngine2 in Gen2 x8 PCIe slot
11/25/20-13:49:27 (tRAID): NOTE: RPA memory region : start 0x473977e00 size 16777216 (ConIO-size 16777216) registered for pre-post data buffers on port 2
11/25/20-13:49:28 (tRAID): NOTE: sebeReadEEPROMChecksum: EEPROM checksum match: 0x81986278
11/25/20-13:49:28 (tRAID): NOTE: Target:irq_ptr:0x0xe3aad8, func:0x3, bcmId:0x3
11/25/20-13:49:28 (tRAID): NOTE: VendorID 0x19a2 DeviceId 0x210 bcmId 3 BDF 2.0.3
11/25/20-13:49:28 (tRAID): NOTE: Target:VKI_INT_CONNECT success:status:0x0
11/25/20-13:49:28 (tRAID): ERROR: Target:ISR registered:irq_ptr:0xe3aad8, phba:0x32300e0, func:0x3
11/25/20-13:49:28 (tRAID): NOTE: BcmId [3] PCI [2.0.3]
11/25/20-13:49:28 (tRAID): NOTE: DevId 0x0210 VendId 0x19a2
11/25/20-13:49:28 (tRAID): NOTE: BAR0 IO base 0x00000000 size 0
11/25/20-13:49:28 (tRAID): NOTE: BAR1 MEM base 0xf0320000 size 1
11/25/20-13:49:28 (tRAID): NOTE: BAR2 MEM base 0xf0340000 size 1
11/25/20-13:49:28 (tRAID): NOTE: BAR4 MEM base 0xf0360000 size 1
11/25/20-13:49:28 (tRAID): NOTE: MPU_EP_SEMAPHORE 0x0000c000
Driver Build Date:Apr 13 2017, Time:18:13:48
ServerEngines iSCSI Target Driver loaded
iSCSI Firmware Version:2.901.326.0
iSCSI Driver Version:2.901.242.0
Found BladeEngine2 in Gen2 x8 PCIe slot
11/25/20-13:49:29 (tRAID): NOTE: RPA memory region : start 0x474977e00 size 16777216 (ConIO-size 16777216) registered for pre-post data buffers on port 3
11/25/20-13:49:30 (tRAID): SOD: Pre-Initialization Phase Complete
11/25/20-13:49:38 (tRAID): WARN: CmgrLockdownException: CORRUPT DBM DATABASE DETECTED - LOCKDOWN Type=6
11/25/20-13:49:38 (tRAID): WARN: ACS: testCommunication: Domi Exception caught: IconSendInfeasibleException Error
11/25/20-13:49:38 (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Status: 0
11/25/20-13:49:38 (tRAID): WARN: ACS: autoCodeSync(): Skipped since alt not communicating.
11/25/20-13:49:39 (tRAID): SOD: Code Synchronization Initialization Phase Complete
11/25/20-13:49:38 (tRAID): WARN: Lockdown case-DB CORRUPT. NVPS did not update from Sstor.
11/25/20-13:49:38 (tRAID): NOTE: Controller is in lockdown; skipping sendStagedFirmwareUpdateEvent()
11/25/20-13:49:39 (tRAID): SOD: Initialization Phase Complete
==============================================
Title: Disk Array Controller
Copyright 2008-2017 NetApp, Inc. All Rights Reserved.

Name: RC
Version: 08.20.24.60
Date: 04/13/2017
Time: 18:11:47 CDT
Models: 2660
Manager: devmgr.v1120api13.Manager
==============================================

11/25/20-13:49:38 (tRAID): NOTE: SYMbol available
11/25/20-13:49:38 (tRAID): WARN: *********************************************************
11/25/20-13:49:38 (tRAID): WARN: *********************************************************
11/25/20-13:49:38 (tRAID): WARN: ** **
11/25/20-13:49:38 (tRAID): WARN: ** WARNING!!!!!! **
11/25/20-13:49:38 (tRAID): WARN: ** **
11/25/20-13:49:38 (tRAID): WARN: ** This controller is locked down due to detected **
11/25/20-13:49:38 (tRAID): WARN: ** corruption in the primary database. **
11/25/20-13:49:38 (tRAID): WARN: ** In order to prevent any configuration loss, the **
11/25/20-13:49:38 (tRAID): WARN: ** backed up database must be restored. **
11/25/20-13:49:38 (tRAID): WARN: ** **
11/25/20-13:49:38 (tRAID): WARN: ** **
11/25/20-13:49:38 (tRAID): WARN: *********************************************************
11/25/20-13:49:38 (tRAID): WARN: *********************************************************
11/25/20-13:49:39 (tRAID): SOD: sodComplete Notification Complete
11/25/20-13:49:39 (tRAID): sodMain CtlrLockdown sequence finished, elapsed time = 60 seconds
11/25/20-13:49:39 (tRAID): sodMain complete
11/25/20-13:49:38 (tRAID): WARN: SOD lockdown sequence complete - suspending...

The unit has been out of warranty for a long while.

The original disks were removed (which is what caused this issue). Would buying new controllers and putting them into the chassis resolve this issue or brick the new controllers as well?

Ok, so it looks like you have an error caused by a corruption in the primary database. Clearing the lockdown will not fix the issue. If your PowerVault is still under warranty, you really need to contact your local support and they will have to escalate the issue to a L3 Analyst. They can try to recover the data using On Board Backup (OBB) or DBM file only if the system has a Dynamic Disk Pool (DDP) as well as on Disk Group configuration.

This is a complex procedure that can only be applied by a L3 Analyst in a PowerVault that is still in warranty.

Hope this helps.
Regards.

Hello R1-matte,

Buying a new controller will not resolve your issue.  When you removed the disk there must have been a DDP, or Disk group & virtual disk that was still configured.  When you inserted the new drives, your MD couldn’t find the configuration so that is the reason for the lockdown in your case.  If you are not trying to recover any data, then you can do a Syswipe on your controllers and it will make your system back to factory.

I don't need to save any information, I just want to start fresh and get this unit back to a functional state.

What steps do I need to perform to syswipe and get there?

Hello R1-matte,

To do a syswipe you need to access VXShellusr account on your MD3200i.  There is a password that is needed to login, however, that password is only provided to support.  You can do a search to find syswipe instructions, as syswipe is also done by support as well.

Hello , I have the same question. I Can not access to the MD3200 via both client and Putty. The storage can not work when i turn off the power and reboot. The disk indicator is off.   I do not think that both controllers are down.  Any other ways to fix this problem.  Can you support this? 

Error Information with putty connecting ,  noting works when i pressed " ctrl+break " or "ESC;

-=<###>=-
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:" " ...

RTC Error: Real-time clock device is not working
OK.

Adding 13818 symbols for standalone.

Hello  R1-matte,

   I have the same problem with MD3200;  Till now,  Have you solved your problem yet?  Can you  offer solutions to the problem. Thank you for your reply.

Hi @Jacky.fei,

The error seems to be a NVRAM issue of the controller. Are both of your controllers are inaccessible? 

Is your storage still in warranty contract?

There is a NVRAM procedure that could help and maybe resolve the issue, but it involves removing the controller and opening the enclosure's casing to reset the NVRAM component, usually done by a technician. 

connect to another controller, warning " Sodreboot  ..lockdown.."  " ctrl + b ,   "  did not take in effect. use "CTRL + SHIFT + 6 + X", maybe in a kind of  endless loop.   Have any other guide files?

Hello,

as Joey said to resolve the issue we can try the NVRAM procedure but no other procedure available for the customers.

Thanks

Marco

Dear Marco:

  Thank you for your help. Anyway, I will try to reset the NVRAM , However, I see that my second controller in lockdown mode, So, please can you help with defualt username and password to try lemClearLockdown command via serial interface?  You can send the password to my email< Private Email id removed.TOS73>tks.