This table contains entries for those physical entities into
which licenses have been physically programmed. Depending
upon the implementation, this may involve programming the
licenses into the non-volatile ram (NVRAM) of a physical
entity, such as a service module.
An entry in this table is automatically created for those
entities which contain such licenses. This table exists
independently of all previous tables described in this MIB.
The following example illustrates the use of this table for
a specific implementation:
For a module, if the object celPhysicallyProgLicenseStatus has
the value 'hasInstallableLic', it means that this module has
never had its programmed licenses installed (or transferred)
into any chassis, and therefore its license can be installed
(or transferred) if needed. If installation (or transferring)
of licenses (programmed on the entity) takes place, it
results in incrementing the number of licenses in the
license pool (object celPoolLicensesInstalled) for the
vendor-specific hardware type corresponding to this module.
Once the licenses from the module have been installed (or
transferred) into the chassis, the value of the object
celPhysicallyProgLicenseStatus changes to 'alreadyInstalled'.
This prevents any re-installation or re-use of licenses. This
example shows the usage of the module as a vehicle for
installing (or transporting) licenses into the license pool.
Parsed from file CISCO-LICENSE-MIB.mib
Module: CISCO-LICENSE-MIB
This table contains entries for those physical entities into
which licenses have been physically programmed. Depending
upon the implementation, this may involve programming the
licenses into the non-volatile ram (NVRAM) of a physical
entity, such as a service module.
An entry in this table is automatically created for those
entities which contain such licenses. This table exists
independently of all previous tables described in this MIB.
The following example illustrates the use of this table for
a specific implementation:
For a module, if the object celPhysicallyProgLicenseStatus has
the value 'hasInstallableLic', it means that this module has
never had its programmed licenses installed (or transferred)
into any chassis, and therefore its license can be installed
(or transferred) if needed. If installation (or transferring)
of licenses (programmed on the entity) takes place, it
results in incrementing the number of licenses in the
license pool (object celPoolLicensesInstalled) for the
vendor-specific hardware type corresponding to this module.
Once the licenses from the module have been installed (or
transferred) into the chassis, the value of the object
celPhysicallyProgLicenseStatus changes to 'alreadyInstalled'.
This prevents any re-installation or re-use of licenses. This
example shows the usage of the module as a vehicle for
installing (or transporting) licenses into the license pool.
Parsed from file CISCO-LICENSE-MIB.my.txt
Company: None
Module: CISCO-LICENSE-MIB
This table contains entries for those physical entities into
which licenses have been physically programmed. Depending
upon the implementation, this may involve programming the
licenses into the non-volatile ram (NVRAM) of a physical
entity, such as a service module.
An entry in this table is automatically created for those
entities which contain such licenses. This table exists
independently of all previous tables described in this MIB.
The following example illustrates the use of this table for
a specific implementation:
For a module, if the object celPhysicallyProgLicenseStatus has
the value 'hasInstallableLic', it means that this module has
never had its programmed licenses installed (or transferred)
into any chassis, and therefore its license can be installed
(or transferred) if needed. If installation (or transferring)
of licenses (programmed on the entity) takes place, it
results in incrementing the number of licenses in the
license pool (object celPoolLicensesInstalled) for the
vendor-specific hardware type corresponding to this module.
Once the licenses from the module have been installed (or
transferred) into the chassis, the value of the object
celPhysicallyProgLicenseStatus changes to 'alreadyInstalled'.
This prevents any re-installation or re-use of licenses. This
example shows the usage of the module as a vehicle for
installing (or transporting) licenses into the license pool.
celPhysicallyProgLicenseTable OBJECT-TYPE SYNTAX SEQUENCE OF CelPhysicallyProgLicenseEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains entries for those physical entities into which licenses have been physically programmed. Depending upon the implementation, this may involve programming the licenses into the non-volatile ram (NVRAM) of a physical entity, such as a service module. An entry in this table is automatically created for those entities which contain such licenses. This table exists independently of all previous tables described in this MIB. The following example illustrates the use of this table for a specific implementation: For a module, if the object celPhysicallyProgLicenseStatus has the value 'hasInstallableLic', it means that this module has never had its programmed licenses installed (or transferred) into any chassis, and therefore its license can be installed (or transferred) if needed. If installation (or transferring) of licenses (programmed on the entity) takes place, it results in incrementing the number of licenses in the license pool (object celPoolLicensesInstalled) for the vendor-specific hardware type corresponding to this module. Once the licenses from the module have been installed (or transferred) into the chassis, the value of the object celPhysicallyProgLicenseStatus changes to 'alreadyInstalled'. This prevents any re-installation or re-use of licenses. This example shows the usage of the module as a vehicle for installing (or transporting) licenses into the license pool. " ::= { celGeneral 5}
Vendor: Cisco
Module: CISCO-LICENSE-MIB
[Automatically extracted from oidview.com]
celPhysicallyProgLicenseTable OBJECT-TYPE SYNTAX SEQUENCE OF CelPhysicallyProgLicenseEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains entries for those physical entities into which licenses have been physically programmed. Depending upon the implementation, this may involve programming the licenses into the non-volatile ram (NVRAM) of a physical entity, such as a service module. An entry in this table is automatically created for those entities which contain such licenses. This table exists independently of all previous tables described in this MIB. The following example illustrates the use of this table for a specific implementation: For a module, if the object celPhysicallyProgLicenseStatus has the value 'hasInstallableLic', it means that this module has never had its programmed licenses installed (or transferred) into any chassis, and therefore its license can be installed (or transferred) if needed. If installation (or transferring) of licenses (programmed on the entity) takes place, it results in incrementing the number of licenses in the license pool (object celPoolLicensesInstalled) for the vendor-specific hardware type corresponding to this module. Once the licenses from the module have been installed (or transferred) into the chassis, the value of the object celPhysicallyProgLicenseStatus changes to 'alreadyInstalled'. This prevents any re-installation or re-use of licenses. This example shows the usage of the module as a vehicle for installing (or transporting) licenses into the license pool. " ::= { celGeneral 5}
celPhysicallyProgLicenseTable OBJECT-TYPE SYNTAX SEQUENCE OF CelPhysicallyProgLicenseEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains entries for those physical entities into which licenses have been physically programmed. Depending upon the implementation, this may involve programming the licenses into the non-volatile ram (NVRAM) of a physical entity, such as a service module. An entry in this table is automatically created for those entities which contain such licenses. This table exists independently of all previous tables described in this MIB. The following example illustrates the use of this table for a specific implementation: For a module, if the object celPhysicallyProgLicenseStatus has the value 'hasInstallableLic', it means that this module has never had its programmed licenses installed (or transferred) into any chassis, and therefore its license can be installed (or transferred) if needed. If installation (or transferring) of licenses (programmed on the entity) takes place, it results in incrementing the number of licenses in the license pool (object celPoolLicensesInstalled) for the vendor-specific hardware type corresponding to this module. Once the licenses from the module have been installed (or transferred) into the chassis, the value of the object celPhysicallyProgLicenseStatus changes to 'alreadyInstalled'. This prevents any re-installation or re-use of licenses. This example shows the usage of the module as a vehicle for installing (or transporting) licenses into the license pool. " ::= { celGeneral 5}
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.359.1.1.5.1 | celPhysicallyProgLicenseEntry | 10 | 10 | Entry containing details on a physically programmed license. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.359.1.1.1 | celLicenseConfigHistoryTable | 1 | 9 | This table keeps track of the license installation history. Each time licenses are installed, a record is made in one of the entr… |
| 1.3.6.1.4.1.9.9.359.1.1.2 | celLicenseConfigDetailTable | 1 | 4 | For each entry in the table celLicenseConfigHistoryTable, this table expands the information showing the installed type of licens… |
| 1.3.6.1.4.1.9.9.359.1.1.3 | celPoolLicenseTable | 1 | 7 | This table contains the inventory of installed licenses and completely defines the license pool owned by the SNMP agent implement… |
| 1.3.6.1.4.1.9.9.359.1.1.4 | celInUseLicenseTable | 1 | 8 | This table contains entries showing the entities (physical or otherwise) that are using up licenses, and the number and type of l… |