how to upload cisco license to air-ct2500 k9controller

Managing Licenses

Installing and Configuring Licenses

Information About Installing and Configuring Licenses

Yous can order Cisco 5500 Series Controllers with support for 12, 25, fifty, 100, 250 or 500 admission points as the controller's base capacity. You can add together boosted admission betoken capacity through capacity adder licenses available at 25, 50, 100 and 250 access point capacities. You lot can add together the capacity adder licenses to any base license in any combination to go far at the maximum capacity of 500 access points. The base and adder licenses are supported through both rehosting and RMAs.

For information almost upgrade and capacity adder licenses, see the product data sheet of your controller model.

Guidelines and Limitations About Licenses

The base license supports the standard base software fix, and the premium software fix is included as function of the base feature prepare, which includes this functionality:

Datagram Ship Layer Security (DTLS) data encryption for added security beyond remote WAN and LAN links.

The Availability of data DTLS is as follows: Cisco 5500 Series Controller—The Cisco 5500 Series Controller will exist available with two licensing options: One with data DTLS capabilities and another image without data DTLS. 2500, WiSM2—These platforms by default will not incorporate DTLS. To turn on information DTLS, you must install a license. These platforms volition have a single epitome with data DTLS turned off. To use data DTLS you will demand to have a license.

Support for OfficeExtend access points, which are used for secure mobile teleworking.

All features included in a Wireless LAN Controller WPLUS license are now included in the base license. At that place are no changes to WCS BASE and PLUS licensing. These WPlus license features are included in the base license:

OfficeExtend AP

Enterprise Mesh

CAPWAP Data Encryption

The licensing change can bear on features on your wireless LAN when you upgrade or downgrade software releases, so you should be enlightened of these guidelines:

If y'all have a WPlus license and you upgrade from 6.0.ten.x to seven.x.x.x, your license file contains both Basic and WPlus license features. You won't see any disruption in feature availability and operation.

If you have a WPlus license and you downgrade from 7.x.x.x to 6.0.196.0 or vi.0.188.0 or vi.0.182.0, your license file contains but base license, and you lot will lose all WPlus features.

If you have a base license and you downgrade from half-dozen.0.196.0 to 6.0.188.0 or half-dozen.0.182.0, when you downgrade, you lot lose all WPlus features.

In the controller software 7.0.116.0 and afterward releases, the AP association trap is ciscoLwappApAssociated. In prior releases, the trap was bsnAPAssociated.

The ap-count licenses and their corresponding image-based licenses are installed together. The controller keeps track of the licensed access point count and does non allow more than the number of access points to associate to it.

The Cisco 5500 Serial Controller is shipped with both permanent and evaluation base of operations and base of operations-ap-count licenses. If desired, you tin activate the evaluation licenses, which are designed for temporary apply and set to elapse later 60 days.

No licensing steps are required after you receive your Cisco 5500 Series Controller because the licenses you ordered are installed at the factory. In addition, licenses and product authority keys (PAKs) are preregistered to serial numbers. However, every bit your wireless network evolves, you might want to add support for boosted admission points or upgrade from the standard software set to the base software gear up. To do so, you lot demand to obtain and install an upgrade license.
Obtaining an Upgrade or Capacity Adder License

This department describes how to go an upgrade or capacity adder license.

Information Almost Obtaining an Upgrade or Capacity Adder License

Obtaining and Registering a PAK Certificate

Information Nigh Obtaining an Upgrade or Capacity Adder License

A document with a product authorization cardinal (PAK) is required before you can obtain an upgrade license.

You can utilise the capacity adder licenses to increase the number of admission points supported past the controller up to a maximum of 500 admission points. The chapters adder licenses are available in access indicate capacities of ten, 25, l, 100 and 250 access points. Yous can add these licenses to any of the base capacity licenses of 12, 25, 50, 100 and 250 admission points.

For example, if your controller was initially ordered with support for 100 access points (base license AIR-CT5508-100-K9), yous could increase the chapters to 500 admission points by purchasing a 250 access indicate, 100 admission point, and a fifty admission point additive capacity license (LIC-CT5508-250A, LIC-CT5508-100A, and LIC-CT5508-50A).

Yous can find more data on ordering capacity adder licenses at this URL: http://www.cisco.com/en/The states/products/ps10315/products_data_sheets_list.html

Note

If yous skip whatsoever tiers when upgrading (for example, if you lot practise not install the -25U and -50U licenses along with the -100U), the license registration for the upgraded capacity fails.

For a single controller, you can order different upgrade licenses in 1 transaction (for case, -25U, -50U, -100U, and -250U), for which y'all receive one PAK with one license. Then you have merely one license (instead of four) to install on your controller.

If you lot take multiple controllers and want to upgrade all of them, y'all can society multiple quantities of each upgrade license in 1 transaction (for example, you can gild 10 each of the -25U, -50U, -100U, and -250 upgrade licenses), for which you lot receive one PAK with one license. You can go on to annals the PAK for multiple controllers until it is wearied.

