NSX Segment status stuck "in-progress" due to DHCP Server IP overlap

Products

• VMware NSX

Issue/Introduction

• The Segment status remains stuck in an "in-progress" state after the Segment CIDR value is updated.
• This issue occurs when a DHCP server IP is configured to fall within the segment's subnet range.
• 
• Restarting the nsx-ccp service on NSX managers with root privileges (/etc/init.d/nsx-ccp restart) does not resolve the "in-progress" status.

Environment

VMware NSX 

Cause

The issue is caused by a configuration conflict where the DHCP server IP overlaps with the segment subnet range. This conflict prevents the Corfu table status from reaching a Realized state, causing it to remain Unrealized. While the GPRR table may indicate a status of Realized, the NSX Manager UI reflects the underlying Corfu state and continues to display the segment status as "in-progress."

Resolution

This issue is resolved in the following VMware NSX versions:

• NSX 4.2.0 and above
• NSX 9.0 and above

Workaround

To manually synchronize the segment status, perform the following steps:

1. Modify Segment Subnet: Edit the segment and change the subnet CIDR (e.g., from #.#.#.#/24 to #.#.#.#/23). Click Apply and Close the editor.
2. Update DHCP Server IP: Re-edit the segment and update the DHCP Server IP to the correct value. Click Apply and Close the editor.
3. Extend DHCP IP Range: Re-edit the segment and update the DHCP IP range to the desired new values. Click Apply and Close the editor.

"Note: The IP addresses and ranges provided are examples; values should be configured to match the specific environment."