Service Engine failed to come up after the upgrade from 22.x to 30.x version

Products

• VMware Avi Load Balancer

Issue/Introduction

• Avi ALB Service Engine start crashing after upgrade from 22.1.x to 30.2.2-2p1 when SEs with more than 8GB memory configured with se_lro disabled under service engine group properties

Environment

VMware and NSX-T

Cause

• In scenarios where se_lro is explicitly disabled, the Service Engine (SE) fails to come up, and se_dp process on Service Engine is observed as defunct state.
• This issue involved SE crashes due to memory reservation exceeding allocated HugePages when SE_LRO is disabled in 30.x

Resolution

Workaround:

1. How to check if LRO is enabled/disabled on the SE interface

Login to Controller Shell Mode
  
[admin:]: > show serviceengine <SE-Name> interface | grep lro
| lro_on                                   | False                                                       |

2. How to Enable LRO for SE Group
    
Login to Controller Shell Mode

  > configure serviceenginegroup <SE-Group-Name>
  > se_lro
  > save
  
Verify if the SE LRO settings are saved
  [admin:]: > show serviceenginegroup <SE-Group-Name> | grep lro
  | se_lro                                  | True                                                   |

Please note that LRO is enabled on serviceenginegroup by default for supported environments, such as, VMware, NSX-T Cloud.

As It's SE-Group configurable property, The Service Engines  should be rebooted for this configuration to work after enable the LRO

Reference KB - https://techdocs.broadcom.com/us/en/vmware-security-load-balancing/avi-load-balancer/avi-load-balancer/30-2/vmware-avi-load-balancer-configuration-guide/vmware-nsx-advanced-load-balancer-configuration-guide-30-2--ditamap/se-advanced-networking/configuring-tso-gro-rss-.html

Fix Version: 30.2.2-2p3 and 30.2.3 (future release)