Veritas Access Troubleshooting Guide
- 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
Replacing an Ethernet interface card (offline mode)
In some cases, you may need to replace an existing Ethernet interface card (NIC) on a node. This section describes the steps to replace the NIC card. When you replace the NIC, there should not be any mismatch with the number of NICs in the cluster. All the nodes in cluster should have an equal number of disks after you replace the NIC card.
You need to provide a correct and permanent MAC address (in case of bonded NICs) before you proceed with the NIC replacement. High availability services of service groups are temporarily disabled when you replace the NIC. The same PCI slot needs to be used when you replace an Ethernet card.
In the VLAN configured environment, when you add nodes, the IPs/netmasks that are assigned to the devices may not work correctly. To avoid these issues, modify the IPs by using the following command:
clish> network ip addr modify 192.168.10.21 192.168.10.27 255.255.240.0
After you add a node in the cluster, it triggers the recovery for the detached disks.
Note:
These steps do not work for adding an Ethernet interface card to the cluster. After the successful replacement operation, remove the faulty NIC. Before you install the Ethernet interface card on the node, install the device driver that is required for the Ethernet interface card.
To replace an offline Ethernet interface card
- Run the Cluster> del command to delete the node from the cluster.
- Install the Ethernet interface card on the node that you want replace with the existing NIC card and restart the node.
Note:
Make sure that the Ethernet interface card and node are online and searchable.
- Run the Cluster> add command to add the node into the cluster.
For example:
Cluster> add 172.16.113.118