Secondary Node Deregistration in Cisco ISE Distributed Deployment

C.

When a Cisco ISE distributed deployment has two nodes and the secondary node is deregistered, the primary node will continue to operate normally as a standalone deployment. The following details explain what happens in this scenario:

1. The secondary node is deregistered from the deployment: When the secondary node is deregistered, it is removed from the deployment and is no longer considered part of the distributed deployment. The primary node will continue to function as normal, but without the added capabilities of the secondary node.

2. The primary node continues to operate: The primary node in the distributed deployment will continue to function as a standalone deployment. It will continue to process all authentication and authorization requests, and it will still store all the configuration and policy information.

3. No impact on the network: Deregistering a secondary node from a distributed deployment has no impact on the network. All network devices will continue to communicate with the primary node, and users will still be able to authenticate and access network resources.

4. No need to rebuild the deployment: Deregistering a secondary node from a distributed deployment does not require the deployment to be rebuilt. The primary node will continue to function normally, and a new secondary node can be added to the deployment if needed.

In summary, when a Cisco ISE distributed deployment has two nodes and the secondary node is deregistered, the primary node will continue to operate normally as a standalone deployment without any impact on the network.