IPMI | VMM bare metal builds

A couple of tips when investigating VMM bare-metal IPMI issues
The VMM jobs will report the following if the connection failed:

Error 21212: Connecting to the BMC with address x.x.x.x failed.

This error indicates a problem with network connectivity, likely a firewall or routing issue (most IPMI communications go over port 623 UDP)

Error 21220: An out of band operation (IPMI) for the BMC x.x.x.x failed IPMI completion code 0x9 – Invalid Role.

This error indicates a problem with authentication. Check the VMM Run-As account, the username must have exactly the same case as the IPMI username. Also check the permissions required are sufficient (Full Admin Permissions are usually required)

SCVMM 2012 Bare-Metal Failing on HP G7 Blade (IPMI Failure)

Found an issue with a blade yesterday where SCVMM 2012 was failing to power on the blade. The communication was occurring over IPMI. This was the first G7 that I had been testing bare-metal deployments on (having previously worked with Gen 8 Blades).

The iLO event logs would reveal the following entries:

IPMI/RMCP login by scvmm – x.x.x.x(DNS name not found)

IPMI/RMCP logout by scvmm – x.x.x.x(DNS name not found)

 

Whats more, after this occurred the ilo remote console would become unresponsive, requireing the blade to be reseated, or a reset of iLO.

 

Interestingly there was an option on the iLO Dedicated Network Port  that specified that iLO client applications (does this include IPMI?) should use IPv6 first

 

The fix for me was to disable IPv6 on the iLO dedicated network port, then SCVMM could communicate with the blade via IPMI.