When multiple NIC cards are used on a remote cluster submit host, additional configuration may be necessary to establish communications between the RSM client and the submit host.
If necessary, stop the RSM launcher service.
Use the RSM Utilities application to specify the correct IP address of the cluster submit host. The correct IP address is the address seen in the output of a “ping” program from any remote machine to this machine using the Fully Qualified Domain Name (FQDN). Examples are
1.2.3.4andmachine.mycompany.com.Windows: Run the following command in the [RSMInstall]\bin directory:
rsm.exe appsettings set Global RemotingMachineNameAttribute <IP address>Linux: Run the following command in the [RSMInstall]\Config\tools\linux directory:
rsmutils appsettings set Global RemotingMachineNameAttribute <IP address>If you chose RSM Internal File Transfer as your file handling method, RSM will use TCP sockets to stream files from the client machine to the submit host machine. In this case, use the RSM Utilities application to specify the correct IP address in the
SocketTransfererListenerIpAddresssetting:Windows: Run the following command in the [RSMInstall]\bin directory:
rsm.exe appsettings set UserProxy SocketTransfererListenerIpAddress <IP address>Linux: Run the following command in the [RSMInstall]\Config\tools\linux directory:
rsmutils appsettings set UserProxy SocketTransfererListenerIpAddress <IP address>Restart the RSM launcher service:
For Windows: On your Administrative Tools or Administrative Services page, open the Services dialog box. Restart the services by right-clicking on the service and selecting .
For Linux: Log into a Linux account with administrative privileges and ensure that
Ans.Rsm.*processes are not running. Open a terminal window in the [RSMInstall]/Config/tools/linux directory and run the following command:./rsmlauncher restartIf you run the RSM launcher service as a daemon, go to the
/etc/init.ddirectory and run the following command:./rsmlauncher242 restart