Systemwalker Resource Coordinator Virtual server Edition

---

---

Functional overview

Unified operation and management of both physical and virtual blade servers

Systemwalker Resource Coordinator Virtual server Edition provides a common management view with customized graphical user interfaces that lets you manage (i) Physical server operating systems (Physical OS), (ii) VMware Infrastructure 3 ESX Server environments (ESX Server) and (iii) guest operating systems (Guest OS) running on top of the virtual server.

• Tree structured management
  - System managers can quickly identify the effects on Guest OS of physical server problems. Blade server chassis, blade servers, ESX Server and Guest OS can all be viewed in one informative hierarchical tree structure.
  - In addition, ESX server is handled using the same operational procedures as Physical OS. Therefore operation is simplified and errors minimized.
• OS and application management
  - The relationship between Physical OS and Guest OS is also shown. This means managers can also consistently monitor and reconfigure systems, regardless of their physical or virtual nature, using the same procedures.

---

Systemwalker Resource Coordinator Virtual server Edition can be used as is or in combination with the functions provided by VMware Infrastructure 3. In particular, in a SAN boot environment, Systemwalker Resource Coordinator Virtual server Edition can share spare servers with VMware HA.

Systemwalker Resource Coordinator Virtual server Edition also simplifies operation, as the agent installed on ESX Server controls Guest OS. No separate agents need be installed on each Guest OS for full operation.

---

IO virtualization simplifies system operation　

A unique physical World Wide Name (WWN) is fixed to each blade server IO adapter (HBA) when the server is shipped. This WWN is used by the storage network to recognize the server. When servers are added or switched, these physically unique storage network WWN must be changed.

The I/O virtualization technology of Systemwalker Resource Coordinator, enable servers to control I/O by setting up a virtual WWN for each server, instead of a fixed physical address WWN.

This means system administrators can now dynamically add, replace and automatically recover blade servers just be changing the server configuration. It removes the impact of changing the complicated storage configurations. Administrators now simply predefine the relation between the virtual WWN and storage volume once only.

<Note> The above functions require PRIMERGY Blade Server I/O virtualization (FC).

Automated blade server installation and configuration

Systemwalker Resource Coordinator Virtual server Edition allows you to simply copy and collectively install a common system image on multiple physical servers all at once (Cloning). This significantly reduces administrative workload and human error.

Under a SAN boot environment, administrators can therefore configure and install blade servers without need to change the existing SAN storage configuration.

In addition, when a server administrator wants to separate blade servers from business LAN subnet, VLAN switchblade configuration, which previously required complicated operational processes is now easily performed. Further, the use of Cloning enables business LAN configuration to be automated.

Simplified blade server addition and maintenance

Server IO virtualization, lets you easily and quickly install additional and maintain blade servers in a SAN boot environment.

(1) Server addition
Simply using virtual WWN and system disk image selection allows the Blade to be automatically recognized by the SAN storage and OS configuration and setup automatically completed.

(2) Server maintenance
The front panel LED can be lit remotely to identify a defective or offlined blade. This prevents mis-operation when changing or servicing blade servers. Once replaced the Virtual WWN is applied and OS configuration and setup can be completed.

In addition, under a local boot environment, Systemwalker Resource Coordinator Virtual server Edition enables efficient installation of additional or replacement blade servers by maintaining and restoring their system backups.

<Note 1>
When restoring VMware ESX server backups, system image for Guest OS should be allocated on a disk in the SAN environment as the system image of the Guest OS cannot be restored together with ESX server.

<Note 2>
ETERNUS SF Storage Cruiser must be used for SAN storage management.
http://www.fujitsu.com/global/services/computing/storage/software/cruiser/

Improved server availability (Automated Recovery)

By configuring an automatic recovery operation to a server, a user can continue his/her business operation without knowing the server is switched over when it is down.

(1) A SAN boot environment
Using server IO virtualization, blade servers can be switched without changing SAN environment configuration. OS and applications are made available on the spare server using the same boot disk as the original server. With VMware ESX Server running, the VMware ESX Server and Guest OS continue to run.

---

(2) A local boot environment
Creating backup images for each blade server in advance allows them to be cloned onto a spare server and booted to replace a downed server. System administrators can further reduce the time required to switch to the spare server if they restore the backup onto the spare server in advance.

<Note> ETERNUS SF Storage Cruiser must be used for SAN storage management.