Guest

Cisco Catalyst 4500 Series Switches

Cisco Catalyst 4500E Supervisor 7-E and 7L-E and Cisco Catalyst 4500-X Series Software Activation Licensing Deployment Guide

  • Viewing Options

  • PDF (3.3 MB)
  • Feedback

1. Introduction

With the introduction of Catalyst 4500E Supervisor 7-E, Cisco Software Activation Licensing (SAL) is used for customers to deploy different IOS feature sets. This paper provides detailed description of the SAL operation on Catalyst 4500E Supervisor 7-E and 7L-E and Cisco Catalyst 4500-X Series for different deployment scenarios. The audiences for this document are partners, customers, network operators and administrators who procure, upgrade and replace software on Catalyst 4500E Supervisor 7-E or 7L-E or Cisco Catalyst 4500-X Series systems.

2. Overview of Supervisor 7-E, 7L-E and Cisco Catalyst 4500-X Series Software Licenses

With Catalyst 4500E Supervisor 7-E, 7L-E and Cisco Catalyst 4500-X Series, universal IOS images are used to simplify customer deployments. An universal image is a “kitchen sink” image that contains all the IOS feature packages from LAN Base to Enterprise Services. Customers can deploy a specific feature package by applying corresponding software activation licenses. The following are the types of software licenses available:

2.1 Permanent License

A Permanent license is valid for the lifetime of the system on which it is installed. Permanent licenses include LAN Base, IP Base, and Enterprise Services feature sets. When installed, the permanent license overrides any other temporary licenses.

2.2 Demo License

Demo Licenses are used by customers for evaluating new capabilities or by Cisco Sales team for demonstrating software features to customers. The demo license enables a feature set to be used for 60 days. The usage is calculated based on the actual number of days the system is operational in this license mode. This license can be availed by emailing the Global Licensing Operations (GLO) Team - better known as Licensing TAC - at licensing@cisco.com or by visiting the below website: https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet?FormId=586

After installing the license using IOS CLI “license install” mentioned in Section 4.1, configure the system to boot in the demo license by using the IOS CLI shown below:

RAFALE (config)#license boot level ipbase | entservices
RAFALE (config)#^Z
RAFALE#copy running-config startup-config
RAFALE#reload

Text Box. 1

Note that the keywords “ipbase” or “entservices” used in the above command are case-sensitive.

User will be notified of the impending license expiration before it expires. After the demo license expires, the system continues to run at that license level, to ensure network availability. However, syslog messages indicating the expired license are displayed on the console, at an interval of one every five minutes.

If for any reason the system reloads and the “license boot level ipbase | entservices” IOS CLI is saved as part of startup-configuration, the system overrides the base license, and continues to boot in the license level specified in the IOS CLI, even though it is expired. This behavior might be changed in future when licenses will be enforced.

If for any reason the system reloads and the “license boot level ipbase | entservices” IOS CLI is NOT saved as part of startup-configuration, the system will boot in the default LAN Base license.

Customers can request a new Demo license that renews the 60-day operational period. It is strongly recommended to purchase and install a permanent license to ensure entitlement.

2.3 Evaluation License

Evaluation License is a built-in one-time license for customers to evaluate a specific feature package for a period of 60 days of actual use. It does not require access to the Cisco Licensing Portal to activate this license. It is recommended that end customers use this license only in times of contingency to get their systems operational at the desired feature package.

To configure the evaluation license, execute the “license boot” IOS CLI as shown in Text Box. 1 above.

User will be notified of the impending license expiry before it expires. After the evaluation license expires, the system continues to run at that license level. However, syslog messages indicating the expired license are continuously displayed on the console, at an interval of one every five minutes.

If for any reason the system reloads and the “license boot level ipbase | entservices” IOS CLI is saved as part of startup-configuration, the system overrides the base license, and continues to boot in the license level specified in the IOS CLI, even though it is expired. This behavior might be changed in future when licenses will be enforced.

If for any reason the system reloads and the “license boot level ipbase | entservices” IOS CLI is NOT saved as part of startup-configuration, the system will boot in the default LAN Base license.

Unlike the Demo License, the evaluation license cannot be renewed after expiration. It is strongly recommended to purchase and install a permanent license to ensure entitlement.

3. Components to Generate License

Below are the components used in licensing operations.

3.1 Product Identification (PID)

The PID stands for the model number of the device. In the Catalyst 4500E or 4500-X Series, since the license is locked to the chassis, the PID is associated with the chassis model number. For example, the PID can be 4503-E, 4506-E, 4507R-E, 4507R+E, 4510R-E and 4510R+E depending on the chassis.

3.2 Unique Device Identifier (UDI)

The UDI consists of the PID along with the Chassis Serial Number. One can get the UDI for the Cisco Catalyst 4500-X or 4500E Chassis in which the Supervisor 7E or 7L-E will be installed by following the steps given below:

Figure 1.      SUP7-E Console screenshot

In case the Supervisor 7-E or 7L-E is a replacement for an existing Supervisor 6-E or older Supervisor system, one can get the chassis PID and serial number as seen below:

Figure 2.      SUP6-E screenshot

3.3 Product Activation Key (PAK)

A PAK is an 11-digit alphanumeric key created by Cisco manufacturing that identifies a specific software purchase - in other words, it is a short alphanumeric string provided by Cisco as a “proof of purchase” when a software feature set is purchased. PAKs can be ordered independently for feature upgrades. PAKs do not have an expiration date and can be redeemed any time after purchase.

Delivery of PAKs can be paper based or electronic. Customers ordering paper based PAKs are sent a software claim certificate by mail identifying their PAK string.

The electronic delivery PAK is differently indicated in the PID below by having “L-” prefix, as seen below, from the screen shot taken from the Dynamic Configuration Tool (DCT).

Figure 3.      DCT Screenshot showing types of PAK Delivery options

Customers ordering an electronic PAK receive an email that points to a secure portal where they can download a pdf file containing the PAK information. This information is sent to the customer in a matter of minutes after purchase.

Catalyst 4500E Supervisor 7-E, 7L-E and Cisco Catalyst 4500-X Series support multi-use PAK. One PAK holds multiple tokens to obtain licenses for more than one system. The backend software on the Cisco Licensing Portal keeps track of how many times a PAK is redeemed if it is a multi-use PAK.

Below screenshots show that the customer can order multiple licenses for different features sets within the same order, by choosing the “C4500E-LIC=” Spare License PID, as seen below. In the below example, there are 5 quantities of IP Base to Enterprise services upgrade licenses, as well as 5 quantities of upgrade from LAN Base to Enterprise services and 15 quantities of upgrade from LAN Base to IP Base feature package. The same PAK can be used to obtain licenses for multiple Supervisor systems.

The below screen shots from DCT shows how to order the multi-use PAK - for paper-based delivery option in Figure. 4 and electronic delivery option in Figure. 5. For electronic delivery option, use the “L-C4500E-LIC” PID.

Figure 4.      Paper-based delivery option for multi-use PAK

Figure 5.      Electronic delivery option for multi-use PAK

Below is a screen shot of an actual multi-use PAK selected with the option of paper delivery.

Figure 6.      Multi-use PAK

The 4500E Supervisor 7-E and 7L-E ship with a PAK for IPBase, if a spare supervisor is ordered.

Figure 7.      Dynamic Configurator Screenshot

As seen from a screenshot from the Dynamic Configuration Tool (DCT) above, the last item: C4500E-LIC-PAK indicates that a paper PAK will be shipped with the spare supervisor. The PAK is enclosed in the same packaging as the Supervisor 7-E and looks as shown below:

Figure 8.      Physical PAK

Figure 9.      Dynamic Configuration Screenshot

If chassis are integrated with the Supervisor 7-E or 7L-E at the time of ordering - as seen in the example above - there are no PAKs shipped. Comparing Figure.8 above with Figure.6, notice that “C4500E-LIC-PAK” is not present in the above screen shot. Cisco Manufacturing installs the licenses on the systems and they are ready to use upon arrival, at customer locations.

3.4 Device Credentials

