Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

P2000: Partner Firmware update failed.

Sergei Zobov
Occasional Contributor

P2000: Partner Firmware update failed.

In one of our storages p2000MSA, controller A (p2000 FC Rev. D firmware TS230P006) produced error SuperCapasitor End-Of-Life. We ordered the new controller. In 3 months we received the new controller (p2000 FC Rev. K firmware TS201R015). The controller has been inserted, all ports are connected. Option PFU has been enabled. Update process firmware on the new controller (A) began.

In 1 hour the new controller passed in state Operational (It was updated Storage Controller, all LUNs became visible to hosts), Management Port answered on ping, but the console (SMU, TELNET) was not accessible.

telnet-> controllerB> version detail

Controller A Versions
---------------------
Storage Controller CPU Type: INTEL TOLAPAI 1200MHz
Bundle Version: TS230P006
Build Date: Fri Aug 12 3:49:29 PM MDT 2011
Storage Controller Code Version: T230P03
Storage Controller Code Baselevel: T230P03
Memory Controller FPGA Code Version: F400R02
Storage Controller Loader Code Version: 23.008
CAPI Version: 3.15
Management Controller Code Version:
Management Controller Loader Code Version:
Expander Controller Code Version: 1130
CPLD Code Version: 22
Hardware Version: 53
Host Interface Module Version: 51
Host Interface Module Model: 15
Backplane Type: 7
Host Interface Hardware (Chip) Version: 2
Disk Interface Hardware (Chip) Version: 3


ftp-> controllerB\bundle\pfu.log

Fri Jan 20 15:01:40 UTC 2012: PFU Started
Fri Jan 20 15:01:40 UTC 2012: Local Version: L230R025
Fri Jan 20 15:01:40 UTC 2012: Local Bundle Version: TS230P006
Fri Jan 20 15:01:42 UTC 2012: Remote Version: L201R021
Fri Jan 20 15:01:42 UTC 2012: Remote Bundle Version: TS201R015
Fri Jan 20 15:01:45 UTC 2012: Local CPLD Version: 22, Remote CPLD Version: 13
Fri Jan 20 15:01:45 UTC 2012: Version L230R025 is greater than version L201R021
Fri Jan 20 15:01:48 UTC 2012: Starting bundle build and file transfer to update other MC
Fri Jan 20 15:04:03 UTC 2012: Full MC bundle file built
Fri Jan 20 15:04:03 UTC 2012: Bundle file starting sending to other MC
Fri Jan 20 15:27:10 UTC 2012: Bundle file sent to other controller
Fri Jan 20 15:27:41 UTC 2012: PFU successful
Fri Jan 20 15:28:39 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:29:39 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:30:39 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:31:39 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:32:39 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:33:39 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:34:39 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:35:39 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:36:39 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:37:42 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:38:40 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:39:39 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:40:39 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:41:39 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:42:39 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:43:39 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:44:52 UTC 2012: PFU can not proceed because the other controller does not appear to be responding to communication attempts.
Fri Jan 20 15:45:15 UTC 2012: PFU Started
Fri Jan 20 15:45:15 UTC 2012: Local Version: L230R025
Fri Jan 20 15:45:15 UTC 2012: Local Bundle Version: TS230P006
Fri Jan 20 15:45:17 UTC 2012: Remote Version: L230R025
Fri Jan 20 15:45:17 UTC 2012: Remote Bundle Version: TS230P006
Fri Jan 20 15:45:20 UTC 2012: Local CPLD Version: 22, Remote CPLD Version: 22
Fri Jan 20 15:45:20 UTC 2012: Other MC is the same version of software; not updating via PFU.
Fri Jan 20 15:45:20 UTC 2012: Other MC bundle verison is at the same version of software; not updating via PFU.
Fri Jan 20 15:46:15 UTC 2012: PFU Started
Fri Jan 20 15:46:15 UTC 2012: Local Version: L230R025
Fri Jan 20 15:46:15 UTC 2012: Local Bundle Version: TS230P006
Fri Jan 20 15:46:17 UTC 2012: Remote Version: L230R025
Fri Jan 20 15:46:17 UTC 2012: Remote Bundle Version: TS230P006
Fri Jan 20 15:46:20 UTC 2012: Local CPLD Version: 22, Remote CPLD Version: 22
Fri Jan 20 15:46:20 UTC 2012: Other MC is the same version of software; not updating via PFU.
Fri Jan 20 15:46:20 UTC 2012: Other MC bundle verison is at the same version of software; not updating via PFU.
Fri Jan 20 15:47:53 UTC 2012: PFU can not proceed because the other MC is not up
Fri Jan 20 15:48:37 UTC 2012: PFU can not proceed because the other MC is not up
Fri Jan 20 15:49:37 UTC 2012: PFU can not proceed because the other MC is not up
.....
Fri Jan 20 16:17:25 UTC 2012: PFU can not proceed because the other MC is not up

 

Whether there is a method separately to update Managememt Controller? Or it is necessary to return the controller to the supplier?

2 REPLIES
Torsten.
Acclaimed Contributor

Re: P2000: Partner Firmware update failed.

The logh says both versions are the same.

Double check the versions.

# show versions

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
hvhari
HPE Pro

Re: P2000: Partner Firmware update failed.

It seems firmware upgrade is completed and again started.

 

 

Below two articles can help in this.

HP P2000/MSA2000 SAN Array Systems - Unable to Access Management Controller: MC and SC Unable to Communicate:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c03153230

HP Storageworks MSA2000/P2000 G1/G2/G3 - MSA Management Controller Hang During FW Upgrade:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c03137800

Regards,
Hari

If this post was useful , click the Kudos Star on the left side to say Thanks!