This is an old post, but I would like to share some information that might help someone. I had the same problem.

The CMC (Chassis Management Controller) was set to "Fault Tolerant" power mode. This mode blocked a lot of power (1139 W) as a backup reserve. As a result, the server in slot 1 only had 31 W left to turn on. The CMC got confused and reported a false error: "A hardware incompatibility is detected between Server in slot 1 and PSU.

I changed the power policy from "Fault Tolerant" to "Redundancy Alerting Only". This stopped the CMC from reserving so much power. Suddenly, 1136 W became available. The server powered on normally, and the error message disappeared completely.

No hardware was broken. It was just a misleading power policy setting.

Hi,

Could you check the FX2s's CMC firmware and FC630's iDRAC is up to date? You may get error on the if the both firmware are mismatched. Let's get everything on the firmware up to date, and see if it resolves the issue.

Let me know if you have any questions.

Good morning Subnet,

Does the CMC's log have any errors displayed in it, to your knowledge? You should be able to find that from the web UI.

I took a look at the part numbers you provided, there doesn't look to be an issue there to me, either. With the reporting saying the issue is between the chassis and the node in slot 4, I'd say the next step would be to acquire logs. If you're able to get into the iDRAC of the FC630 and export a SupportAssist collection, it may be enlightening. However, I'd expect the more actionable information to come from the chassis logs. To acquire those, you'll want to SSH into the CMC and run the following two commands 'racdump' and then 'dumplogs.' 

If you're on a Windows workstation, I generally recommend using PuTTY and using it's native option to save output to a text file. This should provide us with a better idea of what the problem is from the chassis' perspective and from the node's perspective.

They are all up to date. CMC is at 2.30 and all iDRACs are at 2.75.75.75 (17).

Here are the requested logs zipped up: https://www.dropbox.com/s/ouzku89qcwvypkh/FX2Logs.zip?dl=0

I should also note that the 1100W power supplies are not currently installed - I didn't want to chance erratic behavior. I do have a second 'cold standby' chassis I could put them in and pull the same logs from if that would be of more help.

Unfortunately, there's not much I can do with these two logs, though I did look at them. I can see that there was an issue previously, but can't provide any constructive recommendations. What I'd need to see is a log that had the questionable power supplies interacting with the node, so that we have the best opportunity of recording the root issue.

Ok, I installed the 1100W power supplies in my second chassis and moved an idle compute module over to it and got the same results. Here are the results from that chassis: https://www.dropbox.com/s/g81aatjy5tnma0h/FX2sLogs2.zip?dl=0

Also, here's a SupportAssist bundle from the FC630: https://www.dropbox.com/s/yje5vr00d9yifyq/TSR20200814114912_43M.zip?dl=0

Both PSUs are showing up correctly in both the server and chassis logs. However, I did see this entry:

Are you changing the PSUs out with the chassis live? If so, what I'd recommend (when time permits) is to shut the chassis down, unplug it from power, hold the power button down for 10-30 seconds, then power it back up. I'm not seeing any other issues, so I think there's a fair chance this will clear it up.

No, this was from a cold chassis. Installed the power supplies, connected them to power, powered on the chassis, then powered on the FC630.

I also just tried starting it up with just the NTCWP power supply installed and got the same mismatch error, so it would seem it's not a mismatch between the two power supplies.