T-ISP-028 · IP SLA / Y.1731 OAM Monitor

Provision and collect IP SLA probes (ICMP/UDP-jitter) and Ethernet Y.1731 OAM (DMM/SLM) measurements, computing per-path latency/jitter/loss against SLA targets for proactive NOC alerting.

Cisco IOS/XE

Cisco IOS-XR

Juniper Junos

Open in Generator Open in Platform

You're viewing a preview

The full script, parameters, and execution console are available with a free account.

Already have access? Sign in →

Capabilities

IP SLA probe provision
Y.1731 DMM/SLM collect
Latency/jitter/loss calc
Target threshold alert
Per-path rollup
JSON report

Required inputs

Parameters the script accepts. Defaults shown; some are vendor- or context-gated.

Parameter	Type	Default	Notes
Latency target (ms) latency_ms	number	30	—
Loss target (%) loss_pct	number	0.1	—

Hint 1 — Name your vendors and OS versions

Mention the exact platforms you run (Cisco IOS/XE, Cisco IOS-XR, Juniper Junos) so the generated isp & peering logic uses the right CLI/NETCONF syntax.

Hint 2 — State your real thresholds

Provide concrete values for Latency target (ms), Loss target (%) instead of the defaults — they shape what counts as a fault.

Hint 3 — Prioritize the checks you need

This tool can iP SLA probe provision and y.1731 DMM/SLM collect. Ask for the subset relevant to your incident to keep output focused.

Hint 4 — Describe your inventory format

Tell the assistant whether your device list is CSV, YAML, or JSON and which columns it has, so parsing matches your data.

Sample inventory schema

Authoritative shape of the device/policy data this script consumes.

No bundled inventory sample. The script accepts standard device lists (CSV/YAML) with hostname, mgmt IP, vendor, and credentials.

Expected output

Reference terminal output the script should produce — used as a stylistic and structural target.

terminal

2026-06-15 21:00:00 INFO  Collected 24 SLA/OAM measurements
2026-06-15 21:00:00 INFO  pe-rtr-01->pe-rtr-05: 12.4ms jitter 1.1ms loss 0.0% OK
2026-06-15 21:00:00 WARN  pe-rtr-02->pe-rtr-09: 41.7ms (> 30ms target) BREACH
2026-06-15 21:00:00 INFO  Report written to oam-report.json (1 breach)