Upgrades - Cisco Catalyst 9400 System Management Configuration Manual

Smart Licensing Using Policy
• A switchover.
• A reload.
When one of the above events occur, the "Next report push" date of the show license status privileged EXEC
command is updated. But it is the implemented topology and associated reporting method that determine if
the report is sent by the product instance or not. For example, if you have implemented a topology where the
product instance is disconnected (Transport Type is Off), then the product instance does not send RUM reports
even if the "Next report push" date is updated.
For a new member or standby addition:
• A product instance that is connected to CSLU, does not take any further action.
• A product instance that is directly connected to CSSM, performs trust synchronization. Trust

Upgrades

This section describes how upgrade or migration to Smart Licensing Using Policy is handled. It also clarifies
how Smart Licensing Using Policy handles all earlier licensing models including: the earlier version of Smart
Licensing, Specific License Reservation (SLR), Right-to-Use Licensing (RTU), and how evaluation or expired
licenses from any of the earlier licensing models are handled in Smart Licensing Using Policy environment.
To migrate to Smart Licensing Using Policy, you must upgrade to a software version that supports Smart
Licensing Using Policy. After you upgrade, Smart Licensing Using Policy is the only supported licensing
model and the product instance continues to operate without any licensing changes. The
Licensing Using Policy, on page 118
to Cisco Catalyst Access, Core, and Aggregation Switches.
Device-led conversion is not supported for migration to Smart Licensing Using Policy.
Identifying the Current Licensing Model Before Upgrade
Before you upgrade to Smart Licensing Using Policy, if you want to know the current licensing model that
is effective on the product instance, enter the show license all command in privileged EXEC mode. This
command displays information about the current licensing model for all except the RTU licensing model. The
show license right-to-use privileged EXEC command displays license information only if the licensing model
is RTU.
How Upgrade Affects Enforcement Types for Existing Licenses
When you upgrade to a software version which supports Smart Licensing Using Policy, the way existing
licenses are handled, depends primarily on the license enforcement type.
synchronization involves the following:
Installation of trust code on the standby or member if not installed already.
If a trust code is already installed, the trust synchronization process ensures that the new standby or
member is in the same Smart Account and Virtual Account as the active. If it is not, the new standby or
member is moved to the same Smart Account and Virtual Account as the active.
Installation of an authorization code, policy, and purchase information, if applicable
Sending of a RUM report with current usage information.
System Management Configuration Guide, Cisco IOS XE Bengaluru 17.4.x (Catalyst 9400 Switches)
section provides details and examples for migration scenarios that apply
Upgrades
Migrating to Smart
105