Firewall configuration has changed. Operation 'disable' for rule set vsanmgmt-https-tunnel succeeded.
Firewall configuration has changed. Operation 'enable' for rule set vsanmgmt-https-tunnel succeeded.vCenter-extracted-logs/commands/journalctl_-b--{0-9].txt vpxd [] Event [4730183] [1-1] [vim.event.EventEx] [info] [] [xxx-xxx-comp_xxxx] [4730183] [Firewall configuration has changed. Operation 'enable' for rule set vsanmgmt-https-tunnel succeeded.]
vpxd [] Event [4730186] [1-1] [vim.event.EventEx] [info] [] [xxx-xxx-comp_xxxx] [4730186] [Firewall configuration has changed. Operation 'enable' for rule set vsanmgmt-https-tunnel succeeded.]
vpxd [] Event [4730189] [1-1] [vim.event.EventEx] [info] [] [xxx-xxx-comp_xxxx] [4730189] [Firewall configuration has changed. Operation 'enable' for rule set vsanmgmt-https-tunnel succeeded.]
vpxd [] Event [4730234] [1-1] [vim.event.EventEx] [info] [] [xxx-xxx-comp_xxxx] [4730234] [Firewall configuration has changed. Operation 'disable' for rule set vsanmgmt-https-tunnel succeeded.]
vpxd [] Event [4730237] [1-1] [vim.event.EventEx] [info] [] [xxx-xxx-comp_xxxx] [4730237] [Firewall configuration has changed. Operation 'disable' for rule set vsanmgmt-https-tunnel succeeded.]This issue happens if the service "vmware-vsan-health" ( formerly vsan-health ) is enabled on a vCenter where no vSAN cluster is enabled
vsan-health ) can be stopped on the VC by logging as root on cliservice-control --stop vmware-vsan-healthNote:
1. Ensure a full back up of the vCenter server is taken before activity
2. The snapshot of the vCenter VM should be taken before activity
The service "vmware-vsan-health" is default to automatic start when vCenter is rebooted. If you do not want to manually stop the service everytime the vCenter is rebooted, please change the "vmware-vsan-health" service Startup Type from "Automatic" to "Manual". Please see the following KB to change the vCenter server services start up type: