VMware vSphere+: Despliegue de VMware Cloud Gateway

Hola amigos del blog, en esta oportunidad les quiero escribir sobre VMware vSpehre+, el nuevo portal de administración centralizada multi nube. En este primer post, trataré los términos generales y principales para implementar VMware Cloud Gateway.

VMware vSphere+ es compatible con todas las capacidades existentes de vSphere, incluyendo el Modo vinculado mejorado y vSphere High Availability (HA). El host ESXi y vCenter Server deben cumplir ciertos requisitos de software y hardware para poder asignar licencias basadas en suscripción a través del portal VMware vSphere+.

Requisitos del host ESXi y vCenter Server:

* Hosts ESXi: Todas las versiones que son compatibles con las versiones compatibles de vCenter Server.

* Requisitos de hardware: El clúster donde se implementan vCenter Server y vCenter Cloud Gateway debe cumplir con ciertos requisitos de hardware. La CPU, la memoria y el almacenamiento en el clúster deben tener al menos el doble del tamaño del vCenter Server implementado para que el hardware sea suficiente para las actualizaciones de vCenter Server.

Requisitos de software:

* vCenter Server: Todas las versiones que son compatibles con las versiones compatibles de ESXi.

* ESXi: Todas las versiones que son compatibles con las versiones compatibles de vCenter Server.

Requisitos de hardware para las actualizaciones de vCenter Server:

* La CPU, la memoria y el almacenamiento en el clúster deben tener al menos el doble del tamaño del vCenter Server implementado para que el hardware sea suficiente para las actualizaciones de vCenter Server.

Agregue el FQDN de vCenter Cloud Gateway en su servidor DNS y configure búsquedas DNS directas e inversas. Si utiliza un servidor proxy para conectarse a Internet, tenga a mano los siguientes detalles del proxy:

* Nombre de host o dirección IP del servidor proxy

* Número de puerto

* Nombre de usuario y contraseña para autenticarse en el servidor proxy

vCenter Cloud Gateway no es compatible con IPv6. Asegúrese de que vCenter Server no esté configurado con una dirección IPv6.

Para que vCenter Cloud Gateway se comunique con VMware Cloud y vCenter Server, asegúrese de que los siguientes puertos de firewall estén abiertos:

* Puerto 443 (HTTPS)

* Puerto 22 (SSH)

* Puerto 5901 (API)

* Puerto 5902 (SOAP)

La cantidad de instancias de vCenter Cloud Gateway que debe instalar depende de la cantidad de instancias de vCenter Server que desee suscribir a vSphere+. Puede conectar hasta 8 instancias de vCenter Server en cada instancia de vCenter Cloud Gateway.

En cuanto al despliegue, puede utilizar cualquier sistema operativo invitado para ejecutar el instalador ISO de vCenter Cloud Gateway. Algunos de los sistemas operativos compatibles son:

* Windows Server 2016

* Windows Server 2019

* Linux Ubuntu 18.04 LTS

* Linux Red Hat Enterprise Linux 8

Espero que esta información sea útil para su implementación de VMware vSphere+. En el próximo post, trataré los pasos de despliegue y consideraciones técnicas a tener en cuenta.

¡No te pierdas nuestras publicaciones! Suscribirse al blog para recibir notificaciones por correo electrónico cada vez que se publique un nuevo artículo.

vSphere 8 Update 1: Enhancing Security, Performance, and Scalability

In the latest release of vSphere 8, VMware has introduced several new features and improvements that aim to enhance security, performance, and scalability for organizations of all sizes. As a follow-up to the initial release, vSphere 8 Update 1 brings more exciting capabilities to the table, making it an essential upgrade for any business relying on virtualization technology.

Enhanced Security Features

One of the most significant updates in vSphere 8 Update 1 is the introduction of Skyline Health Diagnostics, a self-service diagnostic platform that provides admins with insights into their environment and helps troubleshoot issues automatically. This feature aims to reduce the need for support tickets and enables IT teams to resolve issues more quickly and efficiently. Additionally, vSphere 8 Update 1 includes Green Metrics, which tracks energy consumption and establishes the efficiency of the infrastructure, helping organizations reduce their carbon footprint and operating costs.

Performance Enhancements

vSphere 8 Update 1 introduces several performance-enhancing features, including support for NVIDIA NVSwitch, a high-performance networking fabric designed for interconnecting multiple GPUs and servers in a data center environment. This feature allows for the connection of up to 8 GPUs to the same VM, providing a significant boost in performance for demanding workloads such as graphics rendering and scientific simulations.

