Working From Anywhere with Advanced Load Balancing and VMware Horizon VDI

Confidential │ ©2021VMware,Inc.
Working From Anywhere
with
Advanced Load Balancing
and
VMware Horizon VDI
19th January 2021
Abhinav Modi
Mittali Chawla

Agenda
2
Introduction to NSX ALB (Avi)
Avi for Horizon VDI
Demo
Q&A

Confidential │ ©2021VMware,Inc. 3
App Analytics / Insights
Container Ingress Services
DNS and IP Address
Management (IPAM)
Web Application Firewall (WAF)
and App Security
Global Server Load Balancing
(GSLB)
Enterprise-gradeLoad
Balancing
Consistent L4-L7 enterprise-grade app services across multi-cloud environments
VMware NSX Advanced Load Balancer (Avi Networks)

Consistent L4-L7 enterprise-grade services across multi-cloud environments
VMware NSX Advanced Load Balancer (Avi Networks)
PowerfulApp Analytics /
Insights
Container Ingress Services
DNS and IP Address
Management (IPAM)
Web Application Firewall (WAF)
and App Security
Global Server Load Balancing
(GSLB)
Enterprise-gradeLoad
Balancing
NSX
Horizon(VDI)
vSphere/vCenter
Deliver
Any App
on
Any Cloud
with
One Platform
VCF
VMC
Tanzu
vRO/vRA
Every Horizon
deployment needs
load balancing. Avi
delivers integrated,
full-stack VMware VDI
solution

Enterprises rushing to enable remote workers cannot rely on legacy solutions
Business Continuity Challenges with Traditional Load Balancers
Takes Too Long To
Deploy
Hard to
Troubleshoot
• Takes from days to weeks to
procure/ provision
• Dependency on networking
team slows down provisioning
• Inconsistent deployment across
on-prem and clouds
• Need to manage each instance, no
automation
• No insights to troubleshoot user
experience issues
• Hard to troubleshoot remote
worker performance without
correlating IP with Geo locations
Expensive /
Overprovisioned
• Deployed as expensive active-standby
appliances – wastes capacity
• Significant increase in OPEX – need to
manage each instance, no automation
A
S 0%
25%

Can I have the Best of Both Worlds?
The legacy VEs and cloud provider solutions are an unacceptable compromise
Load Balancing Challenges/Tradeoffs in the Public Cloud
Legacy
Virtual
LB
offers
features
Cloud
Provider LB
offers
automation&
elasticity
?
Tradeoff operational simplicity,
automation, and cloud-native
capabilities
Tradeoff features (like WAF and
other enterprise features), multi-
cloud consistency, and portability

Go from monolithic appliances to elastic, multi-cloud application services fabric
Avi Networks – Modern, Scalable Architecture
Centralized Policies and Full Lifecycle Management
App Services
ControlPlane
Data Plane
SoftwareLoad Balancer Intelligent WAF Container Ingress
Avi Controller
Bare Metal Virtualized Containers
ON PREMISES PUBLIC CLOUD
SEPARATECONTROL & DATA
PLANE
ELASTICITY
Application Services Fabric
MULTI-CLOUD
ANALYTICS AUTOMATION

Public Cloud On-Premises
Avi Controller SaaS Overview
VMware
Managed
Customer
Managed
FASTER TIME-TO-VALUE
Easyon-ramp
OPERATIONAL SIMPLICITY
Proactive support
DEPLOYMENT FLEXIBILITY
Consistentexperience

Avi NSX ALB with Horizon
UAG
UAG
UAG
UAG
CS
CS
CS
CS
VM VM VM VM
VM VM VM VM
VMware vSphere
VM VM VM VM
VM VM VM VM
VM VM VM VM
Avi Controller
Avi Service
Engines
Horizon
ConnectionServers
HorizonDesktops
and RDS Hosts
Avi GSLB

Deliver virtual desktops and apps anywhere quickly and cost-effectively
Avi Networks and Horizon – Complete VMware VDI Solution
One-Click Deployments
No trouble tickets
Deploy Horizon in any cloud
Fastest LB Provisioning
Easy Troubleshooting
End-user Visibility
Application/SecurityAnalytics
PinpointPerformance Issues
Reduced Costs
Avi CCU license SKU
Product / Operational Savings
Elastic, on-demand scalability
Deploy on x86 servers or VMs

• All you need to know is number of users.
• No extra metric is required to decide the capacity of LB
• Eliminates the overhead of multiple metrics for a complete vDI solution
• Unified SKU for all features like LB,GSLB, WAF, advanced custom actions etc
User based SKU for Horizon use cases
Avi CCU SKU

Sample cost savings from an examplecustomer
NSX ALB (Avi Networks) – TCO Comparison vs. F5 Networks
3-year TCO F5 vs Avi
Savings of 30-35% on product and support, 60-65% including operations
$0
$200,000
$400,000
$600,000
$800,000
$1,000,000
$1,200,000
$1,400,000
F5 Networks Avi - VMware LB
Analytics
Central Management
x86 Server Costs
Product + Support
$925,082
$138,762
$138,762
$698,880
$20,000 $718,880
$1,202,606

How Avi is Better Than Legacy LBs (On-prem)
Competitive Summary
VDI Load Balancing Requirements
VMware NSX-ALB
(Avi Networks)
Hardware Load Balancers
(Virtual Appliances)
Enterprise-grade Load Balancing
Single point of control and policies forall load balancers across data
centers and clouds
Visibility and analytics for app performance, users, security
Automation and self-service (provisioning in minutes, automatic
capacity management
On-demand elasticity (auto-scale LBs and UAGs based on real time data)
Troubleshoot apps in a few clicks (misconfigured UAGs, slow responses,
down servers etc.)
Integrated and consistent “cloud-optimized” VDI deployments in private
and public clouds
Fully integrated deployments for public clouds
Eliminate overprovisioning of load balancers with A-A fabric
Cost of ownership (product and operational savings)

How Avi is Better Than Legacy LBs for HCoA
Competitive Summary
VMware NSX-ALB
(Avi Networks)
Legacy Load Balancers
(Virtual Appliances)
centers and clouds
capacity management
down servers etc.)
and public clouds

How Avi is Better Than Azure LB (Layer 4) for HCoA
Competitive Summary
VMware NSX-ALB
(Avi Networks)
Azure LB
centers and clouds
capacity management
down servers etc.)
and public clouds

• Deliver virtual desktops quickly to thousands of employees of
large newly acquired companies
• Avi’s elasticity and A-A configuration eliminated the challenge
of overprovisioning for worst-case scenario
• Avi platform simplifies VDI deployment and operations
– Single consolidated view of LB deployment
– Real time health of UAGs and Connection Servers
– End user insights
Virtual desktops provisioned in shortest time in the history of the company
VMware IT Delivers VDI Services In Record Time
“ Avi helped us deliver a large VDI
deployment in a day instead of
weeks with legacy load balancers. It
saves costs, simplifies ops, and gives
us great app and client insights.
Swapnil Hendre
Director of Solutions Engineering and Design

Avi for Load Balancing
Horizon On-premises

Avi for Load Balancing Horizon On-premises
HTML Access or
Horizon Client
DMZ
Connection
Server
UAG
Connection
Server
AviController
AviService Engine
Load Balancer
Horizon
UAG
Virtual
Desktops and
RDSH Apps
Internal
users
• Avi can be used in front of UAG and/or
ConnectionServers
• 3 design optionsavailableto use Avi
load balancer for UAG servers
Analytics-Driven, Elastic, Per-Tenant Load Balancing for VDI

Design Options to Use Avi LB for UAG Servers
At a glance
Design Option HTTPS/XML-API
via Avi
Blast/PCoIP
via Avi
Source IP
Persistence
mandatory
SSL
Termination
for L7
Remarks
L7+L4 virtual
service Shared
VIP
Yes Yes Yes Yes Most commonly used
design
L4 virtual service Yes Yes Yes No Required for
HIPAA/NIST compliance
and smart card
authentication
(n+1) VIP Yes No No Yes Hub sites behind
network address
translatedIP

Connection
Servers
Horizon Client
DMZ
Internet
UAGs
CS1
CS2
UAG2
UAG1
1. Primary Protocol
(XML-API)
2. Secondary Protocols
(Blast/PCoIP)
Virtual Desktops and RDSH
Apps
Avi Load
Balancer
L7+L4 VS
Single VIP with two Virtual Services
Key Points :
• L7 VS ( for XML-API) & L4 VS ( for
Blast/PCoIP) using shared VIP
• SSL terminationfor XML-API l on L7 VS
• SSL Re-encrypt to UAG
• Benefit - Rich analytics and metrics for
primaryprotocol

Connection
Servers
Horizon Client
DMZ
Internet
UAGs
CS1
CS2
UAG2
UAG1
1. Primary Protocol
(XML-API)
(Blast/PCoIP)
Apps
Avi Load
Balancer
L4 VS
Single L4 Virtual Service
Key Points :
• Single L4 VS - All protocolsvia same VS
• SSL terminationon UAG
• Primarily used for NIST, HIPAA
complianceor smart card authentication

Connection
Servers
Horizon Client
DMZ
Internet
UAGs
CS1
CS2
UAG2
UAG1
1. Primary Protocol
(XML-API)
(Blast/PCoIP)
VIP1
VIP2
VIP0
AviLoad Balancer
(n+1)VIP
Apps
n+1 VIP
Key Points :
• Secondary protocol to bypass load balancer
• Useful where source IP affinity is not preferable
• Requires n+1 Public IP add.;
n = No. of UAG servers and 1 is for LB VIP

Avi for HCoA

Horizon components managed by VMware
UAG1
UAG2
DMZ Subnet
Pod Manager(s)
Desktop Subnet
Microsoft Azure(Customer Subscription)
External Clients
Internal Clients
Desktops &
RDSH VMs
HCoA with Azure LB
(Default Deployment)

Horizon components managed by VMware
UAG1
UAG2
DMZ Subnet
Pod Manager(s)
Desktop Subnet
Microsoft Azure(Customer Subscription)
External Clients
Internal Clients
Desktops &
RDSH VMs
HCoA with Avi
(Customer Opt-in)
Avi is deployed and managed by the customer

26
Demo
A single application
services fabric across
multiple clouds
Virtualized Containers
BareMetal Virtualized Containers
Virtualized Containers
On-premises

Visibility and Analytics

The Only Load Balancer with Network Visibility

Unique Client Analytics – Simplify Troubleshooting

Drill Down to Each Transaction – Proactively Identify Issues

Thank You

Working From Anywhere with Advanced Load Balancing and VMware Horizon VDI

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Working From Anywhere with Advanced Load Balancing and VMware Horizon VDI

Similar to Working From Anywhere with Advanced Load Balancing and VMware Horizon VDI (20)

More from Avi Networks

More from Avi Networks (15)

Recently uploaded

Recently uploaded (20)