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
Using the traceroute command
The Support> traceroute command displays all of the intermediate nodes on a route between two nodes.
To use the traceroute command
- To use the Support> traceroute command, enter the following:
Support> traceroute destination [source] [maxttl]
destination
The target node. To display all of the intermediate nodes that are located between two nodes on a network, enter the destination node.
You need to specify either an IPv4 address for an IPv4 installation or an IPv6 address for an IPv6 installation.
The accepted range for an IPv6 prefix is 0-128 integers.
source
Specifies the source node name from where you want to begin the trace.
maxttl
Specifies the maximum number of hops. The default is seven hops.
For example, to trace the route to the network host, enter the following:
Support> traceroute www.veritas.com fssClus_01 10 traceroute to www.veritas.com (23.5.150.79), 10 hops max, 60 byte packets 1 puna-sli-core-b01-vlan329.net.symantec.com (10.209.192.2) 0.356 ms 0.354 ms 0.376 ms 2 punb-vfpi-eng-1-aggregate2-104.net.veritas.com (10.209.186.14) 0.298 ms 0.322 ms 0.379 ms 3 puna-spi-core-b02-vlan105.net.symantec.com (143.127.185.130) 1.851 ms 1.964 ms 1.940 ms 4 bnrcatcore01-teng6-2.net.symantec.com (143.127.185.205) 1.902 ms 1.903 ms 1.932 ms 5 puna-vfpi-main-1-vip.net.veritas.com (10.212.252.50) 1.886 ms 1.945 ms 1.922 ms