All MIBs › ENTERASYS-SSH-SERVER-MIB › etsysSshGenerateHostKeys
etsysSshGenerateHostKeys
Module: ENTERASYS-SSH-SERVER-MIB
OID (symbolic): ENTERASYS-SSH-SERVER-MIB::etsysSshGenerateHostKeys
OID (numeric): 1.3.6.1.4.1.5624.1.2.26.1.5.1
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: Causes the host to generate a new private/public host key pair, using the cipher algorithm currently selected in etsysSshAdminKeyType. 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 etsysSshGenerateHostKeys?
This deprecated, read-write INTEGER both triggers and reports the state of SSH host key pair generation: writing generate(4) causes the device to create a new key pair using the algorithm in etsysSshAdminKeyType, while reading returns notInitiated(1), completed(2), failed(3), generate(4, still working), or completedPending(5, generated but pending a required operation like a reboot). Admins write generate(4) after changing etsysSshAdminKeyType to actually produce the new key material, then poll this object until it reports completed or completedPending. For example, after setting etsysSshAdminKeyType to rsa2048 and writing generate(4), an admin would poll this object and see it move from generate(4) to completed(2) once the new RSA-2048 host key is ready.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5624.1.2.26.1.5.1 snmpwalk -v2c -c public <target> ENTERASYS-SSH-SERVER-MIB::etsysSshGenerateHostKeys
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.5624.1.2.26.1.5.1.1 snmpget -v2c -c public <target> ENTERASYS-SSH-SERVER-MIB::etsysSshGenerateHostKeys.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.5624.1.2.26.1.5.1.1 i <value>
Start monitoring Enterasys/Extreme Networks wireless switch/controller (embedded SSH server, session limits) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ENTERASYS-SSH-SERVER-MIB::etsysSshGenerateHostKeys OID value, configure state conditions and alerts, and monitor any Enterasys/Extreme Networks wireless switch/controller (embedded SSH server, session limits) from a single console.
OID Breakdown
Upper-level ancestors (9 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.5624 | enterasys | ENTERASYS-MIB-NAMES |
| 1.3.6.1.4.1.5624.1 | etsysMibs | ENTERASYS-MIB-NAMES |
| 1.3.6.1.4.1.5624.1.2 | etsysModules | ENTERASYS-MIB-NAMES |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.5624.1.2.26 | etsysSshServerMIB | ENTERASYS-SSH-SERVER-MIB |
| 1.3.6.1.4.1.5624.1.2.26.1 | etsysSshObjects | ENTERASYS-SSH-SERVER-MIB |
| 1.3.6.1.4.1.5624.1.2.26.1.5 | etsysSshServerKeyBranch | ENTERASYS-SSH-SERVER-MIB |
| 1.3.6.1.4.1.5624.1.2.26.1.5.1 | etsysSshGenerateHostKeys | ENTERASYS-SSH-SERVER-MIB |