NSX Advanced Load Balancer 21.1.X Release Notes

Issues Resolved in 21.1.6 Patch Releases

Issues Resolved in 21.1.6-2p7

Release Date: 28 July 2023

• AV-171793: Virtual service logs may not load intermittently or exhibit delay in loading.
• AV-181548: TCP proxy protocol is not supported with override of application profile.
• AV-184284: Duplicated network names displayed in the UI causing inability to uniquely identify a network.

Issues Resolved in 21.1.6-2p6

Release Date: 21 June 2023

• AV-179167: False alerts about 100% license consumption may be displayed when license consumption is greater than the license capacity of the recently added license unit.
  For example, when the license units are added in values 2, 5, and 8 service units, the alert is displayed when consumption exceeds 8 since 8 is the recently added value. In case the order is 8, 5, and 2, the alert is displayed when the consumption exceeds 2.
• AV-178270: On changing the name of the GSLB service, it may transition to down state even when one or more pools belonging to the GSLB service are up.
• AV-168904: When a DNS virtual service is linked to a deactivated GSLB service and later deleted, it causes stale entries in the GSLB service DNS virtual service list. When such a GSLB service is enabled, it may cause SE failure or memory corruption.

Issues Resolved in 21.1.6-2p5

Release Date: 25 May 2022

• AV-136048: The rsync exclusion list contains hidden files, resulting in the hidden files being synced across Controllers.
• AV-178169: Cross-tenant error when persistence is enabled in a GSLB service.

Issues Resolved in 21.1.6-2p4

Release Date: 09 May 2022

• AV-166018: SE failure during boot-up due to race condition between SE-Agent and SE-log-agent.
• AV-170118: For DNS traffic over TCP in the case of pass-through, the TCP connection lingers for a longer duration because the load balancer expects either the client or the server to initiate the close.
• AV-172209: The packet corruption from the underlying kernel driver in PCAP mode AWS fast path resulting in a day 0 issue, when there’s an MSS mismatch between client/server.
• AV-175496: Service Engines are failing because the GSLB Service had multiple groups with the same name.

Issues Resolved in 21.1.6-2p3

Release Date: 21 March 2022

• AV-170744: License remains in escrow for up to 2 hours

Issues Resolved in 21.1.6-2p2

Release Date: 21 March 2022

• AV-172551: SE crashed when The NTLM server responded with a mismatched status code to the health monitor.
• AV-172397: Changes to reduce the memory footprint for PKIProfile CRLs in Controller processes.
• AV-171698: In some cases, WAF requests can become slow if client_request_max_body_size in the WAF Profile is set to high values.
• AV-168659: In a string group, if a prefix of the existing string is added, the prefix is not added to radix tree. This can lead wrong results in policy matches while performing the EQUALS operation.
• AV-164842: There are race conditions at hour boundaries between inserting metrics into the current table and dropping the previous metrics table, causing a dip in the metrics as they are not being written into the current table.

Issues Resolved in 21.1.6-2p1

Release Date: 28 February 2022

• AV-152343: Virtual Service placement is stuck at OPER_RESOURCES due to an internal race condition which clears the discovered networks on the virtual services.
• AV-164049: vCenter cloud creation fails to discover vCenter objects, if there are any distributed virtual port group with traffic filtering and marking feature enabled.
• AV-166890: The error message Default Secure Channel Certificate cannot be modified is seen when updating existing or creating new application certificates.
• AV-165613: Service time-out during certificate creation through the UI or API in a Controller with more than 1,000 certificates.
• AV-164156: Controller Service HealthScore manager fails due to an internal race condition with metrics database.

What’s New in 21.1.6

Release Date: 24 November 2022
To refer to the upgrade checklist, click here.

Cloud Connector

• AWS: Support for shared VPC
• Azure: Support for Dsv5-series flavour
• VMware: Enhanced vCenter cloud for better performance and support for Content Library.

Core LB Features

• Support for load balancing in the round-robin mode at a per-SE level instead of the default per core

Monitoring and Observability

• Support for real-time Prometheus API

System

• Allow value VS_TYPE_VH_SNI in the Basic tier

Web Application Firewall (WAF) and App Security

• Support to send Assertion Consumer Service (ACS) URL and index to the IDP as part of the auto-authentication

Issues Resolved in 21.1.6

• AV-139352: Virtual service switchover on ACI-based environment can lead to MAC-IP mapping flap, eventually leading to blocking of virtual IP address.
• AV-140199: For TLS client, handshake API does not work as expected when connections are terminated after a log server restarts.
• AV-142908: On failure of a macro-API containing a VSVIP change or a VSVIP post failure, the IP allocated is not released on failure.
• AV-145995: Possible configuration loss after a leader transitions to a follower, which was not replicating the configuration from the leader.
• AV-146153: IPAM auto-allocate function does not work properly in NSX Advanced Load Balancer when connected to an Infoblox IPAM source with a non-default network view and DNS view.
• AV-146774: When the albservicesconfig object is updated using the CLI or through the API, the timers for IP Reputation and App Signature are not triggered immediately. There is a subsequent delay depending upon the configured time interval for service.
• AV-147685: Postgres service on a leader is stuck, and hence it is not writing heartbeats to the database. The followers are not able to replicate the configuration.
• AV-147689: IP addresses allocated to a VS VIP is not released when the creation or update of VS VIP fails.
• AV-148238: Oracle client-based external health monitor may cause failure of other external health monitors due to excessive logging.
• AV-148423: Unable to create VIP from the UI in Azure cloud.
• AV-148598: High CPU usage observed while streaming logs to external server using se_log_agent because of frequent connection resets.
• AV-149146: Increased disk usage when application signature is enabled in the Pulse connector configuration.
• AV-149858: External logs are not received on the external server when the whole pod or container gets deleted or re-imaged.
• AV-150213: Frequent enabling and disabling of servers of a pool within a few seconds can cause loss of reporting of pool-server metrics on Service Engines with five or fewer virtual services placed on them.
• AV-151431: When connection multiplexing is disabled, persistence to a pool from prior requests can override the content-switching pool group selected by an HTTP request policy.
• AV-151469: Applying a TLS profile, configured with only TLS1.3 and TLS 1.3 ciphers, to a pool, results in virtual service failure with the reason Fault in SE.
• AV-151550: Upgrading a FIPS-enabled setup fails if the configuration was imported after FIPS mode was enabled.
• AV-151942: The API call to fetch transport nodes fails when the transport_zone_id filter is used.
• AV-152018: NSX Advanced Load Balancer does not display an error for duplicate VIP addresses.
• AV-152071: Controller service (security manager) fails as postgres database connection is not concurrency-safe.
• AV-152250: When using the Certificate Management profile to auto-renew certificates, auto-renewal of certificates is triggered multiple times until the certificate is deleted from the Controller.
• AV-152343: Virtual service placement gets stuck at OPER_RESOURCES due to an internal race condition which clears the discovered networks on the virtual service.
• AV-152444: Portal connector service logs can reveal user-sensitive information configured in the system configuration.
• AV-152581: Postfix package has a stale dependency on OpenSSL 1.1.1f in FIPS mode.
• AV-153196: When connection multiplexing is enabled, in the HTTP cookie mode of persistence, the cookie with the first request is not sent.
• AV-153627: The Service Engine might crash when disabling and enabling the virtual services sharing a pool after going into fault state.
• AV-153725: False alert about IP reputation and App Signature sync failure when a registered Controller is disconnected from the Pulse portal.
• AV-153739: vCenter discovery may get stuck when using a static IP address for SE data vNIC allocation.
• AV-154157: When using exclusions on a WAF policy with a case-insensitive, non-regex match on the path field, the performance of WAF goes down dramatically. This is especially the case if these exclusions are on a group level.
• AV-154173: Disabling debugging for a virtual service does not stop debug logs from being written by the Service Engine.
• AV-154511: Service Engine metrics vm_stats.avg_cpu_usage and vm_stats.avg_mem_usage are not populated to the UI.
• AV-154738: The Avi Controller does not fetch all the services/groups from the NSX-T manager.
• AV-155045: On an update to a virtual service with BGP peer labels configured, the virtual service briefly goes down and comes up, resulting in connection drops.
• AV-155117: Potential crash on Service Engines in DPDK mode supporting hot plug of network interfaces at interface detach.
• AV-155317: DPDK driver crashes with bond interfaces configured on LSC deployments containing a mix of Mellanox and other network interfaces.
• AV-155471: The Avi GCP cloud disables BFD on GCP cloud routers while creating a new VIP.
• AV-156737: The Avi NSX-T cloud UI does not display all the segments available for selection of data or management segments, when there are more than 1000 segments.
• AV-156741: Prometheus-metrics API does not fetch all metrics for cases when output exceeds the default dimension limit of 1000.
• AV-156979: SE group upgrade fails due to network disconnection when replicating se.pkg to the follower nodes.
• AV-157195: IP addresses allocated to a VS VIP are not released when the creation or update of VS VIP fails.
• AV-157419: Infoblox IPAM/DNS failing to use non-default dns_view.
• AV-157767: Over 4 billion packet transactions on a TCP connection can lead to a SE crash due to a counter overflow.
• AV-157866: Unable to change license type for an SE group on Azure cloud
• AV-157962: Caching incomplete objects received from the back-end server could lead to Service Engine failure if the connection to the server closes abnormally.
• AV-158267: Service Engine failure seen with NTLM requests with unicode characters in the username.
• AV-159203: Memory exhaustion on Service Engine will lead to Service Engine failure when attempting to establish a connection to the LDAP server.
• AV-159228: Virtual Service with only an EC certificate with OCSP stapling enabled can cause Service Engine failure.
• AV-159311: SE may fail due to connection memory allocation failures when processing buffered requests.
• AV-160898: False negatives observed for WAF CRS rules 941160, 941170, 941210, 941220, 941310, 941350 and 942190.
• AV-161287: Restart of an external server may cause se-log-agent to crash.
• AV-161432: When creating or editing an existing cloud of type VMware through the UI, the Create IPAM/ DNS screen opens behind the Create/Edit Cloud screen making it invisible.
• AV-168796: In the vCenter cloud, Service Engines might get assigned to Default-SEGroup instead of specified SEGroup.

Key Changes in 21.1.6

• Starting with NSX Advanced Load Balancer 21.1.6, DNS and IPAM profile should be created prior to configuring the cloud connector, using the Template > IPAM/DNS Profiles option for the following clouds:
  • vCenter
  • NSX-T
  • Linux Server
  • No Orchestrator

  Once the profiles are created, they can be referenced in the cloud connector configuration.
  Note: The above-mentioned changes are applicable only to NSX Advanced Load Balancer 21.1.x releases starting from 21.1.6.

• Network objects in NSX Advanced Load Balancer now sync with the name of the associated port group in vCenter. Previously, changing name of the port group and name of the network in NSX Advanced Load Balancer was independent of each other
• The Avi Controller OVA supports additional OVF properties. The following properties have been added to facilitate automated deployment of the Avi Controller by the NSX Manager in a future release:
  • NSX-T Node ID
  • NSX-T IP Address
  • Authentication token of NSX-T
  • NSX-T thumbprint
  • Hostname of Avi Controller

  These fields should be left blank in case of a direct deployment of the Avi Controller.

• NSX-T cloud deployment fails to perform virtual service placement when the management segment name is changed on NSX-T. Names of management and data networks imported from NSX-T will be updated on Avi Controller to match with name in NSX-T.
• Connections are terminated if the application profile is set as System-SSL-Application, and the session idle time is set as 10 minutes. Now the idle connection timeout for SSL connections is increased to 60 minutes.

Known Issue in 21.1.6

• AV-162591: Password/passphrase limitation - XSS special characters (‘>’ & ‘<’ ) are not supported for new configurations on NSX Advanced Load Balancer.

Checklist for Upgrade to NSX Advanced Load Balancer Version 21.1.6

Refer to this section before initiating upgrade.

• Upgrade to NSX Advanced Load Balancer version 21.1.6 is only supported from the following versions:
  

  • Version 18.2.6 through 18.2.13
  • Version 20.1.1 through 20.1.9
  • Version 21.1.1 through 21.1.5

• NSX Advanced Load Balancer no longer supports VMware vCenter version 5.5. The End of General Support for vSphere 5.5 by VMware was on September 29th, 2018, before upgrading to NSX Advanced Load Balancer version 21.1.1, it is recommended to upgrade to a current vCenter version. For more information, refer to the System Requirements article.

• Linux Server Cloud: OEL 6.9 reached the end of support in March 2021. Starting with NSX Advanced Load Balancer version 21.1.3, support for OEL 6.9 will be removed. If you are running OEL 6.9, upgrade to a supported Linux distribution before upgrading to NSX Advanced Load Balancer 21.1.3 or higher.

