CISCO-IPSEC-SIGNALING-MIB :: cisgIpsSgFailReason

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-IPSEC-SIGNALING-MIBcisgIpsSgFailReason

cisgIpsSgFailReason

Module: CISCO-IPSEC-SIGNALING-MIB

OID (symbolic): CISCO-IPSEC-SIGNALING-MIB::cisgIpsSgFailReason

OID (numeric): 1.3.6.1.4.1.9.9.438.1.4.2.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The reason for the failure. Possible reasons include: 1 = other 2 = peer delete request was received 3 = contact with peer was lost 4 = local failure occurred 5 = authentication failure 6 = hash validation failure 7 = encryption failure 8 = internal error occurred 9 = system capacity failure 10 = proposal failure 11 = peer's certificate is unavailable 12 = peer's certificate was found invalid 13 = local certificate expired 14 = certificate revoke list (crl) failure 15 = peer encoding error 16 = Reference to a non-existent control tunnel 17 = Extended User authentication failed 18 = operator requested termination. 19 = An attempt to establish a tunnel was aborted by the admission control policy (this could include a simple policy that limits the maximum active tunnels) 20 = A protocol specific reason (look in the protocol-specific MIB for more info).

What is cisgIpsSgFailReason?

This reports the specific reason a Phase-1 negotiation failure was recorded, per its description, with coded values including peer delete request, lost contact with peer, local failure, authentication failure, hash validation failure, encryption failure, internal error, system capacity failure, proposal failure, and peer certificate issues. It's the single most diagnostic field in the failure table, immediately telling an admin the category of problem behind a specific failed negotiation attempt without needing to cross-reference other counters. A failure entry showing reason 9 (system capacity failure) points straight at the device running out of resources, entirely different troubleshooting from reason 5 (authentication failure) pointing at a credential problem.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.438.1.4.2.1.2
snmpwalk -v2c -c public <target> CISCO-IPSEC-SIGNALING-MIB::cisgIpsSgFailReason

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.438.1.4.2.1.2.1
snmpget -v2c -c public <target> CISCO-IPSEC-SIGNALING-MIB::cisgIpsSgFailReason.1

SNMPv3 example:

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

Start monitoring Cisco VPN gateway equipment with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-IPSEC-SIGNALING-MIB::cisgIpsSgFailReason OID value, configure state conditions and alerts, and monitor any Cisco VPN gateway equipment from a single console.

OID Breakdown

Upper-level ancestors (8 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.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.438ciscoIPsecSignalingMIBCISCO-IPSEC-SIGNALING-MIB
1.3.6.1.4.1.9.9.438.1ciscoIPsecSigMIBObjectsCISCO-IPSEC-SIGNALING-MIB
1.3.6.1.4.1.9.9.438.1.4cisgIpsSgFailuresCISCO-IPSEC-SIGNALING-MIB
1.3.6.1.4.1.9.9.438.1.4.2cisgIpsSgFailTableCISCO-IPSEC-SIGNALING-MIB
1.3.6.1.4.1.9.9.438.1.4.2.1cisgIpsSgFailEntryCISCO-IPSEC-SIGNALING-MIB
1.3.6.1.4.1.9.9.438.1.4.2.1.2cisgIpsSgFailReasonCISCO-IPSEC-SIGNALING-MIB