For more data about the base license SKUs and chapters adder licenses, see the respective controller'southward data sheet.
Obtaining and Registering a PAK Certificate
Step i Lodge the PAK certificate for an upgrade license through your Cisco channel partner or your Cisco sales representative, or order it online at this URL:
http://world wide web.cisco.com/go/ordering

Stride 2 If you are ordering online, begin by choosing the primary upgrade SKU L-LIC-CT5508-UPG or LIC CT5508-UPG. Then, cull whatever number of the following options to upgrade one or more controllers under i PAK. After you lot receive the certificate, utilize i of 2 methods to register the PAK:

Cisco License Manager (CLM)—This method automates the procedure of obtaining licenses and deploying them on Cisco devices. For deployments with more than 5 controllers, we recommend using CLM to register PAKs and install licenses. You can also use CLM to rehost or RMA a license.

Notation
You cannot use CLM to change the licensed feature set up or activate an ap-count evaluation license. To perform these operations, you must follow the instructions in the Activating an AP-Count Evaluation License department. Because you can use CLM to perform all other license operations, you can disregard the remaining licensing information in this chapter except these two sections and the Configuring the License Agent section if y'all want your controller to utilise HTTP to communicate with CLM.

Licensing portal—This culling method enables y'all to manually obtain and install licenses on your controller. If you want to use the licensing portal to register the PAK, follow the instructions in Step 3.
Step 3
Use the licensing portal to annals the PAK every bit follows:
Become to http://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet

On the primary Product License Registration page, enter the PAK mailed with the certificate in the Product Authorization Cardinal (PAK) text box and click Submit.

On the Validate Features page, enter the number of licenses that y'all desire to register in the Qty text box and click Update.
To determine the controller's product ID and series number, cull Controller > Inventory on the controller GUI or enter the show license udi command on the controller CLI.
Information similar to the following appears on the controller CLI:
                                         Device# PID                     SN                      UDI ------- -------------------- ----------------------- ----------------------- *0      AIR-CT5508-K9 	 	 	 	 CW1308L030		 	 	 	 	 AIR-CT5508-K9:FCW1308L030                                      
On the Designate Licensee folio, enter the product ID and serial number of the controller on which you plan to install the license, read and accept the weather condition of the cease-user license understanding (EULA), complete the residual of the text boxes on this page, and click Submit.

On the End and Submit page, verify that all information is right and click Submit.

When a message appears indicating that the registration is complete, click Download License. The license is due east-mailed within 1 60 minutes to the address that you specified.

When the e-mail arrives, follow the instructions provided.

Re-create the license file to your TFTP server.
Installing a License

Installing a License (GUI)

Footstep 1 Choose Management > Software Activation > Commands to open the License Commands page.

Stride ii From the Action drop-down list, choose Install License. The Install License from a File department appears.

Step 3 In the File Proper name to Install text box, enter the path to the license (*.lic) on the TFTP server.

Step four Click Install License. A message appears to show whether the license was installed successfully. If the installation fails, the message provides the reason for the failure, such as the license is an existing license, the path was not institute, the license does not vest to this device, yous practise not have right permissions for the license, and then on.

Step v If the cease-user license agreement (EULA) acceptance dialog box appears, read the agreement and click Accept to accept the terms of the agreement.

Note
Typically, yous are prompted to have the EULA for evaluation, extension, and rehost licenses. The EULA is also required for permanent licenses, but information technology is accustomed during license generation.

Stride 6 Save a backup copy of all installed licenses as follows:

From the Action drop-downwards list, choose Salvage License.

In the File Name to Save text box, enter the path on the TFTP server where you want the licenses to be saved.

Note
You lot cannot save evaluation licenses.

Click Salve Licenses.

Stride vii Reboot the controller.

Installing a License (CLI)

Step one Install a license on the controller by inbound this control:
license install url

where url is tftp:// server_ip / path / filename .

Note
To remove a license from the controller, enter the license clear license_name command. For example, you might desire to delete an expired evaluation license or whatsoever unused license. Yous cannot delete unexpired evaluation licenses, the permanent base paradigm license, or licenses that are in employ by the controller.

Step 2 If you are prompted to accept the end-user license understanding (EULA), read and accept the terms of the agreement.

Notation
Typically, you lot are prompted to have the EULA for evaluation, extension, and rehost licenses. The EULA is also required for permanent licenses, but information technology is accepted during license generation.

Step 3 Add comments to a license or delete comments from a license by entering this control:
license annotate { add | delete} license_name comment_string

Stride four Save a backup re-create of all installed licenses by entering this command:
license salvage url

where url is tftp:// server_ip/ path/ filename.

Step 5 Reboot the controller by inbound this control:
reset system .

Viewing Licenses

Viewing Licenses (GUI)

Step 1 Choose to open the Licenses page.
This page lists all of the licenses installed on the controller. For each license, it shows the license blazon, expiration, count (the maximum number of access points allowed for this license), priority (depression, medium, or high), and status (in use, not in use, inactive, or EULA not accepted).

