Skip to content

v2.69

Choose a tag to compare

View all tags
@Vadims06 Vadims06 released this 31 Aug 21:14
· 4 commits to master since this release
v2.69
ec6de54

Topolograph Release Notes v2.69

BGP Topology Integration

Topolograph now ingests BGP control-plane data from BMP Watcher, alongside
existing OSPF and IS-IS topology data:

  • BGP graph and topology overlay. BGP sessions are shown on the existing
    network graph as their own layer, toggled independently from IGP topology
    and LSPs. A BGP graph can also stand alone when no IGP topology is
    available for the same devices. Route reflectors are labeled where the
    collected data identifies them.
  • Automatic binding to IGP topology. A BGP graph is automatically matched
    to the OSPF or IS-IS graph(s) that share its routers, including
    multi-domain networks where BGP bridges two separate IGP domains. An
    ambiguous or incomplete match is left for manual confirmation instead of
    being guessed.
  • VRF inventory. Detected VRF names, route distinguishers, and import/
    export route targets are shown on the node card and in the BGP route
    table.
  • BGP route search. IPv4, IPv6, VPNv4, and VPNv6 routes can be searched
    by exact prefix, containment, or longest-prefix match, with filters for
    VRF, route distinguisher, route target, community, and evidence level
    (pre-policy, post-policy, or best path). Large route tables page through
    results instead of loading everything at once, and can be re-sorted by
    clicking a column header — address and prefix columns order by numeric
    value, not as text.
  • Route Lookup with BGP awareness. The existing path-lookup tool now
    considers static, OSPF, IS-IS, and BGP candidates together, selects the
    correct route by longest-prefix match and administrative distance, and
    resolves the resulting path — including recursive BGP next hops and
    eligible LSP shortcuts.
  • BGP change history. Session up/down events and route churn appear on
    the existing monitoring timeline, and BGP state can be compared between
    two points in time or between two collector sessions, the same way IGP
    graphs are already compared.

End-to-end collection

BMP Watcher sends BGP topology snapshots and events straight to Topolograph.
It attaches the API token on every request (--topolograph-api-token, or
TOPOLOGRAPH_API_TOKEN in the environment), the same token-based
authentication the OSPF and IS-IS watchers use. The Fluent Bit event shipper
carries the same header.

Upgrade

BGP route tables collected before this release cannot yet be sorted by
prefix, next hop, or peer address — that ordering stays inactive on those
graphs until a one-time backfill fills in the sort keys. Run once after
upgrading:

python scripts/backfill_route_sort_keys.py --apply

Route data collected after the upgrade is sortable immediately. Sorting by
AFI, SAFI, prefix length, local preference, or MED works without the
backfill.

Screenshots

BGP sessions overlay the IGP graph; each feed's observed RIB view is kept
separate.

BGP sessions

The graph-wide BGP route table filters by prefix, RD, RT, community, AFI/SAFI,
peer, next hop and evidence level (pre-policy / post-policy / Loc-RIB).

BGP routes

A router's device form lists its routes and the RIB breakdown behind them.

Route view on the node card

Best-path selection: Route resolution names the attribute that decided the
winner and the next hop it selected.

Best-path selection

Route Lookup shows the hand-off explicitly: BGP chooses the route, OSPF
supplies reachability to the selected BGP next hop.

BGP next hop resolved through OSPF

Compare evaluates BGP route state at two instants: added, withdrawn or changed,
with before/after attributes.

Route-state comparison

Full walkthrough on the demo topology: /how-to/bgp.

Vendor Support

LSDB parsing added for three more platforms.

OSPFv3

Vendor Command
IP Infusion OcNOS show ipv6 ospf database router / network / external / intra-prefix
Fortinet FortiOS get router info6 ospf database router / network / external / intra-prefix
MikroTik RouterOS /routing/ospf/lsa/print detail without-paging where instance=v3

For OcNOS and FortiOS the per-LSA-type forms are required (the bare
show ipv6 ospf database form is an index table only), and intra-prefix is
mandatory: OSPFv3 carries prefixes only in that LSA.

IS-IS

Vendor Command
IP Infusion OcNOS show isis database verbose (use verbose, not detail; only verbose prints the TE sub-TLVs)
Fortinet FortiOS get router info isis database detail

docs/VENDORS.md has the full per-vendor notes.

Scale

BGP route search, graph-to-topology binding and event ingestion are built to
handle large route tables (100,000+ routes) and many stored graphs.

Compatibility

Component Minimum version
Topolograph v2.69
OSPF Watcher No version requirement
IS-IS Watcher No version requirement
BMP Watcher Build with --topolograph-api-token (bmpwatcher after v1.0.0)
Assets 2
Loading