Veritas Access Troubleshooting Guide

Last Published:
Product(s): Access (7.3.1)
Platform: Linux
  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

The storage disk list command returns nothing

The storage disk list command may display blank disk names due to the following reasons:

  • In Virtual environments, Virtual Machine Disk (VMDK) disks are shared across the nodes of the cluster.

    Resolution:

    Ideally, VMDK disks should be attached as local disks.

  • Local disks have a unique device identifier (UDID) that is not unique.

    For example, in a cluster having node1 and node2, the local disk that is attached to node1 may have the same UDID as the local disk attached to node2.

    Resolution:

    Run the following command:

    #	storage disk configure local <node_name> <vendor_id> <product_id>
[serial_num]

    Where <vendor_id> is the ID of the vendor.

    <product_id> is the ID of the product.

    <node_name> is the name of the node on which the command is run.

    <serial_num> should be given in the format opcode/pagecode/offset/length calculated carefully from the serial number format of the disk.

    If you want to run the command on all the nodes, specify the <node_name> value as all.

    For details on the storage disk configure local command, see the storage_disk manual page.