Note
Controller platforms do not support the condition of "grace period" or "extension" equally a license type. The license status will always show "evaluation" even if a grace menstruation or an extension evaluation license is installed.

Note
If you ever want to remove a license from the controller, hover your cursor over the blue driblet-down arrow for the license and click Remove. For case, you might want to delete an expired evaluation license or any unused license. Y'all cannot delete unexpired evaluation licenses, the permanent base prototype license, or licenses that are in use by the controller.

Footstep 2 Click the link for the desired license to view more details for a particular license. The License Particular page appears.
This folio shows the post-obit boosted information for the license:

The license type (permanent, evaluation, or extension)

The license version

The status of the license (in use, not in use, inactive, or EULA non accustomed)

The length of fourth dimension earlier the license expires

Note
Permanent licenses never expire.

Whether the license is a built-in license

The maximum number of admission points allowed for this license

The number of access points currently using this license

Footstep 3 If you want to enter a comment for this license, blazon it in the Annotate text box and click Apply.

Step 4 Click Save Configuration to salve your changes.
Viewing Licenses (CLI)
Before You Begin
See the license level, license type, and number of access points licensed on the controller by entering this command: show sysinfo Information similar to the following appears:
                               Manufacturer'due south Name.............................. Cisco Systems Inc. Product Name..................................... Cisco Controller Product Version.................................. 7.0 RTOS Version..................................... seven.0 Bootloader Version............................... 5.2 Emergency Image Version.......................... N/A Build Blazon....................................... DATA + WPS Organisation Name...................................... Cisco 69 Arrangement Location.................................. na System Contact................................... abc@cisco.com Organization ObjectID.................................. 1.iii.6.1.iv.1.14179.i.1.4.three IP Address....................................... 10.10.10.ten System Up Time................................... three days 1 hrs 12 mins 42 secs System Timezone Location......................... CurrentBoot License Level..........................base CurrentBoot License Type...........................Permanent NextBoot License Level............................base NextBoot License Type.............................Permanent Operating Environment............................ Commercial (0 to 40 C) Internal Temp Warning Limits....................... 0 to 65 C Internal Temperature............................. +40 C Land of 802.11b Network......................... Enabled Country of 802.11a Network......................... Enabled Number of WLANs.................................. 4 Number of Active Clients......................... 0 Burned-in MAC Address............................ 00:1A:6D:DD:1E:40 Crypto Accelerator i............................. Absent Crypto Accelerator two............................. Absent Power Supply one................................... Absent-minded Power Supply 2................................... Present, OK Maximum number of APs supported.................. 12                            
Note

The Operating Surroundings and Internal Temp Alarm Limits data are not displayed for Cisco Flex 7500 Series Controllers.
Encounter a brief summary of all active licenses installed on the controller by entering this command: show license summary Information similar to the post-obit appears:
                               Index 1 Feature: wplus         Menstruation left: 0 minute 0 2nd Alphabetize ii Characteristic: wplus-ap-count 		Period left: 0 minute 0 second Index3 		Feature: base 		Menstruum left: Life time 		License Blazon: Permanent 		License Country: Active, In Use 		License Count: Non-Counted 		License Priority: Medium Index 4 Feature: base-ap-count 		Period left: 6 weeks, 4 days 		License Type: Evaluation 		License Country: Active, In Use 		License Count: 250/250/0 		License Priority: High                            
Run across all of the licenses installed on the controller by entering this command: show license all Data similar to the post-obit appears:
                               License Store: Primary License Storage StoreIndex:  one  Characteristic: base   Version: 1.0         License Type: Permanent         License State: Active, Non in Use         License Count: Non-Counted         License Priority: Medium  StoreIndex:  three  Characteristic: base-ap-count   Version: 1.0         License Blazon: Evaluation         License State: Active, In Use             Evaluation total flow:  8 weeks  4 days             Evaluation menses left:  8 weeks  3 days         License Count: 250/0/0         License Priority: High                            
See the details for a particular license by entering this command: show license item license_name Information similar to the following appears:
                               Index:  i       Feature: base-ap-count   Version: one.0         License Type: Permanent         License Country: Active, Not in Employ         License Count: 12/0/0         License Priority: Medium         Shop Index: 0         Store Name: Primary License Storage  Index:  2       Characteristic: base of operations-ap-count   Version: 1.0         License Type: Evaluation         License Land: Inactive             Evaluation total catamenia:  viii weeks  4 days             Evaluation menses left:  eight weeks  four days         License Count: 250/0/0         License Priority: Low         Store Index: 3         			Shop Proper noun: Evaluation License Storage                            
Run into all expiring, evaluation, permanent, or in-use licenses by entering this command: evidence license { expiring | evaluation | permanent | in-utilize} Information similar to the following appears for the show license in-use command:
                               StoreIndex:  ii  Feature: base-ap-count   Version: i.0         License Type: Permanent         License State: Active, In Apply         License Count: 12/12/0         License Priority: Medium StoreIndex:  3  Feature: base Version: 1.0         License Blazon: Permanent         License State: Active, In Use         License Count: Not-Counted License Priority: Medium                            
