What occurs when a Cisco ISE distributed deployment has two nodes and the secondary node is deregistered?
A. The secondary node restarts.
B. The primary node restarts.
C. Both nodes restart.
D. The primary node becomes standalone.
What occurs when a Cisco ISE distributed deployment has two nodes and the secondary node is deregistered?
Im having a hard time believing both nodes restart in a distributed deployment when you deregistrer a secondary node. this would mean service impact on the customer.
If you look at the documentation:
The application server in an ISE node restarts when you make any of the following changes:
•Register a node (Standalone to Secondary)
•Deregister a node (Secondary to Standalone)
•Primary node is changed to Standalone (if no other nodes are registered with it; Primary to Standalone)
•Administration ISE node is promoted (Secondary to Primary)
•Change the personas (when you assign or remove the Policy Service or Monitoring persona from a node)
•Modify the services in the Policy Service ISE node (enable or disable the session and profiler services)
•Restore a backup on the primary and a sync up operation is triggered to replicate data from primary to secondary nodes
See also:
https://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_dis_deploy.html#:~:text=A%20Cisco%20ISE%20distributed%20deployment%20consists%20of%20one%20primary%20Administration,%2C%20Policy%20Service%2C%20and%20Monitoring.
The documentation cleary states while deregistering a node it causes the application server of that node to restart. it doesnt mention the primary at all.
I would go for answer A, but havent been in de situation to test this out yet.
I believe the original primary as it becomes standalone, it also restarts as it is separated by the secondary. The restart is the application ise not the ISE server.