The MIB module for managing licenses on the system.
The licensing mechanism provides flexibility to
enforce licensing for various features in the system.
The following text introduces different concepts and
terms those are necessary to understand the MIB definition
and to perform license management.
UDI
Universal Device Identifier that uniquely identifies a
device. It comprises of product ID, version ID and serial
number of the device.
NODE LOCKED LICENSE:
Node locked licenses are locked to one of the device
identifiers in the system. For example, the license
can be locked to the UDI value of one of the devices
in the system. Locking a license to an UDI guarantees
that the license will not be moved to a device with a
different UDI.
NON-NODE LOCKED LICENSE:
Non-node locked licenses are not locked to any device
identifier. They can be used on other similar devices.
METERED LICENSE:
Metered licenses are valid for limited period of time
and they expire after that. This period is the usage
period of a license and it is not based on real time
clock, but system clock.
EULA:
End User License Agreement.
EVALUATION LICENSE:
Evaluation licenses are non-node locked metered
licenses which are valid only for a limited period.
They are used only when there are no permanent,
extension or grace period licenses for a feature.
User will have to accept EULA (End User License
Agreement) before using an evaluation license. Even
though they are not node locked, their usage is
recorded on the device.
RIGHT TO USE (RTU) LICENSE:
Right to use license is a non-node locked metered
license which is in evaluation mode for a limited
time after which it is converted to Right To Use (RTU)
license and is valid for the lifetime of the product.
User will have to accept EULA (End User License Agreement)
before using this license. Even though it is not node
locked, usage information is recorded on the device.
EXTENSION LICENSE:
Extension licenses are node locked metered licenses.
These licenses are issued by Cisco's licensing portal.
These licenses need to be installed using management
interfaces on the device. User will have to accept an
EULA as part of installation of extension license.
GRACE PERIOD LICENSE:
Grace period licenses are node locked metered licenses.
These licenses are issued by Cisco's licensing portal
as part of the permission ticket to rehost a license.
These licenses are installed on the device as part of
the rehost operation. User will have to accept an
EULA as part of the rehost operation for this type
of license. Details on permission ticket, rehost
operations are provided further down in this
description clause.
PERMANENT LICENSE:
Permanent licenses are node locked licenses that have
no usage period associated with them. These licenses
are issued by Cisco's licensing portal. These licenses
need to be installed using management interfaces on
the device. Once these licenses are installed, they
will provide needed permission for the feature/image
across different versions.
COUNTED LICENSE:
Counted licenses limit the number of similar entities
that can use the license. For example, a counted
license when used by a feature can limit the number
of IP phones that can connect or the number of tunnels
that can be created.
UNCOUNTED LICENSE:
Uncounted licenses do not limit the number of similar
entities that can use the licenses.
License can be enforced at the image level or at the feature
level and this MIB module supports both.
IMAGE LEVEL LICENSING:
A universal image that contains all levels of
software packages is loaded on to the device. At boot
time, the device determines the highest level of license
and brings up the appropriate software features or
subsystems.
FEATURE LEVEL LICENSING:
Feature level licensing will support enforcement of
license at individual feature. Features have to check
for their licenses before enabling themselves. If it
does not have a license, the feature should disable
itself.
There is a one-to-one relationship between
a feature and a license. That is, a feature can use
only one license at a time and a license can be used
by only one feature at a time.
LICENSE LINE:
A License line is an atomic set of ASCII characters
arranged in a particular format that holds the license
for a single feature within it. A line has all the
necessary fields and attributes that make it a valid,
non-tamper able and complete license.
LICENSE FILE:
File generated by Cisco licensing portal. It is used
to install license on product. It has a user readable
part and it contains one or more license lines.
DEVICE CREDENTIALS:
Device credentials file is a document that is generated
by a licensed device. This document establishes the
identity of the device and proves that the sender/user
has/had authorized access to the device.
REHOST:
Rehost operation allows a node locked license that
is installed on a device to be installed on other
similar device. As part of rehost operation, a device
processes the permission ticket, revokes the license(s)
on the device and generates a rehost ticket as the
proof of revocation. This rehost ticket needs to be
presented to the Cisco's licensing portal to get the
license transferred on to a new similar device.
PERMISSION TICKET:
Permission ticket is a document generated by Cisco
licensing portal that allows a device to rehost its
licenses.
REHOST TICKET:
Rehost ticket is document generated by a device after
it has applied a permission ticket. The rehost ticket
is a proof of revocation.
LICENSING PORTAL:
Generates licenses, permission tickets and verifies
device credentials and rehost tickets.
This MIB module provides MIB objects to install, clear,
revoke licenses. It also provides objects to regenerate
last rehost ticket, backup all the licenses installed
on a device, generate & export EULA for licenses.
STEPS TO INSTALL A LICENSE:
To install a license, the management application
1. Retrieves device credentials of the device.
2. Communicates with Cisco's licensing portal to get
the license file, uses device credentials to identify
the device
3. Executes the license install action.
STEPS TO CLEAR A LICENSE:
To clear a license, the management application
1. Identifies the license to be cleared using license
index.
2. Executes the license clear action.
STEPS TO REHOST A LICENSE:
To rehost a license, the management application
1. Retrieves device credentials of the device.
2. Communicates with Cisco's licensing portal to get
the permission ticket, uses device credentials to
identify the device.
3. Executes the processPermissionTicket action. Device
revokes the license and generates rehost ticket to be
submitted as proof of revocation.
4. Retrieves device credentials of the device where the
license needs to be transferred to.
5. Submits rehost ticket as proof of revocation to
Cisco's licensing portal, uses device credentials of
the new device to identify the device, gets license
file.
6. Executes the license install action on the new
device.
STEPS TO REGENERATE LAST REHOST TICKET:
To regenerate last rehost ticket, the management
application
1. Retrieves device credentials of the device.
2. Uses already obtained permission ticket or
communicates with Cisco's licensing portal to get
the permission ticket, uses device credentials to
identify the device.
3. Executes the regenerateLastRehostTicket action.
Device generates rehost ticket to be submitted as
proof of revocation.
STEPS TO BACKUP ALL LICENSES:
To backup all licenses installed in the device, the
management application
1. Specifies the backup file path.
2. Executes the license backup action.
STEPS TO GENERATE & EXPORT EULA:
To install certain kind of licenses, the management
application must accept EULA first. The management
application can generate and export EULA for one or
more licenses with out installing licenses as follows.
1. Specifies the license file path that has licenses to be
installed
2. Specifies the EULA file path where EULA need to be
exported to
3. Executes the generate EULA action.
To support the various license actions, this MIB module
also defines MIB objects to know if a device supports
licensing, retrieve device credentials, retrieve
information on license stores in the device.
It also defines MIB objects to expose management
information associated with the licenses installed on the
device, with the licensable features in the software image.
This MIB module also defines various notifications that
will be triggered to asynchronously notify the management
application of any critical events.
This MIB module is defined generically so it can be
implemented on stand alone devices or stack of devices.
In stack of devices, one device in the stack acts as
master agent and rest are slave agents. Each device in the
stack has its own UDI. The master agent receives requests
on behalf of all the devices in the stack including itself
and delegates it to other devices as needed. It also
collects responses from other devices and sends them to
the management application. Examples of such devices include
stackable switches, devices with route processor and line
cards. On the other hand, stand alone device is a single
device and has only one UDI associated with it.
entPhysicalIndex imported from ENTITY-MIB is used to
identify the device uniquely. It is specified as the index
or one of the index for tables in this MIB as needed.
Parsed from file CISCO-LICENSE-MGMT-MIB.my.txt
Company: None
Module: CISCO-LICENSE-MGMT-MIB
The MIB module for managing licenses on the system.
The licensing mechanism provides flexibility to
enforce licensing for various features in the system.
The following text introduces different concepts and
terms those are necessary to understand the MIB definition
and to perform license management.
UDI
Universal Device Identifier that uniquely identifies a
device. It comprises of product ID, version ID and serial
number of the device.
NODE LOCKED LICENSE:
Node locked licenses are locked to one of the device
identifiers in the system. For example, the license
can be locked to the UDI value of one of the devices
in the system. Locking a license to an UDI guarantees
that the license will not be moved to a device with a
different UDI.
NON-NODE LOCKED LICENSE:
Non-node locked licenses are not locked to any device
identifier. They can be used on other similar devices.
METERED LICENSE:
Metered licenses are valid for limited period of time
and they expire after that. This period is the usage
period of a license and it is not based on real time
clock, but system clock.
EULA:
End User License Agreement.
EVALUATION LICENSE:
Evaluation licenses are non-node locked metered
licenses which are valid only for a limited period.
They are used only when there are no permanent,
extension or grace period licenses for a feature.
User will have to accept EULA (End User License
Agreement) before using an evaluation license. Even
though they are not node locked, their usage is
recorded on the device.
RIGHT TO USE (RTU) LICENSE:
Right to use license is a non-node locked metered
license which is in evaluation mode for a limited
time after which it is converted to Right To Use (RTU)
license and is valid for the lifetime of the product.
User will have to accept EULA (End User License Agreement)
before using this license. Even though it is not node
locked, usage information is recorded on the device.
EXTENSION LICENSE:
Extension licenses are node locked metered licenses.
These licenses are issued by Cisco's licensing portal.
These licenses need to be installed using management
interfaces on the device. User will have to accept an
EULA as part of installation of extension license.
GRACE PERIOD LICENSE:
Grace period licenses are node locked metered licenses.
These licenses are issued by Cisco's licensing portal
as part of the permission ticket to rehost a license.
These licenses are installed on the device as part of
the rehost operation. User will have to accept an
EULA as part of the rehost operation for this type
of license. Details on permission ticket, rehost
operations are provided further down in this
description clause.
PERMANENT LICENSE:
Permanent licenses are node locked licenses that have
no usage period associated with them. These licenses
are issued by Cisco's licensing portal. These licenses
need to be installed using management interfaces on
the device. Once these licenses are installed, they
will provide needed permission for the feature/image
across different versions.
COUNTED LICENSE:
Counted licenses limit the number of similar entities
that can use the license. For example, a counted
license when used by a feature can limit the number
of IP phones that can connect or the number of tunnels
that can be created.
UNCOUNTED LICENSE:
Uncounted licenses do not limit the number of similar
entities that can use the licenses.
License can be enforced at the image level or at the feature
level and this MIB module supports both.
IMAGE LEVEL LICENSING:
A universal image that contains all levels of
software packages is loaded on to the device. At boot
time, the device determines the highest level of license
and brings up the appropriate software features or
subsystems.
FEATURE LEVEL LICENSING:
Feature level licensing will support enforcement of
license at individual feature. Features have to check
for their licenses before enabling themselves. If it
does not have a license, the feature should disable
itself.
There is a one-to-one relationship between
a feature and a license. That is, a feature can use
only one license at a time and a license can be used
by only one feature at a time.
LICENSE LINE:
A License line is an atomic set of ASCII characters
arranged in a particular format that holds the license
for a single feature within it. A line has all the
necessary fields and attributes that make it a valid,
non-tamper able and complete license.
LICENSE FILE:
File generated by Cisco licensing portal. It is used
to install license on product. It has a user readable
part and it contains one or more license lines.
DEVICE CREDENTIALS:
Device credentials file is a document that is generated
by a licensed device. This document establishes the
identity of the device and proves that the sender/user
has/had authorized access to the device.
REHOST:
Rehost operation allows a node locked license that
is installed on a device to be installed on other
similar device. As part of rehost operation, a device
processes the permission ticket, revokes the license(s)
on the device and generates a rehost ticket as the
proof of revocation. This rehost ticket needs to be
presented to the Cisco's licensing portal to get the
license transferred on to a new similar device.
PERMISSION TICKET:
Permission ticket is a document generated by Cisco
licensing portal that allows a device to rehost its
licenses.
REHOST TICKET:
Rehost ticket is document generated by a device after
it has applied a permission ticket. The rehost ticket
is a proof of revocation.
LICENSING PORTAL:
Generates licenses, permission tickets and verifies
device credentials and rehost tickets.
This MIB module provides MIB objects to install, clear,
revoke licenses. It also provides objects to regenerate
last rehost ticket, backup all the licenses installed
on a device, generate & export EULA for licenses.
STEPS TO INSTALL A LICENSE:
To install a license, the management application
1. Retrieves device credentials of the device.
2. Communicates with Cisco's licensing portal to get
the license file, uses device credentials to identify
the device
3. Executes the license install action.
STEPS TO CLEAR A LICENSE:
To clear a license, the management application
1. Identifies the license to be cleared using license
index.
2. Executes the license clear action.
STEPS TO REHOST A LICENSE:
To rehost a license, the management application
1. Retrieves device credentials of the device.
2. Communicates with Cisco's licensing portal to get
the permission ticket, uses device credentials to
identify the device.
3. Executes the processPermissionTicket action. Device
revokes the license and generates rehost ticket to be
submitted as proof of revocation.
4. Retrieves device credentials of the device where the
license needs to be transferred to.
5. Submits rehost ticket as proof of revocation to
Cisco's licensing portal, uses device credentials of
the new device to identify the device, gets license
file.
6. Executes the license install action on the new
device.
STEPS TO REGENERATE LAST REHOST TICKET:
To regenerate last rehost ticket, the management
application
1. Retrieves device credentials of the device.
2. Uses already obtained permission ticket or
communicates with Cisco's licensing portal to get
the permission ticket, uses device credentials to
identify the device.
3. Executes the regenerateLastRehostTicket action.
Device generates rehost ticket to be submitted as
proof of revocation.
STEPS TO BACKUP ALL LICENSES:
To backup all licenses installed in the device, the
management application
1. Specifies the backup file path.
2. Executes the license backup action.
STEPS TO GENERATE & EXPORT EULA:
To install certain kind of licenses, the management
application must accept EULA first. The management
application can generate and export EULA for one or
more licenses with out installing licenses as follows.
1. Specifies the license file path that has licenses to be
installed
2. Specifies the EULA file path where EULA need to be
exported to
3. Executes the generate EULA action.
To support the various license actions, this MIB module
also defines MIB objects to know if a device supports
licensing, retrieve device credentials, retrieve
information on license stores in the device.
It also defines MIB objects to expose management
information associated with the licenses installed on the
device, with the licensable features in the software image.
This MIB module also defines various notifications that
will be triggered to asynchronously notify the management
application of any critical events.
This MIB module is defined generically so it can be
implemented on stand alone devices or stack of devices.
In stack of devices, one device in the stack acts as
master agent and rest are slave agents. Each device in the
stack has its own UDI. The master agent receives requests
on behalf of all the devices in the stack including itself
and delegates it to other devices as needed. It also
collects responses from other devices and sends them to
the management application. Examples of such devices include
stackable switches, devices with route processor and line
cards. On the other hand, stand alone device is a single
device and has only one UDI associated with it.
entPhysicalIndex imported from ENTITY-MIB is used to
identify the device uniquely. It is specified as the index
or one of the index for tables in this MIB as needed.
ciscoLicenseMgmtMIB OBJECT IDENTIFIER ::= { ciscoMgmt 543 }
Vendor: Cisco
Module: CISCO-LICENSE-MGMT-MIB
[Automatically extracted from oidview.com]
ciscoLicenseMgmtMIB MODULE-IDENTITY LAST-UPDATED "201104190000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553 -NETS E-mail: [email protected]" DESCRIPTION "The MIB module for managing licenses on the system. The licensing mechanism provides flexibility to enforce licensing for various features in the system. The following text introduces different concepts and terms those are necessary to understand the MIB definition and to perform license management. UDI Universal Device Identifier that uniquely identifies a device. It comprises of product ID, version ID and serial number of the device. NODE LOCKED LICENSE: Node locked licenses are locked to one of the device identifiers in the system. For example, the license can be locked to the UDI value of one of the devices in the system. Locking a license to an UDI guarantees that the license will not be moved to a device with a different UDI. NON-NODE LOCKED LICENSE: Non-node locked licenses are not locked to any device identifier. They can be used on other similar devices. METERED LICENSE: Metered licenses are valid for limited period of time and they expire after that. This period is the usage period of a license and it is not based on real time clock, but system clock. EULA: End User License Agreement. EVALUATION LICENSE: Evaluation licenses are non-node locked metered licenses which are valid only for a limited period. They are used only when there are no permanent, extension or grace period licenses for a feature. User will have to accept EULA (End User License Agreement) before using an evaluation license. Even though they are not node locked, their usage is recorded on the device. RIGHT TO USE (RTU) LICENSE: Right to use license is a non-node locked metered license which is in evaluation mode for a limited time after which it is converted to Right To Use (RTU) license and is valid for the lifetime of the product. User will have to accept EULA (End User License Agreement) before using this license. Even though it is not node locked, usage information is recorded on the device. EXTENSION LICENSE: Extension licenses are node locked metered licenses. These licenses are issued by Cisco's licensing portal. These licenses need to be installed using management interfaces on the device. User will have to accept an EULA as part of installation of extension license. GRACE PERIOD LICENSE: Grace period licenses are node locked metered licenses. These licenses are issued by Cisco's licensing portal as part of the permission ticket to rehost a license. These licenses are installed on the device as part of the rehost operation. User will have to accept an EULA as part of the rehost operation for this type of license. Details on permission ticket, rehost operations are provided further down in this description clause. PERMANENT LICENSE: Permanent licenses are node locked licenses that have no usage period associated with them. These licenses are issued by Cisco's licensing portal. These licenses need to be installed using management interfaces on the device. Once these licenses are installed, they will provide needed permission for the feature/image across different versions. COUNTED LICENSE: Counted licenses limit the number of similar entities that can use the license. For example, a counted license when used by a feature can limit the number of IP phones that can connect or the number of tunnels that can be created. UNCOUNTED LICENSE: Uncounted licenses do not limit the number of similar entities that can use the licenses. License can be enforced at the image level or at the feature level and this MIB module supports both. IMAGE LEVEL LICENSING: A universal image that contains all levels of software packages is loaded on to the device. At boot time, the device determines the highest level of license and brings up the appropriate software features or subsystems. FEATURE LEVEL LICENSING: Feature level licensing will support enforcement of license at individual feature. Features have to check for their licenses before enabling themselves. If it does not have a license, the feature should disable itself. There is a one-to-one relationship between a feature and a license. That is, a feature can use only one license at a time and a license can be used by only one feature at a time. LICENSE LINE: A License line is an atomic set of ASCII characters arranged in a particular format that holds the license for a single feature within it. A line has all the necessary fields and attributes that make it a valid, non-tamper able and complete license. LICENSE FILE: File generated by Cisco licensing portal. It is used to install license on product. It has a user readable part and it contains one or more license lines. DEVICE CREDENTIALS: Device credentials file is a document that is generated by a licensed device. This document establishes the identity of the device and proves that the sender/user has/had authorized access to the device. REHOST: Rehost operation allows a node locked license that is installed on a device to be installed on other similar device. As part of rehost operation, a device processes the permission ticket, revokes the license(s) on the device and generates a rehost ticket as the proof of revocation. This rehost ticket needs to be presented to the Cisco's licensing portal to get the license transferred on to a new similar device. PERMISSION TICKET: Permission ticket is a document generated by Cisco licensing portal that allows a device to rehost its licenses. REHOST TICKET: Rehost ticket is document generated by a device after it has applied a permission ticket. The rehost ticket is a proof of revocation. LICENSING PORTAL: Generates licenses, permission tickets and verifies device credentials and rehost tickets. This MIB module provides MIB objects to install, clear, revoke licenses. It also provides objects to regenerate last rehost ticket, backup all the licenses installed on a device, generate & export EULA for licenses. STEPS TO INSTALL A LICENSE: To install a license, the management application 1. Retrieves device credentials of the device. 2. Communicates with Cisco's licensing portal to get the license file, uses device credentials to identify the device 3. Executes the license install action. STEPS TO CLEAR A LICENSE: To clear a license, the management application 1. Identifies the license to be cleared using license index. 2. Executes the license clear action. STEPS TO REHOST A LICENSE: To rehost a license, the management application 1. Retrieves device credentials of the device. 2. Communicates with Cisco's licensing portal to get the permission ticket, uses device credentials to identify the device. 3. Executes the processPermissionTicket action. Device revokes the license and generates rehost ticket to be submitted as proof of revocation. 4. Retrieves device credentials of the device where the license needs to be transferred to. 5. Submits rehost ticket as proof of revocation to Cisco's licensing portal, uses device credentials of the new device to identify the device, gets license file. 6. Executes the license install action on the new device. STEPS TO REGENERATE LAST REHOST TICKET: To regenerate last rehost ticket, the management application 1. Retrieves device credentials of the device. 2. Uses already obtained permission ticket or communicates with Cisco's licensing portal to get the permission ticket, uses device credentials to identify the device. 3. Executes the regenerateLastRehostTicket action. Device generates rehost ticket to be submitted as proof of revocation. STEPS TO BACKUP ALL LICENSES: To backup all licenses installed in the device, the management application 1. Specifies the backup file path. 2. Executes the license backup action. STEPS TO GENERATE & EXPORT EULA: To install certain kind of licenses, the management application must accept EULA first. The management application can generate and export EULA for one or more licenses with out installing licenses as follows. 1. Specifies the license file path that has licenses to be installed 2. Specifies the EULA file path where EULA need to be exported to 3. Executes the generate EULA action. To support the various license actions, this MIB module also defines MIB objects to know if a device supports licensing, retrieve device credentials, retrieve information on license stores in the device. It also defines MIB objects to expose management information associated with the licenses installed on the device, with the licensable features in the software image. This MIB module also defines various notifications that will be triggered to asynchronously notify the management application of any critical events. This MIB module is defined generically so it can be implemented on stand alone devices or stack of devices. In stack of devices, one device in the stack acts as master agent and rest are slave agents. Each device in the stack has its own UDI. The master agent receives requests on behalf of all the devices in the stack including itself and delegates it to other devices as needed. It also collects responses from other devices and sends them to the management application. Examples of such devices include stackable switches, devices with route processor and line cards. On the other hand, stand alone device is a single device and has only one UDI associated with it. entPhysicalIndex imported from ENTITY-MIB is used to identify the device uniquely. It is specified as the index or one of the index for tables in this MIB as needed." REVISION "201104190000Z" DESCRIPTION "This version of the MIB adds support for Right to use (RTU) licensing. The revisions are: o Added RTU license definition to MIB description above. o Updated clmgmtLicenseType object to support the following new types of license: evalRightToUse rightToUse o Added following objects to clmgmtLicenseInfoTable clmgmtLicensePeriodUsed o Added following objects to clmgmtLicensableFeatureTable clmgmtFeaturePeriodUsed o Added the following notifications clmgmtLicenseEvalRTUTransitionWarning clmgmtLicenseEvalRTUTransition o Added the following conformance groups clmgmtLicenseRTUGroup clmgmtLicenseRTUUsageNotifGroup The new module compliance is ciscoLicenseMgmtComplianceRev1." REVISION "200811210000Z" DESCRIPTION "This version of the MIB adds support for subscription licensing. Subscription licenses provide software enforcement for a licensed feature for a fixed calendar period. The revisions are: o Updated clmgmtLicenseType object to support the following three new types of licenses: paidSubscription evaluationSubscription extensionSubscription o Added following objects to clmgmtLicenseInfoTable clmgmtLicenseStartDate clmgmtLicenseEndDate o Added following objects to clmgmtLicensableFeatureTable clmgmtFeatureStartDate clmgmtFeatureEndDate o Added the following notifications clmgmtLicenseSubscriptionExpiryWarning clmgmtLicenseSubscriptionExtExpiryWarning clmgmtLicenseSubscriptionExpired o Added the following conformance groups clmgmtLicenseSubscriptionGroup clmgmtLicenseSubscriptionUsageNotifGroup The new module compliance is ciscoLicenseMgmtComplianceRev1." REVISION "200610030000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 543 }
ciscoLicenseMgmtMIB MODULE-IDENTITY LAST-UPDATED "201204190000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553 -NETS E-mail: [email protected]" DESCRIPTION "The MIB module for managing licenses on the system. The licensing mechanism provides flexibility to enforce licensing for various features in the system. The following text introduces different concepts and terms those are necessary to understand the MIB definition and to perform license management. UDI Universal Device Identifier that uniquely identifies a device. It comprises of product ID, version ID and serial number of the device. NODE LOCKED LICENSE: Node locked licenses are locked to one of the device identifiers in the system. For example, the license can be locked to the UDI value of one of the devices in the system. Locking a license to an UDI guarantees that the license will not be moved to a device with a different UDI. NON-NODE LOCKED LICENSE: Non-node locked licenses are not locked to any device identifier. They can be used on other similar devices. METERED LICENSE: Metered licenses are valid for limited period of time and they expire after that. This period is the usage period of a license and it is not based on real time clock, but system clock. EULA: End User License Agreement. EVALUATION LICENSE: Evaluation licenses are non-node locked metered licenses which are valid only for a limited period. They are used only when there are no permanent, extension or grace period licenses for a feature. User will have to accept EULA (End User License Agreement) before using an evaluation license. Even though they are not node locked, their usage is recorded on the device. RIGHT TO USE (RTU) LICENSE: Right to use license is a non-node locked metered license which is in evaluation mode for a limited time after which it is converted to Right To Use (RTU) license and is valid for the lifetime of the product. User will have to accept EULA (End User License Agreement) before using this license. Even though it is not node locked, usage information is recorded on the device. EXTENSION LICENSE: Extension licenses are node locked metered licenses. These licenses are issued by Cisco's licensing portal. These licenses need to be installed using management interfaces on the device. User will have to accept an EULA as part of installation of extension license. GRACE PERIOD LICENSE: Grace period licenses are node locked metered licenses. These licenses are issued by Cisco's licensing portal as part of the permission ticket to rehost a license. These licenses are installed on the device as part of the rehost operation. User will have to accept an EULA as part of the rehost operation for this type of license. Details on permission ticket, rehost operations are provided further down in this description clause. PERMANENT LICENSE: Permanent licenses are node locked licenses that have no usage period associated with them. These licenses are issued by Cisco's licensing portal. These licenses need to be installed using management interfaces on the device. Once these licenses are installed, they will provide needed permission for the feature/image across different versions. COUNTED LICENSE: Counted licenses limit the number of similar entities that can use the license. For example, a counted license when used by a feature can limit the number of IP phones that can connect or the number of tunnels that can be created. UNCOUNTED LICENSE: Uncounted licenses do not limit the number of similar entities that can use the licenses. License can be enforced at the image level or at the feature level and this MIB module supports both. IMAGE LEVEL LICENSING: A universal image that contains all levels of software packages is loaded on to the device. At boot time, the device determines the highest level of license and brings up the appropriate software features or subsystems. FEATURE LEVEL LICENSING: Feature level licensing will support enforcement of license at individual feature. Features have to check for their licenses before enabling themselves. If it does not have a license, the feature should disable itself. There is a one-to-one relationship between a feature and a license. That is, a feature can use only one license at a time and a license can be used by only one feature at a time. LICENSE LINE: A License line is an atomic set of ASCII characters arranged in a particular format that holds the license for a single feature within it. A line has all the necessary fields and attributes that make it a valid, non-tamper able and complete license. LICENSE FILE: File generated by Cisco licensing portal. It is used to install license on product. It has a user readable part and it contains one or more license lines. DEVICE CREDENTIALS: Device credentials file is a document that is generated by a licensed device. This document establishes the identity of the device and proves that the sender/user has/had authorized access to the device. REHOST: Rehost operation allows a node locked license that is installed on a device to be installed on other similar device. As part of rehost operation, a device processes the permission ticket, revokes the license(s) on the device and generates a rehost ticket as the proof of revocation. This rehost ticket needs to be presented to the Cisco's licensing portal to get the license transferred on to a new similar device. PERMISSION TICKET: Permission ticket is a document generated by Cisco licensing portal that allows a device to rehost its licenses. REHOST TICKET: Rehost ticket is document generated by a device after it has applied a permission ticket. The rehost ticket is a proof of revocation. LICENSING PORTAL: Generates licenses, permission tickets and verifies device credentials and rehost tickets. This MIB module provides MIB objects to install, clear, revoke licenses. It also provides objects to regenerate last rehost ticket, backup all the licenses installed on a device, generate & export EULA for licenses. STEPS TO INSTALL A LICENSE: To install a license, the management application 1. Retrieves device credentials of the device. 2. Communicates with Cisco's licensing portal to get the license file, uses device credentials to identify the device 3. Executes the license install action. STEPS TO CLEAR A LICENSE: To clear a license, the management application 1. Identifies the license to be cleared using license index. 2. Executes the license clear action. STEPS TO REHOST A LICENSE: To rehost a license, the management application 1. Retrieves device credentials of the device. 2. Communicates with Cisco's licensing portal to get the permission ticket, uses device credentials to identify the device. 3. Executes the processPermissionTicket action. Device revokes the license and generates rehost ticket to be submitted as proof of revocation. 4. Retrieves device credentials of the device where the license needs to be transferred to. 5. Submits rehost ticket as proof of revocation to Cisco's licensing portal, uses device credentials of the new device to identify the device, gets license file. 6. Executes the license install action on the new device. STEPS TO REGENERATE LAST REHOST TICKET: To regenerate last rehost ticket, the management application 1. Retrieves device credentials of the device. 2. Uses already obtained permission ticket or communicates with Cisco's licensing portal to get the permission ticket, uses device credentials to identify the device. 3. Executes the regenerateLastRehostTicket action. Device generates rehost ticket to be submitted as proof of revocation. STEPS TO BACKUP ALL LICENSES: To backup all licenses installed in the device, the management application 1. Specifies the backup file path. 2. Executes the license backup action. STEPS TO GENERATE & EXPORT EULA: To install certain kind of licenses, the management application must accept EULA first. The management application can generate and export EULA for one or more licenses with out installing licenses as follows. 1. Specifies the license file path that has licenses to be installed 2. Specifies the EULA file path where EULA need to be exported to 3. Executes the generate EULA action. To support the various license actions, this MIB module also defines MIB objects to know if a device supports licensing, retrieve device credentials, retrieve information on license stores in the device. It also defines MIB objects to expose management information associated with the licenses installed on the device, with the licensable features in the software image. This MIB module also defines various notifications that will be triggered to asynchronously notify the management application of any critical events. This MIB module is defined generically so it can be implemented on stand alone devices or stack of devices. In stack of devices, one device in the stack acts as master agent and rest are slave agents. Each device in the stack has its own UDI. The master agent receives requests on behalf of all the devices in the stack including itself and delegates it to other devices as needed. It also collects responses from other devices and sends them to the management application. Examples of such devices include stackable switches, devices with route processor and line cards. On the other hand, stand alone device is a single device and has only one UDI associated with it. entPhysicalIndex imported from ENTITY-MIB is used to identify the device uniquely. It is specified as the index or one of the index for tables in this MIB as needed." REVISION "201204190000Z" DESCRIPTION "This version of the MIB adds support for Permanent Right to use (RTU) licensing. The revisions are: o Updated clmgmtLicenseType object to support the following new types of license: permanentRightToUse The new module compliance is ciscoLicenseMgmtComplianceRev1." REVISION "201104190000Z" DESCRIPTION "This version of the MIB adds support for Right to use (RTU) licensing. The revisions are: o Added RTU license definition to MIB description above. o Updated clmgmtLicenseType object to support the following new types of license: evalRightToUse rightToUse o Added following objects to clmgmtLicenseInfoTable clmgmtLicensePeriodUsed o Added following objects to clmgmtLicensableFeatureTable clmgmtFeaturePeriodUsed o Added the following notifications clmgmtLicenseEvalRTUTransitionWarning clmgmtLicenseEvalRTUTransition o Added the following conformance groups clmgmtLicenseRTUGroup clmgmtLicenseRTUUsageNotifGroup The new module compliance is ciscoLicenseMgmtComplianceRev1." REVISION "200811210000Z" DESCRIPTION "This version of the MIB adds support for subscription licensing. Subscription licenses provide software enforcement for a licensed feature for a fixed calendar period. The revisions are: o Updated clmgmtLicenseType object to support the following three new types of licenses: paidSubscription evaluationSubscription extensionSubscription o Added following objects to clmgmtLicenseInfoTable clmgmtLicenseStartDate clmgmtLicenseEndDate o Added following objects to clmgmtLicensableFeatureTable clmgmtFeatureStartDate clmgmtFeatureEndDate o Added the following notifications clmgmtLicenseSubscriptionExpiryWarning clmgmtLicenseSubscriptionExtExpiryWarning clmgmtLicenseSubscriptionExpired o Added the following conformance groups clmgmtLicenseSubscriptionGroup clmgmtLicenseSubscriptionUsageNotifGroup The new module compliance is ciscoLicenseMgmtComplianceRev1." REVISION "200610030000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 543 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.543.0 | ciscoLicenseMgmtMIBNotifs | 14 | 14 | None |
| 1.3.6.1.4.1.9.9.543.1 | ciscoLicenseMgmtMIBObjects | 4 | 96 | None |
| 1.3.6.1.4.1.9.9.543.2 | ciscoLicenseMgmtMIBConform | 2 | 18 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.493 | ciscoCefTextualConventions | 0 | 0 | ciscoCeftextualConventions |
| 1.3.6.1.4.1.9.9.494 | ciscoEntityRedunTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Entity Redundancy MIBs. |
| 1.3.6.1.4.1.9.9.495 | ciscoPsdClientMIB | 3 | 44 | This MIB module manages the client side functionality of the Persistent Storage Device(PSD). This MIB instrumentation is for conf… |
| 1.3.6.1.4.1.9.9.497 | cGgsnSAMIB | 3 | 247 | This MIB module manages the service-aware feature of Gateway GPRS Support Node (GGSN). This MIB is an enhancement of the CISCO-GG… |
| 1.3.6.1.4.1.9.9.498 | ciscoEntityRedunMIB | 3 | 93 | This management information module supports configuration, control and monitoring of redundancy protection for various kinds of c… |
| 1.3.6.1.4.1.9.9.500 | ciscoStackWiseMIB | 3 | 111 | This MIB module contain a collection of managed objects that apply to network devices supporting the Cisco StackWise(TM) technolo… |
| 1.3.6.1.4.1.9.9.504 | ciscoSwitchMulticastMIB | 3 | 108 | This MIB module defines management objects for the Multicast Switching features on Cisco Layer 2/3 devices. Definition of some of … |
| 1.3.6.1.4.1.9.9.505 | cpkiMIB | 3 | 44 | A networking device may provide several security services and protocols like SSL, SSH, IPSec/IKE etc. which need identities … |
| 1.3.6.1.4.1.9.9.507 | ciscoPolicyGroupMIB | 3 | 35 | The MIB module is for configuration of policy and policy group. A policy group can be described as a set of entities identified b… |
| 1.3.6.1.4.1.9.9.508 | ciscoSlbHealthMonMIB | 3 | 62 | An extension to the CISCO-SLB-EXT-MIB for SLB health monitoring probes. SLB: Server Load Balancing. Server load balancing provides… |
| 1.3.6.1.4.1.9.9.509 | ciscoWdsInfoMIB | 3 | 141 | This MIB is intended to be implemented on all Cisco network entities that provide Wireless Domain Services (WDS). The WDS provide… |
| 1.3.6.1.4.1.9.9.510 | ciscoErmMIB, ciscoVoiceLmrMIB | 3 | 176 | This MIB module provides management of voice tone signal as static injected tone for Land Mobile Radio The tone signal includes … |
| 1.3.6.1.4.1.9.9.511 | ciscoCbpTargetTCMIB | 0 | 0 | This MIB module defines Textual Conventions for representing targets which have class based policy mappings. A target can be any … |
| 1.3.6.1.4.1.9.9.512 | ciscoLwappWlanMIB | 3 | 249 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weigh… |
| 1.3.6.1.4.1.9.9.513 | ciscoLwappApMIB | 4 | 386 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.514 | ciscoLwappTextualConventions | 0 | 0 | This module defines textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Controlle… |
| 1.3.6.1.4.1.9.9.515 | ciscoLwappWebAuthMIB | 4 | 43 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.516 | ciscoLwappLinkTestMIB | 3 | 57 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.517 | ciscoLwappReapMIB | 3 | 63 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.518 | ciscoLwappMfpMIB | 4 | 64 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.519 | ciscoLwappIdsMIB | 3 | 28 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.520 | ciscoLwappCcxRmMIB | 3 | 45 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.521 | ciscoLwappWlanSecurityMIB | 3 | 51 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.522 | ciscoLwappDot11ClientCalibMIB | 3 | 50 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.523 | ciscoLwappClRoamMIB | 3 | 61 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.524 | ciscoLwappQosMIB | 3 | 119 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.525 | ciscoLwappTsmMIB | 3 | 57 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.529 | ciscoItpMsuRatesMIB | 3 | 61 | This MIB provides information used to manage the number of MTP3 MSUs transmitted and received per processor. Many of the higher … |
| 1.3.6.1.4.1.9.9.530 | ciscoNacTcMIB | 0 | 0 | This module defines the textual conventions for Cisco Network Admission Control(NAC) system. The Cisco Network Admission Control … |
| 1.3.6.1.4.1.9.9.532 | ciscoNATExtMIB | 3 | 13 | This MIB is an extension to the NAT-MIB. This MIB module includes objects for providing the NAT related statistics. Acronyms: NAT… |
| 1.3.6.1.4.1.9.9.533 | ciscoCbpTargetMIB | 3 | 25 | This MIB module defines the managed objects for representing targets which have class-based policy mappings. A target can be any… |
| 1.3.6.1.4.1.9.9.548 | ciscoErrDisableMIB | 3 | 43 | This MIB module provides the ability for a Network Management Station (NMS) to configure and monitor the error-disable feature vi… |
| 1.3.6.1.4.1.9.9.572 | ciscoRttMonIPExtMIB | 2 | 38 | This MIB contains extensions to tables in CISCO-RTTMON-MIB to support IP-layer extensions, specifically IPv6 addresses and other … |
| 1.3.6.1.4.1.9.9.573 | ciscoQosTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Qos MIBs. |
| 1.3.6.1.4.1.9.9.576 | ciscoLwappMobilityMIB | 3 | 60 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.577 | ciscoLwappAclMIB | 3 | 26 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.578 | ciscoRoutePoliciesMIB | 3 | 5 | This module provides a subtree to define OIDs so that various routing 'policies' used by Cisco routers can be expressed. This mod… |
| 1.3.6.1.4.1.9.9.580 | ciscoSwitchQosMIB | 3 | 295 | This MIB module extends the CISCO-CLASS-BASED-QOS-MIB by defining configuration and statistics information specific to the qualit… |
| 1.3.6.1.4.1.9.9.583 | ciscoGslbTcMIB | 0 | 0 | This MIB module defines Textual Conventions and OBJECT-IDENTITIES for use in documents defining management information base (MIBs… |
| 1.3.6.1.4.1.9.9.584 | ciscoEntityDiagTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Entity Diag MIB. |
| 1.3.6.1.4.1.9.9.585 | ciscoIpSlaEthernetMIB | 3 | 194 | This MIB module consists of two parts. 1) Auto-Ethernet-CFM Control: | | 2) ethernetJitter Stats: | | The first part defines a mechani… |
| 1.3.6.1.4.1.9.9.586 | ciscoNotificationControlMIB | 2 | 28 | This MIB provides network management support to regulate the transmission of notifications generated by a system providing networ… |
| 1.3.6.1.4.1.9.9.589 | ciscoGslbSystemMIB | 3 | 103 | This MIB module defines objects for network and system information of Global Server Load Balancer(GSLB) as a network device. A G… |
| 1.3.6.1.4.1.9.9.590 | ciscoCvpMIB | 3 | 255 | The Cisco Unified Customer Voice Portal (CVP) application integrates with both traditional time-division multiplexing (TDM) and I… |
| 1.3.6.1.4.1.9.9.592 | ciscoPrefPathMIB | 3 | 56 | The MIB module for the management of preferred path. This MIB enables managers to configure and monitor Preferred Path parameters.… |
| 1.3.6.1.4.1.9.9.593 | ciscoFcSdvMIB | 3 | 28 | This MIB instrumentation is for managing Fibre Channel (FC) SAN Device Virtualization (SDV) solution on Cisco Fibre Channel devic… |
| ... | ||||