There are different scenarios for taking this course of action as detailed in VMware KB2144269 in my case this was a result of losing my lab vCenter which resulted in a manual effort to remove reservations, VM’s and tenant. The following details how to cleanup the virtual machines associated with a ‘Devops’ business group which prevented deletion of the associated reservation:
The error ‘Unable to authenticate’ may be because the root password has expired. The root account password by default is set to expire after 365 days and if the password is not changed before the expiry window concludes then vRA VAMI is not accessible:
In order to verify that the services are REGISTERED log into the VAMI (Virtual Appliance Management Infrastructure): https://vra01.domain.local:5480 as root and click on Services: Continue reading
This VMware Validated Design SDDC ‘Standard Architecture’ is Based on the ‘two-pod’ design where the management workloads & compute and edge workloads are segregated. The management workloads have their own dedicated vSphere cluster while the compute and edge reside on a separate vSphere cluster . This ‘two-pod’ design requires at least 8 ESXi hosts, 4 for mgmt and 4 for shared compute and edge workloads. The VVD Standard Architecture supports both single and dual-region deployments. Dual-region implies 2 DC’s located in geographically dispersed locations, leveraging vSphere replication and SRM to protect the workloads. VMware official ‘Overview of Standard SDDC’.
This VMware Validated Design SDDC ‘Consolidated Architecture’ is Based on the ‘one-pod’ design where both the management workloads and compute/edge workloads are co-located on a single vSphere cluster. Requires a minimum of 4 hosts and supports a single-region. VMware official ‘Overview of Consolidated SDDC’.
Note: As of VVD 4.2 the term ‘Pod’ is being replaced by ‘Workload Domain’ to describe the different cluster types: Management, Compute & Edge.
VVD FAQ:
https://communities.vmware.com/docs/DOC-34266
VVD Quick References:
‘Welcome to the New era of Dell EMC CI’
Some brief highlights and related articles covering the next generation of Dell EMC CI – VxBlock System 1000
The VxBlock 1000 architecture is designed to allow for the option of running multiple storage arrays within a single VxBlock system supported under one RCM (beginning with RCM 6.5.3), which means the concept of storage extensions becomes a mute point and allows for the ease of expansion and mixing of storage arrays and their associated resources as required for specific workloads. The four Dell EMC array types include VMAX, Unity, Isilon Gen6 and XtremIO X2(available post GA). Previous VxBlock systems allowed for a single array per system, now dependent on the SAN switch chosen the VxBlock 1000 supports up to 10 arrays per system (mixed array types if required to cater for varying workloads). Continue reading
The following applies to a vCenter Server Appliance that contains a vCenter Server with an embedded Platform Services Controller, a vCenter Server with an external Platform Services Controller, or a Platform Services Controller.
Note: Please perform during a maintenance window as vCSA services will be unavailable.
The following steps detail how to apply a vCSA patch directly from an ISO which can be downloaded from:
https://my.vmware.com/group/vmware/patch#search
Attach the ISO to the vCSA.
VxBlock offers the award-winning all-flash enterprise storage VMAX 950F – Either with a VxBlock 740 as primary storage or as a VxBlock Storage Technology Extension (STE) add-on to a VxBlock 350, 540 or 740.
The VMAX 950 hardware code-named Thunderbolt , along with running the Hypermax Cypress release offers further enhancements in terms of performance and functionality. When combined with a VxBlock 740 you now have the most powerful, intelligent, scalable and enterprise ready industry leading CI to support your most mission-critical applications. Continue reading
