HP Virtual Connect 4Gb FC Module 409513-B22 unable to assign IP

[David Bonham_1]

We have several: HP Virtual Connect 4Gb FC Module 409513-B22  none of which will obtain an IP address.  "Management IP Address" shows "unknown"  and shows 0.0.0.0 under current IP in EBIPA

This is in c7000 412152-B21 enclosure.  OA is at latest firmware: 4.97

no amount of resetting, re-seating, factory defaulting, makes any difference.

I'm seeing the following in a show all output regardless of which of the 3 FC modules I plug:

Jan 5 11:38:21 OA: @@@ ISMIC bad checksum: icbay=7 block=27 cs=5Eh
Jan 5 11:38:22 OA: @@@ ISMIC bad checksum: icbay=7 block=27 cs=5Eh
Jan 5 11:38:23 OA: @@@ ISMIC bad checksum: icbay=7 block=27 cs=5Eh
Jan 5 11:38:24 OA: @@@ ISMIC bad checksum: icbay=7 block=27 cs=5Eh
Jan 5 11:40:00 OA: i2c (48, 3a) read error: 1 7 0

do I have an incompatibilty?

Thanks and Merry New Year!

[support_s]

System recommended content:

1. HPE Virtual Connect SE 16Gb FC Module for HPE Synergy Release Notes

If the above information is helpful, then please click on "Thumbs Up/Kudo" icon.

Thank you for being a HPE community member.

[Torsten.]

What is the status in VCM?

@support_syour link is not related at all.

[David Bonham_1]

VCM:

Overall status: degraded
VC status: degraded

Bay3 (HP Virtual Connect 4Gb FC Module)   status: No communication

Module enc0:iobay3 unable to communicate with enclosure enc0

Enclosure enc0 contains abnormal FC modules

Thanks!

[David Bonham_1]

we put one of the FC modules into a c3000 enclosure and had the same result:  no IP assigned, 0.0.0.0 and get "no communication" in VCM.

hard to believe 3 FC modules like these just stop working, but there's plenty of posts on the forum to show that its been happening to many; usually after a power down of the enclosure

this is concerning:  the OA "show all" showing this OA: @@@ ISMIC bad checksum: icbay=7 block=27 cs=5Eh  
under the section:
(For troubleshooting purposes of the HPE support teams)
>DEBUG LOG OA 2

I don't think you can upgrade the firmware of the module unless it has an IP assigned, is that right?  or is there a way to force it somehow?  there's no reset button on these 4Gb FC modules that I can see, so options are limited/non existent.

we'll be trying some 8GB FC modules, I'm hoping those don't have a similiar issue.

[Mark-S · Accepted solution]

David,

This sounds like DRAM failure at boot of some sort if they were operational (already booted) and then reset or remove/insert and stopped working. Agree, the symptom would be no IP address, since module is not booting due to mem issue. - I have not seen that problem ever against 8Gb FC modules. 8/20 or the 8/24.

Correct without IP, VCSU no update to the module. But again if this is a DRAM issue with booting, a firmware flash would not recover it.

Moving it to another chassis ruled out the OA and other issues that could be contributing to no IP address.
I think you are correct, these modules are in a failed state, cannot recover.