Put Cisco ISE servers in an active/standby HA pair to
provide redundancy.
| Where Can I Use This? | What Do I Need? |
|---|
|
|
One of the following subscriptions:
Device Security subscription for an advanced
Device Security product (Enterprise Plus,
Industrial OT, or Medical)
Device Security X subscription
One of the following Cortex XSOAR setups:
A free, cohosted, limited-featured
Cortex XSOAR instance
AND
A free Cortex XSOAR Engine (on-premises integration)
A full-featured Cortex XSOAR server
|
Device Security uses the term "active" and Cisco
uses the term "primary" to refer to the node in an HA pair that
is in active mode and processing data. Device Security uses the term
"standby" and Cisco uses the term "secondary" to refer to the node
that is in passive mode waiting to take over if the active node
fails.
The Device Security terms "primary" and "secondary" refer
to two ISE instances to which Device Security sends device attributes.
The primary instance, which can be a single ISE server or HA pair,
is the one taking action on the data it receives. The secondary
instance, which can also be a single ISE server or HA pair, receives
the data but typically does not act upon it. In this case, the secondary
instance provides redundancy in case the primary instance stops
functioning. If that happens, an ISE administrator can manually
activate the secondary instance and resume NAC operations.
Setting
up an active/standby HA pair of ISE servers involves the following steps.
