Network Bgp Diagnostics

This is a read-only BGP troubleshooting workflow that walks you through neighbor state checks, transport verification, and route policy inspection without touching session resets or config changes during triage. It covers the standard states (Idle, Active, OpenSent, Established), gives you the show commands to run on Cisco-style boxes, and includes a Python regex parser for BGP summary output. The anti-patterns section is honest about common mistakes like assuming Active always means the remote side is down or ignoring VRF and address family context. Use this when a session is flapping or established but missing prefixes, and you need to collect evidence before opening a change window.

skills.sh installs: 5.4K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill network-bgp-diagnostics --agent claude-code

Installs into .claude/skills of the current project.

Files

Network BGP Diagnostics

Use this skill when a BGP session is down, flapping, established with missing routes, or advertising unexpected prefixes. The default workflow is read-only evidence collection; policy and reset actions belong in a reviewed change window.

When to Use

BGP neighbors are stuck in Idle, Connect, Active, OpenSent, or OpenConfirm.
A session is Established but expected prefixes are missing.
A route-map, prefix-list, max-prefix limit, or AS path policy may be filtering routes.
You need before/after evidence for a BGP change.
You are reviewing automation that parses BGP summary output.

Read-Only Triage Flow

Identify the exact neighbor, address family, VRF, and local/remote ASNs.
Capture summary state and last reset reason.
Prove reachability to the peer source address.
Check route policy references before assuming transport failure.
Compare advertised, received, and installed routes where the platform supports those commands.

SKILL.md on GitHub