• No results found

Chapter 16 Troubleshooting

16.2 When a Problem Occurs during Cloning

The following describes how to collect the troubleshooting data if clone image creation or cloning problems occur when adding or deleting slave servers.

Refer to "Troubleshooting" in the "ServerView Resource Orchestrator Virtual Edition V3.1.0 Operation Guide" for details.

16.2.1 Types of Troubleshooting Data

Collect the troubleshooting data when a problem occurs on the system where this product is being used so that Fujitsu technical support can investigate the problem.

1.

Collecting the initial troubleshooting data

Collect the data required for initial triage of the cause of the problem that occurred and contact Fujitsu technical support. The amount of information collection is small and so can be easily sent by means such as email.

Refer to "16.2.2 Collecting Initial Troubleshooting Data" for details.

2.

Collecting detailed troubleshooting data

It is sometimes possible to determine the cause by using just the initial troubleshooting data, but more troubleshooting data may be required for some problems.

It is then necessary to collect more detailed troubleshooting data. Detailed investigation involves collecting large number of resources that are needed to determine the cause of a problem that has occurred.

Consequently, the information collected will be larger than the initial troubleshooting data collected to triage the problem. If requested by Fujitsu technical support, send the detailed troubleshooting data that has been collected.

Refer to "16.2.3 Collecting Detailed Troubleshooting Data" for details.

Note

Collect the troubleshooting data quickly when a problem occurs. The information required to investigate a problem disappears as time passes.

16.2.2 Collecting Initial Troubleshooting Data

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.

1.

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.

2.

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.

Collecting diagnostics data from the admin sever (rcxadm mgrctl snap -all)

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).

1.

Log in to the master server using root permissions.

2.

Execute the rcxadm mgrctl snap -all command.

3.

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.

Collecting resources from servers (rcxadm mgrctl snap, rcxadm agtctl snap)

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).

1.

Log in to the server where the data will be collected using root permissions.

2.

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>

3.

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.

16.2.3 Collecting Detailed Troubleshooting Data

This section describes how to collect detailed troubleshooting data needed to determine the cause of a problem.

When the cause of a problem cannot be determined just from the initial troubleshooting data, more detailed troubleshooting data is required. The troubleshooting data required to determine the cause of a problem is collected by executing the troubleshooting data collection commands (rcxadm mgrctl snap -full and rcxadm agtctl snap -full) on servers.

80 MB of available space is required to execute this feature.

On the server where resources are to be collected, use the following procedure to collect the resources.

2.

Execute the rcxadm mgrctl snap -full or rcxadm agtctl snap -full 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 -full [-dir directory] <Enter>

When collecting on a slave server

# /opt/FJSVrcxat/bin/rcxadm agtctl snap -full [-dir directory] <Enter>

3.

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.

Related documents