• vCenter Read Access cloud is deprecated in NSX Advanced Load Balancer 21.1.3. Support for vCenter Read Access has already been removed for 22.1.x versions. In the 21.1.x branch, removal of support to vCenter Read Access cloud will take effect from version 21.1.6. If you are using vCenter Read Access environment, it is recommended to migrate to vCenter Write Access or vCenter No Access.

• In case of Service Engine upgrade in a Nutanix Acropolis Hypervisor (AHV) environment, refer to the pre-upgrade changes.
  

• To transition the NSX Advanced Load Balancer Controller to the SaaS edition refer to Getting Started with NSX Advanced Load Balancer Cloud Services

  • Upgrade Avi Controller cluster to Avi version 21.1.4 (or later)
  • Disable Cloud Services (Pulse) if enabled,
  • Change License Tier from ENTERPRISE to ENTERPRISE_WITH_CLOUD_SERVICES
  • Register with VMware NSX Advanced Load Balancer Cloud Services (Pulse)

• RHEL 7.4 version for Linux server host is deprecated. If you are running RHEL 7.4, upgrade to a supported RHEL version before upgrading to NSX Advanced Load Balancer 21.1.6.

Issues Resolved in 21.1.5 Patch Releases

Issues Resolved in 21.1.5-3p1

Release Date: 16 December 2022

• AV-142908: On failure of a macro-API containing a VSVIP change or a VSVIP post failure, the IP allocated is not released on failure.
• AV-147689: IP addresses allocated to a VS VIP are not released when the creation or update of VS VIP fails.
• AV-149807: The vCenter cloud in NSX Advanced Load Balancer may go down during the resyncing process with the error “Resync failed with the vCenter” if the vCenter version is 7.0 or above.
• AV-153345: SE creation may fail in vCenter Cloud on vsphere 8.0 and higher.
• AV-155117: Potential crash on Service Engines in DPDK mode supporting hot plug of network interfaces at interface detac
• AV-155317: DPDK driver crash with bond interfaces configured on LSC deployments containing a mix of Mellanox and other network interfaces.

Issues Resolved in 21.1.5-2p4

Release Date: 11 April 2023

• AV-146774: When the albservicesconfig object is updated from CLI or through API, the timers for IP Reputation and App Signature are not triggered immediately, there is subsequent delay depending upon configured time interval for service.
• AV-147685: Postgres service on leader is stuck and hence it is not recording heartbeats to the database. The followers are not able to replicate the configuration.
• AV-152343: Virtual Service placement is stuck at OPER_RESOURCES due to an internal race condition which clears the discovered networks on the virtual services.
• AV-156765: Once Cloud Services get disconnected, it does not get connected without manual intervention.
• AV-160899: Persistence profile switch between App cookie and client IP can lead to SE failure.
• AV-162948: L3 encapsulation for a scaled-out UDP virtual service with the udp-per-pkt load balancing network profile may lead to SE failure.
• AV-166183: The filename format for Log Manager event-mapping index leads to scale and performance issues for event handling.
• AV-171698: In some cases, WAF requests can become slow if client_request_max_body_size in the WAF Profile is set to high values.
• AV-170811: Unable to switch from Enterprise with Cloud Services tier to Enterprise tier when licenses consumed is greater than what is available in Enterprise tier.

Issues Resolved in 21.1.5-2p3

Release Date: 25 January 2023

• AV-165248: From version 21.1.4 onwards, on disabling one of the VSes with shared VIP, NSX Advanced Load Balancer throw a config error if any of those VSes have child VSes.
• AV-162724: Symptoms: Selected subnet from multi-subnetted Networks, in VS-Vip create/edit modal, in Openstack cloud wont be matched with API info, as UI assumes a network in OStack can have one and only one subnet. Workarounds: No Workarounds possible from UI, can be configured only using API/CLI.
• AV-161259: SE failure when updating HTTP Policy sets to stop using IP Reputation database and when the SE handles HTTP persistent connections during the update.
• AV-160898: Under some conditions, in virtual services referring to a WAF policy in which WAF CRS is selected at the SE boot up, some rules in the CRS section of WAF do not run all transformations before evaluating a request causing false negatives in rules 941160, 941170, 941210, 941220, 941310, 941350 and 942190.
• AV-160593: When Client Insights for a virtual service is set to Active, the virtual service is vulnerable to an HTTP desync attack on the /__avirum__ endpoint.
• AV-156737: The Avi NSX-T cloud UI does not display all the segments available for selection for data or management segments when there are more than 1000 segments.

Issues Resolved in 21.1.5-2p2

Release Date: 06 October 2022

• AV-155317: DPDK driver crash with bond interfaces configured on LSC deployments containing a mix of Mellanox and other network interfaces.
• AV-155117: Potential crash on Service Engines in DPDK mode supporting hot plug of network interfaces at interface detach.
• AV-157195: IP addresses allocated to a VS VIP are not released when the creation or update of VS VIP fails.

  Issues Resolved in 21.1.5-2p1

Release Date: 06 September 2022

• AV-153345: SE creation may fail on vCenter Cloud 8.0 and higher.
• AV-153322: Support for load balancing in the round-robin mode at per-SE level instead of the default per core.
• AV-153196: When connection multiplexing is enabled , with http_cookie persistence enabled, the cookie with the first request is not sent.
• AV-151431: When connection multiplexing is disabled, persistence to a pool from prior request can override the content-switching pool group selected by an HTTP Request Policy.

What’s New in 21.1.5

Release Date: 11 August 2022
To refer to the upgrade checklist, click here.

Cloud Connector

• OpenStack: CLI support to tag OpenStack objects created by NSX Advanced Load Balancer .

• OpenStack: The option to enable caching for frequently used objects to improve performance and reduce load on OpenStack Controllers .

Core LB Features

• Support to pass along X-Accel headers to the HTTP response sent to the client .

Issues Resolved in 21.1.5

• AV-136469: When adding a GSLB pool member for a follower site through the NSX Advanced Load Balancer UI, clicking the Virtual Services drop down list displays an error VirtualService object not found!.

• AV-137080: BFD echo mode does not work with NSX Advanced Load Balancer.

• AV-140552: NSX-ALB versions 21.1.3, 21.1.4 with PODMAN based controller deployment, attaching to controller via cli container using “ssh cli@>controller-ip< -p >controller ssh port< do not work.

• AV-142030: Password reset link for admin account fails with the error message {error: “Invalid token”}.

• AV-142116: For Service Engines in DPDK mode of operation, incoming fragmented IPv4 packets, carrying TCP payload post-reassembly which get redirected to SE Linux interface exhibit an issue with IP checksum.

• AV-142174: Service Engine can fail if a virtual service is deleted while an ICAP request is being processed.

• AV-142620: Under VS VIP configuration, under Private IP, when the VIP Address Allocation Network is updated, the NSX Advanced Load Balancer UI retained the IP address associated with the network configured earlier.

• AV-143099: SSL certificate generation using ControlScripts for flows trying to connect to external SSL certificate authority (for example, LetsEncrypt, Venafi, Sectigo) may fail.

• AV-143121: With Infoblox IPAM, if an invalid domain is specified in the config, host record creation requests result in a timed-out error from Infoblox leading to the leader node UI and CLI getting unresponsive.

• AV-143198: Service Engine may fail if the L7 virtual service listening service is configured with L4 app profile using override_application_profile and is followed by the virtual service’s network profile update.

• AV-143227: On failure of a macro API containing a VSVIP change or a VSVIP post failure, the IP allocated is not released on failure.

• AV-143699: When using WAF and CRS rules, a CRS rule which is part of a default deactivated CRS group (for example, group CRS_950_Data_Leakages) is executed.

• AV-143825: Real-time metrics API response occasionally missing data for some virtual services.

• AV-143988: POST API call made to Macro API /api/macro containing GSLB objects errors out with the message ” error”: “_perf() got multiple values for keyword argument ‘defer_octavius_request’“.

• AV-144016: SE might crash when updating a WAF policy that is referenced by a virtual service in fault state, with open connections.

• AV-144235: In NSX-T, AWS, and Openstack environments, packet capture does not work on a virtual service when dedicated dispatcher is enabled on the SE.

• AV-144262: Creating/ updating IP address groups fails with the error {“error”: “Check checks.IpAddrGroupCheck Panicked!”} when UUID is present in the system configuration (ApiAccess and SshAccess).

• AV-144468: Upgrade failure in WaitUntilClusterReadyLocally task due to timeout on waiting for the image_manager queue.

• AV-144544: When using write-access Openstack Cloud Connector in large Openstack environments, Avi API can time out during bulk VSVIP operations.

• AV-144680: Duplicate floating IP is assigned to the VIPs in OpenStack Contrail environment.

• AV-144971: Updating large IP address groups can fail with a service timeout.

• AV-145264: Creating a DNS-type health monitor without filling the dns_monitor field (keeping the dns_mintor field blank) results in a failure.

• AV-145541: Service Engine failure when client resets the connection on an HTTP/2 request.

• AV-145696: When the virtual service VIP is deleted from the Controller, the corresponding AWS Route 53 records are not removed.

• AV-145954: Clients might receive the OCSP staple status as GOOD even though the certificate has expired.

• AV-146188: Deleting an FQDN from virtual service VIP deletes all the FQDNs of a VIP on AWS Route 53.

• AV-146493: Rate limiting is not functional in WAF rules.

• AV-146644: The error NUM_VIRTUALSERVICES: limit value 200, object count 200 is displayed when creating the 200th virtual service in UI of medium and large Controller sizes.

• AV-146999: SE may fail when a pool group has the option deactivate_primary_pool_on_down enabled and the primary pool is deleted from the pool group.

• AV-147679: NSX-T: The Virtual IP Placement Settings section in the virtual service configuration is unavailable through the NSX Advanced Load Balancer UI.

• AV-149537: The execution of the ControlScript se_grp_cleanup_old_spec_se fails resulting in the SEs using older instance flavor retaining older instance after the SE Group instance_flavor property is changed in an Azure cloud.

Key Changes in 21.1.5

• Only single X-forward-proto will be sent to the server. If the client request contains an X-forward-proto header, then NSX Advanced Load Balancer rewrites it.

• vCenter Read Access cloud is deprecated in NSX Advanced Load Balancer 21.1.3. Support for vCenter Read Access has already been removed for 22.1.x versions. In the 21.1.x branch, removal of support to vCenter Read Access cloud will take effect from version 21.1.6. If you are using vCenter Read Access environment, it is recommended to migrate to vCenter Write Access or vCenter No Access.

Known Issue in 21.1.5

• AV-155317: DPDK driver crash with bond interfaces configured on LSC deployments containing a mix of Mellanox and other network interfaces.

Checklist for Upgrade to NSX Advanced Load Balancer Version 21.1.5

Refer to this section before initiating upgrade.

• Upgrade to NSX Advanced Load Balancer version 21.1.5 is only supported from the following versions:
  

  • Version 18.2.6 through 18.2.13

  • Version 20.1.1 through 20.1.9

  • Version 21.1.1 through 21.1.4

• NSX Advanced Load Balancer no longer supports VMware vCenter version 5.5. The End of General Support for vSphere 5.5 by VMware was on September 29th,
  1. 
     Before upgrading to NSX Advanced Load Balancer version 21.1.1, it is recommended to upgrade to a current vCenter version. For more information, refer to the System Requirements article.

• Linux Server Cloud: OEL 6.9 reached the end of support in March 2021. Starting with NSX Advanced Load Balancer version 21.1.3, support for OEL 6.9 will be removed. If you are running OEL 6.9, upgrade to a supported Linux distribution before upgrading to NSX Advanced Load Balancer 21.1.3 or higher.

• vCenter Read Access cloud is deprecated in NSX Advanced Load Balancer 21.1.3. Support for vCenter Read Access has already been removed for 22.1.x versions. In the 21.1.x branch, removal of support to vCenter Read Access cloud will take effect from version 21.1.6. If you are using vCenter Read Access environment, it is recommended to migrate to vCenter Write Access or vCenter No Access.

• In case of Service Engine upgrade in a Nutanix Acropolis Hypervisor (AHV) environment, refer to the pre-upgrade changes.
  

• To transition the NSX Advanced Load Balancer Controller to the SaaS edition refer to Getting Started with NSX Advanced Load Balancer Cloud Services .

  • Upgrade Avi Controller cluster to Avi version 21.1.4 (or later)
  • Disable Cloud Services (Pulse) if enabled,
  • Change License Tier from ENTERPRISE to ENTERPRISE_WITH_CLOUD_SERVICES
  • Register with VMware NSX Advanced Load Balancer Cloud Services (Pulse)

Issues Resolved in 21.1.4 Patch Releases

Issues Resolved in 21.1.4-2p18

Release Date: 25 May 2023

• AV-136048: The rsync exclusion list contains hidden files, resulting in the hidden files being synced across Controllers.
• AV-167281: Invalid or non-UTF-8 characters when parsing metrics.
• AV-176511: Invalid or non-UTF-8 characters displayed when parsing metrics.

Issues Resolved in 21.1.4-2p17

Release Date: 31 March 2023

