CISCO-IPSEC-SIGNALING-MIB :: cisgIpsSgTunHistTermReason

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-IPSEC-SIGNALING-MIBcisgIpsSgTunHistTermReason

cisgIpsSgTunHistTermReason

Module: CISCO-IPSEC-SIGNALING-MIB

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

OID (numeric): 1.3.6.1.4.1.9.9.438.1.3.2.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The reason the Phase-1 Control Tunnel was terminated. Possible reasons include: 1 = other 2 = normal termination 3 = operator request 4 = peer delete request was received 5 = contact with peer was lost 6 = applicationInitiated (eg: L2TP requesting the termination) 7 = failure of extended user authentication 8 = local failure occurred.

What is cisgIpsSgTunHistTermReason?

This reports why a specific Phase-1 control tunnel in the history table was terminated, per its description, with coded reasons including normal termination, operator request, peer delete request, lost contact with peer, application-initiated closure, extended user authentication failure, and local failure. It's the single most useful field for triaging why a tunnel went away after the fact, distinguishing a routine, expected teardown from an actual problem worth escalating. A history entry showing reason 7 (failure of extended user authentication) for a remote-access tunnel points straight at a client credential issue rather than a network problem.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.438.1.3.2.1.2
snmpwalk -v2c -c public <target> CISCO-IPSEC-SIGNALING-MIB::cisgIpsSgTunHistTermReason

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.438.1.3.2.1.2.1
snmpget -v2c -c public <target> CISCO-IPSEC-SIGNALING-MIB::cisgIpsSgTunHistTermReason.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::cisgIpsSgTunHistTermReason 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.3cisgIpsSgHistoryCISCO-IPSEC-SIGNALING-MIB
1.3.6.1.4.1.9.9.438.1.3.2cisgIpsSgTunnelHistTableCISCO-IPSEC-SIGNALING-MIB
1.3.6.1.4.1.9.9.438.1.3.2.1cisgIpsSgTunnelHistEntryCISCO-IPSEC-SIGNALING-MIB
1.3.6.1.4.1.9.9.438.1.3.2.1.2cisgIpsSgTunHistTermReasonCISCO-IPSEC-SIGNALING-MIB