Note

Controller platforms practice not support the status of "grace flow" or "extension" as a license blazon. The license status will always show "evaluation" even if a grace menstruation or an extension evaluation license is installed.
Come across the maximum number of access points immune for this license on the controller, the number of access points currently joined to the controller, and the number of access points that can still bring together the controller by entering this control: prove license capacity Information like to the post-obit appears:
                               Licensed Feature    Max Count      Electric current Count       Remaining Count ----------------    ---------      -------------       --------------- AP Count              250              4                    246                            
Come across statistics for all licenses on the controller by entering this command: evidence license statistics

See a summary of license-enabled features past entering this command: show license feature
Troubleshooting Licensing Bug

Configure debugging of license agent by entering this command:

debug license agent {errors | all} {enable | disable}

Configure debugging of licensing cadre events and core errors by entering this control:

debug license cadre {all | errors | events} {enable | disable}

Configure debugging of licensing errors by entering this command:

debug license errors {enable | disable}

Configure debugging of licensing events past entering this command:

debug license events {enable | disable}

Activating an AP-Count Evaluation License

Information Well-nigh Activating an AP-Count Evaluation License

If you are considering upgrading to a license with a higher access point count, yous tin endeavor an evaluation license before upgrading to a permanent version of the license. For instance, if you are using a permanent license with a 50-access-betoken count and desire to endeavor an evaluation license with a 100-access-point count, you can try out the evaluation license for 60 days.

AP-count evaluation licenses are set to depression priority by default so that the controller uses the ap-count permanent license. If you want to try an evaluation license with an increased access point count, you must change its priority to high. If you no longer want to take this higher capacity, you lot tin can lower the priority of the ap-count evaluation license, which forces the controller to utilize the permanent license.

Annotation

To preclude disruptions in operation, the controller does not switch licenses when an evaluation license expires. You must reboot the controller in order to return to a permanent license. Following a reboot, the controller defaults to the aforementioned feature set level as the expired evaluation license. If no permanent license at the same feature set level is installed, the controller uses a permanent license at some other level or an unexpired evaluation license.

Activating an AP-Count Evaluation License (GUI)

Step 1 Choose to open up the Licenses page.
The Status column shows which licenses are currently in use, and the Priority column shows the current priority of each license.

Step 2 Actuate an ap-count evaluation license every bit follows:

Click the link for the ap-count evaluation license that you want to activate. The License Item folio appears.

Cull High from the Priority drop-downwards list and click Fix Priority.

Annotation
Y'all tin can set the priority just for ap-count evaluation licenses. AP-count permanent licenses ever accept a medium priority, which cannot be configured.

Click OK when prompted to ostend your decision most changing the priority of the license.

When the EULA appears, read the terms of the agreement and and then click Accept.

When prompted to reboot the controller, click OK.

Reboot the controller in club for the priority change to take upshot.

Click Licenses to open the Licenses page and verify that the ap-count evaluation license now has a high priority and is in use. You tin can use the evaluation license until it expires.

Step 3 If yous decide to stop using the ap-count evaluation license and want to revert to using an ap-count permanent license, follow these steps:

On the Licenses folio, click the link for the ap-count evaluation license that is in apply.

Choose Low from the Priority drop-downwardly listing and click Set Priority.

Annotation
You can gear up the priority only for ap-count evaluation licenses. AP-count permanent licenses always have a medium priority, which cannot be configured.

Click OK when prompted to ostend your decision about irresolute the priority of the license.

When the EULA appears, read the terms of the agreement so click Accept.

When prompted to reboot the controller, click OK.

Reboot the controller in order for the priority change to take consequence.

Click Licenses to open the Licenses folio and verify that the ap-count evaluation license now has a depression priority and is not in apply. Instead, the ap-count permanent license should be in use.
Activating an AP-Count Evaluation License (CLI)
Step 1
See the electric current status of all the licenses on your controller past entering this command:
evidence license all

Data similar to the following appears:
                                   License Store: Principal License Storage StoreIndex:  0  Feature: base-ap-count   Version: 1.0         License Type: Permanent         License Land: Active, In Use         License Count: 12/0/0         License Priority: Medium StoreIndex:  i  Feature: base   Version: 1.0         License Type: Permanent         License Country: Active, In Use         License Count: Not-Counted         License Priority: Medium StoreIndex:  2  Feature: base   Version: ane.0         License Type: Evaluation         License State: Inactive             Evaluation total period:  viii weeks  4 days             Evaluation period left:  8 weeks  4 days         License Count: Non-Counted         License Priority: Depression StoreIndex:  three  Feature: base-ap-count   Version: ane.0         License Type: Evaluation 		License Country: Inactive             Evaluation full period:  8 weeks  4 days             Evaluation period left:  eight weeks  4 days         License Count: 250/0/0         		 	License Priority: Low                                
