Request help from the person who have fc60

[Printaporn_1]

what is your NVSRAM checksum value from amdsp -c output ?
for me it is not equal for controller A and B,
like this:
cthsfr01:#amdsp -c fc1 | more
Information for Controller A - 000800A0B8091C40:
Controller Status = GOOD
Controller Mode = ACTIVE
Vendor ID = HP
Product ID = A5277A
Serial Number = 1T02910198
Firmware Revision = 04000304
Boot Revision = 04000200
HP Revision = HP08
Loop ID = 5
AL_PA = 0xE0
Preferred AL_PA = 0xE0
Controller Date = 10/25/2001
Controller Time = 10:48:36
Cache Battery Age = 450 to 539 days
NVSRAM Checksum = 0xA14486DA

Information for Controller B - 000800A0B8091C40:
Controller Status = GOOD
Controller Mode = ACTIVE
Vendor ID = HP
Product ID = A5277A
Serial Number = 1T02810802
Firmware Revision = 04000304
Boot Revision = 04000200
HP Revision = HP08
Loop ID = 4
AL_PA = 0xE1
Preferred AL_PA = 0xE1
Controller Date = 10/25/2001
Controller Time = 10:57:20
Cache Battery Age = 360 to 449 days
NVSRAM Checksum = 0xA13D86DA

but FC60 operate as normal , I want to know this is normal or not ?
thanks in advance,

[Bill McNAMARA_1]

No it's not common.. and is a known issue

FC60 Incorrect NVSRAM Checksum Values Cause Erroneous Critical Events

We have seen some very strange problems with the amdsp outputs reporting FRU???s in CRITICAL states when
they are perfectly healthy as well as other strange behaviour. We have noticed that some of these can be caused
by a mismatch of the NVSRAM checksums as seen by the two controllers. Here???s an example:

Information for Controller A - 000600A0B8067FEE:
Controller Status = GOOD
Controller Mode = ACTIVE
Vendor ID = HP
Product ID = A5277A
Serial Number = 1T00910466
Firmware Revision = 03010303
Boot Revision = 03010302
HP Revision = HP03
Loop ID = 20
AL_PA = 0xC9
Preferred AL_PA = 0xC9
Controller Date = 02/23/2001
Controller Time = 00:54:43
Cache Battery Age = 270 to 359 days
NVSRAM Checksum = 0x343C86DF <- Value should match for BOTH Controllers AND
should be one of the expected values below depending in the Controller firmware installed.

Here are the expected values for the current versions of NVSRAM seen in the field today:

HP01 - 0x353181DF
HP03 - 0x343C86DF
HP08 - 0xA14486DA
HP09 - 0xE14655DA

If they do not match the above then you will need to download the correct
NVSRAM file using the normal documented procedures to correct the problem.

Bill

[Bill McNAMARA_1]

Here are the expected values for the current versions of NVSRAM seen in the field today:
HP01 - 0x353181DF
HP03 - 0x343C86DF
HP08 - 0xA14486DA
HP09 - 0xE14655DA

[Printaporn_1]

thanks for answer Bill, but
- how can I get the document to download NVSRAM file ?
- Do I need downtime ?

[Insu Kim]

Based on your posting, I noticed an important thing as follows.
HP Revision = HP08
(The controller firmware revision in FC60 is HP08)


HP has been implementing a program "proactive field update" to prevent possible disasters for every single FC60 worldwide.

In this program,
HP recommends that firmware revision of FC60 be HP03.
If it's HP08, firmware downgrade to HP03 is neccessary and if it's HP01, upgrade to HP03 by HP people and its qualified partners.
( Now, we have a new released HP10 firemware but looks like that HP03 is still more stable. )

Because it looks like that you're thinking about doing something about firmware mismatch,
I recommend that you place a call to HP to apply this nice program to your FC60 to get a more stable FC60.

One more thing is, unfortunatly,
it always requires downtime indicating that all the volume groups associated with FC60 should be deactivated, unmounted when we do something for firmware like firmware update.

Hope this helps,