AVAYA-IPSEC-MIB :: avipsGlobalsInvalidSpiRecovery

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsAVAYA-IPSEC-MIBavipsGlobalsInvalidSpiRecovery

avipsGlobalsInvalidSpiRecovery

Module: AVAYA-IPSEC-MIB

OID (symbolic): AVAYA-IPSEC-MIB::avipsGlobalsInvalidSpiRecovery

OID (numeric): 1.3.6.1.4.1.6889.2.6.1.1.1.1

Node type: OBJECT-TYPE

Type: TruthValue

Access: read-write

Description: This object determines whether invalid-spi-recovery is enabled (true) or disabled (false). When enabled, the device shall open an IKE SA, if it does not already exist, in order to send DELETE message to the remote peer when receiving an invalid spi or invalid cookie with SIP of that remote peer. This causes faster recovery times in case of SADB inconsistency, but may cause D/DoS attack on the remote peer.

What is avipsGlobalsInvalidSpiRecovery?

This read-write switch turns on invalid-SPI recovery, which makes the device open an IKE security association (if none exists) so it can send a DELETE message to a remote peer that sent an invalid SPI or cookie. Enabling it speeds up recovery from SA-database inconsistencies, but the tradeoff is that it can expose the device to a denial-of-service attack from a spoofed remote peer, so it's a security-vs-resilience tradeoff an admin should weigh deliberately.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6889.2.6.1.1.1.1
snmpwalk -v2c -c public <target> AVAYA-IPSEC-MIB::avipsGlobalsInvalidSpiRecovery

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6889.2.6.1.1.1.1.1
snmpget -v2c -c public <target> AVAYA-IPSEC-MIB::avipsGlobalsInvalidSpiRecovery.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.6889.2.6.1.1.1.1.1 s <value>

Start monitoring Avaya converged Gateways with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the AVAYA-IPSEC-MIB::avipsGlobalsInvalidSpiRecovery OID value, configure state conditions and alerts, and monitor any Avaya converged Gateways from a single console.

OID Breakdown

Upper-level ancestors (9 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
1.3.6.1.4.1.6889avayaAV-APPLICATION-ENABLEMENT-SERVICES-MIB
1.3.6.1.4.1.6889.2mibsAV-APPLICATION-ENABLEMENT-SERVICES-MIB
1.3.6.1.4.1.6889.2.6avGatewayMibsAVAYAGEN-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6889.2.6.1avayaIpsecMibAVAYA-IPSEC-MIB
1.3.6.1.4.1.6889.2.6.1.1avipsMIBObjectsAVAYA-IPSEC-MIB
1.3.6.1.4.1.6889.2.6.1.1.1avipsGlobalsAVAYA-IPSEC-MIB
1.3.6.1.4.1.6889.2.6.1.1.1.1avipsGlobalsInvalidSpiRecoveryAVAYA-IPSEC-MIB