Keep in mind, will have to be generated via Smart License portal to make sure device is added to correct Virtual Account (VA). I assume you’ve already setup Smart License Account, there will only show a minimum required config: Switch(config)#call-home Make sure you enable Smart License before you perform the conversion. It is the following license smart conversion start
Cisco 3850 right to use license how to#
So, one might be guessing how to remain compliant?Īpparently, there’s a very handy command that performs the conversion of RTU license into Smart License. In fact, we haven’t even had any PAK codes, it was all RTU based. I was confused initially as all our Catalyst 3850 switches have been purchased using Cisco One license, well before Smart License become mandatory. So, keep this in mind and plan carefully. It won’t affect basic switch functions, but will definitely affect anything DNA-based (e.g.
When you upgrade, switches will silently activate EVALUATION mode, which will be valid for the next 90 days, but then, if you do not configure Smart Licensing you automatically go into non-compliance state. Release Notes for Cisco Catalyst 3850 Series Switches, Cisco IOS XE Fuji 16.9.x
Starting from Cisco IOS XE Fuji 16.9.1 the Right-To-Use (RTU) licensing mode is deprecated, and the associated license right-to-use command is no longer available on the CLI. Cisco made this licensing mandatory for Catalyst switching platforms starting from Fuji 16.9.1, as per below However, it also brings some challenges and surprises that everyone must be aware of.įirst of all, keep in mind that eventually everything will be Smart License managed. Overall, this new system brings loads of benefits, such as ability to track license utilization, see all managed instances by hostname, transfer licenses and product instances between virtual accounts (i.e.
It’s been a while since Cisco has announced Smart License to replace Traditional PAK-based licensing.
0 kommentar(er)
