MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 359 (ciscoLicenseMIB). 1 (celMIBObjects). 1 (celGeneral). 5 (celPhysicallyProgLicenseTable)
OID : 1.3.6.1.4.1.9.9.359.1.1.5
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. ciscoLicenseMIB. celMIBObjects. celGeneral. celPhysicallyProgLicenseTable
Enfants
Détails
OID1.3.6.1.4.1.9.9.359.1.1.5
Module CISCO-LICENSE-MIB (CISCO)
NomcelPhysicallyProgLicenseTable
Statuscurrent
DescriptionThis 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.