IBM has developed an I/O virtualisation tool that makes it easier to move workloads from one blade server to another by automating the process of assigning I/O addresses.
IBM BladeCenter Open Fabric Manager will start shipping in mid-December. IBM bills the product as an upgrade over HP's Virtual Connect because IBM uses open technology that's compatible with switches from multiple vendors.
I/O address virtualisation solves a problem faced by blade administrators, who are faced with constant provisioning and reconfiguration of systems to adjust for changing workloads, writes analyst Joe Clabby in a piece for Pund-IT Research analysing IBM's offering.
Administrators must assign MAC addresses and World Wide Name identifiers, and after basic hardware set-up they have to assign LAN and SAN connection addresses. Then they have to repeat this process for every server they install.
"Instead of physically mapping each blade to external networks every time a new or replacement server is needed, IBM's BladeCenter Open Fabric Manager automatically maps new or reconfigured servers," Clabby writes. "Blade managers can cut configuration time down from days to minutes."
It also saves customers the trouble of assigning new addresses when one blade fails and a workload must be moved to another server, says Stuart McRae, IBM's BladeCenter business line manager.
IBM's new I/O virtualisation offering will compete with HP's Virtual Connect.
HP's product is simpler, as it can be run by lesser-skilled systems administrators as long as they know how to monitor and control a blade systems environment, Clabby writes. But Virtual Connect costs more than IBM's take on I/O virtualisation, because HP bundles I/O address management with Ethernet and Fibre Channel hardware that is more expensive than that offered by IBM, according to Clabby.
McRae argues that IBM has one-upped HP by supporting technology from multiple vendors, like Blade Network Technologies, Brocade, Cisco, Emulex, NetXen and QLogic.
"You see huge cost savings with the IBM route because customers can choose switch technology that meets the functionality they have," McRae says.
HP has instead engineered its own proprietary device, Clabby writes, so "the level of HP's Virtual Connect integration with other vendors' management environments is not as feature/function rich as the IBM offerings."