Veritas Access Troubleshooting Guide
- Introduction
- General troubleshooting procedures
- Monitoring Veritas Access
- Common recovery procedures
- Bringing services online
- Speeding up replication
- Troubleshooting the Veritas Access cloud as a tier feature
- Troubleshooting Veritas Access installation and configuration issues
- Troubleshooting Veritas Access CIFS issues
- Troubleshooting Veritas Access GUI startup issues
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
- Obtain the Management console virtual IP address by using the Network> ip addr show command from the Veritas Access CLISH.
- Use the Management console IP with the port number 14161 to access the Veritas Access GUI.
Example:
https://console IP address:14161
- If this does not work, verify the GUI set up.
To verify the GUI setup
- Log on to the Access 3340 Appliance by using the admin user on the node where the Veritas Access Management console is running.
- Check the
/opt/SYMCsnas/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.
- Allow the 5634 and 14161 ports to be accessible remotely.
- 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
- Turn off the firewall on start up:
# chkconfig iptables off
Note:
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.
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.
- Verify if a port is accessible by running the following command:
telnet hostname/ipaddress 14161
Note:
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 can notice a difference in behavior.
- Restart if the web server is not running.
service vamgmt forcestop
service vamgmt start
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 development
Note:
You should be able to connect to the GUI and be able to log on.
- 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
- If there are any errors, check the log file.
/opt/VRTSnas/log/isagui_cluster_perf.log