CISCO-IMAGE-LICENSE-MGMT-MIB

        The MIB module for managing the running image level
of a Cisco device. Cisco's licensing mechanism provides
flexibility to run a device on a chosen image level.
This mechanism is referred to as image level licensing.
Image level licensing leverages the universal image
based licensing solution.
        
The image level licensing mechanism works as follows - 
        
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.
The user can configure the image level with which the
device has to boot. The system will verify whether the
appropriate license is available for the configured image
level. The image level for the next boot will be determined
based on the availability of the license. The following
scenarios explains some use-cases of image level licensing:
        
Scenario 1:
- Customer selects advsecurityk9 based image.
- Manufacturing installs advsecurity license on the device.
- This device will run all features that are part of the
base advsecurity license.
- Customer upgrades to advipservicesk9 license.
- The next boot level is set to advipservicesk9.
- The device will run advsecurityk9 feature until the
next reboot. After reboot the device will run 
advipservicesk9 features.
        
Scenario 2:
- Customer selects advipservicesk9 based image.
- Manufacturing installs advipservices and advsecurity
license on the device.
- This device will run all features that are part of the
base advipservices license.
- No upgrades available for advipservices license.
        
The user has to accept the End User License Agreement(EULA)
before using this MIB to configure the image level. 
        
This MIB should be used in conjuntion with
CISCO-LICENSE-MGMT-MIB module to achieve the image level
licensing functionality.
        
This MIB module defines objects which provides the different
image levels supported by the device and the license required
to enable a particular image level. It also defines objects
to let the user configure the required image level. The MIB 
module contains notification which will be triggered when
the user changes the image level for next boot. 
        
The CISCO-LICENSE-MGMT-MIB module should be used to export
the EULA and to configure the required license.
        
This MIB module is defined generically so it can be used for
both stand-alone as well as stackable devices. The
entPhysicalIndex imported from ENTITY-MIB is used to identify
the device uniquely.
    
Source file
CISCO-IMAGE-LICENSE-MGMT-MIB
Last revised
Identity
ciscoImageLicenseMgmtMIB
Base OID
1.3.6.1.4.1.9.9.640
Imported Objects
CISCO-SMI ciscoMgmt
ENTITY-MIB entPhysicalIndex
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC TEXTUAL-CONVENTION (no object page) TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-IMAGE-LICENSE-MGMT-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-IMAGE-LICENSE-MGMT-MIB::ciscoImageLicenseMgmtMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-IMAGE-LICENSE-MGMT-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-IMAGE-LICENSE-MGMT-MIB::ciscoImageLicenseMgmtMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (25)
.1.3.6.1.4.1.9.9.640
.1.3.6.1.4.1.9.9.640.0
.1.3.6.1.4.1.9.9.640.1
.1.3.6.1.4.1.9.9.640.1.1
.1.3.6.1.4.1.9.9.640.1.1.1
.1.3.6.1.4.1.9.9.640.1.1.1.1
.1.3.6.1.4.1.9.9.640.1.1.1.2
.1.3.6.1.4.1.9.9.640.1.1.1.3
.1.3.6.1.4.1.9.9.640.1.1.1.4
.1.3.6.1.4.1.9.9.640.1.1.1.5
.1.3.6.1.4.1.9.9.640.1.1.1.6
.1.3.6.1.4.1.9.9.640.1.1.1.7
.1.3.6.1.4.1.9.9.640.1.1.1.8
.1.3.6.1.4.1.9.9.640.1.2
.1.3.6.1.4.1.9.9.640.1.2.1
.1.3.6.1.4.1.9.9.640.1.2.1.1
.1.3.6.1.4.1.9.9.640.1.2.1.2
.1.3.6.1.4.1.9.9.640.1.2.1.3
Unsigned32
.1.3.6.1.4.1.9.9.640.1.2.1.4
.1.3.6.1.4.1.9.9.640.1.3
.1.3.6.1.4.1.9.9.640.1.4
.1.3.6.1.4.1.9.9.640.1.4.1
.1.3.6.1.4.1.9.9.640.2
.1.3.6.1.4.1.9.9.640.2.1
.1.3.6.1.4.1.9.9.640.2.2
Dependencies (8) 6 direct · 2 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (2)
OctetString range: 0..255
OctetString range: 0..255
Conformance Groups (3)
Objects for performing license set operation for setting
next boot level.
.1.3.6.1.4.1.9.9.640.2.2.1
Objects for getting current image level configuration data.
.1.3.6.1.4.1.9.9.640.2.2.2
Objects for getting current image level configuration data.
.1.3.6.1.4.1.9.9.640.2.2.3
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.640.2.1.1
Compliance statement for Cisco Image level license mgmt MIB.
Required groups
mandatory cilmAdminGroup
mandatory cilmNotifGroup
optional cilmOperGroup This group is mandatory for all devices where
multiple license are supported.
Notifications / Traps (1)
NameOIDDescription
.1.3.6.1.4.1.9.9.640.0.1
This notification is triggered when next boot image level
is changed in the management entity. The current and
configured image level are indicated by cilmCurrentImageLevel
and cilmConfiguredBootImageLevel objects respectively.