ENTERASYS-ACTIVATION-MIB
AI MIB Summary
The ENTERASYS-ACTIVATION-MIB enables SNMP-based management of product activation keys on Enterasys Networks hardware, specifically monitoring the status and configuration of license entitlements required to enable or restrict device features.
This MIB module defines a portion of the SNMP enterprise MIBs under Enterasys Networks' enterprise OID pertaining to configuration of product activation keys.
Main OID:
etsysActivationMIB.1.3.6.1.4.1.5624.1.2.99999
20
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
20 total| Object Name |
|---|
etsysActivationMIBThis MIB module defines a portion of the SNMP enterprise MIBs under Enterasys Networks' enterprise OID pertaining to configuration of product activation keys. MODULE-IDENTITY .1.3.6.1.4.1.5624.1.2.99999 |
etsysActivationObjects OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.99999.1 |
etsysActivationBaseBranch OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.99999.1.1 |
etsysMaxActivationKeyRowThe largest value that the agent supports for the index object etsysActivationKeyRow.ro Integer32( 1..2147483647 ) .1.3.6.1.4.1.5624.1.2.99999.1.1.1 |
etsysActivationKeyTableThis table contains activation keys for optional features. SEQUENCE OF EtsysActivationKeyEntry .1.3.6.1.4.1.5624.1.2.99999.1.1.2 |
etsysActivationKeyEntryEach valid conceptual row contains basic information about one product activation key. Only those rows for which the etsysActivationKeyStatus is active(1) may enable features. Note that it is possible for an active(1) row to contain a well-formatted, internally-consistent key that has expired. A managed system is under no obligation to enable features in response to the presence of expired keys. EtsysActivationKeyEntry .1.3.6.1.4.1.5624.1.2.99999.1.1.2.1 |
etsysActivationKeyRowAn index that uniquely identifies a row in the product key table. Agents are not required to accept arbitrary indices -- they may limit indices to numbers in the range (1 - N), where N is defined as the maximum number of activation keys that can usefully be supported on a product. Integer32( 1..2147483647 ) .1.3.6.1.4.1.5624.1.2.99999.1.1.2.1.1 |
etsysActivationLicenseStringA place for human-readable administrative information associated with this activation key, such as a product serial number or a demo key's registration date. Some key formats may require entry of 'License String' values provided by the vendor. Agents may enforce the following rule with respect to such paired-key rows: ------------------------------------------------------- This object MUST be set before etsysActivationKeyStatus can become active(1), and MAY NOT be modified while etsysActivationKeyStatus is active(1). -------------------------------------------------------rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.5624.1.2.99999.1.1.2.1.2 |
etsysActivationKeyValueAn activation key. The activation key must be coded as a string of printable characters. Spaces and hyphens are reserved punctuation characters. They may be used freely on input and output, and do not form part of the key value. (The agent is not required to preserve these or other non-essential aspects of the key formatting.) The key must conform to one of the meta-formats defined in this DESCRIPTION. These meta-formats are subject to change. Agents should validate activation keys at Set time. An agent may reject even a valid key if it is inapplicable to the managed device. This object MUST be set before etsysActivationKeyStatus can become active(1), and MAY NOT be modified while etsysActivationKeyStatus is active(1). ======================================================= Standard activation keys have the following format: <FormatCode> <OpaqueKey> The <FormatCode> is encoded as four hexadecimal digits, and identifies the format of the <OpaqueKey>. The <OpaqueKey> may be encoded in any fashion the agent likes, within the constraints mentioned earlier in this DESCRIPTION. ======================================================= A platform may accept keys of the format <Keyword> [Qualifiers] provided that there is no possibility of confusion with standard activation keys. This format is best suited to non-secret demo keys that are intended for a wide audience ('everyone reading the user manual'). ======================================================= Backwards compatibility example Task : Configure an existing RoamAbout AccessPoint 2000 P-MP activation key, using this MIB. <OpaqueKey> : XXXX-XXXX-XXXX-XXXX (existing key) <FormatCode> : 0001 You enter : 0001-XXXX-XXXX-XXXX-XXXX =======================================================rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.5624.1.2.99999.1.1.2.1.3 |
etsysActivationKeyTypeDerived from the activation key. Identifies the type of key (product key vs. demonstration key). Identification of existing demonstration keys may not be 100% accurate.ro EnterasysKeyType .1.3.6.1.4.1.5624.1.2.99999.1.1.2.1.4 |
etsysActivationKeyStatusSupports creation, deletion, and activation of rows in the etsysActivationKeyTable. An instance of this variable may become active(1) only when there is a corresponding etsysActivationKeyValue. For some key formats, the etsysActivationLicenseString may need to be set to a matching vendor-supplied value. Note that a row with an active(1) status may contain a demo key that has expired, and that no longer provides access to any features.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.5624.1.2.99999.1.1.2.1.5 |
etsysActivationKeyFeatureTableThis table indicates which optional feature or features each activation key enables. Rows only appear in this table for 'etsysActivationKeyValue' instances that contain recognizable key values. SEQUENCE OF EtsysActivationKeyFeatureEntry .1.3.6.1.4.1.5624.1.2.99999.1.1.3 |
etsysActivationKeyFeatureEntryEach valid conceptual row indicates the existence of a known mapping between an activation key and an optional feature. EtsysActivationKeyFeatureEntry .1.3.6.1.4.1.5624.1.2.99999.1.1.3.1 |
etsysActivationKeyFeatureIdentifies one of the optional product features enabled by an activation key in the etsysActivationKeyTable. EnterasysFeature .1.3.6.1.4.1.5624.1.2.99999.1.1.3.1.1 |
etsysActivationKeyRestrictionsIf the activation key associated with this row is a demo key, this MIB object may contain a human-readable string describing the key's restrictions, expiration conditions, and/or status. A demo key that enables several features could, at least theoretically, have different conditions for each. Platforms may automatically enforce expirations, but are not guaranteed to do so. It is ultimately the system manager's responsibility to clean up expired keys. For a key that has no restrictions, this object's value may consist of the empty string, or of whitespace.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.5624.1.2.99999.1.1.3.1.2 |
etsysActivationConformance OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.99999.2 |
etsysActivationGroups OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.99999.2.1 |
etsysActivationBaseGroupA collection of objects for configuring activation keys for optional platform features. Unknown .1.3.6.1.4.1.5624.1.2.99999.2.1.1 |
etsysActivationCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.99999.2.2 |
etsysActivationComplianceThe compliance statement for devices that support the Enterasys Product Activation MIB. Unknown .1.3.6.1.4.1.5624.1.2.99999.2.2.1 |