Flex-10 module not in domain/VCM saying No Communication

[Pubstarhero]

Had some power hiccup issues. Had to replace a HP OA module that decided to flip out. I failed over to its secondary that was already in the chassis and put in a new one as a backup. Sometime after that, my Flex-10 Module in Bay 5 of that enclosure started to freak out and say No Communication. All links were still available from the module (as in I was getting no "Redundant Network Link Lost" errors in VMware as this chassis hosts exclusively ESXi hosts), but I had zero management over it.

I attempt the one fix that HP says should work (and that I needed to do anyways) and upgraded firmware. After I did that, all links were lost and the module started reporting as Unintegrated/Not In Sync. I decided to pull another Flex-10 module from Dev and put it into this domain and upgrade its firmware as well, and now I'm getting Unitegrated/Invalid. HP VCM still reporting that the module is No Communication and says the module is off even though I can reboot and control it through HP OA. When I did install the Flex-10 from my Dev environment it did immediately grab the proper IP address from HP OA.

So whats been tried:  Multiple known good link cables, multiple Flex-10 modules, Firmware upgrades.

All my google-fu pulls up is results for "Just upgrade firmware" or manuals that list the domain states but no way to resolve it. See imgur gallery below for what I see.

https://imgur.com/a/rJYkGIy

Edit:  Just wanted to know that this chassis is linked to a different chassis and that one is the primary in the domain, the one Im having issues with is the subordinate chassis.

[AmRa]

Collect VC SHOWALL * report by executing below command on VCM CLI console.

>SHOW ALL *

and share the below output from captured report.

*******************************************************************************
STACKINGLINK INFORMATION
*******************************************************************************

Connection Status : OK
Redundancy Status : OK

Stacking Mode : Full

===========================================
Link Speed Connected From Connected To
===========================================
1 40Gb enc0:1:Q3.1 enc0:3:Q3.1
2 40Gb enc0:1:Q4.1 enc0:3:Q4.1
3 20Gb enc0:1:X10 enc0:2:X10
4 20Gb enc0:1:X9 enc0:2:X9
5 40Gb enc0:2:Q3.1 enc0:4:Q3.1
6 40Gb enc0:2:Q4.1 enc0:4:Q4.1
7 20Gb enc0:3:X10 enc0:4:X10
8 20Gb enc0:3:X9 enc0:4:X9

*******************************************************************************
STATUS INFORMATION
*******************************************************************************
Overall Domain Status : Info : The domain is in a non-error or transitional
state.

Status Cause : -----------------------------------------

Root Cause : -------------------------------------------

Critical : 0
Major : 0
Minor : 0
Warning : 0
Informational : 2
Unknown : 0

=========================================================================

[Pubstarhero]

*******************************************************************************
STACKINGLINK INFORMATION
*******************************************************************************

Connection Status : OK
Redundancy Status : OK

Stacking Mode : Full

===========================================
Link Speed Connected From Connected To
===========================================
1 10Gb enc0:1:X2 enc0:5:X1
2 10Gb enc0:1:X7 enc0:2:X7
3 10Gb enc0:1:X8 enc0:2:X8
4 10Gb enc0:2:X1 enc1:6:X2
5 10Gb enc0:2:X2 enc0:6:X1
6 10Gb enc0:5:X2 enc1:1:X1
7 10Gb enc0:5:X7 enc0:6:X7
8 10Gb enc0:5:X8 enc0:6:X8
9 10Gb enc0:6:X2 enc1:2:X1
10 10Gb enc1:1:X7 enc1:2:X7
11 10Gb enc1:1:X8 enc1:2:X8
12 10Gb enc1:2:X2 enc1:6:X1

*******************************************************************************
STATUS INFORMATION
*******************************************************************************
Overall Domain Status : Critical : The domain is incapable of managing its
contained VC components.

Status Cause : Domain contains abnormal enclosures and profiles

Root Cause : The ESXi_Enc1_B01 profile is assigned to an abnormal server in bay
enc1:devbay1; The ESXi_Enc1_B02 profile is assigned to an abnormal server in
bay enc1:devbay2; The ESXi_Enc1_B03 profile is assigned to an abnormal server
in bay enc1:devbay3; The ESXi_Enc1_B04 profile is assigned to an abnormal
server in bay enc1:devbay4; The ESXi_Enc1_B05 profile is assigned to an
abnormal server in bay enc1:devbay5; The ESXi_Enc1_B06 profile is assigned to
an abnormal server in bay enc1:devbay6; The ESXi_Enc1_B09 profile is assigned
to an abnormal server in bay enc1:devbay9; The ESXi_Enc1_B11 profile is
assigned to an abnormal server in bay enc1:devbay11; The
OFM_Prod_[SERVERNAMEREDACTED]_Enc1 profile is assigned to an abnormal server in bay
enc1:devbay16; The Sabre01NEW_Enc1_B07 profile is assigned to an abnormal
server in bay enc1:devbay7

Critical : 1
Major : 1
Minor : 45
Warning : 20
Informational : 0
Unknown : 25

[AmRa]

Based on VC SHOWALL report output, Overall Domain Status : Critical : The domain is incapable of managing its
contained VC components.

i. Have you checked by reseating OA and OA tray.

ii. Have you check by reset the Virtual Connect Manager application.

To reset the Virtual Connect Manager application running on the primary Virtual Connect Ethernet module, select Reset Virtual Connect Manager from the Tools pull-down menu. The Reset Virtual Connect Manager screen is displayed.

If still issue persists, please raise support ticket with HPE support team for further troubleshooting as we need to perform deep analysis of logs captured from c7000 enclosure.