I've followed the instructions in Integrating Cisco UCS with vSphere Distributed Power Management on one of the hosts in my new UCS cluster but I cannot get vCenter to update the IPMI info without throwing a:
Connection Error:The request failed because the remote server 'vcenter' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
Call "HostSystem.UpdateIpmi" for object "vmhost8.rx.umaryland.edu" on vCenter Server "vCenter.rx.umaryland.edu" failed.
I've check the account/pwd vmware/cisco123 are pretty easy to type so I'm reasonably comfortable I haven't repeated a typo.
sudo nmap -sU -p 623 134.192.XX.XX
[sudo] password for xxxxxx:
Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2012-10-03 11:34 PDT
Interesting ports on 134.192.XX.XX:
PORT STATE SERVICE
623/udp open|filtered unknown
ipmitool -H 134.192.XX.XX -U vmware -P cisco123 sel
Error: Unable to establish LAN session
Get SEL Info command failed
I'm kind of at a lost as to what to try next. I'd love to get DPM setup but seem to have run into a wall here.
Any suggestions or guidance would be greatly appreciated.
Solved! Go to Solution.
I assumed you created an IPMI user and policy and applied to the service profile?
Have you assigned a Management IP to the Service profile (not the static blade IP either)?
Have you enabled IPMI in vCenter for the host and assigned the same username & password?
The IPMI address you should be targeting is the management IP (assigned to the CIMC) correct not the host IP?
As it turns out, I was getting intermittent, seemingly spurious, fan alerts related to an I2C bus defect. To resolve this I was asked to reseat all the fans, PSUs and IOMs in my chassis. I ended up reseating my blades too and that reapplied the service profile. Lo and behold I was able to add the IPMI info successfully without a hitch and I'm happily sending hosts into Standby Mode without a problem.
Thanks for the help.