WDS/MDT change of NIC

[the_quick]

Hi All

 

We have our WDS/MDT as Vmware vm, I wanted to upgrade NIC from E1000 to vmxnet3. Keeping same IP config. As soon as we do it and we try to build a machine over PXE it takes few attempts to connect to WDS to pull initial image. On E1000 it works flawlessly.

Another thing we tried is adding another E1000 nic and switching server to this (same IP again) and problem occurs. Another weird thing is , on both network cards it works fine on same vlan as server, but problem shows on a different vlans (a different subnet)

So just wonder if there is any MAC association in WDS or anywhere else that can cause it?

 

Or is there another explanation, I really hope I described the problem clearly enough, but just in case more on example

 

Network card on server: e1000

building machine on server vlan - fine

building machine on classroom vlan - fine

 

Network card on the server: vmxnet3

building machine on server vlan - fine

building machine on classroom vlan - takes few attempts to connect to the server

 

Network card on the server: new e1000

building machine on server vlan - fine

building machine on classroom vlan - takes few attempts to connect to the server

 

Each time only one nic is enabled

 

Anyone seen this problem?

Thanks in advance

[Davit2005]

Not seen that problem.

 

What switch are you using for your core/layer3 switch? have you just got the one NIC in the WDS server at any one time enabled?

Edited August 7, 2020 by Davit2005

[jtotheb]

Network card on the server: vmxnet3

building machine on server vlan - fine

building machine on classroom vlan - takes few attempts to connect to the server

 

Does it take a few attempts to connect to the server every time? E.g. once a machine in the classroom VLAN has started to PXE boot, if you restart the machine will it then PXE boot again straight away or does it start to require a few attempts to connect again?

[the_quick]

Davit, switch is HP A5500 and always just 1 nic enabled

 

jtotheb I will try that, need to ask my technician if he tried few times.

[jtotheb]

jtotheb I will try that, need to ask my technician if he tried few times.

 

Cool, I'd be interested to know. The reason I ask is that in the same VLAN the client is going to find the PXE boot source via a broadcast. When the client is in a different VLAN it's going to be directed by the L3 device somehow to the PXE boot source (in Cisco land it'd be an "IP Helper" but I'm going to assume HP have something very similar). I'm wondering if the switch is having to rebuild a resolution table entry which is causing the initial time out.

[the_quick]

Hi

 

Each PXE boot we do on same machine, will show same problem if we change NIC, multiple restarts do not change anything. Really weird problem