• AV-172840: Log Manager stall leads to unbounded task queue growth.
• AV-172220: Service Engine failure when using avi.http.response with two arguments in the RESP_FAILED DataScript event.
• AV-169781: OpenSSL-1.1.1f stack in the Controller and Service Engine is vulnerable to CVE-2023-0286
• AV-169464: Symptoms: OpenSSL-1.1.1f stack in the controller and service engine is vulnerable to CVE-2023-0286, CVE-2023-0215, and CVE-2022-4304.
• AV-149853: OpenSSL-1.1.1f stack fixes for CVE-2022-1292, CVE-2022-2068, and CVE-2022-2097

Issues Resolved in 21.1.4-2p16

Release Date: 22 March 2023

• AV-172793:The total mbuf clusters are reduced if HugePages are larger than 16G. This impact is noticed only on applying 21.1.4-2p14.
• AV-171698: In some cases, WAF requests can become slow if client_request_max_body_size in the WAF Profile is set to high values.
• AV-171587: Due to a race condition, when an SE disconnects and reconnects with the Controller some time later, the virtual service placed on that SE can end up in a state where it is placed on more SEs than the number of SEs requested configured in the SE Group.
  This state persists, and in the case of Parent-Child VS it can cause FQDN issues.
• AV-171222: When an SNI child virtual service with a DataScript in the CLIENT_SSL_PRE_CONNECT event is deleted while processing traffic, it results in Service Engine failure.

Issues Resolved in 21.1.4-2p15

Release Date: 04 March 2023

• AV-159102: Bot Management is unable to refresh UA entries due to disconnection with Avi Pulse service.
• AV-166887: Due to a race condition, if an SE is rebooted from vCenter, the SE might end up with duplicate static subnets configured on multiple VNICs.

Issues Resolved in 21.1.4-2p14

Release Date: 21 February 2023

• AV-147689: IP addresses allocated to a VS VIP are not released when the creation or update of VS VIP fails.
• AV-156765: On getting disconnected, Cloud Services requires manual intervention to reconnect.
• AV-157195: IP addresses allocated to a VS VIP are not released when the creation or update of VS VIP fails.
• AV-168742: NIC initialization fails in BM deployments as result of physical memory fragmentation.
• AV-168904: When a DNS virtual service is attached to a deactivated GSLB service and later deleted, it causes stale entries in the GSLB service DNS virtual service list. When such a GSLB service is enabled, it may cause SE failure or memory corruption.
• AV-169440: Disabling virtual service traffic in an NSX-T Cloud can take up to 5 minutes to take effect.
• AV-170116: When a DNS virtual service is bound to disabled GSLB services, on disabling and re-enabling of the DNS virtual service, the virtual service may get stuck in the OPER_DOWN state.

Issues Resolved in 21.1.4-2p13

Release Date: 19 January 2023

• AV-152343: Virtual Service placement is stuck at OPER_RESOURCES due to an internal race condition which clears the discovered networks on the virtual services.
• AV-160593: When Client Insights for a virtual service is set to Active, the virtual service is vulnerable to an HTTP desync attack on the /__avirum__ endpoint.
• AV-160898: Under some conditions, in virtual services referring to a WAF policy in which WAF CRS is selected at the SE boot up, some rules in the CRS section of WAF do not run all transformations before evaluating a request causing false negatives in rules 941160, 941170, 941210, 941220, 941310, 941350 and 942190.
• AV-161259: SE failure when updating HTTP Policy sets to stop using IP Reputation database and when the SE handles HTTP persistent connections during the update.

  Issues Resolved in 21.1.4-2p12

  Release Date: 29 November 2022
  

• AV-161344: In NSX Advanced Load Balancer versions 21.1.3 and 21.1.4 with Podman-based Controller deployment, binding to the Controller through the CLI container using ssh cli@<controller-ip> -p <controller ssh port> does not work.
• AV-160771: SE fails to come up due to memory fragmentation in DPDK mode when the packet buffer’s memory exceeds 16G. With this update, the packet buffers are reduced and the SE would be operational, but in a degraded mode. A host reboot is required for this update to take effect.
• AV-159311: Under memory pressure , SE may fail due to connection memory allocation failures when processing buffered requests.
• AV-159203: Memory exhaustion on Service Engine causes Service Engine failure when attempting to establish a connection to the LDAP server.
• AV-159182: During network downtime, packet buffers can get queued up causing packet buffer exhaustion leading to SE failure.
• AV-142174: Service Engine failure if a virtual service is deleted when processing an ICAP request.

Issues Resolved in 21.1.4-2p10

Release Date: 12 October 2022

• AV-156748: Virtual service can goes down with an error VIP requires access to network dvportgroup-xyz which does not exist in the infrastructure in vCenter version 7.0 and above.
• AV-154738: The Avi Controller does not fetch all the services/groups from NSX-T manager.
• AV-148598: High CPU SE log agent process without any traffic.

Issues Resolved in 21.1.4-2p9

Release Date: 27 September 2022

• AV-155045: On an Update to a virtual service with bgp_peer_labels configured, virtual service will be removed and added back immediately resulting in connection drops.
• AV-155117: Potential crash on Service Engines in DPDK mode supporting hot plug of network interfaces at interface detach.
• AV-151431: When connection multiplexing is disabled, persistence to a pool from the prior request can override the Content-Switching pool group selected by a HTTP Request Policy.
• AV-152343: Virtual service gets stuck in OPER_RESOURCES due to an internal race condition which clears the discovered networks on the VS.
• AV-155317: DPDK driver crashes with bond interfaces configured on LSC deployments containing a mix of Mellanox and other network interfaces.
• AV-153627: The service engine might crash when disabling and enabling the virtual services sharing pool after going into a fault state
• AV-153739: vCenter discovery may be stuck in one of the cases when using static_ip for SE data vnic allocation.

What’s New in 21.1.4-2p8

Release Date: 15 September 2022

• Azure: Support for Dv5 and Dsv5-series flavours.

  Issues Resolved in 21.1.4-2p8

• AV-154241: Support for Standard_*ds_v5 flavors for Azure.
• AV-152444: Portal connector service logs can reveal user-sensitive information configured in system configuration.
• AV-152064: Sensitive information regarding SNMP v3 passphrase gets exposed as plain text in maintenance.log file.
• AV-146774: When the albservicesconfig object is updated from CLI or through API, the timers for IP Reputation and App Signature are not triggered immediately, there is subsequent delay depending upon configured time interval for service.
• AV-146153: IPAM auto allocate function does not work properly in NSX Advanced Load Balancer when connected to an Infoblox IPAM source with non-default network view and DNS view.

Issues Resolved in 21.1.4-2p7

• AV-130347: Indexing errors causing log manager queue build up and controller cluster instability.
• AV-140199: For TLS client, handshake API does not work as expected when connection is terminated after log server restart.
• AV-143376: Logs are missing due to index error.
• AV-150135: A WAF policy is allowed to be attached to a Layer 4 virtual service or a DNS Virtual Service instead of Layer 7 virtual services only.
• AV-151469: SSL profile with only TLS1.3 protocol and TLS1.3 ciphers could cause a fault on the Service Engine.
• AV-152018: NSX Advanced Load Balancer does not throw an error in case of Duplicate VIP addresses.

Issues Resolved in 21.1.4-2p6

• AV-151942: The API call to fetch transport nodes fails when the transport_zone_id filter is used.

Issues Resolved in 21.1.4-2p5

Release Date: 09 August 2022

• AV-141800: Jobmanager sends API queries to all objects without filtering for VS DataScript APIs.
• AV-147689: IP addresses allocated to a VS VIP are not released when the creation or update of VS VIP fails.
• AV-148314: Addition of IPv6 SNAT IP fails if IPAM is configured with IPv4 address.
• AV-149537: The execution of the ControlScript se_grp_cleanup_old_spec_se fails resulting in the SEs using older instance flavor retaining older instance after the SE Group instance_flavor property is changed in an Azure cloud.
• AV-149807: The vCenter cloud in NSX Advanced Load Balancer may go down during the resyncing process with the error ** Resync failed with vCenter** if the vCenter version is 7.0 or higher.
• AV-149860: When override_application_profile_uuid is set on one of the virtual service’s service ports, configuration updates to the virtual service can cause the Virtual service to drop connections.

What’s New in 21.1.4-2p4

Release Date: 16 June 2022

• AV-145542: Experimental limited ENS backend support for full access deployments (Tech preview)

Issues Resolved in 21.1.4-2p4

• AV-146188: Deleting an FQDN from a VSVIP deletes all the FQDNs of a VIP on AWS
• AV-145696: Route53 DNS records are not deleted when the VSVIP is deleted from the Controller
• AV-144971: Updating large IpAddrGroups can fail with a Service Timeout
• AV-144544: API timeouts on OpenStack environment when VSVIP objects are created or deleted in bulk
• AV-140287: When sending RST packets, longstanding flows during upgrade leads to longer timeouts.
• AV-137080: BFD echo mode does not work with NSX Advanced Load Balancer
• AV-136469: Fixes error when adding a GSLB pool member for a site with a parent/child VSThe error VirtualService object not found! is displayed when adding a GSLB pool member for a site with a parent or child virtual services

Issues Resolved in 21.1.4-2p3

Release Date: 27 May 2022

• AV-139230: Connection closure time of a TCP session may increase when multiple DNS requests are pipelined by the client and the response is received from the pool member
• AV-142908: On failure of a macro-API containing a VSVIP change or a VSVIP post failure, the IP allocated is not released on failure.
• AV-143198: Service Engine may fail if the L7 virtual service listening service is configured with L4 app profile using override_application_profile and is followed by the virtual service’s network profile update
• AV-144235: Packet capture is not working on a virtual service when dedicated dispatcher is enabled on the SE
• AV-144468: Upgrade failure in WaitUntilClusterReadyLocally task due to timeout on waiting for the image_manager queue
• AV-144621: vCenter cloud discovery might fail with inventory state “VCENTER_INVENTORY_RETRIEVING_DC” in vCenter cloud version 7.0 an higher
• AV-144790: Do not throttle the logs in SE when client log settings are set to unlimited
• AV-145264: HealthMonitorChecks panicked while creating DNS type healthmonitor without dns_monitor
• AV-145541: Service Engine failure when client resets the connection on an HTTP/2 request
• AV-158550: No-access deployment of NSX Advanced Load Balancer in legacy HA mode in OpenStack environment sends a copy of the packet to standby SE, causing issues with virtual service traffic.

Issues Resolved in 21.1.4-2p2

Release Date: 12 May April 2022

• AV-144262: Unable to create/update IpAddrGroups, when any group UUID is present in ApiAccess/SshAccess in system configuration
• AV-143988: Macro API containing GSLB objects errors out
• AV-143897: Added support for kernel version 4.18.0-305.34.2.el8_4.x86_64
• AV-143099: SSL certificate generation using control scripts for flows trying to connect to external SSL certificate authority(for example, Let’s Encrypt, Venafi, Sectigo) may fail

What’s New in 21.1.4-2p1

Release Date: 05 May April 2022

• Support for real-time Prometheus API

Issue Resolved in 21.1.4-2p1

• AV-143825: Real-time metrics API response is missing data for some virtual services in random fashion.

What’s New in 21.1.4

Release Date: 07 April 2022
To refer to the upgrade checklist, click here.

Cloud Connector

• AWS: Support for the region ap-east-1

• AWS: New flavors introduced to support AWS regions

• NSX-T: Preserve Client IP Support for NSX-T Overlay

• OpenStack: Reduction in the number of API calls to OpenStack Neutron and Nova

Core LB Features

• Generic Routing Encapsulation (GRE) tunnel support for DSR Type L3 (Layer 3)

• Support for BGP peer label-based virtual service placement

• Layer 7: Support for HTTP/2 WebSocket

DNS/IPAM

• Infoblox IPAM: Multi-AZ support for AWS

Issues Resolved in 21.1.4

• AV-129536: vCenter cloud may fail with vCenter 7.0 and higher

• AV-130533: In a VMware cloud deployment with ESX version 7.x, Layer 2 DSR (Direct Server Return), TCP and, HTTP health monitor may fail due to incorrect checksum handling

• AV-131382: OpenStack floating IP subnet is not visible in the VSVIP configuration for an OpenStack cloud

• AV-132841: For HTTP2 connections sending a 307 redirect or local response for client requests, without making an upstream connection can result in a memory leak

• AV-132945: BGP peer configuration with # in the MD5 password might cause configuration failure

• AV-133050: Re-uploading the image may fail if cloud-generated SE files are present only in the leader node but not in the follower nodes

• AV-133110: In the cloud services portal, the used service units for a Controller may be updated with a maximum delay of one hour

• AV-133272: SE fails if a PKI profile having an expired certificate is updated

• AV-133276: SE creation may fail on vCenter cloud

• AV-133339: Azure: After upgrade to NSX Advanced Load Balancer version 21.1.3, virtual services are down due to SE health probe failures