The License State text box shows the licenses that are in use, and the License Priority text box shows the current priority of each license.

Notation
In the 7.2.110.0 release, the command output displays the full in-utilise count for active base-ap-count license even though at that place are no APs connected.
Step 2 Actuate an ap-count evaluation license as follows:

To raise the priority of the base-ap-count evaluation license, enter this command:
license alter priority license_name loftier

Note
You can set the priority only for ap-count evaluation licenses. AP-count permanent licenses always accept a medium priority, which cannot be configured.

To reboot the controller in order for the priority change to accept effect, enter this command:
reset system

To verify that the ap-count evaluation license now has a high priority and is in employ, enter this command:
prove license all

Y'all can use the evaluation license until information technology expires.

Step iii If yous make up one's mind to stop using the ap-count evaluation license and desire to revert to using an ap-count permanent license, follow these steps:

To lower the priority of the ap-count evaluation license, enter this command:
license modify priority license_name low

To reboot the controller in order for the priority change to take consequence, enter this control:
reset system

To verify that the ap-count evaluation license now has a low priority and is not in use, enter this command:
show license all

Instead, the ap-count permanent license should exist in use.
Configuring Correct to Use Licensing

Information Nigh Right to Use Licensing

Right to Utilise (RTU) licensing is a model in which licenses are not tied to a unique device identifier (UDI), product ID, or serial number. Employ RTU licensing to enable a desired AP license count on the controller after you take the End User License Agreement (EULA). This allows you lot to add AP counts on a controller interacting with external tools.

RTU licensing is supported only on Cisco Flex 7500 Series and Cisco 8500 Series Wireless LAN Controllers.

In the RTU licensing model, the following types of licenses are available:

Permanent or base licenses—These licenses are programmed into the controller hardware at the time of manufacturing. These are base count licenses that cannot exist deleted or transferred.

Adder licenses—These are wireless admission betoken count licenses that you tin can activate by accepting the RTU EULA. The EULA states that you are obliged to purchase the specified access point count licenses at the fourth dimension of activation. Y'all must actuate these licenses for the purchased admission points count and take the EULA.

You can remove an adder license from one controller and transfer the license to some other controller in the same product family. For case, an adder license such as LIC-CT7500-100A can be transferred (partially or fully) from one Cisco Flex 7500 Series controller to another Cisco Flex 7500 Series controller.

Note

Licenses embedded in the controller at the time of shipment is non transferrable.

Evaluation licenses—These are demo or trial way licenses that are valid for 90 days. Fifteen days prior to the expiry of the 90-day period, you are notified almost the requirement to buy the permanent license. These evaluation licenses are installed with the license image. You lot tin can activate the evaluation licenses anytime with a command. A EULA is prompted to yous subsequently you run the activation command on the controller CLI. The EULA states that you are obligated to pay for the specified license count within 90 days of usage. Countdown starts subsequently y'all accept the EULA.

Whenever you add or delete an access point adder license on the controller, y'all are prompted with an RTU EULA. You lot tin can either accept or decline the RTU EULA for each add together or delete operation.

For high-availability (HA) controllers when y'all enable HA, the controllers synchronize with the enabled license count of the primary controller and back up loftier availability for up to the license count enabled on the chief controller.

You can view the RTU licenses through the controller GUI or CLI. You tin too view these licenses across multiple wireless controllers through Cisco Prime Infrastructure.

Configuring Right to Use Licensing (GUI)

Step 1 Choose to open the Licenses page.

Stride 2 In the Adder License area, choose to add or delete the number of APs that an AP license can support, enter a value, and click Gear up Count.

Pace iii Click Salvage Configuration.

Configuring Right to Use Licensing (CLI)

To add or delete the number of APs that an AP license can support, enter this command: license {add together | delete} ap-count count

To add together or delete a license for a feature, enter this command: license {add | delete} feature license_name

To activate or deactivate an evaluation AP count license, enter this command: license {activate | deactivate} ap-count eval

Note

When you lot actuate the license, you are prompted to take or refuse the End User License Understanding (EULA) for the given license. If you activate a license that supports fewer number of APs than the current number of APs continued to the controller, the activation command fails.

To activate or conciliate a characteristic license, enter this command: license {activate | conciliate} feature license_name

To see the licensing data, enter this control: show license all

Rehosting Licenses

This department describes how to rehost licenses.

Information About Rehosting Licenses

Rehosting a License

Transferring Licenses to a Replacement Controller later an RMA

Information About Rehosting Licenses

Revoking a license from one controller and installing it on another is called rehosting. You might desire to rehost a license in social club to change the purpose of a controller. For example, if you desire to move your OfficeExtend or indoor mesh access points to a different controller, you could transfer the adder license from ane controller to another controller of the aforementioned model, say from one 5500 serial controller to another 5500 series controller (intramodel transfer). This can exist washed in the case of RMA or a network rearchitecture that requires you to transfer licenses from i apparatus to another. Information technology is not possible to rehost base of operations licenses in normal scenarios of network rearchitecture. The just exception where the transfer of base licenses is allowed is for RMA when you lot get a replacement hardware when your existing appliance has a failure.

