Posts

Edge node vmid not found on NSX manager

Image
  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 VCF and vSphere Diagnostic tool-VDT

Image
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 Impact of Terrapin SSH Attack

Image
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 OSA and ESA overview.

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

Update certificate/password on vRA cloud account

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

BGP EVPN Support in NSX-T Data Center

Image
  NSX-T Data Center   leverages BGP EVPN technology to interconnect and extend NSX-managed overlay networks to other data center environments not managed by NSX, VXLAN encapsulation is used between NSX TEPs (edge nodes and hypervisors) and external network devices to ensure data plane compatibility. Two connectivity modes are supported for EVPN implementation in  NSX-T Data Center : Inline Mode: In this mode, the tier-0 gateway establishes MP-BGP EVPN control plane sessions with external routers to exchange routing information. In the data plane, edge nodes forwards all the traffic exiting the local data center to the data center gateways and incoming traffic from the remote data center to the hypervisors in the local data center. Since the edge nodes are in the data forwarding path, this model is called the Inline model. Route Server Mode: In this mode, the tier-0 gateway establishes MP-BGP EVPN control plane to exchange routing information with the external router or ro...

SDDC manager backup task failed with error "Could not start SDDC Manager backup Backup failed : Unexpected error encountered when processing SDDC Manager Backup"

Image
Today, I am writing this post related to SDDC manager backup task failure with error message " Could not start SDDC Manager backup Backup failed : Unexpected error encountered when processing SDDC Manager Backup ". SDDC manager is running with VCF 4.5.1 version. We have configured the SDDC backups on a external SFTP server. Below is the screenshot of backup task failure. After checking the operations logs under   /var/log/vmware/vcf/operationsmanager/operationsmanager.logs we have found below entries related to backup failures that indicating issue with SOS client service and Too many files open in backup task.   2023-09-25T11:22:34.655+0000 ERROR [vcf_om,99cc8bcd8fbb453b,d881] [c.v.v.b.helper.SosBackupApiClient,http-nio-127.0.0.1-7300-exec-5] An exception 500 INTERNAL SERVER ERROR: "{"arguments":[],"causes":[{"message":"[Errno 24] Too many open files: '/var/log/vmware/vcf/sddc-support/vcf-sos.log'","type":...