The Resource Coordinator VE manager starts automatically on the admin server.
This section explains how to manually start or stop the manager and how to check its running state.
[Windows]
The manager is made up of the following two groups of Windows 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
From the Windows Control Panel, open "Administrative Tools". Then, open the [Services] window to check the state of each service.
Services are started and stopped using the rcxadm mgrctl command (start and stop subcommands). As this command collectively controls both manager and deployment services, use the command to start and stop services.
For details on these commands, refer to "5.6 rcxadm mgrctl" of the "ServerView Resource Coordinator VE Command Reference".
To start or stop a manager in a clustered configuration, right-click the manager application shown under the Failover Cluster Management tree, and select either [Bring this service or application online] or [Take this service or application offline].
[Linux]
The manager is made up of the following two groups of Linux services.
Manager services
rcvmr
Manager services also include the following daemons.
rcxmanager
rcxtaskmgr
rcxmongrel1
rcxmongrel2
rcxhttpd
Deployment services
scwdepsvd
scwpxesvd
scwtftpd
The status of each of those services can be confirmed from the "service" command, as shown below.
# service rcvmr status <RETURN> |
Services are started and stopped using the rcxadm mgrctl command (start and stop subcommands).
For details on these commands, refer to "5.6 rcxadm mgrctl" of the "ServerView Resource Coordinator VE Command Reference".
To start or stop a manager in a clustered configuration, use the cluster administration view (Cluster Admin).
For details, refer to the PRIMECLUSTER manual.
Note
If ServerView Deployment Manager is used on the admin LAN, the Deployment services of Resource Coordinator VE are automatically disabled. To prevent conflicts with ServerView Deployment Manager, those services should never be started. Refer to "Appendix H Co-Existence with ServerView Deployment Manager" for details.
The "Systemwalker MpWksttr" service is shared between the following products:
Systemwalker Centric Manager
ETERNUS SF Storage Cruiser
Since the Systemwalker MpWksttr service is shared, the rcxadm mgrctl command has the following effects:
rcxadm mgrctl start
This command starts the Systemwalker MpWksttr service only if it was not already running.
rcxadm mgrctl stop
This command leaves the Systemwalker MpWksttr service running.
Use the following procedure to stop the Systemwalker MpWksttr service.
[Windows]
Stop the other manager services using the "rcxadm mgrctl stop" command.
If there are other products installed on the admin server that share the Systemwalker MpWksttr service, stop the services associated with these products.
From the Control Panel, open "Administrative Tools", open the [Services] window, and stop the Systemwalker MpWksttr service.
[Linux]
Stop the other manager services using the "rcxadm mgrctl stop" command.
If there are other products installed on the admin server that share the Systemwalker MpWksttr service, stop the services associated with these products.
Use the following command to stop the Systemwalker MpWksttr service.
# /opt/FJSVswstt/bin/mpnm-trapd stop <RETURN> |
Resource Coordinator VE cannot operate if any of the manager services are stopped. Ensure that all services are running when Resource Coordinator VE is running.
If the manager is unable to communicate on the admin LAN when started up (because of LAN cable disconnections or any other causes), PXE Services may not start automatically. If PXE Services are stopped, investigate the network interface used for the admin LAN and confirm whether it can communicate with other nodes on the admin LAN.
If the manager cannot communicate with admin LAN nodes, restore the admin LAN itself and restart the manager according to the above procedure.