Moreover, vSphere 8 Update 1 introduces support for 3rd party identity providers to Okta, enabling organizations to use their preferred identity provider for both vCenter and NSX Manager. This feature enhances the security and scalability of vSphere and NSX environments by providing more flexible and secure access control mechanisms.

Improved Scalability and Flexibility

vSphere 8 Update 1 offers several improvements that enhance the scalability and flexibility of vSphere environments. One such improvement is the introduction of vSAN ESA, which delivers enhanced value by providing Desired Configuration capabilities at the cluster level for vSphere hosts. This feature enables admins to monitor configuration drift and issue notifications for the administrator to act on and remediate.

Another notable improvement in vSphere 8 Update 1 is the support for different types of workloads on a single physical GPU, such as VDI, compute, graphics, and more. This feature enables organizations to optimize their GPU resources more efficiently and reduce costs by consolidating their GPU infrastructure.

Conclusion

In conclusion, vSphere 8 Update 1 brings several exciting features and improvements that can greatly benefit organizations of all sizes. From enhanced security and performance capabilities to improved scalability and flexibility, the new version offers a range of functionalities that can help businesses streamline their operations and improve their overall efficiency.

As a virtualization expert, I highly recommend that organizations running vSphere 8 upgrade to vSphere 8 Update 1 as soon as possible to take advantage of these new features and improvements. Additionally, businesses looking for options on how to protect their vSphere and VMware Cloud Director workloads should consider Nakivo Backup & Replication, which offers capabilities to back up vSphere VMs and VCD objects such as vApps, individual VMs, and vApp metadata, ensuring that remote workloads can be recovered in case of a data loss event.

Exploring Azure VMware Solution REST API with Az Rest

In part 1 of this series, we discovered the Azure VMware Solution (AVS) REST API through the Postman collection. In this post, we will delve deeper into the fundamentals of the API using az rest, a useful subset of the Azure Command-Line Interface. We will explore how to use az rest to manage an AVS instance and perform various actions on it.

Az Rest vs Postman

——————-

While both Postman and az rest can be used to discover and execute REST API calls, there are some advantages to using az rest. Here are a few reasons why:

1. Easier to use: Az rest is a command-line tool that provides a simpler way to execute REST API calls compared to Postman. You don’t need to manually provide authentication tokens or handle pagination.

2. Integrated with Azure CLI: Az rest is an integrated part of the Azure Command-Line Interface (CLI), which means you can use it to manage not only AVS but also other Azure resources.

3. Automation friendly: Az rest is designed for automation, making it easier to script and automate repetitive tasks.

4. Faster execution: Az rest executes REST API calls faster compared to Postman, especially when dealing with large datasets.

Getting Started with Az Rest

—————————–

To get started with az rest, you need to have the Azure CLI installed on your system. Once you have the Azure CLI installed, you can use the following command to open the AVS REST API documentation:

“`css

az rest –help

“`

This will open the AVS REST API documentation in your default web browser. From here, you can explore the various endpoints and actions available for managing an AVS instance.

Connecting to Your Tenant

————————-

Before you can start executing REST API calls, you need to connect to your Azure tenant. You can do this by using the following command:

“`bash

az rest –connect

“`

This will open a web browser and ask you to log in to your Azure tenant. Once you have logged in, you can close the web browser and continue with the REST API calls.

Retrieving Base URI for AVS Resources

————————————

To execute REST API calls on an AVS resource, you need to know its base URI. The base URI is built using the following components:

* `https://management.azure.com/subscriptions/`

* Your subscription ID

* `/resourceGroups/`

* Your resource group name

* `/providers/Microsoft.AVS/privateClouds/`

* Your AVS instance name

You can use the following command to retrieve the base URI for an AVS resource:

“`bash

az rest –get-base-uri

“`

For example, to retrieve the base URI for an AVS resource named `myavsinstance`, you would run the following command:

“`bash

az rest –get-base-uri myavsinstance

“`

This will print the base URI for the specified resource.

Executing REST API Calls with Az Rest

————————————-

Now that we have covered how to connect to your tenant and retrieve the base URI for an AVS resource, let’s dive into executing REST API calls using az rest. Here are some examples of common actions you can perform on an AVS instance:

