@ redbarron
We just started looking into this as well. At this point, we have come up with the concept to monitor the keep-alive probes. That was the closest we could get to monitor the IPSEC Tunnels. Here are the values for the probes:
adGenAOSnmStatusName OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(1..40))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The name of the corresponding probe entry. The probe identified by
a particular value of this index is the same probe as identified
by the same value as a adGenAOSnmName object instance."
::= { adGenAOSnmProbeStatusEntry 1 }
adGenAOSnmTestStatus OBJECT-TYPE
SYNTAX INTEGER
{
fail (1),
pass (2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current test state of the probe."
::= { adGenAOSnmProbeStatusEntry 2 }
adGenAOSnmTestsRun OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of test run on the probe."
::= { adGenAOSnmProbeStatusEntry 3 }
adGenAOSnmTestsFailed OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of test that failed."
::= { adGenAOSnmProbeStatusEntry 4 }
adGenAOSnmStatsToleranceTestSize OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the test size."
::= { adGenAOSnmProbeStatusEntry 5 }
adGenAOSnmStatsToleranceTestValue OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies number of tests that passed or failed.
Check 'adGenAOSnmTestStatus' for test state."
::= { adGenAOSnmProbeStatusEntry 6 }
adGenAOSnmTimeSinceLastStatusChange OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time since last status change."
::= { adGenAOSnmProbeStatusEntry 7 }
