AVAYA-IPSEC-MIB :: avipsTunnelState

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsAVAYA-IPSEC-MIBavipsTunnelState

avipsTunnelState

Module: AVAYA-IPSEC-MIB

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

OID (numeric): 1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.16

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This object specifies the state of this tunnel. 1. closed - The tunnel does not exist between the peers because it was not negotiated yet, or because last tunnel closed normally due to hard timeout, clear by admin or DELETE received from the remote peer. This is also the initial state of the row when it is created. 2. inProgress - The tunnel does not exist between peers, but it is currently being negotiated in IKE Quick Mode. 3. established - The tunnel exists between peers. 4. failed - The tunnel does not exist between peers because of a failure: 1. Last time we tried to establish this tunnel the negotiation failed. 2. The connection with the remote peer has failed due to one of the following, and hence all the corresponding ipsec tunnels were closed: a. Last time we tried to establish IKE the negotiation failed. b. During last connection a track object signaled a connection failure. c. The interface used for local-address does not have an IP address asigned to it 1 minute or more after this row was created.

NOTE: The word 'tunnel' in this context refers to 1 or more IPSec SAs (ESP or AH) between the peers, pertaining to the proxy addresses specified in this entry. As long as there is at least 1 SA established, the tunnel state shall remain 'established'.

What is avipsTunnelState?

This read-only value reports this specific tunnel's current state: closed (no SA yet, or last one ended normally), inProgress (being negotiated via IKE Quick Mode), established (at least one IPSec SA up), or failed (negotiation failure, or the underlying peer connection itself failed). Since a 'tunnel' here can consist of multiple ESP/AH SAs, the state stays established as long as at least one of them is up.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.16
snmpwalk -v2c -c public <target> AVAYA-IPSEC-MIB::avipsTunnelState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.16.1
snmpget -v2c -c public <target> AVAYA-IPSEC-MIB::avipsTunnelState.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> avipsTunnelState.1

Start monitoring Avaya converged Gateways with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the AVAYA-IPSEC-MIB::avipsTunnelState 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.4avipsMonitoringGroupAVAYA-IPSEC-MIB
1.3.6.1.4.1.6889.2.6.1.1.4.1avipsMonitoringTablesAVAYA-IPSEC-MIB
1.3.6.1.4.1.6889.2.6.1.1.4.1.3avipsTunnelTableAVAYA-IPSEC-MIB
1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1avipsTunnelEntryAVAYA-IPSEC-MIB
1.3.6.1.4.1.6889.2.6.1.1.4.1.3.1.16avipsTunnelStateAVAYA-IPSEC-MIB