Home/Catalog/XEDIA-SSHD-MIB

XEDIA-SSHD-MIB

AI MIB Summary

The XEDIA-SSHD-MIB enables monitoring and configuration of the Secure Shell (SSH) daemon on Xedia Access Point devices, specifically tracking SSH session states, connection statistics, and daemon operational parameters.

This module defines Secure Shell Daemon configuration and statistics for Xedia AP devices.
Main OID:
xediaSshDMIB.1.3.6.1.4.1.838.3.35
65
Objects
Active
Status
4
Dependencies

Imported Objects

Objects

65 total
Object Name
xediaSshDMIBThis module defines Secure Shell Daemon configuration and statistics for Xedia AP devices.
MODULE-IDENTITY
.1.3.6.1.4.1.838.3.35
xSshDObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.35.1
xSshDGlobal
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.35.1.1
xSshDGlobalCfg
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.35.1.1.1
xsshdCfgAdminStatusThe administrative status of Secure Shell in the router. The value of: 'enabled' - indicates that the ssh daemon will process requests from clients. If there are enough node resources, and the host/user pass authentication, then the user will be allowed to log into the CL.I 'disable' - indicates that the ssh daemon will not process requests from clients. Existing sessions will not be torn down. 'testing' - will process requests from clients, and periodically output a test pattern if the client is authenticated. 'disabledDown' - indicates that the ssh daemon will not process requests from clients, and, at system initialization, the ssh daemon will NOT be started. This can be used to free up node resources if ssh is not going to be used. Existing sessions will not be torn down. The ssh daemon can only be started at intialization time. So, if it was set to 'disabledDown' and the daemon never started, a full node boot will be required to enable the ssh daemon.rw
Enumeration
.1.3.6.1.4.1.838.3.35.1.1.1.1
xsshdCfgListenPortThe tcp port number that will be used to listen for requests. Changing this parameter will require a node boot to take affect.rw
INTEGER
.1.3.6.1.4.1.838.3.35.1.1.1.2
xsshdCfgKeyNameThe name of the PKI key-pair that is configured in the box for use by SSH. It SHOULD be a DSA formatted key. If this index is left blank, the first available key will be used.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.1.1.3
xsshdCfgMaxSessionsThe maximum number of SSH sessions allowed at one time.rw
INTEGER
.1.3.6.1.4.1.838.3.35.1.1.1.4
xsshdCfgSessionEventsThe overall control of session event generation that is used in conjuction with the normal system event filters. If the session flag is 'disabled' no session events will be sent. If the flag is 'enabled' the normal event filter mechanisms will still be used to customize input/output of the events.rw
Enumeration
.1.3.6.1.4.1.838.3.35.1.1.1.5
xsshdCfgUserAuthControlThe method of authentication for users. If 'password' is used, then the user will be looked up and authenticated using the general 'authentication user table'. If 'publicKey' is used, then the client/user public key will be looked up in the SSH Client-Key table.rw
Enumeration
.1.3.6.1.4.1.838.3.35.1.1.1.6
xsshdCfgHostAuthControlThe method of authentication for client machines. If 'list' is used, then the client address is validated against the accept/deny list of clients.rw
Enumeration
.1.3.6.1.4.1.838.3.35.1.1.1.7
xsshdCfgEncryptionControlThis object controls the ciphers that are allowed to be used during negotiation with a client.rw
BIT STRING { none(0), des(1), des3(2) }
.1.3.6.1.4.1.838.3.35.1.1.1.8
xsshdCfgMacControlThis object controls the hmac algorithms are allowed to be used during negotiation with a client.rw
BIT STRING { none(0), sha(1), sha96(2), md5(3), md596(4) }
.1.3.6.1.4.1.838.3.35.1.1.1.9
xsshdCfgCompressionControlThe methods of compression that can be negotiated.rw
BIT STRING { none(0), zlib(1) }
.1.3.6.1.4.1.838.3.35.1.1.1.10
xsshdCfgPasswordRetryThe number of times a user can re-enter a password before the user is considered to be invalid.rw
INTEGER
.1.3.6.1.4.1.838.3.35.1.1.1.11
xsshdCfgAuthGraceTimeThe total number of seconds allowd for host/user authentication. In most cases only a few seconds is needed. But, in the case of user/password authentication, the user may 'stall' the session by not supplying a password in a timely manner. This object roughly defines the number of seconds to wait for the entire authentication process to complete. It is NOT an exact number of seconds. The authentication status is checked as a background task (specific timer interval) for each session thread. Therefore, it MAY take a few seconds beyond the configured value for the connection to be terminated.rw
INTEGER
.1.3.6.1.4.1.838.3.35.1.1.1.12
xsshdCfgIdleTimeOutThe number of minutes without any user input, that is allowed, before disconnecting a session. Setting this value to zero disables the idle-timeout feature.rw
INTEGER
.1.3.6.1.4.1.838.3.35.1.1.1.13
xsshdCfgHostAcceptListThe list of clients that are allowed to connect to the server. This list is only used if the host control is set. The list can be made up of individual addresses separated or address ranges, with each component being separated by a comma. ie '1.2.3.4, 1.2.5.0-1.2.5.30'rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.1.1.14
xsshdCfgHostDenyListThe list of clients that are not allowed to connect to the server. This list is only used if the host control is set. The list can be made up of individual addresses separated or address ranges, with each component being separated by a comma. ie '1.2.3.4, 1.2.5.0-1.2.5.30'rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.1.1.15
xsshdCfgDbgTraceLevelThe numeric value that is used to apply 'trace-levels' of the debug events. It's intended to be used by Xedia Support only when normal events and statistics are not able to provide enough information to properly debug problems in the field.rw
Integer32
.1.3.6.1.4.1.838.3.35.1.1.1.16
xsshdCfgPresentedKeyTypesThis object controls which ssh key types will be presented to the client during negotiation. Since 'dsa' support is mandatiory, and 'rsa' support is optional, the administrator will have some control over what is presented to the clients. If 'dsa' is chosen, only 'ssh-dss' will be presented to the client for negotiation. If 'dsaAndRsa' is selected, both formats will be presented to the client 'ssh-rsa,ssh-dss'. But, when 'dsaAllowRsa' is used, ssh-rsa will only be presented to the client when the ssh daemon is using an rsa formatted key.rw
Enumeration
.1.3.6.1.4.1.838.3.35.1.1.1.17
xSshDGlobalOper
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.35.1.1.2
xsshdOperStatusThe operational status of Secure Shell in the router.ro
Enumeration
.1.3.6.1.4.1.838.3.35.1.1.2.1
xsshdOperCipherListThe list of Ciphers configured.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.1.2.2
xsshdOperCiphersThe list of Ciphers that can be negotiated base on what functions are available with the current version of software.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.1.2.3
xsshdOperMacListThe list of MAC algorithms configured.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.1.2.4
xsshdOperMacsThe list of MAC algorithms that can be negotiated based on what functions are available with the current version of software.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.1.2.5
xsshdOperCompressionListThe list of Compression algorithms configured.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.1.2.6
xsshdOperCompressionsThe list of Compression algorithms that can be negotiated based on what functions are available with the current version of software.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.1.2.7
xsshdOperHostAcceptListThe operational list of clients that are allowed to connect to the server.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.1.2.8
xsshdOperHostDenyListThe operational list of clients that are not allowed to connect to the server.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.1.2.9
xsshdOperPresentedKeyTypesThe operational list of key types presented to the client for negotiation.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.1.2.10
xSshDGlobalStats
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.35.1.1.3
xsshdStatsCurrentSessionCountThe number of current SSH sessions in progress.ro
Integer32
.1.3.6.1.4.1.838.3.35.1.1.3.1
xsshdStatsTotalSessionCountThe total number of SSH session requests.ro
Counter32
.1.3.6.1.4.1.838.3.35.1.1.3.2
xsshdStatsSessionSuccessCountThe total number of SSH sessions that were able to to obtain all necessary resources, and authenticate the user and host. (basically, allowed to initiate a CLI session)ro
Counter32
.1.3.6.1.4.1.838.3.35.1.1.3.3
xsshdStatsSessionAuthFailsThe number of session authentication failures.ro
Counter32
.1.3.6.1.4.1.838.3.35.1.1.3.4
xsshdStatsSessionResourceFailsThe number of session resource failures. This statistic is incremented for memory and system resource failures as well as when the maximum number of SSH sessions prohibits a session from being established.ro
Counter32
.1.3.6.1.4.1.838.3.35.1.1.3.5
xSshDSession
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.35.1.2
xSshDSessionOper
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.35.1.2.1
xsshdSessionTableA list of active SSH sessions entries
SEQUENCE OF XsshdSessionEntry
.1.3.6.1.4.1.838.3.35.1.2.1.1
xsshdSessionEntryAn entry containing information about an SSH session
XsshdSessionEntry
.1.3.6.1.4.1.838.3.35.1.2.1.1.1
xsshdSessionIndexThe index of the session.
INTEGER
.1.3.6.1.4.1.838.3.35.1.2.1.1.1.1
xsshdSessionRemoteIpAddressThe ip address of the connected client.ro
IpAddress
.1.3.6.1.4.1.838.3.35.1.2.1.1.1.2
xsshdSessionRemoteNodeThe node identifier of the connected client.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.2.1.1.1.3
xsshdSessionRemoteUserThe remote user of the session.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.2.1.1.1.4
xsshdSessionNegotiationThe negotiated results of the session.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.2.1.1.1.5
xsshdSessionTimeThe number of 1/100 seconds that the session has been connected.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.838.3.35.1.2.1.1.1.6
xsshdSessionUiBytesInThe number of data bytes passed to the internal user interface up from the Secure Shell layer.ro
Counter32
.1.3.6.1.4.1.838.3.35.1.2.1.1.1.7
xsshdSessionUiBytesOutThe number of data bytes passed from the internal user interface down to the Secure Shell layer.ro
Counter32
.1.3.6.1.4.1.838.3.35.1.2.1.1.1.8
xsshdSessionRowStatusThe status of the entry. The only operations that are allowed are 'active' and 'destroy'. Existing sessions can be set to 'active' which causes no change. And, existing sessions can be set to 'destroy' to abort the particular session.rw
Enumeration
.1.3.6.1.4.1.838.3.35.1.2.1.1.1.9
xSshDClientKeys
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.35.1.3
xSshDClientKeyStats
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.35.1.3.1
xsshdClientKeyCountTotalThe number of configured SSH Client keys.ro
Integer32
.1.3.6.1.4.1.838.3.35.1.3.1.1
xsshdClientKeyCountActiveThe number of active SSH Client keys.ro
Integer32
.1.3.6.1.4.1.838.3.35.1.3.1.2
xSshDClientKeyTable
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.35.1.3.2
xsshdClientKeyTableA list of active SSH sessions entries
SEQUENCE OF XsshdClientKeyEntry
.1.3.6.1.4.1.838.3.35.1.3.2.1
xsshdClientKeyEntryAn entry containing information about an SSH session
XsshdClientKeyEntry
.1.3.6.1.4.1.838.3.35.1.3.2.1.1
xsshdClientKeyIpAddressThe ip address of the client associated with the key entry.
IpAddress
.1.3.6.1.4.1.838.3.35.1.3.2.1.1.1
xsshdClientKeyUserThe name of the user associated with the key entry.
DisplayString
.1.3.6.1.4.1.838.3.35.1.3.2.1.1.2
xsshdClientKeyDataThe key data for the associated host/user.rw
LongDisplayString
.1.3.6.1.4.1.838.3.35.1.3.2.1.1.3
xsshdClientKeyRowStatusThe status of the entry.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.838.3.35.1.3.2.1.1.4
xSshDConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.35.2
xsshdCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.35.2.1
xsshdGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.838.3.35.2.2
XEDIA-SSHD-MIB - SNMP MIB Reference | MIBs Explorer