VMware Networking Community
thompsoa
Enthusiast
Enthusiast
Jump to solution

VXLAN configuration Status Busy

Hi Team,

I've recently configured new hosts with LACP, host preparation completed with no problems, but when I select "Configure" it doesn't progress. VXLAN status is "Busy".

VTEP configuration:

MTU 1600

We use DHCP for IP allocation

Teaming Policy: Enhanced LACP

NSX version: 6.2.4

Have you experienced this problem before?

Thanks!

Alicia Thompson www.bakingclouds.com Twitter:@bakingclouds
0 Kudos
1 Solution

Accepted Solutions
thompsoa
Enthusiast
Enthusiast
Jump to solution

NSX has a limitation where you can't share a vDSwitch with Clusters with different IP network configuration. In our scenario we have a cluster with LACP config and the other without it.

We had to remove LACP config and it worked.

Cheers,

Alicia

Alicia Thompson www.bakingclouds.com Twitter:@bakingclouds

View solution in original post

0 Kudos
6 Replies
rajeevsrikant
Expert
Expert
Jump to solution

Since you are using DHCP server(not IP pool), can you please ensure that the helper address is configured to reach out the DHCP server.

Also please check if the vmkernel interface for the VXLAN got IP Address.

0 Kudos
hansroeder
Enthusiast
Enthusiast
Jump to solution

Try using an IP Pool first. If that works, something must be wrong with the DHCP server (settings).

0 Kudos
rajeevsrikant
Expert
Expert
Jump to solution

were you able to check with the recommendations suggested.

Just curious to know the status

0 Kudos
bayupw
Leadership
Leadership
Jump to solution

As mentioned in above replies, try static IP Pool first.

If it doesn't work, try to restart the NSX Manager

Bayu Wibowo | VCIX6-DCV/NV
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://github.com/bayupw/PowerNSX-Scripts
https://nz.linkedin.com/in/bayupw | twitter @bayupw
0 Kudos
thompsoa
Enthusiast
Enthusiast
Jump to solution

NSX has a limitation where you can't share a vDSwitch with Clusters with different IP network configuration. In our scenario we have a cluster with LACP config and the other without it.

We had to remove LACP config and it worked.

Cheers,

Alicia

Alicia Thompson www.bakingclouds.com Twitter:@bakingclouds
0 Kudos
purwandi80
Contributor
Contributor
Jump to solution

thanks mas bayu for enlighment

0 Kudos