Loss Of Communication Between Failover Units; Upgrading Failover Pairs; Licenses Faq - Cisco ASA 5505 Configuration Manual

Information About Feature Licenses
To view the combined license, see the

Loss of Communication Between Failover Units

If the failover units lose communication for more than 30 days, then each unit reverts to the license
installed locally. During the 30-day grace period, the combined running license continues to be used by
both units.
If you restore communication during the 30-day grace period, then for time-based licenses, the time
elapsed is subtracted from the primary license; if the primary license becomes expired, only then does
the secondary license start to count down.
If you do not restore communication during the 30-day period, then for time-based licenses, time is
subtracted from both primary and secondary licenses, if installed. They are treated as two separate
licenses and do not benefit from the failover combined license. The time elapsed includes the 30-day
grace period.
For example:
1.
2.
3.
4.
•
•

Upgrading Failover Pairs

Because failover pairs do not require the same license on both units, you can apply new licenses to each
unit without any downtime. If you apply a permanent license that requires a reload (see
page
you can reload them separately so you have no downtime.

Licenses FAQ

Q.
A.
Q.
Cisco ASA 5500 Series Configuration Guide using ASDM
4-20
For example, if you have 48 weeks left on the Botnet Traffic Filter license on both units, then the
combined duration is 96 weeks.
You have a 52-week Botnet Traffic Filter license installed on both units. The combined running
license allows a total duration of 104 weeks.
The units operate as a failover unit for 10 weeks, leaving 94 weeks on the combined license (42
weeks on the primary, and 52 weeks on the secondary).
If the units lose communication (for example the primary unit fails over to the secondary unit), the
secondary unit continues to use the combined license, and continues to count down from 94 weeks.
The time-based license behavior depends on when communication is restored:
Within 30 days—The time elapsed is subtracted from the primary unit license. In this case,
communication is restored after 4 weeks. Therefore, 4 weeks are subtracted from the primary license
leaving 90 weeks combined (38 weeks on the primary, and 52 weeks on the secondary).
After 30 days—The time elapsed is subtracted from both units. In this case, communication is
restored after 6 weeks. Therefore, 6 weeks are subtracted from both the primary and secondary
licenses, leaving 84 weeks combined (36 weeks on the primary, and 46 weeks on the secondary).
4-24), then you can fail over to the other unit while you reload. If both units require reloading, then
Can I activate multiple time-based licenses, for example, SSL VPN and Botnet Traffic Filter?
Yes. You can use one time-based license per feature at a time.
Can I "stack" time-based licenses so that when the time limit runs out, it will automatically use the
next license?
"Viewing Your Current License" section on page
Chapter 4 Managing Feature Licenses
4-23.
Table 4-10 on
OL-20339-01