Device credential is an electronically signed hash of the UDI and license. The Cisco Licensing Portal backend system authenticates a license by means of encrypted device credentials. This ensures that the license information is secure and tamper-resistant.

The device credential is required to transfer a license from one chassis to another - a process called re-hosting, which is described in detail later in the document.

4. Deployment Scenarios

The following sections detail the steps that are required by the end user to register, receive and install the license on the Supervisor 7-E, 7L-E and Cisco Catalyst 4500-X Series in various deployment scenarios.

4.1 Supervisor Upgrade to Supervisor 7-E or 7L-E

This scenario details the steps needed to install the license during an upgrade to Supervisor 7-E or 7L-E.

Begin the licensing process by browsing to http://www.cisco.com/go/license. There is a PAK (for IP Base [default] or Entservices) which is shipped with each spare Supervisor 7-E and 7L-E. Type in the PAK number, as seen below.

Figure 10.    Input PAK

After clicking on the “Submit” button, the system will process the PAK submitted and present the SKU configuration for that PAK, as seen below in the next screen.

Figure 11.    PAK showing the License Feature set

One PAK might contain more than one license for a SKU. In the above example, there is only one quantity of the 4500E-LIC-PAK. Once all the information is entered into the screen above, select the “All Done” button in the browser. The next screen asks for the PID and the UDI which was collected before we began the Licensing Process. Enter the PID and the UDI as shown in the screenshot below:

Figure 12.    Chassis PID and Serial Number

The next screen asks for the end user’s basic information like name, address, company, email address, etc. Feed all the required information as specified in the next screen, and select the “Continue” button. After this the next screen displays information about the PID, Serial Number of the Chassis, Product SKU, PAK number, description, Feature SKU, and other information. Pls see the screen below for example:

Figure 13.    Review screen

Click the “Submit” button if all the above information is accurate.

The system will open a screen stating it is processing the request - and shortly present a screen stating that registration is complete, and a button to download the license, as seen below:

Figure 14.    Registration complete

Clicking the “Download License” button in the browser, opens up the next screenshot, where you save the file, which is of the *.lic format, as can be seen in the screenshot below:

Figure 15.    Download License file

Copy the file onto the Switch using TFTP, or RCP or by using the various usual means available. In the example below, the *.lic file is copied from a USB stick onto the bootflash device of the Supervisor.

Figure 16.    License copy to USB disk

One could also install the license without copying the *.lic to any local device on the switch.

The last part is the installation of the license on the 4500E system. Follow the steps as shown below in the screenshot to install the license.

Figure 17.    License install

As seen from the above output, the current level is “lanbase”, but on the next reboot, the license level will be “ipbase”. Reload the system once to enable the system to boot in the installed license level.

Figure 18.     “show license image level” output

Use “reloads” for reloading single Supervisor 7-E or 7L-E systems, and use “redundancy reload shelf” for reloading both the active and standby Supervisor 7-E or 7L-E Supervisors, in a redundant supervisor system. Using “reload” on redundant Supervisor systems will cause a switchover and not a reload of the entire system.

Note:    Licenses are tied to the chassis but are stored locally on a Supervisor. Hence when ordering a spare Supervisor, a PAK is shipped with the Supervisor. Once the Supervisor is in the appropriate chassis, user can perform the above procedure for installing and activating the license.

Also on redundant Supervisor systems, the license is synchronized from the active to the standby so users ordering a redundant system have to order only one IPBase or Enterprise Services license to be installed and activated on redundant Supervisor systems.

4.2 Greenfield Deployment with New Supervisor 7-E, 7L-E and Cisco Catalyst 4500-X Series Systems

This scenario deals with deploying systems that are ordered together with supervisor, chassis and license. In this scenario, because the chassis and supervisor are ordered together, Cisco manufacturing will install the purchased software license before it ships to the customer.

This system is ready to use upon arrival, and needs no further license installation steps by the end customer, hence no PAK is delivered. If needed, the license information can be looked up on the Cisco license portal, as seen in the screen shots below.

Figure 19.    License lookup

Figure 20.    Device credentials and UDI