* Create a new NSX-T segment: `az rest –post /providers/Microsoft.AVS/privateClouds//networking/segments –json={“displayName”:”my-new-segment”}`

* Read the details of an existing NSX-T segment: `az rest –get /providers/Microsoft.AVS/privateClouds//networking/segments/ –json`

* Update the settings of an existing NSX-T segment: `az rest –put /providers/Microsoft.AVS/privateClouds//networking/segments/ –json={“settings”:{ “vmotion-enabled”:true }}`

* Delete an existing NSX-T segment: `az rest –delete /providers/Microsoft.AVS/privateClouds//networking/segments/`

These are just a few examples of the many actions you can perform on an AVS instance using az rest. For a full list of available endpoints and actions, you can refer to the Azure VMware Solution REST API documentation.

Conclusion

———-

In this post, we explored how to use az rest to manage an Azure VMware Solution (AVS) instance and perform various actions on it. We also covered how to connect to your tenant and retrieve the base URI for an AVS resource. Az rest is a powerful tool that makes it easy to automate repetitive tasks and manage large AVS workloads with production and self-remediation requirements.

VMware vSphere 8: What’s New and Improved?

VMware vSphere 8 is the latest version of VMware’s virtualization platform, which provides a scalable, secure, and efficient infrastructure for running applications and workloads in a cloud environment. In this article, we will explore the new and improved features of vSphere 8 compared to previous versions.

1. DPU: DPU (Distributed Power Unit) is a new architecture introduced in vSphere 8 that allows for better performance and scalability. It replaces the traditional CPU and memory architecture with a unified architecture that provides more processing power and improved efficiency.

2. vSphere Lifecycle Management: vSphere Lifecycle Management (vLCM) is a new feature in vSphere 8 that enables automated management of the entire lifecycle of virtual machines, including provisioning, patching, and upgrading. It also provides better support for security and compliance.

3. Improved Performance: vSphere 8 includes several performance enhancements over previous versions, including better CPU and memory utilization, improved I/O performance, and faster boot times.

4. Enhanced Security: vSphere 8 includes several new security features, such as encrypted virtual machines, secure boot, and advanced threat protection. It also supports the latest security standards, including TLS 1.2 and PCI-DSS compliance.

5. Simplified Management: vSphere 8 provides a simplified management interface that makes it easier to manage and monitor virtual machines and infrastructure. This includes new features such as automatic VM sizing, improved vMotion performance, and better support for hybrid cloud environments.

6. Artificial Intelligence (AI) and Machine Learning (ML): vSphere 8 includes several AI- and ML-powered features that enable predictive maintenance, automated troubleshooting, and optimized resource allocation. These features use advanced algorithms to analyze performance data and identify potential issues before they occur.

7. Kubernetes Support: vSphere 8 provides built-in support for Kubernetes, which enables organizations to deploy containerized applications in a cloud environment. This includes support for Kubernetes networking, storage, and security policies.

8. Enhanced Networking: vSphere 8 includes several enhancements to the networking architecture, such as improved network performance, better support for east-west traffic, and expanded support for network virtualization.

9. Better Support for EUC: vSphere 8 provides better support for End-User Computing (EUC) environments, which are critical for modern workforces that rely on desktop and mobile devices. This includes improved support for Windows 10 and macOS, as well as better integration with EUC management tools.

10. Enhanced vSphere Distributed Services Engine: The vSphere Distributed Services Engine (DSE) is a new feature in vSphere 8 that provides a more scalable and efficient infrastructure for running distributed applications. It includes several enhancements over previous versions, such as improved load balancing, better support for multi-site deployments, and enhanced monitoring and troubleshooting capabilities.

In conclusion, VMware vSphere 8 offers several new and improved features compared to previous versions. These features provide better performance, security, management, and support for modern workloads and cloud environments. Organizations that adopt vSphere 8 can benefit from these enhancements to improve their overall virtualization infrastructure and reduce costs.

The Mysterious Case of Insufficient Resources: A Lesson in DRS Troubleshooting

As a seasoned IT professional, I have encountered my fair share of mysterious errors and unexpected behavior in virtualized environments. However, a recent case involving a DRS-enabled cluster left me stumped for a while. In this blog post, I will delve into the details of the issue, the troubleshooting process, and the solution that was eventually found.

The Case: Insufficient Resources? But Why?!

