FI-A backplane port admin down and blade vNIC link state in error and FI-B is ok?

[fly]

we found iom-1 on all six chassis on fi-a side backplane port  in admin down state

and connect to FI-B is ok

we tried to reset iom-1 on one chassis and reload FI-A ,but no use

is there any idea?

I found some log and state infor

1) FSM:<Ethernet1/1/7> Transition at 435013 usecs after Thu Apr 16 08:53:10 2020
Previous state: [ETH_PORT_FSM_ST_NOT_INIT]
Triggered event: [ETH_PORT_FSM_EV_MODULE_INIT_DONE]
Next state: [ETH_PORT_FSM_ST_INIT_EVAL]

2) FSM:<Ethernet1/1/7> Transition at 435066 usecs after Thu Apr 16 08:53:10 2020
Previous state: [ETH_PORT_FSM_ST_INIT_EVAL]
Triggered event: [ETH_PORT_FSM_EV_IE_ADMIN_DOWN]
Next state: [ETH_PORT_FSM_ST_DOWN]

show service-profile circuit server 1/3
Service Profile: B1
Server: 1/3
Fabric ID: A
Path ID: 3
VIF vNIC Link State Oper State Prot State Prot Role Admin Pi
n Oper Pin Transport
---------- --------------- ----------- ---------- ------------- ----------- --------
-- ---------- ---------
723 vHBA-A Error Error No Protection Unprotected 0/0
1/27 Fc
8915 Error Error No Protection Unprotected 0/0
0/0 Ether
985 vNIC-A-1 Error Error No Protection Unprotected 0/0
0/0 Ether
986 vNIC-A-2 Error Error No Protection Unprotected 0/0
0/0 Ether
987 vNIC-A-3 Error Error No Protection Unprotected 0/0
0/0 Ether
Fabric ID: B
Path ID: 3
VIF vNIC Link State Oper State Prot State Prot Role Admin Pi
n Oper Pin Transport
---------- --------------- ----------- ---------- ------------- ----------- --------
-- ---------- ---------
724 vHBA-B Up Active No Protection Unprotected 0/0
1/32 Fc
8916 Up Active No Protection Unprotected 0/0
0/0 Ether
988 vNIC-B-1 Up Active No Protection Unprotected 0/0
0/2 Ether
989 vNIC-B-2 Up Active No Protection Unprotected 0/0
0/2 Ether
990 vNIC-B-3 Up Active No Protection Unprotected 0/0
0/2 Ether

(nxos)# show interface eth 1/1/7
Ethernet1/1/7 is down (Administratively down)

(nxos)# show interface eth 1/1/8
Ethernet1/1/7 is down (Administratively down)

[fly]

Hi, 

   I find FI-A reload him self due to snmpd hap reset

  and blader server  vNIC connect to FI-B (connected to FI-A before)

   but now FI-A is come back online, why  blader server vnic reconnect back to  FI-A?

   the FI-A is reload him self on Apr 16 08:50:23 2020 but IOM-1 backplane port admin down happened at  08:53:10 2020

//like below

  FI-A
`show system uptime`
System start time: Thu Apr 16 08:50:23 2020
System uptime: 0 days, 23 hours, 53 minutes, 16 seconds
Kernel uptime: 0 days, 23 hours, 57 minutes, 7 seconds
Active supervisor uptime: 0 days, 23 hours, 53 minutes, 16 seconds

Last reset at 681500 usecs after Thu Apr 16 08:45:15 2020

Reason: Reset triggered due to HA policy of Reset
System version: 5.2(3)N2(2.22c)
Service: snmpd hap reset

ON FI-B  I found FI-B lose HA CLuster interconnect  TO FI-A  8 hours after FI-A reload himself 

2020 Apr 16 16:32:41  FI-B %UCSM-2-LINK_DOWN: [F0294][critical][link-down][sys/mgmt-entity-B] Fabric Interconnect B, HA Cluster interconnect total link failure

now FI-A is online  ,and HA status with FI-B is ok ,but why 6 chassis iom-1 connect FI-A still backplane admin down?

thank you

Tom