I looked at the CMDTool2 manual for the RMT3CB080 Raid controller and found the syntax to change the DirectPDMapping setting, default is off. Every time I issue the command to turn it on I get an exit code 0x1. On LSI controllers I have successfully done this in EFI. I tried MegaCLI, StorCLI and CmdTool2 in EFI and DOS, no luck. In the StorCLi utility it replies that the directpdmapping failed for set cmd Error code 3. Has anyone else seen this behavior?
After further investigating here, we confirm that
While the DirectPdMapping command is not available in UEFI when using CmdTool2 (see the "UEFI Command Line" section on page 7 of the Command Line Tool 2 User Guide http://www.intel.com/support/motherboards/server/sb/CS-031604.htm here), the same works when using Storcli; the correct command syntax is storcli /c0 set directpdmapping =on, however:
Thank you for the implied feedback on this document typo, as the same had a missing a space.
Could you please confirm the firmware version for the RAID controller? If needed, make sure it is updated to https://downloadcenter.intel.com/download/24663/ir3-2208-ROC-Hardware-RAID-Firmware-Flash-Update version 23.32.0-0017. If this situation persists, I would recommend contacting our http://www.intel.com/p/en_US/support/contactsupport Intel Customer Support team for proper follow up of your case.
I tried both dos and efi to set the properties of this adapter. I issued the reset factory defaults command in both the RADI gui and the –appfacdefset in dos. Still getting the same message, failed to set data on adapter 0. Tried both utilities cmdtool2 and storcli to issue commands, no success. I have another module to test, but I am guessing it will do the same thing. I will post the results. I have attached a pic of the sticker you were asking about.
A second controller is showing the same behavior issuing the directpdmapping in DOS and EFI. All firmware and server board bios are current. Even separately flashed the BMC when I installed a RMM4 module. I have tried unhooking the backplane, same result. There has to be a reason I am locked out from setting this parameter. Did your research dept have a battery backup attached to the module? I do not.