Troubleshooting Errors When You are Unable to Ping the Gateway or the Other Nodes

Use the following steps to resolve communication issues that prevent successful ping operations to the gateway or other nodes.

Interface Misconfiguration

Ensure that the network interface on the node is functioning correctly. You can validate this by attempting to ping the node’s own IP address. This simple sanity check helps confirm that the network stack on the node is configured and operating as expected.

Duplicate IP Addresses

If the IP address assigned to the HyperScale node is already in use, the interface may fail to come online correctly. Run the following command to check for duplicate IP address issues:

journalctl -xe | grep ifup

If the interface fails to come online due to a duplicate IP address, you will see an error similar to the one shown in the following example:

Troubleshooting Errors When You are Unable to Ping the Gateway or the Other Nodes (1)

To resolve this issue, assign a new IP address to one of the affected devices. The error message includes a MAC address to help your Network Administrator identify the device using the duplicate IP address.

Setting Up the DNS

Incorrect Port Mode

When configuring the network switch, ports can be set to either trunk mode or access mode (sometimes referred to as tagged and untagged). This configuration determines how traffic is routed to the appropriate VLAN.

For HyperScale installations, network ports must be configured as access (untagged) ports. If a port is incorrectly configured as a trunk port, ping tests between HyperScale nodes or to the gateway may fail. Your Network Administrator must verify and correct the port configuration.

Incorrect VLAN

If the switch is configured with an incorrect VLAN, the nodes may be unable to ping the gateway but might still be able to ping other HyperScale nodes using the data protection IP addresses. Your Network Administrator should verify the switch configuration and ensure that the correct VLAN is applied.

ICMP (ping) Blocked

In some cases, ICMP (the protocol used by the ping command) may be blocked on the gateway. This scenario is common when the gateway is a firewall device or when HyperScale is deployed in a high-security environment.

To complete the installation, you may need to allow ICMP traffic from the HyperScale nodes for the duration of the installation. If your security policies prevent this, contact your Commvault representative for assistance.

×

Loading...