From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pdm-devel@lists.proxmox.com
Subject: [pdm-devel] [PATCH proxmox-datacenter-manager 1/1] docs: add section on evpn status panel
Date: Wed, 3 Dec 2025 14:54:22 +0100 [thread overview]
Message-ID: <20251203135423.402705-1-s.hanreich@proxmox.com> (raw)
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
docs/sdn-integration.rst | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/docs/sdn-integration.rst b/docs/sdn-integration.rst
index 5dcfe373..131e6221 100644
--- a/docs/sdn-integration.rst
+++ b/docs/sdn-integration.rst
@@ -82,3 +82,29 @@ It contains the following columns:
* VNI: The L3VNI (for zones) or L2VNI (for vnets)
* Zone: The name of the zone that contains the vnet
* Remote: The name of the remote that contains the zone (and therefore vnet).
+
+
+Status Panel
+''''''''''''
+
+Selecting a zone or vnet shows the current status of the IP-VRF / MAC-VRF for the selected zone /
+vnet on a given node. The node can be selected via the dropdown in the EVPN status panel.
+
+For zones it shows the contents of the IP-VRF, as seen by the kernel. This means that routes for
+guests located on the note do not show up in the IP-VRF status, since they are handled by the
+connected route for the subnet. For vnets it shows the type 2 routes, as learned via BGP, so all
+guests are included in this view.
+
+The following properties are shown for entries in the zone:
+
+* Destination: The CIDR of the destination for this routing table entry
+* Nexthops: The nexthops for this route, for vnets this is usually the local bridge - for
+ externally learned routes (e.g. default routes) the IP of the next hop
+* Protocol: The protocol via which this routes was learned
+* Metric: The metric (or cost) of a route, lower cost routes are preferred over higher cost routes
+
+The following properties are shown for entries in the vnet:
+
+* IP Address: The IP-Address from the type-2 route
+* MAC Address: The MAC-Address from the type-2 route
+* via: The nexthop for the type-2 route
--
2.47.3
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next reply other threads:[~2025-12-03 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 13:54 Stefan Hanreich [this message]
2025-12-03 14:28 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251203135423.402705-1-s.hanreich@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=pdm-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox