Solved: Re: 6248 FI - Inoperable - Ports are still up

dowjones · ‎03-03-2025

We have legacy envoiroment that is no longer under support as this is EOL equipment so I'm unable to utilize TAC. I have a FI that faulted over the weekend. Funny enough all ports FC\ETH are still green and traffic appears to still be flowing as none of my ESX hosts are showing paths down. The HA status shows Ready - No, State - Down. Leadership - Inapplicable

This is the fault seen on the FI - Fabric Interconnect A operability: inoperable

[FSM:FAILED]: Ethernet traffic flow monitoring configuration on A(FSM:sam:dme:SwEthLanFlowMonDeploy). Remote-Invocation-Error: FSM Retries Exhausted

When I show pmon state all services are running. I do not see any physcial hardware issues, PSU are both up, connectivity to IO modules on all 3 chassis are green. The UCSM version on this FI is 4.0(4c). No recent changes have been made as this FI has been up for a few years now.

I can connect to the CLI of the FI. Im wondering if might be just a case that a reboot is needed but since I have no support Im trying to be a bit more cautious.

Any other ideas?

Wes Austin · ‎03-06-2025

Sounds like something from the management services side is not working properly on FI-A. Reboot is probably your only option to recover, but if there are any other underlying issues on FI-A (filesystem corruption, boot path not set correctly, etc) then it may not boot back up properly. You would probably have to determine if its worth rebooting if everything is up and running. If you have a spare 6200, it may be worth preparing it with the same firmware in case you need to swap it out.

View solution in original post

dowjones · ‎03-05-2025

Something that may be related is when I try to scope FI-A (broken) or FI-B I receive the same error on both FI

Software Error: Exception during execution: [Error: Timed out communicating with DME]

Wes Austin · ‎03-06-2025

Sounds like something from the management services side is not working properly on FI-A. Reboot is probably your only option to recover, but if there are any other underlying issues on FI-A (filesystem corruption, boot path not set correctly, etc) then it may not boot back up properly. You would probably have to determine if its worth rebooting if everything is up and running. If you have a spare 6200, it may be worth preparing it with the same firmware in case you need to swap it out.

dowjones · ‎03-06-2025

Thank you for replying. Yep I think that is what the decission is just leave it be for now. This environment was supposed to be shut down a few years ago but here we are lol. We have had boot flash corruption on this FI before which is why im hesitant on the reboot.