VRF / MPLS Integrity Checker

MPLS/VPN integrity: VRF route-target consistency, LDP/RSVP label binding verification, PE-CE routing check, VPLS MAC learning, traffic-engineered tunnel state, and end-to-end L3VPN reachability.

Cisco IOS/XE/XR

Juniper MPLS

Nokia SR-OS

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

VRF RT import/export audit
LDP label binding check
LSP path verification
PE-CE routing verify
VPLS MAC learn audit
TE tunnel state & BW
L3VPN end-to-end ping

Required inputs

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

Parameter	Type	Default	Notes
VRF names to check (CSV) vrf_list	string	CUST-A,CUST-B	—
Verify LDP bindings check_ldp	bool	true	—
Check TE tunnels check_te	bool	true	—
PE router list (CSV) pe_list	string	—	—

Hint 1 — Name your vendors and OS versions

Mention the exact platforms you run (Cisco IOS/XE/XR, Juniper MPLS, Nokia SR-OS) so the generated analysis logic uses the right CLI/NETCONF syntax.

Hint 2 — State your real thresholds

Provide concrete values for VRF names to check (CSV), Verify LDP bindings, Check TE tunnels instead of the defaults — they shape what counts as a fault.

Hint 3 — Prioritize the checks you need

This tool can vRF RT import/export audit and lDP label binding check. 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.

l3vpn.yaml

yaml

4 customer VRFs (hub-and-spoke + DR) with RT/RD plan and expected route counts

yaml

# L3VPN customers (RT/RD plan) — verified end-to-end across PEs
asn: 65000
rd_format: "65000:{vrf_id}"
vrfs:

Expected output

Reference terminal output the script should produce — used as a stylistic and structural target.

terminal

VRF / MPLS INTEGRITY CHECK
━━━━━━━━━━━━━━━━━━━━━━━━━━━

VRF ROUTE-TARGET AUDIT:
  VRF CUST-A (RT export: 65001:100, import: 65001:100)
    pe-rtr-01: export=65001:100 import=65001:100  ✓ consistent
    pe-rtr-02: export=65001:100 import=65001:200  ← MISMATCH!
      Impact: CUST-A routes on pe-rtr-02 not being imported correctly
      Fix: 'route-target import 65001:100' under vrf CUST-A on pe-rtr-02