> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/device-setup/licensing-details.md). # Licensing details ## Overview This page has details of Cisco licence information, listed in Reporting inventory and Details Technical. The same licences may be listed several times if there are several types and status of that licence. ## Cisco licence information ### Licence Feature Name This is the name of the licence feature, for example `IPBASE`, `ADVIPSERVICE` and `DATA`. If the router has multiple licences, each licence will be listed, separated by a semi-colon (`;`) ### Licence Type This identifies the type of licence. Licences may have a validity period defined in terms of time duration that the licence is valid for or it may be defined in terms of actual calendar dates. Subscription licences are licences that have validity period defined in terms of calendar dates. | Type | Description | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | demo | Demo(evaluation licence) licence | | extension | Extension(expiring) licence | | gracePeriod | Grace period licence | | permanent | Permanent licence, the licence has no expiry date | | paidSubscription | Paid subscription licences are the licences which are purchased by customers. These licences have a start date and end date associated with them. | | evaluationSubscription | Evaluation subscription licences are the trial licences. These licences are node locked and it can be obtained only once for an UDI. They are valid based on calendar days. These licences have a start date and an end date associated with them and are issued once per UDI. | | extensionSubscription | Extension subscription licences are similar to evaluation subscription licences but these licences are issued based on customer request. There are no restrictions on the number of licences available for a UDI | | evalRightToUse | Evaluation Right to use (RTU) licence | | rightToUse | Right to use (RTU) licence | | permanentRightToUse | Right To Use licence right after it is configured and is valid for the lifetime of the product. This is a Right To Use licence which is not in evaluation mode for a limited time | ### Licence Status This represents the status of the licence: | Status | Description | | ------------------ | --------------------------------------------------------------------------------------------------------------------- | | inactive | licence is installed, but not active | | notInUse | licence is installed and available for use | | inUse | licence is being used (by a feature) | | expiredInUse | licence is expired but still being held by the feature | | expiredNotInUse | licence is expired and not being held by any feature | | usageCountConsumed | number of entities using this licence has reached the allowed limit; no new entities are allowed to use this licence. | ## Related * [Reporting inventory](https://help.highlight.net/reporting/inventory) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.highlight.net/device-setup/licensing-details.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.