HM2-LOGGING-MIB :: hm2LogEmailNumEmailsSent

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsHM2-LOGGING-MIBhm2LogEmailNumEmailsSent

hm2LogEmailNumEmailsSent

Module: HM2-LOGGING-MIB

OID (symbolic): HM2-LOGGING-MIB::hm2LogEmailNumEmailsSent

OID (numeric): 1.3.6.1.4.1.248.11.23.1.10.6

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Number of email alerts that have been sent successfully.

What is hm2LogEmailNumEmailsSent?

A running count of email alerts the device has successfully sent, which an admin can watch to confirm the email-alert feature is actually delivering mail.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.248.11.23.1.10.6
snmpwalk -v2c -c public <target> HM2-LOGGING-MIB::hm2LogEmailNumEmailsSent

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.248.11.23.1.10.6.1
snmpget -v2c -c public <target> HM2-LOGGING-MIB::hm2LogEmailNumEmailsSent.1

Start monitoring Hirschmann HiOS industrial switch (logging/syslog config) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HM2-LOGGING-MIB::hm2LogEmailNumEmailsSent OID value, configure state conditions and alerts, and monitor any Hirschmann HiOS industrial switch (logging/syslog config) from a single console.

How to Use in IPNetwork Monitor

Select a Hirschmann HiOS industrial switch (logging/syslog config) 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 hm2LogEmailNumEmailsSent into the Find box to locate it in the OID tree, then select it and click OK. It reports the number of email alerts that have been sent successfully. 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.248hirschmannHM2-TC-MIB
1.3.6.1.4.1.248.11hm2ConfigurationMibsHM2-TC-MIB
Numeric OIDNameModule
1.3.6.1.4.1.248.11.23hm2LoggingMibHM2-LOGGING-MIB
1.3.6.1.4.1.248.11.23.1hm2LoggingMibObjectsHM2-LOGGING-MIB
1.3.6.1.4.1.248.11.23.1.10hm2LogEmailAlertGroupHM2-LOGGING-MIB
1.3.6.1.4.1.248.11.23.1.10.6hm2LogEmailNumEmailsSentHM2-LOGGING-MIB