vCenter Plugin - Host and iDRAC on Seperate Networks - Options?

Hi all,

We have 2x R720 virtual hosts, with LOM IPs on the LAN (10.227.0.x) and iDRAC IPs on a physically seperate management network - 10.227.2.x. iDRAC is running in dedicated NIC mode, and is accessible from the management network. The Dell vCenter Management Plugin is up and running, registered with vCenter, and has connection profiles - 1 per server.

When I test the a connection profile, it can talk to the LOM IP, but fails on the iDRAC IP. Firmware and warranty inventory also fail. The iDRAC IPs are not pingable from inside the CentOS base of the plugin.

Running the ProtocolEndpoint.bat script from http://www.dell.com/support/troubleshooting/us/en/19/KCS/KcsArticles/ArticleView?c=us&docid=597574 shows it is correctly resolving the iDRAC IP, but obviously it can't talk to it because the networks aren't linked. So, what are my options here:

• Can I somehow configure iDRAC with both a LAN and a management network IP (presumably switching away from using the dedicated iDRAC NIC)?
• Should I just temporarily change the iDRAC dedicated NIC to be on the LAN, swap the patch leads, do vCenter Plugin things and then switch back?
• Is it possible to set up a network route in the CentOS base for the plugin? Getting root access to that seems to be not possible (admin password doesn't work, and readonly account is just that, and the route command doesn't work either) - this combined with some other network fiddling could work
• Any other options?

I'd prefer if the plugin could talk to the R720 iDRACs 24/7 for ongoing monitoring, but the main purpose for the plugin for us is occasional firmware updates, so temporarily changing the iDRAC dedicated IPs is an option.

Thanks

Lukas