ZHNLANDEVICE :: bytesSent

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › ZHNLANDEVICE › bytesSent

bytesSent

Module: ZHNLANDEVICE

OID (symbolic): ZHNLANDEVICE::bytesSent

OID (numeric): 1.3.6.1.4.1.5504.2.5.41.1.4.2.1.1

Node type: OBJECT-TYPE

Type: Gauge32

Access: read-only

Description: Total number of bytes sent over the interface since the CPE was last reset.

What is bytesSent?

Total bytes transmitted over this Ethernet interface since the CPE was last reset, a basic throughput counter for capacity or usage monitoring.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5504.2.5.41.1.4.2.1.1
snmpwalk -v2c -c public <target> ZHNLANDEVICE::bytesSent

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.5504.2.5.41.1.4.2.1.1.1
snmpget -v2c -c public <target> ZHNLANDEVICE::bytesSent.1

Start monitoring Zhone Technologies broadband gateways/routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ZHNLANDEVICE::bytesSent OID value, configure state conditions and alerts, and monitor any Zhone Technologies broadband gateways/routers from a single console.

How to Use in IPNetwork Monitor

Select a Zhone Technologies broadband gateway/router 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 bytesSent into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports the total number of bytes sent over the interface since the CPE was last reset. 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 Gauge32-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 (9 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.5504ZhoneBITSTORM-HP-160-MIB
1.3.6.1.4.1.5504.2zhoneProductZhone
1.3.6.1.4.1.5504.2.5zhoneWtnZhone
Numeric OIDNameModule
1.3.6.1.4.1.5504.2.5.41zhnLANDeviceZHNLANDEVICE
1.3.6.1.4.1.5504.2.5.41.1zhnLANDeviceObjectsZHNLANDEVICE
1.3.6.1.4.1.5504.2.5.41.1.4zhnLANEthernetInterfaceObjectsZHNLANDEVICE
1.3.6.1.4.1.5504.2.5.41.1.4.2lanEthIntfStatisticsTableZHNLANDEVICE
1.3.6.1.4.1.5504.2.5.41.1.4.2.1lanEthIntfStatisticsEntryZHNLANDEVICE
1.3.6.1.4.1.5504.2.5.41.1.4.2.1.1bytesSentZHNLANDEVICE