At VMware Explore 2023 in Barcelona, we made a big announcement about VMware Data Services Manager (DSM) version 2.0. In the upcoming series of blog posts, I will introduce you to the new features of DSM version 2.0. One major shift in focus is that DSM 2.0 is squarely aimed at the vSphere […]
I first wrote about the tiny palm size iKOOLCORE R1 back in Spring of this year, I was pretty impressed at how capable the R1 was, especially given the tiny footprint that is slightly taller than a Lego minifigure! It has not even been a full year since the release of the R1 and the […]
In addition to the big announcements from yesterday on major simplification of the new VMware by Broadcom offers and licensing model and the new chapter for the VMware Desktop Hypervisor products, I have one more piece of exciting news that I would like to share with our users, just […]
By vExpert Behzad Hassanzadeh. During the VCSA install, we select a password for the Root user and by that, we access vCenter Management (VAMI) and Command-Line. […]
Retrospection | Starting with the previous VMware Cloud Director (VCD) release (10.5), the Border Gateway Protocol (BGP) feature of the platform has begun to change. The BGP configuration was initially available to service providers and tenants via the Edge Gateway UI. The main reason for that […]
Deterministic peering sounds very complicated, doesn’t it? It is also sometimes called deterministic steering. In short, within NSX it used as ‘being able to determine which BGP neighbor to peer with’, or ‘being able to determine which path the traffic should take’. Even shorter: ‘does this […]
I was unable to manage Virtual Machines with virtual Hardware Version 9 or older via the vSphere Client while they are in a powered on state.
Symptoms
vCenter Server Version: The problem is specific to vCenter Server version 8.0 U2 – 22385739.
Virtual Machine Hardware Version: Affected VMs are those with hardware version 9 or below.
VM State: The issue occurs when the Virtual Machine is in a powered-on state.
UI Glitches: In the vSphere Client, when attempting to open the ‘Edit Settings’ for the affected VMs, users notice red exclamation marks next to the Virtual Hardware and VM Options tabs. Additionally, the rest of the window appears empty, hindering any further action.
Impact and Risks:
The primary impact of this issue is a significant management challenge:
Users are unable to manage Virtual Machines with Virtual Hardware Version 9 or older through the vSphere Client while they remain powered on. This limitation can affect routine operations, maintenance, and potentially urgent modifications needed for these VMs.
Workarounds:
In the meantime, users can employ either of the following workarounds to manage their older VMs effectively:
Power Off the VM: By powering off the VM, the ‘Edit Settings’ window should function correctly. While this is not ideal for VMs that need to remain operational, it can be a temporary solution for making necessary changes.
Use ESXi Host Client: Alternatively, users can connect directly to the ESXi Host Client to perform the ‘Edit Settings’ operations. This method allows the VM to remain powered on, which is beneficial for critical systems that cannot afford downtime.
With the release of ONTAP 9.10.1, NetApp has introduced a significant advancement in data protection technology: the Autonomous Ransomware Protection (ARP). ARP is designed to safeguard your data volumes against the ever-evolving threat of ransomware attacks. This feature can be applied to both new and existing volumes, providing an essential layer of security for your data.
Understanding the ARP Implementation Process
Initiate ARP in Learning Mode: The first step in deploying ARP is to activate it in learning mode. During this phase, ARP meticulously analyzes your system’s workload, thereby establishing a baseline for normal operational behavior. This approach is crucial in minimizing false positives once ARP transitions to active mode.
Configuring ARP on Volumes: ARP offers flexibility; it can be enabled on a newly created volume or an existing one. For existing volumes, it’s important to note that ARP’s learning and active modes are applied only to new data written post-activation, leaving existing data unanalyzed.
Prerequisites: Ensure your storage VM is set up for NFS or SMB protocols. Additionally, verify that your ONTAP version is correctly licensed and that you have a NAS workload with configured clients. The target volume should have an active junction path and must not be at full capacity.
Learning Mode Duration: It is advisable to allow ARP to operate in learning mode for at least 30 days. However, starting with ONTAP 9.13.1, ARP can autonomously determine the optimal learning period and may transition to active mode sooner if it deems appropriate.
If you upgraded to ONTAP 9.13.1 or later, adaptive learning is enabled so that the change to active state is done automatically. If you do not want this behavior to be automatically enabled, change the setting at the SVM level on all associated volumes:
Notification Setup: Configuring the Event Management System (EMS) for email notifications is recommended. This setup ensures you are promptly informed of any ARP activities.
Multi-Admin Verification (MAV): From ONTAP 9.13.1 onwards, enabling MAV is advised. This feature requires the authentication of multiple admin users for configuring ARP settings, adding an extra layer of security.
For a detailed understanding of ARP’s learning and active modes, and for information on configuring EMS notifications and MAV, refer to the respective sections in the ONTAP documentation.
In the ever-evolving landscape of artificial intelligence, the potential of generative AI has captured the attention of organizations worldwide. From code generation to IT operations automation, its applications are diverse and impactful. Recognizing the centrality of data in all AI use cases, […]