Veritas Access Appliance 8.3 Troubleshooting Guide
- Introduction
- General troubleshooting procedures
- Monitoring Access Appliance
- Common recovery procedures
- Bringing services online
- Speeding up episodic replication
- Troubleshooting the Access Appliance cloud as a tier feature
- Troubleshooting Access Appliance installation and configuration issues
- Troubleshooting Access Appliance CIFS issues
- Troubleshooting Access Appliance GUI startup issues
- Troubleshooting Veritas Data Deduplication issues
Replacing an Ethernet interface card (online mode)
In some cases, you may need to replace an existing Ethernet interface card on a node. This section describes the steps to replace the NIC card. When you replace the NIC card, there should not be any mismatch with the number of NICs in the cluster. All the nodes in the cluster should have an equal number of disks after you replace the NIC card.
You need to provide an accurate 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 during the NIC replacement operation.
Note:
This procedure does not work for adding an Ethernet interface card to the cluster and in VLAN environments. After the successful replacement operation, remove the faulty NIC card. Before you install the Ethernet interface card on the node, install the required device driver for the Ethernet interface card.
To replace an online Ethernet interface card (NIC)
- Add a new NIC card on the server.
Note:
The new NIC card should be online and searchable by the server.
- Run the # ip link show command to get the MAC address of the new NIC card.
- Run the following command on the Access Appliance node to replace the NIC card.
# /opt/VRTSnas/scripts/net/net_device_add.sh -r <old_mac_address> -w <new_mac_address>
- To replace the NIC card in the bonded interface, you need to find a permanent hardware address by using one of the following commands.
# ethtool -P <interfacename>
or
# cat /proc/net/bonding/<bondname>
For details, see the following examples.
: To replace the "pubeth2" interface in the bond with the new NIC "eth0"
Bonding details:
# cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: load balancing (round-robin) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: pubeth1 MII Status: up Speed: 10000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:50:56:05:0a:ea Slave queue ID: 0 Slave Interface: pubeth2 MII Status: up Speed: 10000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:50:56:05:e0:45 Slave queue ID: 0 # ip link show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: priveth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000 link/ether 00:50:56:05:a3:1d brd ff:ff:ff:ff:ff:ff 3: pubeth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000 link/ether 00:50:56:05:e0:44 brd ff:ff:ff:ff:ff:ff 4: pubeth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT qlen 1000 link/ether 00:50:56:05:0a:ea brd ff:ff:ff:ff:ff:ff 5: pubeth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT qlen 1000 link/ether 00:50:56:05:0a:ea brd ff:ff:ff:ff:ff:ff 6: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT qlen 1000 link/ether 00:50:56:05:41:53 brd ff:ff:ff:ff:ff:ff 7: priveth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000 link/ether 00:50:56:05:e0:41 brd ff:ff:ff:ff:ff:ff 8: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT qlen 1000 link/ether 00:50:56:05:0a:ea brd ff:ff:ff:ff:ff:ff
NIC replacement operation
# /opt/VRTSnas/scripts/net/net_device_add.sh -r 00:50:56:05:e0:45 -w 00:50:56:05:41:53 100% [#] Success: Device replace successful. After NIC replacement
# cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: load balancing (round-robin) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: pubeth1 MII Status: up Speed: 10000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:50:56:05:0a:ea Slave queue ID: 0 Slave Interface: pubeth2 MII Status: up Speed: 10000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:50:56:05:41:53 Slave queue ID: 0