XEDIA-SSHD-MIB :: xsshdStatsTotalSessionCount

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › XEDIA-SSHD-MIB › xsshdStatsTotalSessionCount

xsshdStatsTotalSessionCount

Module: XEDIA-SSHD-MIB

OID (symbolic): XEDIA-SSHD-MIB::xsshdStatsTotalSessionCount

OID (numeric): 1.3.6.1.4.1.838.3.35.1.1.3.2

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The total number of SSH session requests.

What is xsshdStatsTotalSessionCount?

Running total of all SSH session requests the daemon has received, successful or not, since it started.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.838.3.35.1.1.3.2
snmpwalk -v2c -c public <target> XEDIA-SSHD-MIB::xsshdStatsTotalSessionCount

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.838.3.35.1.1.3.2.1
snmpget -v2c -c public <target> XEDIA-SSHD-MIB::xsshdStatsTotalSessionCount.1

Start monitoring Xedia AP access point, Xedia router (SSHD session-count/failed-login-event status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the XEDIA-SSHD-MIB::xsshdStatsTotalSessionCount OID value, configure state conditions and alerts, and monitor any Xedia AP access point, Xedia router (SSHD session-count/failed-login-event status) from a single console.

How to Use in IPNetwork Monitor

Select a Xedia AP access point, Xedia router (SSHD session-count/failed-login-event status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type xsshdStatsTotalSessionCount into the Find box to locate it in the OID tree, then select it and click OK. The total number of SSH session requests. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (8 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.838xediaXEDIA-REG
1.3.6.1.4.1.838.3xediaMibsXEDIA-REG
Numeric OIDNameModule
1.3.6.1.4.1.838.3.35xediaSshDMIBXEDIA-SSHD-MIB
1.3.6.1.4.1.838.3.35.1xSshDObjectsXEDIA-SSHD-MIB
1.3.6.1.4.1.838.3.35.1.1xSshDGlobalXEDIA-SSHD-MIB
1.3.6.1.4.1.838.3.35.1.1.3xSshDGlobalStatsXEDIA-SSHD-MIB
1.3.6.1.4.1.838.3.35.1.1.3.2xsshdStatsTotalSessionCountXEDIA-SSHD-MIB