network-bgp-diagnostics
Diagnostics-only BGP troubleshooting patterns for neighbor state, route exchange, prefix policy, AS path inspection, and safe evidence collection. Use when a BGP neighbor is down, routes are missing, or prefix policy and AS path need inspection.
- Kind
- Skill
- Works with
- Claude Code, Codex
- Source
- affaan-m/ECC @ d3b8a3e90890
- Path
- skills/network-bgp-diagnostics/SKILL.md
- License
- MIT
- Jobs
- Debugging, Guardrails
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# 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 1. Identify the exact neighbor, address family, VRF, and local/remote ASNs. 2. Capture summary state and last reset reason. 3. Prove reachability to the peer source address. 4. Check route policy references before assuming transport failure. 5. Compare advertised, received, and installed routes where the platform supports those commands. ```text show bgp summary show bgp neighbors <peer> show ip route <peer> show tcp brief | include <peer>|:179 show logging | include BGP|<peer> show running-config | section router bgp …