All MIBs › A10-AX-TRAPS
Category: Alarm and Event Management, Vendor: A10 Networks
Description: Provides SNMP trap definitions for A10 Networks AX Series load balancers, including health-check and resource alert traps.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.
What Is A10-AX-TRAPS?
A10-AX-TRAPS is the companion vendor MIB from A10 Networks that defines the actual SNMP NOTIFICATION-TYPE (trap) definitions fired by AX Series application delivery controllers and load balancers, as opposed to the payload objects carried in A10-AX-NOTIFICATIONS. It belongs to the A10 AX product line's fault-management framework, covering events such as server-load-balancing health-check failures, virtual-server state changes, and resource-threshold alarms. Its purpose is fault/event monitoring rather than static configuration: it lets an NMS know the instant a real server, virtual server, or trunk changes state or a configured usage threshold is crossed. Each trap embeds the objects from A10-AX-NOTIFICATIONS, so the two modules are tightly coupled and must be loaded together for traps to decode correctly. It's deployed wherever A10 AX/Thunder appliances balance traffic to server farms and operations teams want immediate alerts rather than only polling. Engineers can download the A10-AX-TRAPS file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in A10-AX-TRAPS. 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 Networks AX Series application delivery controller / load balancer
Monitoring Examples
A trap bound to axNotificationSLBServer, axNotificationSLBPort, and axNotificationSLBCurConns fires when a load-balanced pool member fails its health check or exceeds its connection ceiling, letting an admin pull it from rotation. Another trap carrying axNotificationDroppedPackets alongside axNotificationConfiguredThreshold and axNotificationCurrentUsage signals that a rate-limit or bandwidth threshold on a virtual server has been breached and packets are being discarded. axNotificationConnLimit and axNotificationTrunkID let the receiver distinguish a per-connection-limit event from a trunk/link-level fault.
What Can Be Monitored
- SLB server health-check state changes
- virtual server up/down events
- connection limit breaches
- dropped packet alarms
- configured threshold vs current usage
- trunk fault events
Imported Objects
From A10-AX-MIB
| axLogging | OBJECT-IDENTITY |
| axNotification | OBJECT-IDENTITY |
From INET-ADDRESS-MIB
| InetAddressType |
From SNMPv2-SMI
| Counter32 | |
| Integer32 | |
| OBJECT-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| DateAndTime | |
| DisplayString | |
| PhysAddress |
How to Use in IPNetwork Monitor
Example using axNotificationSLBCurConns OID:
OIDs
RFC description
SNMPv1 trap definitions for A10 AX load balancer system, application, and network events.
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.