TENJO TENGE GN VOL 02 (MR) (C: 1-0-1): Volume 2

Product Information

Adding one or multiple ESXi hosts during a remediation process of a vSphere HA enabled cluster, results in the following error message: Applying HA VIBs on the cluster encountered a failure. The error message in French language: La VM « VMC on DELL EMC -FileServer », située sur le cluster « {Cluster-1} », a signalé un problème empêchant le passage en mode de maintenance : Unable to access the virtual machine configuration: Unable to access file[local-0] VMC on Dell EMC - FileServer/VMC on Dell EMC - FileServer.vmx Mellanox ConnectX-4 or ConnectX-5 native ESXi drivers might exhibit minor throughput degradation when Dynamic Receive Side Scaling (DYN_RSS) or Generic RSS (GEN_RSS) feature is turned on

Some ESXi configuration files become read-only: As of ESXi 7.0 Update 2, configuration formerly stored in the files /etc/keymap, /etc/vmware/welcome, /etc/sfcb/sfcb.cfg, /etc/vmware/snmp.xml, /etc/vmware/logfilters, /etc/vmsyslog.conf, and /etc/vmsyslog.conf.d/*.conf files, now resides in the ConfigStore database. You can modify this configuration only by using ESXCLI commands, and not by editing files.For more information, see VMware knowledge base articles 82637and 82638. When using the lsi_msgpt3, lsi_msgpt35 and lsi_mr3 controllers, there is a potential risk to see dump file lsuv2-lsi-drivers-plugin-util-zdump. There is an issue when exiting the storelib used in this plugin utility. There is no impact on ESXi operations, you can ignore the dump file. In vSphere 7.0, NSX Distributed Virtual port groups consume significantly larger amounts of memory than opaque networks. For this reason, NSX Distributed Virtual port groups can not support the same scale as an opaque network given the same amount of memory.Workaround: Avoid resetting the NIC. If you already face the issue, use the following commands to restore the VLAN capability, for example at vmnic0: Changes in the properties and attributes of the devices and storage on an ESXi host might not persist after a reboot Occasionally, all active paths to NVMeOF device register I/O errors due to link issues or controller state. If the status of one of the paths changes to Dead, the High Performance Plug-in (HPP) might not select another pathif it shows high volume of errors. As a result, the I/O fails. You may see unnecessary zeros in currency notation to the hundredths or thousandths place — depending on the currency noted — to standardize decimal currency notation. For example, the American currency system notates to the hundredth place because the American dollar is made up of 100 pennies. As an example, consider the speed of light which travels at about 671,000,000 miles per hour. Written in standard form this number is equivalent to 6.71 x 10 8.

Workaround: Make all transport nodes join the transport zone by N-VDS or the same VDS 7.0 instance. Workaround: None. To configure the number of virtual functions for an SR-IOV device, use the same method every time. Use the VIM API or use the max_vfs module parameter and reboot the ESXi host. vSphere Lifecycle Manager and vSAN File Services cannot be simultaneously enabled on a vSAN cluster in vSphere 7.0 release ACC MULTI-SERVICE TACTICS, TECHNIQUES, AND PROCEDURES FOR AIR CONTROL COMMUNICATION (MCRP 3-20F.10, NTTP 6-02.9, AFTTP 3-2.8) An ESXi host might fail with a purple diagnostic screen due to a rare race condition in the qedentv driverAny change in the NetQueue balancer settings causes NetQueue to be disabled after an ESXi host reboot This might occur when, for example, you use an incompliant storage policy to create a CNS volume. The operation fails, while the vSphere Client shows the task status as successful. MULTISERVICE TACTICS, TECHNIQUES, AND PROCEDURES FOR TREATMENT OF NUCLEAR AND RADIOLOGICAL CASUALTIES (MCRP 4-11.1B, NTRP 4-02.21, AFMAN 44-161(I)) For more information, see the Upgrading Hosts by Using ESXCLI Commandsand the VMware ESXi Upgradeguide. Product Support Notices

When you apply an existing host profile with version 6.5, add an advanced configuration option VMkernel.Boot.autoCreateDumpFile in the host profile, configure the option to a fixed policy, and set value to false. In contrast, when only a non-head extent fails, but the head extent remains accessible, the datastore heartbeat appears to be normal. And the I/Os between the host and the datastore continue. However, any I/Os that depend on the failed non-head extent start failing as well. Other I/O transactions might accumulate while waiting for the failing I/Os to resolve, and cause the host to enter the non responding state. Workaround: After a change in the NetQueue balancer settings and host reboot, use the command configstorecli config current get -c esx -g network -k nics to retrieve ConfigStore data to verify whether the /esx/network/nics/net_queue/load_balancer/enable is working as expected. So, avoid adding zeros to the far right or left of a number and do not remove any zeros between the numerals. The Decimal System Workaround: Replace the STS certificate with a valid certificate that contains a SAN field then proceed with the vCenter Server 7.0 Upgrade/Migration.You should not add zeros to the left side of the whole number, either. Additional zeros only add value if holding a place closer to the decimal point. If you automate the firewall configuration in an environment that includes multiple ESXi hosts, and run the ESXCLI command esxcli network firewall unload that destroys filters and unloads the firewall module, the hostd service fails and ESXi hosts lose connectivity. When adding a VMkernel NIC (vmknic) to an NSX portgroup, vCenter Server reports the error "Connecting VMKernel adapter to a NSX Portgroup on a Stateless host is not a supported operation. Please use Distributed Port Group instead."

You cannot enable NSX-T on a cluster that is already enabled for managing image setup and updates on all hosts collectivelyThis error appears in the UI wizard after the Host Selection step and before the Datastore Selection step, in cases where the VM has an assigned storage policy containing host-based rules such as encryption or any other IO filter rule. Workaround: You can hot-remove and hot-add the affected Ethernet NICs of the VM to restore traffic. On Linux guest operating systems, restarting the network might also resolve the issue. If these workarounds have no effect, you can reboot the VM to restore network connectivity.