Please enter search query.
Search <book_title>...
Veritas Access Troubleshooting Guide
Last Published:
2018-08-10
Product(s):
Appliances (7.3.2)
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
- 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 Veritas Access CIFS issues
- Troubleshooting Veritas Access GUI startup issues
Setting the CIFS log level
You can set the CIFS log level for the Veritas Access cluster, and then upload the debugging information to an external server for troubleshooting.
See the support_debug.1 man page.
See Retrieving and sending debugging information.
To set the CIFS log level
- Set the CIFS-related log level for the Veritas Access cluster.
Support> debuginfo setlog cifs loglevel
A valid loglevel ranges from 0 to 10, 10 being the most detailed log level. It is recommended to increase the CIFS log level, reproduce the CIFS issue, and then upload debugging information for the CIFS issue.
The default log level is 2.
For example, to set the CIFS log level to 10 for the Veritas Access cluster:
Support> debuginfo setlog cifs 10