sam
0c91cad55f
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>
52 lines
1.9 KiB
INI
52 lines
1.9 KiB
INI
! ============================================================================
|
|
! 02-bgp-ls.cfg -- BGP-LS export of the IGP topology to the collector
|
|
! ============================================================================
|
|
! Feeds the OBMP-LinkState dashboards (ls_nodes, ls_links, ls_prefixes,
|
|
! LS Topology map). Enable on every router that runs IS-IS in the domain
|
|
! you want visualized; typically only the RRs need to actually SEND the
|
|
! link-state AF to the collector, but any router can distribute its local
|
|
! IGP database into BGP-LS.
|
|
!
|
|
! Three-part configuration:
|
|
! Part A: tell IS-IS to distribute the LSDB into BGP-LS.
|
|
! Part B: enable the link-state address-family in BGP globally.
|
|
! Part C: activate the link-state AF toward the collector's RR peers.
|
|
!
|
|
! Apply after 01-bmp-basic.cfg.
|
|
! ============================================================================
|
|
|
|
! --- Part A: IS-IS distribute link-state ------------------------------------
|
|
router isis <ISIS_INSTANCE>
|
|
distribute link-state
|
|
!
|
|
|
|
! --- Part B: BGP address-family link-state link-state (global) --------------
|
|
router bgp <LOCAL_ASN>
|
|
address-family link-state link-state
|
|
!
|
|
!
|
|
|
|
! --- Part C: activate LS AF per-neighbor (toward the RRs) -------------------
|
|
! On a client router, activate LS toward the two RRs. On an RR, activate
|
|
! toward its peer RR (and toward the collector's own BGP peer if present).
|
|
router bgp <LOCAL_ASN>
|
|
neighbor <RR_LOOPBACK_1>
|
|
address-family link-state link-state
|
|
!
|
|
!
|
|
neighbor <RR_LOOPBACK_2>
|
|
address-family link-state link-state
|
|
!
|
|
!
|
|
!
|
|
|
|
! --- Verify -----------------------------------------------------------------
|
|
! show isis database detail
|
|
! show bgp link-state link-state summary
|
|
! show bgp link-state link-state
|
|
!
|
|
! On the stack side:
|
|
! docker exec -i obmp-psql psql -U openbmp -d openbmp \
|
|
! -c "SELECT protocol, count(*) FROM ls_nodes GROUP BY protocol;"
|
|
! Grafana -> OBMP-LinkState -> LS Topology / LS Nodes
|