I think I have a ghost vmkernel nic that vSAN thinks exist, but is no more. Trying to clean up errors in vSAN heath check.
Host in UI sees vmk0 (mgmt/vm), vmk1 (vSAN/VMotion)
But CLI for vSAN shows different story
[root@medusa:~] esxcli network ip interface list
vmk0
Name: vmk0
MAC Address: 00:1e:67:a4:a2:bf
Enabled: true
Portset: DvsPortset-0
Portgroup: N/A
Netstack Instance: defaultTcpipStack
VDS Name: dvswitch0
VDS UUID: 50 02 e8 65 55 42 7d 66-e9 c9 62 d4 1c c9 6d 2b
VDS Port: 303
VDS Connection: 994449442
Opaque Network ID: N/A
Opaque Network Type: N/A
External ID: N/A
MTU: 1500
TSO MSS: 65535
RXDispQueue Size: 2
Port ID: 67108882
vmk2
Name: vmk2
MAC Address: 00:50:56:68:8c:23
Enabled: true
Portset: vswitch1
Portgroup: storage_101
Netstack Instance: defaultTcpipStack
VDS Name: N/A
VDS UUID: N/A
VDS Port: N/A
VDS Connection: -1
Opaque Network ID: N/A
Opaque Network Type: N/A
External ID: N/A
MTU: 9000
TSO MSS: 65535
RXDispQueue Size: 2
Port ID: 100663315
[root@medusa:~] esxcli vsan network list
Interface
VmkNic Name: vmk1
IP Protocol: IP
Interface UUID: b5764a61-8596-0a27-76a2-98be9459fea0
Agent Group Multicast Address: 224.2.3.4
Agent Group IPv6 Multicast Address: ff19::2:3:4
Agent Group Multicast Port: 23451
Master Group Multicast Address: 224.1.2.3
Master Group IPv6 Multicast Address: ff19::1:2:3
Master Group Multicast Port: 12345
Host Unicast Channel Bound Port: 12321
Data-in-Transit Encryption Key Exchange Port: 0
Multicast TTL: 5
Traffic Type: vsan
Interface
VmkNic Name: vmk2
IP Protocol: IP
Interface UUID: 99d7cd61-f79d-98ac-5fb7-98be9459fea0
Agent Group Multicast Address: 224.2.3.4
Agent Group IPv6 Multicast Address: ff19::2:3:4
Agent Group Multicast Port: 23451
Master Group Multicast Address: 224.1.2.3
Master Group IPv6 Multicast Address: ff19::1:2:3
Master Group Multicast Port: 12345
Host Unicast Channel Bound Port: 12321
Data-in-Transit Encryption Key Exchange Port: 0
Multicast TTL: 5
Traffic Type: vsan
[root@medusa:~] esxcli vsan network remove -i vmk1
Unable to complete Sysinfo operation. Please see the VMkernel log file for more details.: Not found
[root@medusa:~]
[root@medusa:~] tail -20 /var/log/syslog.log
2022-01-19T19:44:01Z backup.sh[548303]: Using key ID b87ae72b-ae50-4536-ae3e-8b04797ac3e8 to encrypt
2022-01-19T19:44:51Z vdfsd: vdfs-proxy is running
2022-01-19T19:44:51Z vdfsd: vdfs-server is running
2022-01-19T19:45:00Z crond[524974]: USER root pid 548726 cmd /bin/hostd-probe.sh ++group=host/vim/vmvisor/hostd-probe/stats/sh
2022-01-19T19:46:00Z crond[524974]: USER root pid 548821 cmd /usr/lib/vmware/vsan/bin/vsanObserver.sh ++group=host/vim/vmvisor/vsanobserver
2022-01-19T19:46:01Z root: There are 1 /usr/lib/vmware/vsan/bin/vsanObserver.sh running ...
2022-01-19T19:46:01Z root: Cannot parse UUID from /vsantraces
2022-01-19T19:46:01Z root: Failed to get freeMB from UUID. Roll back.
2022-01-19T19:46:01Z root: Calc for ramdisk mounted on /, freeMB:28
2022-01-19T19:46:01Z root: Calc for ramdisk mounted on /vsantraces, freeMB:280
2022-01-19T19:46:01Z root: CalcFreeSpace sizeKB: 892, freeMB: 280
2022-01-19T19:47:01Z vdfsd: vdfs-proxy is running
2022-01-19T19:47:01Z vdfsd: vdfs-server is running
2022-01-19T19:48:00Z crond[524974]: USER root pid 549173 cmd /usr/lib/vmware/vsan/bin/vsanObserver.sh ++group=host/vim/vmvisor/vsanobserver
2022-01-19T19:48:01Z root: There are 1 /usr/lib/vmware/vsan/bin/vsanObserver.sh running ...
2022-01-19T19:48:01Z root: Cannot parse UUID from /vsantraces
2022-01-19T19:48:01Z root: Failed to get freeMB from UUID. Roll back.
2022-01-19T19:48:01Z root: Calc for ramdisk mounted on /, freeMB:28
2022-01-19T19:48:01Z root: Calc for ramdisk mounted on /vsantraces, freeMB:280
2022-01-19T19:48:01Z root: CalcFreeSpace sizeKB: 908, freeMB: 280
[root@medusa:~]
So I can't delete this ghost vmk1 as I think vSAN still thinks it has a file or some kind of lock..
Ideas?