All scripts
isp
Advanced
2–6 min
T-ISP-021 · Customer Prefix Validation
Validate customer-advertised prefixes against the agreed allow-list and IRR/RPKI: detect bogons, unexpected/more-specific prefixes, and AS-origin mismatches before they reach the route policy.
Cisco IOS-XR
Cisco IOS/XE
Juniper Junos
You're viewing a preview
The full script, parameters, and execution console are available with a free account.
Already have access? Sign in →
Capabilities
- Allow-list enforcement
- Bogon/private detection
- More-specific detection
- AS-origin check
- IRR/RPKI hint
- JSON report
Required inputs
Parameters the script accepts. Defaults shown; some are vendor- or context-gated.
| Parameter | Type | Default | Notes |
|---|---|---|---|
Max prefixes max_prefixes | number | 100 | — |
Strict mode (reject extras) strict | string | true | — |
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 14:00:00 INFO Customer ACME: 42 received prefixes, 40 allow-listed 2026-06-15 14:00:00 WARN Unexpected prefix 203.0.113.0/24 (not in allow-list) 2026-06-15 14:00:00 WARN Bogon detected: 10.0.0.0/8 2026-06-15 14:00:00 INFO Report written to prefix-validation.json (2 violations)