NETWORK-ALCHEMY-IPSEC-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › NETWORK-ALCHEMY-IPSEC-MIB

Organization: Network Alchemy, Inc.

Last Updated: 2000-10-25

Category: IPSec/VPN

Description: Monitors IPsec tunnel states, SA counts, and VPN throughput on Network Alchemy security appliances.

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 NETWORK-ALCHEMY-IPSEC-MIB?

NETWORK-ALCHEMY-IPSEC-MIB is a vendor-specific MIB from Network Alchemy, Inc. (a maker of IPsec/VPN crypto cluster appliances) that exposes aggregate, appliance-wide IPsec statistics rather than a per-tunnel table. It is organized into replayStats (replayStatsWraps, replayStatsReplays, replayStatsoutofrange), naIKEStats (naIKEStatsacounts for total ISAKMP SAs, naIKEStatsmainmodes/quickmodes/aggressivemodes, naIKEStatsbadhash/badsig for authentication failures), naAHStats and naESPStats (per-protocol sent/received datagram counts, crypto-processing distribution across server process/secondary processor/HiFn hardware accelerator, output/input errors, SA lookup failures, replay detections), and naKeyStats. These scalar counters are useful for monitoring the overall health and load of the IPsec crypto engine — authentication failure rates, hardware-offload utilization, and SA churn — even though they don't break results down by individual tunnel or peer. It depends on the vendor's NETAL-SMI module for its OID root and standard SNMPv2-SMI/TC imports, and is deployed on Network Alchemy IPsec/VPN cluster appliances; this NETWORK-ALCHEMY-IPSEC-MIB is used for SNMP monitoring of IPsec crypto engine health.

IPNetwork Monitor allows you to monitor SNMP objects defined in NETWORK-ALCHEMY-IPSEC-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

  • Network Alchemy IPsec/VPN crypto cluster appliances

Monitoring Examples

An operator polls naESPStats objects to track esp output/input error counts and SA lookup failures alongside naIKEStatsacounts for the total ISAKMP SA count; a rising naESPStats error counter combined with a flat or falling ISAKMP SA total would indicate the crypto hardware is failing to process ESP traffic even as new tunnels attempt to negotiate.

What Can Be Monitored

  • anti-replay window statistics
  • IKE/ISAKMP SA counts and negotiation-mode counters
  • AH and ESP sent/received datagram counters
  • crypto processing distribution (server/secondary/hardware accelerator)
  • output/input errors and resource-allocation drops
  • SA lookup failure and replay-detection counts
Imported Objects

From NETAL-SMI

ipsecOBJECT-IDENTITY
netalModulesOBJECT-IDENTITY

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString

How to Use in IPNetwork Monitor

Example using replayStatsWraps OID:

Select a Network Alchemy IPsec/VPN crypto cluster appliance 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 replayStatsWraps into the Find box to locate it in the OID tree, then select it and click OK. It reports the number of wrapped sequence numbers detected. 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 the count changes from its expected baseline, since that would indicate the underlying set of items changed unexpectedly. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Monitors IPsec performance statistics including IKE, AH, ESP, and replay attack detection in Network Alchemy systems.

Start monitoring Network Alchemy IPsec/VPN crypto cluster appliance 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 NETWORK-ALCHEMY-IPSEC-MIB