Evaluation licenses cannot be rehosted.

In club to rehost a license, you must generate credential information from the controller and use it to obtain a permission ticket to revoke the license from the Cisco licensing site. Adjacent, you must obtain a rehost ticket and employ it to obtain a license installation file for the controller on which you want to install the license.

Notation

A revoked license cannot be reinstalled on the same controller.

Rehosting a License

Rehosting a License (GUI)

Footstep ane Choose to open the License Commands page.

Step 2 From the Activeness drib-downwardly list, choose Rehost. The Revoke a License from the Device and Generate Rehost Ticket area appears.

Stride 3 In the File Name to Save Credentials text box, enter the path on the TFTP server where you lot want the device credentials to be saved and click Save Credentials.

Pace four To obtain a permission ticket to revoke the license, follow these steps:

Click Cisco Licensing (https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet).

On the Product License Registration page, click Await Up a License under Manage Licenses.

Enter the product ID and serial number for your controller.

Note
To find the controller'due south production ID and series number, cull on the controller GUI.

Open the device credential information file that you saved in Pace 3 and re-create and paste the contents of the file into the Device Credentials text box.

Enter the security code in the blank box and click Go along.

Choose the licenses that you want to revoke from this controller and click Start License Transfer.

On the Rehost Quantities page, enter the number of licenses that you want to revoke in the To Rehost text box and click Continue.

On the Designate Licensee page, enter the product ID and series number of the controller for which you plan to revoke the license, read and accept the conditions of the End User License Agreement (EULA), consummate the rest of the text boxes on this folio, and click Continue.

On the Review and Submit page, verify that all data is right and click Submit.

When a message appears indicating that the registration is complete, click Download Permission Ticket. The rehost permission ticket is e-mailed within one hr to the address that you specified.

After the e-post arrives, copy the rehost permission ticket to your TFTP server.

Step 5 Apply the rehost permission ticket to revoke the license from this controller and generate a rehost ticket equally follows:

In the Enter Saved Permission Ticket File Proper noun text box, enter the TFTP path and filename (*.lic) for the rehost permission ticket that you generated in Step 4.

In the Rehost Ticket File Name text box, enter the TFTP path and filename (*.lic) for the ticket that will be used to rehost this license on another controller.

Click Generate Rehost Ticket.

When the Stop User License Agreement (EULA) acceptance dialog box appears, read the agreement and click Have to take the terms of the agreement.

Step 6 Use the rehost ticket generated in Step 5 to obtain a license installation file, which can then exist installed on some other controller as follows:

Click Cisco Licensing.

On the Production License Registration folio, click Upload Rehost Ticket under Manage Licenses.

On the Upload Ticket page, enter the rehost ticket that y'all generated in Step 5 in the Enter Rehost Ticket text box and click Proceed.

On the Validate Features page, verify that the license data for your controller is correct, enter the rehost quantity, and click Continue.

On the Designate Licensee folio, enter the product ID and serial number of the controller on which yous programme to use the license, read and have the conditions of the End User License Agreement (EULA), complete the residue of the text boxes on this page, and click Continue.

On the Review and Submit page, verify that all data is correct and click Submit.

When a message appears indicating that the registration is complete, click Download License. The rehost license cardinal is due east-mailed inside 1 hour to the address that you specified.

Later on the e-mail arrives, copy the rehost license cardinal to your TFTP server.

Follow the instructions in the Installing a License section to install this on another controller.

Rehosting a License (CLI)

Step 1 Save device credential data to a file by inbound this command:
license salve credential url

where url is tftp:// server_ip/ path/ filename.

Stride 2 Obtain a permission ticket to revoke the license as follows:

Go to https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet. The Product License Registration page appears.

Nether Manage Licenses, click Wait Up a License.

Enter the product ID and serial number for your controller.

Note
To discover the controller's product ID and serial number, enter the show license udi command on the controller CLI.

Open the device credential data file that you saved in Step 1 and re-create and paste the contents of the file into the Device Credentials text box.

Enter the security code in the blank box and click Go on.

Choose the licenses that y'all want to revoke from this controller and click Start License Transfer.

On the Rehost Quantities folio, enter the number of licenses that you desire to revoke in the To Rehost text box and click Continue.

On the Designate Licensee page, enter the product ID and serial number of the controller for which you lot program to revoke the license, read and have the weather of the End-User License Agreement (EULA), complete the rest of the text boxes on this folio, and click Continue.

On the Review and Submit page, verify that all information is right and click Submit.

When a message appears indicating that the registration is complete, click Download Permission Ticket. The rehost permission ticket is due east-mailed within 1 hour to the address that you specified.

After the e-mail arrives, re-create the rehost permission ticket to your TFTP server.

