T-ISP-002 · BGP Community Policy Enforcer

Audit and enforce a canonical BGP community policy (RFC 8642-style action communities, no-export/no-advertise hygiene, and customer signalling) against live route-policy configuration.

Cisco IOS-XR

Juniper Junos

Arista EOS

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

Canonical community catalog
Drift detection vs intent
No-export hygiene checks
Customer signalling validation
Auto-remediation snippets
JSON + human report

Required inputs

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

Parameter	Type	Default	Notes
Policy YAML path policy_file	string	communities.yaml	—
Emit fix config remediate	bool	true	—

Hint 1 — Name your vendors and OS versions

Mention the exact platforms you run (Cisco IOS-XR, Juniper Junos, Arista EOS) so the generated isp & peering logic uses the right CLI/NETCONF syntax.

Hint 2 — State your real thresholds

Provide concrete values for Policy YAML path, Emit fix config instead of the defaults — they shape what counts as a fault.

Hint 3 — Prioritize the checks you need

This tool can canonical community catalog and drift detection vs intent. 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

2026-06-15 10:01:11 INFO  Loaded 18 canonical communities
2026-06-15 10:01:12 WARN  edge-rtr-02: missing 65010:666 (blackhole) tag mapping
2026-06-15 10:01:12 WARN  edge-rtr-02: customer prefix not tagged 65010:1001
2026-06-15 10:01:12 INFO  2 violations · remediation written to fix-edge-rtr-02.txt