FUJITSU ServerView Virtual-IO Manager V3.1 - Manual (Page 266)

7 Managing servers with VIOM
7.5 VIOM-internal operations on a PRIMERGY rack
server
This section explains the internal operations perfomed when you activate or
deactivate management with VIOM for a PRIMERGY rack server.
VIOM-internal operations during activation
When you activate management with the Virtual-IO Manager for a PRIM-
ERGY rack server, the following actions occur internally:
1. The PRIMERGY rack server is indicated as “managed” by this VIOM
installation. This is done by assigning a corresponding status to this
server node in the VIOM database and also by storing information about
the VIOM installation in a VIOM-specific property in the iRMC. This infor-
mation uniquely identifies the current VIOM installation. (Note: This infor-
mation is not changed during an update installation of VIOM, but it does
change when uninstalling and during a new installation.)
This information in the iRMC is always checked before a server
is managed. If VIOM can recognize from this that a PRIM-
ERGY rack server is already managed by another Virtual-IO
Manager, you receive a corresponding warning. If, however,
you are sure that a server is no longer managed by another
VIOM installation, you can still add the server to the man-
agement despite the warning.
VIOM also changes a special VIOM-enabled flag in the iRMC from “not
enabled” to “enabled” and a trap destination is stored in the iRMC. The
trap destination is one of the required details that VIOM needs to manage
a PRIMERGY rack server. The trap destination must be the IP address
or server name of the ServerView management station where this Vir-
tual-IO Manager and ServerView Operations Manager are installed.
When you specify a server name, the iRMC must be able to resolve this
server name into a valid IP address via DNS so that SNMP traps sent by
iRMC to the IP address reach the VIOM management station.
266 ServerView Virtual-IO Manager