VPN-MIB :: logAttackType

MIB Reference — IPNetwork Monitor · Updated September 21, 2026

All MIBs › VPN-MIB › logAttackType

logAttackType

Module: VPN-MIB

OID (symbolic): VPN-MIB::logAttackType

OID (numeric): 1.3.6.1.4.1.1866.7.3.1.1.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The type of packet error that caused us to perceive this as an attack. 1 - SKIP header error. e.g. this packet was not IPSec AH or IPSec ESP. 2 - SKIP Counter N error. Not currently (1/9/98) supported. 3 - SKIP Algorithm mismatch. The parameters of the VPN that this packet belongs to does not match the VPN parameters in the SKIP header. 4 - SKIP Authentication error. The authentication key in the offending packet was not correct. This type of attack results in an authFailure trap which shows up on the VPNmanager as Invalid Authentication Signature. 5 - SKIP Authentication Header error. Not supported. 6 - SKIP Encryption Header error. The packet's ESP trailer wasn't correct.

What is logAttackType?

Read-only code identifying what kind of packet anomaly this security log entry represents: 1 SKIP header error (not valid IPSec AH/ESP), 2 SKIP counter N error (unsupported), 3 SKIP algorithm mismatch, 4 SKIP authentication error (bad key, also raises an authFailure trap), 5 SKIP authentication header error (unsupported), or 6 SKIP encryption header error (bad ESP trailer).

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1866.7.3.1.1.3
snmpwalk -v2c -c public <target> VPN-MIB::logAttackType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1866.7.3.1.1.3.1
snmpget -v2c -c public <target> VPN-MIB::logAttackType.1

Start monitoring VPN gateway / WAN access router (per-interface frame/error/discard counter status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the VPN-MIB::logAttackType OID value, configure state conditions and alerts, and monitor any VPN gateway / WAN access router (per-interface frame/error/discard counter status) from a single console.

OID Breakdown

Upper-level ancestors (6 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
Numeric OIDNameModule
1.3.6.1.4.1.1866vpnetVPN-MIB
1.3.6.1.4.1.1866.7vpnmibVPN-MIB
1.3.6.1.4.1.1866.7.3logVPN-MIB
1.3.6.1.4.1.1866.7.3.1logTableVPN-MIB
1.3.6.1.4.1.1866.7.3.1.1logEntryVPN-MIB
1.3.6.1.4.1.1866.7.3.1.1.3logAttackTypeVPN-MIB