One day, one of my customers contacted me with an urgent request to troubleshoot an issue they were experiencing with their DRS-enabled cluster. When attempting to start a virtual machine, they were met with the generic error “Insufficient resources.” However, further checking revealed that there were plenty of resources available on all hosts in the cluster. This was puzzling, to say the least.

The usual questions that come to mind in such situations – “Is the host running out of memory?”, “Are there any resource contention issues?” – were all ruled out. The customer had already checked these and ensured that there were no obvious reasons for the error. That’s when I decided to dive into the Advanced Options of DRS, which is often overlooked but can provide valuable insights into unexpected behavior.

The Solution: A Less-Known Setting with Unintended Consequences

As I explored the Advanced Options of DRS, I stumbled upon a setting called “LimitVMsPerESXHostPercent.” This setting, which is not well-known and is often set to 0 by default, controls the maximum number of virtual machines that can be running on any given ESXi host. In this customer’s environment, the setting was still set to 0, which seemed to be causing the issue.

Removing the setting for testing purposes allowed the virtual machine to power on successfully, and DRS behavior returned to normal. It turned out that this setting had been causing unexpected side effects in the customer’s environment for quite some time!

The Takeaway: Check Those Advanced Options!

As IT professionals, we often overlook certain settings or options in our haste to troubleshoot issues. The case of LimitVMsPerESXHostPercent is a perfect example of this. It’s essential to remember that even the most obscure settings can have a significant impact on the behavior of our virtualized environments.

In conclusion, when encountering unexpected behavior in your DRS-enabled cluster, never hesitate to explore all available options and settings. You never know what hidden gem you might discover!

About the Author: Patrik Kernstock

Hello there! My name is Patrik Kernstock, and I’m a 25-year-old perfectionist born in Austria and living in Ireland, Cork. As a tech and security enthusiast, I enjoy exploring Linux, container solutions, and software offerings from Microsoft, Veeam, and VMware. When not working or troubleshooting, you can find me binge-watching series and movies or indulging in my love for Linux and open-source projects.

Thank you for providing a detailed step-by-step guide on creating a scheduled job in VMware Aria Operations Automation Central to clean up snapshot older than 7 days within vCenter Server. Your explanation of the features and options available within the wizard is very helpful for users who are new to the platform or looking to automate specific tasks.

I appreciate your cautionary notes about scheduling duplicate jobs too closely together and the potential impact on I/O against storage systems, as well as your suggestion for additional features such as running other actions against virtual machines or scheduling VMware Aria Automation Orchestrator workflows. These are all valuable points to consider when using Automation Central for automating tasks within vCenter Server.

Overall, your post provides a comprehensive and practical guide for users looking to automate clean-up of snapshot older than 7 days within vCenter Server using VMware Aria Operations Automation Central. I am confident that readers will find this informative and helpful in their own implementations.

As a seasoned infrastructure administrator, I have spent countless hours troubleshooting virtual storage area networks (vSAN) clusters and ensuring their optimal performance. One of the most valuable tools in my toolkit has been vSAN Health, which provides a comprehensive overview of the cluster’s health and alerts me to any potential issues. However, there have been times when an updated vSAN Health report did not indicate any problems, even though I knew that something was amiss. In this blog post, I will share one of the simplest ways to check historical vSAN Health data, which is to examine the log files in your vCenter.

The Log File Goldmine

One of the most underutilized resources for troubleshooting vSAN issues is the log file located at /var/log/vmware/vsan-health/vmware-vsan-health-summary-result.log. This file contains a wealth of information about the historical health of your vSAN cluster, including any errors or warnings that have occurred over time. By examining this log file, you can gain valuable insights into how your cluster has been performing and identify any trends or patterns that may indicate underlying issues.

For example, if you notice a sudden increase in the number of errors or warnings in the log file, it could be an indication that there is a problem with your vSAN configuration or that one of your hosts is experiencing hardware issues. By investigating these issues and addressing them promptly, you can help prevent more serious problems from occurring in the future.

How to Check Historical vSAN Health Data

Checking historical vSAN Health data in your log files is relatively straightforward. Here are the steps you can follow:

1. Open your vCenter server and navigate to the logs section.

2. Scroll down to the /var/log/vmware/vsan-health directory and open the vmware-vsan-health-summary-result.log file.

3. Use a text editor or an log analysis tool to search for any errors or warnings that have occurred over time.

4. Look for patterns or trends in the log data that may indicate underlying issues with your vSAN cluster.

