NSX-T VTEP ip pool subnet mask change

[MaxB]

Hello folks

we are using a NSX Ip-pool for our VTEP addresses of the ESXi. In the pool is currently a private not routed /24 network with its CIDR and its associated ip-range stored.

Unfortunately we are slowly but surely running out of ips in the range. Our idea is to extend the network to a /22.
The plan would be as follows:
1. adjust the CIDR in the IP pool from /24 to /22
2. wait until all existing ESXi have adjusted the subnet mask of their VMkernel ports
3. add additional IP-ranges to the ip-pool

Does anyone already have experience with such a scenario? Will the ESXi automatically adjust their subnet mask at all? I think there might be a short communication downtime between the ESXi until the subnet mask change is done.

best regards,
Max

[Sreec]

You can create a new TEP-POOL and assign the same to Transport Nodes. There will be a traffic interruption.

[MaxB]

Thanks for your fast answer!

So the ESXi VMkernel ports will automatically get reconfigured by nsx? Or will I need to take any manual actions?

And edit of the CIDR of the existing IP pool would not be an option? I know the result will be the same but just asking.

Good to know, that i will have to plan a traffic downtime.

[Sreec]

I have not tested expanding existing pools, however, using a new pool and mapping to the transport nodes always worked for me, 

[MaxB]

Thank you very much for Testing it. 
For claryfication, did you just add a new IP range or have you also adjusted the CIDR for a greater subnet mask? 

sorry for asking this a lot, but I dont have a QA environment and I am a bit nervous about the change 😐

[Sreec]

It was a new subnet. Kindly note that if you have routed TEP pools, you need to route new TEP pools in the physical network as well.