PermitANY

Troubleshooting · python · 444 copies

Network Path Analyzer

A traceroute shows you less than half the path. Layer 2 switches never appear in one because they do not decrement TTL, and a firewall that happily forwards your probe can still be dropping the port you care about -- the probe is ICMP or UDP and matches a different rule. This walks the real path for one flow, from the source's own gateway so the path is the one that traffic takes, enters every device on it, and names the hop that hurts: the saturated uplink, the access port throwing CRCs, the link that flapped at 3am, or the rule that denies the traffic, by name. Counters are read by cause rather than listed -- CRC is the cable, late collisions are a duplex mismatch, output drops are not an error at all -- and the age of those counters is printed beside them, because a total is not a rate. Pivots to the HSRP or VRRP active member on its own, and a field it could not read prints as a dash, never as a zero.

  • Arista EOS
  • FortiOS
  • Cisco IOS
  • Cisco IOS-XE
  • Cisco IOS-XR
  • Junos
  • Cisco NX-OS
  • PAN-OS
$pip install "netmiko>=4.0" pyyaml
terminal

Tags

traceroutepathtroubleshootingfirewallhsrpcdplldputilizationpacket-loss