
Proxmox VE 9.2 SDN Audit Checklist Before VM Migration
Move VMs only after you know which VLAN, VXLAN, firewall, and DNS settings actually apply to each Proxmox zone.
Page 2 of 22 — showing Proxmox VE articles 13–24 of 253.

Move VMs only after you know which VLAN, VXLAN, firewall, and DNS settings actually apply to each Proxmox zone.

Three default OCI LXC settings can break DNS, firewall, and backups before your first production request hits service.

Compare Datacenter Manager inventory with live Proxmox API and SSH checks before automation to prevent wrong installs.

A timestamped text export turns Proxmox SDN state into a diffable restore point before risky cluster changes.

Empty SDN zones are the safest moment to lock down traffic, because renumbering VLANs under live VMs is painful.

New SDN interfaces can bypass old bridge rules, so audit Proxmox VE 9.2 zones before cross-tenant traffic slips through.

Turn a small PBS node into a repeatable offsite backup target for VMs and containers, then prove restores work.

A backup success flag can hide a broken restore path, so this test proves Proxmox S3 recovery boots and verifies data.

Isolation beats exposure: verify blocked sources, pin DNS, and prove the firewall before you open the container.

A dead node need not mean a dead container; a spare node can take over with a verified restore and Docker check.

A ten-minute host audit can stop VMs from inheriting broken bridges, missing VLAN tags, and open management ports.

A single PBS snapshot captures the whole Home Assistant container, so a failed node does not erase your automations.