Chassis /FEX Discovery policy - Error

[JDMils]

I have noticed the following error in my UCSM environment:

Chassis discovery policy conflict: Link IOM 3/1/1 to peer port A:N/A/1/76 not configured

IOM 3/1/1 is the following:

Type: FEX
Name: FEX3
Model: Cisco Nexus 2232PP

Fabric Ports:

1/1, sys/fex-3/slot-1/fabric-pc/pc-1027/ep-slot-1-port-1, sys/switch-A/slot-1/switch-ether/port-76, Ack=Un-Acknowledged
1/2, sys/fex-3/slot-1/fabric-pc/pc-1027/ep-slot-1-port-2, sys/switch-A/slot-1/switch-ether/port-77, Ack=OK
1/3, sys/fex-3/slot-1/fabric-pc/pc-1027/ep-slot-1-port-3, sys/switch-A/slot-1/switch-ether/port-78, Ack=OK
1/4, sys/fex-3/slot-1/fabric-pc/pc-1027/ep-slot-1-port-4, sys/switch-A/slot-1/switch-ether/port-79, Ack=OK

So 3 of the fabric ports from the FEX to the FI-A are OK, the other does not seem to be and thus the logged fault.

This is Fabric A. I have another FEX which has 4 fabric ports connected to FI-B and they are all connected OK.

FIs are: Model: Cisco UCS 64108

Is this simply a case of clicking "Acknowledge Fex" on the FEX unit and if so, will this cause any type of outage?

[RedNectar · Accepted solution]

Hi @JDMils ,

Definitely the first step is to re-acknowledge the FEX.  But when you do, the existing traffic will be re-balanced across all four links, so there may be a second or two interruption to existing flows.

[JDMils]

Thanks- that fixed it. I just was not sure how a re-ack would affect the server's operation.

[RedNectar]

HI @JDMils ,

Has this problem been solved or do you need more help?

If your question has been answered, it is a great idea to mark the question as being answered.  This helps:

1. others with a similar problem find the correct answer
2. people who look for "unanswered" questions to answer finding this
3. prevent your question from becoming a "dead thread"

[JDMils]

Re-acknowledging the FEX has fixed the issue, thank you.