CME-MIB :: mmSshClientAuthPubKeyEntryStatus

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCME-MIBmmSshClientAuthPubKeyEntryStatus

mmSshClientAuthPubKeyEntryStatus

Module: CME-MIB

OID (symbolic): CME-MIB::mmSshClientAuthPubKeyEntryStatus

OID (numeric): 1.3.6.1.4.1.2.3.51.2.4.1.6.1.1.9

Node type: OBJECT-TYPE

Type: EntryStatus

Access: read-write

Description: This object manages the creation and deletion of this entry. The steps recommended to install and to activate a new client authorization public key are: 1. Set values for mmSshClientAuthPubKeyTftpServer, mmSshClientAuthPubKeyFileName, mmSshClientAuthPubKeyFileFormat 2. Create a new entry in this table mmSshClientAuthPubKeyEntryStatus = createRequest 3. Import a new key mmSshClientAuthPubKeyAction = import This entry will be valid after mmSshClientAuthPubKeyAction is successfully imported. 4. Set mmSshClientAuthPubKeyAcceptFrom and mmSshClientAuthPubKeyComment as required.

valid(1) - Indicates that the public key pair represented by this entry is available for use by the Secure Shell Server for client authentication.

createRequest(2) - A new entry will be created in this table for the specified host key pair and the new entry will transition to the underCreation(3) state. The operation is only accepted if the associated RemoteAccessIdsEntry row defining a local user account is configured.

underCreation(3) - Indicates that this entry exists in the agent but is unavailable for use. After completing the create operation, the agent will set this object to underCreation(3).

invalid(4) - Deletes this entry and any client authentication public key that may be associated with it. Note: only one row may be created at one time.

What is mmSshClientAuthPubKeyEntryStatus?

This read-write EntryStatus object manages creation and deletion of an SSH client public key table row, following a multi-step process of setting TFTP server, filename, and format, creating the row, and then triggering the import action. An admin follows this exact sequence to provision a new SSH key for passwordless login by a user. For example, after setting the TFTP details and creating the row, an admin sets mmSshClientAuthPubKeyAction to import to complete activating the new key entry.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.4.1.6.1.1.9
snmpwalk -v2c -c public <target> CME-MIB::mmSshClientAuthPubKeyEntryStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.4.1.6.1.1.9.1
snmpget -v2c -c public <target> CME-MIB::mmSshClientAuthPubKeyEntryStatus.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.2.3.51.2.4.1.6.1.1.9.1 s <value>

Start monitoring Cisco Communications Manager Express (CME) router/gateway with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CME-MIB::mmSshClientAuthPubKeyEntryStatus OID value, configure state conditions and alerts, and monitor any Cisco Communications Manager Express (CME) router/gateway from a single console.

OID Breakdown

Upper-level ancestors (12 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.2ibmBLADE-MIB
1.3.6.1.4.1.2.3ibmAgentsBLADE-MIB
1.3.6.1.4.1.2.3.51netfinitySupportProcessorAgentBLADE-MIB
1.3.6.1.4.1.2.3.51.2bladeCenterSnmpMIBBLADE-MIB
1.3.6.1.4.1.2.3.51.2.4configureSPBLADE-MIB
1.3.6.1.4.1.2.3.51.2.4.1remoteAccessConfigBLADE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2.3.51.2.4.1.6mmSshClientAuthCME-MIB
1.3.6.1.4.1.2.3.51.2.4.1.6.1mmSshClientAuthPubKeyTableCME-MIB
1.3.6.1.4.1.2.3.51.2.4.1.6.1.1mmSshClientAuthPubKeyEntryCME-MIB
1.3.6.1.4.1.2.3.51.2.4.1.6.1.1.9mmSshClientAuthPubKeyEntryStatusCME-MIB