5. Take note of any error messages or warning messages that may provide clues about the cause of the issue.

6. Use this information to identify potential problems and address them promptly.

Tips for Using Log Files Effectively

While examining log files can be a valuable tool for troubleshooting vSAN issues, it is important to use them effectively. Here are some tips to keep in mind:

1. Use a text editor or log analysis tool that can search and filter the log data easily. This will help you quickly identify any errors or warnings that have occurred over time.

2. Look for patterns or trends in the log data, as these can provide valuable clues about the cause of the issue.

3. Take note of any error messages or warning messages that may provide more information about the problem.

4. Use this information to identify potential problems and address them promptly.

5. Regularly review your log files to ensure that your vSAN cluster is performing optimally and to catch any issues before they become serious problems.

Conclusion

In conclusion, examining historical vSAN Health data in your log files can be a valuable tool for troubleshooting vSAN issues and ensuring the optimal performance of your virtual storage area network. By following the steps outlined above and using the tips provided, you can quickly and easily check historical vSAN Health data and identify any potential problems before they become serious issues. Regularly reviewing your log files is an important part of maintaining a healthy and high-performing vSAN cluster, and it is an essential skill for any infrastructure administrator to master.

OVN (Open Virtual Network): The Future of Virtual Networking

In the ever-evolving landscape of cloud computing, virtualization is at the forefront, and network management is a crucial aspect of this virtualized world. Among the array of tools and technologies available, OVN (Open Virtual Network) stands out as a powerful open-source program that simplifies and streamlines virtual network development and management. As a seasoned blogger and vExpert, I will delve into the realm of OVN and explore its features, advantages, and potential for transforming your virtual networking experience.

What is OVN?

OVN is an open-source software platform that enables you to control your virtual networks using abstractions similar to logical switches and routers. It sits atop Open vSwitch (OVS), a popular virtual switch, and acts as an interpreter, converting high-level network configurations into OpenFlow, the language that OVS speaks. This approach allows you to work with familiar network principles without getting bogged down in low-level flow programming complexities.

Advanced Features of OVN

OVN offers a wide range of features that set it apart from other virtual networking solutions. Some of these advanced features include:

1. Network Functions Virtualization (NFV): OVN supports NFV, allowing you to deploy network functions such as firewalls and load balancers as software-based virtual appliances.

2. Multi-tenancy: OVN provides support for multi-tenancy, enabling multiple virtual networks to coexist on the same physical infrastructure.

3. Network Segmentation: OVN allows you to segment your virtual networks into smaller, isolated segments, improving security and network performance.

4. SDN-based Networking: OVN is built on top of OpenFlow, making it an ideal solution for software-defined networking (SDN) environments.

5. Extensibility: OVN’s architecture is highly extensible, allowing developers to build custom plugins and integrations to extend its functionality.

Benefits of OVN

The benefits of using OVN are numerous and compelling. Some of the key advantages include:

1. Simplified Network Management: OVN’s abstractions and high-level APIs make it easier to manage virtual networks, reducing the complexity and time required for network administration.

2. Flexibility: With OVN, you can define your virtual networks using familiar network concepts like switches and routers, making it easier to transition from physical networking to virtual networking.

3. Scalability: OVN’s architecture is highly scalable, allowing you to build large-scale virtual networks with ease.

4. Open-source: As an open-source project, OVN is community-driven, and its source code is freely available for anyone to review, modify, and distribute.

5. Cost-effective: By leveraging open-source technology, OVN offers a cost-effective solution for virtual networking, reducing the financial burden of proprietary solutions.

Getting Started with OVN

If you’re new to OVN, getting started can seem daunting, but fear not! The project offers thorough documentation, tutorials, and a vibrant community to help you along the way. Here are some steps to get you started:

1. Familiarize yourself with OVN concepts and architecture.

2. Download and install OVN on your preferred hypervisor or cloud provider.

3. Create virtual networks using OVN’s high-level APIs or the command-line interface (CLI).

4. Deploy network functions such as firewalls and load balancers as software-based virtual appliances.

5. Explore OVN’s advanced features, such as network segmentation and SDN-based networking.

Conclusion

In conclusion, OVN is a powerful open-source program that streamlines and simplifies virtual network development and management. With its advanced features and benefits, OVN has the potential to transform your virtual networking experience. As a vExpert and seasoned blogger, I highly recommend exploring the world of OVN, discovering its possibilities, and taking control of your virtual domain. Embrace open-source collaboration, put user-friendliness first, and unleash the full potential of virtual networking with OVN.

