From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 084DA1FF0AA for ; Tue, 03 Nov 2026 19:57:37 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 81FFF216DD; Tue, 03 Nov 2026 19:56:50 +0100 (CET) From: Hannes Laimer To: pve-devel@lists.proxmox.com Subject: [PATCH pve-docs v4 13/13] sdn: ipam: document zone namespaces in NetBox and phpIPAM Date: Tue, 3 Nov 2026 19:55:59 +0100 Message-ID: <20261103185559.420277-14-h.laimer@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261103185559.420277-1-h.laimer@proxmox.com> References: <20261103185559.420277-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: 1793732179169 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.319 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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: DJ7TWE3RBDJAW5MDMWHERBM23M46VVM3 X-Message-ID-Hash: DJ7TWE3RBDJAW5MDMWHERBM23M46VVM3 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: Signed-off-by: Hannes Laimer --- pvesdn.adoc | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/pvesdn.adoc b/pvesdn.adoc index c85d86a48112..0cd1b938528d 100644 --- a/pvesdn.adoc +++ b/pvesdn.adoc @@ -1287,6 +1287,22 @@ Fingerprint:: The SHA-256 fingerprint of the NetBox API. Can be retrieved with `openssl x509 -in /etc/ssl/certs/netbox.crt -noout -fingerprint -sha256` when using the default certificate. +With the `zone-namespaces` option of the IPAM entry turned on, {pve} creates a +VRF named `pve-` for every zone, together with the first subnet of the +zone, and keeps the prefixes of the zone's subnets in it. This way two zones can +use the same subnet. The option is off by default and meant to be turned on once +every node runs a version that knows the VRFs, since a node that does not puts +an explicit mapping into the global table. Clusters sharing one NetBox set a +`zone-namespace-prefix` of their own, the names start with `pve` by default. The +IP addresses allocated in a prefix carry the MAC address of the guest in their +description. Prefixes created in the global table, by earlier versions or with +the option off, are still found there and can be moved into the VRF of their +zone, together with their IP addresses and IP ranges. A zone gets its VRF only +with the next subnet added to it, so to move prefixes into it earlier, create +the VRF `pve-` by hand. With the option on, creating a subnet whose range +the global table still holds is refused, since a prefix in the VRF would hide +the addresses recorded in the old one, so move or remove that prefix first. + [[pvesdn_ipam_plugin_phpipam]] phpIPAM Plugin @@ -1304,6 +1320,23 @@ Token:: An API access token Section:: An integer ID. Sections are a group of subnets in phpIPAM. Default installations use `sectionid=1` for customers. +With the `zone-namespaces` option of the IPAM entry turned on, {pve} creates a +sub-section named `pve-` under the configured section for every zone, +together with the first subnet of the zone, and keeps the zone's subnets in it. +This way two zones can use the same subnet. The option is off by default and +meant to be turned on once every node runs a version that knows the +sub-sections. phpIPAM nests sections one level deep, so a configured section +that is itself a sub-section gets no sub-sections and the subnets of all zones +stay in it. Section names are global in phpIPAM, so clusters sharing one set a +`zone-namespace-prefix` of their own, the names start with `pve` by default. +Subnets created in the configured section itself, by earlier versions or with +the option off, are still found there and can be moved into the sub-section of +their zone. A zone gets its sub-section only with the next subnet added to it, +so to move subnets into it earlier, create the sub-section under the configured +section by hand. With the option on, creating a subnet whose range the +configured section still holds is refused, since a copy in the sub-section would +hide the addresses recorded in the old one, so move or remove that subnet first. + [[pvesdn_config_dns]] DNS -- 2.47.3