ARUBAWIRED-PORTSECURITY-MIB :: arubaWiredClientLimitViolationCount

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ARUBAWIRED-PORTSECURITY-MIB › arubaWiredClientLimitViolationCount

arubaWiredClientLimitViolationCount

Module: ARUBAWIRED-PORTSECURITY-MIB

OID (symbolic): ARUBAWIRED-PORTSECURITY-MIB::arubaWiredClientLimitViolationCount

OID (numeric): 1.3.6.1.4.1.47196.4.1.1.3.21.1.2.1.1.8

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Number of client limit violations that have occurred on this port since system boot.

What is arubaWiredClientLimitViolationCount?

This counter tallies how many times a port exceeded its client limit since system boot. Example: if limit is 1 and two devices connect, the count increments. Useful for identifying problematic ports requiring policy adjustment.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.47196.4.1.1.3.21.1.2.1.1.8
snmpwalk -v2c -c public <target> ARUBAWIRED-PORTSECURITY-MIB::arubaWiredClientLimitViolationCount

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.47196.4.1.1.3.21.1.2.1.1.8.1
snmpget -v2c -c public <target> ARUBAWIRED-PORTSECURITY-MIB::arubaWiredClientLimitViolationCount.1

Start monitoring Aruba (HPE) ArubaOS-CX wired switches with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ARUBAWIRED-PORTSECURITY-MIB::arubaWiredClientLimitViolationCount OID value, configure state conditions and alerts, and monitor any Aruba (HPE) ArubaOS-CX wired switches from a single console.

How to Use in IPNetwork Monitor

Select an Aruba (HPE) ArubaOS-CX wired switch 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 arubaWiredClientLimitViolationCount 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 client limit violations that have occurred on this port since system boot. 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 between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (12 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.47196hpeARUBAWIRED-NETWORKING-OID
1.3.6.1.4.1.47196.4hpeNetworkingARUBAWIRED-NETWORKING-OID
1.3.6.1.4.1.47196.4.1wiredNetworkingDevicesARUBAWIRED-NETWORKING-OID
1.3.6.1.4.1.47196.4.1.1arubaOS_CXARUBAWIRED-NETWORKING-OID
1.3.6.1.4.1.47196.4.1.1.3wndFeaturesARUBAWIRED-NETWORKING-OID
1.3.6.1.4.1.47196.4.1.1.3.21arubaWiredPortSecurityMIBARUBAWIRED-NETWORKING-OID
Numeric OIDNameModule
1.3.6.1.4.1.47196.4.1.1.3.21.1arubaWiredPortSecurityObjectsARUBAWIRED-PORTSECURITY-MIB
1.3.6.1.4.1.47196.4.1.1.3.21.1.2arubaWiredPortSecurityPortObjectsARUBAWIRED-PORTSECURITY-MIB
1.3.6.1.4.1.47196.4.1.1.3.21.1.2.1arubaWiredPortSecurityPortTableARUBAWIRED-PORTSECURITY-MIB
1.3.6.1.4.1.47196.4.1.1.3.21.1.2.1.1arubaWiredPortSecurityPortEntryARUBAWIRED-PORTSECURITY-MIB
1.3.6.1.4.1.47196.4.1.1.3.21.1.2.1.1.8arubaWiredClientLimitViolationCountARUBAWIRED-PORTSECURITY-MIB