RUCKUS-WLINK-MIB :: ruckusWLINKTxPkts

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › RUCKUS-WLINK-MIB › ruckusWLINKTxPkts

ruckusWLINKTxPkts

Module: RUCKUS-WLINK-MIB

OID (symbolic): RUCKUS-WLINK-MIB::ruckusWLINKTxPkts

OID (numeric): 1.3.6.1.4.1.25053.1.1.15.1.1.1.1.1.5

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Number of tx packets.

What is ruckusWLINKTxPkts?

This read-only counter tracks the total number of packets transmitted over this wireless bridge link. Admins monitor it to confirm the link is actively passing traffic and to gauge relative traffic load compared to other links in a mesh deployment. A ruckusWLINKTxPkts counter that stops incrementing would tell the admin this link has stopped transmitting traffic, even if it still shows as up.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.25053.1.1.15.1.1.1.1.1.5
snmpwalk -v2c -c public <target> RUCKUS-WLINK-MIB::ruckusWLINKTxPkts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.25053.1.1.15.1.1.1.1.1.5.1
snmpget -v2c -c public <target> RUCKUS-WLINK-MIB::ruckusWLINKTxPkts.1

Start monitoring Ruckus Wireless bridge/mesh access points (wireless backhaul link configuration/performance) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RUCKUS-WLINK-MIB::ruckusWLINKTxPkts OID value, configure state conditions and alerts, and monitor any Ruckus Wireless bridge/mesh access points (wireless backhaul link configuration/performance) from a single console.

How to Use in IPNetwork Monitor

Select a Ruckus Wireless bridge/mesh access point (wireless backhaul link configuration/performance) 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 ruckusWLINKTxPkts 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 number of tx packets. 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 (10 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.25053ruckusRootMIBRUCKUS-ROOT-MIB
1.3.6.1.4.1.25053.1ruckusObjectsRUCKUS-ROOT-MIB
1.3.6.1.4.1.25053.1.1ruckusCommonRUCKUS-ROOT-MIB
1.3.6.1.4.1.25053.1.1.15ruckusCommonWLINKModuleRUCKUS-ROOT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.25053.1.1.15.1ruckusWLINKMIBRUCKUS-WLINK-MIB
1.3.6.1.4.1.25053.1.1.15.1.1ruckusWLINKObjectsRUCKUS-WLINK-MIB
1.3.6.1.4.1.25053.1.1.15.1.1.1ruckusWLINKInfoRUCKUS-WLINK-MIB
1.3.6.1.4.1.25053.1.1.15.1.1.1.1ruckusWLINKTableRUCKUS-WLINK-MIB
1.3.6.1.4.1.25053.1.1.15.1.1.1.1.1ruckusWLINKEntryRUCKUS-WLINK-MIB
1.3.6.1.4.1.25053.1.1.15.1.1.1.1.1.5ruckusWLINKTxPktsRUCKUS-WLINK-MIB