Figure 21.    Final license lookup

It is strongly recommended to save the license and device credentials in an accessible location, since they are essential in looking up licenses, Re-hosting and RMA operations.

Below is an example where the license information is saved on a USB stick.

Figure 22.    License file

Device credentials can be saved as shown below:

Figure 23.    Device credentials

4.3 Deploying Redundant Supervisor

This scenario details the procedure in adding a redundant Supervisor 7-E or 7L-E to a production system. There are two scenarios depending on the existing IOS feature package:

1.     Existing supervisor with LAN Base feature set - in this case the redundant supervisor (shipped with PAK for IP Base [default] or entservices [if ordered] feature set) will upgrade the system to the feature set of the newly ordered redundant supervisor. Because of the feature package change, customers would need to go through the license activation steps described above.

2.     Existing supervisor with either ipbase or entservices feature set - in this case, the system will stay at the same feature set with the redundant supervisor.

The spare Supervisor 7-E and 7L-E include IP Base feature set, at no extra cost. When upgrading a system to Enterprise Services license, only one license “C4500E-IP-ES” needs to be purchased when ordering 4500E Chassis and redundant Supervisor 7-E or 7L-E. Once the license is installed on the active Supervisor, the standby Supervisor copies the license as part of the bulk synchronization process; and gets automatically installed on the standby supervisor.

The license is based on the chassis and not the Supervisor 7-E or 7L-E - although the license is stored on the Supervisor for that chassis.

The following example outlines the steps for scenario 1 described above.

Ensure that the console of both the Active and Standby Supervisors is accessible, before starting.

The UDI information can be found using the command “show license udi”.

Follow the procedure outlined in Section 4.1 above, to register the PAK and obtain the license file for the redundant supervisor.

Insert the spare Supervisor in the standby slot - slot 6 in a 4510R+E chassis, and slot 4 in a 4507R+E chassis. In this example, a 4510R+E chassis is used. Since the active Supervisor in slot 5 is operational in LAN Base level, the Supervisor in slot 6 will initialize itself in RPR redundancy mode with the same LAN Base level, as shown in the screenshot below.

Figure 24.    System messages

Install the license obtained from the Cisco Licensing portal from the Active (slot 5) Supervisor; as shown below:

Figure 25.    License install

Once the license is installed on the system, use the built-in Evaluation license to force the system to boot in IP Base image, on the subsequent reboot. Use the Cisco IOS CLI as shown below:

Switch (config)#license boot level ipbase

Text Box. 2

Save the configuration, and reload only the Standby Supervisor, in slot 6. Below screenshot shows the steps to configure on the switch and the corresponding system level messages generated.

Figure 26.    Reset standby supervisor

The Standby Supervisor in slot 6 reboots and detects the Active Supervisor operational in LAN Base level. The “license boot level ipbase” forces the Supervisor to override the Active Supervisor license level; and the Standby Supervisor in slot 6 continues to boot in IP Base level. Because of the difference in license levels between the Active (in LAN Base), and Standby (in IP Base) Supervisors, the redundancy mode falls back to RPR between the Supervisors. Check the screenshot below:

Figure 27.    License level mismatch

After the system initializes in RPR redundancy mode, initiate a switchover from the Active Supervisor in slot 5 to the Supervisor in slot 6, by issuing “reload” command on Active Supervisor console.

Using “reload” on Catalyst 4500E redundant Supervisor systems will cause a switchover and not a reload of the entire system.

Proceed to the console of the Supervisor in slot 5 - which is in the process of rebooting. Break the automatic boot process, by typing Ctrl+c once or twice when the prompt for disabling automatic boot shows up on the console. Let this Supervisor be in ROMMON prompt.

The Supervisor in slot 6 - that is online in IPBase license - will take the active Supervisor role in the chassis, as seen in the screenshot below:

Figure 28.    New active supervisor in IP Base feature set

From the Active Supervisor in slot 6, configure the system to boot using the Permanent license by issuing “no license boot level ipbase” from the IOS Configuration mode. Configure SSO redundancy mode at this time. The software will prompt to reboot the Standby Supervisor (in slot 5) - confirm to reboot - exit configuration mode and save the configuration.

