ALTIGA-EVENT-STATS-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › ALTIGA-EVENT-STATS-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2003-01-13

Category: VPN and Security, Vendor: Altiga

Description: Altiga (Cisco VPN 3000) event statistics MIB for monitoring system event log counts and severity distribution.

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 ALTIGA-EVENT-STATS-MIB?

ALTIGA-EVENT-STATS-MIB is a proprietary MIB from Altiga Networks, whose product line became the Cisco VPN 3000 Series Concentrator, used to track statistics about the device's internal system event log. It exposes a table of event counts broken out by event class and event number, along with a notification object for alerting on event activity. This is fundamentally a software-health monitoring MIB: rising counts for a particular event class or number reveal recurring internal faults, warnings, or error conditions logged by the concentrator's software, letting an admin spot problems before they escalate. It is a standalone Altiga proprietary module typically deployed alongside the sibling ALTIGA-FILTER-STATS-MIB, ALTIGA-L2TP-STATS-MIB, and ALTIGA-MULTILINK-STATS-MIB modules that share the same enterprise MIB architecture. It is deployed on Cisco/Altiga VPN 3000 Series Concentrators used for remote-access and site-to-site VPN termination, where administrators often load it into an ALTIGA-EVENT-STATS-MIB MIB Browser to inspect event counters directly.

IPNetwork Monitor allows you to monitor SNMP objects defined in ALTIGA-EVENT-STATS-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

  • Cisco/Altiga VPN 3000 Series concentrator

Monitoring Examples

An administrator would poll alEventStatsTable entries keyed by alEventStatsClass and alEventStatsEventNumber to read alEventStatsCount, watching for a sharp rise in counts for a high-severity event class as an early indicator of a recurring internal fault. The alStatsEventNotificationId trap can be configured to alert automatically when a counter increments significantly, reducing the need for constant polling. Comparing counts across event classes over time helps distinguish a one-off glitch from a systemic software issue.

What Can Be Monitored

  • event count by class and event number
  • event log severity distribution
  • event count threshold notifications
Imported Objects

From ALTIGA-GLOBAL-REG

alEventMibModuleOBJECT-IDENTITY

From ALTIGA-MIB

alEventGroupOBJECT-IDENTITY
alStatsEventOBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString

How to Use in IPNetwork Monitor

Example using alEventStatsCount OID:

Select a Cisco (Altiga) VPN 3000 Series Concentrator (legacy) 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 alEventStatsCount 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. The number of times that the given event for the give class has been generated. 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.
OIDs

RFC description

Altiga (Cisco VPN 3000) MIB that models event statistics and counters on VPN concentrators, enabling monitoring of VPN-related events and system alerts.

Start monitoring Cisco (Altiga) VPN 3000 Series Concentrators (legacy) 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 ALTIGA-EVENT-STATS-MIB