HIPATH-WIRELESS-HWC-MIB :: vnLocalClients

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › HIPATH-WIRELESS-HWC-MIB › vnLocalClients

vnLocalClients

Module: HIPATH-WIRELESS-HWC-MIB

OID (symbolic): HIPATH-WIRELESS-HWC-MIB::vnLocalClients

OID (numeric): 1.3.6.1.4.1.4329.15.3.2.5.4

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Number of locally associated clients to this controller that is considered to be their home controller in the mobility zone, which this controller is part of.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4329.15.3.2.5.4
snmpwalk -v2c -c public <target> HIPATH-WIRELESS-HWC-MIB::vnLocalClients

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4329.15.3.2.5.4.1
snmpget -v2c -c public <target> HIPATH-WIRELESS-HWC-MIB::vnLocalClients.1

Start monitoring Siemens/Enterasys HiPath Wireless Controller (HWC) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HIPATH-WIRELESS-HWC-MIB::vnLocalClients OID value, configure state conditions and alerts, and monitor any Siemens/Enterasys HiPath Wireless Controller (HWC) from a single console.

How to Use in IPNetwork Monitor

Select a Siemens/Enterasys HiPath Wireless Controller (HWC) 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 vnLocalClients into the Find box to locate it in the OID tree, then select it and click OK. It reports the number of locally associated clients to this controller that is considered to be their home controller in the mobility zone, which this controller is part of. 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 (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.4329siemensFSC-RTP-MIB
1.3.6.1.4.1.4329.15hiPathWirelessHIPATH-WIRELESS-SMI
1.3.6.1.4.1.4329.15.3hiPathWirelessMgmtHIPATH-WIRELESS-SMI
Numeric OIDNameModule
1.3.6.1.4.1.4329.15.3.2hiPathWirelessControllerHIPATH-WIRELESS-HWC-MIB
1.3.6.1.4.1.4329.15.3.2.5vnManagerObjectsHIPATH-WIRELESS-HWC-MIB
1.3.6.1.4.1.4329.15.3.2.5.4vnLocalClientsHIPATH-WIRELESS-HWC-MIB