Increase CPU/Memory/DISK for a Active/Standby Service Engine Group
search cancel

Increase CPU/Memory/DISK for a Active/Standby Service Engine Group

book

Article ID: 430347

calendar_today

Updated On:

Products

VMware Avi Load Balancer

Issue/Introduction

This document is to explain how to increase CPU/DISK and Memory for a service engine in a Active/Standby SE group

Environment

Active-Standby SE group in vCenter/NSX-T Cloud

Resolution

This article provides a step-by-step procedure for increasing memory resources on an existing Service Engine Group. 

Prerequisites

  • vCenter Access: Ensure you have the necessary permissions to modify VM resources.

  • Controller CLI Access: You will need to execute switchover commands.

  • Health Check: Verify that the SE Group is in a healthy state and all Virtual Services are synchronized before starting.

  • Licenses: Please check available licenses core before increasing number of CPU for the service engine.

Procedure

Phase 1: Update the Secondary (Standby) Service Engine

  1. Shutdown: Power off the Secondary Service Engine via vCenter.

  2. Modify Resources: In vCenter, navigate to the VM settings and increase the cpu/memory/disk to the desired value.

  3. Power On: Start the Service Engine.

  4. Verification: Wait for the SE to reconnect to the Controller. Ensure all Virtual Services are properly placed and synchronized on this secondary SE.

Phase 2: Perform Traffic Switchover

Once the secondary SE is updated and healthy, you must migrate the primary traffic to it.

  1. Trigger Switchover: Log into the Controller CLI and execute the following command for the Active SE:

    switchover serviceengine <active_se_name>

    Note: Long standing connection with Service Engine will be dropped during the switchover of the service engine.

  2. Validate: Confirm that the standby SE (the one you just upgraded) has successfully taken over as the Primary for all Virtual Services.

  3. Switchover Event: Check the Service Engine Event to confirm if swhitchover command was executed successfully.

Phase 3: Update the Remaining Service Engine

  1. Shutdown: Power off the original Primary Service Engine (which is now in a standby role).

  2. Modify Resources: Increase the memory in vCenter to match the first SE.

  3. Power On: Start the Service Engine.

  4. Final Sync: Wait for the Controller to recognize the SE and for all Virtual Services to be placed back in a redundant configuration.

Important: Update SE Group Properties

To ensure that any new Service Engines created by the Controller (due to scale-out or recovery) have the correct specifications, you must update the SE Group template.

  • Navigate to Infrastructure > Cloud Resources -> Service Engine Group (Select correct cloud from drop down)

  • Edit the specific SE Group.

  • Update the CPU/DISK/Memory per SE field to match the new resources applied in vCenter.

 

Note: Failure to update the SE Group properties may result in resource mismatches if service engines are recreated.

Powered by Wolken Software