vSphere ESXi 7.0 U2 and later versions configuration files for sfcb "wbem" and snmp can no longer be edited
Article ID: 340446
Updated On:
Products
Issue/Introduction
As part of the bigger goal of moving away from using stickybit files, VMware have moved the configuration stored in these files to ConfigStore.
These files are used just as cache files by the services, the configurations in these files are now stored in the ConfigStore. The ConfigStore is the single source of truth in ESXi 7.0 Update 2 and later.
Symptoms:
The ESXi configuration files /etc/sfcb/sfcb.cfg, /etc/vmware/snmp.xml, /etc/vmsyslog.conf, /etc/vmware/logfilters and /etc/vmsyslog.conf.d/*.conf can no longer be edited.
It is no longer possible to make changes to snmp, sfcb/wbem, or syslog by editing these config files. From ESXi 7.0 Update 2, files under /etc are read-only and edits do not persist across reboot.
Environment
VMware vSphere ESXi 7.0.2
VMware vSphere ESXi 7.0.3
Resolution
Use the following esxcli commands to configure snmp, sfcb/wbem, and syslog on ESXi. The commands have been modified to read/write to configstore instead of interacting with a stickybit file.
- esxcli system wbem get > Displays sfcb "wbem" current configuration
- esxcli system wbem set
- esxcli system snmp get > Displays snmp current configuration
- esxcli system snmp set
- esxcli system syslog mark
- esxcli system syslog reload
- esxcli system syslog config set
- esxcli system syslog config logger set
- esxcli system syslog config logfilter set
- esxcli system auditrecords local set
- esxcli system auditrecords remote
Additional Information
For versions before ESXi 7.0U2 refer the following KB article to make changes for disabling static ciphers,
Disabling static ciphers for TLS in ESXi
Feedback