Footstep 3 Use the rehost permission ticket to revoke the license from this controller and generate a rehost ticket as follows:

To revoke the license from the controller, enter this control:
license revoke permission_ticket_url

where permission_ticket_url is tftp:// server_ip/ path/ filename.

To generate the rehost ticket, enter this command:
license revoke rehost rehost_ticket_url

where rehost_ticket_url is tftp:// server_ip/ path/ filename.

If prompted, read and accept the terms of the Stop-User License Understanding (EULA).

Footstep 4 Use the rehost ticket generated in Step three to obtain a license installation file, which can and then be installed on another controller equally follows:

Get to https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet.

On the Product License Registration folio, click Upload Rehost Ticket under Manage Licenses.

On the Upload Ticket page, enter the rehost ticket that you lot generated in Footstep iii in the Enter Rehost Ticket text box and click Go on.

On the Validate Features page, verify that the license information for your controller is right, enter the rehost quantity, and click Continue.

On the Designate Licensee page, enter the product ID and serial number of the controller on which you plan to use the license, read and have the conditions of the End-User License Agreement (EULA), consummate the residue of the text boxes on this page, and click Go on.

On the Review and Submit page, verify that all information is right and click Submit.

When a bulletin appears indicating that the registration is complete, click Download License. The rehost license key is e-mailed within ane hour to the accost that you specified.

Afterwards the email arrives, re-create the rehost license central to your TFTP server.

Follow the instructions in the Installing a License (GUI) department to install this license on another controller.

Transferring Licenses to a Replacement Controller later on an RMA

Data Well-nigh Transferring Licenses to a Replacement Controller after an RMA

If you return a Cisco 5500 Series Controller to Cisco as part of the Render Material Authorization (RMA) process, you must transfer that controller'south licenses within threescore days to a replacement controller that you receive from Cisco.

Replacement controllers come preinstalled with the following licenses: permanent base and evaluation base, base-ap-count. No other permanent licenses are installed. The SKU for replacement controllers is AIR-CT5508-CA-K9.

Because licenses are registered to the serial number of a controller, yous tin utilise the licensing portal on Cisco.com to request that the license from your returned controller exist revoked and authorized for use on the replacement controller. After your asking is approved, you can install the quondam license on the replacement controller. Whatsoever additional ap-count licenses if installed in the returned controller has to be rehosted on the replacement controller. Before you begin, you lot need the product ID and serial number of both the returned controller and the replacement controller. This information is included in your purchase records.

Note

The evaluation licenses on the replacement controller are designed for temporary apply and elapse afterwards 60 days. To prevent disruptions in operation, the controller does not switch licenses when an evaluation license expires. You must reboot the controller in club to return to a permanent license. If the evaluation licenses expire before you transfer the permanent licenses from your defective controller to your replacement controller, the replacement controller remains upward and running using the permanent base license, but access points are no longer able to join the controller.

Transferring a License to a Replacement Controller subsequently an RMA

Pace 1 Browse to https://sso.cisco.com/autho/forms/CDClogin.html.

Step 2 On the Product License Registration page, choose .

Stride 3 Click Specify Device and so cull the controller model from the Product Family drop-down list.

Step 4 Complete the on-screen instructions to generate the license file.
The license is provided online or in an e-mail.

Step 5 Copy the license file to the TFTP server.

Footstep six Install the license past choosing .

Configuring the License Amanuensis

Information About Configuring the License Agent

If your network contains diverse Cisco-licensed devices, you might want to consider using the Cisco License Director (CLM) to manage all of the licenses using a single application. CLM is a secure client/server awarding that manages Cisco software licenses network wide.

The license agent is an interface module that runs on the controller and mediates between CLM and the controller's licensing infrastructure. CLM can communicate with the controller using diverse channels, such as HTTP, Telnet, and so on. If you want to employ HTTP equally the communication method, you must enable the license agent on the controller.

The license amanuensis receives requests from CLM and translates them into license commands. It also sends notifications to CLM. It uses XML messages over HTTP or HTTPS to receive the requests and send the notifications. For example, CLM sends a license install command, and the agent notifies CLM after the license expires.

Configuring the License Amanuensis (GUI)

Footstep one Choose to open the License Amanuensis Configuration page.

Stride 2 Select the Enable Default Authentication bank check box to enable the license agent, or leave it unselected to disable this feature. The default value is unselected.

Step 3 In the Maximum Number of Sessions text box, enter the maximum number of sessions for the license agent. The valid range is 1 to 25 sessions (inclusive).

Step iv Configure the license agent to heed for requests from the CLM as follows:

Select the Enable Listener bank check box to enable the license agent to receive license requests from the CLM, or unselect this check box to disable this characteristic. The default value is unselected.

