Cannot reach TOC quorum. Use ‘setsysmgr’ to set system manager startup state

[babafemi]

I have a 3PAR P10000 V400 system bought as a HP Demo Unit, Upon powering it up and connecting to the controller node 3, i came across the following error

Cannot reach TOC quorum. Use ‘setsysmgr’ to set system manager startup state

No TOCs found.
32 disks were considered invalid TOC sources due to unread or bad labels."

i tried to look for the Gen number as suggested by some Post but was not displayed. what else can i do.

[Dennis Handly]

What 3PAR OS version do you have?

Have you tried "showsysmgr -d"?

Is there any data on the array you want to keep?

[babafemi]

it 3PAR 3.1.1

there is no data on it at the moment, we are runing it for the first time since we got it Last month.

this ws what i got fromt eh showsysmgr -d

Cannot reach TOC quorum. Use ‘setsysmgr’ to set system manager startup state

[Dennis Handly]

>it 3PAR 3.1.1

You may want to update to the latest 3.1.2 MU.

>there is no data on it at the moment, we are running it for the first time

So you could either use:

setsysmgr [-f] tocgen [<toc_gen_number> [<disk_quorum>]]

I hope if you left off <toc_gen_number>, it would give you a list and you could select the reasonable one, most recent one.

setsysmgr [-f] wipe [<system_ID>] <system_name>

This wipes the whole system of data.  You would need to use the SP to initialize it again.

The <system_ID> and <system_name> are shown with showsys, when sysmgr is working.

[babafemi]

Thank you for your response,

when i ran Setsysmgr -f tocgen, i got the following message

InServ cli% setsysmgr -f tocgen
Error setting system state. Could not read TOC 0.

Should i proceed to try the second option. Do i carry out the wipe first before updating the Software

BTW: I ran

showversion -b -a command and this is what i got

Release version 3.1.2.278

Patches:  P01

Component Name                   Version

CLI Server                       3.1.2.282 (P01)

CLI Client                       3.1.2.282 (P01)

System Manager                   3.1.2.282 (P01)

Kernel                           3.1.2.278

TPD Kernel Code                  3.1.2.278

TPD Kernel Patch                 3.1.2.282 (P01)

CIM Server                       3.1.2.278

WSAPI Server                     3.1.2.278

Console Menu                     3.1.2.278

Event Manager                    3.1.2.278

Internal Test Tools              3.1.2.278

LD Check Tools                   3.1.2.278

Network Controller               3.1.2.278

Node Disk Scrubber               3.1.2.278

PD Scrubber                      3.1.2.278

Per-Node Server                  3.1.2.278

Persistent Repository            3.1.2.278

Powerfail Tools                  3.1.2.278

Preserved Data Tools             3.1.2.278

Process Monitor                  3.1.2.278

Rolling Upgrade Tools            3.1.2.278

Software Updater                 3.1.2.278

TOC Server                       3.1.2.278

VV Check Tools                   3.1.2.278

SNMP Agent                       1.6.0

SSH                              5.5p1-6+squeeze1

Firmware Database                20121109

Drive Firmware                   20121026

BIOS                             4.2.8

UEFI BIOS                        1.2.9

MCU Firmware                     3.73

Cage Firmware (DC1)              4.44

Cage Firmware (DC2)              2.64

Cage Firmware (DC3)              08

Cage Firmware (DC4)              2.64

Cage Firmware (DCS1)             320C.1

Cage Firmware (DCS2)             320C.1

Cage Firmware (DCN1)             320C.1

QLogic QLA4052C HBA Firmware     03.00.01.67

QLogic QLE8242 CNA Firmware      04.11.115

Emulex LP11002 HBA Firmware      02.82.x10

Emulex LPe12004 HBA Firmware     02.01.x14

3PAR FC044X HBA Firmware         200A8

LSI 9201-16e HBA Firmware        11.00.00

LSI 9205-8e HBA Firmware         11.00.00

so i think the OS is 3.1.2. the DVD that came with the system had 3.1.1 on it.

Regards

[Dennis Handly]

>when I ran setsysmgr -f tocgen, I got the following message

The examples of that TOC quorum message say a list of generation numbers is listed after that error.

So that's the number you need for "setsysmgr -f tocgen".

>Do I carry out the wipe first before updating the Software

You have newer software?

[babafemi]

Unfortunately no toc number was displayed and i do not have newer software

After several tries, i decided to check the health of the 3PAR system then i found out that it was unable to detect the B Loop of  6 of my cages, so i started checking the fibre connection (cable and SFP modules) to the NODEs then i saw that the Rx on the B loops were not active.

  I changed all the Cable for the B loops  and all Rx came up. So i ran the checkhealth command again and it was able to talk to all cage and drives.

The next thing i did was to use the option 7 (Set up the system to wipe and rerun ootb)  of the Console menu and that also went well as well, i re-ran the OOTB and then the system manager swung into operation, checking disk, creating admin volume etc.

I got an Alter on the Second 3PAR unit about the Node Batteries ( Says they have not been tested in the last 30days) - is this anything to worry about.? 

We just powered on the Second Unit yesterday since we recieved the units (over 30days).

[Dennis Handly]

>Says they have not been tested in the last 30days) - is this anything to worry about?

I assume it's because the system hasn't been on.  Is the alert still there?

[babafemi]

I will check on the status of the alert tomorrow and revert back to you.

Thank you so much

[babafemi]

The battery Error is no longer there. the system has now been configured. However i woul like to seek your opinion on this.

We will be moving the Seocnd 3PAR unit to a DR site after syncronising all data with the Primary unit. i am thinking we should take out the drive magazines, package properly and separately before shiping the unit. What would you advice.

Regards

[Dennis Handly]

>What would you advise?

Sounds reasonable but I've no experience in that area.