How do you set up multicasting with the K2000?
Ok, this is the last chance before I ditch the K2000 (and maybe the entire Kace product line).
We have close to 2000 computers throughout out school district. We're going to reimage them over the summer. When we set up a multicast session, it hangs on trying to connect to the session and just fails after it can't connect.
I know the K2000 multicast feature only supports PGM. we configured our 6500 router for PGM, but the problem seems to be on the 3750 layer 3 switches we have running in each schools MDF.
Our environment is broken up into 7 buildings. Each building has 3 wiring closets connected to an MDF. The MDF has the 3750 switch and the closets have 2960 switches connected to the 3750. Each building is broken up into 4 vlans (each closet is a vlan). The MDF connects to the HS.
has anyone with this type of setup been able to multicast with the K2000?
2 Comments
[ + ] Show comments
-
E-mail me and I might be able to help with a workaround. - nheyne 8 years ago
-
Will do. - mjreccoppa 8 years ago
-
This is a bigger issue than it is getting attention for. Come on Dell, step it up! - jjvillani 8 years ago
Answers (3)
Please log in to answer
Posted by:
chucksteel
8 years ago
We have also been disappointed in the multicast support of the K2000. Our switches do not support PGM at all so we are hoping that Dell implements IGMP in a future release. It doesn't solve your problem but I'm hoping that the more of us that raise this issue will result in a quicker implementation.
We have resorted to imaging machines in unicast batches, which works, but is obviously less than optimal.
Comments:
-
Thank you Chucksteel for your reply. I had everyone that does images limit their unicast imaging to 5-10 machines per batch, but when there are 2000 computers, it gets to be a bit much.
I really wish Dell would have mentioned that to us when we specifically asked about any limitations with multicasting. I've had to go back to MDT 2013 and WDS for multicasting, which is ridiculous. I'm not going to have 2 different deployment systems. - mjreccoppa 8 years ago
Posted by:
SMal.tmcc
8 years ago
I store my wim files on windows shares and we have unicast up to 120 machines at the same time at TMCC via Kace.
http://www.itninja.com/blog/view/wim-storage-freeing-up-space-on-your-k2000-if-you-are-using-wims-k2000-version-3-6
http://www.itninja.com/blog/view/wim-storage-freeing-up-space-on-your-k2000-if-you-are-using-wims-k2000-version-3-6
Posted by:
TheAustinDave
8 years ago
Hello,
The most common issue on multicast is the push speed of the data, leaving it set at 10 MBytes/sec will have nearly all systems fail as the network (real speed) is not able to deliver at that rate.
I would recommend setting to 4 or 5 MBytes/sec and test on a couple of machines. If during the testing you need to end a multicast session complete a Cntl-C on the system and terminate the batch so the K2000 knows to stop sending data to that IP address. The alternative is to wait for it to time-out which could take up to a couple of hours.
When running the multicast with the new setting the details of the session can be found at Settings>Appliance Logs>K2000 Server --> Mulitcast Log.
TheAustinDave
The most common issue on multicast is the push speed of the data, leaving it set at 10 MBytes/sec will have nearly all systems fail as the network (real speed) is not able to deliver at that rate.
I would recommend setting to 4 or 5 MBytes/sec and test on a couple of machines. If during the testing you need to end a multicast session complete a Cntl-C on the system and terminate the batch so the K2000 knows to stop sending data to that IP address. The alternative is to wait for it to time-out which could take up to a couple of hours.
When running the multicast with the new setting the details of the session can be found at Settings>Appliance Logs>K2000 Server --> Mulitcast Log.
TheAustinDave
