We have a location where our tech is reporting he cannot ghost image a computer lab (roughly 20 PCs). At that site we have a core of x670v-48x and x460-48p switches. Code is at 188.8.131.52 patch 1-5
As a test, our tech plugged all the computers into a dumb switch and was able to mulitcast fine. He cannot multicast when he's connected to the extreme stack. When he is connected to the extreme stack, the clients are able to join the ghost server, but when he hits send to send them their images, it just spins then fails.
I've done the old stare and compare with other sites where I have been told multi-casting works fine, and I can't see a configuration difference.
I guess I'm looking for suggestions on what to try / tweak / look for?
Hmm, that does sound like a client issue with Ghost. I'm assuming you are mirroring the client port to take a capture? Do you see the stream making it all the way to the client when trying to use Ghost?
That is the same tool we use, and in this case it works fine. It is just Ghost that fails, we have been trying to figure out if there differences between the the steams that could make one forward and the other not.
My latest WireShark captures seem to show everything working as expected but when I look at the logs on Ghost it is stuck in a re-transmit loop.
Ghost Log Level All 93736593 timed out after 1015 ticks
Wait(1000) timed out after 1016 ticks
93737609 Wait(1000) timed out after 1000 ticks
93738609 Wait(65) timed out after 78 ticks
93738687 Retransmit timeout
You could use this in the network to see if you are able to get a stream routed from the server to client VLANs. If you are, then it looks like the network side is good and any issues may be client side.