A10-AX-MIB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsA10-AX-MIB

Organization: A10 Networks, Inc.

Last Updated: 2007-05-07

Category: Hardware and Environment, Vendor: A10 Networks

Description: MIB for managing A10 Networks AX/Thunder application delivery controllers, covering server load balancing statistics, SSL proxy metrics, DDoS counters, along with CPU and power supply status.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring A10-AX-MIB with a free 30-day trial of IPNetwork Monitor.

What Is A10-AX-MIB?

A10-AX-MIB is A10 Networks' enterprise MIB for its AX Series/Thunder application delivery controllers (ADC), covering server load balancing, SSL offload, and security functions. Based on the visible notification objects, its data spans configuration and operational state around virtual servers, real (SLB) servers, and trunk/link-aggregation groups, along with threshold-based alerting for resource usage and connection limits. Its monitoring focus is squarely on software/service health and performance: current connection counts per SLB server, traffic-drop events with a stated reason (useful for DDoS mitigation visibility), and configured-versus-current usage thresholds that flag when a resource such as connection limits is being exceeded -- complementing the CPU, memory, and power-supply status covered elsewhere in the fuller A10 MIB suite. As an ADC-specific enterprise MIB it is generally deployed alongside standard IF-MIB and ENTITY-MIB objects for interface and chassis inventory, since A10-AX-MIB itself concentrates on load-balancing/security semantics rather than base hardware inventory. It is used in data centers and service-provider environments where A10 Thunder/AX appliances front-end application servers and need real-time load, threshold, and anomaly notification, making A10-AX-MIB SNMP monitoring a standard part of ADC-focused network monitoring deployments.

IPNetwork Monitor allows you to monitor SNMP objects defined in A10-AX-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • A10 Thunder 7460S (2025) — 6th-gen mid-range ADC, 150–270 Gbps
  • A10 Thunder 1060S (2024) — 6th-gen entry-level ADC

Monitoring Examples

An administrator would watch for axNotificationMsg traps carrying axNotificationSLBServer and axNotificationSLBPort together with axNotificationSLBCurConns, revealing that a specific real server/port has hit an unusually high current-connection count. A trap referencing axNotificationVirtualServer, axNotificationVirtualServerPort, and axNotificationDropEventReason would indicate the ADC dropped traffic on a virtual server -- for example due to a DDoS mitigation trigger -- and comparing axNotificationCurrentUsage against axNotificationConfiguredThreshold shows how far a monitored resource has exceeded its configured limit. axNotificationTrunkID further ties these events to a specific link-aggregation trunk, helping isolate which physical trunk group is involved in a connection-limit or threshold event.

What Can Be Monitored

  • SLB server current connections
  • virtual server traffic drop events
  • configured vs. current resource usage thresholds
  • connection limit breaches
  • trunk-level event correlation
Imported Objects

From A10-COMMON-MIB

a10MgmtOBJECT-IDENTITY

From RFC1155-SMI

Counter

From SNMPv2-SMI

Counter32
Counter64
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString
PhysAddress

How to Use in IPNetwork Monitor

Example using axSysMemoryUsage OID:

Select an A10 Networks Thunder ADC 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 axSysMemoryUsage into the Find box to locate it in the OID tree, then select it and click OK. It reports the amount of memory currently in use, in KB. 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 usage approaches the device's total memory capacity (e.g. above 85-90% of total), since sustained high memory usage can precede performance degradation. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Management MIB for A10 Networks AX/Thunder application delivery controllers, covering server load balancing stats, SSL proxy metrics, DDoS counters, CPU, and power supply status.

Start monitoring A10 Networks Thunder ADCs with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download A10-AX-MIB