This section describes how to collect the troubleshooting data needed to triage the cause of a problem.
Collect resources by using the appropriate method, depending on the characteristics of the collection method and the environment and the system where the problem occurred.
Collecting resources from the master server
Collect the troubleshooting data from the master server (rcxadm mgrctl snap -all)
The troubleshooting data from managed servers can be collected in a batch using the network, so this method is much simpler than executing the command on each individual managed server.
Refer to "Collecting diagnostics data from the admin sever (rcxadm mgrctl snap -all)", and collect the information.
Along with the 65 MB of available space required to execute the rcxadm mgrctl snap -all command, approximately 30 MB of space is required for each server.
Collecting resources from servers
Collect the troubleshooting data from servers (rcxadm mgrctl snap, rcxadm agtctl snap)
Refer to "Collecting resources from servers (rcxadm mgrctl snap, rcxadm agtctl snap)", and collect the information.
65 MB of available space is required to execute the rcxadm mgrctl snap command.
30 MB of available space is required to execute the rcxadm agtctl snap command.
By executing the command for collecting the troubleshooting data (rcxadm mgrctl snap -all) on the admin server, the troubleshooting data for managed servers is collected in a batch.
The following describes collecting the troubleshooting data with the command (rcxadm mgrctl snap -all).
Log in to the master server using root permissions.
Execute the rcxadm mgrctl snap -all command.
# /opt/FJSVrcvmr/bin/rcxadm mgrctl snap [-dir directory] -all <Enter>Send the information collected to Fujitsu technical support.
Note
When collecting resources from the master server, the manager must be operating on the admin server. If the manager is not operating, collect resources on individual servers.
The troubleshooting data cannot be collected from managed servers in the following cases:
When a communications route has not been established
If a managed server has stopped
In either case, collection of the troubleshooting data on other managed servers continues uninterrupted.
Check the command execution results in the execution log.
Refer to "rcxadm mgrctl" in the "ServerView Resource Orchestrator Express/Virtual Edition V3.1.0 Command Reference" for details.
When collection has failed on a managed server, either execute the rcxadm mgrctl snap -all command on the master server again or execute the rcxadm agtctl snap command on the managed server.
Apart from the rcxadm mgrctl snap -all command that is executed on the master server and that can collect the troubleshooting data in a batch from managed servers, there are the rcxadm mgrctl snap and rcxadm agtctl snap commands that collect the information only on the server where they are executed.
The following describes collecting the troubleshooting data with the commands (rcxadm mgrctl snap or rcxadm agtctl snap).
Log in to the server where the data will be collected using root permissions.
Execute the rcxadm mgrctl snap or rcxadm agtctl snap command.
Note that the command executed depends on the server where the resources are collected.
When collecting on a master server
# /opt/FJSVrcvmr/bin/rcxadm mgrctl snap [-dir directory] <Enter>When collecting on a slave server
# /opt/FJSVrcxat/bin/rcxadm agtctl snap [-dir directory] <Enter>Send the information collected to Fujitsu technical support.
Refer to "rcxadm agtctl" or "rcxadm mgrctl" in the "ServerView Resource Orchestrator Express/Virtual Edition V3.1.0 Command Reference" for details.