Virtual Connect FC issue

[Balde]

As i told you before, i already moved that module to another bay, also to another enclousure, i know that 1 bad module isn't lucky, but 3 bad modules... something is going wrong.... the 3 bad modules broke on different enclousures, we already check for high temp, energy stuff, changed modules to different bays, downgrade firmware of VC, checked EBIPA IP assign, power off and on the entire enclousure, reset everything that have a reset.... the logs says:
VCETW280200PL vcmd: [FC:enc0:iobay3:4019:Major] FC Module state NO_COMM : Cannot communicate with component
VCETW280200PL vcmd: [FC:enc0:iobay3:4004:Info] FC Module power on
VCETW280200PL vcmd: [FC:enc0:iobay3:4011:Warning] FC Module state UNKNOWN : Component operational state cannot be determined

[The Brit]

Maybe I'm missing something here, but it seems to me that what you are saying is that

1. You have ONE failed VC FC module (In Bay 3).
2. Your other VC FC modules are functioning correctly
3. You have tried the same "bad" module in different bays, and different enclosures, and in each case, the module failed.

So the only question I have is

Have you tried a "Good" VC FC module in BAY 3, and if so, what was the result????

[Balde]

Yes, also in diferent bays on different enclousures

[The Brit]

So you tried a "Good" module in Bay 3 and it worked fine ??

Do you have any reason to think that the original module from Bay 3, i.e. the "Bad" module, is really "GOOD" ???

I have re-read this thread several times and it seems to me that this module has not worked, (in any enclosure bay), since the power was taken off the enclosure. Correct me if I am wrong!!

So why don't you replace it ???

Dave.

[norbert rudholzer]

Hello,

we have exactly the same Problem on 2  C3000 Enclosures.
The 4Gb VC Modul ( Part Number 409513-B22)
worked already ~4 Years (FW 2.00 VirtualConnect 4.10)

We had to remove one Modul from Bay 4.
After reinserting it into the same slot, we get "No Communication" an no management IP Adress.

EPIBA settings are OK

On another C3000 Enclosure with a functioning Module, there was the same.

We removed a working Module and reinserted it

And now we have 2 Modules not working in Slot 4

Any suggestions?

[jdixon]

We are having this exact same problem? Any updates from anyone? I know it has been a long time snice this was posted.

[peyrache]

What are OA/VC firmware versions ?
Shall you post OA logs please ?
OA is very sensitive to broadcast storm
Did you connect OA network on separate Lan (isolated )
JY

[WilliamSmith11]

Exactly the same issue

But in may case it happen when we try to restore a backup configuration.

We have two C7000,

We moved the two VC-FC to a different enclosure and dont work.

We downgrade de OA firmware  version and dont work,

Some suggestion ?

[Torsten.]

You have VC FC modules only. This cannot work. You need VC ethernet modules to manage them.

[WilliamSmith11]

In th attachment all module are inserted, same result