• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1193
  • Last Modified:

Routing PXE traffic between Hypervisors

Hi

I've got two Hyper-V servers on the same subnet, connected via a switch. I've successfully routed traffic between them using RRAS including DHCP, so a DC on Hyper1 will send IP addresses to a VM on Hyper2.

On Hyper1 there is an Altiris Deployment Server for providing automated machine builds over PXE. If I create a new VM on Hyper1 with a legacy network adapter I can boot it through to the WinPE environment and deploy an image to it. If I do the same on Hyper2 the new VM will PXE boot but halfway through downloading the boot image it generates a 0xc0000001 error, "inaccessible boot device". The VMs are identical in machine configuration, so I think this may be related to TFTP routing. I have disabled multicasting (MTFTP) on the Altiris DS and this already resolved a PXE-E32 error. I've temporarily suspended the firewalls on each machine and have confirmed that these are not interrupting the traffic.

Can anyone recommend how I should setup TFTP to route from one Hypervisor to the other?

Thanks

AdoBeebo
0
AdoBeebo
Asked:
AdoBeebo
1 Solution
 
pwindellCommented:
I've got two  Hyper-V servers on the same subnet, connected via a switch. I've  successfully routed traffic between them using RRAS including DHCP, so a  DC on Hyper1 will send IP addresses to a VM on Hyper2.
-------------------------------------------------

If they are on the same subnet then there is no routing.  Therefore you would not have done what you think you done.  DHCP would have already did what it is doing and RRAS would have had nothing to do with it.

----------------------------------------------------Can anyone recommend how I should setup TFTP to route from one Hypervisor to the other?
-----------------------------------------------------

There is no routing.  They are on the same subnet.  Each HyperV machine is viewed as a Switch,...the VMs are then seen as Hosts plugged into the Switch.  It is that simple.

I don't know exactly where the problem is,...but I know where it is not,...you are looking in the wrong place.  TFTP is connectionless,...it has no error checking (as opposed to FTP which does),...if there are any errors in the transmission it will fail.  An image must be perfect,...just one single "bit" lost leaves it corrupt.


0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now