WLSX-TUNNELEDNODE-MIB :: wlsxNumTunnels

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › WLSX-TUNNELEDNODE-MIB › wlsxNumTunnels

wlsxNumTunnels

Module: WLSX-TUNNELEDNODE-MIB

OID (symbolic): WLSX-TUNNELEDNODE-MIB::wlsxNumTunnels

OID (numeric): 1.3.6.1.4.1.14823.2.2.1.17.1.1.1.3

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: Number of tunnels originating from Tunneled Node

What is wlsxNumTunnels?

This object reports how many active tunnels are currently established that originate from a particular tunneled node. An admin uses this to spot nodes generating an unusually high number of tunnels, which could indicate legitimate multi-session use or a misbehaving or misconfigured client. For example, a tunneled node showing 15 active tunnels when a typical client only opens one or two would warrant investigation.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.14823.2.2.1.17.1.1.1.3
snmpwalk -v2c -c public <target> WLSX-TUNNELEDNODE-MIB::wlsxNumTunnels

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.14823.2.2.1.17.1.1.1.3.1
snmpget -v2c -c public <target> WLSX-TUNNELEDNODE-MIB::wlsxNumTunnels.1

Start monitoring Aruba Networks wireless mobility controllers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the WLSX-TUNNELEDNODE-MIB::wlsxNumTunnels OID value, configure state conditions and alerts, and monitor any Aruba Networks wireless mobility controllers from a single console.

How to Use in IPNetwork Monitor

Select an Aruba Networks wireless mobility controller 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 wlsxNumTunnels 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 tunnels originating from Tunneled Node. 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 an Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if the count changes from its expected baseline, since that would indicate the underlying set of items changed unexpectedly. 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.14823arubaAP80-PRIVATE-MIB
1.3.6.1.4.1.14823.2arubaEnterpriseMibModulesAP80-PRIVATE-MIB
1.3.6.1.4.1.14823.2.2switchARUBA-MIB
1.3.6.1.4.1.14823.2.2.1wlsxEnterpriseMibModulesARUBA-MIB
Numeric OIDNameModule
1.3.6.1.4.1.14823.2.2.1.17wlsxTunneledNodeMIBWLSX-TUNNELEDNODE-MIB
1.3.6.1.4.1.14823.2.2.1.17.1wlsxTunneledNodeOpGroupWLSX-TUNNELEDNODE-MIB
1.3.6.1.4.1.14823.2.2.1.17.1.1wlsxTunneledNodeRequestTableWLSX-TUNNELEDNODE-MIB
1.3.6.1.4.1.14823.2.2.1.17.1.1.1wlsxTunneledNodeRequestEntryWLSX-TUNNELEDNODE-MIB
1.3.6.1.4.1.14823.2.2.1.17.1.1.1.3wlsxNumTunnelsWLSX-TUNNELEDNODE-MIB