Switch setup for laptop trolley

[X-13]

I'm guessing this goes in "Wired Networks"...

 

We've got a few Cisco Catalyst 2950's knocking about that I'm sorting for our laptop trollies [2x16 laptops]

 

I've had to do a factory reset as no-one knows the password so I can't set them up with a new IP. Everything has seemingly gone through properly, I can connect to the web interface and when a pre-build computer is attached to one it can still access the network, albeit slowly.

 

However, when I try to PxE boot our laptops through the switch the port becomes "disabled" on the web interface and re-enables after a little while. The laptop itself can download the boot image perfectly fine, but is assigned an I.P from the 169.254.x.x range and then doesn't pick up the domain. [The option to manually input the domain and Windows Key is disabled.]

 

 

Is there something I've forgotten to do or is this an exercise in futility?

[jamesreedersmith]

Are you uni casting or multi casting (do the swithes support what you are trying to do - some of the older 2900 and 2950's didnt support multi casting.

[X-13]

Erm... I suddenly feel very stupid.

 

I'm guessing unicasting. Purely due to the fact the laptops should only be connecting to our server to get OS files.

[Ric_]

Maybe the ports aren't negotiating quick enough... maybe try putting one into Portfast mode?

[glennda]

Erm... I suddenly feel very stupid.

 

I'm guessing unicasting. Purely due to the fact the laptops should only be connecting to our server to get OS files.

 

What imaging software are you using? How many machines are you trying to image too?

[X-13]

What imaging software are you using? How many machines are you trying to image too?

 

WDS and I was only trying to build one laptop as a test to see if the switch was working properly.

[glennda]

WDS and I was only trying to build one laptop as a test to see if the switch was working properly.

 

Then I guess its uni-casting as i think you have to specify Multicasting in WDS.

 

The difference between them is Uni-casting is more direct and ok for a couple of machines i.e each packet is sent to each machine receive the image

 

multi-casting it broadcasts the packets to the entire lan and its up to a machine to accept them if it is part of the process.

[X-13]

Maybe the ports aren't negotiating quick enough... maybe try putting one into Portfast mode?

 

I've had a look on the web interface and there's no option for portfast.

 

I can connect to it with PuTTY, but I'm not sure of what commands I need to use.

[Psymon]

This could be that you do not have the correct NIC driver in the install.wim image - so the boot.wim is happy, until the machine gets to the OOBE and realises there is no NIC driver. Check device manager after a failed install.

 

Also you could try this laptop using any other switch (that you know works) - this will tell you wether it's the switch, or the machine.

[X-13]

This could be that you do not have the correct NIC driver in the install.wim image - so the boot.wim is happy, until the machine gets to the OOBE and realises there is no NIC driver. Check device manager after a failed install.

 

Also you could try this laptop using any other switch (that you know works) - this will tell you wether it's the switch, or the machine.

 

I've imported the drivers, but it isn't allowing me to use them in a build disk [THANKS RM!]... However, it built fully [Without any serious issues] when connected to the network socket on the wall...

 

I also tried it on another switch. Same model, same settings... Same problem.

 

The port is set to auto/auto [speed/duplex respectively] which becomes 100/full when the machine is connected but off.

 

When turned on, it goes orange [error disabled] but comes back after a few seconds.

 

 

I may need to have a word with our LEA to see if they'll tell me which arcane spells they used to set it up last time...

[Ric_]

@X-13 It won't be driver related as the DHCP lease is negotiated by the PXE boot (before the OS loads). If you have no config on the switch, get up a console in enable mode and run the following:

 

wr erase
reload

 

This WILL wipe the switch config!!!!

 

You should then pick a port (say the first one) and again use the console for the following (assuming 100Mbps ports):

 

conf t
interface FastEthernet0/1
spanning-tree portfast

 

then press ctrl-z and type

wr mem

 

Cross your fingers and see if it works - it does look like the it is timing out getting a DHCP lease.

[X-13]

@Ric_ you're the best.

 

That worked and it's going through fine now!

 

Is there a way to do it for all ports or is it a case of doing each one manually?

 

 

Le EDIT: Nevermind, figured it out.

 

interface range fa0/1 - 23

Edited December 3, 2012 by X-13