SAS controller-p700m mismatch

[chuckk281]

Meg had a customer problem when using the SAS controller:

*************************************

I have a customer getting this issue…c7000 with bl460 g6’s

Basically, when I put the SAS controller in Mezzanine 1 (which matches up with the SAS switches in interconnect slots 3 and 4) the server will not power on. I get a partner mismatch error.  In order to boot the server, I have to remove the SAS controller.

I suspect a fw mismatch with maybe the OA?  I have been searching for the FW compatibility matrix on our website, but for some reason can’t find it.  I know it’s out there. 

Any other reason besides a fw issue that  I might be seeing this issue

******************************

Monty joined in:

*****************************

Do you have an OA show all for this enclosure?

Partner blades are also known as sidecar blades and include the SB40c storage blade, tape blade and PCI Expansion blade.

The OA does not prevent a server power on – due to partner errors. The OA will prevent a partner blade power on if there is no adjacent server installed.

Firmware version checks are not involved in the OA logic determine whether or not to grant the server (actually iLO) power on request.

************************

But it seems that Hoa had the answer:

*******************

The MDS600 and SAS Switch put power delay on that Blade until the MDS600 is ON and Ready before it allows the Blade to power on.

*******************************

Other comments? Are you using the M700 SAS switch successfully?