To avoid issues after installing a full-cp-key / SRX3K-EXTREME-LTU license on a chassis cluster, both nodes within the cluster must be rebooted at the same time.

For more information about this license, refer to the following articles:

• KB23853 - [SRX] Information on Expanded Performance and Capacity License for SRX3x00 (SRX3K-EXTREME-LTU ) [juniper.net]

• KB24134 - [SRX] How to check if Extreme license (SRX3K-EXTREME-LTU) is successfully installed on SRX 3k series devices [juniper.net]

Symptoms may be unpredictable. Some users have reported issues such as Key Management Daemon (KMD) crashes and IPsec failures.

If the two nodes are rebooted at different times, the node that was first rebooted comes online and tries to synchronize with the other node.

Attempting to synchronize the nodes (one with the activated license and the other node that does not have an activated license) causes inconsistencies, which lead to unpredictable failures.

The issue persists even if the nodes are rebooted in a staggered fashion a second time.

After installing the license, both nodes of the cluster must be rebooted  at the same time (within a few seconds of each other at least).

If too much time passes between the reboot of each node, the cluster remains in an inconsistent state until they can be rebooted  at the same time.

2021-09-20: marked article as EOL/EOE.
2020-10-07: Archived.