Outbound NAT VM Assignment Issue
Closed this issue · 0 comments
I am able to deploy the SDNEXpress successfully with the 3 x NC, 2 x LB, and 2 x GW configuration.. Many of the features that I have deployed seem to work as expected.
Here's the issue:
Load Balancer Configuration
- Frontend IP Config: Public IP; BGP advertising it as expected with routes to Lb0 and Lb1
- Backend pool: 6 identical test VMs
- Inbound NAT Rules: none
- Outbound NAT Rules: Protocol = ALL
- Load Balancing Rules: none
- Health Probes: none
L3 Gateway connection enabled.
After adding all network interfaces to the load balancer backend pool, in order, the results are as follows:
Vm0 - NAT not enabled
Vm1 - NAT enabled
Vm2 - NAT not enabled
Vm3 - NAT enabled
Vm4 - NAT not enabled
Vm5 - NAT enabled
There is a clear alternation occurring to which VM is permitted to use the NAT and which are not. I don't understand why this would be the case. I would expect them all to be enabled. Windows Admin Center SDN diagnostics shows all system as healthy. I'm clearly missing something.
The OS is Windows 2022 July version, which, by the way, manages to fail on New-NetworkContorllerCluster
during deployment. However, this command works normally on the Windows 2022 Sept 2023 version, which is what I was forced to use to deploy the the SDN VMs. I then updated all of the SDN VMs.