Figure 29.    New active supervisor SSO configuration

As the Supervisor in slot 5 reboots, it detects that the Active Supervisor in slot 6 is operational in the IP Base license, and in SSO redundancy mode. The software on this Supervisor boots in IPBase license, and proceeds to initialize in SSO mode - where the license is part of the bulk synchronization process; and gets automatically installed on this Supervisor, as seen in the following screen shots.

Figure 30.    Supervisor SSO synchronization messages

Figure 31.    System successfully upgraded to IP Base image

Figure 32.    Active and Standby supervisor roles reversed

The summary of the steps above is given below:

   Obtain the system UDI and subsequently the License file

   Insert the Supervisor in Standby slot

   Install the license

   Configure system to use Evaluation license by “license boot level ipbase | entservices”

   Reboot only the Standby Supervisor

   Supervisors will initialize in RPR redundancy mode, due to license level mismatch

   Initiate RPR switchover

   Hold the rebooting Supervisor in ROMMON mode, by disabling auto-boot (Ctrl+c)

   Configure system to use Permanent license by issuing “no license boot level ipbase | entservices”

   Configure SSO redundancy mode - this will automatically reboot the standby Supervisor

   Save configuration

   Standby Supervisor boots in IP Base license level and because of SSO the license is automatically installed as part of bulk synchronization process

   The Active and Standby Supervisor slots will be reversed, by this procedure

4.4 Changing Supervisor across Chassis or Supervisor RMA

If a Supervisor needs to be swapped around from one chassis to another chassis, due to lab testing or RMA, below are the steps to perform.

It is important that the license for the chassis is available for this operation to be successful.

For example, below is a Supervisor 7-E system already installed with Entservices license.

RAFALE#sh license image level
Module Name        Image level  Priority  Configured  Valid license
--------------------------------------------------------------------
 
WS-X45-SUP7-E      entservices  1         NO          entservices             
                   ipbase       2         NO          ipbase                    
                   lanbase      3         NO          lanbase                   
 
Module Name        Role           Current Level     Reboot Level
--------------------------------------------------------------------
WS-X45-SUP7-E      Active         entservices       entservices      

Text Box. 3

Assume that this supervisor has to be RMA-ed, the newly inserted supervisor module will not contain the license for this chassis; and initially the image will boot online in LAN Base license; as can be seen in the console display, below.

*Jan  8 19:25:19.333: %C4K_IOSSYS-6-IMAGELEVEL: Supervisor booting in image level 'lanbase'
Switch#sh license image level
Module Name        Image level  Priority  Configured  Valid license
--------------------------------------------------------------------
 
WS-X45-SUP7-E     entservices  1         NO          entservices             
                  ipbase       2         NO          ipbase                   
                  lanbase      3         NO          lanbase                   
Module Name        Role           Current Level     Reboot Level
--------------------------------------------------------------------
WS-X45-SUP7-E      Active         lanbase           lanbase          

Text Box. 4

Next, install the previously saved license to bring the system to the previous feature set. In this example, the license is installed from a USB storage disk. The system has to be reloaded to activate the license.

Switch#license install usb0:FOX1349GA3Z_20110108191907574.lic
Installing licenses from "usb0:FOX1349GA3Z_20110108191907574.lic"
Installing...Feature :entservices...Successful:Supported
1/1 licenses were successfully installed
0/1 licenses were existing licenses
0/1 licenses were failed to install
 
Switch#
*Jan  8 20:38:37.136: %LICENSE-6-LICENSE_LEVEL: Module name = WS-X45-SUP7-E Next reboot level = entservices and License = entservices
*Jan  8 20:38:37.195: %LICENSE-6-INSTALL: Feature entservices 1.0 was installed in this device. UDI=WS-C4510R+E:FOX1349GA3Z:Active; StoreIndex=2:Primary License Storage
Switch#
Switch#sh license image level
Module Name        Image level  Priority  Configured  Valid license
--------------------------------------------------------------------
 
