PSN Node Group Behaviour

[aarav]

Hi ,

Could someone clarify on the PSN Node group behavior on the below scenarios during ISE upgrade 2.2 to 2.6

Deployment - Distributed Environment with 2 PSN (PSN1 & PSN2) Nodes in a Node Group A

Scenario 1:

When one of the PSN nodes (PSN2) is De-registered, what happens to the sessions that were served by the PSN2? Will PSN1 issues COA to disconnect those sessions? 

Scenario 2:

The old 2.2 deployment backup is restored on a New 2.6 deployment.

This PSN2 reimaged and registered to a New Deployment as a First PSN and added to the Node group A

The PSN1 is still on Active on the parallel Old deployment, so will these PSN1 & PSN2 still exchange Heartbeat Messages even though they have identical config but two different parallel deployments (This will be a transition state during the Upgrade from Old to the New Deployment, so I'm not sure how the Node group behaviour will be in this Split Node group phase)

 Thanks in advance....

Aarav

[poongarg]

Scenario 1:

If one of the nodes in a node group fails, the other nodes detect the failure and reset any URL-redirected sessions.

Scenario 2:

Since this 2.6 is a new deployment (although backup is restored) and PSN2 is joined to new admin node, there will not be any communication between the old PSN1 and this PSN2 between the old and new deployment.

[aarav]

Hi Poongarg,

Thanks for your response...

For Senario 1 : I'm it will send COA for Nodes failed within the Node Group?

Is this behavior the same for Node that is getting De-Registered? Does the Node group treat the De-registration process of PSN as Node failure within the Node group?

Scenario 2: What happens to the Sessions when PSN1 (last node in the 2.2 clusters) when its deregistered and PSN2 on the new deployment does it take any initiative to those sessions of PSN1. Will there be a heavy network disruption?