Virtual connect Manager showing critical errors. Any advice...

[Raghuarch]

Try updating your OA firmware:

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=329290&prodSeriesId=3188465&swItem=MTX-945bcf9f337b476390b3effdc3&prodNameId=3188475&swEnvOID=1005&swLang=13&taskId=135&mode=4&idx=0

After OA upgrade, update your VC to the latest:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=329290&prodSeriesId=3201263&swItem=MTX-476f7fc031f24133b51b45579d&prodNameId=3201264&swEnvOID=1005&swLang=8&taskId=135&mode=4&idx=1

it should resolve the issue.

[Terri Harris]

Just to summarize what revisions VC & the related components should be, see this HP web page:

http://h18004.www1.hp.com/products/blades/components/c-class-compmatrix.html#1

It has not yet been updated for OA 2.31. But minimum revs need to be:
VC 1.32: Don't update to 2.00 unless you have the new HP FlexAttach-10 Ethernet module installed.
OA 2.25: or the current 2.31
iLO2 1.61 or higher

[The Brit]

Terri
Thanks for the (too late) warning. I have already upgraded my VC's to 2.00.

1. Have I created a problem for my self?
2. Should I downgrade back to 1.32?

Dave.

PS. I dont recall any warning at the "download" site/page.

[The Brit]

Terri,
Also noted that there is a new FW release, 2.01. Should I move to that version?

Dave.

[cjb_1]

Predictably, we had the same problem on one of our enclosures this morning.

Things at the server end were fine and problem was solved in our case by bouncing the problematic vcfc module and upgrading to fw 1.32.

We have v2 on another enclosure. Notice the release been erased from the revision history. Fix in 2.01 seems worth upgrading to.

"Fixed an issue where Virtual Connect defined FC WWNs were not being written to the server HBA after upgrading firmware to Virtual Connect 2.00."

[Terri Harris]

If you have Virtual Connect 2.00 and do not have the HP FlexAttach-10 module installed (1)if you are having any issues with VCM (Virtual Connect Manager) itself or (2) the FC HBA (Qlogic or Emulex) BIOS is not reporting the virtual pWWN addresses as it should, then upgrade to 2.01:

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=329290&prodSeriesId=3201263&swItem=MTX-476f7fc031f24133b51b45579d&prodNameId=3201264&swEnvOID=1005&swLang=8&taskId=135&mode=4&idx=3

Otherwise it is ok to be at VC 2.00 and not have the HP FlexAttach (Ethernet) module installed.

[Ewen Willox]

Thanks guys, a F/W update of the OA and all the FC modules has cleared the problem. Everything is talking again and looking good.

I notice that others have asked questions in this topic so I don't want to just close it down incase there are further Q/A related.

I will close it in a while unless someone tells me other wise.

Thanks for all the help folks.

[Ewen Willox]

A F/W update of the OA and all the FC modules has cleared the problem. Everything is talking again and looking good.