Veritas Access Troubleshooting Guide

Last Published:
Product(s): Appliances (7.3.2)
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
    10. Speeding up replication
      1.  
        About synchronizing a replication job
      2.  
        Synchronizing an episodic replication job
    11.  
      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 Veritas Access CIFS issues
    1.  
      User access is denied on a CTDB directory share
  8. Troubleshooting Veritas Access GUI startup issues
    1.  
      Resolving GUI startup issues

Generating CPU and device utilization reports

To use the iostat command

  • To use the Support> iostat cpu command, enter the following:
    Support> iostat cpu [nodename] [interval] [count]

    nodename

    The name of the node from where the report is generated. The default is console for the Management Console.

    interval

    The duration between each report in seconds. The default is 2 seconds.

    count

    The number of reports generated at the interval entered in seconds. The default is one report.

    where the nodename option asks for the name of the node from where the report is generated. The default is console for the Veritas Access Operations Manager console.

    For example, to generate the CPU utilization report of the console node, enter the following:

    Support> iostat cpu access_01
    Linux 2.6.16.60-0.21-smp (access_01)       02/09/16
    
    avg-cpu:  %user   %nice  %system  %iowait  %steal   %idle
               1.86    0.07     4.53     0.13    0.00   93.40

To use the iostat device command

  • To use the Support> iostat device command, enter the following:
    Support> iostat device [nodename] [dataunit]
    [interval] [count]

    nodename

    The nodename option asks for the name of the node from where the report is generated. The default is console for the Management Console.

    dataunit

    The dataunit option lets you generate the report in block(s) or kilobytes(s). The default is block(s).

    interval

    The duration between each report in seconds. The default is two seconds.

    count

    The number of reports generated at the interval entered in seconds. The default is one report.

    For example, to generate a device utilization report of a node, enter the following:

    Support> iostat device access_01 Blk
    Linux 2.6.16.60-0.21-smp (access_01)       02/09/16
    
    Device:      tps   Blk_read/s   Blk_wrtn/s   Blk_read   Blk_wrtn
    hda         4.82        97.81        86.11    1410626    1241992
    sda         1.95        16.83         4.05     242712      58342
    hdc         0.00         0.01         0.00        136          0