ENTERASYS-TLS-MIB :: etsysTlsGenerateKeys

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ENTERASYS-TLS-MIB › etsysTlsGenerateKeys

etsysTlsGenerateKeys

Module: ENTERASYS-TLS-MIB

OID (symbolic): ENTERASYS-TLS-MIB::etsysTlsGenerateKeys

OID (numeric): 1.3.6.1.4.1.5624.1.2.30.1.3.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Causes the host to generate a new key pair using the cipher algorithm currently selected in etsysTlsAdminKeyType. Note that this can be compute intensive on many platforms.

The meaning of the values are as follows:

notInitiated (1) On a write, this is a no-operation, on a read, it indicates that no key material generation operation has ever been initiated, at least since the last reset to factory defaults initialization of the managed entity. No key material exists.

completed (2) On a write, this is a no-operation, on a read, this indicates that a key pair has been successfully generated.

failed (3) On a write, this is a no-operation, on a read, it indicates that the key generation operation has failed.

generate (4) On a write, this causes the managed entity to generate a new key pair, on a read, it indicates that the managed entity is still working on creating the new keys.

completedPending (5) On a write, this is a no-operation, on a read, this indicates that a key pair has been successfully generated but its use is pending due to another required operation, such as a reboot.

What is etsysTlsGenerateKeys?

This object both triggers and reports the state of TLS key-pair generation on the device, using the cipher algorithm currently set in etsysTlsAdminKeyType. An admin writes generate(4) to this object to start creating a new key pair, which can be CPU-intensive, then reads the object back to check whether it shows completed(2), failed(3), or is still generate(4) in progress, with completedPending(5) meaning a reboot is needed before the new key takes effect. For example, an admin who changes etsysTlsAdminKeyType to rsa2048 would then write generate(4) here to produce the new RSA-2048 key pair.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5624.1.2.30.1.3.1
snmpwalk -v2c -c public <target> ENTERASYS-TLS-MIB::etsysTlsGenerateKeys

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.5624.1.2.30.1.3.1.1
snmpget -v2c -c public <target> ENTERASYS-TLS-MIB::etsysTlsGenerateKeys.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.5624.1.2.30.1.3.1.1 i <value>

Start monitoring Enterasys (Extreme Networks) Ethernet switches with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ENTERASYS-TLS-MIB::etsysTlsGenerateKeys OID value, configure state conditions and alerts, and monitor any Enterasys (Extreme Networks) Ethernet switches from a single console.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.5624enterasysENTERASYS-MIB-NAMES
1.3.6.1.4.1.5624.1etsysMibsENTERASYS-MIB-NAMES
1.3.6.1.4.1.5624.1.2etsysModulesENTERASYS-MIB-NAMES
Numeric OIDNameModule
1.3.6.1.4.1.5624.1.2.30etsysTlsMIBENTERASYS-TLS-MIB
1.3.6.1.4.1.5624.1.2.30.1etsysTlsObjectsENTERASYS-TLS-MIB
1.3.6.1.4.1.5624.1.2.30.1.3etsysTlsServerKeyBranchENTERASYS-TLS-MIB
1.3.6.1.4.1.5624.1.2.30.1.3.1etsysTlsGenerateKeysENTERASYS-TLS-MIB