This section explains how to change the settings for the Admin Server.
Use the following procedure to change the admin IP address of the Admin Server.
Change procedure
Log in to the Admin Server with an OS administrator account.
Stop the Manager.
Refer to "5.1 Manager" for details on how to stop the Manager.
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.
Refer to the manual of the LAN switch blade used for details.
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 settings of the following LAN redundancy software.
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 from the [Failover Cluster Management] window.
Change the IP address set for the Manager.
Use the "rcxadm mgrctl modify" command to set a new IP address.
>"Installation folder\Manager\bin\rcxadm" mgrctl modify -ip IP_address <RETURN> |
In a clustered Manager configuration, refer to "Clustered Manager Configuration" for details on how to change the Manager IP address.
Log in to the Admin Server with an OS administrator account.
Change ServerView Agent settings on the managed server.
Change the SNMP trap destination of the ServerView Agent. Refer to the ServerView Agent manual for details on changing SNMP trap settings.
Stop the Agent on managed servers. [Windows/Linux] [Hyper-V]
Refer to "5.2 Agent" for details on how to stop the Agent.
Change Agent settings. [Windows/Linux] [Hyper-V]
Use the "rcxadm mgrctl modify" command to set the new Manager IP address.
>"Installation folder\Agent\bin\rcxadm" agtctl modify -manager IP_address <RETURN> |
Restart the Agent on managed servers. [Windows/Linux] [Hyper-V]
Refer to "5.2 Agent" for details on how to restart the Agent.
Repeat steps 6 to 11 for each managed server on which the Agent is running.
Restart the Manager.
Refer to "5.1 Manager" for details on how to restart the Manager.
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 "6.2.2.1 Settings for the HBA address rename setup service".
Back up managed servers.
If system image backups were already collected, it is recommended to update those images in order to reflect the changes made above. Refer to "8.2 Backing Up System Images" in the "ServerView Resource Coordinator VE Operation Guide" for details on system image backup.
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.
Re-collect cloning images. [Windows/Linux]
If cloning images were already collected, it is recommended to update those images to reflect the changed made above. Refer to "8.2 Collecting a Cloning Image" for details on cloning image collection.
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.
Clustered Manager Configuration
In a clustered Manager configuration, use the following procedure to change the admin IP address.
Remove 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.
For x64 architectures
SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\DHCP
For x86 architectures
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] dialog is displayed.
In the [Registry Replication] tab, select the above registry key and click the <Delete> button.
The selected key is removed from the [Root registry key] list.
After removing the registry key, click the <Apply> button.
Once settings are applied, click the <OK> button 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\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] dialog is displayed.
In the [Registry Replication] tab, click the <Add> button.
The [Registry Key] dialog is displayed.
Restore the registry key deleted in step 1 in "Root registry key" and click the <OK> button.
After completing registry key settings, click the <Apply> button.
Once settings are applied, click the <OK> button to close the dialog.
Assign the Manager shared disk and IP address to the secondary node.
In the Failover Cluster Management tree, right-click [Services and Applications]-[RC-manager], and select [Move this service or application to another node]-[1 - Move to node node_name].
The name of the secondary node is displayed in 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 shared disk and IP address to the primary node.
In the Failover Cluster Management tree, right-click [Services and Applications]-[RC-manager], and select [Move this service or application to another node]-[1 - Move to node node_name].
The name of the primary node is displayed in node_name.
On the primary node, bring online the Manager shared disk and IP address.
Resource Coordinator VE requires the following services to be running. When starting these services, make sure that the ports they are using do not conflict with the ports used by other applications or services. If necessary, change the ports used by Resource Coordinator VE services.
Manager services
Resource Coordinator Manager
Resource Coordinator Task Manager
Resource Coordinator Web Server (Apache)
Resource Coordinator Sub Web Server (Mongrel)
Resource Coordinator Sub Web Server (Mongrel2)
Systemwalker MpWksttr
Deployment services
Deployment Service
TFTP Service
PXE Services
Change the ports used by the above services if there is a possibility that they will conflict with other applications or services.
For Windows operating systems, an ephemeral port may conflict with a Resource Coordinator VE service if the maximum value allowed for ephemeral ports (5000 by default) was changed. In this case, change the port numbers used by Resource Coordinator VE services to values greater than the maximum ephemeral port value.
This section explains how to change the ports used by Resource Coordinator VE services.
Refer to the ServerView Operations Manager manual for information on how to change the ports used by ServerView Operations Manager. The ports used for SNMP communication and server power control are defined by standard protocols and fixed at the hardware level, thus can not be changed.
Refer to "Appendix C Port List", for details on the ports used by Resource Coordinator VE.
When using a firewall on the network, firewall settings should be updated to match the new port definitions and allow communications for any modified port.
Manager services
Use the following procedure to change the Admin Server ports used by Manager services:
Stop Manager services.
Refer to "5.1 Manager" for details on how to stop Manager services.
Change port numbers.
Use the "rcxadm mgrctl modify" command to set a new port number for a given service name.
>"Installation_folder\Manager\bin\rcxadm" mgrctl modify -port name=number <RETURN> |
Refer to "5.6 rcxadm mgrctl" of the "ServerView Resource Coordinator VE Command Reference" for details on this command and the service names that can be passed in the name parameter.
In a clustered Manager configuration, bring offline all Manager resources except for the shared disk and IP address, move all cluster resources from the primary node to the secondary node, then execute the "rcxadm mgrctl modify" command on all the nodes that are hosting cluster resources.
Restart Manager services.
Refer to "5.1 Manager" for details on how to restart Manager services.
Note
When changing the "rcxweb" port, the following ports should be set to the same value.
Admin Client
Enter the "rcxweb" port in the Web browser URL used to log into Resource Coordinator VE.
If this URL is bookmarked in the Web browser "Favorites", change the port set in the bookmark's URL.
Change the RC console shortcut on the Manager
Open the following folder on the Admin Server.
Installation folder\Manager
Right click the "RC Console" icon, and select [Properties] from the popup menu.
In the [Web Document] tab, change the port number set in the "URL" field (as shown below).
URL: https://localhost:23461/ |
Click the <OK> button.
HBA address rename setup service
If the HBA address rename setup service is running, change the port number used to communicate with the Admin Server to the "rcxweb" port according to "6.3.3 Changing Settings for the HBA Address Rename Setup Service".
When changing the "nfagent" port, the following ports on managed servers should be set to the same value.
Set the "nfagent" port set on each managed server to the same value, according to the instructions given in "6.3.2.6 Changing Port Numbers".
The system image and cloning images collected before the change can no longer be used, and should be deleted.
If necessary, re-collect system images and cloning images.
Deployment services
Use the following procedure to change the ports used by deployment services.
Change port numbers.
Open the Windows Registry Editor, and search for the following subkey:
When using a 32-bit version of Windows:
Key name: HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\SystemcastWizard\CLONE
When using a 64-bit version of Windows:
Key name: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\CLONE
Select "PortBase" from the registry entries under this subkey.
From the menu, select "Edit"-"Modify"
The "Edit DWORD Value" dialog is displayed.
In the "Edit DWORD Value" dialog, select the "Decimal" base, and enter a new port value in "Value data".
This port value will define the first port of the range used by deployment services.
Note, however, that up to 16 port numbers will be used by deployment services, so ensure that none of the ports between "PortBase" (defined here) and "PortBase+15" conflict with any other application or service. Also, be sure to set a value lower than 65519 for "PortBase" so that the highest port number ("PortBase+15") does not exceed the largest valid port number (65534).
Click the <OK> button.
In a clustered Manager configuration, change port numbers on both the primary and secondary node.
Restart the server on which the port number has been changed.
Information
Deployment services allow managed servers to boot from the network using a dedicated module stored on the Admin Server during backup, restore or cloning.
Note that changing port numbers on the Admin Server alone is enough to support communication during the above image operations. Therefore, no additional configuration is required on the managed servers.
Use the following procedure to change the maximum number of system image versions.
Change the maximum number of system image versions.
Confirm the maximum number of system image versions.
Refer to "5.4 rcxadm imagemgr" of the "ServerView Resource Coordinator VE Command Reference" for details.
Note
If the specified limit is smaller than the number of existing system image versions, older versions will not be deleted automatically. In this case, backing up a new system image, will only delete the oldest version.
Delete unused image versions manually if they are no longer necessary. Refer to "8.5 Deleting a System Image" in the "ServerView Resource Coordinator VE Operation Guide" for details.
Use the following procedure to change the maximum number of cloning image versions.
Change the maximum number of cloning image versions.
Confirm the maximum number of cloning image versions.
Refer to "5.4 rcxadm imagemgr" of the "ServerView Resource Coordinator VE Command Reference" for details.
Note
If the specified limit is smaller than the number of existing cloning image versions, older versions will not be deleted automatically. In this case, collecting a new cloning image version will require selecting a previous image version for deletion.
Delete unused image versions manually if they are no longer necessary. Refer to "8.5 Deleting a Cloning Image" for details.
Use the following procedure to change the location (path) of the image files folder.
Select the [Image List] tab in the RC console and confirm the current image list.
Log on to the Admin Server as the administrator.
Stop manager services.
Refer to "5.1 Manager" for details.
Change the location of the image folder.
Refer to "5.4 rcxadm imagemgr" of the "ServerView Resource Coordinator VE Command Reference" for details.
It may take time to execute the command because image files will be copied during this operation.
In a clustered Manager configuration, refer to "Clustered Manager Configuration" for details on how to change the image folder location.
Start manager services.
Refer to "5.1 Manager" for details.
Select the [Image List] tab in the RC console and confirm the image list is same as before.
Clustered Manager Configuration
Remove registry replication settings.
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 "Deployment Services" cluster resource.
For x64 architectures
SOFTWARE\Wow6432Node\Fujitsu\SystemcastWizard\ResourceDepot
For x86 architectures
SOFTWARE\Fujitsu\SystemcastWizard\ResourceDepot
Use the following procedure to remove the registry key.
In the [Failover Cluster Management] window, right click the "Deployment Service" resource in "Summary of RC-Manager"-"Other Resources", and select [Properties] from the popup menu.
The [Deployment Service Properties] dialog is displayed.
In the [Registry Replication] tab, select the above registry key and click the <Delete> button.
The selected key is removed from the [Root registry key] list.
After removing the registry key, click the <Apply> button.
Once settings are applied, click the <OK> button to close the dialog.
Change the location of the image files folder
Change the location of the image files folder according to the instructions given in "5.4 rcxadm imagemgr" of the "ServerView Resource Coordinator VE Command Reference".
Because image files are actually copied over to the new location, this step may take some time to complete.
Run the "rcxadm imagemgr" command from either node of the cluster resource.
The new location should be a folder on the shared disk.
Restore registry replication settings
Restore the registry key deleted in step 1 to the registry replication settings of the "Deployment Service" resource.
Use the following procedure to restore the registry key.
In the [Failover Cluster Management] window, right click the "Deployment Service" resource in "Summary of RC-Manager"-"Other Resources", and select [Properties] from the popup menu.
The [Deployment Service Properties] dialog is displayed.
In the [Registry Replication] tab, click the <Add> button.
The [Registry Key] dialog is displayed.
Restore the registry key deleted in step 1 in "Root registry key" and click the <OK> button.
After completing registry key settings, click the <Apply> button.
Once settings are applied, click the <OK> button to close the dialog.
