locked
Multicasting Using Virtual Distribution Point RRS feed

  • Question

  • For a while now I have been troubleshooting various problems related to multicasting with SCCM 2012 r2. My most recent hurdle has been overcoming awful multicast stream speeds. Production Distribution Points are Windows Server 2012 r2 virtualized on ESX 5.5 using the VMXNET3 network adapter. Networking (so far) has not been able to find any errors or packet loss on the network, so I am thinking maybe the Virtualization layer could be cause of my headaches. I stood up a physical Distribution Point in same network as some physical clients. From testing with the physical Distribution Point the speeds have definitely increased. Speeds were maxing out at about 20 Mbps once all of the client machines joined the multicast stream. I am more confident now that something in the virtualization layer is causing the problem, maybe the virtual switch? I just don’t know. Does anyone out there have any thoughts or suggestions from where to go from here? What to check in the virtualization layer, etc? Has anyone else experienced slow multicast speeds when using a virtual ESX host as a Multicast Distribution Point, or even had acceptable speeds for that matter?

    -Tony

    Tuesday, February 3, 2015 6:42 PM

Answers

  • On the virtual side of things, Microsoft acknowledged there is a known bug and to get semi usable speeds the WDS registry setting of TpMaxBandwidth needs to be changed from 100 [default] to 1. However, even with that we still have not been able to push past 11%-14% network utilization. boo! :-) 

    • Marked as answer by Tony Chirillo Wednesday, April 22, 2015 2:06 PM
    Wednesday, April 22, 2015 2:06 PM

All replies

  • Many people cite the VMXNET3 adapter and/or its driver as a source of many issues (both ConfigMgr and non-ConfigMgr). I would suggest switching the NIC type and then trying.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, February 4, 2015 3:08 AM
  • Thanks for the input, but I did not have any luck with switching to a different virtual nic. The speeds remained the same. -Tony
    Thursday, February 5, 2015 3:42 PM
  • On the virtual side of things, Microsoft acknowledged there is a known bug and to get semi usable speeds the WDS registry setting of TpMaxBandwidth needs to be changed from 100 [default] to 1. However, even with that we still have not been able to push past 11%-14% network utilization. boo! :-) 

    • Marked as answer by Tony Chirillo Wednesday, April 22, 2015 2:06 PM
    Wednesday, April 22, 2015 2:06 PM