Troubleshooting Errors When Network Interfaces Appear Offline

Use the following steps to troubleshoot errors when network interfaces appear offline or do not show any link status.

If your deployment uses LACP bonding and the switch is already configured for LACP, it is common for some network interfaces to appear offline before LACP is configured on the HyperScale nodes. This behavior is expected for most switch models, and you can continue with network configuration despite the offline interfaces.

If an interface remains offline after LACP is configured on the HyperScale node, review the remaining sections in this topic.

Cabling

In some cases, the appliance may not be cabled correctly. Check for ports that are unexpectedly offline and verify the cabling based on your network topology.

For more information, see
Determining the Network Topology.

Network Switchport

In many environments, it is a common security practice to leave switch ports disabled until they are ready for use. As a result, the ports may still be offline on the switch.

This condition cannot be verified from the appliance. Your Network Administrator must check and enable the switch ports as required.

Incompatible SFP+ Modules

HyperScale X supports multiple connector and NIC types for 10GbE networking. By default, the appliance includes fiber channel modules with SFP+ based NICs that support optical or Twinax connections.

If you require RJ45 connections, contact your Commvault representative.

When troubleshooting connectivity issues, verify the following:

  • Optical fiber cabling:

    • Always use the provided SFP+ modules for HyperScale nodes. Do not replace them with third-party SFP+ modules.

    • Ensure that multimode fiber cabling (such as OM3 or OM4) is used together with multimode SFP+ modules on the switch side.

  • Direct Attach Copper (Twinax) cabling:

    • Verify that the Twinax cables meet the required specifications for HyperScale X.

      For more information, see the Supported Network Cables section in the
      Network Topology documentation.

    • Confirm that the Twinax cables are compatible with the switch, especially when using Cisco switches. Many Cisco switch models, such as Nexus, disable ports by default when unsupported third-party cables are connected. Your Network Administrator must verify and correct this configuration.

  • Incorrect NIC type:

    • If the appliance has an incorrect NIC type installed, contact your Commvault representative to coordinate a replacement.

Hardware Issues

Although uncommon, hardware issues can occur with new equipment. When a hardware issue is suspected, isolate the suspected component and test it using known good components.

When troubleshooting network connectivity, check the following four components:

  • Network Interface Card (NIC):

    Each HyperScale node contains two network cards. Swap cabling and SFP modules between the cards to isolate the faulty card. In some cases, a NIC may shift during shipping—re-seating the card in the chassis may resolve the issue.

  • SFP+ module(s):

    When using fiber, an SFP module is present on each end of the connection. Swap modules one at a time with known good modules to determine whether an SFP module is faulty.

  • Cable (fiber or Twinax):

    Replace the suspected cable with a known good cable to determine whether the cable is at fault.

  • Network switch port:

    Move the connection to a known working switch port to verify whether the original port is defective.

Hardware issues are less common than software or configuration issues. If the problem affects multiple nodes or components, revalidate the configuration, as the root cause is unlikely to be hardware-related.

×

Loading...