Skip to main content
Agent skill

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.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Network Bgp Diagnostics when an AI agent needs a reusable SKILL.md workflow for this job: 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.

When not to use it

Skip Network Bgp Diagnostics when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/network-bgp-diagnostics
# Save SKILL.md to ~/.claude/skills/network-bgp-diagnostics/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/network-bgp-diagnostics/SKILL.md. For a shared project, commit the folder at .claude/skills/network-bgp-diagnostics/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Network Bgp Diagnostics skill for this task: BGP neighbors are stuck in Idle, Connect, Active, OpenSent, or OpenConfirm. Confirm any required inputs or files before making changes.

What supports this recommendation?

83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
92/100
Practical detail
92/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# 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 show ip prefix-list show route-map ```

Use platform-specific address-family commands when the device uses VRFs, IPv6, VPNv4, or EVPN. Do not assume global IPv4 unicast.

## State Interpretation

| State | First checks | | --- | --- | | Established with prefix count | Route exchange is up; inspect policy and table selection | | Established with zero prefixes | Check inbound policy, max-prefix, advertised routes, and AFI/SAFI | | Active | TCP session is not completing; check routing, source, ACLs, and peer reachability | | Connect | TCP connection is in progress; check path and remote listener | | OpenSent/OpenConfirm | TCP works; check ASN, authentication, timers, capabilities, and logs | | Idle | Neighbor may be disabled, missing config, blocked by policy, or backoff timer |

## Transport Checks

```text ping <peer> source <local-source> traceroute <peer> source <local-source> show ip route <peer> show bgp neighbors <peer> | include BGP state|Last reset|Local host|Foreign host ```

If the peer is sourced from a loopback, confirm both directions route to the loopback addresses and that the neighbor config uses the expected update source.

Avoid disabling ACLs or firewall policy as a diagnostic shortcut. Read hit counters, logs, and path state first.

## Route Policy Checks

```text show bgp neighbors <peer> advertised-routes show bgp neighbors <peer> routes show ip prefix-list <name> show route-map <name> show bgp <prefix> ```

Some platforms require additional configuration before `received-routes` is available. Do not add that configuration during incident triage unless the operator approves the change.

## AS Path And Prefix Review

```text show bgp regexp _65001_ show bgp regexp ^65001$ show bgp <prefix> show bgp neighbors <peer> advertised-routes | include Network|Path|<prefix> ```

Use AS-path regex carefully. `_65001_` matches AS 65001 as a token. Plain `65001` can match longer ASNs or unrelated text.

## Parser Pattern

```python import re from typing import Any

BGP_SUMMARY_RE = re.compile( r"^(?P<neighbor>\d{1,3}(?:\.\d{1,3}){3})\s+" r"(?P<version>\d+)\s+" r"(?P<remote_as>\d+)\s+" r"(?P<msg_rcvd>\d+)\s+" r"(?P<msg_sent>\d+)\s+" r"(?P<table_version>\d+)\s+" r"(?P<input_queue>\d+)\s+" r"(?P<output_queue>\d+)\s+" r"(?P<uptime>\S+)\s+" r"(?P<state_or_prefixes>\S+)$", re.M, )

def parse_bgp_summary(raw: str) -> list[dict[str, Any]]: rows = [] for match in BGP_SUMMARY_RE.finditer(raw): state_or_prefixes = match.group("state_or_prefixes") if state_or_prefixes.isdigit(): state = "Established" prefixes_received = int(state_or_prefixes) else: state = state_or_prefixes prefixes_received = None rows.append({ "neighbor": match.group("neighbor"), "remote_as": int(match.group("remote_as")), "state": state, "prefixes_received": prefixes_received, "uptime": match.group("uptime"), }) return rows ```

Prefer structured parser output when available, but store raw output with the incident record because BGP summary formats vary by platform and address family.

## Change-Window Only

These actions can affect routing and should not be suggested as automatic diagnostics:

- Clearing a BGP session. - Changing neighbor authentication, timers, update source, route-maps, or prefix-lists. - Enabling additional received-route storage. - Relaxing firewall, ACL, or control-plane policy.

If a reset is approved, prefer the least disruptive soft or route-refresh option supported by the platform and document exactly why it is safe.

## Anti-Patterns

- Assuming `Active` always means the remote side is down. - Ignoring VRF, address family, or update-source differences. - Using broad AS-path regex without token boundaries. - Hard-resetting a peer before reading last reset reason and logs. - Treating missing `received-routes` output as proof that no routes arrived.

## See Also

- Skill: `cisco-ios-patterns` - Skill: `network-config-validation` - Skill: `network-interface-health`

Intended uses

  • 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
  • You need before/after evidence for a BGP change.
  • You are reviewing automation that parses BGP summary output.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.