This section explains how to change the ports used by the Manager services and related services of Resource Orchestrator.
Resource Orchestrator requires the following services to be running. When starting these services, ensure 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 Orchestrator services.
[Windows Manager]
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)
Resource Coordinator DB Server (PostgreSQL)
Related Services
Deployment Service
TFTP Service
PXE Services
DHCP Server
[Linux Manager]
Manager Services
rcxmanager
rcxtaskmgr
rcxmongrel1
rcxmongrel2
rcxhttpd
rcxdb
Related Services
scwdepsvd
scwpxesvd
scwtftpd
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 Orchestrator service if the maximum value allowed for ephemeral ports (5000 by default) was changed. In this case, change the port numbers used by Resource Orchestrator services to values greater than the maximum ephemeral port value.
For information on how to change the ports used by ServerView Operations Manager, refer to the ServerView Operations Manager manual. The ports used for SNMP communication and server power control are defined by standard protocols and fixed at the hardware level, and thus cannot be changed.
For the port numbers used by Resource Orchestrator, refer to "Appendix A Port List" in the "Design Guide CE".
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 the manager.
Stop the manager, referring to "2.1 Starting and Stopping the Manager" in the "Operation Guide CE".
Change the port numbers.
Use the rcxadm mgrctl modify command to set a new port number for a given service name.
[Windows Manager]
>"Installation_folder\SVROR\Manager\bin\rcxadm" mgrctl modify -port name=number <RETURN> |
[Linux Manager]
# /opt/FJSVrcvmr/bin/rcxadm mgrctl modify -port name=number <RETURN> |
In a clustered manager configuration, bring offline all cluster resources except for the manager's 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.
Start the manager referring to "2.1 Starting and Stopping the Manager" in the "Operation Guide CE".
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 Orchestrator.
If this URL is bookmarked in the Web browser "Favorites", change the port set in the bookmark's URL.
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 "7.2.2 Changing the Port Number Used to Communicate with the Admin Server".
[Windows Manager]
Change the ROR console shortcut on the manager
Open the following folder on the admin server.
Installation_folder\SVROR\Manager
Right-click the "ROR 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 <OK>.
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 "7.1.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.
Related Services
Use the following procedure to change the port numbers used for the related services:
[Windows Manager]
Change the 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.
Select [Decimal] and click <OK>.
This port value will define the first port of the range used by deployment services.
However, because the related services can use up to 16 port numbers, ensure that all ports included between "PortBase" (defined here) and "PortBase+15" do not conflict with any other applications or services. Moreover, 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).
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.
[Linux Manager]
Change the port numbers.
Edit the following file: /etc/opt/FJSVscw-common/scwconf.reg.
In PortBase (under HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\SystemcastWizard\CLONE), set the first value of the port number to be used by deployment services. This value should be entered in hexadecimal format. To avoid conflicts with ephemeral ports, use a value not included in the ephemeral port range defined by "net.ipv4_local_port_range".
However, as a maximum of 16 port numbers are used for image file creation and deployment, ensure that the port numbers for PortBase to PortBase +15 do not conflict with ephemeral or well-known ports.
This ensures that deployment services will use ports outside of the range defined by net.ipv4.ip_local_port_range for image operations.
Moreover, 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).
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
The related 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.
