Cisco 6332 FI's will not route to core switch - previously worked

[alanraczek11]

We have 2 Cisco 6332 FI's hooked together and also trunked to a Cisco 9732 switch. This setup also includes 3 Cisco C240 servers. This was all working and then we had to tear down the setup and move it to another room for lab renovations. Got everything cabled up and fixed an issue with cabling on the FI's with Cisco TAC help. If I do 'sho cdp neighbor' on the FI's they see the port on the CORE switch (9732). Similarly on the CORE switch it see's the port on the FI's. Problem is I cannot ping from the FI's to the connected switch or from the CORE switch to the FI's. Nothing has changed physically on the machines, they are cabled correctly as far as I know. See port info below. What could be happening? 

!Command: show running-config interface Ethernet1/32

!Time: Tue May  4 12:40:34 2021

version 5.0(3)N2(4.04f)

interface Ethernet1/32

  description U: Uplink

  pinning border

  switchport mode trunk

  switchport trunk allowed vlan 1,12,30-31,34-36,41-43,46,69,80,110,128,325,600,

823-824,830,2400

  udld disable

  no shutdown

!Command: show running-config interface Ethernet1/32

!Time: Tue May  4 12:42:05 2021

version 5.0(3)N2(4.04f)

interface Ethernet1/32

  description U: Uplink

  pinning border

  switchport mode trunk

  switchport trunk allowed vlan 1,12,30-31,34-36,41-43,46,69,80,110,128,325,600,

823-824,830,2400

  udld disable

  no shutdown

Ethernet1/32 is up

Dedicated Interface

  Hardware: 40000 Ethernet, address: b4de.3172.2f17 (bia b4de.3172.2f17)

  Description: U: Uplink

PALADIN-FI-A-A(nxos)# show interface ethernet 1/32

Ethernet1/32 is up

Dedicated Interface

  Hardware: 40000 Ethernet, address: b4de.3172.2d6b (bia b4de.3172.2d6b)

  Description: U: Uplink

[Reza Sharifi]

Does "sh cdp nei" show the correct outgoing and local port from the FI and the core switch?

HTH

[alanraczek11]

Yes, the ports are correct. Show cdp neighbors shows the ports and devices on the other side correctly.

[marce1000]

 - It is indeed very difficult to find valid networking reasons for this. Perhaps some equipment got damaged, perhaps you could ask TAC for a temp spare-FI and do some testing, chances are slim, it's a bit of last gasp intuition.

 M.

[alanraczek11]

I have noted in some other posts somewhere that the management port needs to be connected (I don't know if the info I saw was for the 6332). We currently do not have a connection to the management port on the FI's.

?

[marce1000]

 - Perhaps try ?

 M.