PIM neighbor refresh is slow on Check Point Security Gateway / Cluster after neighbor PIM router failover

Support Center > Search Results > SecureKnowledge Details

PIM neighbor refresh is slow on Check Point Security Gateway / Cluster after neighbor PIM router failover

Solution ID	sk107595
Product	Security Gateway, ClusterXL, Cluster - 3rd party, VSX
Version	R77.20, R77.30
OS	Gaia, IPSO 6.2
Platform / Model	All
Date Created	09-Sep-2015
Last Modified	17-May-2017

Symptoms

PIM neighbor refresh is slow on Check Point Security Gateway / Cluster after neighbor PIM router failover:
- After failover of neighboring PIM router (after disconnecting a router link), multicast traffic is recovered after 6 seconds.
- After failback of neighboring PIM router (after reconnecting a router link), multicast traffic is recovered after 10-15 seconds.

Cause

When PIM upstream neighbor changes its GenID, it takes a long time to resume traffic due to tear down of join prune state for all groups associated.
During transitional phase, high volume of multicast traffic causes MFC to register entries as orphans for prolonged period because parent protocol has not fully started.
Some routers might not react well to unicast Join/Prune messages when upstream neighbor GenID changes.

Solution

Note: To view this solution you need to Sign In .

©1994-2019 Check Point Software Technologies Ltd. All rights reserved.
Copyright | Privacy Policy