Networking error

Newbie080643 Lv1Posted 2026-Jun-18 19:27

Dear forum members,
I recently installed HCI 6.11.3 on physical server, I keeped the default ip address and subnet in the management interface (physical and its name is eth2),
and i accessed the server GUI via 10.250.0.7 and i created 2 more subinterfaces in the eth2 (eth2.2320,eth2.2330), then i changed the overlay interface from eth0 (down interface) to the subinterface eth2.2320, the management IP has stopped responding, When i tried modifying the network settings from the server console it does not save this changes, i tried to restart the server and when i tried to access the 'network settings' in the console i am getting this error

what can i do please ?

By solving this question, you may help 874 user(s).

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Humayun Ahmed Lv4Posted 2026-Jun-19 12:03
  
it sounds like the issue occurred after changing the Overlay Network from the default eth0 to a VLAN sub-interface (eth2.2320). This is a common cause of management connectivity problems if the network design or interface assignment isn't complete.
Prosi Lv4Posted 2026-Jun-22 12:43
  
HI,
- Access the console.
- Restore the original overlay interface (eth0) via the CLI.
- Restart the network service.
- If the configuration database is inaccessible and this is a new deployment, reinstalling HCI may be quicker than troubleshooting a corrupted network configuration.
admin Posted 2026-Jun-26 09:39
  
  
Root Cause Analysis

The management IP stopped responding because you violated a fundamental network configuration rule for HCI. The management interface IPs of all hosts must be on the same subnet, and this subnet cannot be shared with other interfaces of the node. By creating sub-interfaces (eth2.2320, eth2.2330) on the same physical NIC (eth2) as your management interface and then assigning the overlay network role to one of them, you caused a subnet conflict. The management interface and the overlay network interface are now on the same physical interface, which is not permitted without proper VLAN isolation.

The error "Failed to obtain the interface information, error communicating with node" on the console is a symptom of the cluster communication failure caused by this misconfiguration.

Resolution Steps

Since the console network configuration is failing, you will need to revert the changes by directly accessing the server. The goal is to restore the overlay network interface to a different physical port, freeing the management interface from the conflict.

Step 1: Free Up the Overlay Network Interface
You must first move the overlay network interface role away from the conflicting sub-interface. According to the knowledge base, you can temporarily switch the Overlay Network Interface to another available interface, or even use the same interface as the management network if no other interface is available.

1. Connect a monitor and keyboard to the physical server's VGA port to access the console directly.
2. Log in to the server's backend command-line interface.
3. You need to temporarily reassign the overlay network interface. If you have another available physical NIC (e.g., eth1), you can use it. If not, you can temporarily multiplex it with the management interface on the base `eth2` interface (not a subinterface) to resolve the immediate conflict. This is a standard troubleshooting step to free up the intended interface for reconfiguration.

Step 2: Reconfigure the Management Interface
Once the overlay network role is moved off the conflicting sub-interface, the management network on `eth2` should recover. You can then properly configure the network.
For a proper interface multiplexing setup in HCI 6.11.3, which supports this feature, you must follow a specific procedure using VLAN sub-interfaces for network isolation.

1. The multiplexing interface must be a 10GB interface, and it is recommended to use an aggregate interface.
2. You must use VLAN sub-interfaces for VLAN isolation of different network planes. Navigate to Nodes > Physical Interfaces and click Add Multiple VLAN Subinterfaces to create them with the correct VLAN IDs.
3. After creating the VLAN sub-interfaces, you then switch the management communication interface and overlay network interface to their respective sub-interfaces. This is done under Nodes > Communication Interfaces by clicking on Management Interface and Overlay Network Interface to configure them.

Crucial Precaution: Before making these changes, ensure the physical switch port connected to your HCI server's `eth2` is configured as a trunk port and that the VLANs you plan to use (e.g., 2320, 2330) are allowed on that trunk. Failure to do so will result in a loss of connectivity.

If you are unable to resolve the issue from the command line, as a last resort for a new deployment, you can restore the system to factory defaults via System > System Backup and Restore > Restore to Factory Defaults > Reset settings of all clustered nodes. This will erase all configuration and allow you to start over.

I Can Help:

Change

Board Leaders

YerkoUm...

Weekly Sharers

Eduardo...

Weekly Questioners