Veritas Access Troubleshooting Guide

Last Published:
Product(s): Appliances (Version Not Specified)
Platform: 3340
  1. Introduction
    1.  
      About troubleshooting
    2.  
      General tips for the troubleshooting process
    3.  
      General techniques for the troubleshooting process
  2. General troubleshooting procedures
    1.  
      About general troubleshooting procedures
    2.  
      Viewing the Veritas Access log files
    3.  
      About event logs
    4.  
      About shell-activity logs
    5.  
      Setting the CIFS log level
    6.  
      Setting the NetBackup client log levels and debugging options
    7.  
      Retrieving and sending debugging information
    8.  
      Insufficient delay between two successive OpenStack commands may result in failure
  3. Monitoring Veritas Access
    1.  
      About monitoring Veritas Access operations
    2.  
      Monitoring processor activity
    3.  
      Generating CPU and device utilization reports
    4.  
      Monitoring network traffic
    5.  
      Exporting and displaying the network traffic details
  4. Common recovery procedures
    1.  
      About common recovery procedures
    2.  
      Restarting servers
    3. Bringing services online
      1.  
        Using the services command
    4.  
      Recovering from a non-graceful shutdown
    5.  
      Testing the network connectivity
    6.  
      Troubleshooting with traceroute
    7.  
      Using the traceroute command
    8.  
      Collecting the metasave image of a file system
    9.  
      Replacing an Ethernet interface card (online mode)
    10.  
      Replacing an Ethernet interface card (offline mode)
    11.  
      Replacing a Veritas Access node
    12.  
      Replacing a disk
    13. Speeding up replication
      1.  
        About synchronizing a replication job
      2.  
        Synchronizing an episodic replication job
    14.  
      Uninstalling a patch release or software upgrade
  5. Troubleshooting the Veritas Access cloud as a tier feature
    1.  
      Troubleshooting tips for cloud tiering
    2.  
      Issues when reading or writing data from the cloud tier
    3.  
      Log locations for checking for cloud tiering errors
  6. Troubleshooting Veritas Access installation and configuration issues
    1.  
      How to find the management console IP
    2.  
      Viewing the installation logs
    3.  
      Installation fails and does not complete
    4.  
      Excluding PCI IDs from the cluster
    5.  
      Cannot recover from root file system corruption
    6.  
      The storage disk list command returns nothing
  7. Troubleshooting the LTR upgrade
    1.  
      Locating the log files for troubleshooting the LTR upgrade
    2.  
      Troubleshooting pre-upgrade issues for LTR
    3.  
      Troubleshooting post-upgrade issues for LTR
  8. Troubleshooting Veritas Access CIFS issues
    1.  
      User access is denied on a CTDB directory share
  9. Troubleshooting Veritas Access GUI startup issues
    1.  
      Resolving GUI startup issues
  10.  
    Index

Retrieving and sending debugging information

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

If a node is a part of the Access 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

To upload debugging information from a specified node to an external server

  • 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 Veritas Access product is installed.

    • install: This module collects the install logs from the CPI install log directory /opt/VRTS/install/logs/.

    • 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 logs 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 the 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 Veritas product is installed.

  • install This module collects the install logs from the CPI install log directory /opt/VRTS/install/logs/.

  • all This module collects information for all the above modules from the cluster nodes.