Use the following procedure to change the IP address used on the admin LAN by the admin server.
Log on to the admin server with OS administrative privileges.
Stop the manager.
Stop the manager, referring to "2.1 Starting and Stopping the Manager" in the "Operation Guide CE".
Change the SNMP trap destination set for the management blade and LAN switch blades.
Set the SNMP trap destination to the new IP address of the admin server.
Note
Depending on the LAN switch blade used, setting an SNMP trap destination may restrict SNMP access to that switch blade.
In a clustered manager configuration, set the physical IP addresses of both the primary and secondary nodes as SNMP trap destinations.
If the LAN switch blade is set to only grant access from known IP addresses, be sure to give permissions to the physical IP addresses of both the primary and secondary cluster nodes, as is done with trap destination settings.
For details, refer to the manual of the LAN switch blade to be used.
Change the IP address set within the operating system.
Change the IP address following the instructions given in the operating system's manual.
If the admin LAN has been made redundant, change the admin IP address set in the following tools or products.
PRIMECLUSTER GLS
BACS
Intel PROSet
Refer to the manual of each product for usage details.
In a clustered manager configuration, change the cluster IP address according to the instructions given in "Changing the IP Address of a Clustered Manager".
Change the IP address registered as the manager's admin IP address.
Use the rcxadm mgrctl modify command to set a new IP address.
[Windows Manager]
>"Installation_folder\SVROR\Manager\bin\rcxadm" mgrctl modify -ip IP_address <RETURN> |
[Linux Manager]
# /opt/FJSVrcvmr/bin/rcxadm mgrctl modify -ip IP_address <RETURN> |
In a clustered manager configuration, for details on how to change the admin IP address registered for the manager, refer to "Settings for Clustered Manager Configurations".
Log in to the managed server with an OS administrator account.
Change ServerView Agents settings on the managed server.
Change the SNMP trap destination of the ServerView Agents. Refer to the ServerView Agent manual for details on changing SNMP trap settings.
Stop the agents on managed servers. [Windows] [Hyper-V] [Linux] [Xen] [KVM]
Stop the agent referring to "2.2 Starting and Stopping the Agent" in the "Operation Guide CE".
Change Agent settings. [Windows] [Hyper-V] [Linux] [Xen] [KVM]
Use the rcxadm agtctl modify command to set the new manager IP address.
[Windows] [Hyper-V]
>"Installation_folder\Agent\bin\rcxadm" agtctl modify -manager IP_address <RETURN> |
[Linux] [Xen] [KVM]
# /opt/FJSVrcxat/bin/rcxadm agtctl modify -manager IP_address <RETURN> |
Restart the agents on managed servers. [Windows] [Hyper-V] [Linux] [Xen] [KVM]
Start the agent referring to "2.2 Starting and Stopping the Agent" in the "Operation Guide CE".
Restart the manager.
Start the manager referring to "2.1 Starting and Stopping the Manager" in the "Operation Guide CE".
Repeat steps 6 to 11 for each managed server on which an agent is running.
Re-configure the HBA address rename setup service.
When using the HBA address rename function, change the IP address of the admin server that is set for the HBA address rename setup service according to "Chapter 10 Settings for the HBA address rename Setup Service" in the "Setup Guide CE".
Back up managed servers.
If system image backups have already been collected from managed servers, it is recommended to update those images in order to reflect the changes made above. For details on system image backup, refer to "10.2 Offline Backup of the Admin Server" in the "Operation Guide CE".
System images backed up before changing the admin IP address of the admin server cannot be restored anymore after the change. It is recommended to delete all system images collected before change, unless those images are specifically needed.
Collect a cloning image. [Physical Servers]
If cloning images have already been collected from managed servers, it is recommended to update those images to reflect the change made above. For details on cloning image collection, refer to "12.2 Collecting a Cloning Image".
Cloning images collected before changing the admin IP address of the admin server cannot be deployed anymore after the change. It is recommended to delete all cloning images collected before change, unless those images are specifically needed.
Note
IP addresses belonging to registered admin LAN subnets cannot be changed.
When a managed server belongs to the same subnet as the admin server, either delete the managed server or manually change the admin IP address of the managed server. Without changing the IP address of the managed server, it is not possible to register the information of the subnet the managed server belongs to, or change the information of the subnet.
Changing the IP Address of a Clustered Manager
In a clustered manager configuration, use the following procedure to change the IP address set within the operating system.
[Windows Manager]
Change the IP address using the [Failover Cluster Management] window.
[Linux Manager]
Stop the manager's cluster service.
Stop the manager's cluster service from the cluster administration view (Cluster Admin).
Log in to the admin server's primary node.
Log in to the operating system of the admin server's primary node with administration privileges.
Mount the shared disk on the primary node.
Mount the admin server's shared disk on the primary node.
Change takeover the logical IP address.
Release PRIMECLUSTER GLS virtual interface settings from the PRIMECLUSTER resource, then change the PRIMECLUSTER GLS configuration.
For details, refer to the PRIMECLUSTER Global Link Services manual.
Activate the takeover logical IP address.
Use the PRIMECLUSTER GLS command-line to activate the takeover logical IP address.
For details, refer to the PRIMECLUSTER Global Link Services manual.
Settings for Clustered Manager Configurations
In a clustered manager configuration, use the following procedure to register an IP address as the manager's admin LAN IP address.
[Windows Manager]
Cancel registry replication settings.
On the primary node, bring online the shared disk and IP address, and take all other resources offline.
Next, remove the following registry key from the registry replication settings set for the [PXE Services] cluster resource.
x64
SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\DHCP
x86
SOFTWARE\Fujitsu\SystemcastWizard\DHCP
Use the following procedure to remove the registry key.
In the [Failover Cluster Management] window, right-click the "PXE Services" resource in [Summary of RC-manager]-[Other Resources], and select [Properties] from the popup menu.
The [PXE Services Properties] window will be displayed.
In the [Registry Replication] tab, select the above registry key.
Click <Remove>.
The selected key is removed from the [Root registry key] list.
After removing the registry key, click <Apply>.
Click <OK> to close the dialog.
Change the manager IP address on the primary node.
On the primary node, use the rcxadm mgrctl modify command to set the new IP address.
>"Installation_folder\SVROR\Manager\bin\rcxadm" mgrctl modify -ip IP_address <RETURN> |
Restore registry replication settings.
Restore the registry key deleted in step 1. to the registry replication settings of the [PXE Services] resource.
Use the following procedure to restore the registry key.
In the [Failover Cluster Management] window, right-click the "PXE Services" resource in [Summary of RC-manager]-[Other Resources], and select [Properties] from the popup menu.
The [PXE Services Properties] window will be displayed.
Click <Add> on the [Registry Replication] tab.
The [Registry Key] window will be displayed.
Configure the above registry key in [Root registry key].
Click <OK>.
After configuration of the registry keys is complete, click <Apply>.
Click <OK> to close the dialog.
Assign the manager's shared disk and IP address to the secondary node.
Right-click [Services and Applications]-[RC-manager] on the Failover Cluster Management tree, and select [Move this service or application to another node]-[1 - Move to node node_name] from the displayed menu.
The name of the secondary node is displayed for node_name.
Change the manager IP address on the secondary node.
On the secondary node, use the rcxadm mgrctl modify command to set the new IP address.
Use the same IP address as the one set in step 2.
Assign the manager's shared disk and IP address to the primary node.
Right-click [Services and Applications]-[RC-manager] on the Failover Cluster Management tree, and select [Move this service or application to another node]-[1 - Move to node node_name] from the displayed menu.
The name of the primary node is displayed for node_name.
On the primary node, take the manager's shared disk and IP address offline.
[Linux Manager]
Change the IP address set for the admin LAN.
Set a new IP address on the primary node using the following command.
# /opt/FJSVrcvmr/bin/rcxadm mgrctl modify -ip IP_address <RETURN> |
De-activate the admin server's takeover logical IP address.
Use the PRIMECLUSTER GLS command-line interface to de-activate the takeover logical IP address.
For details, refer to the PRIMECLUSTER Global Link Services manual.
Register the takeover logical IP address as a PRIMECLUSTER resource.
Use the PRIMECLUSTER GLS command-line interface to register the virtual interface as a PRIMECLUSTER resource.
For details, refer to the PRIMECLUSTER Global Link Services manual.
Un-mount the shared disk.
Un-mount the shared disk from the primary node.
Log in to the admin server's secondary node.
Log in to the operating system of the admin server's secondary node with administration privileges.
Change takeover the logical IP address.
Use the PRIMECLUSTER GLS command-line interface to remove virtual interface settings from the PRIMECLUSTER resource, register the resource, and change the PRIMECLUSTER GLS configuration.
For details, refer to the PRIMECLUSTER Global Link Services manual.
Change the cluster configuration.
Use the cluster RMS Wizard to change the GLS resource set in the cluster service of either one of the cluster nodes.
After completing the configuration, save it and execute the following operations.
Configuration-Generate
Configuration-Activate
Start the Manager's cluster service.
Use the cluster administration view (Cluster Admin) to start the Manager's cluster service.
