This section explains configuration for using ServerView Infrastructure Manager.
Install the ServerView Infrastructure Manager virtual appliance on a server other than the admin server.
For the installation method, refer to the manuals of ServerView Infrastructure Manager.
Note
In ISM V2.2 or later, if the power of an iRMC is lost the virtual I/O settings applied to the profile will also be lost.
In that case, it is necessary to re-apply the virtual I/O settings.
For the method for re-applying the virtual I/O settings, refer to the ISM User's Manual.
With ISM V2.3 or later, the default version of the usable SSL/TLS protocol is set as TLSv1.2.
When using an installation upgraded from ISM V2.2.x, the conventional TLSv1 can be used.
When performing a new installation of ISM V2.3 or later, configure it so that ISM can also use TLSv1.
For details of the method for specifying
# ismadm security enable-tls TLSv1,TLSv1.1,TLSv1.2
and an example of execution, refer to "4.20 Changing the SSL/TLS Protocol Version" in the ISM V2.3 User's Manual.
When performing a new installation of ISM V2.4.c or later, ISM V2.5, or ISM V2.6 or later
Execute the following command within the Infrastructure Manager console with Administrator privileges
# ismadm security set-sslcipher 1
Restart ISM-VA
# ismadm power restart
The following steps are only necessary when using PXE boot in ISM.
Prepare a (Windows) server other than the admin server or managed servers.
Configure the server as a DHCP server using the following procedure:
Add DHCP Server to the server roles.
Bind the DHCP server to the network connection of a NIC configured with an IP address in the same network as the admin LAN of the admin server.
For details on adding and binding, refer to the Windows documentation.
When the DHCP server is a member of a domain, perform the following step.
Authorize the DHCP server.
Click [Control Panel]-[Administrative Tools]-[DHCP].
The [DHCP] window is displayed.
Select [Action]-[Manage authorized servers].
The [Manage Authorized Servers] window will be displayed.
Click the [Authorize] button.
The [Authorize DHCP Server] window will be displayed.
Enter the admin IP address of the admin server in [Name or IP address].
Click the [OK] button.
The [Confirm Authorization] window will be displayed.
Check the [Name] and [IP Address].
Click the [OK] button.
The DHCP server will be added to the [Authorized DHCP servers] on the [Manage Authorized Servers] window.
Install a Resource Orchestrator agent on the DHCP server.
For details, refer to "2.2.2 Installation [Windows] [Hyper-V]".
Note
Select [Express/Virtual Edition] for the agent edition.
On the [License Authentication Information Entry] window, click [Next>] without selecting [Using the cloning feature of this product].
Note
The basic software which can be installed on the DHCP server is the same as that of the Resource Orchestrator agent [Windows].
The DHCP server is also able to manage VM guests created using virtualization software.
It is not necessary to install ServerView Agents for Windows, which is required software for the Resource Orchestrator agent [Windows], on the DHCP server.
When using PXE boot in ISM, it is necessary to temporarily stop the PXE services of the admin server using the rcxadm pxectl command.
For details, refer to "3.19 rcxadm pxectl" in the "Reference Guide (Command/XML) CE".
While the PXE services of the admin server are stopped, the following functions cannot be used.
HBA address rename settings
Server switchover and failback (based on the HBA address rename and backup-restore methods)
Backup and restore
Deletion of system images
Collection of cloning images
Deployment of cloning images
Deletion of cloning images
Execution of the rcxadm imagemgr set command
Registration of servers
Deletion of servers
Changing of the admin LAN IP addresses of managed servers
Registration of admin subnets
Creation of physical L-Servers
Backup and restore of physical L-Servers
Collection and deployment of cloning images of physical L-Servers
Information
To transfer a managed server from being managed by VIOM to being managed by ISM, perform the following procedure.
If a spare server is configured for the target server, release the spare server settings.
Start the ServerView Virtual-IO Manager Web UI.
For details, refer to "5.1.1 Registering Profiles" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Delete the profile of the relevant server.
Remove the server from the targets of management by VIOM.
Start the ServerView Infrastructure Manager Web UI.
Configure the profile of the target server.
For details, refer to the manuals of ServerView Infrastructure Manager.
Regular update processing of Resource Orchestrator is performed.
The fact that the target server is now being managed by ISM is reflected on Resource Orchestrator.
If necessary, reconfigure the spare server for the transferred server.
Delete the target physical L-Server from Resource Orchestrator.
Start the ServerView Virtual-IO Manager Web UI.
For details, refer to "5.1.1 Registering Profiles" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Delete the profile of the relevant server.
Remove the server from the targets of management by VIOM.
Start the ServerView Infrastructure Manager Web UI.
Configure the profile of the target server.
For details, refer to the manuals of ServerView Infrastructure Manager.
Regular update processing of Resource Orchestrator is performed.
The fact that the target server is now being managed by ISM is reflected on Resource Orchestrator.
Create a physical L-Server based on the transferred server.
