Collects the core files from each component, logs, and configuration information from the management server and directors.
Contexts
All contexts.
Syntax
collect-diagnostics
--local-only
Arguments
Optional arguments
Description
--local-only
Gathers diagnostics only from the local cluster and directors.
-r | --log-range=Range
Collect only the logs that are generated in the range specified. To collect the set of logs that are generated in a certain range of hours of the current day, specify the value as
start-hour-end-hour>. For example, to collect the logs between 11AM to 1PM, enter the
range11-13h. To collect the set of logs generated in a certain range of days in the current month, enter the range
start-day-end-dayd. For example, to get the logs between 11 days ago to 13 days ago, enter the
range of
11-13d.
-l | --last-logs=x
Collect only the logs that are generated in the last
x days or hours are collected. To collect the logs generated in the last 4 hours, the value for this option is 4h. To collect the logs generated in last 4 days, use the value 4d.
--noextended
Omits the collection of extended diagnostics.
Description
Collects logs, cores, and configuration information from the management server and directors. Places the collected output files in the
/diag/collect-diagnostics-out directory on the management server.
Two compressed files are placed in the
/diag/collect-diagnostics-out directory:
<tla>-<cluster>-diag-<datetime>.tar.gz- Contains standard diagnostic logs.
<tla>-<cluster>-diag-ext-<datetime>.tar.gz- Contains standard diagnostic logs, java heap dump, fast trace dump, two latest core files, and two latest core files ( if
--noextended is used, then no core file is collected).
NOTE If
--noextended
is used, then this file is not available.
NOTE The collect-diagnostics must be run as the service user to collect all the available files. For this, the VPlexcli command must be invoked as the service user.
Best practice is to collect both files. The extended file is large, and thus takes some time to transfer.
Recommended practice is to transfer the base file (tla-diagnostics-timestamp.tar.gz) first and begin analysis while waiting for the extended file to transfer.
NOTE On metro node Metro configurations, collect-diagnostics must be invoked from each management server in order to collect complete diagnostics. The management server diagnostics files are only collected for the local cluster.
The director diagnostics are retrieved from ALL directors in a metro node Metro unless the
--local-only argument is used.
All trace files under the folder /cores/nsfw-trace/ on each director will be copied and put in the collected diagnostics.
CAUTION In metro node Metro configurations, run the
collect-diagnostics command on each management server, but NOT at the same time. Even if you use the
--local-only argument, do not run the command on both management servers at the same time.
If you know the time period in which an event happened, you can collect a subset of logs based on time period. This reduces the time to collect diagnostics. Use the
--log-range and
--last-logs arguments to collect a subset of diagnostics.
Remove files created by collect-diagnostics from the management server as soon as possible to avoid filling management server disk partitions.
Example
Collect diagnostics for the entire cluster:
VPlexcli:/> collect-diagnostics
If this is a metro configuration, then run it on each cluster independently.
VPlexcli:/> collect-diagnostics --noextended
Collect diagnostics, omitting trace files on the directors and the management server console heap, and send the output to the default directory.
See also
cluster configdump
director appdump
getsysinfo
sms dump
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\