Support Center > Search Results > SecureKnowledge Details
PIM neighbor refresh is slow on Check Point Security Gateway / Cluster after neighbor PIM router failover
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 .