etsysActivationKeyValue 1.3.6.1.4.1.5624.1.2.99999.1.1.2.1.3

An 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 =======================================================