Please enter search query.
Search <book_title>...
Veritas Access Troubleshooting Guide
Last Published:
2021-02-14
Product(s):
Appliances (Version Not Specified)
Platform: 3340
- Introduction
- General troubleshooting procedures
- About general troubleshooting procedures
- Viewing the Veritas Access log files
- About event logs
- About shell-activity logs
- Setting the CIFS log level
- Setting the NetBackup client log levels and debugging options
- Retrieving and sending debugging information
- Insufficient delay between two successive OpenStack commands may result in failure
- Monitoring Veritas Access
- Common recovery procedures
- About common recovery procedures
- Restarting servers
- Bringing services online
- Recovering from a non-graceful shutdown
- Testing the network connectivity
- Troubleshooting with traceroute
- Using the traceroute command
- Collecting the metasave image of a file system
- Replacing an Ethernet interface card (online mode)
- Replacing an Ethernet interface card (offline mode)
- Replacing a Veritas Access node
- Replacing a disk
- Speeding up replication
- Uninstalling a patch release or software upgrade
- Troubleshooting the Veritas Access cloud as a tier feature
- Troubleshooting Veritas Access installation and configuration issues
- Troubleshooting the LTR upgrade
- Troubleshooting Veritas Access CIFS issues
- Troubleshooting Veritas Access GUI startup issues
- Index
How to find the management console IP
To identify which node is the console IP (management console IP)
- Identify which node is the management console IP.
# hares - state | grep -I console
- Use a Secure Shell (ssh) to access the management console (only one node has the management console).
- Log on to the Veritas Access management console IP using the admin user credentials.