Connectivity Path Analyzer

End-to-end path verification: bi-directional ping with statistics, traceroute asymmetry detection, MTU path discovery (PMTUD simulation), RPF check, QoS DSCP marking verification, and latency SLA baseline.

Cisco IOS/XE/XR

Juniper

Arista

Any

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

Bi-directional reachability
Traceroute asymmetry detection
MTU path discovery
DSCP marking verification
RPF/uRPF check
Latency SLA baseline
ECMP load-balance analysis

Required inputs

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

Parameter	Type	Default	Notes
Source prefix/host source_prefix	string	—	—
Destination prefix/host dest_prefix	string	—	—
Ping count ping_count	number	100	—
Latency SLA (ms) latency_sla_ms	number	10	—
Verify DSCP marking check_dscp	bool	true	—

Hint 1 — Name your vendors and OS versions

Mention the exact platforms you run (Cisco IOS/XE/XR, Juniper, Arista, …) so the generated analysis logic uses the right CLI/NETCONF syntax.

Hint 2 — State your real thresholds

Provide concrete values for Source prefix/host, Destination prefix/host, Ping count instead of the defaults — they shape what counts as a fault.

Hint 3 — Prioritize the checks you need

This tool can bi-directional reachability and traceroute asymmetry detection. 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

PATH ANALYSIS: 10.0.0.1 → 203.0.113.50
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

FORWARD PATH (10.0.0.1 → 203.0.113.50)
  Hop 1:  10.0.0.1   core-rtr-01    Gi0/0/0    0.2ms
  Hop 2:  10.1.0.1   core-rtr-02    Gi0/1/0    0.5ms
  Hop 3:  192.0.2.1  pe-rtr-01      Te0/0/0    1.2ms
  Hop 4:  203.0.113.1 edge-rtr-01   Te0/1/0    2.1ms
  Hop 5:  203.0.113.50 destination  —          2.4ms