Veritas Access Troubleshooting Guide

Last Published:
Product(s): Appliances (Version Not Specified)
Platform: 3340
  1. Introduction
    1.  
      About troubleshooting
    2.  
      General tips for the troubleshooting process
    3.  
      General techniques for the troubleshooting process
  2. General troubleshooting procedures
    1.  
      About general troubleshooting procedures
    2.  
      Viewing the Veritas Access log files
    3.  
      About event logs
    4.  
      About shell-activity logs
    5.  
      Setting the CIFS log level
    6.  
      Setting the NetBackup client log levels and debugging options
    7.  
      Retrieving and sending debugging information
    8.  
      Insufficient delay between two successive OpenStack commands may result in failure
  3. Monitoring Veritas Access
    1.  
      About monitoring Veritas Access operations
    2.  
      Monitoring processor activity
    3.  
      Generating CPU and device utilization reports
    4.  
      Monitoring network traffic
    5.  
      Exporting and displaying the network traffic details
  4. Common recovery procedures
    1.  
      About common recovery procedures
    2.  
      Restarting servers
    3. Bringing services online
      1.  
        Using the services command
    4.  
      Recovering from a non-graceful shutdown
    5.  
      Testing the network connectivity
    6.  
      Troubleshooting with traceroute
    7.  
      Using the traceroute command
    8.  
      Collecting the metasave image of a file system
    9.  
      Replacing an Ethernet interface card (online mode)
    10.  
      Replacing an Ethernet interface card (offline mode)
    11.  
      Replacing a Veritas Access node
    12.  
      Replacing a disk
    13. Speeding up replication
      1.  
        About synchronizing a replication job
      2.  
        Synchronizing an episodic replication job
    14.  
      Uninstalling a patch release or software upgrade
  5. Troubleshooting the Veritas Access cloud as a tier feature
    1.  
      Troubleshooting tips for cloud tiering
    2.  
      Issues when reading or writing data from the cloud tier
    3.  
      Log locations for checking for cloud tiering errors
  6. Troubleshooting Veritas Access installation and configuration issues
    1.  
      How to find the management console IP
    2.  
      Viewing the installation logs
    3.  
      Installation fails and does not complete
    4.  
      Excluding PCI IDs from the cluster
    5.  
      Cannot recover from root file system corruption
    6.  
      The storage disk list command returns nothing
  7. Troubleshooting the LTR upgrade
    1.  
      Locating the log files for troubleshooting the LTR upgrade
    2.  
      Troubleshooting pre-upgrade issues for LTR
    3.  
      Troubleshooting post-upgrade issues for LTR
  8. Troubleshooting Veritas Access CIFS issues
    1.  
      User access is denied on a CTDB directory share
  9. Troubleshooting Veritas Access GUI startup issues
    1.  
      Resolving GUI startup issues
  10.  
    Index

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)

  1. Add a new NIC card on the server.

    Note:

    The new NIC card should be online and searchable by the server.

  2. Run the # ip link show command to get the MAC address of the new NIC card.
  3. Run the following command on the Veritas Access node to replace the NIC card.
    # /opt/VRTSnas/scripts/net/net_device_add.sh -r
<old_mac_address> -w <new_mac_address>
  4. 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.

Example: 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