Skip to content

bgp nlri ls

Thomas Mangin edited this page May 30, 2026 · 4 revisions

Pre-Alpha. This page describes behavior that may change.

BGP Link-State (RFC 7752) and its VPN variant. Decode-only: Ze parses received BGP-LS NLRI. Encoding is not implemented.

Category

Address families.

Configuration

plugin {
    internal nlri-ls { use bgp-nlri-ls }
}

bgp {
    peer bgpls-collector {
        family {
            bgp-ls/bgp-ls     { prefix { maximum 100000; } }
            bgp-ls/bgp-ls-vpn { prefix { maximum 100000; } }
        }
    }
}

Behaviour

The plugin decodes BGP-LS NLRI (AFI 16388, SAFI 71 and 72), covering node, link, and prefix types with 40 TLV decoders. Received BGP-LS routes are surfaced through the event stream as structured JSON, which is useful for building topology visualisers, traffic-engineering controllers, and route analytics.

Encoding is not implemented. Ze cannot send BGP-LS routes. If you need to originate BGP-LS updates, Ze is not the answer.

Interactions

  • Decode-only. bgp-rib stores the parsed NLRI but does not run best-path selection on BGP-LS.
  • Pairs with external analytics tools that subscribe to the event stream.

Source

main/internal/component/bgp/plugins/nlri/ls/

Home

About

First Steps

Configuration

Operation

Interfaces

Plugins

Plugin Development

Chaos Testing

Blueprints

Development

Reference

Clone this wiki locally