bgp aigp

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

Accumulated IGP metric (RFC 7311). Full attribute support: capability negotiation, wire encoding/decoding, and structured JSON exposure. The AIGP metric is parsed and included in event output.

Category

Capabilities.

Configuration

plugin {
    external aigp { use bgp-aigp; encoder json; }
}

bgp {
    peer upstream {
        capability {
            aigp;
        }
    }
}

Behaviour

The plugin enables AIGP capability negotiation and encodes and decodes the AIGP attribute on the wire. Routes that carry AIGP are parsed into their structured form and the metric is exposed on the JSON event envelope. RFC 4271 attribute flags are included in Ze's native JSON output for full protocol transparency.

What is not implemented: AIGP is not consumed in Ze's best-path selection. RFC 7311 requires the AIGP metric to be considered before MED in some deployments; that step is not in Ze. If your deployment depends on AIGP-driven best-path selection, Ze is not the answer.

Interactions

• bgp-rib receives the parsed AIGP metric on every UPDATE but does not use it in best-path.

Source

main/internal/component/bgp/plugins/aigp/