CloudArena

 Hello, As you all know that VMware NSX has native Load Balancing capabilities which provides Basic Load balancing to the virtualized environment.  But now VMware is planning to depreciate the native load balancing features and asking the VMware NSX customers to move to AVI Load Balancer product which will give advanced level of load balancing features which are supported by other third party LB vendors like F5, Cisco ACE etc... VMware NSX Advanced Load Balancer (Avi) is an API (Application Programming Interface) first, self-service Multi-Cloud Application Services Platform that ensures consistent application delivery, bringing software load balancers, web application firewall (WAF), and container Ingress for applications across data centers and clouds.    VMware’s Avi is a modern, software-defined elastic application delivery fabric. It is composed of a central control plane and a distributed data plane. VMware Avi Controller provides a centralized policy engi...

  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...

  Hello There, Recently , we faced an issue in our NSX-T envrironment running with 3.2.x version. We saw below error message while running the pre-check for NSX upgrade to 4.x version.  " Edge node 31c2a0ba-e10a-48eb-940d-85f1e48c811f vmId is not found on NSX manager " So to fix this vmId issue for Edge Nodes, we need to edit the DeploymentUnitInstance and EdgeNodeExternalConfig in NSX Corfu DB tables. Steps to be done: 1) Login to NSX Manager UI . Start a backup by going to the NSX Manager UI System > Lifecycle Management > Backup and Restore and click on the START BACKUP button. 2) Log into any of NSX Manager node's CLI using the admin and switch to root account and stop the corfu service using the following command:    /etc/init.d/corfu-server stop 3) Stop the proton service    /etc/init.d/proton stop 4) Start the corfu service    /etc/init.d/corfu-server start 5) Execute the following DB commands to make the changes in...

VMware VDT- VCF Diagnostic Tool Overview VDT (developed and built by VMware Support) is a utility designed to run a series of comprehensive checks live on a target appliance. In its current state, VDT supports the vCenter Server and SDDC Manager appliances. The VCF Diagnostic Tool (VDT) is a diagnostic tool that is run directly on the SDDC Manager or vCenter server. It runs through a series of checks on the system configuration and reports user-friendly PASS/WARN/FAIL results for known configuration issues. It also provides information (INFO) messages from certain areas which we hope will make detecting inconsistencies easier. The goal of these tests is to provide live diagnostic information to the user about their environment which might otherwise be missed.   This tool is completely read-only for the entire environment. hence, it will not make any changes to the environment and no risks to use it. Another important thing about this tool that, it is completely offline a...

CVE-2023-48795 describes a vulnerability in OpenSSH v9.5 and earlier. This vulnerability, also known as the "Terrapin attack", could allow an attacker to downgrade the security of an SSH connection by manipulating information transferred during the the connection's initial handshake/negotiation sequence.  The attacker must have already gained access to the local network, and must be able to both intercept communications and assume the identity of both the recipient and the sender.   The CVSS 3.x rating of "Medium" reflects the difficulty in successfully exploiting this vulnerability. CVE-2023-48795 has since been resolved in OpenSSH v9.6. It's mitigation requires both client and server implementations to be upgraded to this fixed or later version. Additionally, this vulnerability can also be addressed by disabling use of the "ChaCha20-Poly1305" cipher in affected OpenSSH implementations.  This vulnerbility affects all systems having...

  VMware vSAN 8™, Introduces the revolutionary  Express Storage Architecture ™.  This is an optional, alternative storage architecture to the vSAN original storage architecture also found in vSAN 8.  When running on qualified hardware in approved vSAN ReadyNodes, the vSAN Express storage architecture will offer supreme levels of performance, scalability, resilience, and data services without compromising performance.  The vSAN Express Storage Architecture unlocks the capabilities of modern hardware to allow the workloads of today and tomorrow. Below are some key differences between OSA and ESA Architecture. OSA: Original Storage Architecture 1. OSA is a vSAN Distributed File System (vDFS) 2. Drives like SSDs, HDDs, and hybrid supported by OSA. 3. 1 Cache drive per Disk group is supported by OSA. 4. Hardware requirements for OSA is Varies as per vSAN config. 5. With OSA we can get good performance by leveraging different RAID policies with strippin...

Symptoms:- vCenter Server Cloud Account username or password has been changed. An existing endpoint in VMware vRealize Automation (Now VMware Aria Automation) needs to be updated with the new credentials. Credentials validation is successful, but then you see the error: Failed to connect to vCenter: Error: Cannot login due to incorrect username and password The configuration fails to load and the endpoint cannot be saved. Data collection and provisioning to this endpoint fails due to the invalid credentials.   1. Log in to vRA, Right-click anywhere, and click on Inspect. Click on Network tab and press CTRL+R 3. Scroll a bit down and search for Access-Token Row and click on it and navigate to the Response section. 4. Browse to Swagger API from API Documentation and click on Authorize button. 5. Enter Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxx (here xxxxxxxxxx is the Access Token you copied) and hit Authorize. 6. Post performing this - Swagger is now Authorized to vRA and you can use AP...