WS-X45-SUP7-E      entservices  1         NO          entservices              
                  ipbase       2         NO          ipbase                    
                  lanbase      3         NO          lanbase                   
 
Module Name        Role           Current Level     Reboot Level
--------------------------------------------------------------------
WS-X45-SUP7-E      Active         lanbase            entservices           

Text Box. 5

After reboot, confirm that the system is operational in the entservices license that was installed earlier. Compare the below output with the earlier output of this command.

Switch#sh license image level
Module Name        Image level  Priority  Configured  Valid license
--------------------------------------------------------------------
 
WS-X45-SUP7-E      entservices  1         NO          entservices                  
                   ipbase       2         NO          ipbase                       
                   lanbase      3         NO          lanbase                      
 
Module Name        Role           Current Level     Reboot Level
--------------------------------------------------------------------
WS-X45-SUP7-E      Active         entservices       entservices

Text Box. 6

4.5 License Re-Host, Chassis Upgrade

This section describes the actions to be done to install the license from one chassis to another chassis. Consider a scenario where customer wants to upgrade from a 4507R-E (old) chassis to a 4507R+E (new) chassis for the same Supervisor 7-E or 7L-E system, or where a customer wants to transfer a license from a Catalyst 4500X Series chassis to a new one. This scenario is termed as a license revoke/rehost operation from licensing perspective. The license from the old chassis has to be revoked and re-installed on the new chassis. Below are the steps listed to perform a successful revoke/rehost operation.

Log into the Cisco Licensing Portal - http://www.cisco.com/go/license. Select “Lookup a License” under “Manage License” section.

Enter the Product ID, Serial Number, and device credentials from the old chassis. This will show information about the current license.

Select this license and select “Start License Transfer” on the web page. Enter the number of licenses to be rehosted and select “Continue”.

Enter Product ID, Serial Number from the new chassis. Check “End User Agreement”. Verify and/or edit “Registration Information” and “End User Information”. Select “Continue”.

Verify “Product Information” and “Licensee Information”. Click “Submit” button. Download the Rehost Permission ticket, which is a .lic file, by selecting “Download Permission Ticket” button or from the email sent by Cisco Licensing.

Copy the Rehost Permission Ticket on the flash of the old chassis. For this example, assume that this ticket is copied to the SUP7-E bootflash on the old chassis.

Use the “license revoke bootflash:<Permission ticket> bootflash:<Output Rehost Ticket> for obtaining the Rehost Ticket to upload to the Licensing Portal, as proof of revoke operation done on the old chassis.

A 60-day grace period is also installed on the Supervisor in the older chassis or on the older Catalyst 4500 system to facilitate the transfer to the new chassis.

Go back to the Cisco Licensing portal, and select “Upload Rehost Ticket” under “Manage Licenses”. Copy paste the contents of the Rehost Ticket in the box on the portal, and select “Continue”.

Confirm the License UDI (PID, Serial Number) shown in the next screen, and select “Continue”.

Fill in the License UDI (PID and Serial Number) of the new chassis. In this example, the PID and Serial Number of the new chassis will be used. The Licensee information has to be filled, and select “Continue”.

Review the information in the next screen and select “Submit”. Clicking “Submit” will give the customer the new license available for immediate download, and will also be emailed to the end user.

Continue to install this license in the new chassis. Reboot the system and it will be operational in the previous feature set.

4.6 Chassis Return Material Authorization (RMA) Process

This section details the steps to take in case a chassis has to be RMA-ed.

Log into Cisco Licensing portal with CCO username and password. Select “Register for RMA License” under “RMA License Transfer”.

Select 4500E or 4500-X from the drop down box and select “Continue”.

Enter the Product ID and Serial number of the chassis to be sent back to Cisco. Enter the RMA Number.

Verify the licenses installed on the chassis to be replaced, and select “Continue”.

Enter the Product ID and Serial Number of the chassis which was delivered by Cisco, to be inserted into the production network. Check End User Agreement. Confirm the “Registration Information” and “End User Information”. Select “Continue”.

Verify Product and License Information in the next screen. Select “Submit”.

After the backend system completes the License registration, the license is ready to be downloaded, and is also emailed to the customer.

