Rule 5: No Early Career Advice. If i enable multicast globally, then i start imaging machines, they all just start imaging when i press start, there is no session or wait to join session etc. Not sure if it was our environment or not, but I'm almost certain Microsoft said those were expected speeds. My config above seems to work for anyone else having this issue on hp switches. The ghostcast session keeps going.
Below are some screen shots of the imaging. Probably true since our old switch didn't have multicast turned on either, but it still imaged using multicast faster. None of the hardware has changed, I just went from using 10. I'm no network expert and in my situation ironing out al the wrinkles in my network would be hell on earth and an extremely long project one that I can never justify for the sake of imaging. I will keep you posted. The A Series are the rebranded H3C read: 3Com and I've been reviewing.
Rule 4: No Low Quality Posts. This is an old article, but it shows how Ghost communicates over the network in unicast and multicast. Port mirroring is required to see any traffic that is not broadcast on a switched network. Why do you want multicast to work when unicast to multiple clients works fine? Throw some of the machines, and maybe a printer or something, on an unmanaged switch. Norton Ghost takes a long time to save and load an image to and from the server. Thanks to all for your input.
Each transmission can be run only as fast as the slowest client. The times are not consistent. Technically, multicast can use whatever protocol you want. Of course it will slow down if the hard disks cannot sustain the initial rate. Is there a step by step troubleshoot procedure? Norton Ghost rides the network layer or stack created.
We don't check the modqueue very often. Best regards, Peter Hi Peter; I wanted to get on the forum and thank you for a quick reply, and give the group some of my preliminary findings. The clients we're deploying to also should have no problems at all. That's where I would start. Your solution will depend on the complexity, layout of your network, and the frequency of with which you will be imaging systems. In the case of a single switch, that's all you need to to. We were all n00bs at one point well we still are if we are honest.
If you see a drastic improvement, it's probably a setting on the switch es. Fortunately, I am working in a school environment, not a commercial or production environment, so my labs can afford downtime during the summer. Nothing has changed server side, and if you look into using GhostCast there is pretty much no configurations that can be done. We are still doing more sharking. Sometimes it will use the universal driver and not have a problem.
Read the steps in numerical sequence. Some switches just do broadcast for multicast or limit amount of broadcast. Hope this help you understand the differences. Any suggestions on why the speed is so slow. I am not coming here to bitch. Running two concurrent unicast or multicast sessions, well that is a different story.
We have no access layer, just a core and the edge switch. The vlan variable is required when you configure the traffic filter entry. There are no complicated commands required to make the multicast work. That is, the entire transmission will be slow if there is one slow client. This topic has been discussed at length, please use the search feature.
Ignore the 5 cables plugged into the old switch as that was just for testing. If you need assistance with the information contained in this document, please consult your networking documentation or your Information Technology department. It was already on core switch 1. Layer 2 multicast works fine. If this is the case, like Ive stated in previous posts, its a horrible way to deliver data which should be sent complete and intact.