HH3C-DHCP-SNOOP2-MIB :: hh3cDhcpSnoop2PktSentNum

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › HH3C-DHCP-SNOOP2-MIB › hh3cDhcpSnoop2PktSentNum

hh3cDhcpSnoop2PktSentNum

Module: HH3C-DHCP-SNOOP2-MIB

OID (symbolic): HH3C-DHCP-SNOOP2-MIB::hh3cDhcpSnoop2PktSentNum

OID (numeric): 1.3.6.1.4.1.25506.2.124.1.2.1

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: The total number of the packets send by DHCP snooping.

What is hh3cDhcpSnoop2PktSentNum?

Running counter of DHCP packets the snooping process itself has sent (Counter64), useful as a sanity check that snooping is actively relaying/forwarding DHCP traffic rather than sitting idle.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.25506.2.124.1.2.1
snmpwalk -v2c -c public <target> HH3C-DHCP-SNOOP2-MIB::hh3cDhcpSnoop2PktSentNum

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.25506.2.124.1.2.1.1
snmpget -v2c -c public <target> HH3C-DHCP-SNOOP2-MIB::hh3cDhcpSnoop2PktSentNum.1

Start monitoring H3C access-layer switch (DHCP Snooping v2) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HH3C-DHCP-SNOOP2-MIB::hh3cDhcpSnoop2PktSentNum OID value, configure state conditions and alerts, and monitor any H3C access-layer switch (DHCP Snooping v2) from a single console.

How to Use in IPNetwork Monitor

Select an H3C access-layer switch (DHCP Snooping v2) 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 hh3cDhcpSnoop2PktSentNum into the Find box to locate it in the OID tree, then select it and click OK. The total number of the packets send by DHCP snooping. 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 Counter64-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.25506hh3cHH3C-OID-MIB
1.3.6.1.4.1.25506.2hh3cCommonHH3C-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.25506.2.124hh3cDhcpSnoop2HH3C-DHCP-SNOOP2-MIB
1.3.6.1.4.1.25506.2.124.1hh3cDhcpSnoop2ScalarObjectsHH3C-DHCP-SNOOP2-MIB
1.3.6.1.4.1.25506.2.124.1.2hh3cDhcpSnoop2StatisticsGroupHH3C-DHCP-SNOOP2-MIB
1.3.6.1.4.1.25506.2.124.1.2.1hh3cDhcpSnoop2PktSentNumHH3C-DHCP-SNOOP2-MIB