BugZero updated this defect 38 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
4/11/2024
NSX Advanced Load Balancer
No affected releases provided.
No fixed releases provided.
Auto enable of LRO post upgrade may cause Performance/packet loss issues if Preserve Client IP option is enabled in the Virtual Service.Bigger packets will be seen on SE capture if LRO knob is enabled on Service engine group in environments with IP Routing enabled .This will eventually cause ICMP Fragmentation Needed error.(as DF bit is set)
Starting with NSX Advanced Load Balancer 22.1.3 version, LRO is enabled on serviceenginegroup by default for supported environments, such as, Vmware/ NSX-T Cloud.LRO is a NIC offload which coalesces incoming packets to deliver larger packets to the stack. However, this shouldn’t be turned on for routing use-cases. Turning this on for routing use-case may cause ICMP Fragmentation Needed error as the MTU is lower than the coalesced larger packet.
The following are the CLI commands to determine if LRO is enabled at the Service Engine and the Service Engine Group level - [admin:<Ctrl IP>]: > show serviceengine <se-name> interface | grep lro | lro_on | True [admin:<Ctrl IP>]: > show serviceenginegroup <seg-name> | grep lro | se_lro | True We need to disable LRO at the SE group level. The following is the CLI to disable LRO on the SE Group level: [admin:<Ctrl IP>]: > configure serviceenginegroup Default-Group [admin:<Ctrl IP>]: serviceenginegroup> no se_lro [admin:<Ctrl IP>]: serviceenginegroup> save The service engines have to be rebooted for this configuration to take effect.Refer to the configuration guide for more information - https://avinetworks.com/docs/22.1/configuration-guide-tso-lro-gro-rss/#in-nsx-advanced-load-balancer
Not available