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

Resolving GUI startup issues

Veritas Access GUI accessibility issues occur if specific ports are inaccessible. Ports might be turned off on the node or on the network switch. Veritas selectively opens ports at the network switch.

To use the Veritas Access GUI after installing Veritas Access

  1. Obtain the console virtual IP address by using the network ip addr show command.
  2. Use the console IP with the port number 14161 to access the Veritas Access GUI.

    Example:

    https://console IP address:14161
  3. Log on to the Veritas Access GUI using the support user name and password.

If this does not work, verify the GUI set up.

To verify the GUI set up

  1. Check the /opt/VRTSnas/log/isagui_config.log file to verify that the GUI is properly configured.

    If there are any problems during the configuration, the problems are reported in this log file.

  2. You need to allow ports 5634 and 14161 to be accessible remotely.
  3. Open these ports by executing the following commands.

    You must log on as the root user.

    # /etc/init.d/iptables save
# /etc/init.d/iptables stop
  4. Turn off the firewall on start up:
    # chkconfig firewalld off

    The commands work if there is no network switch-based firewall in the environment. Otherwise you need to contact the network administrator to open these ports.

  5. Ports must be opened before the GUI is configured. Otherwise you should rerun the GUI configuration. Before you rerun the GUI configuration, try connecting the browser to the management console.
  6. You can verify if a port is accessible by running the following command:
    telnet hostname/ipaddress 14161

    If the port is not opened or not listened to, the connection waits forever. Try connecting with a random port that is not open. You see a difference in behavior.

  7. Restart if the web server is not running.
    # /opt/VRTSnas/pysnas/bin/vamgmt -h
    # /opt/VRTSnas/pysnas/bin/vamgmt status
    # ps -ef | grep node

    After running the ps -ef | grep node command, the results should show:

    /opt/VRTSnas/isagui/ext_modules/node /opt/VRTSnas/isagui/application/server.js production
  8. You should be able to connect to the GUI and be able to log on.
  9. If data is not properly discovered or not seen in the GUI, run the following commands:
    Export EXTRA_LOG=1
    /opt/VRTSnas/pysnas/bin/isagui_cluster_perf.py --full
  10. If there are any errors, check the log file.
    /opt/VRTSnas/log/isagui_cluster_perf.log