No link between IOM 1/1/3 and FI A 1/3

[lorenzobexer]

Hi,

when we first set up our UCS we connected all four of the IOM Ports to the Fabric Interconnects but now we wanted to remove two of them in order to save some ports on the FI. We unconfigured the server ports #3 and #4 on both FIs and removed the cables afterwards.

However, now we receive the error message F0367 "No link between IOM port 1/2/3 and fabric interconnect B:1/3"  for all of the fabric ports where we removed the cables.

Even setting the discovery policy to 2 links and re-acknowledging the chassis didn't resolve the errors.

Does somebody know how to resolve this issue?

Regards

[Jeremy Waldrop]

sounds like you need to re-acknowledge the chassis

[lorenzobexer]

hi,

as mentioned above: "Even setting the discovery policy to 2 links and re-acknowledging the chassis didn't resolve the errors."

[Jeremy Waldrop]

sorry, I missed that in your original post.

[abbharga · Accepted solution]

Hi Lorenz,

What version of UCS are you currently on?

Also are you seeing any traffic loss on the blades for which these faults are being raised?

I guess you are hitting the following bug : CSCtg74026 (IOM Faults:not clearing after chassis discovery policy change )

This has been fixed in the current relase of 1.4. However the workaround is to do a chassis de-comission and re-discovery.

Hope this helps!

./Abhinav

[lorenzobexer]

We are on version 1.4 (except server BIOS, which was still 1.3). I can't tell if there was any traffic loss, as we are still in an early test phase and there are no servers running on UCS.

However, your advice helped. After de-commissioning and re-discovery the faults cleared.

Thanks.

[Sanjesh Kishore]

Hi,

I am on 1.4.1. Only 1 of 4 IOM link is up and active. All others are in up state but in un-initialsed state. I guess I need to re-acknolowdge the chassis. Is re-acknowledging chassis disruptive? I have some production VMs running in this chassis.

Thanks

[Robert Burns]

Yes you will need to re-ack the chassis this will be a disruptive operation and networking between the chassis and FI are rebuilt.

--

Sent from my Android phone with K-9 Mail. Please excuse my brevity.

[adchaicisco]

Hi,

I faced the same problem and tried recommision the UCS chassis. But the recommision process is hang as the screen shot below. Kindly advise how to solve the problem. Should I shut down the chassis and power up again?

[rammuthaiya]

Hi ,

This is know issue in UCSM 1.4.1 and same was resolved in subsequent releases. Please do try upgrade UCSM.

Regards,

Ram,

[adchaicisco]

Hi Ram,

Fyi, we were having the latest firmware version for all UCS components including UCSM when the above problem happened. Current version is 1.4 2(b). This problem should be solved in version 1.4.2(b), right?

[rammuthaiya]

FYI....current version is 1.4(3i). Please go through the release notes and carry out.