Check IPSLA Tag Status (Service Check)
- 01 Mar 2025
- 1 Minute to read
- Print
- DarkLight
- PDF
Check IPSLA Tag Status (Service Check)
- Updated on 01 Mar 2025
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
See also Service Check
Basic Information
Service Check Category: Network Connectivity Checks
Passive: No
Description
This service check first checks Cisco's "rttMonCtrlAdminEntry" (OID 1.3.6.1.4.1.9.9.42.1.2.1.1.3) for tags that match a user-defined value in the IPSLA TAG NAME field. If it finds any matching tags it checks the current state of that IPSLA tag using rttMonLatestRttOperEntry (OID .1.3.6.1.4.1.9.9.42.1.2.10.1.2).
It will translate the returned code into a status message and return a critical state for any code other than 1.
| Code | Status |
|---|---|
| 0 | unknown |
| 1 | ok |
| 2 | disconnected |
| 3 | over threshold |
| 4 | timeout |
| 5 | busy |
| 6 | not connected |
| 7 | dropped |
| 8 | sequence error |
| 9 | verify error |
| 10 | application specific |
| 11 | dns server timeout |
| 12 | tcp connect timeout |
| 13 | http transaction timeout |
| 14 | dns query error |
| 15 | http error |
| 16 | error |
Check-specific Configuration Fields
The following configuration fields are specific to this type of service check. See Service Check for configuration parameters common to all service checks.
- IPSLA TAG NAME - (Required) This is the only field for this service check. It is compared against the results of 1.3.6.1.4.1.9.9.42.1.2.1.1.3. If an exact match is found, we will check that entry's status.
Was this article helpful?