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>
65fd88a0a2