Review findings from verifying the router-blueprints drop against the
deployed stack:
- router-blueprints/README.md linked docs/router-config-guide.md, which
does not exist -- the guide is docs/router-integration.md
- router-integration.md still advised --router-port 5000 for lab routers;
1790 is the standard now, the note points at re-applying via
cml/proxmox_bmp_config.py instead
- verify sections referenced Grafana paths that don't exist in the
provisioned UI: 'Base-1001 -> Peers Table' -> Inventory / Peer Detail,
and folder 'OBMP-Learning' -> OBMP-Reference
- role-route-reflector.cfg: loud caveat block on next-hop-self -- it only
rewrites eBGP-learned/local routes (what this lab wants); reflected
iBGP routes need 'ibgp policy out enforce-modifications', so on a pure
RR the line is a silent no-op
- cml/xrd-node-definition.yaml BMP timers synced to the blueprint values
(initial-delay 60, refresh 60/30, drop flapping-delay) per the
keep-hand-config-and-automation-in-sync rule
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The stack side is portable; the router side had no reference material -- a
new operator standing up OBMP has no guide for what to configure on their
devices to feed it. Adds two artifacts, both vendor-neutral in intent,
IOS-XR-specific in syntax:
docs/router-integration.md
Multi-path tour of the four ingest paths (BMP, BGP-LS, gNMI,
NETCONF) with a bring-up checklist and cross-references. The BMP
section is deliberately thin -- it hands off to docs/router-bmp-config.md
for the address-selection, port-choice, and RR-scope activation
detail already covered there.
router-blueprints/iosxr/*.cfg
Copy-paste config fragments, one per ingest path plus a
role-route-reflector overlay. All values are <PLACEHOLDER>
substitutions -- no hardcoded IPs, no lab-gear names. Fragments
align to the ROUTER_FACING_IP / ROUTER_FACING_PORT convention
introduced in docs/router-bmp-config.md.
router-blueprints/README.md
Substitution legend + layout, cross-links to PORTABILITY-FINDINGS.md
finding 4 (why routers can't target HOST_IP on WSL).
Also appends the multi-path guide link to the Greenfield deploy section
in README.md so router-side integration is discoverable from the top.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
