Enterprise Software Thread, Upgraded Network Infrastructure, Now Can't Image Computers in Technical; Hello,
We recently upgraded our physical network infrastructure from Cisco Switches to Aruba S2500 switches. Now, this has upgraded us ...
4th April 2013, 08:13 PM #1
- Rep Power
Upgraded Network Infrastructure, Now Can't Image Computers
We recently upgraded our physical network infrastructure from Cisco Switches to Aruba S2500 switches. Now, this has upgraded us so that most of our network is now a full 1Gbps from the server to the workstation. However, I have noticed that when I try and image a machine (using WDS with MDT here...soon SCCM once I have some other problems figured out), the progress bar gets stuck at 5% and doesn't finish downloading the image. Also, I have noticed systems taking longer to PXE boot whereas it used to take maybe a few seconds to get the PXE response, it now seems to take at least 30 seconds or more. In fact, I have even had some systems NOT be able to receive the PXE response at all. I know it is probably something simple that we have to enable on the new Aruba switches, but don't know what setting it would be (plus, trying to learn Aruba's OS).
Anyone have any ideas?
Thanks in Advance,
4th April 2013, 08:30 PM #2
Some NICs have terrible PXE boot implementations, ADMtek, Nvidia especially.
Try changing the port speed at 100Mb as a test to see if WDS downloads the initial PXE boot quicker. Some machines I've imaged need dropping to 100Mb for boot and back to 1Gb one WDS starts to load for the image deployment.
If it's multicasting that the issue then check what the igmp settings are, slow DHCP is probably due to spanning tree, set clients to edge ports or use rtsp for the edge swiches.
19th September 2013, 12:45 PM #3
- Rep Power
We found that some implementations of spanning tree broke pxe booting. It would take ages or just not happen.
19th September 2013, 01:46 PM #4
Do you use vlan's? The Aruba S2500's look very much like the Juniper EX3300's that I use.
19th September 2013, 02:21 PM #5
in ciscoland, seting ports as "portfast" stops them sending/recivind spanning tree BDU information. this means the port comes up and negotiates client links much faster.
We found PXE DHCP failed on switches without portfast.
By GrumbleDook in forum General Chat
Last Post: 6th June 2011, 09:21 AM
By tech_guy in forum General Chat
Last Post: 15th October 2010, 10:15 AM
By bozallen in forum Wireless Networks
Last Post: 10th May 2010, 04:49 PM
By OverWorked in forum MIS Systems
Last Post: 21st January 2010, 02:35 PM
By amvc in forum Wireless Networks
Last Post: 29th August 2008, 01:09 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)