01-20-2022 07:10 PM
Hi All,
For how long the PSNs will hold the policies if the PSNs lose their connectivity to both PANs? Is there a grace period? If yes, how long is the default? I could not find any information on this from documentation.
Appreciate your help.
Thank you,
Mohan
Solved! Go to Solution.
01-20-2022 08:02 PM
The node won't "lose" it's configuration, but there are two scenarios where a node will need manual intervention when it comes back or is fixed.
The first is if a node is offline for 24 hours or longer. The PAN will stop attempting replication and you will have to visit the deployment page in the admin GUI and perform a manual sync.
The second is tied to other problems in the deployment, but if a node falls more than 1 million replication messages behind then the PAN will disconnect is and similar to the first scenario it will require a manual resync from the deployment view.
Both of these scenarios though are mild as far as the fix goes if there isn't some other underlying problem, you just need to click "resync" in the deployment view and in about 20-30 minutes your node will be happy again.
01-20-2022 07:16 PM
PSN node Lost connect with PAN, then it holds the information as of now whatever updated and available with PSN, and continue to work as it is. (there are no updates taken plan since you lost PAN), once the connection is restored it will get updated information.
01-20-2022 08:02 PM
The node won't "lose" it's configuration, but there are two scenarios where a node will need manual intervention when it comes back or is fixed.
The first is if a node is offline for 24 hours or longer. The PAN will stop attempting replication and you will have to visit the deployment page in the admin GUI and perform a manual sync.
The second is tied to other problems in the deployment, but if a node falls more than 1 million replication messages behind then the PAN will disconnect is and similar to the first scenario it will require a manual resync from the deployment view.
Both of these scenarios though are mild as far as the fix goes if there isn't some other underlying problem, you just need to click "resync" in the deployment view and in about 20-30 minutes your node will be happy again.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide