F5 to Avi Load Balancer Migration – Part 2: Migration Strategy Framework

In the first post of this series, I discussed the top reasons why an organization wants to move from F5 to Avi load balancer. In this post, I will discuss the migration strategy for a successful migration.

To migrate from F5 to Avi Load Balancer, VMware provides a free Avi Load Balancer Conversion Tool (ALBCT) that automates the translation of F5 BIG-IP configurations. The migration process involves using this tool to convert the F5 load balancer configuration and then cutting over traffic to the Avi-based environment.

Migration Strategy: An Eight-Stage Approach

The key to successful migration is meticulous planning, comprehensive testing, and leveraging Avi’s conversion tool to automate complex configuration transformations. With proper execution, organizations emerge with a modern, scalable, and easier-to-manage load balancing platform that supports their digital transformation initiatives.

The image below lists the various stages involved in the strategic planning for a successful migration.

Stage 1: Planning and Assessment

Before any technical work begins, thorough planning is essential.Read the rest

F5 to Avi Load Balancer Migration – Part 1: Introduction

Introduction

In today’s digital-first world, enterprises are under constant pressure to modernize infrastructure, adopt hybrid and multi-cloud architectures, and deliver applications faster.  As enterprises accelerate their digital transformation journey, legacy load-balancing infrastructure is becoming a bottleneck. The rise of cloud-native applications, containerization, and the need for operational simplicity have prompted many organizations to evaluate modern alternatives.

F5 BIG-IP, while robust, lacks the agility, automation capabilities, and cloud-native architecture that modern applications demand. On the other hand, Avi Load Balancer, a software-defined, cloud-native alternative, offers organizations the flexibility to evolve their infrastructure with minimal disruption.

In this blog, I will cover the key use cases driving migration from F5 to Avi Load Balancer.

Use Cases for F5 to Avi Migration

Migrating from F5 to Avi helps organizations modernize their application delivery infrastructure, reduce operational complexity, and achieve cloud agility. Below are some common use cases for F5 to Avi migration.

1. Cloud and Multi-Cloud Strategy Enablement

Organizations are adopting multi-cloud architectures to avoid vendor lock-in and leverage best-of-breed services across providers.Read the rest

VCF-9 – Part 10: Deploy VKS with NSX VPCs

Welcome to part 9 of the VCF-9 series. The previous post in this series discussed VPC networking in greater detail. In this post, I will demonstrate how to deploy vSphere Kubernetes Service (VKS) in an NSX VPC.

If you are not following along, I encourage you to read the earlier parts of this series from the links below:

1: VCF-9 Architecture & Deployment Models

2: VCF Installer Walk-through

3: VCF-9 Networking Models

4: NSX Edge Cluster Deployment

5: ESXi Host Commission in VCF

6: Deploying a Workload Domain

7: Deploy VCF Operations for Logs

8: VPC Creation with Centralized Networking

9: VPC Networking Deep Dive

VKS, when integrated with NSX VPCs, enables self-service, secure, and automated network and security consumption for Kubernetes clusters within an NSX Virtual Private Cloud (VPC). This approach provides users with a simplified, self-service model to manage network segments, security policies, and external connectivity for their applications, all within predefined infrastructure guardrails set by the administrator.Read the rest

VCF-9 – Part 9: VPC Networking Deep Dive

Welcome to part 9 of the VCF-9 series. The previous post in this series discussed how to create Virtual Private Clouds (VPCs) with centralized network connectivity. In this post, I will dive deep into the fundamentals of VPC networking. 

If you are not following along, I encourage you to read the earlier parts of this series from the links below:

1: VCF-9 Architecture & Deployment Models

2: VCF Installer Walk-through

3: VCF-9 Networking Models

4: NSX Edge Cluster Deployment

5: ESXi Host Commission in VCF

6: Deploying a Workload Domain

7: Deploy VCF Operations for Logs

8: VPC Creation with Centralized Networking

Part 3 of this series discussed the networking models in VCF-9. In the previous post, I covered the concepts of default transit gateway and VPC gateway, as well as the types of subnets that can be created in a VPC. It is essential to recall these concepts to comprehend VPC networking. Read the rest

VCF-9 – Part 8: Create VPC with Centralized Networking

Welcome to part 8 of the VCF-9 series. The previous post in this series discussed how to deploy VCF Operations for Logs and configure log forwarding for vSphere and NSX components.

In this post, I will discuss the creation of Virtual Private Clouds (VPCs) with centralized network connectivity. 

If you are not following along, I encourage you to read the earlier parts of this series from the links below:

1: VCF-9 Architecture & Deployment Models

2: VCF Installer Walk-through

3: VCF-9 Networking Models

4: NSX Edge Cluster Deployment

5: ESXi Host Commission in VCF

6: Deploying a Workload Domain

7: Deploy VCF Operations for Logs

The NSX VPC feature is not new and was first introduced in NSX 4.0. NSX VPCs provide multi-tenancy capabilities, as they offer networking and security services to multiple tenants that are completely isolated from one another. Access to networking constructs (T1 gateways, segments, etc.) is controlled via RBAC policies, and limits are enforced by assigning quotas to the objects that can be created inside a tenant. Read the rest

VCF-9 – Part 7: Deploy VCF Operations for Logs

Welcome to part 7 of the VCF-9 series. The previous post in this series discussed how to configure an online depot in VCF operations and download the product installation binaries. This post will discuss the steps of deploying an instance of VCF Operations for Logs and configuring vSphere and NSX integration for log forwarding.

If you are not following along, I encourage you to read the earlier parts of this series from the links below:

1: VCF-9 Architecture & Deployment Models

2: VCF Installer Walk-through

3: VCF-9 Networking Models

4: NSX Edge Cluster Deployment

5: ESXi Host Commission in VCF

6: Deploying a Workload Domain

7: Depot Configuration and Binary Management in VCF Operations

VCF Operations for Logs, formerly vRealize Log Insight, is a VMware solution for centralized log management and analysis within a VMware Cloud Foundation (VCF) environment. It provides deep visibility into operational issues, enabling faster troubleshooting and proactive issue detection.Read the rest

VCF 9 – Depot Configuration and Binary Management in VCF Operations

In older versions of VCF (4.x & 5.x), before you deploy any of the Aria suite components, you have to download the binaries online or download the binaries manually and upload them into VMware Aria Suite Lifecycle, followed by binary mapping. Then, you can leverage these binaries to install, upgrade, or patch products from the Aria suite.

In VCF 9, this functionality has been moved to the unified VCF Operations component. All VCF fleet-related configurations/tasks are now performed through the VCF Operations. Using VCF operations, you can configure an online depot (token-based) or an offline depot for binary management. A depot serves as a source for downloading installation, upgrade, and patch binaries. You must set up a depot before downloading and installing components like VCF Operations for Logs and VCF Operations for Networks.

Only one depot connection can be ACTIVE at a time. If a depot is already ACTIVE, you must disconnect it before switching the depot to Online or Offline.Read the rest

VCF-9 – Part 6: Deploying Workload Domain

Welcome to part 6 of the VCF-9 series. The previous post in this series discussed the ESXi host commissioning process. Now it’s time to put those hosts into action by creating a workload domain. This post will guide you on creating a new workload domain. 

If you are not following along, I encourage you to read the earlier parts of this series from the links below:

1: VCF-9 Architecture & Deployment Models

2: VCF Installer Walk-through

3: VCF-9 Networking Models

4: NSX Edge Cluster Deployment

5: ESXi Host Commission in VCF

A typical VCF deployment includes a management domain and one or more VI workload domains. Each VI workload domain can be configured with specific resources, network configurations, and policies to support its intended workloads. The VI workload domains are isolated from the management domain and are used for hosting business applications and providing cloud-like operations within a private data center.Read the rest

VCF-9 – Part 5: ESXi Host Commision – What’s Changed?

Welcome to part 5 of the VCF-9 series. The previous post in this series discussed the new method of deploying the Edge cluster and the transit gateway. In this post, I will discuss the process of commissioning an ESXi host.

If you are not following along, I encourage you to read the earlier parts of this series from the links below:

1: VCF-9 Architecture & Deployment Models

2: VCF Installer Walk-through

3: VCF-9 Networking Models

4: NSX Edge Cluster Deployment

In the VCF world, host commissioning refers to the process of adding physical servers (with ESXi installed) to the SDDC Manager inventory to create a pool of available capacity for workload domains and clusters. Starting with VCF-9, VMware has announced the deprecation of the SDDC manager and moved the majority of the day-1 & day-2 configurations to VCF operations. As part of this change, the process of ESXi host commissioning has also changed, and this feature has been moved to the vCenter server UI. Read the rest

VCF-9 – Part 4: NSX Edge Cluster Deployment

Welcome to part 4 of the VCF-9 series. The previous post in this series discussed the networking models (VPC Networking and Segment Networking) and the key differences between them. In this post, I will discuss deploying NSX Edges through a built-in wizard in the vCenter UI. 

If you are not following along, I encourage you to read the earlier parts of this series from the links below:

1: VCF-9 Architecture & Deployment Models

2: VCF Installer Walk-through

3: VCF-9 Networking Models

In previous VCF releases, NSX Edges were deployed through SDDC Manager using the UI/JSON. VCF-9 has introduced a newer way of deploying NSX Edge VMs, and the deployment can now be performed through vCenter UI to simplify the process, particularly for centralized external network connectivity. However, installation and configuration via the NSX Manager is still possible. 

You will notice one change when deploying Edges through vCenter Server, i.e., instead of creating a tier-1 gateway, the wizard deploys a Transit Gateway.Read the rest