We have a product that utilizes multicast to distribute near-real-time status updates to clients. This is a windows application that has been around for a while . Some customer sites struggle to get multicast setup correctly on their network, and are asking if there is something more we can do as a vendor to help them.
In the latest troubleshooting from one site, they are suggesting that we don't properly notify the Cisco routers that a client is joining the multicast domain and wishes to receive the multicast traffic. I am not a Cisco expert, so I decided to post my question here. They said they have configured the router for PIMS First Sparse Mode, and watching via wireshark, they cannot see the join request.
On the software side, we are issuing calls to Microsoft WINSOCK setsockopt to IP_ADD_MEMBERSHIP which says it will "Join the socket to the supplied multicast group on the specified interface". We have used a 3rd party app to confirm that multicast "send" and "receive" app is also not passing through the router(s).
This same code works on hundreds of other (different) customer sites, so it's most likely a networking configuration concern at this location, but I am wondering if we as a vendor can do something more, or different, to make this easier for all of our customers.
Is it time to give up on multicast and move to unicast for everything? Is there some way to help our customers troubleshoot this quickly?
Quick update. Breaking the Microsoft NIC team and resetting the IP stack has seemed to help. We are able to see the Multicast join via Wireshark. Now I need to convince the site that their router config is not working.
I need some tips on how to troubleshot this in the router. I have no access to this.
Code Exchange is a great place to start. The About page includes this note about support:
Note: All users should inspect the repository for any usage or contributing process questions. Cisco DevNet is not certifying or maintaining the content ...
We are integrating a third party device (AnyRover from AnyWeb). The AnyRover appears in the inventory and in the topology. However, in the topology the link between the AnyRover and the connecting Switch isn't shown. LLDP is turned on on both devices. Wha...
Contributors to Github repos that have been submitted in Code Exchange are welcome and encouraged to add the "DevNet published" badge to these repos.
The way I do this is as follows.
1) Log in to Code Exchange and go to your Dashboar...
As previously promised (although admittedly, a little late) I'll be walking you through the new Server-Sent Events (SSE) feature we're introducing in Prime Infrastructure 3.5. Please see the previous blog for an overview of SSE and why we're bringin...
Hey folks! While we're wrapping up the development of Prime Infrastructure 3.5 and preparing it for release, I thought I'd update you with some of the changes that we're bringing to the Prime Infrastructure API in 3.5.
Removal of DevNet Integ...