![]() any virtual machine with the utility installed and the right credentials could talk directly to the server’s RAID controller. The ESXi version allowed you to “remotely” monitor the RAID controller status by communicating with the underlying hypervisor via the virtual machine layer ie. ![]() Thankfully this was addressed around the release of ESXi 5.0, with vendors such as Adaptec finally being able to release aacraid drivers for ESXi and specific drivers to allow for a “remote-arcconf” utility (Adaptec Raid Controller Configuration utility). One of the more annoying issues with ESXi up until the last 1-2 years, was the inability to monitor the status of your RAID card without rebooting and checking via the RAID BIOS - which is inconvenient to say the least in today’s highly available world. With Xen & XenServer being so closely linked to RHEL/CentOS, monitoring the status of the underlying RAID controller has never really been an issue. However, our tech gurus are adept with the many flavours on the Hypervisor rainbow and for various non-critical or non-production systems we do make use of other HV’s, including VMware ESXi nodes. Generally at Crucial we are a Xen house, with all of our production servers running either Xen or Citrix XenServer Hypervisors.
0 Comments
Leave a Reply. |