Veritas Access Appliance 8.2 Troubleshooting Guide

Last Published:
Product(s): Appliances (8.2)
Platform: Veritas 3340,Veritas 3350,Veritas 3360
  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.  
      Setting the CIFS log level
    5.  
      Setting the NetBackup client log levels and debugging options
    6.  
      Retrieving and sending debugging information
    7.  
      Collecting time-based and archived logs
  3. Monitoring Access Appliance
    1.  
      About monitoring Access Appliance operations
    2.  
      Monitoring hardware components
  4. Common recovery procedures
    1.  
      About common recovery procedures
    2.  
      Restarting servers
    3.  
      Restarting cluster services
    4. Bringing services online
      1.  
        Using the services command
    5.  
      Recovering from a non-graceful shutdown
    6.  
      Testing the network connectivity
    7.  
      Troubleshooting with traceroute
    8.  
      Using the traceroute command
    9.  
      Collecting the metasave image of a file system
    10.  
      Replacing an Ethernet interface card (online mode)
    11.  
      Replacing an Access Appliance node
    12. Speeding up episodic replication
      1.  
        About synchronizing an episodic replication job
      2.  
        Synchronizing an episodic replication job
    13.  
      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. Troubleshooting Veritas Data Deduplication issues
    1.  
      Log locations for the Veritas Data Deduplication server
  10.  
    Index

Resolving GUI startup issues

Access Appliance 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 Access Appliance GUI after installing Access Appliance

  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 Access Appliance GUI.

    Example:

    https://console IP address:14161
  3. Log on to the Access Appliance GUI using the admin 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