Veritas Access Appliance Troubleshooting Guide

Last Published:
Product(s): Appliances (7.4.3)
Platform: Veritas 3340,Access Appliance OS
  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 Access Appliance 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 Access Appliance
    1.  
      About monitoring Access Appliance operations
    2.  
      Monitoring processor activity
    3.  
      Generating CPU and device utilization reports
    4.  
      Monitoring network traffic
  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 an Access Appliance 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 Access Appliance 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 Access Appliance installation and configuration issues
    1.  
      How to find the management console IP
    2.  
      Viewing the installation logs
    3.  
      Installation fails and does not complete
  7. Troubleshooting Access Appliance CIFS issues
    1.  
      User access is denied on a CTDB directory share
  8. Troubleshooting Access Appliance GUI startup issues
    1.  
      Resolving GUI startup issues
  9.  
    Index

General techniques for the troubleshooting process

After applying some general troubleshooting tips to narrow the scope of a problem, here are some techniques to further isolate the problem:

  • Swap identical parts.

    In a system with identical or parallel parts and subsystems, it is a good idea to swap components between those subsystems and see whether or not the problem moves with the swapped component. For example, if you experience Access Appliance network connection problems on one node in a cluster, you could swap Ethernet Interface cards to determine if the problem moves to the new node.

  • Remove parallel components.

    If a system is composed of several parallel or redundant components that can be removed without crippling the whole system, start removing these components (one at a time) and see if things start to work. For example, in a cluster, shutdown the nodes one-by-one to see if the problem still persists.

  • Divide the system into sections.

    In a system with multiple sections or stages, carefully measure the variables going in and out of each stage until you find a stage where things do not look right. For example, if you run across a problem with a replication job, check to see if the job has run successfully before and try to determine the time frame when the job started to fail.

  • Monitor system behavior over time (or location).

    Display a list of services and their current status using the Support> services show all command.

    Set up a process (such as the Support> traceroute command or a series of Support> iostat commands) to monitor system activity over a period of time or to monitor system activity across the network. This monitoring is especially helpful to track down intermittent problems, processor activity problems, node connection problems, and so on.