Proceed with License installation, using the “license install” CLI as mentioned above. The system will need to be reloaded for this license to be effective.

The license that is generated by the backend system is the same as the one which was ordered originally when the system was purchased. For example if the system was purchased at LAN Base level, then the one that is issued by the backend RMA process, is also Lanbase. In other words, the RMA procedure supports like-to-like replacements.

If the system was upgraded to a higher license level, prior to RMA - then - in that case, the license may need to be transferred (rehosted) from the failed chassis to the new chassis to achieve the equivalent software license level on the replacement chassis.

In such cases PIDs and Serial Numbers of both the failed chassis and the replacement chassis need to be available and there is interaction involved with the Cisco Licensing portal, to transfer the license from the failed chassis to the replacement chassis.

5.0 CLI Outputs

The “show license all” shows what licenses are stored in the respective indexes in the store. In the below output, there are two permanent licenses which are stored - ipbase and entservices - in the Primary license storage. The Evaluation license is stored in the Dynamic license storage.

Switch#sh license all
License Store: Primary License Storage
StoreIndex: 1 Feature: ipbase  Version: 1.0
      License Type: Permanent
      License State: Active, Not in Use
      License Count: Non-Counted
      License Priority: Medium
StoreIndex: 2 Feature: entservices  Version: 1.0
      License Type: Permanent
      License State: Active, In Use
      License Count: Non-Counted
      License Priority: Medium
License Store: Dynamic License Storage
StoreIndex: 0 Feature: entservices  Version: 1.0
      License Type: Evaluation
        Evaluation total period: 8 weeks 4 days
        Evaluation period left: 8 weeks 3 days
      License State: Inactive
      License Count: Non-Counted
      License Priority: Low

Text Box. 7

The “show license feature” below, shows what are the available feature licenses with the universal image.

Switch#sh license feature
Feature Name        Enforcement  Evaluation  Clear Allowed  Enabled  
--------------------------------------------------------------------
entservices         true         true        true           true     
ipbase              true         false       true           false    
lanbase             false        false       true           false    
internal_service    true         false       true           false

Text Box. 8

“license clear” command can be used to clear all licenses which are specified in the command, and which are not in use, as seen below:

Switch#license clear ipbase
Feature: ipbase
    1     License Type: Permanent
   License State: Active, Not in Use
   License Addition: Exclusive
   License Count: Non-Counted
   Comment:
   Store Index: 1
   Store Name: Primary License Storage
 
 
Are you sure you want to clear? (yes/[no]): yes
Switch#
*Jan 11 14:20:00.936: %LICENSE-6-LICENSE_LEVEL: Module name = WS-X45-SUP7-E Next reboot level = entservices and License = entservices
*Jan 11 14:20:00.962: %LICENSE-6-REMOVE: Feature ipbase 1.0 was removed from this device, UDI=WS-C4510R+E:FOX1349GA3Z:Active, StoreIndex=0:Primary License Storage
Switch#

Text Box. 9

As can be seen from the command execution below, where an attempt is being made to clear the entservices license, which is in use. The system does not allow this operation to be successful.

Switch#license clear entservices
Feature: entservices
    1     License Type: Permanent
   License State: Active, In Use
   License Addition: Exclusive
   License Count: Non-Counted
   Comment:
   Store Index: 2
   Store Name: Primary License Storage
 
 
Are you sure you want to clear? (yes/[no]): yes
%Clear failed due to license in use
   Release count             0
   Global Notify count       2

Text Box. 10

Below command lists out the license which is actively in use by the system currently.

Switch#sh license in-use
License Store: Primary License Storage
StoreIndex: 2 Feature: entservices  Version: 1.0
      License Type: Permanent
      License State: Active, In Use
      License Count: Non-Counted
      License Priority: Medium
License Store: Dynamic License Storage

Text Box. 11

Below command output lists all the evaluation licenses which are stored in the system currently.

