6 server profile failover (for blade servers only) – FUJITSU ServerView Virtual-IO Manager V3.1 User Manual

Page 47

Advertising
background image

If the virtualization of the I/O addresses for a slot is switched off, e. g. if the
corresponding server profile is unassigned, the physical I/O addresses
assigned by the manufacturer will automatically be reactivated in the next
boot phase.

The iRMC of a PRIMERGY rack server loses virtualization I/O parameter
table during power failures. So the table has to be rewritten by ServerView Vir-
tual-IO Manager before the server is powered on again. This restoration proc-
ess is done automatically. But this requires that the management station has
to be kept running as long as PRIMERGY rack servers are managed. For fur-
ther information, see

"VIOM-internal operations on a PRIMERGY rack

server" on page 266

.

2.6

Server profile failover (for blade servers only)

If a problem occurs or maintenance work needs to be carried out, VIOM pro-
vides the option to move the server profiles from the affected server blade to
a suitable server blade within the same blade server.

In order to do this, you must define spare slots that assume the tasks of the
other server blade in such a case. It is advisable to install server blades at
the spare slots so that they are available if a problem occurs or maintenance
work needs to be carried out. A failover of this type can only take place if the
server blade on which the failover is to take place is switched off.

If a server blade fails, for example, you launch the failover function via the
context menu of the corresponding server blade. VIOM then searches for a
spare slot that has a server blade to which the server profile can be assigned.
Once such a slot has been found, the profile assignment on the affected
server blade is deleted, and the server profile is assigned to the new server
blade. The new server blade thus assumes the role of the failed server blade
including the network addresses.

The Virtual-IO Manager does not make any changes to the boot
image in a SAN and does not clone any disk images to the local hard
disk of the replacement server blade.

ServerView Virtual-IO Manager

47

2.6 Server profile failover (for blade servers only)

Advertising