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.
BackgroundI have written a number of blogs on Network Plug and Play (PnP) on APIC-EM and wanted to provide an update of the new improved PnP in DNA Center.This new series covers the changes and enhancements made to PnP on DNA Center 1.2. The P...
I have seen a number of questions on the best way to authenticate a REST API call on DNA-Center.The documentation on the DNA-C indicates that /api/system/v1/auth/token is the way to get an authentication token in a cookie.For those writing python code or ...
FY18 has been a busy yet successful year for our development team. In Nov 2017, we released pyATS for the first time to customers through Cisco DevNetIn Jan 2018, pyATS was showcased and called out at Cisco Live! Barcelona as the next big thing And today...
pyATS is being showcased during Cisco Live! Barcelona!Join us in person at Cisco Live! EMEA 2018 during Jan 29 - Feb 2 in Barcelona, and discover the benefits of Cisco Test Automation Solution, featuring pyATS + Genie, and how it could beneficial to your ...
So what?Maybe you already have your own DNA Center. Maybe you're wondering how, or why to leverage the APIs it supports?I was thinking the same thing you are --> It better support APIs! OK, then onto the next thought; so what?I decided to explore a bit...