• AV-133349: SSL Profile (UI): The cipher list in NSX Advanced Load Balancer version 21.1.3 displays a limited set of ciphers and erroneously hides the remaining, common ciphers

• AV-133902: When attaching a .dat file to the content switch policy, the virtual service fails with the error Out of memory

• AV-135875: Application profile creation is unsuccessful in the license tier ENTERPRISE_WITH_CLOUD_SERVICES

• AV-135894: Connection mirroring fails in multi-core SEs

• AV-136068: Service Engine fails due to a missing check in the memory allocation routine which gets triggered when Service Engine memory consumption goes high

• AV-136203: Upgrade to NSX Advanced Load Balancer version 21.1.3 may fail, if the current version has alerts configured with se_enable event_id as trigger/action

• AV-136539: Spinning SEs from Azure Market place does not work. All the offers have been invalidated.

• AV-136694: When importing an EC SSL certificate, and adding a passphrase, the EC encrypted private key is not exported as a string

• AV-136945: Increase in memory consumption in SE DPDK mode leads to SE start-up failure when extra_shm_cfg_memory_mb is configured

• AV-137461: If the SE management network is DHCP enabled, but there is an IP address pool configured in this network to use for VIP IPAM (with type static_ips_for_vip), SE creation fails with the error Service Engine management network xxxx configured for static, but no IP addresses available for use

• AV-137544: Custom IPAM assigns VIP only from the first subnet when configured via UI, and excludes the other subnets

• AV-137515: Due to a race condition in the Service Engine bring up sequence, incorrect interface mapping occurs for the HSM interface configured in the CSP environment

• AV-137713: GSLB Pool Member Resolved IP dropdown is not displayed after upgrading to 21.1.3

• AV-138269: Virtual services sharing the same Virtual IP, but asymmetrically placed across the Service Engines of the Service Engine Group (some can be on one single Service Engine) stop working after the Service Engine Group is upgraded

• AV-138278: Under SE group configuration, changes made in Data Store Scope in Service Engine Virtual Machine do not persist after clicking Save, specifically when Shared is selected at first and then changed to Any or ** Local**

• AV-138439: In an over provisioned system, Service Engine failure can occur when ‘se_delayed_flow_delete’ is set to * True*

• AV-138352: Multiple updates to the enhanced virtual service parent could result in failure when traffic is sent to its child virtual service

• AV-13857: Multiple certificates cannot be linked to EVH parent virtual services in the Basic tier

• AV-138428: When the Service Engine is processing configuration updates, a virtual service can transition into a fault state (due to memory pressure). Disabling or enabling the virtual service may lead to a Service Engine failure

• AV-138717: ControlScripts executed in a Controller in the Docker environment only supports ‘overlay2’ and ‘ devicemapper’ storage drivers

• AV-138792: Service Engine might fail with the combination of Error page configuration on failed requests and clients sending pipelined HTTP posts on the same frontend TCP connection

• AV-139248: In vCenter clouds, the Controller can add two vNICs on the SE, in the same VRF/network

• AV-139276: When configured via UI, Infoblox IPAM assigns VIP only from the first subnet, excluding the other subnets

• AV-140442: HTTP policy content switch fails for IPv6 servers

• AV-141095: Request timeout on a Virtual Service when the DataScript line avi.http.response(200) is called in the response event

• AV-141620: If the Resource Manager process is unable to connect to the Redis instance at port 5001, the process hangs instead of shutting down and restarting

• AV-143227: On failure of a macro API containing a VSVIP change or a VSVIP post failure, the IP allocated is not released on failure.

Key Changes in 21.1.4

• Prior to NSX Advanced Load Balancer version 20.1.3, .local domains were resolvable implicitly using the configured DNS server.
  Starting with NSX Advanced Load Balancer version 20.1.3, .local domains are not resolvable by default through the configured DNS server (local domains are not routed to DNS servers). The search domains need to be configured explicitly for “.local” domains to make lookups work within this DNS domain. For more information, see DNS-NTP Settings

• When certificate sharing is enabled, the Intermediate CA certificate with highest expiry in the current tenant is always selected. If there is no Intermediate CA certificate in the current tenant, then the corresponding Intermediate CA is selected from the admin tenant (if any)

• Search of usable networks in IPAM is now case insensitive

• EVH Parent virtual services in Basic tier can now refer to multiple SSL certificates

• ControlScripts that make API calls back to the Controller API using localhost must be updated to use the DOCKER_GATEWAY environment variable instead.

You can now apply any VMware NSX Advanced Load Balancer serial key license to the Avi Controllers .

Known Issues in 21.1.4

• AV-141493: When the Controller of version 21.1.3 or higher is configured with the ENTERPRISE_WITH_CLOUD_SERVICES tier, rolling back the Service Engines to a version lower than 21.1.3, results in failure of the corresponding SE.
  Workaround: Change the license tier to ENTERPRISE before rolling back the Service Engines.

• AV-140496: Virtual service goes into fault state when user-configured object names exceed 256 characters. See Checklist for upgrade.
  Workaround:
  1. Edit the object name to reduce the number of characters.
  2. Disable and enable the virtual service.

• AV-142641: Macro API for virtual service deletion does not support API migration below X-Avi-Version 20.1.1.

• AV-155317: DPDK driver crash with bond interfaces configured on LSC deployments containing a mix of Mellanox and other network interfaces.

Checklist for Upgrade to NSX Advanced Load Balancer Version 21.1.4

Refer to this section before initiating upgrade.

• Upgrade to NSX Advanced Load Balancer is only supported from the following versions:
  

  • Version 18.2.6 through 18.2.13

  • Version 20.1.1 through 20.1.8

  • Version 21.1.1 through 21.1.3

• Ensure the object names are limited to a maximum of 256 characters. To identify the objects with names exceeding 256 characters use the script available here.
  Note: This script only identifies the objects with names exceeding the 256 character-limit. You must manually edit the file names to reduce the number of characters.

• As a part of Ubuntu 20.04 migration, all search domains which need DNS resolution are explicitly specific. This is a deviation from DNS resolver (prior to ubuntu 20.04), where any and all DNS requests were sent to the DNS server. Update the search domain using the CLI if there are not more than one entities.

• NSX Advanced Load Balancer no longer supports VMware vCenter version 5.5. The End of General Support for vSphere 5.5 by VMware was on September 29th,
  1. 
     Before upgrading to NSX Advanced Load Balancer version 21.1.1, it is recommended to upgrade to a current vCenter version. For more information, refer to the System Requirements article.

• To transition the NSX Advanced Load Balancer Controller to the SaaS edition refer to Getting Started with NSX Advanced Load Balancer Cloud Services .

  • Upgrade Avi Controller cluster to Avi version 21.1.3 (or later)
  • Disable Cloud Services (Pulse) if enabled,
  • Change License Tier from ENTERPRISE to ENTERPRISE_WITH_CLOUD_SERVICES
  • Register with VMware NSX Advanced Load Balancer Cloud Services (Pulse)

• Linux Server Cloud: OEL 6.9 reached the end of support in March 2021. Starting with NSX Advanced Load Balancer version 21.1.3, support for OEL 6.9 will be removed. If you are running OEL 6.9, upgrade to a supported Linux distribution before upgrading to NSX Advanced Load Balancer 21.1.3 or higher.

• vCenter Read Access cloud is deprecated in NSX Advanced Load Balancer 21.1.3 and support for vCenter Read Access will be removed in a future release of NSX Advanced Load Balancer. If you are using vCenter Read Access environment, it is recommended to migrate to vCenter Write Access or vCenter No Access.

• In case of Service Engine upgrade in a Nutanix Acropolis Hypervisor (AHV) environment, refer to the pre-upgrade changes.

Issues Resolved in 21.1.3 Patch Releases

Issues Resolved in 21.1.3-2p20

Release Date: 23 May 2023

• AV-136048: The rsync exclusion list contains hidden files, resulting in the hidden files being synced across Controllers.
• AV-159552: Multiple event files are created due to frequent Auth Manager restarts.

---

Issue Resolved in 21.1.3-2p19

Release Date: 07 April 2023

• AV-130347: Indexing errors cause the log manager queue to build up and Controller cluster instability.

Issues Resolved in 21.1.3-2p18

Release Date: 23 March 2023

• AV-171698: In some cases, WAF requests can become slow if client_request_max_body_size in the WAF Profile is set to high values.
• AV-167281: Fixed handling of invalid or non-UTF-8 characters whilst parsing metrics.
• AV-156765: Once Cloud Services get disconnected, it does not get connected without manual intervention
• AV-142174: Service Engine failure if a virtual service is deleted while an ICAP request is being processed.

Issues Resolved in 21.1.3-2p17

• AV-166183: Filename format of the Analytics Engine’s event mapping index leads to scale and performance issues for event handling.
• AV-162948: L3 encapsulation for a scaled-out UDP virtual service with the udp-per-pkt load balancing network profile may lead to SE failure.

Issues Resolved in 21.1.3-2p16

Release Date: 27 December 2022

• AV-160899: Persistence profile switch between App cookie and client IP can lead to SE failure.
• AV-160898:Under some conditions, some rules in the CRS section of WAF does not run all transformations before evaluating a request. This can result in False Negatives in rules “941160”, “941170”, “941210”, “941220”, “941310”, “941350” and “942190”.
• AV-160593: When Client Insights for a virtual service is set to Active, the virtual service is vulnerable to an HTTP desync attack on the /__avirum__ endpoint.
• AV-151942: Fetching Transport nodes API failing when the transport_zone_id filter is used.

Issues Resolved in 21.1.3-2p15

Release Date: 27 October 2022

• AV-154300: Support to allow virtual service with VS_TYPE_VH_SNI in Basic tier to enable the solution to bypass the mandatory deletion of virtual service when switching to BASIC tier.
• AV-155117: Potential crash on Service Engines in DPDK mode supporting hot plug of network interfaces at interface detach.
• AV-155317: DPDK driver crash with bond interfaces configured on LSC deployments containing a mix of Mellanox and other network interfaces.
• AV-147685: Postgres service on leader is stuck and hence not writing heartbeats to the database. The followers are not able to replicate the configuration.

  Issues Resolved in 21.1.3-2p14

Release Date: 15 September 2022

• AV-146774: When the albservicesconfig object is updated from CLI or through API, the timers for IP Reputation and App Signature are not triggered immediately, there is subsequent delay depending upon configured time interval for service.

Issue Resolved in 21.1.3-2p13

Release Date: 09 September 2022

• AV-151431: When connection multiplexing is disabled, persistence to a pool from prior request can override the content-switching pool group selected by an HTTP Request Policy.

Issues Resolved in 21.1.3-2p12

Release Date: 22 August 2022

• AV-150320: With SSL session resumption enabled, the pool’s SSL is using a TLS ticket from an SSL session with failed PKI validation.
• AV-146774: When the albservicesconfig object is updated from CLI or through API, the timers for IP Reputation and App Signature are not triggered immediately, there is subsequent delay depending upon configured time interval for service.
• AV-145700: GSLB configuration changes made in an existing service is not syncing in the follower site.

Issues Resolved in 21.1.3-2p11

Release Date: 18 July 2022

• AV-148423: Unable to create VIP from the UI in Azure Cloud

Issues Resolved in 21.1.3-2p10

Release Date: 13 July 2022

• AV-148423: Unable to create VIP from the UI in Azure Cloud
• AV-147679: Placement network section is not displayed in the NSX-T VIP modal
• AV-145954: Clients might still receive OCSP staple status as GOOD even though the certificate has expired
• AV-141620: If Resource Manager process is unable to connect to Redis port 5001, it will hang instead of being properly shutdown and restarted
• AV-139528: The search filter function for adding usable networks in IPAM profile and for selecting VIP/server placement networks does not work

Issues Resolved in 21.1.3-2p9

Release Date: 22 June 2022

• AV-146188: Deleting an FQDN from a VSVIP deletes all the FQDNs of a VIP on AWS
• AV-145696: Route53 DNS records are not deleted when the VSVIP is deleted from the Controller
• AV-141435: Shell login fails when the number of TIMED_WAITING connections increase on the shell server
• AV-140287: When sending RST packets, long-standing flows during upgrade leads to longer timeouts

Key Change in 21.1.3-2p8

Release Date: 02 June 2022

• The capability to enable X-Accel headers to be passed the client is introduced using the flag pass_through_x_accel_headers.

Issues Resolved in 21.1.3-2p8

• AV-146000: When sending RST packets, long standing flows beyond 30 seconds during upgrade does not work on multi-core systems
• AV-136469: The error VirtualService object not found! is displayed when adding a GSLB pool member for a site with a parent or child virtual services

Issues Resolved in 21.1.3-2p7

Release Date: 25 May 2022

