Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

RTO's for Multicast Routes (mroute) Are Not Sync'd Across in NSRP



Article ID: KB7741 KB Last Updated: 23 Jun 2010Version: 3.0
In NSRP Active-Passive environment, upon failover, multicast traffic will not resume until at least 30 seconds later

In the event of a failover via NSRP, multicast traffic will be dropped, and will not resume for 30 seconds.  This causes application time outs, and will force administrator to manually force quit applications, in order to resume communications.  The same does not occur with OSPF or BGP.


RTO (Run Time Objects) for multicast routes are not sync'd across an NSRP cluster.  For this reason, when an NSRP failover occurs, the multicast routes have to re-built on the NetScreen device, and on adjoining multicast devices (i.e. switches, routers, other firewalls).  The time to re-build the routes will be approximately the join prune interval.

Additional Concerns: When you configure PIM in an NSRP environment, make sure PIM is configured on all active interfaces.


Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search