PIM neighbor refresh is slow on Check Point Security Gateway / Cluster after neighbor PIM router failover
||Security Gateway, ClusterXL, Cluster - 3rd party, VSX
||Gaia, IPSO 6.2
|Platform / Model
- 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.
Note: To view this solution you need to