Issues with Network adapters during build ESXi 7.0U3g

[JRay888]

Im trying to create a weasel script that deletes the current vSwitch and recreates it to what we need. Im testing this build on an ESXi host. So nested ESXi, but only durring testing.

While the machine is building I can see when it starts to ping and once it gets to the KS file it drops communication. So I go to the console. Remove the uplinks from Configure Management Network and then re-add the same uplinks then it starts to ping again. Then I can log into ESXi and all is fine. What is not configured right on first install?

Side Question.... Why hasnt VMWare released 7.0U3i yet in iso yet?

echo '####### Delete existing Mgmt nic and vswitch '

/sbin/esxcli network ip interface remove -i vmk0

/sbin/esxcli network vswitch standard portgroup remove -p "Management Network" -v vSwitch0

/sbin/esxcli network vswitch standard remove -v vSwitch0

echo '####### Define virtual switches '

/sbin/esxcli network vswitch standard add -v DREN

/sbin/esxcli network vswitch standard uplink add -v DREN -u vmnic0

/sbin/esxcli network vswitch standard uplink add -v DREN -u vmnic1

/sbin/esxcli network vswitch standard portgroup add -p B412_WinServer -v DREN

/sbin/esxcli network vswitch standard portgroup add -p B1004_WinServer -v DREN

/sbin/esxcli network vswitch standard portgroup add -p WDS_Imaging -v DREN

/sbin/esxcli network vswitch standard portgroup add -p B412_LinServer -v DREN

/sbin/esxcli network vswitch standard portgroup add -p B412_VirtUsers -v DREN

/sbin/esxcli network vswitch standard portgroup add -p Mgmt -v DREN

echo '####### Define Mgmt nic '

/sbin/esxcli network ip interface add -i vmk0 -p Mgmt

/sbin/esxcli network ip interface ipv4 set -i vmk0 -I 192.168.1.1 -N 255.255.255.0 -t static

/sbin/esxcli network ip route ipv4 add -n default -g 192.168.1.254

/sbin/esxcli network ip interface tag add -i vmk0 -t VMotion

/sbin/esxcli network ip interface tag add -i vmk0 -t faultToleranceLogging

/sbin/esxcli network ip interface tag add -i vmk0 -t vSphereReplication

/sbin/esxcli network ip interface tag add -i vmk0 -t vSphereReplicationNFC

/sbin/esxcli network ip interface tag add -i vmk0 -t vSphereProvisioning

esxcli network vswitch standard policy failover set -a vmnic0,vmnic1 -v DREN

esxcli network vswitch standard portgroup policy failover set -a vmnic0,vmnic1 -p Mgmt

esxcli network vswitch standard policy failover set -l iphash -v DREN

esxcli network vswitch standard portgroup policy failover set -l iphash -p Mgmt

[scott28tt]

I have reported your post to the moderators, asking them to move it to the ESXi area.

[JRay888]

thank you, sorry about that

[JRay888]

[JRay888]

Still having this issue, anyone have any ideas?

[jcallenrh]

I am using the nested content library and experiencing this.

Haven't got a chance to pin down the specific version but 7u3 to 8u1 seem to be experiencing a networking problem after:

esxcli network ip interface remove -i vmk0

Even if you completely recreate vswitches and vmkernel int traffic will not pass.

The only resolution I have found is to use the dcui and reset networking (or /sbin/firmwareConfig.py --reset)