From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 1F8DF1FF13F for ; Thu, 23 Apr 2026 16:03:01 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D358F1AAFB; Thu, 23 Apr 2026 16:02:27 +0200 (CEST) From: Hannes Laimer To: pve-devel@lists.proxmox.com Subject: [PATCH pve-docs v3 8/8] sdn: add bgp fabric section Date: Thu, 23 Apr 2026 16:02:14 +0200 Message-ID: <20260423140214.187001-9-h.laimer@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260423140214.187001-1-h.laimer@proxmox.com> References: <20260423140214.187001-1-h.laimer@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1776952847376 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.081 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: 25VCSYXL6IGM2GPVXJJQ446W6XQI3NLT X-Message-ID-Hash: 25VCSYXL6IGM2GPVXJJQ446W6XQI3NLT X-MailFrom: h.laimer@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --- pvesdn.adoc | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 81 insertions(+) diff --git a/pvesdn.adoc b/pvesdn.adoc index 8f955e8..27a9d75 100644 --- a/pvesdn.adoc +++ b/pvesdn.adoc @@ -835,6 +835,87 @@ NOTE: The dummy interface will automatically be configured as `passive`. Every interface which doesn't have an ip-address configured will be treated as a `point-to-point` link. +[[pvesdn_bgp]] +BGP +~~~ + +BGP (Border Gateway Protocol) can be used as an eBGP unnumbered fabric. Each +node has its own Autonomous System Number (ASN) and peers with its neighbors +over physical interfaces without requiring IP addresses on the fabric links. + +Configuration options: + +[[pvesdn_bgp_fabric]] +On the Fabric +^^^^^^^^^^^^^ + +IPv4 Prefix:: Optional IPv4 CIDR network range (e.g., 192.0.2.0/24) used to +verify that all router-IDs in the fabric are contained within this prefix. + +IPv6 Prefix:: Optional IPv6 CIDR network range (e.g., 2001:db8::/64) used to +verify that all node IPv6 addresses in the fabric are contained within this +prefix. + +BFD:: Enable Bidirectional Forwarding Detection on all peering sessions in this +fabric. BFD provides fast failure detection for links between nodes. + +NOTE: If neither prefix is configured, each node must specify an explicit +Router ID instead. This is useful when the loopback addresses are already +managed by another fabric running on the same nodes. + +[[pvesdn_bgp_node]] +On the Node +^^^^^^^^^^^ + +Options that are available on every node that is part of a fabric: + +Node:: Select the node which will be added to the fabric. Only nodes that +are currently in the cluster will be shown. + +ASN:: BGP Autonomous System Number for this node. It is recommended to use +private ASN numbers (64512-65534 for 16-bit, 4200000000-4294967294 for 32-bit). + +IPv4:: A unique IPv4 address for this node, also used as the BGP router-id. +Required when the fabric has an IPv4 prefix configured; each node in the same +fabric must have a different address. + +IPv6:: IPv6 address for dual-stack fabrics. If only an IPv6 address is +configured (without an IPv4 address), the BGP router-id is automatically +derived from it via a FNV-1a hash. + +Router ID:: Explicit BGP router-id for this node. Required when the fabric +has no prefix configured; otherwise takes precedence over the router-id +derived from the IPv4/IPv6 address. + +Interfaces:: Specify the interfaces used to establish peering connections with +other BGP nodes. These interfaces run BGP unnumbered (no IP address assignment +needed). When a node IP is configured, a dummy "loopback" interface is +automatically created with that IP. + +NOTE: Unlike OSPF and OpenFabric, BGP unnumbered interfaces do not need IP +addresses. Peering is established using IPv6 link-local addresses automatically. + +NOTE: In an eBGP unnumbered fabric, directly peering nodes must have different +ASNs for BGP sessions to establish. + +[[pvesdn_bgp_evpn]] +Using BGP Fabrics with EVPN +^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +When configuring an EVPN controller, a BGP fabric can be selected as the +underlay instead of manually specifying peer addresses. The EVPN overlay +sessions will run as iBGP, using the EVPN controller's ASN for the router +process. The per-node fabric ASN is automatically applied via `local-as` on +the underlay neighbor group. + +This means the EVPN controller ASN and the per-node fabric ASNs should be +different. For example, with three nodes using ASNs 65001, 65002, and 65003 +for the underlay, the EVPN controller could use ASN 65000 for the overlay. + +NOTE: Using a BGP fabric for an EVPN underlay requires the fabric to have a +prefix and each node to have an IP configured, since EVPN uses the node IP +as the VTEP address. + [[pvesdn_config_ipam]] IPAM ---- -- 2.47.3