The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
For detailed information about licenses, see the Overview section.
Use the following guidelines and limitations when configuring the permanent licenses:
Parameter | Switch Edition |
---|---|
license filename |
Default essential edition in case of fresh installation and advanced in case of upgrades. |
volatile license |
Disabled By default, the licenses are not returned to the VSM pool when a VEM is removed from the service. |
You can install the licenses on the Cisco Nexus 1000V by using the install license command. When a module (VEM) comes up, it request licenses from the Cisco Nexus 1000V License Manager.
If the license checkout fails, the module is marked as unlicensed and the virtual Ethernet (veths) interfaces that are attached to that module are not allowed to come up. For the software upgrades from a pre-4.2(1)SV2(1.1) release to 4.2(1)SV2(1.1) release, if the switch is still in the default licensing period, it is extended for another 60 days from the software upgrade date.
Starting with Release 4.2(1)SV2(1.1), the license expiry warning log message informs users about the option to change the system to the Essential edition in addition to the option of installing more licenses. Messages are logged only when the switch is in the Advanced edition and the licenses are in use. Messages are logged every day starting from 4 weeks before the licenses are about to expire and every hour on the last day before the licenses expire.
The license expiry does not have any effect when the switch edition is the Essential edition. The Advanced edition functionality is the same as the current Cisco Nexus 1000V implementation. The existing modules and the interfaces continue to be operationally up and the switch continues to forward the traffic. If an interface or module flaps, it stays down until the valid licenses are installed or the switch is changed to the Essential edition. The new interfaces and the modules come up in the unlicensed state. You can disable the advanced features and change the switch edition to Essential even after the licenses have expired.
By default, the switch uses the Essential edition which can be deployed across 64 hosts with a maximum of 512 CPUs. Default licenses are valid for 60 days from the time of installation, during which time you are allowed to change the switch edition to Advanced and try out the advanced features. A maximum of 512 licenses (up to 64 hosts) are supported during the default license period for the Advanced edition.
The advanced features are available only when you change the switch edition to Advanced. When you install the evaluation or permanent licenses at any time during the default license period, the switch stops using the default licenses and starts using the installed licenses. When the default or the installed licenses expire, if the switch edition is Advanced, it remains in the Advanced edition. You can change the switch edition to the Essential edition even after the license has expired.
After you upgrade the software, the Cisco Nexus 1000V comes up in the configured switch edition. There is no impact to the license status of the modules after the upgrade. The current (pre-4.2(1)SV2(1.1)) installations of Cisco Nexus 1000V are considered to be operating in the Advanced edition. When you upgrade the software to Release 4.2(1)SV2(1.1) or later releases, the switch comes up in the same (Advanced) edition.
If the switch is in the default evaluation period at the time of the upgrade, the default evaluation period is reset to 60 days. You have a choice to move the switch to the Essential edition. This action checks in all the licenses that are currently being used back into the license pool.
The following table lists the default switch editions.
Current N1K Software Version |
Action |
Current Switch Edition |
New Switch Edition |
---|---|---|---|
Pre-4.2(1)SV2(1.1) release |
Upgrade to Release 4.2(1)SV2(1.1) |
— |
Advanced |
None |
Fresh Installation of Release 4.2(1)SV2(1.1) |
— |
Essential |
Release 4.2(1)SV2(1.1) |
Upgrade to post-4.2(1)SV2(1.1) release |
Essential |
Essential |
Advanced |
Advanced |
Starting with Release 4.2(1)SV2(1.1), you can configure which switch edition to use (Advanced or Essential).
This section describes how to obtain the license file that is required for each VSM and then install it. This section includes the following topics:
You can obtain a license file for a VSM.
Step 1 |
Obtain the serial number, also called the host ID, for your VSM: show license host-id switch# show license host-id License hostid: VDH=1280389551234985805
|
||
Step 2 | From your software license claim certificate, locate the product authorization key (PAK). | ||
Step 3 | Go to the Software Download site. | ||
Step 4 | From the Software Download site, go to the Product License Registration site. | ||
Step 5 |
From the Product License Registration website, follow the instructions for registering your VSM license. The license key file is sent to you in an e-mail. The license key authorizes use on only the host ID device. You must obtain separate license key file(s) for each of your VSMs.
|
||
Step 6 | Save your license to a SCP/SFTP/TFTP server. | ||
Step 7 |
Copy your license to bootflash on the VSM. switch# copy scp://user@linux-box.cisco.com/home/user/n1kv_license.lic bootflash: Enter vrf (If no input, current vrf 'default' is considered): user@linux-box.cisco.com's password: n1kv_license.lic 100% 252 0.3KB/s 00:00 switch# |
You can install the license files on a VSM. Installing multiple licenses is called stacking.
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | switch# install license bootflash: filename | Installs the license from the active VSM console.
The license is installed on the VSM and each VEM automatically acquires a license for every CPU socket. |
||
Step 2 | switch# show license file filename | Verifies the license installation by displaying the license configured for the VSM. |
||
Step 3 | switch# show license usage package_name | Verifies the license installation by displaying it in the license usage table.
|
||
Step 4 | switch# copy running-config startup-config | (Optional) Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
This example shows how to install a license file and then display its contents and usage:
switch# install license bootflash:license_file.lic Installing license ..done switch# show license file license_file.lic SERVER this_host ANY VENDOR cisco INCREMENT NEXUS1000V_LAN_SERVICES_PKG cisco 1.0 permanent 10 \ HOSTID=VDH=1575337335122974806 \ NOTICE="<LicFileID>license_file.lic</LicFileID><LicLineID>0</LicLineID> \ <PAK>PAK12345678</PAK>" SIGN=3AF5C2D26E1A switch# show license usage NEXUS1000V_LAN_SERVICES_PKG ---------------------------------------- Feature Usage Info ---------------------------------------- Installed Licenses : 10 Default Eval Licenses : 0 Max Overdraft Licenses : 16 Installed Licenses in Use : 4 Overdraft Licenses in Use : 0 Default Eval Lic in Use : 0 Default Eval days left : 0 Licenses Available : 22 Shortest Expiry : Never ---------------------------------------- Application ---------------------------------------- VEM 3 - Socket 1 VEM 4 - Socket 1 VEM 4 - Socket 2 VEM 5 - Socket 1 ---------------------------------------- switch#
Note |
The Default Eval days left field in the show license usage NEXUS1000V_LAN_SERVICES_PKG CLI command displays the number of default evaluation days that are remaining before the license expires, not including the present day. |
To verify the license configuration, perform one of the following tasks:
Command | Purpose |
---|---|
show license |
Displays the license filename for the VSM. |
show license brief |
Displays the license installed on the VSM. |
show license file filename |
Displays the contents of the license file installed on the VSM, including the license filename and the expiration date for evaluation licenses. |
show license usage |
Displays the total number of licenses in use on the VEMs. |
show license usage package_name |
Displays statistics about the number of evaluation and permanent licenses available, installed, and in use on the VSM. |
show module vem [module] license-info |
Displays the license mode and the usage of licenses by each module. |
This section includes the following topics that describe how to transfer licenses between VEMs and uninstall a license by transferring it from a VEM to the VSM license pool:
You can transfer licenses from one VEM to another, for example, after moving a VM from one host to another.
Command or Action | Purpose | |
---|---|---|
Step 1 | switch# configure terminal | Enters global configuration mode. |
Step 2 | switch(config)# svs license transfer src-vem vem_no dst-vem vem_no | Transfers the licenses from one VEM to another. This command fails if switch is in essential edition. |
Step 3 | switch# show license usage package_name | Verifies the transfer by displaying the licenses in use on each VEM. |
This example shows how to transfer a license from VEM 3 to VEM 5 and verify the transfer in the license usage:
switch(config)# svs license transfer src-vem 3 dst-vem 5 switch(config)# switch# show license usage NEXUS1000V_LAN_SERVICES_PKG ---------------------------------------- Feature Usage Info ---------------------------------------- Installed Licenses : 29 Default Eval Licenses : 0 Max Overdraft Licenses : 16 Installed Licenses in Use : 2 Overdraft Licenses in Use : 0 Default Eval Lic in Use : 0 Default Eval days left : 0 Licenses Available : 43 Shortest Expiry : 01 Jul 2011 ---------------------------------------- Application ---------------------------------------- VEM 5 - Socket 1 VEM 5 - Socket 2 ---------------------------------------- switch#
You can transfer licenses from a VEM to the VSM license pool when, for example, removing a license from a VEM.
Command or Action | Purpose | |
---|---|---|
Step 1 | switch# configure terminal | Enters global configuration mode. |
Step 2 | switch(config)# svs license transfer src-vem vem_no license_pool | Transfers the licenses from a VEM to the license pool. |
Step 3 | switch# show license usage package_name | Verifies the transfer by displaying the licenses in use on each VEM. |
This example shows how to display the licenses in use on each VEM. Notice that the licenses on VEM 3 are no longer in use.
switch# show license usage NEXUS1000V_LAN_SERVICES_PKG ---------------------------------------- Feature Usage Info ---------------------------------------- Installed Licenses : 10 Default Eval Licenses : 0 Max Overdraft Licenses : 16 Installed Licenses in Use : 3 Overdraft Licenses in Use : 0 Default Eval Lic in Use : 0 Default Eval days left : 0 Licenses Available : 23 Shortest Expiry : Never ---------------------------------------- Application ---------------------------------------- VEM 4 - Socket 1 VEM 4 - Socket 2 VEM 5 - Socket 1 ---------------------------------------- switch#
You can use this procedure to transfer licenses from a license pool to a VEM. The VEM will be licensed only if there are enough available licenses. For example, if the license request fails for a module, use the svs license transfer license_pool dst-vem module command to transfer the licenses from the license pool to the VEM.
When you transfer the licenses from the license pool to the VEM, the module will be licensed if there are enough licenses available and all the virtual Ethernet interfaces that were powered down will be powered up.
You are logged in to the CLI in EXEC mode.
Command or Action | Purpose | |
---|---|---|
Step 1 | switch# configure terminal | Enters global configuration mode. |
Step 2 | switch(config)#svs license transfer license_pool dst-vem module | Transfers a license from the license pool to the VEM. This command fails if switch is in essential edition. The value of module can be from 3 to 66. |
Step 3 | switch# show module vem module license-info | Verifies the transfer by displaying the licenses in use on each VEM. |
This example shows how to display the licenses in use on each VEM.
switch# show module vem 3 license-info Licenses are Sticky Mod Socket Count License Usage Count License Version License Status --- ------------ ------------------- --------------- -------------- 3 1 1 1.0 licensed switch#
This section provides information about enabling and disabling the volatile license feature and includes the following sections:
You can enable volatile licenses so that whenever a VEM is taken out of service, its licenses are returned to the VSM pool of available licenses.
Note |
Service Disruption—Volatile licenses are removed from a VEM during a loss in connectivity and the system will try to get the required licenses when connectivity resumes. We recommend that the volatile licenses remain disabled and that you transfer unused licenses using the Transferring Licenses to the License Pool section. |
A volatile license is disabled by default. That is, by default, licenses are not returned to the VSM pool when a VEM is removed from service.
You are logged in to the CLI in EXEC mode.
Command or Action | Purpose | |
---|---|---|
Step 1 | switch# configure terminal | Enters global configuration mode. |
Step 2 | switch(config)# svs license volatile | Enables volatile licenses in the running configuration. |
Step 3 | switch(config)# copy running-config startup-config | (Optional) Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
This example shows how to enable a volatile license:
switch# configure terminal switch(config)# svs license volatile switch(config)# copy running-config startup-config switch(config)#
You can disable volatile licenses so that whenever a VEM is taken out of service its licenses are not returned to the VSM pool of available licenses.
Note |
By default, the licenses are non volatile (sticky) in nature, which is the recommended configuration. This configuration ensures that the licenses are reserved for a VEM. Even after a period of brief connectivity loss between the VEM and the VSM, the VEM is guaranteed to get the needed licenses. |
You are logged in to the CLI in EXEC mode.
Command or Action | Purpose | |
---|---|---|
Step 1 | switch# configure terminal | Enters global configuration mode. |
Step 2 | switch(config)# no svs license volatile | Disables volatile licenses in the running configuration. |
Step 3 | switch(config)# copy running-config startup-config | (Optional) Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
This example shows how to disable a volatile license:
switch# configure terminal switch(config)# no svs license volatile switch(config)# copy running-config startup-config switch(config)#
You can change the serial number, or host ID, associated with a license. This process is also called rehosting and is required if you replace a VSM in your network with a new VSM.
Caution |
Service Disruption—When you remove a VSM from your network, the vEthernet interfaces on the VEMs are removed from service and the traffic flowing to them from virtual machines is dropped. This traffic flow is not resumed until you add a new VSM and new license file with the new host ID. |
Step 1 |
Obtain the serial number, also called the host ID, for your new VSM: switch# show license host-id License hostid: VDH=1280389551234985805
|
||
Step 2 |
E-mail the following information to licensing@cisco.com, requesting the license file be rehosted to the new host ID:
A new license key file, with the host ID of the new VSM, is sent to you in e-mail within 48 hours.
|
||
Step 3 | Save your license to a SCP/SFTP/TFTP server. | ||
Step 4 |
Copy your license to bootflash on the VSM. switch# copy scp://user@linux-box.cisco.com/home/user/n1kv_license.lic bootflash: Enter vrf (If no input, current vrf 'default' is considered): user@linux-box.cisco.com's password: n1kv_license.lic 100% 252 0.3KB/s 00:00 switch# |
This table includes only the updates for those releases that have resulted in additions or changes to the feature.
Feature Name | Releases | Feature Information |
---|---|---|
Default license |
4.2(1)SV2(1.1) |
512 default licenses that are valid for 60 days are included in the software image. |
Evaluation license |
4.0(4)SV1(3) |
16 evaluation licenses that are valid for 60 days are included in the software image. More evaluation licenses of varied durations can be downloaded from Cisco.com and installed separately. |
Evaluation license |
4.0(4)SV1(2) |
Evaluation licenses are part of the software installation or upgrade. A separate evaluation license file no longer needs to be installed. |
show license usage package_name command |
4.0(4)SV1(2) |
The show license usage package_name command output is updated to show statistics about the number of evaluation and permanent licenses available, installed, and in use on the VSM. |
License |
4.0(4)SV1(1) |
This feature was introduced. |