EXCLUSIVE: IBM System x3850 M2
Server virtualisation is a hot topic these days and the System x3850 M2 is IBM’s multi-VM capable one-box solution. We see how it stacks up.
Server virtualisation is enjoying an exponential growth this year and all the key server manufacturers want a piece of the action. None can afford to be left out of this burgeoning market as businesses realise the many benefits that virtualisation has to offer, not just in terms of maximising investment in hardware but also with environmental issues. IBM has seen the light and in an exclusive review we bring you its latest System x3850 M2 offering, which is designed to deliver a complete out-of-the-box solution for server virtualisation.
The x3850 is provided with VMware's ESX 3i Embedded - or ESXi as VMware has recently renamed it as - preinstalled on an internal USB flash memory stick. On power up, the system boots straight into VMware's embedded hypervisor and is managed remotely via the VMware Infrastructure (VI) client. A big advantage of this method is the ESXi hypervisor has had the service console removed and only occupies 32MB of disk space. This does away with any requirement for a standard operating system to act as a platform for the VM software.
Compared with VMware's ESX Server 3.5 Standard and Enterprise, ESXi has a substantially reduced feature set and supports a single virtualisation host. Features you won't see here are VMware's instant server provisioning, VMotion, DRS load balancing or Distributed Power Management. However, ESXi will support all the VMware InfraStructure features that have been purchased separately. It's also worth noting that VMware has now made ESXi freely available but support is an optional extra. IBM advised us that it offers full support for the software which costs 1,239 for a one year contract.
Installation really is as easy as IBM claims. After power up, the server boots the thin hypervisor and presents a basic direct console for initial configuration. All you need do here is set up IP addressing for the management network port and secure administrative access. Next, you install the VI client on your chosen management system and point it at the server's IP address. The client can be installed from the supplied CD-ROM or you can use a web browser session to download it from the server.
The VI client interface is easy enough to use and you can begin by creating pools which contain CPU and memory resources that can be allocated to VMs created within these pools. You'll need to create datastores which use the physical drives on the server to present storage to the VMs. Virtual switches also come into the mix where you assign the physical network ports on the server to them and use these to present VMs to the network.
Now you can move on to creating VMs within a resource pool and this process is handled smoothly by a wizard based routine. You decide how many virtual processors and allocated memory each can have, the datastore and virtual switch they will be assigned to and which OS you plan to install on them. All VMs are configured, controlled and managed from the same interface so it's easy enough to swap from one console to the next. You can see clearly what resources each VM has assigned to it, view a performance graph for each one and take snapshots which act as backups of their environment.
Unlocking collaboration: Making software work better together
How to improve collaboration and agility with the right techDownload now
Four steps to field service excellence
How to thrive in the experience economyDownload now
Six things a developer should know about Postgres
Why enterprises are choosing PostgreSQLDownload now
The path to CX excellence for B2B services
The four stages to thrive in the experience economyDownload now