! ============================================================================ ! 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 distribute link-state ! ! --- Part B: BGP address-family link-state link-state (global) -------------- router bgp 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 neighbor address-family link-state link-state ! ! neighbor 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