Switch#sh license evaluation
License Store: Primary License Storage
License Store: Dynamic License Storage
StoreIndex: 0 Feature: entservices  Version: 1.0
      License Type: Evaluation
        Evaluation total period: 8 weeks 4 days
        Evaluation period left: 8 weeks 3 days
      License State: Inactive
      License Count: Non-Counted
      License Priority: Low

Text Box. 12

Below command lists all the permanent licenses which are stored in the system currently.

Switch#sh license permanent
License Store: Primary License Storage
StoreIndex: 2 Feature: entservices  Version: 1.0
      License Type: Permanent
      License State: Active, In Use
      License Count: Non-Counted
      License Priority: Medium
License Store: Dynamic License Storage

Text Box. 13

Below command lists all the licenses which might be expiring, and shows the time available.

Switch#sh license expiring
License Store: Primary License Storage
License Store: Dynamic License Storage
StoreIndex: 0 Feature: entservices  Version: 1.0
      License Type: Evaluation
        Evaluation total period: 8 weeks 4 days
        Evaluation period left: 8 weeks 3 days
      License State: Inactive
      License Count: Non-Counted
      License Priority: Low

Text Box. 14

“show license summary” lists out all the licenses stored in different indexes in the storage on this system. It also lists out the feature, and type of licenses available in the store.

Switch#sh license summary
Index 0   Feature: entservices
          Period left: Life time
          License Type: Permanent
          License State: Active, In Use
          License Count: Non-Counted
          License Priority: Medium
Index 1   Feature: ipbase
          Period left: 0 seconds
Index 2   Feature: lanbase
          Period left: 0 seconds
Index 3   Feature: internal_service
          Period left: 0 seconds

Text Box. 15

“show license statistics” command shows the licensing operations performed on the system with the results of each operation. As can be seen from below output, there is one successful installation operation, with one operations each of clear, save and save credentials of the license.

Switch#sh license statistics
           Administrative statistics
   Install success count:       1
   Install failure count:       0
   Install duplicate count:     0
   Comment add count:           0
   Comment delete count:        0
   Clear count:                 1
   Save count:                  1
   Save cred count:             1
 
           Client status
   Request success count     1
   Request failure count     0

Text Box. 16

6.0 Best Practices

The best practices are recommended for post-deployment operations once the Supervisor 7-E, 7L-E or Cisco Catalyst 4500-X Series switch has been installed and deployed in the network. The post-deployment operations include maintenance scenarios like chassis upgrades, supervisor swaps across chassis, chassis RMAs, supervisor RMAs, etc. The best practices will alleviate challenges when dealing with exceptions like RMA, or swaps, mentioned above.

Once a license is installed on the switch.

Backup the license to a network-accessible central location with a filename containing the chassis serial number. This is shown in Figure 22.

Backup the device credentials to a network-accessible central location with a filename containing the chassis serial number. This procedure is shown in Figure 23.

The license backup will help in scenarios of supervisor swap across chassis, and supervisor RMA.

The device credentials backup will help in scenarios of license lookup and license re-hosting operations.

7.0 References

1.     Download the Demo license for the Catalyst 4500E Supervisor 7-E: https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet?FormId=586

2.     Catalyst 4500E Licensing FAQ: http://bock-bock.cisco.com/wiki/Cat4K:licensing

3.     More information on Cisco SAL: http://www.cisco.com/go/license

4.     More information on Cisco License Manager: http://www.cisco.com/go/clm

5.     Cisco Software Activation Conceptual Overview: http://www.cisco.com/en/US/docs/ios/csa/configuration/guide/csa_overview.html

6.     Cisco Software Activation Tasks and Commands: http://www.cisco.com/en/US/docs/ios/csa/configuration/guide/csa_commands.html

7.     Cisco License Manager Deployment: A Quick Start: http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps9677/guide_clm_deployment.html

8.     Cisco Software Activation: Simplifying Software Deployment and License Management: http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps9677/whitepaper_cisco_sw_license.html

9.     Maintenance Provider Guidelines for Managing Software Activation: http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps9677/white_paper_maintenance_activation.html

10.   Cisco Software Activation: Channel Partners Guidelines for Managing Software Activation: http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps9677/white_paper_cisco_sw_activation.html