5 Practical Steps to Secure Your Systems After the Alleged Windows XP Source Code Leak

The recent allegations of the Windows XP source code leak has left many of us in the tech community worried about the potential consequences. With millions of computers still running on this outdated operating system, the possibility of an increase in ransomware, malware, and denial of service bots is a real concern. As we move into a future where security threats are becoming more sophisticated, it’s essential to take practical steps to secure your systems. Here are five steps you can take to protect your systems and data:

1. Identify and Remediate Any Windows XP Systems in Your Environment

The first step is to identify and remediate any Windows XP systems in your environment. This includes not only desktop computers but also servers, medical devices, ATMs, and other embedded systems that may be running on Windows XP. It’s essential to prioritize the removal of these systems from your network as soon as possible.

2. Keep Your Systems Current and Patched

Keeping your systems current and patched is crucial in preventing security threats. Ensure that all your systems are updated with the latest security patches, especially for Windows 7 and Windows Server 2008/R2, which have just come off of support. This will help protect against known vulnerabilities that hackers could exploit.

3. Monitor for Suspicious Activity and Update Your Antivirus Software

Monitor your systems for suspicious activity, and update your antivirus software regularly to ensure it can detect the latest threats. Implementing a robust intrusion detection system can help you stay ahead of potential attacks.

4. Review Your Security Policies and Procedures

Review your security policies and procedures to ensure they are up-to-date and aligned with industry best practices. This includes implementing strong password policies, limiting administrative privileges, and segmenting your network to prevent lateral movement in case of a breach.

5. Consider Migrating to a Supported Operating System

Consider migrating to a supported operating system such as Windows 10 or Linux. These systems have more robust security features and receive regular updates to protect against emerging threats. Additionally, Microsoft’s End-of-Support for Windows 7, 2008(R2) has just passed, making it even more critical to upgrade your systems.

In conclusion, the alleged Windows XP source code leak is a significant concern for all of us in the tech community. By taking these practical steps to secure your systems, you can protect against potential security threats and ensure a safer digital environment for your organization. Remember, it’s essential to prioritize the removal of any Windows XP systems from your network, keep your systems current and patched, monitor for suspicious activity, review your security policies and procedures, and consider migrating to a supported operating system. Stay safe out there!

Configuring NSX ALB with Terraform: An Overview

As a VCDX #181, I recently had the opportunity to explore the use of Terraform for configuring NSX Application Load Balancers (ALB). In this blog post, I’ll provide an overview of the process and share my experiences with you.

Before we dive in, let me give you a brief background on NSX ALB. VMware NSX is a network virtualization platform that allows organizations to create flexible, scalable, and secure networks for their applications. Within NSX, the ALB is a critical component that enables load balancing and application delivery.

Terraform is an open-source tool that enables users to define infrastructure as code (IAC) and manage it across a variety of cloud and on-premises environments. By using Terraform with NSX ALB, we can automate the configuration and management of our load balancers, making it easier to deploy and maintain our applications.

Now, let’s take a look at the high-level overview of how to configure NSX ALB with Terraform:

1. Install and configure Terraform on your machine.

2. Define the NSX ALB configuration in a Terraform file.

3. Use Terraform to provision and configure the NSX ALB.

4. Verify the configuration and make any necessary adjustments.

5. Repeat the process for other environments, such as development, test, and production.

In the next part of this series, we’ll dive deeper into each step and explore the specifics of configuring NSX ALB with Terraform. We’ll cover topics such as:

* Creating and managing NSX ALB resources in Terraform

* Defining the NSX ALB configuration using Terraform modules

* Integrating Terraform with NSX to automate the load balancer provisioning process

* Best practices for managing NSX ALBs with Terraform

Stay tuned for part 2 of this series, where we’ll delve into the nitty-gritty details of configuring NSX ALB with Terraform. In the meantime, if you have any questions or feedback, please feel free to reach out to me on social media or through my website.

—

As a VCDX #181, I am passionate about helping organizations build and manage their networks with NSX and other VMware technologies. I share my knowledge and experiences through blog posts, videos, and social media, and I’m always looking for new ways to help others succeed in their networking journeys. Follow me on social media or visit my website to stay up-to-date on the latest network virtualization trends and best practices.