VMware Cloud Foundation 5.0 on Dell VxRail 8.0.100

-

 


VMware Cloud Foundation 5.0 on Dell VxRail 8.0.100 is now GA (Generally Available), this is the first VCF release to support vSphere 8.0.

VMware Cloud Foundation (VCF) on VxRail offers jointly engineered features that simplify, streamline, and automate the operations of the Software-Defined Data Center (SDDC) stack and manage the end-to-end lifecycle. This integration enables VCF to extend the native VxRail capabilities for VMware NSX, VMware Aria Suite (formerly VMware vRealize Suite), and multiple VxRail clusters. VCF on VxRail provides a simple path to the hybrid cloud.


VCF 5.0 on VxRail 8.0.100 hardware and software version details

This section lists the VCF 5.0 on VxRail 8.0.100 hardware and software components.

Hardware and firmware versions

Software versions

VCF 5.0 on VxRail 8.0.100 includes the following software versions.

For the latest updates, see VCF on VxRail Support Matrix.

Table 1. VCF components
SOFTWARE COMPONENT VERSION BUILD NUMBER
VMware Cloud Foundation 5.0 N/A
VMware Cloud Foundation Cloud Builder for VxRail VM 5.0 21822418
VMware Cloud Foundation SDDC Manager 5.0 21822418
VMware vCenter Server Appliance 8.0 Update 1a 21815093
VMware NSX 4.1.0.2 21761691
VMware vRealize Suite Lifecycle Manager 8.10 Patch 1 21331275

Table 2. VxRail components                                                                                                                                                                                                        
SOFTWARE COMPONENT 8.0.100 VERSION BUILD NUMBER
VxRail 8.0.100 28093095
VxRail Manager 8.0.100 28093094
VMware vSphere ESXi 8.0 Update 1a 21813344
VMware vSAN 8.0 Update 1a 21813344  

This release includes the following new features:

  • Life Cycle Management (LCM) updates:
    • Added support for upgrade from VCF 4.3.x, VCF 4.4.x, VCF 4.5.x to VCF 5.0
    • Added support for VxRail accurate versioning
    • Enhancements to SDDC Manager release versions view and API
    • Added support for flexible WLD target versions
    • Enhanced the frequency of SDDC Manager precheck updates
    • Added support for SDDS Manager configuration drift awareness
    • Enhanced the frequency of SDDC Manager prechecks for vRealize or Aria Suite component versions
  • Security updates:
    • Added support for isolated domains with individual SSO. Create and manage workload domains that can each join the management domain's vCenter Single Sign-On domain or a new vCenter Single Sign-On domain that is not used by any other workload domain.
    • Enhanced certificate management
  • Platform and Scale enhancements: Increased the workload domain scalability limits.
  • Storage updates: Added support for NVMe over TCP connected supplemental storage.
  • Operations and Serviceability updates:     
    • Enhancements to VCF+
    • Added support for version aliasing and inventory sync in SDDC Manager
  • Hardware platform updates: Support for single socket 15th generation VxRail P670F
  • Asynchronous release independent related updates: Added support for VCF Async Patch Tool 1.1.0.1 release which supports VCF 5.0 on VxRail 8.0.100.

For more information, see the following:


Comments

Post a Comment

Popular posts from this blog

How to migrate the N-VDS as the host switch to VDS 7.0 in NSX-T 3.x

-
Image
  Hello There, In this article, i am covering how to migrate the ESXi host switch from N-VDS to VDS 7.0 switch in NSX-T 3.2.x version. When using N-VDS as the host switch,  NSX-T  is represented as an opaque network in  vCenter Server . N-VDS owns one or more of the physical interfaces (pNICs) on the transport node, and port configuration is performed from  NSX-T Data Center . You can migrate your host switch to  vSphere  Distributed Switch (VDS) 7.0 for optimal pNIC usage and manage the networking for  NSX-T  hosts from  vCenter Server . When running  NSX-T  on a VDS switch, a segment is represented as an  NSX-T  Distributed Virtual Port Groups. Any changes to the segments on the  NSX-T  network are synchronized in  vCenter Server. We have an NSX-T environment running with NSX-T 3.2.2.1 version. this environment was designed and implemented with NSX-T 2.x version and that time we used the N-VDS as host switch configuration on the transport nodes bcuz VDS was not supported that time. 
Read more

vROPS appliances password remediation tasks failed from SDDC manager

-
Image
Issue details:-   Password remediation tasks on SDDC manager getting failed with below error. However, we are able to connect SSH with root password on the vROPS appliances, no issues with credentials. I checked Operations logs on SDDC manager and found below logs, indicating the SSH connectivity issues from SDDC to vROPS appliances. Tried to do SSH vROPS appliance from SDDC manager, getting below error... Seems some issue with ECDSA key.. Resolution:- SSH to vROPS appliance and retrieve the ECDSA ssh keys as below. Now, we have 2 options to update the correct SSH keys for vROPS appliance on SDDC manager known_Hosts files located at below location.   /root/.ssh/known_hosts   /etc/vmware/vcf/commonsvcs/known_hosts   /home/vcf/.ssh/known_hosts   /opt/vmware/vcf/commonsvcs/defaults/hosts/known_hosts First option is manually copy and paste the SSH key on all the known_hosts files and restart the SDDC manager services and then try to remediate the password again. it will be successful this
Read more

How to Import/Register a VM into vRA portal

-
Image
You can import an unmanaged virtual machine to a vRealize Automation environment. An unmanaged virtual machine exists in a vCenter but is not managed in a vRealize Automation environment and cannot be viewed in the vRA portal . Once you import an unmanaged virtual machine, the virtual machine is managed by using the vRealize Automation management interface. you can see the virtual machine on the Managed Machines tab or the Items tab. Please follow below steps to Import/Register VM into a vRA portal. Log in to vRealize Automation as a fabric administrator and as a business group manager. If you are importing virtual machines that use static IP addresses, prepare a properly configured address pool.  If you use bulk import to import a virtual machine with a static IP address that is allocated to another virtual machine, the import fails. Create a Blueprint and should not have even network attached as well. See below snapin. Create Network profile that shoul
Read more