• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

virtuallyGhetto

  • About
  • Privacy
  • VMware Cloud
  • Home Lab
  • Nested Virtualization
  • Automation
    • VMware Kickstart
    • VMware API/SDK/CLI
    • VMware vMA/VIMA
    • VMware OVF / OVFTOOL
  • Apple Mac
  • VCSA
  • VSAN
You are here: Home / VMware Tanzu / Disabling vSphere with Tanzu does not delete NSX Advanced Load Balancer (NSX ALB) Service Engine (SE) VMs

Disabling vSphere with Tanzu does not delete NSX Advanced Load Balancer (NSX ALB) Service Engine (SE) VMs

03/31/2021 by William Lam Leave a Comment

While working on some automation to deploy a vSphere 7.0 Update 2 environment that has been configured with vSphere with Tanzu and NSX Advanced Load Balancer (NSX ALB), I noticed that when you disable Workload Management on a vSphere Cluster, the two NSX ALB Service Engine (SE) VMs were still left behind.


It turns out that this behavior is due to a default setting within NSX ALB that will NOT automatically delete the SE’s in the case there is a scaled up event which would then cause a re-deploy to happen. Instead, by default it is configured to wait 120 minutes (2hrs) before cleaning up.

If you wish to change this behavior, you can login to NSX ALB UI and navigate to Infrastructure->Service Engine->Advanced and update the “Delete Unused Service Engines After” to your desired value. Please note, that the shortest time interval to wait is 1 minute and if you set it to 0, it means the SE’s VMs not be deleted.


After saving this change, the next time you disable Workload Management, the SE VMs will automatically get cleaned based on the time interval you had configured.

More from my site

  • Automated Lab Deployment Script for vSphere with Tanzu using NSX Advanced Load Balancer (NSX ALB)
  • Automating default admin password change for NSX Advanced Load Balancer (NSX ALB)
  • How to deploy Knative to a Tanzu Kubernetes Grid (TKG) Cluster on both vSphere with Tanzu and TKG Multi-Cloud?
  • Why am I seeing HTTP communication status 404 error when configuring vSphere with Tanzu & how to fix?
  • Automating kubectl-vsphere login for vSphere with Tanzu
Share this...
  • Twitter
  • Facebook
  • Linkedin
  • Reddit
  • Pinterest

Filed Under: VMware Tanzu, vSphere Tagged With: AVI, NSX Advanced Load Balancer, vSphere with Tanzu

Reader Interactions

Thanks for the comment! Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

Author

William Lam is a Senior Staff Solution Architect working in the VMware Cloud team within the Cloud Services Business Unit (CSBU) at VMware. He focuses on Automation, Integration and Operation for the VMware Cloud Software Defined Datacenters (SDDC)

  • Email
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • Vimeo

Sponsors

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright © 2021 · Genesis Sample on Genesis Framework · WordPress · Log in