After a long time i am writing this blog as i was so much busy in new challenges in life/work and didnt got the time to write something new. Anyways i am sharing a recent Scenario which i like to share . May be many guys know it but i thought to document and share it.Scenario : We had a new deployment of HCX on-prem via automation completed and somehow its got the ip already assigned to another host in the Onprem environment, and its start conflcting . Worst thing happened that License for Activation the appliance … Read The Rest ......
While i was preparing for my vSphere Design Exam i found this interesting topic and most important to use in Every Well designed infrastructure for security and hardening of the environment. Hardening vSphere as per customer requirement is comes with may challenges like below.
Understand the customer exactly what he is looking for.
Also Contained a mix of
Operational Guidance – How you use the product in your environment
Programmatic Guidance – What settings should be applied OR audited
Recently i deployed the vSphere update manager in my lab to test some of the functionality . After testing is done i wanted to remove the plugin from vcsa but disabling it doesnt work as my vCenter keep searching and querying the update manager server. So i thought to remove it. As may be most of the people know how to remove it but i thought to share it with the people in more details. There is an VMWare KB is also there to do so. so lets start.
The hottest topic revolving in virtualization in recent times has been about the release of VMware vSphere 6.7. What followed was the increased expectations from the users to get a backup support for vSphere 6.7. While the majority of the backup vendors are scrambling to make progress, we have an update already released to support Backup for vSphere 6.7.
VMware 6.7 was announced on 17th of April, 2018.
In less than 60 days after the official release, Vembu is geared up to support 6.7.
With this latest upgrade, VMware aimed to create a consistent infrastructure for users across all … Read The Rest ......
You can manually rebalance through the cluster health check, or by using RVC commands.
If the Virtual SAN disk balance health check fails, you can initiate a manual rebalance in the vSphere Web Client. Under Cluster health, access the Virtual SAN Disk Balance health check, and click the Rebalance Disks button.
Use the following RVC commands to manually rebalance the cluster:
vsan.check_limits. Verifies whether any capacity device in the Virtual SAN cluster is approaching the 80 percent threshold limit.
vsan.proactive_rebalance [opts]<Path to ClusterComputeResource> –start. Manually starts the rebalance operation. When you run the command, Virtual SAN scans
Virtual SAN automatically rebalances the Virtual SAN cluster when a capacity device reaches 80 percent utilization. Rebalancing also occurs when you place a Virtual SAN host in maintenance mode.Its By Default.
Run the following RVC commands to monitor the rebalance operation in the cluster:
vsan.check_limits. Verifies whether the disk space utilization is balanced in the cluster.
vsan.whatif_host_failures. Analyzes the current capacity utilization per host, interprets whether a single host failure can force the cluster to run out of space for reprotection, and analyzes how a host failure might impact cluster capacity, cache reservation, and cluster components.