When upgrading from NSX 4.2 or VCF 9.0 to VCF 9.1 (or later) with Distributed Load Balancer (DLB) configured, the NSX upgrade pre-check may report WARNING or ERROR messages
Please refer to the table in the Resolution section below for the specific Upgrade precheck messages, impact details, and corresponding remediation steps.
VMware NSX 9.1
VMware Cloud Foundation 9.1
This is an expected behavior during the VCF 9.1 Upgrade Precheck for Distributed Load Balancer (DLB)
2. For prechecks ERROR messages
Note: The NSX upgrade on ESX hosts will temporarily interrupt distributed load balancer traffic. Traffic will resume once clients re-initiate connections.
In the VCF 9.1 release, enabling the virtual server access log, changing the error log level, and configuring persistence profiles are not supported for the distributed load balancer.
The following table lists the upgrade precheck warnings and errors for the VCF 9.1.0 and 9.1.1 or later release, categorized by the DLB configurations of NSX 4.2 or VCF 9.0.
| DLB exists? | DLB connectivity path (API) | DLB unsupported features configured | Precheck Warning/Error | Warning/Error Message in 9.1.0 | Warning/Error Message in 9.1.1 or later release | Comments |
| No | N/A | N/A | N/A | N/A | N/A | N/A |
| Yes | Path of an empty group or Null | No | WARNING (for 9.1.0 release) | Found data inconsistencies: The following features cannot be configured for distributed load balancer in VCF 9.1: error log level, access log enabled, persistence profiles. | N/A | Acknowledge the warning and no extra action is needed. There is no traffic impact. |
| Yes | Path of an empty group or Null | Yes | WARNING | Found data inconsistencies: Unsupported features for distributed load balancer in VCF 9.1, e.g. error log level, access log, persistence profiles, are configured and will be reset after upgrade. | Unsupported features for distributed load balancer in VCF 9.1, e.g. error log level, access log, persistence profiles, are configured and will be reset after upgrade. No extra action is needed. For details, see KB 440901. | Acknowledge the warning and no extra action is needed. There is no traffic impact. |
| Yes | Path of a group with segment ports | No | WARNING | Found data inconsistencies: There will be traffic disruptions or connection reset on distributed load balancer during NSX upgrade on ESX hosts. The following features cannot be configured for distributed load balancer in VCF 9.1: error log level, access log enabled, persistence profiles. | The NSX upgrade on ESX hosts will temporarily interrupt distributed load balancer traffic. Traffic will resume once clients re-initiate connections. No extra action is needed. For details, see KB 440901. | Acknowledge the warning and no extra action is needed. |
| Yes | Path of a group with segment ports | Yes | WARNING | Found data inconsistencies: There will be traffic disruptions or connection reset on distributed load balancer during NSX upgrade on ESX hosts. Unsupported features for distributed load balancer in VCF 9.1, e.g. error log level, access log, persistence profiles, are configured and will be reset after upgrade. | The NSX upgrade on ESX hosts will temporarily interrupt distributed load balancer traffic. Traffic will resume once clients re-initiate connections. Unsupported features for distributed load balancer in VCF 9.1, e.g. error log level, access log, persistence profiles, are configured and will be reset after upgrade. No extra action is needed. For details, see KB 440901. | Acknowledge the warning and no extra action is needed. |
| Yes | DLB connectivity path is set to "ALL" | N/A | ERROR | Found data inconsistencies: Default distributed load balancer instance is not supported in VCF 9.1 release. Please update the distributed load balancer to attach to a group. | Default distributed load balancer instance is not supported in VCF 9.1 release. Please update the distributed load balancer to attach to a specific group and re-run the pre-check. For details, see KB 440901. | Default distributed load balancer instance refers to a DLB configuration where the connectivity path in the API is set to "ALL". This configuration is no longer supported starting from VCF 9.1. |