This section provides an example of a Resource Coordinator VE system configuration.
Figure 1.1 System Configuration Example
The admin server is a server used to manage several managed servers.
The admin server operates in a Windows or Linux environment.
The Resource Coordinator VE manager should be installed on the admin server. When using VIOM for I/O virtualization, ServerView Virtual-IO Manager should also be installed on the admin server.
The admin server can be made redundant by using clustering software.
The admin client can operate on the same machine as the admin server.
The Resource Coordinator VE agent cannot be installed on the admin server to monitor and manage the admin server itself.
Managed servers are the servers used to run applications. They are managed by the admin server.
They include primary servers running Windows, Linux and server virtualization software, and spare servers used to recover applications in case a primary server fails.
A Resource Coordinator VE agent should be installed on each managed server.
Note that in server virtualization environments, the agent should only be installed on the VM host (it does not need to be installed on the VM guests).
Admin clients are terminals used to connect to the admin server, which can be used to monitor and control the configuration and status of the entire system.
Admin clients should run in a Windows environment.
A Web browser should be installed on admin clients.
If a server virtualization software client is installed on an admin client, it can be launched directly from the RC console.
A server on which VM management software (such as VMware vCenter Server and others) has been installed.
Such a server is used to centrally manage virtualization environments.
This server is used to run the HBA address rename setup service.
It is required when using HBA address rename (However, it is not required for VIOM-based I/O virtualization).
This server takes care of configuring a managed server's WWN settings in place of the admin server if the admin server is unreachable when the managed server starts up.
The HBA address rename server operates in a Windows or Linux environment.
The HBA address rename setup service should be installed on this server for the HBA address rename function to operate properly.
This server cannot serve as an admin server or as a managed server.
This server must be powered on at all times to standby for an admin server failure or communication problems between a managed server and the admin server.
The admin LAN is the LAN used by the admin server to control managed servers.
The admin LAN is set up separately from the public LAN used by applications on managed servers.
Use of network redundancy software on the admin LAN enables redundancy for monitoring and power control functions.
For the backup and restore function, network redundancy can only be enabled by using the redundant line control function of PRIMECLUSTER GLS.