• AV-138131: Service Status Updated Object: error:“Access Denied” on all threat intelligence features (IP Reputation and AppSignature) led to repeated accumulation of large objects in logs as a consequence of repeated upstream sync updates from the portal, eventually causing the Controller to run out of disk space.
• AV-144468: Upgrade failure in WaitUntilClusterReadyLocally task due to timeout on waiting for image_manager queue.
• AV-135894: Controllers registered with Avi Pulse, with Application Rules enabled may run out of disk space.

Issue Resolved in 21.1.3-2p6

Release Date: 18 May 2022

• AV-138352: Multiple updates to enhanced virtual service parent could result in a crash when traffic is sent to its child virtual service.
• AV-141800: JobManager makes many invalid API queries

Issues Resolved in 21.1.3-2p5

Release Date: 17 May 2022

• AV-140273: Long standing flows are not RST during upgrade leading to longer timeouts
• AV-140768: Support for DLF v2 and v3
• AV-142116: When incoming fragmented IPv4 packets (carrying TCP payload) post-reassembly get redirected to SE Linux interface in DPDK mode of operation exhibit issue with IP checksum
• AV-142620: VIP retains the old IP address when changing the IP address
• AV-142624: Events and logs are timing out and new events/logs are not visible on the UI/API. When the log manager indexes a file, if the file is corrupted or not able to read the log from the file, the indexer is stuck in loops.
• AV-142680: Changes to handle remote LDAP user with username only in lowercase

Issues Resolved in 21.1.3-2p4

Release Date: 05 April 2022

• AV-140505: Virtual service fails after upgrading, if the value of Rules per HTTP Policy (num_rules_per_http_policy) exceeds 128
• AV-140442: HTTP policy content switch not fails for IPv6 servers

Issues Resolved in 21.1.3-2p3

Release Date: 20 March 2022

• AV-140366: Mitigation for CVE-2022-0778
• AV-139276: Infoblox IPAM assigns VIP only from the first subnet when configured via UI, it does not consider the other subnets
• AV-138357: Multiple certificates cannot be linked to EVH parent virtual services in Basic tier
• AV-137713: Dropdown to select resolved IPs is not rendered due to JavaScript Console error
• AV-137544: Custom IPAM assigns VIP only from the first subnet when configured via UI, it does not consider the other subnets
• AV-135875: User is unable to create an Application Profile due to a side effect from a new licensing tier that was added
• AV-135843: After applying the Controller patch, the indexer service fails
• AV-133276: SE creation attempt may fail on vCenter cloud
• AV-131382: Adds network selection for floating IP subnet in OpenStack cloud virtual service VIP configuration

Issues Resolved in 21.1.3-2p2

Release Date: 09 March 2022

21.1.3-2p2 is a renumber build for 21.1.3. All features available in 21.1.3 and 21.1.3-2p1 continue to be available, along with the fixes for the issues mentioned here.

Note: We recommend customers who have deployed 21.1.3 with Service Engines in a Linux Service Cloud environment to upgrade to 21.1.3-2p2 since the fix for AV-136945 is available in this build.

While 21.1.3-2p2 follows the patch numbering convention, it is a regular software maintenance build.
To install 21.1.3-2p2 as a new deployment, refer the installation guide for your environment.
To upgrade to 21.1.3-2p2, refer the Upgrade checklist for 21.1.3.

• AV-138428: When SE is processing configuration updates and the virtual service is put into fault state due to the SE being under memory pressure, disable/enable of the virtual service may lead to SE failure.
• AV-137515: Incorrect interface mapping with HSM interface configured in CSP environment causes failure in SE upgrade
• AV-137080: BFD echo mode does not work with NSX Advanced Load Balancer
• AV-136945: Increase in memory consumption in SE DPDK mode leading to SE start-up failure when extra_shm_cfg_memory_mb is configured.
• AV-136284: show virtualservice authstats did not return any output even when an LDAP Auth Profile was attached to the virtual service.
• AV-136203: Upgrade to NSX Advanced Load Balancer version 21.1.3 may fail, if the current version has alerts configured with with se_enable event_id as trigger/action.
• AV-136068: Service Engine failure due to insufficient memory.
• AV-135843: After applying the Controller patch, the indexer service fails.
• AV-134095: GCP pub/sub topic gets created on cloud reconfiguration even with no autoscaling groups present in Avi pools.
• AV-133360: Remote_site_watcher process can get stuck if there is a GRPC connection failure during resync process.
• AV-133272: SE fails if a PKI profile having an expired certificate is updated
• AV-132841: For HTTP2 connections, sending a 307 redirect or local response for client requests without making an upstream connection can result in a memory leak.
• AV-132736: Private keys uploaded as part of Certificate are explicitly moved to avoid disclosure with any GET APIs.
• AV-130533: In a VMware cloud deployment with ESX version 7.x, Layer 2 DSR (Direct Server Return), TCP and, HTTP health monitor may fail due to incorrect checksum handling.
• AV-126501: If jwt_config is not present in virtual service, it might lead to a config fault state.

Issues Resolved in 21.1.3-2p1

Release Date: 14 January 2022

• AV-131681: If the follower site is being upgraded without putting leader site in maintenance mode, config sync to remote site can fail.
• AV-133050: Re-uploading the image may fail if cloud generated SE files are present only in the leader node but not on the follower nodes.
• AV-133339: Azure: After upgrade to 21.1.3, Virtual services are down due to ALB-SE health probe failures.
• AV-133902: When attaching a .dat extension file to content switch policy, the virtual service goes to failure state with Out of memory error.

Known Issue in 21.1.3-2p1

• AV-133349: SSL Profile UI: The Cipher list in NSX Advanced Load Balancer version 21.1.3 displays a limited set of ciphers, and erroneously hides additional, common ciphers. Workaround: Do not modify / update an existing SSL profile post upgrade, via the GUI. Use CLI to modify the Ciphers if required.

• AV-155317: DPDK driver crash with bond interfaces configured on LSC deployments containing a mix of Mellanox and other network interfaces.

What’s New in 21.1.3

Release Date: 21 December 2021
To refer to the upgrade checklist, click here.

Application Security

• Detection of DNS NXDOMAIN DDoS Attack

• Support for custom bot classification

• Support for NSX Advanced Load Balancer to act as Client and Resource Server for Open Authentication(OAuth)/ OpenID Connect 1.0 (OIDC)

Avi Cloud Services

• Introducing VMware NSX Advanced Load Balancer with Cloud Services - available through a new License Tier called * Enterprise with Cloud Services.
  Note: Avi Pulse has been rebranded as *VMware NSX Advanced Load Balancer (Avi) Cloud Services

• Central Licensing will enable zero-touch capacity management and cloud bursting for globally distributed NSX Advanced Load Balancer deployments

Cloud Connector

• NSX-T: Preserve Client IP Support for NSX-T Overlay

  Note: This feature is currently under tech preview.

Core LB Features

• When vSphere High Availability is enabled, if the Controller detects that a vSphere host failure has occurred, SEs will transition to OPER_PARTITIONED or OPER_DOWN prior to missing six consecutive heartbeat misses .

• Support for True Client IP in Layer 7 security features.

• Enhancements in Content Rewrite Profile.

• Support to configure cookie timeout in GSLB site persistence cookies .

• Support to configure cookie timeout in HTTP persistence cookies .

• Support for LDAP Health monitor.

• Support to monitor the health of the FTP servers configured as pool members using HEALTH_MONITOR_FTP .

• Support to configure DNS resolution on SE.

• Support for active/standby topology at AZ level.

• Support to removes the existing cookie attributes in HTTP response using the DataScript avi.http.remove_cookie_attribute .

• Support to get pool IP and port through DataScript in a response event.

• Support schedule-based scale-out and scale-in of ASG Servers .

• UI support for JSON Web Tokens validation.

• L4 DataScript avi.pool.get_server_info() to return the server address and port for any request or response .

• L4 DataScript avi.pool.get_server_ip() to return the IP address of a request or response .

DNS/ IPAM

• Support to Process DNS Request both on SE and Backend Server in case of partial records .

GSLB

• Support to Adaptive Replication Mode in Replication Policy.

Horizon VDI

• Support for VDI WAF profile.

• Easy configuration and better analytics for UAG load balancing

  Note: This feature is currently under tech preview.

Networking

• Support for DPDK mode on Azure Service Engines .

• Virtual service failover upon BGP Peer failures via BGP peer monitoring.

• Support to show the state of BGP peers’ across all the VRFs configured in the SE.

Observability and Monitoring

Application Metrics

• Support to configure custom Controller utilization alert thresholds using CLI .

System

• Controller interface and route management.

• Support for SE Hybrid RSS mode to achieve higher performance on low core SE.

• Support to compare and verify pre/post upgrade operational state .

• Support for multiple queues per dispatcher in SE DPDK mode.

WAF

• Support to mask URI query parameters in Application logs.

• Support for string groups in WAF Allowlist.

• Support for configurable request body processors.

• Support for recommendations to help ascertain and remediate false positives .

Issues Resolved in 21.1.3

• AV-98655: TSO offload does not work if one of the member interfaces in inactive at the time of bond creation.

• AV-101483: GSLB configuration sync to other sites fail, if public IP is configured in the GSLB sites.

• AV-118805: VMXNET3 interface receive stalls due to packet buffer depletion.

• AV-121113: When GeoDB is added with a custom file object having IP Address Mapped to different GEO Attributes in non-ascending order, then rules using country code mapped IP Group in different policies will fail to add the IP Address in GeoDB custom file object into the IP group-generated country code files

• AV-122704: Controller cluster VIP may not be accessible after reboot on Contrail with OpenStack.

• AV-124867: Unable to mask query parameters in application logs

• AV-125094: Scanner Application Profile rate limiter with Report Only action was not captured in significant logs.

• AV-125824: If a bond exists on the management interface NICs (>=10G), it can be broken while stopping / restarting / upgrading the Service Engines in LSC deployments.

• AV-126508: BGP: Virtual service scale in can result in minor traffic disruption.

• AV-126754: Cluster VIP configuration fails in GCP cloud when the Controllers have Public IPs assigned to them.

• AV-127498: When the SE group is in a version lower than 20.1.5 and the Controller is in a version 20.1.5 or higher, the SE may fail if a pool has multiple resolve by DNS - based pool members and these pool members fail to resolve.

• AV-127802: Infoblox: When one of the virtual service VIPs is removed, the host record gets removed from the provider, even though there is still one virtual service VIP with that FQDN.

• AV-128044: When streaming request logs over Syslog format, the virtual service name is not included in the streamed logs.

• AV-128228: The SE_SYN_TABLE_HIGH alerts are seen for a large number of embryonic connections without the underlying system under attack or memory stress.

• AV-128339: If the GSLB site was configured with an FQDN instead of an IP address, the GSLB service page failed to render properly, and the URL to the member site was not generated correctly.

• AV-128707: The SE Agent process may leak an opened file descriptor and consume too much disk space.

• AV-128745: When a GSLB leader site is represented as an FQDN instead of the IP address, the GSLB configuration replication from leader to follower site does not work.

• AV-128843: Application traffic in a GSLB environment can get disrupted in upgrade scenarios in the following conditions:

  • GSLB service is configured with NO DATAPATH health monitors and relies on Controller-status.

  • GSLB federation is in maintenance mode

  • Site is upgraded to a newer version

• AV-128928: Server-initiated renegotiation fails for both Pools and HTTPS Health Monitor.

• AV-129063: The GeoDB object and the file objects are not recreated after upgrading to NSX Advanced Load Balancer Enterprise edition.

• AV-129080: NSX Advanced Load Balancer does not sign the SAML authentication requests despite SSL Key and certificate being attached to the SAML virtual service.

Key Changes in 21.1.3

• Avi Cloud Services
  Starting with NSX Advanced Load Balancer 21.1.3, the default license tier on a new Avi Controller deployment will change from ENTERPRISE to ENTERPRISE_WITH_CLOUD_SERVICES.
  To change this, from the NSX Advanced Load Balancer UI, navigate to Administration > Settings > Licensing .
  

• Installing VMware Serial Key Licenses

  • To use VMware Serial Key licenses purchased before December 23, 2021, on a new Avi Controller deployment running version 21.1.3 or later:
    1. Upgrade your VMware Serial Key licenses from the customer connect portal. For more information, refer How to Upgrade License Keys.
    2. Apply the upgraded license keys on the newly deployed Avi Controller.
       Notes:
    • If you run into any issues with applying licenses, reach out to your VMware sales representative and we will provide a license that can be applied on the Avi Controller and fulfil your request.
    • There is no action required on the Avi Controller deployments that are upgraded.
      
  • To use VMware Serial Key licenses purchased after December 23, 2021, on an existing Avi Controller deployment running version 21.1.2 or earlier:
    1. Downgrade your VMware Serial Key licenses from the customer connect portal. For more information, refer How to Downgrade License Keys.
    2. Apply the downgraded license keys on the newly deployed the Avi Controller.

Installing VMware Serial Key Licenses
To use VMware Serial Key licenses purchased before December 23, 2021, on a new Avi Controller deployment running version 21.1.3 or later:

