license needs installed on secondary Admin node?

[huangedmc]

We're in process of installing a two-node ISE cluster, one being the primary Admin & Monitor node, the other being the secondary Admin & Monitor, and both being PSN.

The install guide says:

"if you are installing primary and secondary Administration ISE nodes in your network in a distributed deployment,  each of the Administration ISE nodes in the deployment must have the  same license files."

However, the User Guide, "Setting Up Cisco ISE in a Distributed Environment" chapter says nothing about this requirement, or the instructions.

I assume the license file is based on the primary node's serial number?

Would I be able to install the same license file on the secondary node?

[jrabinow]

Licenses are only installed on the primary administrative node and then get replicated to all servers in the distributed deployment

[huangedmc]

Thank you for the reply.

Could you please clarify what the install guide means by "each of the Administration ISE nodes in the deployment must have the  same license files."?

If each node will have replicated licenses from the primary node, why bother making sure each Admin node has the same license files?

[Saurav Lodh]

In a distributed deployment, where two ISE nodes  assume the Administration persona (primary and secondary), upon  successful installation of the license file, the licensing information  from the primary Administration node is propagated to the secondary  Administration node. So there is no need to install the same license on  each Administration node within the deployment.

[huangedmc]

what if I install the license on primary Admin node, before I register the secondary to primary?

Will license still be propagated to secondary Admin, after it joins the cluster? (the way you described requires the cluster to form first)

[Tarik Admani]

Hi,

When you register the secondary node, regardless of when the licenses is installed either before or after the licenses are applied. A full DB sync occurs when the secondary is joined, so therefore the licensing for the entire deployment is also synced.

Thanks,

Tarik Admani
*Please rate helpful posts*