Search <book_title>...

Veritas Access Appliance 8.3 Troubleshooting Guide

Last Published: 2024-09-24

Product(s): Appliances (8.3)

Platform: Veritas 3360,Veritas 3350,Veritas 3340

Retrieving and sending debugging information

You can retrieve Access Appliance debugging information from the Access Appliance node and send the information to a server using an external FTP or SCP server.

If a node is part of the cluster, you can use the Veritas Access CLI to run the debuginfo command to collect and upload debug information to an SCP or an FTP server. If the node is not a part of the Access cluster, the Veritas Access CLI is not accessible, and you must instead use the collect_debuginfo.sh script to collect and upload the debug information.

See the following article for more information on how to provide data for Veritas Technical Support:

http://www.veritas.com/docs/000097935

Uploading debug information from a cluster node

You can upload debugging information from a specified node to an external server.

Support> debuginfo upload nodename
			debug-URL module

For example, to upload all debugging information to an FTP server:

Support> debuginfo upload node1_1
ftp://admin@ftp.docserver.company.com/patches/ all

For example, to upload CIFS-related debugging information to an SCP server:

Support> debuginfo upload node1_1
scp://root@server.company.com:/tmp/node1_1-cifs-debuginfo.tar.gz

nodename

Specifies the nodename from which to collect the debugging information.

debug-URL

Specifies the remote file or directory for uploading debugging information.

Depending on the type of server from which you upload debugging information, use one of the following example URL formats:

ftp://admin@ftp.docserver.company.com/
patches/

scp://root@server.company.com:/tmp/

If debug-URL specifies a remote file, the debuginfo file is saved by that name. If debug-URL specifies a remote directory, the debuginfo file name displays as the following:

nas_debuginfo_nodename_modulename_timestamp.tar.gz

module

Specifies the values for module.

The following options are supported:

generic: This module collects generic information such as details about the operating system and the CIFS module and SOS reports. This does not collect product information.
nas:This module collects product information from the cluster nodes.
os:This module collects SOS reports from all the cluster nodes.
explorer:The VxExplorer utility collects logs and environment data from all the servers where the Access Appliance product is installed.
install: This module collects the install logs from the CPI install log directory /opt/VRTS/install/logs/.
nas-procstacks: This module collects the stack trace for all the daemons that are in running state.
netbackup : This module collects logs about NetBackup from nodes.
appliance: This module collects the logs related to the appliance.
sds: This module collects SDS logs.
api_gateway: This module collects API gateway logs.
upgrade: This module collect the upgrade logs for all the cluster nodes.
backup: This module collects NetBackup client logs and other diagnostic information.
vdd: This module collects the deduplication logs provided dedupe is configured on the cluster nodes.
default: This module collects logs from all modules of the cluster nodes except the os module.
all: This module collects information for all the above modules from the cluster nodes.

The Support> debuginfo command also collects information for the sosreport command for Red Hat Enterprise Linux (RHEL). The sosreport is collected for all the loaded modules except for the selinux module.

Uploading debug information from a node that is not a part of the Access cluster

Use the /opt/VRTSnas/scripts/support/collect_debuginfo.sh script to collect and upload debug information when a node is not a part of the Access cluster. The script uses the following format:

/opt/VRTSnas/scripts/support/collect_debuginfo.sh -o upload -n nodename -d debug-URL -m module

where:

upload	Specifies the operation to perform. Use the upload option to upload the debug information to the location specified by the debug-URL parameter.
nodename	Specifies the name of the node from where you want to collect the debug information.
debug-URL	Specifies the location for uploading the debug information. The location can be an SCP server, an FTP server, or a remote file or a directory. Use one of the following formats based on location where you want to upload the debug information: ftp://url For example: ftp://admin@ftp.docserver.company.com/ scp://url For example: scp://root@server.company.com:/tmp/ If you specify a remote file, the debug information is saved in the specified file. If you specify a remote directory, the debug information is saved in the directory as a `tar.gz` file in the following format: `nas_debuginfo_nodename_modulename_timestamp.tar.gz`. For example: The sh /opt/VRTSnas/scripts/support/collect_debuginfo.sh -o upload -n node_01 -d file:///root/log/ -m nas-procstacks uploads the information to the `nas_debuginfo_node_01_nas-procstacks_201808270145.tar.gz` file in the `/root/log` directory.
modules	Specifies the modules. The following options are supported: `generic:` This module collects generic information such as details about the operating system and the CIFS module and SOS reports. This does not collect product information. `nas:`This module collects product information from the cluster nodes. `os:`This module collects SOS reports from all the cluster nodes. `explorer:`The VxExplorer utility collects logs and environment data from all the servers where the Access Appliance product is installed. `install:` This module collects the install logs from the CPI install log directory `/opt/VRTS/install/logs/`. `nas-procstacks:` This module collects the stack trace for all the daemons that are in running state. `netbackup :` This module collects logs about NetBackup from nodes. `appliance:` This module collects the logs related to the appliance. `sds:` This module collects SDS logs. `api_gateway:` This module collects API gateway logs. `upgrade:` This module collect the upgrade logs for all the cluster nodes. `backup:` This module collects NetBackup client logs and other diagnostic information. `vdd:` This module collects the deduplication logs provided dedupe is configured on the cluster nodes. `default:` This module collects logs from all modules of the cluster nodes except the os module. `all:` This module collects information for all the above modules from the cluster nodes.