Configure Monitoring Nodes for Automatic Failover
If you have two Monitoring nodes in a deployment, you can configure a primary-secondary pair for automatic failover to avoid downtime in the Cisco ISE Monitoring service. A primary-secondary pair ensures that a secondary Monitoring node automatically provides monitoring should the primary node fail.
Before you begin
Before you can configure Monitoring nodes for automatic failover, they must be registered as Cisco ISE nodes.
Configure monitoring roles and services on both nodes and name them for their primary and secondary roles, as appropriate.
Configure repositories for backup and data purging on both the primary and secondary Monitoring nodes. For the backup and purging features to work properly, use the same repositories for both the nodes. Purging takes place on both the primary and secondary nodes of a redundant pair. For example, if the primary Monitoring node uses two repositories for backup and purging, you must specify the same repositories for the secondary node.
Configure a data repository for a Monitoring node using the repository command in the system CLI.
Caution
For scheduled backup and purge to work properly on the nodes of a Monitoring redundant pair, configure the same repository, or repositories, on both the primary and secondary nodes using the CLI. The repositories are not automatically synced between the two nodes.
From the Cisco ISE dashboard, verify that the Monitoring nodes are ready. The System Summary dashlet shows the Monitoring nodes with a green check mark to the left when their services are ready.
Procedure
Step 1
Choose Administration > System > Deployment.
Step 2
In the Deployment Nodes page, check the check box next to the Monitoring node that you want to specify as active, and click Edit .
Step 3
Click the General Settings tab and choose Primary from the Role drop-down list.
When you choose a Monitoring node as primary, the other Monitoring node automatically becomes secondary. In the case of a standalone deployment, primary and secondary role configuration is disabled.
Step 4
Click Save . The active and standby nodes restart.