VMware Cloud Community
cheese2
Enthusiast
Enthusiast
Jump to solution

VCSA 6.5 loses IP address after reboot

I was investigating the new HA feature for the 6.5 Appliance in our dev/test environment and have run into a weird problem.  Somewhere in attempting to do a manual deployment the primary appliance had its primary network interface (eth0) deleted.  The second vnic that you add for the HA network (eth1) was retained.  I have re-added an eth0 interface however this interface won't keep its IP configuration across reboots.  I am using the configuration tool in /opt/VMware/share/vami/vami_config_net to set things up, and everything appears to go smoothly.  However after a reboot I notice the configuration file it created in /etc/system/network is renamed from 10-eth0.network to 10-eth0.network.manual and the eth0 interface is once again unconfigured.  The contents of the file are still correct, but the interface is down.

What is renaming the 10-eth0.network file?  How do I stop it?  How do I get this thing to remember settings across a reboot?  Any ideas?

Thanks.

Reply
0 Kudos
1 Solution

Accepted Solutions
cheese2
Enthusiast
Enthusiast
Jump to solution

Found the answer in this thread:

VCSA HA eth0 and services dont start after reboot

The VCHA service had been partially configured and that is what shuts down the eth0 interface and renames the file.  Running destroy-vcha stops this behaviour.

View solution in original post

Reply
0 Kudos
1 Reply
cheese2
Enthusiast
Enthusiast
Jump to solution

Found the answer in this thread:

VCSA HA eth0 and services dont start after reboot

The VCHA service had been partially configured and that is what shuts down the eth0 interface and renames the file.  Running destroy-vcha stops this behaviour.

Reply
0 Kudos