Hi,
I configured in our test environment a VCSA 6.5 HA deployment. All three node were up and fine, vcenter showed them green at HA status. First problem: After a simultaneous reboot of all three machines, the eth0 interface of master and passive node stays down. Second problem: even after configuring eth0 manually and successfully regaining IP connectivity on public interface, the vcsa services can't be started:
Command> service-control --status
Running:
vmware-statsmonitor vmware-vcha vmware-vmon
Stopped:
applmgmt lwsmd pschealth vmafdd vmcad vmcam vmdird vmdnsd vmonapi vmware-cis-license vmware-cm vmware-content-library vmware-eam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-perfcharts vmware-psc-client vmware-rbd-watchdog vmware-rhttpproxy vmware-sca vmware-sps vmware-sts-idmd vmware-stsd vmware-updatemgr vmware-vapi-endpoint vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsphere-client vsphere-ui
Command> service-control --start --all
Perform start operation. vmon_profile=HACore, svc_names=None, include_coreossvcs=True, include_leafossvcs=False
2017-01-13T13:30:25.695Z Running command: ['/usr/bin/systemctl', 'is-enabled', u'lwsmd']
2017-01-13T13:30:25.698Z Done running command
Service lwsmd startup type is not automatic. Skip
2017-01-13T13:30:25.701Z Running command: ['/usr/bin/systemctl', 'is-enabled', u'vmafdd']
2017-01-13T13:30:25.703Z Done running command
Service vmafdd startup type is not automatic. Skip
2017-01-13T13:30:25.705Z Running command: ['/usr/bin/systemctl', 'is-enabled', u'vmdird']
2017-01-13T13:30:25.707Z Done running command
Service vmdird startup type is not automatic. Skip
2017-01-13T13:30:25.710Z Running command: ['/usr/bin/systemctl', 'is-enabled', u'vmcad']
2017-01-13T13:30:25.712Z Done running command
Service vmcad startup type is not automatic. Skip
2017-01-13T13:30:25.714Z Running command: ['/usr/bin/systemctl', 'is-enabled', u'vmware-sts-idmd']
2017-01-13T13:30:25.716Z Done running command
Service vmware-sts-idmd startup type is not automatic. Skip
2017-01-13T13:30:25.719Z Running command: ['/usr/bin/systemctl', 'is-enabled', u'vmware-stsd']
2017-01-13T13:30:25.721Z Done running command
Service vmware-stsd startup type is not automatic. Skip
2017-01-13T13:30:25.723Z Running command: ['/usr/bin/systemctl', 'is-enabled', u'vmdnsd']
2017-01-13T13:30:25.726Z Done running command
Service vmdnsd startup type is not automatic. Skip
2017-01-13T13:30:25.728Z Running command: ['/usr/bin/systemctl', 'is-enabled', u'vmware-psc-client']
2017-01-13T13:30:25.730Z Done running command
Service vmware-psc-client startup type is not automatic. Skip
Successfully started vmon services. Profile HACore.
/etc/systemd/network/10-eth0.network.manual:
[Match]
Name=eth0
[Network]
Gateway=10.45.128.1
Address=10.45.128.32/24
DHCP=no
[DHCP]
UseDNS=false
/etc/systemd/network/10-eth1.network
[Match]
Name=eth1
[Network]
Address=192.168.64.204/23
DHCP=no
[DHCP]
UseDNS=false
Now I shut the passive node down to get active node and witness node up again but the problems still persist. Pinging between active and witness node HA interfaces works. Why are both eth0 down after boot and why cant i start the services?
edit:
networkctl status eth0
● 2: eth0
Link File: /usr/lib/systemd/network/99-default.link
Network File: n/a
Type: ether
State: routable (unmanaged)
Path: pci-0000:03:00.0
Driver: vmxnet3
Vendor: VMware
Model: VMXNET3 Ethernet Controller
HW Address: 00:0c:29:7e:7e:08 (VMware, Inc.)
MTU: 1500
Address: 10.45.128.32
Gateway: 10.45.128.1 (ICANN, IANA Department)
Network file n/a and State: unmanged??? But I have file /etc/systemd/network/10-eth0.network.manual which was created by vcenter. How can I fix this?