Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

ESXi Firewall Rule configuration continuously updated on the hosts with enable and disable operations for "esxupdate" (67241)

Last Updated: 1/19/2024Categories: InformationalTotal Views: 29602Language:
Chinese (Simplified)JapaneseEnglish

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Symptoms

Every hour, a number of ESXi Firewall Rule configuration change events are observed on all hosts in vSAN Clusters:

Firewall configuration has changed. Operation 'enable' for rule set 'esxupdate' succeeded.
Firewall configuration has changed. Operation 'disable' for rule set 'esxupdate' succeeded.

You also notice VUM scan events around the above Firewall changed events.

Successfully scanned <ESXi FQDN>

Messages in envoy.log might show the local http connection limit being hit due to connections to 127.0.0.1:8084 (8084, 9084, and 9087 are VUMs port)

2023-12-12T13:33:33.036Z warning envoy[3405621] [Originator@6876 sub=filter] [C11747] local https connections exceed max allowed: 2048
2023-12-15T13:33:33.036Z warning envoy[3405621] [Originator@6876 sub=filter] [C11747] closing connection TCP<127.0.0.1:41032, 127.0.0.1:8084>

The user initiating the VUM scan is com.vmware.vsan.health

The  timing of these events varies with different clusters

The vSAN clusters have vSAN Health Service enabled with a scheduled check every 60 minutes

Cause

vSAN generates system baselines and baseline groups for use with vSphere Update Manager. You can use these recommended baselines to update software, patches, and extensions for hosts in your vSAN cluster.

vSAN 6.6.1 and later generates automated build recommendations for vSAN clusters. vSAN combines information in the VMware Compatibility Guide and vSAN Release Catalog with information about the installed ESXi releases. These recommended updates provide the best available release to keep your hardware in a supported state.

The vSAN Build Recommendation checks are initiated as part of the vSAN Health Check that is run every 60 mins (default configuration). See KB  https://kb.vmware.com/s/article/58891 for details on this test.

Resolution

This is an expected behavior based on the configuration of the vSAN Health Check in the affected vSAN cluster.
If you wish to disable the VUM scans or reduce their frequency, check the Workaround section of this article.

Workaround

Option 1: Reduce the frequency of VUM Scans

For e.g. to set the scans to happen weekly, do the below:

SSH into the vCenter Appliance

Edit /etc/vmware-vsan-health/config.conf file using a text editor like 'vi'

Under [VumIntegration] section add the below parameters (the values are in minutes, 10080=7 days)

autoCheckerInterval = 10080
VumScanTaskIntervalInMin = 10080

Restart vSAN health service using this command

/usr/lib/vmware-vmon/vmon-cli -r vsan-health

Option 2: Disable vSAN Baseline VUM Scans completely

Note: Build recommendation would not be provided in vSAN Health Service after making the changes below.

SSH into the vCenter Appliance

Edit /etc/vmware-vsan-health/config.conf file using a text editor like 'vi'

Under the parameter [KillSwitch], add the following field. Create one if [KillSwitch] section doesn't exist.

[KillSwitch]

VumIntegration = false

Restart vSAN health service using this command

/usr/lib/vmware-vmon/vmon-cli -r vsan-health

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 8.0.x

VMware vSAN 7.0.x

VMware vSAN 6.6.x

Take Our Survey

Support Assistant