We have two hub sites with about 300 spokes in a true “hub and spoke” MPLS topology. Half of the spokes use a single hub-site for services while the other half of the spokes use the opposite hub-site for services. There is a backup link - isolated from MPLS cloud - between the two hub-sites as-well. Everything works very well at this point.
We want the hub sites to provide redundant multicast rendezvous points (RP) to the spokes. We use pim sparse-mode only with auto-rp and mapping agents; totally dynamic. Currently, we will only source from the hub sites (we don’t currently plan to source from any spoke). We will not simultaneously source from the two hub sites; solo sourcing only. Nor will we provide Video-on-Demand or VTC. We plan to source HQ updated information on a continuous loop out to the spokes to allow the end-users to “tune-in” when convenient; sort of like a radio station or a broken record.
Since we are using dynamic RP dissemination, is there any advantage to making the Rendezvous Points addresses the same or different?
I am currently configuring the RPs with duplicate addresses and have noticed a few issues.
1. The MPLS PE "aggregation" router chooses a single prefix and thus forces ALL traffic destine to the RP address through a single hub regardless of the spoke source (not multicast source).
I have the prefix 10.99.99.99/32 arriving at the PE router that supports 2 spokes (hub and spoke design), one 10.99.99.99/32 came from hub1 while the other 10.99.99.99/32 came from hub2. BGP filters through the list of route selection parameters and determined the oldest prefix is the one to select as best. Now both spokes route using this single prefix. This was easily fixed with MPLS route-targets and LP assisgnments!!
2. I now have 2 active RPs (single source) in my single multicast domain which violate basic multicast rules.
I implemented MSDP to sync up the two RPs to avoid RPF failures.
3. Failover is instant as the spokes RP mappings always have the RP address 10.99.99.99 regardless of where it came from. If hub1 fails, hub2 is still providing the same RP address and it's already in the RP mapping table.
ok, hopefully someone ---with more multicast experience than myself ---will jump in and assist me - P L E A S E!!!!!!!
I have implemented multicast on the network in a hub and spoke topology. i have set up ospf routing protocol and broadcast all network and can successfully ping.
I am currently using VLC player as my media streaming server and client. i have set up rtp streaming from the HUb router using multicast ip 184.108.40.206 and unable to broadcast the multicast traffic across the spokes 1 and 2 PC's
I have never used vlc player never set up multicast network before and i am struggling with this and need help.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...