The immpassthru provider runs on ESXi and mirrors all the CIM functionality available in the IBM IMM. CIM requests to ESXi get the same response as requests directly to the IBM IMM.
The filetrans provider is used to transfer files to the ESXi host in preparation to fulfill a future requirement.
The fwupdate provider is used to update all IBM firmware supported by the IBM IMM. Currently, the IMM supports updating the IMM, pre-boot DSA, UEFI, and FPGA.
The concretejob provider is an assistant provider. It is used by consumer providers (such as Filetrans, Fwupdate, or other providers) to support asynchronous operations. In addition, it provides a logging mechanism for all of the providers.
Disclaimer: The partner product referenced in this article is a software module that is developed and supported by a partner. Use of this product is also governed by the end user license agreement of the partner. You must obtain the application, support, and licensing for using this product from the partner. See http://www.ibm.com/.
All four providers must be installed together to work correctly. Installation can be done in one of two ways:
With the IBM providers, IBM ToolsCenter and IBM Systems Director can manage a system with ESXi 5.0.
Details for IBM ToolsCenter and IBM Systems Director can be found at http://www.ibm.com.
Details for the VMware vSphere 5.0 with IBM Customization Image can be found at http://www-03.ibm.com/systems/x/os/vmware/esxi/.
None.
immpassthru provider schema is mapped from IBM IMM and follows DMTF standard DSP1023.
Filetrans provider does not follow any DMTF or SMI-S specification. Instead, it follows a private OEM profile.
Fwupdate provider follows DMTF standard DSP1025.
Concretejob provider does not follow any DMTF or SMI-S specification. Instead, it follows a private OEM profile.
None.
As noted above, all four providers must be installed together to work correctly. Logging can be enabled to debug the providers with class IBM_RecordLog. The log is saved to the /tmp/IBMIMMLog.log file.