VMware vSphere 7.0 Update 1c Released

VMware has released vCenter 7.0 update 1c, ESXi 7.0 1c and earlier they released VMware Tools 11.2.1.

vCenter 7.0 update 1c

What’s new:

• Physical NIC statistics: 
  • vCenter Server 7.0 Update 1c adds five physical NIC statistics:droppedRx, droppedTx, errorsRx, RxCRCErrors and errorsTx, to the hostd.log file at /var/run/log/hostd.log to enable you detect uncorrected networking errors and take necessary corrective action.
• Advanced Cross vCenter vMotion: 
  • With vCenter Server 7.0 Update 1c, in the vSphere Client, you can use the Advanced Cross vCenter vMotion feature to manage the bulk migration of workloads across vCenter Server systems in different vCenter Single Sign-On domains. Advanced Cross vCenter vMotion does not depend on vCenter Enhanced Linked Mode or Hybrid Linked Mode and works for both on-premise and cloud environments. Advanced Cross vCenter vMotion facilitates your migration from VMware Cloud Foundation 3 to VMware Cloud Foundation 4, which includes vSphere with Tanzu Kubernetes Grid, and delivers a unified platform for both VMs and containers, allowing operators to provision Kubernetes clusters from vCenter Server. The feature also allows smooth transition to the latest version of vCenter Server by simplifying workload migration from any vCenter Server instance of 6.x or later.
• Parallel remediation on hosts in clusters that you manage with vSphere Lifecycle Manager baselines: 
  • With vCenter Server 7.0 Update 1c, you can run parallel remediation on ESXi hosts in maintenance mode in clusters that you manage with vSphere Lifecycle Manager baselines.
• Third-party plug-ins to manage services on the vSAN Data Persistence platform: 
  • With vCenter Server 7.0 Update 1c, you can enable third-party plug-ins to manage services on the vSAN Data Persistence platform from the vSphere Client, the same way you manage your vCenter Server system. For more information, see the vSphere with Tanzu Configuration and Management documentation

See the release notes here.

ESXi 7.0 1c

What’s new:

• ESXi 7.0 Update 1c supports vSphere Quick Boot on the following servers:
  • Cisco Systems Inc:
    • HX240C-M5SD
    • HXAF240C-M5SD
    • UCSC-C240-M5SD
  • Dell Inc:
    • PowerEdge C6420
    • PowerEdge C6525
    • PowerEdge FC640
    • PowerEdge M640
    • PowerEdge MX740c
    • PowerEdge MX840c
    • PowerEdge R540
    • PowerEdge R6515
    • PowerEdge R6525
    • PowerEdge R7515
    • PowerEdge R7525
    • PowerEdge R840
    • PowerEdge R930
    • PowerEdge R940
    • PowerEdge R940xa
  • HPE:
    • ProLiant DL385 Gen10
• With ESXi 7.0 Update 1c, you can use the --remote-host-max-msg-len parameter to set the maximum length of syslog messages, to up to 16 KiB, before they must be split. By default, the ESXi syslog daemon (vmsyslogd), strictly adheres to the maximum message length of 1 KiB set by RFC 3164. Longer messages are split into multiple parts. Set the maximum message length up to the smallest length supported by any of the syslog receivers or relays involved in the syslog infrastructure.
• With ESXi 7.0 Update 1c, you can use the installer boot option systemMediaSize to limit the size of system storage partitions on the boot media. If your system has a small footprint that does not require the maximum 138 GB system-storage size, you can limit it to the minimum of 33 GB. The systemMediaSize parameter accepts the following values:
  • min (33 GB, for single disk or embedded servers)
  • small (69 GB, for servers with at least 512 GB RAM)
  • default (138 GB)
  • max (consume all available space, for multi-terabyte servers)
  • The selected value must fit the purpose of your system. For example, a system with 1TB of memory must use the minimum of 69 GB for system storage. To set the boot option at install time, for example systemMediaSize=small, refer to Enter Boot Options to Start an Installation or Upgrade Script. For more information, see VMware knowledge base article 81166.
• Select Resolved issues:
  • After upgrade of HPE servers to HPE Integrated Lights-Out 5 (iLO 5) firmware version 2.30, you see memory sensor health alerts

See the release notes here.

VMware Tools 11.2.1

This version fixes some Display driver bugs in version 11.2.0.

See the release notes here.