Cisco MDS SanOS Troubleshooting Guide -- Troubleshooting Licensing
From DocWiki
(→Displaying License Information Using Fabric Manager) |
|||
| Line 100: | Line 100: | ||
===Displaying License Information Using Fabric Manager=== | ===Displaying License Information Using Fabric Manager=== | ||
| + | To view license information using Fabric Manager, follow these steps: | ||
| + | <p>1. Select Switches > Licenses from the Physical Attributes pane. You see the license information in the Information pane, one line per feature.</p> | ||
| + | <p>2. Click the Feature Usage tab to see the switch, name of the feature package, the type of license installed, the number of licenses used (Installed Count), the expiration date, the grace period (if you do not have a license for a particular feature), and any errors (for example, if you have a missing license). Click the Keys tab to display information about each of the License Key files installed on your switches. </p> | ||
| + | <p>3. Click the Usage tab to see the applications using the feature package on each switch. Use this tab to determine which applications depend on each license you have installed. </p> | ||
| + | |||
===Displaying License Information Using Device Manager=== | ===Displaying License Information Using Device Manager=== | ||
===Displaying License Information Using Fabric Manager Web Client=== | ===Displaying License Information Using Fabric Manager Web Client=== | ||
Revision as of 20:07, 20 July 2010
This section describes how to manage the issues with licensing. Licensing functionality is available in all switches in the Cisco MDS 9000 Family. This functionality allows you to access specified premium features on the switch after you install the appropriate license for that feature. Licenses are supported, and enforced in Cisco MDS SAN-OS Release 1.3(1) and later.
License Overview
Cisco SAN-OS requires licenses for advanced features. These licenses have two options:
- Feature-based licensing—Features that are applicable to the entire switch. You need to purchase and install a license for each switch that uses the features you are interested in. The Enterprise license is an example of a feature-based license.
- Module-based licensing—Features that require additional hardware modules. You need to purchase and install a license for each module that uses the features you are interested in. The SAN Extension over IP license is an example of a module-based license.
 | Note: | The Cisco MDS 9216i switch enables SAN Extension features on the two fixed IP services ports only. The features enabled on these ports are identical to the features enabled by the SAN Extension over IP license on the14/2-port Multiprotocol Services (MPS-14/2) module. If you install a module with IP ports in the empty slot on the Cisco MDS 9216i, a separate SAN Extension over IP license is required to enable related features on the IP ports of the additional module. |
Chassis Serial Numbers
Licenses are created using the serial number of the chassis where the license file is to be installed. Once you order a license based on a chassis serial number, you cannot use this license on any other switch. If you use a license meant for another chassis, you may see the following system message:
Error MessageLICMGR-3-LOG_LIC_INVALID_HOSTID: Invalid license hostid VDH=[chars] for feature [chars].
Explanation The feature has a license with an invalid license Host ID. This can happen if a supervisor module with licensed features for one switch is installed on another switch.
Recommended Action Reinstall the correct license for the chassis where the supervisor module is installed.
Grace Period
If you use a feature that requires a license but have not installed a license for that feature, you are given a 120 day grace period to evaluate the feature. You must purchase and install the number of licenses required for that feature before the grace period ends or Cisco SAN-OS will disable the feature at the end of the grace period. If you try to use an unlicensed feature, you may see the following system messages:
Error MessageLICMGR-2-LOG_LIC_GRACE_EXPIRED: Grace period expired for feature [chars].
Explanation The unlicensed feature has exceeded its grace time period. Applications using this license will be shut down immediately.
Recommended Action Please install the license file to continue using the feature.
Error MessageLICMGR-3-LOG_LICAPP_NO_LIC: Application [chars] running without [chars] license, shutdown in [dec] days.
Explanation The Application [chars1] has not been licensed. The application will work for a grace period of [dec] days after which it will be shut down unless a license file for the feature is installed.
Recommended Action Install the license to continue using the feature.
Error MessageLICMGR-3-LOG_LIC_LICENSE_EXPIRED: Evaluation license expired for feature [chars].
Explanation The feature has exceeded its evaluation time period. The feature will be shut down after a grace period.
Recommended Action Install the license to continue using the feature.
Error MessageLICMGR-3-LOG_LIC_NO_LIC: No license(s) present for feature [chars]. Application(s) shutdown in [dec] days.
Explanation The feature has not been licensed. The feature will work for a grace period, after which the application(s) using the feature will be shutdown.
Recommended Action Install the license to continue using the feature.
Error MessageLICMGR-6-LOG_LICAPP_EXPIRY_WARNING: Application [chars] evaluation license [chars] expiry in [dec] days.
Explanation The application will exceed its evaluation time period in the listed number of days and will be shut down unless a permanent license for the feature is installed.
Recommended Action Install the license file to continue using the feature.
License packages can contain several features.If you disable a feature during the grace period and there are other features in that license package that are still enabled, the clock does not stop for that license package. To suspend the grace period countdown for a licensed feature, you must disable every feature in that license package. Choose Switches > Licenses and select the Usage tab in Fabric Manager or use the show license usage CLI command to determine which features are enabled for a license package.
Initial Troubleshooting Checklist
Begin troubleshooting license issues by checking the following issues first:
|
Checklist |
Checkoff |
|---|---|
Verify the chassis serial number for all licenses ordered. |
|
Verify the platform or module type for all licenses ordered. |
|
Verify that the Product Authorization Key you used to order the licenses comes from the same chassis that you retrieved the chassis serial number on. |
|
Verify that you have installed all licenses on all switches that require the licenses for the features you enable. |
|
Displaying License Information Using Fabric Manager
To view license information using Fabric Manager, follow these steps:
1. Select Switches > Licenses from the Physical Attributes pane. You see the license information in the Information pane, one line per feature.
2. Click the Feature Usage tab to see the switch, name of the feature package, the type of license installed, the number of licenses used (Installed Count), the expiration date, the grace period (if you do not have a license for a particular feature), and any errors (for example, if you have a missing license). Click the Keys tab to display information about each of the License Key files installed on your switches.
3. Click the Usage tab to see the applications using the feature package on each switch. Use this tab to determine which applications depend on each license you have installed.
