Fujitsu V3.1 manual Behavior after AC failure

7.5 VIOM-internal operations on a PRIMERGY rack server

addresses or WWN addresses) are used from now on. Also the boot device priority setting as defined in the VIOM server profile is no longer valid. The performed init boot results in a power-off state and the server reports the status “Boot without VIOM” which is also displayed in the VIOM user interface on the Server Configuration tab in the table col- umn state. In some situations you may need to manually update this information in order to get the current state. To do this, click the Update States button.

Behavior after AC failure

The VIOM-specific virtualization data and inventory data are stored in the iRMC. This data only remains valid as long as the iRMC is powered on. Dur- ing a power loss (disconnection of all power cables or power loss in the data center) the iRMC will forget the VIOM virtualization data as well as the VIOM-specific inventory data. When AC power returns and the iRMC has booted again, it still has the following information:

1.This PRIMERGY rack server is managed by VIOM.

2.The VIOM-enabled flag is set.

3.The unique identification of the VIOM installation.

4.The SNMP trap destination as specified by VIOM when managing the server.

5.Whether VIOM virtualization data was stored in the iRMC before power loss or not.

If VIOM virtualization data was stored in the iRMC before power loss and because the iRMC knows that the server was managed by VIOM and that vir- tualization data was assigned, a special communication process with the VIOM management station will start when the iRMC is booted again after power has returned. This communication is based on sending SNMP traps to the VIOM management station and setting specific status information in the iRMC. For this process to work, the VIOM management station must be run- ning and must be accessible to the iRMC.

As long as the iRMC did not receive virtualization data from the VIOM man- agement station, it will periodically send SNMP traps to the management

ServerView Virtual-IO Manager 269