7.5 VIOM-internal operations on a PRIMERGY rack server

The iRMC has limited storage to store multiple trap des- tinations. This configuration can be modified by other programs or by using the iRMC user interface. When removing the trap destination of the VIOM management station from the iRMC configuration, this might result in incorrect behavior of the server, in the case of a power loss event for this server.

VIOM also needs a username and password in order to authen- ticate on the iRMC when communicating with the iRMC via RMC protocol (IPMI over LAN).

2.The Virtual-IO Manager performs a special so-called “inventory boot”, which creates an inventory table for this server in the iRMC. This inven- tory table is used to check the availability of the required I/O devices when assigning a VIOM server profile to this PRIMERGY rack server.

Therefore you will see that a PRIMERGY rack server is powered on when a server is managed by VIOM. This inventory boot does not boot an operating system; it powers down the server when the inventory table is created and stored in the iRMC.

After these actions the PRIMERGY rack server is integrated into the VIOM management and is ready to be assigned a VIOM server profile. When assigning a VIOM server profile the following actions are performed:

1.VIOM checks that the server is powered off by reading the power state reported by the iRMC.

2.VIOM reads the inventory data stored in the iRMC and checks whether the server supplies the I/O devices configured in the VIOM server profile that is to be assigned to this server.

3.VIOM writes virtualization data to the iRMC. This data contains the vir- tual addresses for all the configured I/O devices in the VIOM server pro- file and also the boot information. The virtualization data also contains the port-disable configuration for any I/O device found in the inventory data of this server, for which the server profile does not contain a con- figuration. VIOM cannot guarantee that all I/O devices that are not con- figured in the profile are disabled. This only works on devices that

ServerView Virtual-IO Manager

267

Page 267
Image 267
Fujitsu V3.1 manual