All MIBs › AVAYA-IPSEC-MIB › avipsPeerIsakmpState
avipsPeerIsakmpState
Module: AVAYA-IPSEC-MIB
OID (symbolic): AVAYA-IPSEC-MIB::avipsPeerIsakmpState
OID (numeric): 1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.13
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: This object specifies the state of the IKE connection between the peers. 1. closed - No IKE SA exists between peers because it was not negotiated yet, or because last IKE 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 - No IKE SA exists between peers, but it is currently being negotiated in Phase-1. 3. established - IKE SA exists between peers. 4. failed - No IKE SA exists between peers because of a failure. Possible reasons are: 1. Last time we tried to establish IKE the negotiation failed. 2. Last time we tried to establish IKE the remote peer DNS resolution failed. 3. During last connection DPD signaled a connection failure. 4. During last connection a track object signaled a connection failure. 5. The interface used for local-address does not have an IP address asigned to it 1 minute or more after this row was created. 6. Last time we negotiated Phase-2 the negotiation timed-out, and the current IKE was subsequently deleted.
NOTE: When continuous-channel IKE is used, the state shall remain 'established' during the normal transition time between one IKE SA and the next. However, if the IKE SA was deleted due to a suspected problem then the state will change normally during the transition (i.e. 'closed' and then 'inProgress'). [Suspected problem: if the last IKE SA was DELETEd by the remote peer after less then 5 minutes,or if it was deleted by local admin]
What is avipsPeerIsakmpState?
This read-only value reports the current IKE (Phase 1) connection state between the local and remote peer: closed (no SA, not yet negotiated or cleanly ended), inProgress (negotiation underway), established (SA exists), or failed (SA absent due to negotiation failure, DNS failure, DPD signaling a problem, a tracker signaling failure, or a missing local IP). Under continuous-channel IKE the state normally stays established through routine SA renewal, only dropping to closed/inProgress if the prior SA was deleted for a suspected problem.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.13 snmpwalk -v2c -c public <target> AVAYA-IPSEC-MIB::avipsPeerIsakmpState
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.13.1 snmpget -v2c -c public <target> AVAYA-IPSEC-MIB::avipsPeerIsakmpState.1
Start monitoring Avaya converged Gateways with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the AVAYA-IPSEC-MIB::avipsPeerIsakmpState 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.6889 | avaya | AV-APPLICATION-ENABLEMENT-SERVICES-MIB |
| 1.3.6.1.4.1.6889.2 | mibs | AV-APPLICATION-ENABLEMENT-SERVICES-MIB |
| 1.3.6.1.4.1.6889.2.6 | avGatewayMibs | AVAYAGEN-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.6889.2.6.1 | avayaIpsecMib | AVAYA-IPSEC-MIB |
| 1.3.6.1.4.1.6889.2.6.1.1 | avipsMIBObjects | AVAYA-IPSEC-MIB |
| 1.3.6.1.4.1.6889.2.6.1.1.4 | avipsMonitoringGroup | AVAYA-IPSEC-MIB |
| 1.3.6.1.4.1.6889.2.6.1.1.4.1 | avipsMonitoringTables | AVAYA-IPSEC-MIB |
| 1.3.6.1.4.1.6889.2.6.1.1.4.1.2 | avipsPeerTable | AVAYA-IPSEC-MIB |
| 1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1 | avipsPeerEntry | AVAYA-IPSEC-MIB |
| 1.3.6.1.4.1.6889.2.6.1.1.4.1.2.1.13 | avipsPeerIsakmpState | AVAYA-IPSEC-MIB |