Forum Discussion
Hyper-V servers DHCP
Found the culprit!!!
First of all, When installing Hyper-V and using an ISCSI LUNs, the MSiSCSI services is throwing DHCP discover packets when it start. After it finds the NIC that uses the iSCSI targets it uses that NIC and doesn't attempt to search for DHCP until the next reboot \ restart of the service.
Apparently when installing SCVMM server and SCVMM agent this is what happens: On the SCVMM server the iSCSI initiator service is installed and starts running (like the Hyper-V) which causes the first DHCP discover packets. Than, On all the server that SCVMMAgent service is installed, a DHCP discover packet is broadcasted repeatedly in a constant interval for each server.
The solution: https://download.microsoft.com/download/A/E/9/AE91DEA1-66D9-417C-ADE4-92D824B871AF/uGuide.doc
Although this is for server 2008 and 2003, when Creating the MSiSNS Key and adding the DHCPRetries DWORD with the value 0, it causes iSCSI to stop sending DHCP discover packets.Hope this helps anyone.
Rahamim.
Found the culprit!!!
First of all, When installing Hyper-V and using an ISCSI LUNs, the MSiSCSI services is throwing DHCP discover packets when it start. After it finds the NIC that uses the iSCSI targets it uses that NIC and doesn't attempt to search for DHCP until the next reboot \ restart of the service.
Apparently when installing SCVMM server and SCVMM agent this is what happens: On the SCVMM server the iSCSI initiator service is installed and starts running (like the Hyper-V) which causes the first DHCP discover packets. Than, On all the server that SCVMMAgent service is installed, a DHCP discover packet is broadcasted repeatedly in a constant interval for each server.
The solution: https://download.microsoft.com/download/A/E/9/AE91DEA1-66D9-417C-ADE4-92D824B871AF/uGuide.doc
Although this is for server 2008 and 2003, when Creating the MSiSNS Key and adding the DHCPRetries DWORD with the value 0, it causes iSCSI to stop sending DHCP discover packets.
Hope this helps anyone.
Rahamim.