In the Listener Message Processing URL text box, enter the URL where the license amanuensis receives license requests (for example, http://209.165.201.xxx/licenseAgent/custom). The Protocol parameter indicates whether the URL requires HTTP or HTTPS.

Annotation
Yous tin specify the protocol to use on the HTTP Configuration page.

Select the Enable Hallmark for Listener cheque box to enable authentication for the license agent when it is receiving license requests, or unselect this check box to disable this feature. The default value is unselected.

In the Max HTTP Bulletin Size text box, enter the maximum size for license requests. The valid range is 0 to 9999 bytes, and the default value is 0.

Stride 5 Configure the license agent to ship license notifications to the CLM as follows:

Select the Enable Notification check box to enable the license agent to send license notifications to the CLM, or unselect this check box to disable this characteristic. The default value is unselected.

In the URL to Transport the Notifications text box, enter the URL where the license agent sends the notifications (for instance, http://www.cisco.com/license/notify).

In the User Name text box, enter the username required in club to view the notification messages at this URL.

In the Password and Ostend Password text boxes, enter the password required in lodge to view the notification letters at this URL.

Pace 6 Click Utilise to commit your changes.

Step 7 Click Salvage Configuration to save your changes.
Configuring the License Agent (CLI)
Step 1 Enable the license amanuensis by inbound one of these commands:

config license agent default cosign —Enables the license agent default listener with hallmark.

config license agent default authenticate none —Enables the license amanuensis default listener without authentication.

Annotation
To disable the license agent default listener, enter the config license amanuensis default disable control . The default value is disabled.

Step 2 Specify the maximum number of sessions for the license agent past entering this control:
config license agent max-sessions sessions

The valid range for the sessions parameter is 1 to 25 (inclusive), and the default value is 9.

Step 3 Enable the license agent to receive license requests from the CLM and to specify the URL where the license agent receives the requests by inbound this control:
config license agent listener http { plaintext | encrypt} url authenticate [ none] [ max-message size] [ acl acl]

The valid range for the size parameter is 0 to 65535 bytes, and the default value is 0.

Note
To prevent the license agent from receiving license requests from the CLM, enter the config license amanuensis listener http disable control . The default value is disabled.

Step 4 Configure the license amanuensis to send license notifications to the CLM and to specify the URL where the license amanuensis sends the notifications by entering this command:
config license agent notify url username countersign

Note
To forbid the license amanuensis from sending license notifications to the CLM, enter the config license agent notify disable username password command. The default value is disabled.

Step five Enter the salvage config command to save your changes.
Stride 6
Run across statistics for the license agent'due south counters or sessions by inbound this control:
evidence license agent { counters | sessions}

Information similar to the following appears for the prove license amanuensis counters command:
                                   License Agent Counters Request Letters Received:x: Messages with Errors:1 Request Operations Received:9: Operations with Errors:0 Notification Messages Sent:12: Transmission Errors:0: Lather Errors:0                                
Information similar to the following appears for the show license amanuensis sessions command:
                                   License Agent Sessions: i open up, maximum is 9                                
Notation
To clear the license agent's counter or session statistics, enter the clear license amanuensis { counters | sessions} command.

benoithisiblim.blogspot.com

Source: https://www.cisco.com/en/US/docs/wireless/controller/7.4/configuration/guides/system_management/config_system_management_chapter_011.html

how to upload cisco license to air-ct2500 k9controller

Managing Licenses

Information About Installing and Configuring Licenses

Guidelines and Limitations About Licenses

Obtaining an Upgrade or Capacity Adder License

Information Nigh Obtaining an Upgrade or Capacity Adder License

Obtaining and Registering a PAK Certificate

Installing a License

Installing a License (GUI)

Installing a License (CLI)

Viewing Licenses (GUI)

Viewing Licenses (CLI)

Troubleshooting Licensing Bug

Information Well-nigh Activating an AP-Count Evaluation License

Activating an AP-Count Evaluation License (GUI)

Activating an AP-Count Evaluation License (CLI)

Configuring Correct to Use Licensing

Information Nigh Right to Use Licensing

Configuring Right to Use Licensing (GUI)

Configuring Right to Use Licensing (CLI)

Rehosting Licenses

Information About Rehosting Licenses

Rehosting a License (GUI)

Rehosting a License (CLI)

Data Well-nigh Transferring Licenses to a Replacement Controller after an RMA

Transferring a License to a Replacement Controller subsequently an RMA

Information About Configuring the License Agent

Configuring the License Amanuensis (GUI)

Configuring the License Agent (CLI)

0 Response to "how to upload cisco license to air-ct2500 k9controller"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel

Step 1	Choose to open the Licenses page.
Stride 2	In the Adder License area, choose to add or delete the number of APs that an AP license can support, enter a value, and click Gear up Count.
Pace iii	Click Salvage Configuration.

Pace 1	Browse to https://sso.cisco.com/autho/forms/CDClogin.html.
Step 2	On the Product License Registration page, choose .
Stride 3	Click Specify Device and so cull the controller model from the Product Family drop-down list.
Step 4	Complete the on-screen instructions to generate the license file. The license is provided online or in an e-mail.
Step 5	Copy the license file to the TFTP server.
Footstep six	Install the license past choosing .