dohertj2/network
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
5e384f23f91ba5b5775e8a341801aa50b5d9a673
network/esxi.md
T
dohertj2 14cc4faa28 Delete the Plex VM disks 
Completes section 9 step 3. govc vm.destroy Plex removed the inventory
entry and the [NVME_1] Plex/ folder; datastore free space went
1,619.8 -> 1,756.1 GB (+136.3 GB). 10.100.0.24 / 10.50.0.31 and MACs
00:0c:29:4a:ef:3d / 00:0c:29:4a:ef:47 are now free for reuse.

Done on 2026-09-17 rather than the planned ~2026-10-15. Checking the
plan's own Veeam precondition inverted its assumption: the Backup VMs
job has EnableDeletedVmDataRetention set to False with Simple retention
of 7 restore points, so a VM removed from the job has its points pruned
as the remaining VMs roll the chain - Plex's are due to age out around
2026-09-24, about three weeks before the disks were scheduled for
deletion. Deleting while a good restore point still existed (2026-09-17
03:01, consistent) was safer than deleting later with none.

Recovery position is now: Veeam image restore until ~2026-09-24, then
only the pre-migration library DB at
/mnt/share/backups/plex-migration-2026-09-16/, which rebuilds a Plex
install but not the VM.

veeam.md gains the retention gotcha, since it applies to any future
decommission and the 30-day DeletedVmsDataRetentionPeriodDays value is
misleading while the toggle is off.

Also flags in esxi.md that its VM tables are incomplete: the host has 10
VMs, WW_DEV_VM / Rockwell_Win10 / TCBSD are absent, and DevVM is powered
off rather than on. Left the tables themselves alone as out of scope.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-17 12:12:20 -04:00

4.9 KiB
Raw Blame History

ESXi Host

Access

  • IP: 10.2.0.12 (VLAN 0 / DEFAULT, management)
  • Version: VMware ESXi 8.0.3 build-24280767 (Update 3, Patch 35)
  • Credentials: govc / Tn9.xKw-m4Vp (Administrator role)
  • API access via govc: 
    GOVC_URL=https://10.2.0.12/sdk GOVC_USERNAME=govc GOVC_PASSWORD='Tn9.xKw-m4Vp' GOVC_INSECURE=true govc <command>
  • Do NOT use SSH — ESXi keyboard-interactive auth is unreliable from this machine; use govc exclusively
  • Hardware: HP, 2x Intel Xeon E5-2697 v4 (36 logical CPUs @ 2.3GHz), 256GB RAM
  • Boot time: 2025-09-22

Physical NICs

NIC Driver Speed Link MTU MAC Description
vmnic0 igbn — Down 1500 ec:b1:d7:82:3b:40 Intel 1Gb 2-port 361i
vmnic2 ixgben — Down (admin down) 1500 48:df:37:07:a9:6c Intel 82599 10GbE
vmnic3 ixgben 10 Gbps Up 1500 48:df:37:07:a9:6d Intel 82599 10GbE
vmnic4 nmlx5_core 25 Gbps Up 1500 b8:83:03:60:e4:e0 Mellanox ConnectX-4 Lx
vmnic5 nmlx5_core 25 Gbps Up 9000 b8:83:03:60:e4:e1 Mellanox ConnectX-4 Lx

Active uplinks: vmnic3 (unused — no vSwitch), vmnic4 (vSwitch0), vmnic5 (jumboFrameSwitch)

vSwitches

vSwitch0 (vmnic4 — 25Gbps Mellanox, MTU 1500)

Carries VLAN-tagged traffic for management, LAN, IoT, and guest networks.

Port Group VLAN ID Active Ports Subnet
DEFAULT_0 0 (untagged) 1 10.2.0.0/24 (ESXi mgmt)
MGMT_1 0 (untagged) 0 —
GUEST_3 3 0 —
LAN_100 100 6 10.100.0.0/24
IOT_200 200 1 10.200.0.0/24

jumboFrameSwitch (vmnic5 — 25Gbps Mellanox, MTU 9000)

Dedicated storage network with jumbo frames. Switch port 32 is configured as a trunk (forward=all, MGMT native) so VLAN 50 frames arrive tagged, matching the DATA_50 port group's VLAN ID.

Port Group VLAN ID Active Ports Subnet
DATA_50 50 3 10.50.0.0/24

All port groups: promiscuous mode=No, forged transmits=No, MAC changes=No.

VMkernel Interface

Interface IP Netmask Portgroup MAC Stack
vmk0 10.2.0.12 255.255.255.0 DEFAULT_0 48:df:37:07:a9:6d defaultTcpipStack
  • Default gateway: 10.2.0.1
  • DNS search: localdomain (no DNS servers configured)

Virtual Machines

Plex was deleted 2026-09-17 (migrated to a container on DOCKER; see plex-docker-migration.md §9). Its former addresses 10.100.0.24 / 10.50.0.31 and MACs 00:0c:29:4a:ef:3d / 00:0c:29:4a:ef:47 are released and free for reuse.

These tables are incomplete. The host actually has 10 VMs; WW_DEV_VM (see ww.md), Rockwell_Win10 and TCBSD are not listed below, and DevVM is currently powered off, not on. Verify against govc ls /ha-datacenter/vm before relying on them.

Powered On

VM Guest OS CPU RAM LAN_100 IP DATA_50 IP Other IPs
TrueNAS Debian 12 16 128GB 10.100.0.25 10.50.0.26 +secondary IPs on both
DOCKER Debian 12 22 32GB 10.100.0.35 10.50.0.35 Docker bridges: 172.18.0.1, 172.19.0.1
Veeam Win Server 2025 8 8GB 10.100.0.30 10.50.0.32 —
HA Oracle Linux 6 16 16GB 10.100.0.40 — Docker bridge: 172.30.32.1
Ignition Debian 11 4 16GB 10.100.0.90 — IOT_200 NIC connected but no IP
DevVM Win 10 8 16GB 10.100.0.47 — IOT_200: 10.200.0.47

Powered Off

VM Guest OS CPU RAM Port Groups Notes
DevServer Win Server 2022 12 32GB LAN_100 —

Per-VM Network Detail

TrueNAS

NIC MAC Port Group IPs
Adapter 1 00:0c:29:bb:71:43 LAN_100 10.100.0.25, .26, .27
Adapter 2 00:0c:29:bb:71:4d DATA_50 10.50.0.25, .26, .27, .28

DOCKER

NIC MAC Port Group IPs
Adapter 1 00:0c:29:cf:bb:bb LAN_100 10.100.0.35
Adapter 2 00:0c:29:cf:bb:c5 DATA_50 10.50.0.35

Veeam

NIC MAC Port Group IPs
Adapter 1 00:0c:29:33:76:a5 DATA_50 10.50.0.32
Adapter 2 00:0c:29:33:76:af LAN_100 10.100.0.30

HA (Home Assistant)

NIC MAC Port Group IPs
Adapter 2 00:0c:29:f3:f3:5b LAN_100 10.100.0.40

Ignition

NIC MAC Port Group IPs
Adapter 1 00:0c:29:87:5f:f8 LAN_100 10.100.0.90
Adapter 2 00:0c:29:87:5f:02 IOT_200 (no IP, disconnected)

DevVM

NIC MAC Port Group IPs
Adapter 1 00:0c:29:5c:f9:f7 IOT_200 10.200.0.47
Adapter 2 00:0c:29:5c:f9:01 LAN_100 10.100.0.47
Reference in New Issue View Git Blame Copy Permalink