1. Upgrade your VMware Serial Key licenses from the customer connect portal. For more information, refer How to Upgrade License Keys.
2. Apply the upgraded license keys on the newly deployed Avi Controller.

If you run into any issues applying licenses, reach out to your VMware sales representative and we will provide a license that can be applied on the Avi Controller and fulfil your request.
Note: There is no action required on the Avi Controller deployments that are upgraded.

• FQDNs need to be configured for successful registration of NSX Advanced Load Balancer Controllers with Cloud Services.

• DNS configuration in systemconfigurationtakes effect even in container-based deployments (Podman/ Docker).

• The Avi server side now allows SSL renegotiation request from the backend server.

• The user-agent check in Bot management allows user-agent strings with an uneven number of single quotes. For instance, Mozilla/5.0 (compatible; Let’s Encrypt validation server; +https://www.letsencrypt.org).

• If a user-defined bot mapping is specified in a bot detection policy, the system bot mapping reference can be left empty.

• RBAC: Roles can only be created in admin tenant only.

• On Controller container deployment, the default DNS config from the host is inherited. This can be overridden by user configuration using system configuration.

• If the admin_auth_profile is set to LDAP, after upgrading to version 21.1.3 all remote users which are not in lowercase will be removed from the system along with their auth tokens. Going forward, all LDAP users will be created in lowercase instead of being case sensitive.

Ecosystem Changes

• Linux Server Cloud: OEL 6.9 reached end of support in March 2021. Starting with NSX Advanced Load Balancer version 21.1.3, OEL 6.9 is no longer supported. If you are running OEL 6.9, upgrade to a supported Linux distribution before upgrading to NSX Advanced Load Balancer 21.1.3.

• vCenter Read Access cloud is deprecated in NSX Advanced Load Balancer 21.1.3 and support for vCenter Read Access will be removed in a future release of NSX Advanced Load Balancer. If you are using vCenter Read Access environment, it is recommended to migrate to vCenter Write Access or vCenter No Access.

Known Issues in 21.1.3

• The license tier ENTERPRISE_WITH_CLOUD_SERVICES is incompatible with older versions of SEs: If the Controller is on version 21.1.3 or higher and the Service Engines are on versions lower than 21.1.3, this causes Service Engine failure. As a consequence, the virtual services placed on the respective service engines will be down.
  Note: Do not configure ENTERPRISE_WITH_CLOUD_SERVICES if the Service Engines are running versions lower than 21.1.3.

• SSL Profile UI: The Cipher List in NSX Advanced Load Balancer 21.1.3 displays a limited set of ciphers, and erroneously hides the additional, common ciphers.
  Workaround: Do not modify/update an existing SSL profile post upgrade, through the GUI. Use CLI to modify the Ciphers, if required.

• Increase in memory consumption in SE DPDK mode leading to SE start-up failure.
  

• DPDK driver crash with bond interfaces configured on LSC deployments containing a mix of Mellanox and other network interfaces.

• Macro API for virtual service deletion does not support API migration below X-Avi-Version 20.1.1.

Checklist for Upgrade to NSX Advanced Load Balancer Version 21.1.3

Refer to this section before initiating upgrade.

• Upgrade to NSX Advanced Load Balancer is only supported from the following versions:
  

  • Version 18.2.6 through 18.2.13

  • Version 20.1.1 through 20.1.7

  • Version 21.1.1 and 21.1.2

• NSX Advanced Load Balancer no longer supports VMware vCenter version 5.5. The End of General Support for vSphere 5.5 by VMware was on September 29th,
  1. 
     Before upgrading to NSX Advanced Load Balancer version 21.1.1, it is recommended to upgrade to a current vCenter version. For more information, refer to the System Requirements article.

• To transition the NSX Advanced Load Balancer Controller to the SaaS edition refer to Getting Started with NSX Advanced Load Balancer Cloud Services .

  • Upgrade Avi Controller cluster to Avi version 21.1.3 (or later)
  • Disable Cloud Services (Pulse) if enabled,
  • Change License Tier from ENTERPRISE to ENTERPRISE_WITH_CLOUD_SERVICES
  • Register with VMware NSX Advanced Load Balancer Cloud Services (Pulse)

• Linux Server Cloud: OEL 6.9 reached end of support in March 2021. Starting with NSX Advanced Load Balancer version 21.1.3, support for OEL 6.9 will be removed. If you are running OEL 6.9, upgrade to a supported Linux distribution before upgrading to NSX Advanced Load Balancer 21.1.3.

• vCenter Read Access cloud is deprecated in NSX Advanced Load Balancer 21.1.3 and support for vCenter Read Access will be removed in a future release of NSX Advanced Load Balancer. If you are using vCenter Read Access environment, it is recommended to migrate to vCenter Write Access or vCenter No Access.

• In case of Service Engine upgrade in a Nutanix Acropolis Hypervisor (AHV) environment, refer to the pre-upgrade changes.
  

Issues Resolved in 21.1.2 Patch Releases

Issues Resolved in 21.1.2-2p18

Release Date: 12 July 2023

• AV-182830: L4 SSL DataScripts with request or response events may cause SE failure.
• AV-181508: Remote site watcher exceptions when the leader and follower are in different versions.
• AV-145700: GSLB services are not syncing to the follower site.

Issue Resolved in 21.1.2-2p17

Release Date: 07 April 2023

• AV-166018: SE failure during boot-up due to race condition between SE-Agent and SE-log-agent.

Issues Resolved in 21.1.2-2p16

Release Date: 27 December 2022

• AV-151942: The API to fetch transport nodes fails when the transport_zone_id filter is used.
• AV-160593: When Client Insights for a virtual service is set to Active, the virtual service is vulnerable to an HTTP desync attack on the /__avirum__ endpoint.
• AV-160898: Under some conditions, in virtual services referring to a WAF policy in which WAF CRS is selected at the SE boot up, some rules in the CRS section of WAF do not run all transformations before evaluating a request causing false negatives in rules 941160, 941170, 941210, 941220, 941310, 941350 and 942190.
• AV-160899: Switching th persistence profile between App cookie and client IP can lead to SE failure.

Issues Resolved in 21.1.2-2p16

• AV-171698: In some cases, WAF requests can become slow if client_request_max_body_size in the WAF Profile is set to high values.
• AV-156765: Once Cloud Services get disconnected, it does not get connected without manual intervention

Issues Resolved in 21.1.2-2p15

Release Date: 23 December 2022

• AV-149807: The vCenter cloud in NSX Advanced Load Balancer may go down during the resyncing process with the error Resync failed with the vCenter if the vCenter version is 7.0 or above.
• AV-155317: DPDK driver crash with bond interfaces configured on LSC deployments containing a mix of Mellanox and other network interfaces.
• AV-157797: Support for SSL Session ID persistence using DataScripts. Any changes made to Default-TLS DataScript template through UI will be overwritten by latest Default-TLS with this upgrade.
• AV-160593: When Client Insights for a virtual service is set to Active, the virtual service is vulnerable to an HTTP desync attack on the /__avirum__ endpoint.

Issues Resolved in 21.1.2-2p14

Release Date: 19 September 2022

• AV-146774: When the albservicesconfig object is updated from CLI or through API, the timers for IP Reputation and App Signature are not triggered immediately. There is a delay depending on the configured time interval for service.

Issues Resolved in 21.1.2-2p13

Release Date: 09 September 2022

• AV-151469: SSL profile with only TLS1.3 protocol and TLS1.3 ciphers could cause a fault on the Service Engine.
• AV-152444: Portal connector service logs can reveal user-sensitive information configured in system configuration.
• AV-152064: Sensitive information regarding SNMP v3 passphrase gets exposed as plain text in maintenance.log file.

Issues Resolved in 21.1.2-2p12

Release Date: 22 August 2022

• AV-150877: When application profile is System-SSL-Application, connections are terminated if the session is idle for 10 mins.

Issues Resolved in 21.1.2-2p10

Release Date: 11 July 2022

• AV-142624: Events and logs are timing out and new events/logs are not visible on the UI/API. When the log manager indexes a file, if the file is corrupted or not able to read the log from the file, the indexer is stuck in loops.
• AV-141620: If Resource Manager process is unable to connect to Redis port 5001, it will hang instead of being properly shutdown and restarted.

Issue Resolved in 21.1.2-2p9

Release Date: 09 June 2022

• AV-136469: The error VirtualService object not found when adding a GSLB pool member for a site with a parent/child virtual service.

Issue Resolved in 21.1.2-2p8

Release Date: 02 June 2022

• AV-136539: Spinning SEs from Azure market place does not work. All the offers have been invalidated.

Issues Resolved in 21.1.2-2p7

Release Date: 22 March 2022

• AV-138352: Multiple updates to enhanced virtual service parent could result in a crash when traffic is sent to its child virtual service.
• AV-135843: After applying the Controller patch, the indexer service fails.

Issues Resolved in 21.1.2-2p6

Release Date: 2 March 2022

• AV-136694: When importing an EC SSL certificate, and adding a passphrase, the EC encrypted private key is not exported as a string.
• AV-136068: Service Engine failure due to insufficient memory.
• AV-135843: After applying the Controller patch the indexer service fails.
• AV-132736: Private-keys uploaded as part of Certificate are explicitly moved to avoid disclosure with any GET APIs.
• AV-131472: Auto-download of CRS via Pulse fails
• AV-130199: GSLB sites go out of sync with “Controller Faults Deprecated API version in use. The minimum api version supported is 18.2.6. Please check events for details.”

Issues Resolved in 21.1.2-2p5

Release Date: 22 December 2021

• AV-132122: RSS does not work for Mellanox ConnectX-4 VLAN interfaces

What’s New in 21.1.2-2p4

Release Date: 12 December 2021

• RSS support for LSC cloud deployments on VMware virtual machines.

Issues Resolved in 21.1.2-2p4

• AV-129063: The GeoDB object and file objects are not recreated after upgrade to the Enterprise tier.

• AV-130838: Issue with TCP checksum offload.

• AV-131554: Service Engine failure occurs when a misconfigured SSL profile is attached to a pool.

• AV-130669: Cloud UUID is not populated correctly due to which DNS resolution on SE fails.

• AV-132339: Incorrect accounting of opackets & obytes of interface statistics in non-DPDK mode.

• AV-132431: Mitigation for CVE-2021-44228.

What’s New in 21.1.2-2p3

Release Date: 26 November 2021

• AV-130700: LSC DPDK mode support to handle memory fragments for hosts with greater than 256 GB memory.

Issues Resolved in 21.1.2-2p3

• AV-128928: Server-initiated renegotiation was disabled in 20.1.5. This results in Server-initiated renegotiation failures for both Pools and HTTPS health monitor.

• AV-129080: NSX Advanced Load Balancer does not sign the SAML authentication requests despite SSL Key and certificate being attached to the SAML virtual service.

• AV-129171: With Linux Server Cloud and Avi or Infoblox IPAM configured in a scaled setup, the virtual service placement can get stuck due to unnecessary attached IP RPCs being issued and these RPCs timing out.

• AV-130327: GSLB configuration sync fails when site is represented by Cluster-VIP/FQDN/public-network address translated IPs.

• AV-127498: When the SE group is in a version lower than 20.1.5 and the Controller is in a version 20.1.5 or higher, the SE may fail if a pool has multiple resolve by DNS - based pool members and these pool members fail to resolve.

What’s New in 21.1.2-2p2

Release Date: 03 November 2021

• AV-128013: Support for kernel version 3.10.0-1160.45.1.el7.x86_64

Issues Resolved in 21.1.2-2p2

• AV-125824: If a bond exists on the management interface NICs (>=10G), it can be broken while stopping / restarting / upgrading the Service Engines in LSC deployments.

• AV-126508: BGP: Virtual service scale in can result in minor traffic disruption.

• AV-128044: When streaming request logs over Syslog format, the virtual service name is not included in the streamed logs.

• AV-128339: If the GSLB site was configured with an FQDN instead of an IP address, the GSLB service page failed to render properly, and the URL to the member site was not generated correctly.

Key Change in 21.1.2-2p2

• AV-121820: By default faults are not available in the inventory APIs. A query parameter to include faults is introduced in the inventory APIs.

Key Changes in 21.1.2-2p1

Release Date: 22 October 2021

• AV-127130: Support round-robin selection of vCenter rather than random selection in NSX-T cloud with multiple vCenters.

What’s New in 21.1.2

Release Date: 14 October 2021
To refer to the upgrade checklist, click here.

Cloud Connector

• ** GCP**: Support to update SE Project ID cloud configuration

• OpenStack: Support for OpenStack Wallaby

Load Balancer Networking

• BGP: BFD support for multi-hop deployments

Issues Resolved in 21.1.2

• AV-116516: Graceful disable of server does not work for existing client connections to an L7 virtual service even when connection multiplex is disabled.

• AV-118269: Network resolution of GSLB site persistence pool fails when using per tenant VRF in vCenter. This can cause the VS placement to fail if the site persistence is enabled before the VS is placed on all requested number of SEs.

• AV-120022: In FIPS mode, TLS persistence on the pool used by the L7 virtual service may not be working as expected.

• AV-120446: HSM: Virtual service with RSA certificates is inaccessible when HSM integration with Thales Luna HSM is enabled, and the Thales Luna HSM has FIPS enabled.

• AV-121761: LSC: On hosts with large memory (>= 256 GB), when the Controller is also running on the same host, the Service Engine may fail due to memory fragmentation.

• AV-122119: NSX-T cloud configuration APIs are failing on the Controller version 21.1.1, with header X-Avi-Version 20.1.6.

• AV-122772: SE fails when auto gateway is enabled and the value of TCP maximum segment size (MSS) is 0 for IPv6 connections.

• AV-122836: When GSLB leader site is represented with cluster VIP, configuration replication between sites is not working.

• AV-124588: HTTPS requests with chunked transfer encoding might timeout when DataScript or WAF is enabled on the virtual service.

• AV-124931: Auto-download of CRS fails when proxy is configured.

• AV-124936: GRO in DPDK mode may be impaired for the following NIC families:
  • Virtio
  • ENA
  • VMXNET3

• AV-125098: Upgrade to NSX Advanced Load Balancer fails in the tiers BASIC and ESSENTIALS.

• AV-125377: External health monitor is unable to invoke ping since it requires raw socket access privileges.

• AV-125530: During SE restart, a race condition could potentially result in SE failure.

• AV-125682: GCP cloud fails to connect to the GCP API servers with x509.CertificateInvalidError.

• AV-126067: The rollback system fails (with AttributeError:prev_patch_img_path) when the previous version has more than two patch versions

• AV-126143: High Latency and reduced throughput may be observed on Service Engines running in the below ecosystems:
  • Linux Server Cloud using NICs apart from Mellanox ConnectX-4 and ConnectX-5 series
  • Cisco CSP
  • OpenStack
  • Google Cloud Platform

• AV-126148: The Avi cloud connector fails to sync AWS Auto Scaling groups if there are more than 200 servers in the cloud.

• AV-126153: When a patch is applied to the Controller or SE, file extraction can fail in some scenarios causing the patch operation to end prematurely.

• AV-126389: When RSS is enabled, SE may fail due to a race condition during packet transmission on vNICs that have VLAN configured.

• AV-127244: Upgrade is successful even when the max_active_versions is greater than 2. This leads to an unsupported deployemnt where the NSX Advanced Load Balancer might be running with 3 different versions and can lead to SE sync issues.

• AV-127278: Existing static routes are overwritten due to pagination issues on the UI

Key Changes in 21.1.2

• show servicenengine <se> cpu is extended to display cpu set information.

• X_AVI_VERSION (AVI_API_VERSION) is removed from the response header.

• As prevention against potential security threats, NSX Advanced Load Balancer version details will now be revealed only to authenticated users at all endpoints like CLI, API, and UI.
  The following endpoints are secured from displaying version related information:
  

  • initial-data

  • cluster/runtime

  • cluster/status

    To view the version details, ensure your account is authenticated.
    

    Note: The version details are permanently removed from the Controller SSH login banner.

• Starting with NSX Advanced Load Balancer version 21.1.2, roles can only be created in the admin tenants.

Known Issues in 21.1.2

• AV-127481: Auto-deployment of CRS might fail.
  Workaround: Manually download the CRS and upload it to the system.

• AV-132122: Mellanox NICs [ConnectX-4/ConnectX-4 Lx/ConnectX-5] : RSS with VLAN tagged packets do not work.

• AV-126071: System limit on the number of virtual services that can be created is not honoured. The total virtual service created in the system exceeds the max virtual service limit in the system by 1.

• AV-142641: Macro API for virtual service deletion does not support API migration below X-Avi-Version 20.1.1.

• AV-155317: DPDK driver crash with bond interfaces configured on LSC deployments containing a mix of Mellanox and other network interfaces.

Checklist for Upgrade to NSX Advanced Load Balancer Version 21.1.2

Refer to this section before initiating upgrade.

• Upgrade to NSX Advanced Load Balancer is only supported from the following versions:
  

  • Version 18.2.6 through 18.2.13

  • Version 20.1.1 through 20.1.7

  • Version 21.1.1

• NSX Advanced Load Balancer no longer supports VMware vCenter version 5.5. The End of General Support for vSphere 5.5 by VMware was on September 29th,
  1. 
     Before upgrading to NSX Advanced Load Balancer version 21.1.1, it is recommended to upgrade to a current vCenter version. For more information, refer to the System Requirements article.

• Starting with NSX Advanced Load Balancer 20.1.5, the NSX-V Cloud Connector is not supported. The NSX-V cloud was deprecated in version 20.1.3, and is now unsupported. It is recommended to migrate to an NSX-T cloud connector, or switch to no-orchestrator mode with NSX-V.

• The default disk size for new SEs is 15 GB.
  For OpenStack deployments, ensure that the disk size for the requisite flavors is increased to a minimum of 15 GB

• The Avi Controller and Service Engines use Python 3. Refer to the migration notes in the following sections:

  • For ControlScripts

  • For Python-based External Health Monitors

• Licensing Management of the Avi Service Engines has been updated. Refer to the License Management article for more information.

• NSX Advanced Load Balancer now enforces system limits based on Controller cluster size. Refer to the System Limits article for more information.

• In case of Service Engine upgrade in a Nutanix Acropolis Hypervisor (AHV) environment, refer to the pre-upgrade changes.
  

• Support for Inter-SE Distributed Object Store: Service Engines can now perform the distribution and synchronization of information without the involvement of the Controller in AWS, Azure, GCP, OpenStack clouds (with default port being 4001). Ensure that TCP traffic on the selected port between Service Engine management interfaces is allowed via appropriate firewall rule.

Issues Resolved in 21.1.1 Patch Releases

Issue Resolved in 21.1.1-2p11

• AV-171698: In some cases, WAF requests can become slow if client_request_max_body_size in the WAF Profile is set to high values.

Issues Resolved in 21.1.1-2p10

Release Date: 21 November 2023

• AV-120446: In NSX Advanced Load Balancer version 20.1.5, the gemengine-1.3 in the SE does not work for RSA ciphers when HSM is running in FIPS mode
• AV-127881: Issue with Thales-Luna autorecovery causes the NSX Advanced Load Balancer and HSM pair to fail when a HSM appliance is rebooted
• AV-140259: Service Engines in SE groups that are detached from the HSM groups are rebooted if the HSM group configuration is changed
• AV-142030: The Password reset link does not work since the Password Reset page is missing
• AV-158065: Connection using RSA certificate might fail when used with the Hardware Security Module due to incompatible libgem libraries

Issues Resolved in 21.1.1-2p9

Release Date: 09 September 2023

• AV-149858: External logs are not received on the external server when the whole pod or container gets deleted or re-imaged.
• AV-148491: SE crash when transferring IP reputation files from a Controller.
• AV-128707: The SE Agent process might leak an opened file descriptor and consume too much disk space. This could also manifest as SE Agent crash when processing back to back updates of multiple IP reputation files.

Issues Resolved in 21.1.1-2p8

Release Date: 02 June 2021

• AV-142624: Events and logs are timing out and new events anc logs are not visible on the UI or API. When the log manager indexes a file, if the file is corrupted or not able to read the log from the file, the indexer is stuck in loops
• AV-140199: For TLS client, handshake API does not work as expected when connection is terminated after log server restart
• AV-139352: Virtual service switchover on ACI based environment can lead to MAC-IP mapping flap eventually leading to blocking of VIP
• AV-135843: After applying the Controller patch, the indexer service fails
• AV-120370: When configuring the client request data in the HTTP Health monitor with “/r” in the field, ‘/r’ is converted to ‘/n’

Issues Resolved in 21.1.1-2p7

Release Date: 03 March 2021

• AV-135843: After applying the Controller patch, the indexer service fails.
• AV-130533: In a VMware cloud deployment, with ESX version 7.x, L2 DSR TCP and HTTP health monitor may fail due to incorrect csum handling.
• AV-129245: In case of CSR (Certificate Signing Request) through the Avi UI, on importing the valid certificate, the ** Save** button in the Edit Certificate screen is greyed out.

Issues Resolved in 21.1.1-2p6

Release Date: 05 February 2021

• AV-136068: Service Engine failure due to insufficient memory.
• AV-132736: When a primary key is uploaded as part of a certificate body, after clicking the validate button, the primary key continues to be visible in the certificate section.
• AV-132122: RSS does not work for Mellanox ConnectX-4 VLAN interfaces.
• AV-131472: Auto-download of CRS via Pulse fails

What’s New in 21.1.1-2p5

Release Date: 14 December 2021

• AV-132339: Incorrect accounting of opackets & obytes of interface statistics in non-DPDK mode.

• AV-132431: Mitigation for CVE-2021-44228.

What’s New in 21.1.1-2p4

Release Date: 29 November 2021

• AV-131221: RSS support for LSC cloud deployments on VMware virtual machines.

Issues Resolved in 21.1.1-2p4

• AV-127498: When the SE group is in a version lower than 20.1.5 and the Controller is in a version 20.1.5 or higher, the SE may fail if a pool has multiple resolve by DNS - based pool members and these pool members fail to resolve.

What’s New in 21.1.1-2p3

Release Date: 23 November 2021

• AV-130700: LSC DPDK mode support to handle memory fragments for hosts with greater than 256 GB memory.

Issues Resolved in 21.1.1-2p3

• AV-125824: If a bond exists on the management interface NICs (>=10G), it can be broken while stopping/ restarting / upgrading the Service Engines in LSC deployments
• AV-128220: Patch install from NSX Advanced Load Balancer version 21.1.1-2p1 to version 21.1.1-2p2 gets stuck at 35%.
• AV-128745: When a GSLB leader site is represented as FQDN instead IP address, the GSLB configuration replication from leader to follower site is not working.
• AV-129063: The GeoDB object and file objects are not recreated after upgrade to the Enterprise tier.
• AV-129080: NSX Advanced Load Balancer does not sign the SAML authentication requests despite SSL Key and certificate being attached to the SAML virtual service.
• AV-128928: Server-initiated renegotiation was disabled in 20.1.5. This results in Server-initiated renegotiation failures for both Pools and HTTPS Health Monitor.
• AV-121761: LSC: On hosts with large memory (>= 256 GB), when the Controller is also running on the same host, Service Engine may fail due to memory fragmentation.

Issues Resolved in 21.1.1-2p2

• AV-126389: When RSS is enabled, SE may fail due to a race condition during packet transmission on vNICs that have VLAN configured
• AV-126153: When a patch is applied to the Controller or SE, file extraction can fail in some scenarios causing the patch operation to end prematurely.
• AV-126143: High Latency and reduced throughput may be observed on Service Engines running in the below ecosystems:
  • Linux Server Cloud using NICs apart from Mellanox ConnectX-4 and ConnectX-5 series
  • Cisco CSP
  • OpenStack
  • Google Cloud Platform
• AV-126067: From version 21.1.1, the rollback system fails (with AttributeError:prev_patch_img_path) when the previous version has more the two patch versions
• AV-125530: During SE restart, a race condition could potentially result in SE failure.
• AV-125098: Upgrade to version 21.1.1 fails in the license tiers ‘BASIC’ and ‘ESSENTIALS’
• AV-124931: Auto-download of CRS fails when proxy is configured.

Issues Resolved in 21.1.1-2p1

Release date: 24 September 2021

• AV-124931: Auto-download of CRS fails when proxy is configured.
• AV-124588: HTTPS requests with chunked transfer encoding might timeout when DataScript or WAF is enabled on the virtual service.
• AV-121987: In an Avi Controller with an older Avi API version, local_file can not be configured as fail_action on pool/pool group
• AV-121573: If the Controller does not have access to the internet, creating SE image for vCenter cloud will fail after upgrade.
• AV-116516: Graceful disable of server does not work for existing client connections to an L7 virtual service even when connection multiplex is disabled

What’s New in 21.1.1

Release date: 12 August 2021
To refer to the upgrade checklist, click here.

Application Security

• DDoS: Detection and mitigation of Layer 7 (DNS) attacks: DNS Amplification Egress and DNS Reflection

• Bot Management: Support to detect, classify and manage bot traffic

  Note: This feature is currently under tech preview.

Automation

• Support for distributing Avi SDK and Config roles as Ansible Collection

Avi Pulse

• Proactive Tech Support Management including:
  

  • Auto Case Creation On SE Failure

  • Auto Case Creation On System Failure

  Note: This feature is currently under tech preview.

Cloud Connector

• AWS: Support to track Controller and Service Engine upgrade information via the custom tags Current Avi Version and Avi Upgrade Date

• ** AWS**: Extended support to Gov Cloud US-East region

• GCP: Support for Shared VPC Multi-NIC

• Microsoft Azure: The maximum number of availability zones (AZ) for SEdistribution is increased from two to three

• ** LSC**: Support for base kernel versions 3.10.0-1160.25.1.el7.x86_64 and 3.10.0-1160.31.1.0.1.el7.x86_64

• ** LSC**: Mellanox NICs: Mellanox Technologies MT27800 Family [ConnectX-5]

Core LB Features

• Persistence: Honor persistence when gracefully disabling a server in a pool

• Pools: L4 and L7 virtual services can use the same pool for backend traffic

• Health Monitoring: Support for External PostgreSQL Health Monitors

• HTTP/2: Support for HTTP/2 upgrade on the client side

• HTTP/2: Support for caching

• SE Time Flow Tracker: Support to track the network characteristics, processing time at key checkpoints and flag queuing delays in a packet journey through the network appliance

• Support to add query in an HTTP request redirect policy

• The flag http_only is introduced in the  HTTP Cookie Persistence Profile  to set the  HTTP Only attribute in the cookie. This prevents the client side scripts from accessing this cookie

• For every virtual service, user-configurable default HTML error page profile (Custom-Error-Page-Profile) is available for Avi-generated 4xx and 5xx errors. This feature is available only in the ENTERPRISE license tier

• Support to update the port to the hostname in the host header, in requests to the servers via the field  Append Port  during pool configuration

• Support for dynamic modification of the number of se_dps without rebooting the Service Engine

• Support to configure specific set of signature algorithms for an SSL profile

• Support to configure Elliptic Curve Cryptography (ECC) Cipher Suites in an SSL profile

• Support for Service Engine Datapath Isolation

• Enhancing GeoDB for Layer 7 and network policies (operations like HTTP security policies, and more):

  • Granular GeoDB based on region, city, ASN, ISP, etc.
  • Support to configure user-defined GeoDB mapping attributes

DataScripts

• The support to return all geo information available, including any user mapping matches for a target IP via the flag  _ All_ introduced for the DataScript function avi.utils.get_geo_from_ip

• API support to return the total number of open connections per Service Engine attached to the current virtual service

• API support to return the total number of service engines attached to the current virtual service

• API support to modify the existing cookie attributes value in the HTTP response

• Support for SSL events in DataScripts for L7 and L4 SSL virtual services

• Support for STARTTLS : A new DataScript event in L4 SSL (VS_DATASCRIPT_EVT_TCP_CLIENT_ACCEPT) and the APIs avi.ssl.disable_ssl() and avi.ssl.enable_ssl() are introduced to disable/ enable traffic during SSL respectively

• Support for XML parsing in L7 DataScripts

DNS & IPAM

• Support for third party IPAM providers using respective REST API via Custom IPAM Profile

• DNS Query failed events will be raised as unsuccessful DNS lookup

Networking

• IPv6: Support to deactivate IPv6 learning in SE using the field  deactivate_ipv6_discovery in the Service Engine group properties

• Packet Capture support for NAT flows

Observability and Monitoring

• Monitoring: E-mail Notification timestamp is displayed with the local timezone

• Support to enable/ disable inventory faults per object

Platform

• Tenancy: Granular RBAC support for SE Group objects

• TSO (TCP Segmentation Offload) support in environments where DPDK mode is enabled for packet processing, for deployments where SE routing is enabled

• Migration of Basic Auth to SSO Policy

User Interface

• User Interface Enhancements

• Internationalization (i18n): NSX Advanced Load Balancer UI support for Japanese and Simplified Chinese

WAF

• ICAP support extended for NSX Defender’s (lastline) ICAP server to prevent malicious file uploads

• Support for XML XPath based exclusion in processing WAF rules

Issues Resolved in 21.1.1

• AV-87320: In a Terraform plan with nested blocks, the Avi Terraform provider sets default values for the optional fields which were not defined in the plan

• AV-102522: When FIPS mode is enabled, the Service Engine may fail if a virtual service is configured with the http security policy with the rate limiting rules per_client_ip and per_uri_path.

• AV-111140: Unable to search audit logs for usernames containing the special character “.”

• AV-113654: In the Avi UI, after adding a new GSLB site when the Save and Set DNS Virtual Services button was clicked, the HTTP error, 403: GSLB Operations are NOT Permitted. is displayed.

• AV-115671: In an OpenStack cloud, the Controller may initiate multiple Add VNIC operations on the SE for the same network and VRF before the vNIC IP limit is reached, causing potential traffic issues.

• AV-115797: The SE_DOWN event is not displayed under Operations > Events > All Events and user login events are not displayed in the Config Audit Trail.

• AV-116043: Cluster based events are not generated when the Controller cluster leader is restarted.

• AV-116327: High disk usage on the Controller leader node due to excess files in /var/lib/avi/systeminfo.

• AV-116398: AWS: Removing the application domain name from a shared virtual service results in the deletion of a random entry from the list.

• AV-116411: Service Engine fails when a HTTP/1.0 request is sent without a host header to a virtual service with a pool with both HTTP/2 and SSL enabled.

• AV-116440: Reindexing a HTTP policy via the UI using Virtual Service >Policies>HTTP Requests>Move To does not work.

• AV-116620: In an OpenStack cloud, the Service Engine Group page is inaccessible via the UI.

• AV-116791: For OpenStack clouds using BGP, configuring a BGP peer network displays the error Network object not found.

• AV-116974: SE may fail due to invalid memory access in local port processing.

• AV-117141: PKI profile does not support API versioning.

• AV-117414: An L4 object’s name exceeding 128 characters may lead to SE failure.

• AV-117715: In an L4-SSL virtual service, disabling a server while it’s handing the traffic results in SE failure.

• AV-117720 : App Cookie persistence fails when used in combination with the avi.http.remove_header (“Set-Cookie”) and avi.http.add_header (“Set-Cookie”) DataScript APIs, if the app cookie persistence and DataScript are on the same virtual service.

• AV-117865: SE fail-over time is higher (more than three minutes) in AWS

• AV-117960: The Avi Controller upgrade with AWS cloud can fail if the cloud is in failed state.

• AV-118134: When a virtual service is configured with use_vip_as_snat or effectively using VIP IP as SNAT, consecutive migrations to the same SE may render the virtual service with that VIP inoperative.

• AV-118242: ‘;’ is not allowed as a URL query parameter delimiter.

• AV-118264: SE fails if the NAT policy is configured with source/destination port match and when a routable ICMP packet to external world lands on the SE.

• AV-118277: High disk usage on SE because of IP reputation files consuming space.

• AV-118802: System generates duplicate diffs for federated objects which can potentially lead to streaming of incorrect config objects to follower sites in a GSLB federation

• AV-119921: In a persistence profile, the ip_mask behaves as an inverse CIDR mask and distributes the clients across servers instead of ensuring the clients in the same subnet are connected to the same servers.

• AV-119971: When Ignore request body parsing errors due to partial scanning is enabled in a WAF Profile and ** Enable Request Body Buffering** is also enabled in the Application profile, the parsing errors are not ignored in WAF and the request is denied.

• AV-122119: NSX-T cloud configuration APIs failing on a Controller with header X-Avi-Version 20.1.6

Key Changes in 21.1.1

• The maximum number of characters in a vip_id is limited to 16 characters.

• Launching Bash access in the CLI shell using cli@<controlleriip> is deactivated.

• Prior to NSX Advanced Load Balancer version 21.1.1, it was not possible to configure a service match criterion for policies under a child virtual service due to the lack of existing services object to be verified against. Starting with NSX Advanced Load Balancer 21.1.1, in SNI virtual hosting and Enhanced Virtual Hosting, for policies under a child virtual service, the service match criterion is matched against its parent virtual service.

• For pools and pool groups, the special character “$” is not allowed in the field Name.

• After switching to the Basic/ Essentials license tier, the default Error Page Profile reference is removed from the virtual service object.

• The DOS_ATTACK events will be shown on the UI as non-internal events. That is, without clicking on the Internal checkbox, the user can see these events directly on the Controller events UI.

• The minimum value for X-Avi-Version that can be used when interacting with the Avi Controller is 18.2.6. It is recommended to update the automation assets, as required.

• Support for Inter-SE Distributed Object Store: Service Engines can now perform the distribution and synchronization of information without the involvement of the Controller in AWS, Azure, GCP, OpenStack clouds (with default port being 4001). Ensure that TCP traffic on the selected port between Service Engine management interfaces is allowed via appropriate firewall rule.

• LDAP : Support for including exclamation mark ( ! ) in the username for Controller authentication

Known Issues in 21.1.1

• AV-126143: High latency and reduced throughput may be observed on Service Engines running in the below ecosystems:
  • Linux Server Cloud using NICs apart from Mellanox ConnectX-4 and ConnectX-5 series
  • Cisco CSP
  • OpenStack
  • Google Cloud Platform
    Work Around: Disable TSO configuration for each Service Engine Group. For more details on the CLI, refer to Enabling GRO and TSO on an Avi SE .
    Notes:
    
  • TSO is enabled by default in environments supporting DPDK. Refer to TSO, GRO, RSS, and Blocklist Feature on Avi Vantage for more details.
  • Environments using VMXNET3 (vCenter, NSX-T, VMC on AWS, AVS, GCVE) and ENA (AWS) are not impacted.
    

• AV-121113: Using GeoDB files that are not sorted in ascending order in the System-GeoDB can result in IP Groups missing entries.
  Workaround: Upload the GeoDB custom file object with IP addresses mapped to different Geo attributes only in ascending order.

• AV-121573: If the Controller does not have access to the internet, creating SE image for vCenter cloud fails after upgrade.

• AV-115513: LSC:
  
  • Upgrade/Patch may not work if the Controller is running as a container on a host running RHEL 8.x.
    
  • Podman version higher than 1.6.4 is not supported.

• AV-127481: Auto-deployment of CRS might fail.
  Workaround: Manually download the CRS and upload it to the system.

• AV-132122: Mellanox NICs [ConnectX-4/ConnectX-4 Lx/ConnectX-5] : RSS with VLAN tagged packets do not work.

• AV-142641: Macro API for virtual service deletion does not support API migration below X-Avi-Version 20.1.1.

• AV-155317: DPDK driver crash with bond interfaces configured on LSC deployments containing a mix of Mellanox and other network interfaces.

System Limits Enforced

• System Limits applied for L7 objects:
  • HTTP Policies
  • Caching
  • Compression
• System Limits applied for L4 objects

Checklist for Upgrade to NSX Advanced Load Balancer Version 21.1.1

Refer to this section before initiating upgrade.

• Upgrade to NSX Advanced Load Balancer is only supported from the following versions:
  

  • Version 18.2.6 through 18.2.12

  • Version 20.1.1 through 20.1.6

• NSX Advanced Load Balancer no longer supports VMware vCenter version 5.5. The End of General Support for vSphere 5.5 by VMware was on September 29th,
  1. 
     Before upgrading to NSX Advanced Load Balancer version 21.1.1, it is recommended to upgrade to a current vCenter version. For more information, refer to the System Requirements article.

• Starting with NSX Advanced Load Balancer 20.1.5, the NSX-V Cloud Connector is not supported. The NSX-V cloud was deprecated in version 20.1.3, and is now unsupported. It is recommended to migrate to an NSX-T cloud connector, or switch to no-orchestrator mode with NSX-V.

• The default disk size for new SEs is 15 GB.
  For OpenStack deployments, ensure that the disk size for the requisite flavors is increased to a minimum of 15 GB

• The Avi Controller and Service Engines use Python 3. Refer to the migration notes in the following sections:

  • For ControlScripts

  • For Python-based External Health Monitors

• Licensing Management of the Avi Service Engines has been updated. Refer to the License Management article for more information.

• NSX Advanced Load Balancer now enforces system limits based on Controller cluster size. Refer to the System Limits article for more information.

• In case of Service Engine upgrade in a Nutanix Acropolis Hypervisor (AHV) environment, refer to the pre-upgrade changes.
  

• Support for Inter-SE Distributed Object Store: Service Engines can now perform the distribution and synchronization of information without the involvement of the Controller in AWS, Azure, GCP, OpenStack clouds (with default port being 4001). Ensure that TCP traffic on the selected port between Service Engine management interfaces is allowed via appropriate firewall rule.

Supported Platforms

Refer to System Requirements: Ecosystem

Product Documentation

For more information, please see the following documents, also available within this Knowledge Base.

Installation Guides

• NSX Advanced Load Balancer Installation Guides

Copyrights and Open Source Package Information

For copyright information and packages used, refer to open_source_licenses.pdf. For software bill of materials (SBOM), refer to s3://aviopensource/21.1.6/spdx-sbom-avi-21.1.6-2022-11-16T04_12_29Z.spdx.

Avi Networks software, Copyright © 2015-2021 by Avi Networks, Inc. All rights reserved. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at http://www.opensource.org/licenses/gpl-2.0.php and http://www.opensource.org/licenses/lgpl-2.1.php

Additional Reading

Protocol Ports Used by NSX Advanced Load Balancer for Management Communication