Table Of Contents
MPSM License Concepts and Terms
Displaying Licenses for a Specific MPSM Card Type
Displaying the License Usage for All Cards
Displaying the License Usage for a Specific Card
Displaying a History of License Updates
Adding Licenses Purchased from Cisco.com
Moving Licenses from an MPSM Card to the Switch
Allocating Feature Licenses to a Card
Recovering Feature Licenses That are Not In Use
Saving and Restoring the License Configuration
Transferring Licenses between Switches
MPSM Licensing
MPSM Licensing Information
The multiprotocol service module (MPSM) family of cards includes MPSM-T3E3-155, MPSM-16-T1E1, and MPSM-8-T1E1 service modules. With proper licensing, these cards can provide multiple services or features.
The MPSM provides these services and features with the same hardware and same runtime firmware image using License Management. License Management is a software component that grants and enforces the use of licensed services.
This appendix explains license management functions and procedures. It includes the following sections:
•MPSM License Concepts and Terms
•Adding Licenses Purchased from Cisco.com
•Moving Licenses from an MPSM Card to the Switch
•Allocating Feature Licenses to a Card
•Recovering Feature Licenses That are Not In Use
•Saving and Restoring the License Configuration
MPSM License Overview
This appendix will help you with the following five MPSM licensing scenarios:
•You purchase MSPM cards and licenses as part of an initial chassis purchase. The license(s) will ship to you loaded on the PXM card.
•You purchase spare MPSM cards with licenses loaded.
•You purchase MPSM license(s) only, with no hardware.
•You need to transfer MPSM license(s) from one MGX node to another.
•You need to have MPSM licenses that are in an alarm state rekeyed.
Note You can purchase MGX systems, spares, and MPSM licenses from www.cisco.com, specifically, http://www.cisco.com/order/apollo/configureHome.html.
Tip Licensed services are new for MGX switches. Although available licenses are summarized in Table F-1, please read this whole appendix to become familiar with the terms and processes used for MPSM licensing. For example, if your shelf goes into Node License Alarm, you will have a 5-day grace period in which to recover licenses without interrupting service. After you read this whole appendix, you will be comfortable with the licensing and rekeying process. If you need additional assistance, please contact licensing@cisco.com.
Table F-1 lists the MPSM licenses that can be purchased for the MPSM cards.
The MGX chassis can ship with licenses already programmed on the MPSM cards. The MPSM card registers these licenses with the chassis, creating a pool of licenses for the chassis. This pool of licenses is stored on the PXM hard disk and is managed by the PXM controller.
Licenses are authorized for a specific backplane serial number, and then licenses are allocated to specific slots. When an MPSM card is provisioned, the licenses required for that configuration are allocated to that slot.
Note Redundant cards require the same licenses as the primary cards they protect. For 1:N redundancy, a redundant card needs one of each type of licence used by the primary cards it protects.
The PXM CLI command, cnflic, can be used to add licenses to the PXM license pool or to transfer licenses from other nodes. The cnflic command gets license information using the encrypted key that was generated by the License Keycutter application on a Cisco server when the license was purchased
The MPSM CLI command, movlic, moves licenses from the MPSM card to the PXM license pool.
Additional commands for managing licenses are dsplicalms, dspliccd, dspliccds, dsplicnodeid, and dsplics. These commands are described in procedures contained in this manual, and explained in greater detail in the Cisco MGX 8800/8900 Series Command Reference, Release 5.1, at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/rel5/cmdref/index.htm.
MPSM licenses enable the optional MPSM features listed in Table F-2. These features are enabled whenever a feature license is available in the license pool.
Table F-2 Feature Options for MPSM Services
Licensed Feature MPSM-8-T1E1 MPSM-T3E3-155 MPSM-16-T1E1 ATM Circuit Emulation Frame Relay ATM Frame Relay ATM Frame RelayRate Control
—
—
X
—
X
—
X
Channelization
—
—
—
X
X
—
—
Multiservice1
—
—
—
X
X
X
X
Multilink2
—
—
—
X
—
X
—
PPP
—
—
—
—
—
X
X
1 The multiservice feature allows ATM and Frame Relay services to run simultaneously only on MPSM cards.
2 The multilink feature enables IMA support for ATM services and multilink Frame Relay (MFR) support for Frame Relay services.
These licenses can be installed in the PXM license pool. In a shelf, there may be different MPSM cards that can support the licensed services and features. Licenses for one type of card cannot be used on another type of card. For the MPSM-T3E3-155 or MPSM-16-T1E1 cards, if no license is allocated to the service module, only the default single service functionality is available on that service module.
MPSM License Concepts and Terms
Table F-3 lists concepts and terms used to explain the MPSM licensing procedure.
Table F-4 lists the terminology used for managing feature licenses on the MPSM cards.
PXM License Pool
Figure F-1 illustrates the license pool and the types of items that are stored in it.
Figure F-1 The Switch License Pool
The switch license pool serves as a depository for all licenses installed on a switch. When a card needs to use a license, it checks the license out of the depository and the license becomes unavailable to all other cards while it is checked out. For example, if a standard ABR connection is provisioned on an MPSM-8-T1E1 card configured for Frame Relay services, a rate control license in the pool is checked out or allocated to that card. If the ABR connection is removed and no other ports on the card have provisioned standard ABR connections, the rate control feature license is checked back into the license pool and becomes available for other cards.
There are three ways to add licenses to the license pool:
•If the license is purchased with the MPSM card, use movlic to move the license(s) from the MPSM card to the PXM license pool.
•If the license is purchased alone—without the MPSM hardware, use cnflic to add the license(s) to the PXM license pool.
•If you want to move a license from one MGX node to another MGX node, you must transfer the license.
To explain these cases further, if a license is purchased at the same time as the MPSM card, the license can be programmed on the MPSM card. When a license is programmed on an MPSM card, the license is unavailable to that card and all other cards in the switch. To enable use of the license, it must be moved to the switch license pool, which is a database on the PXM card. The MPSM movelic CLI command is used to move programmed licenses from MPSM cards to the PXM license pool.
If you want to add licenses after receiving an MPSM card, you can purchase them using the Cisco.com website. Licenses that are purchased on the web site can arrive in the form of an encrypted key in an E-mail message or a file that contains an encrypted key. The PXM cnflic command is used with the encrypted key or license file to add licenses to the PXM license pool.
When a license is checked out, the switch records the assignment of the feature to a card and enables the feature on the card. The license remains in the license pool until explicitly removed. The only way to safely remove a license from the pool is to explicitly transfer it to another switch.
Displaying License Data
Display commands allow you to view node license data, card license data, or license history data. The following sections describe ways to view the license data.
Displaying All Node Licenses
To display all node licenses, enter the dsplics command as follows:
M8830_CH.1.PXM.a > dsplicsM8830_CH System Rev: 04.09 Mar. 08, 2004 00:15:51 GMTMGX8830 Node Alarm: CRITICALNode License Alarm : MinorLicensed License Licenses Licenses LicensesCard Type Type Installed Allocated Available----------------- ----------- --------- --------- ---------MPSM-T3E3-155 MultiSrvc 4 1 3Channelize 4 1 3Multilink 4 0 4RateControl 4 1 3This command displays all the license data on the node for all MPSM card types. It also shows how many licenses are in use and how many are available.
Displaying Licenses for a Specific MPSM Card Type
To display the license usage for a specific MPSM card type, enter the dsplics -cd command. The number in the command specifies the MPSM card type which must be one of the following:
•MPSM-8-T1E1 = 1
•MPSM-16-T1E1 = 2
•MPSM-T3E3-155 = 3
Note The dsplics -cd command displays the same information as the dsplics, command, but it limits the display to a single card type.
For example:
M8830_CH.1.PXM.a > dsplics -cd 3M8830_CH System Rev: 04.09 Mar. 08, 2004 00:08:45 GMTMGX8830 Node Alarm: CRITICALLicensed License Licenses Licenses LicensesCard Type Type Installed Allocated Available----------------- ----------- --------- --------- ---------MPSM-T3E3-155 MultiSrvc 4 1 3Channelize 4 1 3Multilink 4 0 4RateControl 4 1 3Displaying the License Usage for All Cards
Note Redundant cards require the same licenses as the primary cards they protect. For 1:N redundancy, a redundant card needs one of each type of licence used by the primary cards it protects.
The dspliccds command displays the total licenses allocated or programmed on all cards. The dspliccds command is a non-privileged command and is available on the PXM45 and PXM1E cards.
Note To get detailed information for a specific card, use dspliccd command for a particular slot.
The following example displays licenses of all cards.
M8830_CH.1.PXM.a > dspliccdsM8830_CH System Rev: 05.00 Apr. 11, 2004 19:08:26 GMTMGX8830 Node Alarm: CRITICALCard Card Lic Prov License AllocSlot Type Alarm Status Type lics---- ------------- -------- ------ ------- ----1 -- -- -- -- --2 -- -- -- -- --3 MPSM-T3E3-155 No Yes MultiSrvc 1Channelize 1MultiLink 1RateControl 14 MPSM-T3E3-155 Minor Yes MultiSrvc 15 MPSM-T3E3-155 Minor No MultiSrvc 1MultiLink 16 MPSM-T3E3-155 No Yes -- --9 -- -- -- -- --10 MPSM-8T1E1 No Yes RateControl 111 MPSM-8T1E1 No Yes -- --12 MPSM-8T1E1 No Yes RateControl 112 MPSM-16T1E1 No Yes MultiSrvc 1MultiLink 1RateControl 1PPP 1......The following example displays programmed licenses of all cards.
MGX8850.7.PXM.a> dspliccds -progMynode19 System Rev: 04.00 Feb. 27, 2003 17:28:26 GMTChassis Serial No: SAA02390010 Chassis Rev: E4 GMT Offset: 0Node Alarm: MAJORCard Licenses License ProgrammedSlot Type Moved Type lics---- ------------- -------- ------- ----------1 -- -- -- --2 -- -- -- --3 MPSM-T3E3-155 No MultiSrvc 1Channelize 1MultiLink 14 MPSM-T3E3-155 Yes MultiSrvc 1Channelize 15 MPSM-T3E3-155 Yes MultiSrvc 1MultiLink 1RateControl 16 MPSM-T3E3-155 N/A -- --9 -- -- -- --10 MPSM-8T1E1 No RateControl 111 MPSM-8T1E1 N/A -- 012 MPSM-8T1E1 Yes RateControl 113 MPSM-16T1E1 N/A -- 0.........Displaying the License Usage for a Specific Card
To display the license usage for a single card within a switch, enter the dspliccd command on either the PXM or the MPSM. The following example shows how the display appears when the command is run from a PXM card:
M8830_CH.11.PXM.a > dspliccd 11M8830_CH System Rev: 04.00 Feb. 27, 2003 17:28:26 GMTChassis Serial No: SAA02390010 Chassis Rev: E4 GMT Offset: 0Node Alarm: NONECard License Alarm: MinorService Module Type: MPSM-T3E3-155Service Module Serial Number: 3SA4567011Provisioning allowed: YesGrace-Period Remaining: 3 Days 4 Hours=========================================================Allocated License Type Qty---------------------- ----Multi-Srvc 1Channelize 1=========================================================Programmed License Type Qty----------------------- ----Multi-Srvc 1Channelize 1=========================================================Programmed Licenses Registered: YESLicense Registration Node: MyNodeBuilding3License Registration Chassis Serial No: 8SA931247821License Creation Timestamp: Oct 25, 2003 14:20:40License Registration Timestamp: Dec 02, 2003 19:33:12=========================================================In the example above, the following states might occur:
•If the grace period has already expired, the following output displays:
Provisioning allowed: No Grace-Period Status: Expired•If the slot is running normally without a license alarm, only the following output displays:
Provisioning allowed: YesThe number after the dspliccd command is the slot number for which you want to display license data.
An allocated license is one that has been assigned to a card. A programmed license is a license that has been shipped on a card from the factory. It must be moved to the license pool before it can be allocated to a card.
In the next example, the dspliccd command is run from an MPSM card, so you do not have to enter the slot number:
M8830_CH.12.MPSM155[FR].a > dspliccdCard License Alarm: NoneService Module Type: MPSM-T3E3-155Service Module Serial Number: SAD073504CTProvisioning (addcon) Allowed: YES=========================================================Needed License Type Needed Licenses------------------- ---------------Multi-Srvc 1Channelize 1=========================================================Allocated License Type Allocated licenses---------------------- ------------------Multi-Srvc 1Channelize 1=========================================================Programmed License Type Programmed licenses------------------------ -------------------Multi-Srvc 1Channelize 1=========================================================Programmed License Registered: YESLicense registration node: M8830_CHLicense registration chassis: 8SA931247821=========================================================In the previous example, a needed license is a license that is required by the MPSM card to provide a desired feature.
Displaying a History of License Updates
To display a history of all license updates on the switch, enter the dsplics -history command as follows:
M8830_CH.1.PXM.a > dsplics -historyM8830_CH System Rev: 04.09 Mar. 08, 2004 00:20:22 GMTMGX8830 Node Alarm: CRITICALLicensed Chassis or Update Update LicenseCardType Card Serial# Method Sequence# Update Time---------------- ------------ -------- --------- -----------MPSM-T3E3-155 SAG06152SZM Addition 1 WED OCT 08 19:58:54 2003Displaying License Alarms
To display a list of license feature alarms, enter the dsplicalms command as follows:
M8830_CH.1.PXM.a > dsplicalmsM8830_CH System Rev: 04.09 Mar. 08, 2004 00:20:59 GMTMGX8830 Node Alarm: CRITICALSlot Critical Major Minor || Slot Critical Major Minor---- -------- ------- ------- || ---- -------- ------- -------1 0 0 0 || 8 0 0 02 0 0 0 || 9 0 0 03 0 0 0 || 10 0 0 04 0 0 0 || 11 0 0 05 0 0 0 || 12 0 0 06 0 0 0 || 13 0 0 07 0 0 0 || 14 0 0 0Adding Licenses Purchased from Cisco.com
Purchased licenses are delivered in the form of an encrypted key, which appear within an E-mail message or within a text file attached to an E-mail. When ordering additional licenses, you must provide the output generated by the command dsplicnodeid on the switch that will host the licenses. The output generated by the dsplicnodeid command is part of the encryption key.
The general procedure is as follows:
1. Purchase additional licenses from Cisco.com and receive a Product Authorization Key (PAK) by E-mail.
2. Collect the serial number used for licensing from the destination switch.
3. Using Cisco.com, the PAK, and the destination switch serial number, generate a license key for the destination switch.
4. Move the new license key to the destination switch.
5. Apply the new license on the destination switch.
The following procedure describes how to obtain the back plane serial number so that you can purchase licenses, and it describes how to install licenses when you receive them.
Step 1 Establish a configuration session using a user name with SERVICE_GP privileges or higher.
Step 2 Purchase additional licenses from Cisco.com. After you purchase additional licenses, a Product Authorization Key (PAK) is shipped by E-mail to you.
Step 3 To display the switch serial number used for licensing, enter the dsplicnodeid command. If no licenses have been installed, the switch will generate a node license ID as shown in the following example:
M8850_SF.7.PXM.a > dsplicnodeidThe BkPL recorded Lic Seq Num did not exist. Creating with 0.NodeID=SCA062300GF:000000:004:009:015If the switch has an existing node license ID, it is displayed as follows:
M8850_SF.7.PXM.a > dsplicnodeidNodeID=SCA062300GF:000001:004:009:015Step 4 To generate a license key on Cisco.com, go to the web page specified in the "MPSM License Overview" section.
At this web page, you must specify the PAK and the licenses you want to install, and you must specify the serial number collected in Step 2. After you arrange for additional licenses, you will receive an encrypted key in an E-mail message and in a license file attachment. The key contains the new license information for the destination switch.
•If you plan to install the new license on the destination switch using the new license file, go to Step 6.
•If you plan to install the licenses using the encrypted key sent in the E-mail message, go to Step 5.
Step 5 To install a license using a license file, FTP that file to the C:/LICENSE directory on the destination switch. Enter the cnflic command using the following syntax:
M8850_SF.7.PXM.a > cnflic -f filenameReplace filename with the name of the file provided by Cisco.com as shown in the following example:
M8850_SF.7.PXM.a > cnflic -f Lmpsmoc3_20040615113118099.dat Update method : Addition Card type : MPSM-T3E3-155 Creation date/time : TUE JUN 15 10:31:18 2004 Grace period (days) : 0 Update sequence number: 6 Licence serial number : L0000003878 Num of features : 4 --------------- ----- License Type Qty --------------- ----- MultiSrvc 1 Channelize 1 RateControl 1 MultiLink 1 Please confirm the above licence information. cnflic: Do you want to proceed (Yes/No)? y M8850_SF.7.PXM.a >
Note Skip to Step 7.
Step 6 To install a license using an encrypted license key, copy the license key from the E-mail and enter the cnflic command using the following syntax:
M8850_SF.7.PXM.a > cnflic licenseStringReplace licenseString with the encrypted key supplied in the E-mail message as shown in the following example:
M8850_SF.7.PXM.a > cnflic 01050004cbf7420c534f5e21b97754bdb81da8862607040eebc5702aa37cc1e1c5d4e9b00ea6c89c13f1e50df0 2dc8b374f42e84bf96fd1af672fe571a98ae1bf411d3b4dbd Update method : Addition Card type : MPSM-T3E3-155 Creation date/time : TUE JUN 15 10:17:39 2004 Grace period (days) : 0 Update sequence number: 5 Licence serial number : L0000008633 Num of features : 4 --------------- ----- License Type Qty --------------- ----- MultiSrvc 1 Channelize 1 RateControl 1 MultiLink 1 Please confirm the above licence information. cnflic: Do you want to proceed (Yes/No)? y M8850_SF.7.PXM.a >Step 7 To verify that new licenses have been installed, enter the dsplics command.
Caution To avoid losing licenses during a configuration restoration, save the switch configuration after installing the new licenses by using the saveallcnf command.
Step 8 Enter the saveallcnf command.
Moving Licenses from an MPSM Card to the Switch
To move programmed licenses from an MPSM card to the switch license pool, use the cc command to move to the CLI prompt for the MPSM card. Then enter the movelic command as follows:
M8250_SJ.1.22.MPSM8T1.FRM.a > movelic------------------------------------------------Programmed License Type #Programmed----------------------- -----------Rate-Control 1Do you want to proceed (Yes/No)? YesCard Licenses have been moved to license pool.M8250_SJ.1.22.MPSM8T1.FRM.a >
Note The movelic command requires SERVICE_GP privileges.
In the previous example, the movelic command moved all licenses programmed into the NVRAM on the MPSM card into the PXM license pool. Licenses can be moved only once from a card to a license pool. Licenses cannot be moved back to an MPSM card. If you want to transfer licenses to another switch, see "Transferring Licenses between Switches."
Caution To avoid losing licenses during a configuration restoration, save the switch configuration after moving the new licenses into the PXM license pool by using the saveallcnf command.
Allocating Feature Licenses to a Card
To allocate a feature license to an MPSM card, configure the card to use the licensed feature. For example, to allocate the IMA feature to a card, use the addimagrp command to create an IMA group. Licenses are also allocated to redundant cards, so if you use the addred command to configure a secondary card for a primary card, licenses are allocated to the secondary card. When the secondary card serves multiple primary cards, the secondary card receives one of each type of license used by the primary cards it serves.
If the license pool on the switch has an available license for that feature on the MPSM card type, the license is automatically allocated to the card. Once a license is allocated to the card, it is no longer available for use on other cards until it returns to the license pool (See "Recovering Feature Licenses That are Not In Use").
If you configure a card to use a feature for which no licenses are available, the command that requires the feature will fail.
Recovering Feature Licenses That are Not In Use
Feature licenses are automatically returned to the license pool when the card configuration no longer requires them. The following actions can be used to remove the configuration for featured licenses:
•Use the CLI commands to remove the feature configuration. For example, if you delete all channelized ports (delport) on a card, the channelized feature is no longer required and will be returned to the license pool.
•Clear the entire configuration on the service module (clrsmcnf).
•Clear the entire configuration on the switch (clrallcnf).
•Delete a redundant card configuration. This action releases any licenses reserved for the secondary card, provided that those licenses are no longer required for other primary cards.
When licenses are returned to the license pool, they are immediately available for use on other MPSM cards.
Saving and Restoring the License Configuration
MPSM feature licenses are backed up and restored with the complete switch configuration as described in the "Managing the Configuration Files" section in Chapter 9, "Switch Operating Procedures".
Caution To avoid losing feature licenses, always save the switch configuration after you move, transfer, or add licenses, by using the saveallcnf command.
Transferring Licenses between Switches
When you transfer licenses between switches, you are removing one or more licenses from one switch for use on another switch. To transfer licenses between switches, you will need to get a transfer license from Cisco.com. The general procedure is as follows:
1. Collect the source and destination switch information by running the CLI command dsplicnodeid on these switches.
2. Using Cisco.com, enter the output generated by the dsplicnodeid command, specify the licenses to transfer, and obtain a transfer license.
3. Move the transfer license to the source switch.
4. Apply the transfer license on the source switch to remove the desired licenses and obtain a new license key and file that can be applied on the destination switch.
5. Transfer the new license to the destination switch.
6. Apply the new license on the destination switch.
The following procedure provides instructions for transferring licenses between switches.
Step 1 Establish a configuration session with the source and destination switches using a user name with SERVICE_GP privileges or higher.
Step 2 To display the switch serial number used for licensing on the source switch, enter the dsplicnodeid command.
M8850_SF.7.PXM.a > dsplicnodeidNodeID=SCA062300GF:000001:004:009:015Step 3 To display the switch serial number used for licensing on the destination switch, enter the dsplicnodeid command.
M8850_SF.7.PXM.a > dsplicnodeidNodeID=SCA062300GF:000001:004:009:020Step 4 To request a transfer license from Cisco.com, go to the URL specified in the URL in the "MPSM License Overview" section.
At the license transfer web page, specify the serial numbers you collected in Step 2 and Step 3, and specify the licenses to transfer. After you arrange for a transfer license, you will receive an encrypted key in an E-mail message and in a license file. The encrypted key contains the license transfer information for the specified source and destination switches. Before you can apply the transfer license at the source switch, you must either copy the key from the E-mail message to the switch, or copy the file to the switch.
•If you plan to install licenses using the encrypted key in the E-mail message, go to Step 5.
•If you plan to apply the transfer license using the transfer license file, go to Step 6.
Step 5 To apply the transfer license using the key in the E-mail from Cisco.com, copy the key from the E-mail, and enter the cnflic command on the source switch, using the following syntax:
M8850_SF.7.PXM.a > cnflic licenseStringReplace licenseString with the encrypted key supplied in the E-mail message as shown in the following example:
M8850_SF.7.PXM.a > cnflic 01050004fec28e9e8ab1110f48be83e0d2397cb4048d7c368c53c825c15e9245d5886357eac618012a8b515d1c 3fa29a8f35476b28331ca12b1bef166dc7c0bafc01d9e0b36 Update method : Xfer-out Card type : MPSM-T3E3-155 Creation date/time : TUE JUN 15 10:40:55 2004 Grace period (days) : 0 Update sequence number: 7 Licence serial number : L0000003912 Num of features : 4 --------------- ----- License Type Qty --------------- ----- MultiSrvc 1 Channelize 1 RateControl 1 MultiLink 1 Please confirm the above licence information. cnflic: Do you want to proceed (Yes/No)? y Licence file has been generated as: C:/LICENSE/LX-M8850_NY-7.lic Licence is: 0105000443e166180e7a310f483833a54079b77eb217332057c3d2fbaa4e9245def5aad5558458d6ab2f6bc64a 6c0441839dbdbb43e02aa7a179facb8e058de821e270a233ce87c3 M8850_SF.7.PXM.a >This step removes the licenses identified for transfer from the license pool, and these licenses are no longer available for use on the source switch. To verify that transferred licenses have been removed from the source switch, enter the dsplics command.
This step also generates a new license key and a new license file, which can be used to install the removed licenses on the destination switch. The license key appears in the command output. The license file is stored in the C:/LICENSE directory.
Note Go to Step 7.
Step 6 To apply the transfer license using the key in the license file attached to the E-mail from Cisco.com, FTP that file to the C:/LICENSE directory on the switch, and enter the cnflic command on the source switch, using the following syntax:
M8850_SF.7.PXM.a > cnflic -f filenameReplace filename with the name of the license file provided by Cisco.com as shown in the following example:
M8850_SF.7.PXM.a > cnflic -f Lmpsmoc3_20040615114539410.dat Update method : Xfer-out Card type : MPSM-T3E3-155 Creation date/time : TUE JUN 15 10:45:39 2004 Grace period (days) : 0 Update sequence number: 8 Licence serial number : L0000008916 Num of features : 4 --------------- ----- License Type Qty --------------- ----- MultiSrvc 1 Channelize 1 RateControl 1 MultiLink 1 Please confirm the above licence information. cnflic: Do you want to proceed (Yes/No)? y Licence file has been generated as: C:/LICENSE/LX-M8850_NY-8.lic Licence is: 0105000451ee9dc73e426022d432745064f747169cd393f4a8c5238cfe5ac0166765c9ea6428276a01df3225df ac9aadf17951b2972bb2acf0950fda2a57892fe6e3ec93e1a26e16 M8850_SF.7.PXM.a >This step removes the licenses identified for transfer from the license pool, and these licenses are no longer available for use on the source switch. To verify that transferred licenses have been removed from the source switch, enter the dsplics command.
This step also generates a new license key and a new license file, which can be used to install the removed licenses on the destination switch. The license key appears in the command output. The license file is stored in the C:/LICENSE directory.
Note To install the new license(s) using the encrypted key produced in Step 5 or Step 6, go to Step 7
To install the new license(s) on the destination switch using the new license file produced in Step 5 or Step 6, go to Step 8.
Step 7 To install the new license(s) on the destination switch using the key displayed on the source switch, copy the key and enter the cnflic command with the key generated from the source switch:
M8850_SF.7.PXM.a > cnflic 0105000443e166180e7a310f483833a54079b77eb217332057c3d2fbaa4e9245def5aad5558458d6ab2f6bc64a 6c0441839dbdbb43e02aa7a179facb8e058de8213 Update method : Xfer-in Card type : MPSM-T3E3-155 Creation date/time : TUE JUN 15 18:40:55 2004 Grace period (days) : 0 Update sequence number: 4 Licence serial number : L0000003912 Num of features : 4 --------------- ----- License Type Qty --------------- ----- MultiSrvc 1 Channelize 1 RateControl 1 MultiLink 1 Please confirm the above licence information. cnflic: Do you want to proceed (Yes/No)? y M8850_SF.7.PXM.a >
Note Skip to Step 9.
Step 8 To install the new license on the destination switch using the key in the new license file generated from the source switch, FTP that file to the C:/LICENSE directory on the destination switch enter the cnflic command using the following syntax:
M8850_SF.7.PXM.a > cnflic -f filenameReplace filename with the name of the file transferred from the source switch as shown in the following example:
M8850_SF.7.PXM.a > cnflic -f LX-M8850_NY-8.lic Update method : Xfer-in Card type : MPSM-T3E3-155 Creation date/time : TUE JUN 15 18:45:39 2004 Grace period (days) : 0 Update sequence number: 5 Licence serial number : L0000008916 Num of features : 4 --------------- ----- License Type Qty --------------- ----- MultiSrvc 1 Channelize 1 RateControl 1 MultiLink 1 Please confirm the above licence information. cnflic: Do you want to proceed (Yes/No)? y M8850_SF.7.PXM.a >Step 9 To verify that the transferred licenses have been installed on the destination switch, enter the dsplics command.
Step 10 Enter the saveallcnf command.
Caution To avoid losing licenses during a configuration restoration, save the switch configuration at the source and destination switches by using the saveallcnf command.
MPSM License Alarms
MPSM feature license alarms can occur at the node level or the slot level of the switch. The following sections describe these alarms:
Node License Alarm
Node license alarms occur under the following conditions:
•A switch configuration that was saved before licenses were added or transferred to and from the PXM license pool has been restored. Any mismatch between the actual license sequence number and the restored license sequence number generates a minor node license alarm. To prevent this type of alarm, always save the switch configuration (saveallcnf) after you move, transfer, or add licenses.
•The switch configuration is restored on a different node, or the Cisco MGX chassis is replaced with another chassis. Because licenses are authorized for a specific backplane serial number, such conditions will cause a mismatch between the physical backplane serial number and serial number recorded in the database.
When a node license alarm is raised, all cards that are using feature licenses go into the slot license alarm state. If no licenses are in use by the cards, no slot license alarms will be raised.
On PXM45 and PXM1E platforms, use the PXM dspndalms command to troubleshoot the node license alarm. As shown in the following example on the PXM45 platform, the output of this command will indicate if the switch is in the node license alarm state:
M8850_SF.8.PXM.a > dspndalmsNode Alarm SummaryAlarm Type Critical Major Minor---------- -------- ------- -------Clock Alarms 0 0 0Switching Alarms 0 0 0Environment Alarms 0 0 0Card Alarms 0 0 0Node License Alarm 0 0 1M8850_SF.8.PXM.a >Node license alarms are cleared by validating licenses in the license pool. This is done by applying the special Rekey feature license to the node using the cnflic command. When the pool licenses are validated, any existing slot license alarms are also cleared and normal operation is restored. For the procedure to rekey feature licenses, see "Rekeying Feature Licenses".
Note If the switch is in node license alarm, you must rekey the PXM license pool before proceeding with any other license management tasks.
Slot License Alarms
Slot license alarms are raised under the following conditions:
•When a node license alarm is raised, all cards that are using feature licenses go into the slot license alarm state. Slot license alarms raised under this condition can be cleared by rekeying the PXM license pool. For the procedure to rekey feature licenses, see "Rekeying Feature Licenses".
•The slot in alarm has acquired or oversubscribed one or more licenses while these licenses were not available in the license pool. Slot license alarms raised under this condition are cleared by adding the required number of licenses to the PXM license pool or by releasing corresponding licenses from other slots so that they become available to the slot in alarm. If slots in alarm have redundancy, you must add licenses to cover both the primary and secondary slots to clear the alarms.
On PXM1E and PXM45 platforms, use the PXM dsplicalms command to troubleshoot slot license alarms. The output of this command will indicate which MPSM cards are in the slot license alarm state. The following example shows the output of the PXM dsplicalms command on the PXM45 platform. In this example, the MPSM card in slot 28 is in slot license alarm:
M8850_SF.8.PXM.a > dsplicalmsM8850_SF System Rev: 05.00 Jul. 10, 2004 04:35:12 GMTMGX8850 Node Alarm: MINORSlot Critical Major Minor || Slot Critical Major Minor---- -------- ------- ------- || ---- -------- ------- -------1 0 0 0 || 17 0 0 02 0 0 0 || 18 0 0 03 0 0 0 || 19 0 0 04 0 0 0 || 20 0 0 05 0 0 0 || 21 0 0 06 0 0 0 || 22 0 0 07 0 0 0 || 23 0 0 08 0 0 0 || 24 0 0 09 0 0 0 || 25 0 0 010 0 0 0 || 26 0 0 011 0 0 0 || 27 0 0 012 0 0 0 || 28 0 0 113 0 0 0 || 29 0 0 014 0 0 0 || 30 0 0 015 0 0 0 || 31 0 0 016 0 0 0 || 32 0 0 0M8850_SF.8.PXM.a >On PXM1E and PXM45 platforms, the output of the PXM dspliccd <slot> command also shows if a card is in slot license alarm, and displays how much time is left in the alarm grace period and if provisioning is allowed with the addcon command. The following example shows the output of the PXM dspliccd <slot> command of an MPSM-8T1-FRM card in a PXM45 platform in the slot license alarm state:
M8850_SF.8.PXM.a > dspliccd 28M8850_SF System Rev: 05.00 Jul. 10, 2004 05:02:24 GMTMGX8850 Node Alarm: MINORCard License Alarm: MinorService Module Type: MPSM-8T1-FRMService Module Serial Number: SAG07208RRAProvisioning Allowed: YesGrace-Period Remaining: 4 Days, 22 Hrs=========================================================Allocated License Type Quantity-------------------- --------RateControl 1=========================================================Programmed License Type Quantity-------------------- --------RateControl 1=========================================================Programmed License Registered: YesLicense Registeration Node: M8850_SFLicense Registeration Chassis Serial No: SCA062300GFM8850_SF.8.PXM.a >On PXM1E and PXM45 platforms, the dspcd command will indicate if a card is in slot license alarm. If the card is in the slot license alarm state, the cardIntegratedAlarm will be minor and the cardMinorAlarmBitMap will indicate License Alarm. The following example shows the output of the dspcd command of an MPSM-8T1-FRM card in a PXM45 platform in the slot license alarm state:
M8850_SF.1.28.MPSM8T1.FRM.a > dspcdModuleSlotNumber: 28FunctionModuleState: ActiveFunctionModuleType: MPSM-8T1-FRMFunctionModuleSerialNum: SAG07208RRAFunctionModuleHWRev: 02FunctionModuleFWRev: 030.000.004.016-P2FunctionModuleResetReason: Reset by PXMLineModuleType: LM-RJ48-8T1LineModuleState: PresentmibVersionNumber: 102configChangeTypeBitMap: No changescardIntegratedAlarm: MinorcardMinorAlarmBitMap: LICENSE ALARMFront Card InfoPCB PART NO-(800 LEVEL): 800-22480-04PCB PART_NO-(73 LEVEL): 73-8466-04PCB REVISION (800 LEVEL):PCB SERIAL NO: SAG07208RRACLEI CODE: 0MANUFACTURING ENG: 0x0RMA TEST HISTORY: 0x0Back Card InfoPCB PART NO-(800 LEVEL): 000-00000-00PCB PART NO-(73 LEVEL): 00-00000-00PCB REVISION (800 LEVEL): AAFAB PART NO-(28 LEVEL): 28-02011-01PCB SERIAL NO: 648467MANUFACTURING ENG: 0x1CRMA HISTORY: 0x0M8850_SF.1.28.MPSM8T1.FRM.a >On PXM1E and PXM45 platforms, the output of the MPSM dspliccd command also shows if a card is in slot license alarm. The following example shows the output of the dspliccd command of an MPSM-8T1-FRM card in a PXM45 platform in the slot license alarm state:
M8850_SF.1.28.MPSM8T1.FRM.a > dspliccdCard License Alarm: MinorService Module Type: MPSM8T1E1Service Module Serial Number: SAG07208RRAProvisioning (addcon) Allowed: YES=========================================================Needed License Type Needed Licenses------------------- ---------------RateControl 1=========================================================Allocated License Type Allocated licenses---------------------- ------------------RateControl 1=========================================================Programmed License Type Programmed licenses------------------------ -------------------RateControl 1=========================================================Programmed License Registered: YESLicense registration node: M8850_SFType <CR> to continue, Q<CR> to stop:License registration chassis: SCA062300GF=========================================================M8850_SF.1.28.MPSM8T1.FRM.a >
Note If the switch is in node license alarm, you must rekey the PXM license pool before proceeding with any other license management tasks. (See "Rekeying Feature Licenses" section.)
When the switch is in slot license alarm, you have a grace period of 5 days (120 hours) to resolve the alarm(s). During the first 4 days (96 hours), traps are sent every 24 hours. For the final 24 hours of the grace period, traps are sent every hour of operation. If the alarms do not get cleared, the following actions are taken:
•An event is logged indicating the expiration of the grace period for a given slot needing license(s).
•A trap is sent hourly indicating the expiration of the grace period.
•The addcon command is blocked on the slot in license alarm until the license alarms are cleared.
When the PXM license pool has been rekeyed or licenses have been added to the PXM license pool, provisioning is restored and the switch exits the license alarm state.
Rekeying Feature Licenses
Use this procedure to get your node out of the Node License Alarm state.
A rekey license can be obtained by contacting Cisco TAC. The rekey license is delivered in the form of an encrypted key, which appears within an E-mail message or within a text file attached to an E-mail. To get a rekey license, provide TAC with the output generated by the dsplicnodeid command for the switch that needs to be rekeyed. The general procedure is as follows:
1. Collect the output generated by the dsplicnodeid command for the destination switch.
2. Contact Cisco TAC, provide the output generated by the dsplicnodeid command from the previous step, and obtain a rekey license.
3. Apply the rekey license to the destination switch.
The following procedure describes how to obtain and install a rekey license:
Step 1 Log in to the node.
Step 2 To display the node ID used for licensing, enter the dsplicnodeid command as follows:
M8850_SF.8.PXM.a > dsplicnodeidNodeID=SCA062300GF:000006:005:000:004To generate a rekey license, contact Cisco TAC and provide the output collected in Step 2. After you arrange for the rekey license, you will receive an encrypted key in an E-mail message and in an attached license file.
•If you plan to apply the rekey license using the encrypted key sent in the E-mail message, go to Step 3.
•If you plan to apply the rekey license on the destination switch using the license file, FTP the license file to the C:/LICENSE directory on the destination switch. Then go to Step 4.
Step 3 To apply the rekey license using the encrypted key, copy the encrypted key from the E-mail. Enter the cnflic command using the following syntax, then skip to Step 5:
M8850_SF.7.PXM.a > cnflic licenseStringReplace licenseString with the encrypted key supplied in the E-mail message as shown in the following example:
M8850_SF.8.PXM.a > cnflic 01050004e435730660768401f6608ec42404477f35d311f226fb3bd2992a92359da94c979d7ed2bff3d24c4630 25c1Update method :RekeyCard type :----Creation date/time :TUE JUL 06 21:02:43 2004Grace period (days) :0Update sequence number:7Licence serial number :L0000000502Num of features :0--------------- -----License Type Qty--------------- -----Please confirm the above licence information.cnflic:Do you want to proceed (Yes/No)? yM8850_SF.8.PXM.a >Step 4 To apply the rekey license using the license file, enter the cnflic command using the following syntax:
M8850_SF.7.PXM.a > cnflic -f filenameReplace filename with the name of the license file as shown in the following example:
M8850_SF.8.PXM.a > cnflic -f L_20040706140923521.datUpdate method :RekeyCard type :----Creation date/time :TUE JUL 06 21:09:23 2004Grace period (days) :0Update sequence number:8Licence serial number :L0000003455Num of features :0--------------- -----License Type Qty--------------- -----Please confirm the above licence information.cnflic:Do you want to proceed (Yes/No)? yM8850_SF.8.PXM.a >Step 5 To verify that the feature licenses have been rekeyed, enter the dspndalms command as follows:
M8850_SF.8.PXM.a > dspndalmsNode Alarm SummaryAlarm Type Critical Major Minor---------- -------- ------- -------Clock Alarms 0 0 0Switching Alarms 0 0 0Environment Alarms 0 0 0Card Alarms 0 0 0Node License Alarm 0 0 0M8850_SF.8.PXM.a >In this example, after applying the rekey license to the destination switch, the switch is now out of the Node License Alarm state.
Step 6 Enter the saveallcnf command.
Caution To avoid losing licenses during a configuration restoration, we recommend you save the switch configuration after applying the rekey license by using the saveallcnf command.