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

Exporting and displaying the network traffic details

To use the tethereal command

  • To use the Support> tethereal export command, enter the following:
    Support> tethereal export url [nodename] [interface] [count] 
    [source]

    url

    Provides the location to export the network traffic details. The default file name tethereal.log is used if a file name is not specified in the url.

    nodename

    The name of the node from where the traffic details are generated.

    interface

    Specifies the network interface for the packet capture.

    count

    Specifies the maximum number of packets to read.

    The maximum allowed file size to capture the network traffic details is 128 MB. For a very large "count" value, if the file size exceeds 128 MB, then the command stops capturing the network traffic details.

    source

    Specifies the node to filter the packets.

    For example, to export the network traffic details, enter the following:

    Support> tethereal export scp://user1@172.31.168.140:˜/
    Password: *******
    Capturing on pubeth0 ...
    Uploading network traffic details to scp://user1@172.31.168.140:˜/ 
    is completed.

    When you export network traffic details, press the Ctrl + C keys to stop the capture process and upload traffic details to the URL site.

To use the tethereal show command

  • To use the Support> tethereal show command, enter the following:
    Support> tethereal show [nodename] [interface] [count] 
    [source]

    nodename

    The name of the node from where the traffic details are displayed.

    interface

    Specifies the network interface for the packet capture.

    count

    Specifies the maximum number of packets to read.

    If you do not specify a count value, the network traffic continues to be displayed until you interrupt it.

    source

    Specifies the node to filter the packets.

    For example, the traffic details for five packets are:

    Support> tethereal show access_01 pubeth0 5 172.31.168.140
    0.000000 172.31.168.140 -> 10.209.105.147 ICMP Echo (ping) request
    0.000276 10.209.105.147 -> 172.31.168.140 ICMP Echo (ping) reply
    0.000473 10.209.105.147 -> 172.31.168.140 SSH Encrypted response 
    packet len=112
    0.000492 10.209.105.147 -> 172.31.168.140 SSH Encrypted response 
    packet len=112