Our virtualised server environment consists of VMware ESXi hosts on Cisco UCS blades. In order to assess change impact on our services we would like to build CMDB relationships similar to
Datacenter -> Floor -> Rack -> UCS FIC -> UCS chassis -> Blade -> Service Profile -> ESXi host -> VM -> Service
While this is fairly easy in a static environment this becomes much more of a challenge when VMs move between ESXi hosts due to DRS vMotion operations.
How do other companies approach this problem? We are using a BMC Atrium CMDB and ADDM discovery, but the reliability of CMDB information such as the ESXi host -> VM relationship is not sufficient for impact assessments due to the ADDM scan frequency.
February 21, 2013 2:26 PM