Snap Deploy 2 - PXE works, but Snap Deploy gets 169 IP
I can boot a computer with PXE, but when Snap Deploy loads, it doesn't get a proper IP and gets a 169 address if left to its own devices. This is obviously a bit longwidned, how can I get it correctly get an IP?
The PC I am booting from has a Broadcom NIC and our network has Cisco switches.
We're having the same problem. But the solution above does not really help. Our DHCP server is not the problem as it gives out the correct addresses on other desktops. We just switched to a new desktop with a ful gigabit network adapter and this seems to be the issue. Is there some sort of patch for version 2.0 that allows a pxe boot to this type of adapter?
Hi,
Telling me to just do it manually isn't a solution, it's workaround and not a very good one. Since then, I've upgraded to Snap Deploy 3 and am getting the same problem. As Merit IT said, the DHCP server is working fine without problems. Is there a solution for this for Snap Deploy 3?
I am having the same issues and getting a 169 address assigned to the target PC on selecting the Acronis Snap Deploy Option.
I am using Snap Deploy 3.0, but the same issue persists. the DHCP server is not the same as PXE server.
Manual option works, but is not a solution as the deployment scale is very large.
Hello,
It appears to be a common issue, and it's important for us to determine the exact cause in this case. Unfortunately, we do not have a patch or fix to this issue, but please be sure that we will do our best to resolve the issue. Could you please do the following:
1. If your PXE server is installed on the same machine with DHCP server.
To resolve the issue the DHCP server should be configured with the option 60. This option tells the client to make a boot information negotiation layer (BINL) request to the same server to retrieve boot information.
Add to the DHCP server option 60: "Client Identifier" with string value "PXE Client". This can be done as follows:
Hit Start -> Run and type netsh
netsh>dhcp
netsh>dhcp>server \\[server_machine_name] or [IP address]
netsh dhcp>add optiondef 60 PXEClient STRING 0 comment="Option added for PXE support"
netsh dhcp>set optionvalue 60 STRING PXEClient
2. If this is not the cause:
Check if the bootable components are uploaded to the Acronis PXE Server - see:
- Windows 2000/2003, Windows XP: \Documents and Settings\All Users\Application Data\Acronis\PXEServer\Bootmenu
- Windows Vista, Windows 7, Windows Server 2008: \ProgramData\Acronis\PXEServer\Bootmenu
And collect the following information:
- Log files from the computer where Acronis PXE Server is installed:
- Documents and Settings\All Users\Application Data\Acronis\FileServer\Logs
- Documents and Settings\All Users\Application Data\Acronis\PXEServer\Logs
- Acronis Information File from the computer where Acronis PXE Server is installed;
- Information about where DHCP server is installed;
- Exact model of the network card;
- Error message that is received after trying to boot via PXE;
- PCAP logs gathered from the PXE Server machine at the time of boot failure. See Collecting PCAP Logs.
Then submit a request for technical support. Attach all the collected files and information to your request along with the step-by-step description of the actions taken before the issue appears and the link to this thread. Then please provide me with the case number you receive from our system, so I can pick it up and speed up the process. We will do our best to investigate the problem and provide you with a solution.
Additionally to this, you are welcome to ask me any other questions concerning Acronis, and I will assist you further.
Regards,
Alexander, Thanks for the detailed response. Appreciate the efforts to help out. We have managed to sort out the issue of getting a 169 address.
Root cause - The ethernet switch port where the target PC is connected flaps before the Acronis Loader starts up. The Acronis kernel loads up pretty fast and requests a new DHCP address, but the switch port is still doing an auto-negotiation of the port settings. The DHCP request in the meantime has failed and the target PC (understandably) has assigned itself the 169.. address.
This behaviour was noticed on some old generation Cisco CatOS switches but not on Cisco IOS based switches.
Solution: When configuring the PXE Server, we loaded the desired components and in the network settings, put in the IP address of the Deploy server and put in a DELAY of 25 sec (instead of the Default 5 sec) to search for the OS deploy server. The link recovers from auto-neg issues during this time. :-)
Thanks Ravi. This is most helpful. We experienced the exact same problem for what I determined the exact same reason (we have older Cisco CAT switches). I spent weeks working with Acronis engineers on the issue, and never thought to try extending the search time as a solution.
That said, they (Acronis) eventually modified the Acronis boot OS to compensate, and sent us the new files so it would behave differently. Now when Snap-Deploy misses it's chance at getting a DHCP address, it refreshes the request once the OS has loaded and picks up an IP from DHCP just as the GUI displays the network information window. It's ugly, because the GUI shows a blank (0.0.0.0) or 169.x IP address, yet you have full network connectivity and it can see the deployment server. But it works.
We tested other options like disabling "Port-fast", fixing the auto-neg port parameters to 100Mbps full-duplex .. but nothing worked, except introducing a delay. Yet to finalize, whether the 25 secs can be brought down further :-)
Hello all,
Ravi, thank you very much for sharing the solution with us! Yes, we have experienced similar issues in the past, and we just reconfigured the bootable component to load with the delay for each particular case.
Anyway, I'm very glad that the product works for you now.
Daniel, yes, the IP address and network settings will be displayed incorrectly in case if the refresh is set up, because GUI obtains the settings at very startup and does not change them after refresh. Anyway, you're safe to ignore this behavior.
Please let me know if you need any further assistance.
Regards,
didn´t worked for me.
DHCP is in a home router
Windows Server with only role Snap Deploy 3
When PXE boot it got a DHCP IP Address, when Snap Deploy runs (I gave 60 seconds to preload) it got 169.x.x.x address.
If I force IP from DHCP range it didn´t connect to Snap Deploy server.
Why????????????????
didn't worked for me too
my status of my configuration is
DHCP: not used
connection not connected.
why????
i turned my delay to 120 sec. but didn't worked . . .