Fails invoking script command Pre-Install_6 about sdn HOT 27 OPEN

Hi Will Please open a support case for this issue. They should be able to guide you. Thanks Anirban From: willkruss ***@***.***> Sent: Wednesday, May 10, 2023 9:35 PM To: microsoft/SDN ***@***.***> Cc: Anirban Paul ***@***.***>; Comment ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, it looks like we managed to get the Network Controller script to function properly and install. However, I have another major issue. We have a setup with about 1000 vms in 2016, but our virtual network does not include any logical switches. The bandwidth reservation mode is set to Absolute on the virtual switch. It appears this cannot be changed, and we have 1000 VMs connected to it. We can upgrade to a logical switch, but the bandwidth reservation mode has to be the same (or it won't allow upgrading from virtual switches to logical switches). We can't install the network controller as it says the Logical Switch bandwidth reservation mode has to be 'weight'. How on earth without downtime can I somehow go from Virtual Switches with Absolute reservation mode to Weight mode so I can convert to a logical switch that is compatible with the network controller. We have to figure out how to do this so we can upgrade our cluster from 2016 to 2019 as we run a lot of isolated networks using network virtualization which do not function without a network controller upon upgrade from 2016 to 2019. Thanks in advance for any help or advise. Cheers, Will - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63MP6CIHJ73KFDQWOF3XFRUA5ANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.***>

[+Sonal to answer the VMM Question] Hi Will When you configure Network Controller with a REST name (which is what the default deployment does), the netcontroller.testlab.local will resolve to the IP address of the NC VM which hosts a microservice called ApiService (You can get the list of micro-services by running Get-NetworkControllerReplica on a NC VM). This service hosts the REST endpoint for Network Controller. Now, if the NC VM hosting the ApiService goes down, the service moves to another NC VM. And NC will change the DNS record of the REST name (netcontroller) to the IP of the NC VM now hosting the ApiService. This optimization was done to support a scenario where the NC VM could be placed in different IP subnets, thus providing rack level redundancy. NC could also be deployed in another mode where the REST IP Address is fixed, and must be different from the IP address of any of the NC VMs. In this mode, the NC VMs cannot move to a different subnet. Thanks Anirban From: willkruss ***@***.***> Sent: Monday, May 15, 2023 10:24 PM To: microsoft/SDN ***@***.***> Cc: Anirban Paul ***@***.***>; Comment ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Sorry for the follow up, a couple of questions: Firstly, when provisioning the network controller it applies the domain the same IP as one of the network controllers, is that normal. For example in our testlab once provisioned without error I get: * NC-VM01.testlab.local 192.168.5.11 * NC-VM02.testlab.local 192.168.5.12 * NC-VM03.testlab.local 192.168.5.10 * netcontroller.testlab.local 192.168.5.10 I find it strange that the netcontroller IP provided is the same as one of the actual VMs, and not a separate IP that can fail between hosts like the way the cluster IP works. Secondly, I don't understand how to add the working network controller as a service, when I try to do this I get the error: Non NC managed HNV LND 'Isolated Networks_0' of logical network 'Isolated Networks' has host groups overlaps with Network Controller scope. 'Isolated Networks' is a logical network that uses Hyper-V Virtualization. It is used by VMs in our cluster and therefore the hosts of the VMs have to be in the same host group as the hosts of the network controller VMs. Isn't the idea of the network controller so you can control networks using Hyper-V Network Virtualization? Thanks, Will Kruss - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63LE7PNJ5XTFVYKN6MDXGMFNFANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.***>

+Sonal from the VMM team @sonal ***@***.***>, can you please check the configuration for accuracy. Will, are you able to see IP addresses from the HNV PA network on the physical host where the tenant VM is located? You can check this by running ipconfig /allcompartments /all on the host machine. @sonal ***@***.***>, how can they check the ConfigurationState of the Servers resource from VMM? I can provide REST commands directly, but wondering if VMM also exposes them. Thanks Anirban From: willkruss ***@***.***> Sent: Sunday, May 28, 2023 10:21 PM To: microsoft/SDN ***@***.***> Cc: Anirban Paul ***@***.***>; Comment ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Thank you for the explanation. I have everything running in my test lab, however, for some reason the network controller are not handing out DHCP leases for the IP Pools in the VM Networks which use HNV. It assigns the IP according to system center correctly, but inside the operating system we get DHCPDISCOVER -> No DHCPOFFERS received. Oddly it appears that the Logical Network I created for HNV (Isolated Networks) is not allocating IPs from the IP Pool to the hosts in the manner it worked without using the Network Controller (PA Addresses unused). I've attached screen shots of the setup. If you have any ideas I've love to hear them. Thanks, Will [Image removed by sender. HardwareLogicalNetworkConnectivityOnHost]<https://user-images.githubusercontent.com/4157364/241647351-a6bd5b1c-db10-4f54-955d-c914e2c4923c.png> [Image removed by sender. IsolatedNetworksPAAddresses]<https://user-images.githubusercontent.com/4157364/241647367-7a517484-72aa-45cf-887e-322caf29c05f.png> [Image removed by sender. LogicalNetworks]<https://user-images.githubusercontent.com/4157364/241647374-b72bf2dc-5903-4834-bef8-1c3d0f5f9143.png> [Image removed by sender. LogicalSwitch]<https://user-images.githubusercontent.com/4157364/241647378-bade43fa-ca47-48c4-bb15-fb19ebda2b5e.png> [Image removed by sender. NetController]<https://user-images.githubusercontent.com/4157364/241647381-c46acf7e-33ff-4181-8799-90a746eabbca.png> [Image removed by sender. PortProfile]<https://user-images.githubusercontent.com/4157364/241647386-dc148240-5b4a-4793-94ec-af1a2f02b2a8.png> [Image removed by sender. VirtualSwitchesOnHost]<https://user-images.githubusercontent.com/4157364/241647392-dea5e9f6-9839-4a29-8ea9-559ede56e84e.png> [Image removed by sender. VMHardwareConfig]<https://user-images.githubusercontent.com/4157364/241647395-60531c9e-88c3-40cf-9900-ad055612f758.png> [Image removed by sender. VMNetwork-Connectivity(only want HNV between VMs on this network)]<https://user-images.githubusercontent.com/4157364/241647398-f3e97079-6f2e-417b-9401-ebebd0f94019.png> [Image removed by sender. VMNetwork-IsolatedNetworks]<https://user-images.githubusercontent.com/4157364/241647403-e43dba5f-d614-4e63-9c6a-396252ace18d.png> - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63M2ESZSREB5WYUYT2LXIQW3JANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.***>

Hi Anirban, Maybe I’m missing something here (quite likely). Ipconfig /allcompartments /all shows no IPs assigned from the PA for Isolated Networks, but as it’s assigned to the dedicated NIC for the VM network there are no specific IPs provided there? The IPs listed are only on the management NIC. In the testlab on the Physical host servers I have two NICs (production we have 3 with dedicated SAN network). NIC1: Management NIC – not managed by Network Controller and has static IPs in our management network in the range (192.168.5.0/255.255.0.0) with gateway 192.168.1.1 NIC2: VM NIC – managed by Network Controller and has two logical networks: New Logical Network (192.168.0.0/18) – overlaps management network so we could use a common gateway IP as it’s a test lab (production does not overlap and has separate gateways per /24). IP Pool is 192.168.6.0-192.168.6.254 with gateway at 192.168.1.1 Isolated Networks (192.168.100.0/22) – this one does not function the hosts never get issued a PA IP, and DHCP doesn’t function. The “Isolated Networks” logical network which is managed by the network controller is the problem. I need to be able to have the VMs use VM Networks that are created where the logical network is Isolated Networks, these are setup for internal communication between specific VMs. There is one logical switch “New Virtual Network” which is managed by the network controller and uses the ‘New Virtual Network’ uplink, whereby both Logical Networks are checked (Isolated Networks and New Logical Network). Enable Hyper-V Network Virtualization is also checked – the production cluster was originally upgraded from 2012 to 2016. This matches the Uplink Port Profile ‘New Virtual Network’ which has both Logical Networks and Network Sites checked as per the logical switch. The physical hosts can reach the network controllers and show no errors. Is there any way I can reach Sonal directly to discuss with him? This is more than likely a major misunderstanding on my part for how to structure the networks to get the VMs to be able to use the HNV networks in 2019. The upgrade path from the SCVMM managed network virtualization to the Network Controller managed network virtualization is really not straight forward, and also removes the ability to use x.x.x.1-x.x.x.3 on the virtualized subnets which means disruption after upgrade to some clients as well as their internal IPs will need to change. Thanks, Will From: Anirban Paul ***@***.***> Sent: Wednesday, May 31, 2023 3:25 AM To: microsoft/SDN ***@***.***> Cc: willkruss ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) +Sonal from the VMM team @sonal ***@***.*** <mailto:***@***.***> >, can you please check the configuration for accuracy. Will, are you able to see IP addresses from the HNV PA network on the physical host where the tenant VM is located? You can check this by running ipconfig /allcompartments /all on the host machine. @sonal ***@***.*** <mailto:***@***.***> >, how can they check the ConfigurationState of the Servers resource from VMM? I can provide REST commands directly, but wondering if VMM also exposes them. Thanks Anirban From: willkruss ***@***.*** <mailto:***@***.***> > Sent: Sunday, May 28, 2023 10:21 PM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Thank you for the explanation. I have everything running in my test lab, however, for some reason the network controller are not handing out DHCP leases for the IP Pools in the VM Networks which use HNV. It assigns the IP according to system center correctly, but inside the operating system we get DHCPDISCOVER -> No DHCPOFFERS received. Oddly it appears that the Logical Network I created for HNV (Isolated Networks) is not allocating IPs from the IP Pool to the hosts in the manner it worked without using the Network Controller (PA Addresses unused). I've attached screen shots of the setup. If you have any ideas I've love to hear them. Thanks, Will [Image removed by sender. HardwareLogicalNetworkConnectivityOnHost]<https://user-images.githubusercontent.com/4157364/241647351-a6bd5b1c-db10-4f54-955d-c914e2c4923c.png> [Image removed by sender. IsolatedNetworksPAAddresses]<https://user-images.githubusercontent.com/4157364/241647367-7a517484-72aa-45cf-887e-322caf29c05f.png> [Image removed by sender. LogicalNetworks]<https://user-images.githubusercontent.com/4157364/241647374-b72bf2dc-5903-4834-bef8-1c3d0f5f9143.png> [Image removed by sender. LogicalSwitch]<https://user-images.githubusercontent.com/4157364/241647378-bade43fa-ca47-48c4-bb15-fb19ebda2b5e.png> [Image removed by sender. NetController]<https://user-images.githubusercontent.com/4157364/241647381-c46acf7e-33ff-4181-8799-90a746eabbca.png> [Image removed by sender. PortProfile]<https://user-images.githubusercontent.com/4157364/241647386-dc148240-5b4a-4793-94ec-af1a2f02b2a8.png> [Image removed by sender. VirtualSwitchesOnHost]<https://user-images.githubusercontent.com/4157364/241647392-dea5e9f6-9839-4a29-8ea9-559ede56e84e.png> [Image removed by sender. VMHardwareConfig]<https://user-images.githubusercontent.com/4157364/241647395-60531c9e-88c3-40cf-9900-ad055612f758.png> [Image removed by sender. VMNetwork-Connectivity(only want HNV between VMs on this network)]<https://user-images.githubusercontent.com/4157364/241647398-f3e97079-6f2e-417b-9401-ebebd0f94019.png> [Image removed by sender. VMNetwork-IsolatedNetworks]<https://user-images.githubusercontent.com/4157364/241647403-e43dba5f-d614-4e63-9c6a-396252ace18d.png> - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63M2ESZSREB5WYUYT2LXIQW3JANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> > — Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NF4KCLLOQ3ECFOWTB3XIYUOXANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NBHQOAU4FUR6MCHHJLXIYUOXA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS5QICM6.gif> Message ID: ***@***.*** ***@***.***> >

***@***.*** Kant ***@***.***> to help with the query Thanks, Sonal From: Anirban Paul ***@***.***> Sent: Tuesday, May 30, 2023 10:55 PM To: microsoft/SDN ***@***.***>; microsoft/SDN ***@***.***>; Sonal Agarwal ***@***.***> Cc: Comment ***@***.***> Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) +Sonal from the VMM team @sonal ***@***.***>, can you please check the configuration for accuracy. Will, are you able to see IP addresses from the HNV PA network on the physical host where the tenant VM is located? You can check this by running ipconfig /allcompartments /all on the host machine. @sonal ***@***.***>, how can they check the ConfigurationState of the Servers resource from VMM? I can provide REST commands directly, but wondering if VMM also exposes them. Thanks Anirban From: willkruss ***@***.******@***.***>> Sent: Sunday, May 28, 2023 10:21 PM To: microsoft/SDN ***@***.******@***.***>> Cc: Anirban Paul ***@***.******@***.***>>; Comment ***@***.******@***.***>> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Thank you for the explanation. I have everything running in my test lab, however, for some reason the network controller are not handing out DHCP leases for the IP Pools in the VM Networks which use HNV. It assigns the IP according to system center correctly, but inside the operating system we get DHCPDISCOVER -> No DHCPOFFERS received. Oddly it appears that the Logical Network I created for HNV (Isolated Networks) is not allocating IPs from the IP Pool to the hosts in the manner it worked without using the Network Controller (PA Addresses unused). I've attached screen shots of the setup. If you have any ideas I've love to hear them. Thanks, Will [Image removed by sender. HardwareLogicalNetworkConnectivityOnHost]<https://user-images.githubusercontent.com/4157364/241647351-a6bd5b1c-db10-4f54-955d-c914e2c4923c.png> [Image removed by sender. IsolatedNetworksPAAddresses]<https://user-images.githubusercontent.com/4157364/241647367-7a517484-72aa-45cf-887e-322caf29c05f.png> [Image removed by sender. LogicalNetworks]<https://user-images.githubusercontent.com/4157364/241647374-b72bf2dc-5903-4834-bef8-1c3d0f5f9143.png> [Image removed by sender. LogicalSwitch]<https://user-images.githubusercontent.com/4157364/241647378-bade43fa-ca47-48c4-bb15-fb19ebda2b5e.png> [Image removed by sender. NetController]<https://user-images.githubusercontent.com/4157364/241647381-c46acf7e-33ff-4181-8799-90a746eabbca.png> [Image removed by sender. PortProfile]<https://user-images.githubusercontent.com/4157364/241647386-dc148240-5b4a-4793-94ec-af1a2f02b2a8.png> [Image removed by sender. VirtualSwitchesOnHost]<https://user-images.githubusercontent.com/4157364/241647392-dea5e9f6-9839-4a29-8ea9-559ede56e84e.png> [Image removed by sender. VMHardwareConfig]<https://user-images.githubusercontent.com/4157364/241647395-60531c9e-88c3-40cf-9900-ad055612f758.png> [Image removed by sender. VMNetwork-Connectivity(only want HNV between VMs on this network)]<https://user-images.githubusercontent.com/4157364/241647398-f3e97079-6f2e-417b-9401-ebebd0f94019.png> [Image removed by sender. VMNetwork-IsolatedNetworks]<https://user-images.githubusercontent.com/4157364/241647403-e43dba5f-d614-4e63-9c6a-396252ace18d.png> - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63M2ESZSREB5WYUYT2LXIQW3JANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

Hi Shashi, Unfortunately we aren’t using VLANs at all, and don’t see a reason to use them. There must be something simple I’m missing. Is there any way I can contract one of your team to login to our testlab remotely and get it working. Then advise how this was done. I’m happy to pay for this support. We just need a way to get the Network Controller functioning so that VMs have access to isolated networking through network virtualization. The logical network I create with network virtualization I cannot get to work. The regular logical network works fine. I’ve used the port profiles on the uplink and ensured both Network Sites (my isolated and regular logical network are checked). There is only one Logical Switch and it also lists both the network sites as per the port profile. There are no ‘virtual network adapters’ configured in the Logical Switch -> Uplinks properties (I’ve tried creating but as can only associated with the VM Network that does not use network virtualization I didn’t make any difference). Happy to pay for someone to help us get this up and running. Thanks, Will Kruss From: shalal1095 ***@***.***> Sent: Wednesday, May 31, 2023 11:42 PM To: microsoft/SDN ***@***.***> Cc: willkruss ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) @.*** Kant @.> to help with the query Thanks, Sonal From: Anirban Paul @.> Sent: Tuesday, May 30, 2023 10:55 PM To: microsoft/SDN @.>; microsoft/SDN @.>; Sonal Agarwal @.> Cc: Comment @.> Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572 <#572> ) +Sonal from the VMM team @sonal <https://github.com/sonal> @.>, can you please check the configuration for accuracy. Will, are you able to see IP addresses from the HNV PA network on the physical host where the tenant VM is located? You can check this by running ipconfig /allcompartments /all on the host machine. @sonal <https://github.com/sonal> @.>, how can they check the ConfigurationState of the Servers resource from VMM? I can provide REST commands directly, but wondering if VMM also exposes them. Thanks Anirban From: willkruss @.@.>> Sent: Sunday, May 28, 2023 10:21 PM To: microsoft/SDN @.@.>> Cc: Anirban Paul @.@.>>; Comment @.@.>> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572 <#572> ) Hi Anirban, Thank you for the explanation. I have everything running in my test lab, however, for some reason the network controller are not handing out DHCP leases for the IP Pools in the VM Networks which use HNV. It assigns the IP according to system center correctly, but inside the operating system we get DHCPDISCOVER -> No DHCPOFFERS received. Oddly it appears that the Logical Network I created for HNV (Isolated Networks) is not allocating IPs from the IP Pool to the hosts in the manner it worked without using the Network Controller (PA Addresses unused). I've attached screen shots of the setup. If you have any ideas I've love to hear them. Thanks, Will [Image removed by sender. HardwareLogicalNetworkConnectivityOnHost]https://user-images.githubusercontent.com/4157364/241647351-a6bd5b1c-db10-4f54-955d-c914e2c4923c.png [Image removed by sender. IsolatedNetworksPAAddresses]https://user-images.githubusercontent.com/4157364/241647367-7a517484-72aa-45cf-887e-322caf29c05f.png [Image removed by sender. LogicalNetworks]https://user-images.githubusercontent.com/4157364/241647374-b72bf2dc-5903-4834-bef8-1c3d0f5f9143.png [Image removed by sender. LogicalSwitch]https://user-images.githubusercontent.com/4157364/241647378-bade43fa-ca47-48c4-bb15-fb19ebda2b5e.png [Image removed by sender. NetController]https://user-images.githubusercontent.com/4157364/241647381-c46acf7e-33ff-4181-8799-90a746eabbca.png [Image removed by sender. PortProfile]https://user-images.githubusercontent.com/4157364/241647386-dc148240-5b4a-4793-94ec-af1a2f02b2a8.png [Image removed by sender. VirtualSwitchesOnHost]https://user-images.githubusercontent.com/4157364/241647392-dea5e9f6-9839-4a29-8ea9-559ede56e84e.png [Image removed by sender. VMHardwareConfig]https://user-images.githubusercontent.com/4157364/241647395-60531c9e-88c3-40cf-9900-ad055612f758.png [Image removed by sender. VMNetwork-Connectivity(only want HNV between VMs on this network)]https://user-images.githubusercontent.com/4157364/241647398-f3e97079-6f2e-417b-9401-ebebd0f94019.png [Image removed by sender. VMNetwork-IsolatedNetworks]https://user-images.githubusercontent.com/4157364/241647403-e43dba5f-d614-4e63-9c6a-396252ace18d.png - Reply to this email directly, view it on GitHub<#572 (comment) <#572 (comment)> >, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEBB63M2ESZSREB5WYUYT2LXIQW3JANCNFSM6AAAAAAX23GHYQ. You are receiving this because you commented.Message ID: @.@.>> Hi Will, Are you able to get IP for the Tenant VMs created having Tenant VM Network. As per my knowledge the Physical Host should have access to the HNVPA logical network access. i.e the HNVPA VLAN should be configured as a trunk VLAN in physical host NIC and the Tenant VM Network should be created on top of HNVPA logical network with virtual IP. e.g Host NIC Trunk VLAN has 220, 221, 222, 223 NC Management logical Network is created with VLAN 222 HNVPA logical network is created with VLAN 223 Virtual Switch on Host NIC should have Network site of VLAN 222 and 223 Tenant VM Network have VM Subnet with VLAN 1 and Virtual IP. Tenant VM is connected with Tenant VM Network Can you try with this scenario. Thanks, Shashi — Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NDRRSX4ZCQ4DPIGO7DXI5DDRANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NFDOWF3GP26LDFLJVTXI5DDRA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS5TBFR6.gif> Message ID: ***@***.*** ***@***.***> >

Hi Anirban, No it’s not, I’m happy to pay someone to login to our testlab and go over the configuration. We really just need to know what we are doing incorrectly and we don’t have a proper understanding of it. Thanks, Will From: Anirban Paul ***@***.***> Sent: Saturday, June 3, 2023 9:12 AM To: microsoft/SDN ***@***.***> Cc: willkruss ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will Is this issue resolved. If not, can you send email to ***@***.*** ***@***.***> Thanks Anirban — Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NGRPU6DSFEN2ZC7Z5LXJJXMFANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NHHYNPLMC4JDG2CVPLXJJXMFA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS527IUU.gif> Message ID: ***@***.*** ***@***.***> >

Hi @***@***.***>, Can you check if we can help will with this support. I am not familiar with the process of filing support cases. Thanks, Shashi From: willkruss ***@***.***> Sent: Saturday, June 3, 2023 5:12 AM To: microsoft/SDN ***@***.***> Cc: Shashi Kant Lal ***@***.***>; Comment ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, No it's not, I'm happy to pay someone to login to our testlab and go over the configuration. We really just need to know what we are doing incorrectly and we don't have a proper understanding of it. Thanks, Will From: Anirban Paul ***@***.***<mailto:***@***.***>> Sent: Saturday, June 3, 2023 9:12 AM To: microsoft/SDN ***@***.***<mailto:***@***.***>> Cc: willkruss ***@***.***<mailto:***@***.***>>; Author ***@***.***<mailto:***@***.***>> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will Is this issue resolved. If not, can you send email to ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>> Thanks Anirban - Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NGRPU6DSFEN2ZC7Z5LXJJXMFANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NHHYNPLMC4JDG2CVPLXJJXMFA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS527IUU.gif> Message ID: ***@***.***<mailto:***@***.***> ***@***.***<mailto:***@***.***>> > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQGP3PAGVOR455ZBWBBRVDLXJJ25HANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

Hi All, We really are happy to pay someone personally who is familiar with installing the network controller and configuring for use with HNV. It doesn’t have to be through Microsoft support or anything like that, if there is someone who has the technical ability and is happy to work, just give me an hourly rate. It can of course be through Microsoft, or a recommendation for someone who has these skills and provides technical services. We just need a clear and concise way of getting the network controller up and running on our VM network with HNV enabled for isolated networks between VMs. Cheers, Will From: shalal1095 ***@***.***> Sent: Sunday, June 4, 2023 11:55 PM To: microsoft/SDN ***@***.***> Cc: willkruss ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi @***@***.***>, Can you check if we can help will with this support. I am not familiar with the process of filing support cases. Thanks, Shashi From: willkruss ***@***.*** <mailto:***@***.***> > Sent: Saturday, June 3, 2023 5:12 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: Shashi Kant Lal ***@***.*** <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, No it's not, I'm happy to pay someone to login to our testlab and go over the configuration. We really just need to know what we are doing incorrectly and we don't have a proper understanding of it. Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***%3cmailto:***@***.***> <mailto:***@***.***>> Sent: Saturday, June 3, 2023 9:12 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***%3cmailto:***@***.***> <mailto:***@***.***>> Cc: willkruss ***@***.*** <mailto:***@***.***%3cmailto:***@***.***> <mailto:***@***.***>>; Author ***@***.*** <mailto:***@***.***%3cmailto:***@***.***> <mailto:***@***.***>> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will Is this issue resolved. If not, can you send email to ***@***.*** <mailto:***@***.***%3cmailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***%3cmailto:***@***.***> <mailto:***@***.***>> Thanks Anirban - Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NGRPU6DSFEN2ZC7Z5LXJJXMFANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NHHYNPLMC4JDG2CVPLXJJXMFA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS527IUU.gif> Message ID: ***@***.*** <mailto:***@***.***%3cmailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***%3cmailto:***@***.***> <mailto:***@***.***>> > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQGP3PAGVOR455ZBWBBRVDLXJJ25HANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.******@***.*** <mailto:***@***.******@***.***> >> — Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NGFSQH57CUQITMCJL3XJSHU7ANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NC2E6V64N5G7ECFI63XJSHU7A5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS55FXH4.gif> Message ID: ***@***.*** ***@***.***> >

Hi Anirban, Can you please answer me this question: We have 3 NICs on our host servers: 1. SAN NIC – Hosts use this to connect to the cluster SANs 2. Management NIC – We have no logical network or switch created in SCVMM for this. All IPs are statically assigned to the hosts. 3. VM NIC – This is created using a Logical Network with no management access and is for VM public NICs, also assigning IPs from Pools, and lastly for isolated HNV networks between VMs. I have been trying to install the network controllers on the VM NIC network where the logical network is setup. If I create a new logical network for management and install the network controllers on the Management network it tells me the network controllers are not assigned to the physical network adapter that the VMs are using so I cannot control any VM networking. If I install the network controllers on the VM Logical Network (Physical VM NIC) there seems to be issues with networking and speaking to the hosts properly. Where am I supposed to install the network controllers, and how do I get them to be able to manage networks on the VM Network so I can use HNV there? Thanks, Will From: Anirban Paul ***@***.***> Sent: Saturday, June 3, 2023 9:12 AM To: microsoft/SDN ***@***.***> Cc: willkruss ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will Is this issue resolved. If not, can you send email to ***@***.*** ***@***.***> Thanks Anirban — Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NGRPU6DSFEN2ZC7Z5LXJJXMFANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NHHYNPLMC4JDG2CVPLXJJXMFA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS527IUU.gif> Message ID: ***@***.*** ***@***.***> >

Hi Will The Network Controller VMs need to have access to the Management network since they communicate with hosts to push policy and learn about VMs on the host. Network Controller does not need access to the VM NIC network. This is how it works: 1. NC VMs get IPs from the management network. If this is different from the host management network, ensure that there is routing between the two networks. 2. Hosts are assigned IP Addresses from the HNVPA network by the Network Controller. If IP is not getting assigned, there is some communication issue between the hosts and the Network Controller. 3. The HNVPA network is the underlying physical network for forwarding the virtual network traffic. So, your tenant VMs would get IPs from a virtual network (Which can be a completely fictitious network with no presence in the underlying physical network), your hosts will get IPs from management and HNV PA networks (latter being assigned by the Network Controller), and your NC VMs will get IP from the management network. There are a few sample topologies for NC here: Plan to deploy Network Controller - Azure Stack HCI | Microsoft Learn<https://learn.microsoft.com/en-us/azure-stack/hci/concepts/network-controller#network-controller-requirements> Thanks Anirban From: willkruss ***@***.***> Sent: Monday, June 5, 2023 8:26 PM To: microsoft/SDN ***@***.***> Cc: Anirban Paul ***@***.***>; Comment ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Can you please answer me this question: We have 3 NICs on our host servers: 1. SAN NIC - Hosts use this to connect to the cluster SANs 2. Management NIC - We have no logical network or switch created in SCVMM for this. All IPs are statically assigned to the hosts. 3. VM NIC - This is created using a Logical Network with no management access and is for VM public NICs, also assigning IPs from Pools, and lastly for isolated HNV networks between VMs. I have been trying to install the network controllers on the VM NIC network where the logical network is setup. If I create a new logical network for management and install the network controllers on the Management network it tells me the network controllers are not assigned to the physical network adapter that the VMs are using so I cannot control any VM networking. If I install the network controllers on the VM Logical Network (Physical VM NIC) there seems to be issues with networking and speaking to the hosts properly. Where am I supposed to install the network controllers, and how do I get them to be able to manage networks on the VM Network so I can use HNV there? Thanks, Will From: Anirban Paul ***@***.***> Sent: Saturday, June 3, 2023 9:12 AM To: microsoft/SDN ***@***.***> Cc: willkruss ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will Is this issue resolved. If not, can you send email to ***@***.*** ***@***.***> Thanks Anirban - Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NGRPU6DSFEN2ZC7Z5LXJJXMFANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NHHYNPLMC4JDG2CVPLXJJXMFA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS527IUU.gif> Message ID: ***@***.*** ***@***.***> > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63OAPXAARWNHUKW27MLXJ2PMRANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.***>

Hi Anirban, Okay, that helps, the problem I’ve got is because we setup the physical infrastructure in 2012 the recommendation was at the time to have separate networks for VM network and host management network. Our networks are physically completely different (traffic literally has to pass to our edge firewall and back when a VM is talking to a host server for example). This works brilliantly, but also means we haven’t had to setup logical switches – just the logical network for VM communication, and host management network the hosts are given static IPs. We still have redundant domain controllers and such running on the VM network, but their communication with our physical DCs on the management networks goes through our edge firewall and back. This means we cannot use NIC teaming, as both networks are not connected. If we cannot use NIC teaming, and we setup the NCs on our host management network (easy enough). The problem is I create a switch on the management network which is used when provisioning the network controllers. But then I cannot create a virtual switch for the VM network as I get the error below: Error (50208) Cannot create virtual switch on the host 'VM1.TESTLAB.local' because there already exists a virtual switch on the host that is managed by Microsoft Network Controller. Recommended Action Ensure that the host does not have any other virtual switch managed by Microsoft Network Controller. So how do I get it so that the NCs are provisioned in my management network, but so that the VM network is controlled by the network controller so I can use network virtualization? I cannot use network virtualization in a network that isn’t controlled by the network controller as then I cannot upgrade to 2019 (we are running 2016 at this time). Does this explain what the issues I’m facing are? I’ve tried to provision the network controllers to the VM network instead of management network but then of course they aren’t provisioned with correct networking. I’m really at a loss how to proceed. Thanks, Will From: Anirban Paul ***@***.***> Sent: Wednesday, June 7, 2023 5:36 AM To: microsoft/SDN ***@***.***> Cc: willkruss ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will The Network Controller VMs need to have access to the Management network since they communicate with hosts to push policy and learn about VMs on the host. Network Controller does not need access to the VM NIC network. This is how it works: 1. NC VMs get IPs from the management network. If this is different from the host management network, ensure that there is routing between the two networks. 2. Hosts are assigned IP Addresses from the HNVPA network by the Network Controller. If IP is not getting assigned, there is some communication issue between the hosts and the Network Controller. 3. The HNVPA network is the underlying physical network for forwarding the virtual network traffic. So, your tenant VMs would get IPs from a virtual network (Which can be a completely fictitious network with no presence in the underlying physical network), your hosts will get IPs from management and HNV PA networks (latter being assigned by the Network Controller), and your NC VMs will get IP from the management network. There are a few sample topologies for NC here: Plan to deploy Network Controller - Azure Stack HCI | Microsoft Learn<https://learn.microsoft.com/en-us/azure-stack/hci/concepts/network-controller#network-controller-requirements> Thanks Anirban From: willkruss ***@***.*** <mailto:***@***.***> > Sent: Monday, June 5, 2023 8:26 PM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Can you please answer me this question: We have 3 NICs on our host servers: 1. SAN NIC - Hosts use this to connect to the cluster SANs 2. Management NIC - We have no logical network or switch created in SCVMM for this. All IPs are statically assigned to the hosts. 3. VM NIC - This is created using a Logical Network with no management access and is for VM public NICs, also assigning IPs from Pools, and lastly for isolated HNV networks between VMs. I have been trying to install the network controllers on the VM NIC network where the logical network is setup. If I create a new logical network for management and install the network controllers on the Management network it tells me the network controllers are not assigned to the physical network adapter that the VMs are using so I cannot control any VM networking. If I install the network controllers on the VM Logical Network (Physical VM NIC) there seems to be issues with networking and speaking to the hosts properly. Where am I supposed to install the network controllers, and how do I get them to be able to manage networks on the VM Network so I can use HNV there? Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***> > Sent: Saturday, June 3, 2023 9:12 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: willkruss ***@***.*** <mailto:***@***.***> >; Author ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will Is this issue resolved. If not, can you send email to ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > Thanks Anirban - Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NGRPU6DSFEN2ZC7Z5LXJJXMFANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NHHYNPLMC4JDG2CVPLXJJXMFA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS527IUU.gif> Message ID: ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63OAPXAARWNHUKW27MLXJ2PMRANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> > — Reply to this email directly, <#572 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AA7W7NGTAG5A3PT4Z3XONC3XJ6BCJANCNFSM6AAAAAAX23GHYQ> unsubscribe. You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NBQEF7DO4KJ7FE5JMTXJ6BCJA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6ELGD6.gif> Message ID: < ***@***.***> ***@***.***>

Hi Anirban, Further to my last email, if I try to get both networks setup on the same logical switch by using Embedded teaming I can’t then assign a different uplink port profile to each physical NIC. So I’m at a complete loss at the moment. We can’t change the physical connections of the servers, we need to run a network controller that will have IPs assigned on the management network, but control the VM network (two physically different networks both connected). Any suggestions? This seems like a huge problem in the flexibility of the system as far as I can see, and as we have 1000 VMs in production we can’t simply change physical networking around. Thanks, Will From: William Kruss ***@***.***> Sent: Wednesday, June 7, 2023 4:00 PM To: 'microsoft/SDN' ***@***.***>; 'microsoft/SDN' ***@***.***> Cc: 'Author' ***@***.***> Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Okay, that helps, the problem I’ve got is because we setup the physical infrastructure in 2012 the recommendation was at the time to have separate networks for VM network and host management network. Our networks are physically completely different (traffic literally has to pass to our edge firewall and back when a VM is talking to a host server for example). This works brilliantly, but also means we haven’t had to setup logical switches – just the logical network for VM communication, and host management network the hosts are given static IPs. We still have redundant domain controllers and such running on the VM network, but their communication with our physical DCs on the management networks goes through our edge firewall and back. This means we cannot use NIC teaming, as both networks are not connected. If we cannot use NIC teaming, and we setup the NCs on our host management network (easy enough). The problem is I create a switch on the management network which is used when provisioning the network controllers. But then I cannot create a virtual switch for the VM network as I get the error below: Error (50208) Cannot create virtual switch on the host 'VM1.TESTLAB.local' because there already exists a virtual switch on the host that is managed by Microsoft Network Controller. Recommended Action Ensure that the host does not have any other virtual switch managed by Microsoft Network Controller. So how do I get it so that the NCs are provisioned in my management network, but so that the VM network is controlled by the network controller so I can use network virtualization? I cannot use network virtualization in a network that isn’t controlled by the network controller as then I cannot upgrade to 2019 (we are running 2016 at this time). Does this explain what the issues I’m facing are? I’ve tried to provision the network controllers to the VM network instead of management network but then of course they aren’t provisioned with correct networking. I’m really at a loss how to proceed. Thanks, Will From: Anirban Paul ***@***.*** ***@***.***> > Sent: Wednesday, June 7, 2023 5:36 AM To: microsoft/SDN ***@***.*** ***@***.***> > Cc: willkruss ***@***.*** ***@***.***> >; Author ***@***.*** ***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will The Network Controller VMs need to have access to the Management network since they communicate with hosts to push policy and learn about VMs on the host. Network Controller does not need access to the VM NIC network. This is how it works: 1. NC VMs get IPs from the management network. If this is different from the host management network, ensure that there is routing between the two networks. 2. Hosts are assigned IP Addresses from the HNVPA network by the Network Controller. If IP is not getting assigned, there is some communication issue between the hosts and the Network Controller. 3. The HNVPA network is the underlying physical network for forwarding the virtual network traffic. So, your tenant VMs would get IPs from a virtual network (Which can be a completely fictitious network with no presence in the underlying physical network), your hosts will get IPs from management and HNV PA networks (latter being assigned by the Network Controller), and your NC VMs will get IP from the management network. There are a few sample topologies for NC here: Plan to deploy Network Controller - Azure Stack HCI | Microsoft Learn<https://learn.microsoft.com/en-us/azure-stack/hci/concepts/network-controller#network-controller-requirements> Thanks Anirban From: willkruss ***@***.*** <mailto:***@***.***> > Sent: Monday, June 5, 2023 8:26 PM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Can you please answer me this question: We have 3 NICs on our host servers: 1. SAN NIC - Hosts use this to connect to the cluster SANs 2. Management NIC - We have no logical network or switch created in SCVMM for this. All IPs are statically assigned to the hosts. 3. VM NIC - This is created using a Logical Network with no management access and is for VM public NICs, also assigning IPs from Pools, and lastly for isolated HNV networks between VMs. I have been trying to install the network controllers on the VM NIC network where the logical network is setup. If I create a new logical network for management and install the network controllers on the Management network it tells me the network controllers are not assigned to the physical network adapter that the VMs are using so I cannot control any VM networking. If I install the network controllers on the VM Logical Network (Physical VM NIC) there seems to be issues with networking and speaking to the hosts properly. Where am I supposed to install the network controllers, and how do I get them to be able to manage networks on the VM Network so I can use HNV there? Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***> > Sent: Saturday, June 3, 2023 9:12 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: willkruss ***@***.*** <mailto:***@***.***> >; Author ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will Is this issue resolved. If not, can you send email to ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > Thanks Anirban - Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NGRPU6DSFEN2ZC7Z5LXJJXMFANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NHHYNPLMC4JDG2CVPLXJJXMFA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS527IUU.gif> Message ID: ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63OAPXAARWNHUKW27MLXJ2PMRANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> > — Reply to this email directly, <#572 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AA7W7NGTAG5A3PT4Z3XONC3XJ6BCJANCNFSM6AAAAAAX23GHYQ> unsubscribe. You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NBQEF7DO4KJ7FE5JMTXJ6BCJA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6ELGD6.gif> Message ID: < ***@***.***> ***@***.***>

Hi Anirban, I know you are going to be sick of hearing from me, but it seems it’s simply not possible to have a different physical management and VM tenant network with the network controller. Since the switch cannot manage two networks and allow you to specify different port uplinks per for each NIC, I provisioned the network controllers using a standard switch for the management network, and have the logical switch on the VM Network. This looks fine on paper, the network controllers create without issue and the netcontroller is accessible. However, you cannot provision it as it errors saying: Network controller VMs part of service instance NetController should all be connected to instances of the same logical switch. Recommended Action Connect all VMs to management VM network through instances of a common logical switch and retry. I’m at a complete loss how to get this to work. Can I add a second NIC to the network controllers and assign that to the VM Network on the Logical Switch? Thanks, Will From: William Kruss ***@***.***> Sent: Thursday, June 8, 2023 10:56 AM To: 'microsoft/SDN' ***@***.***>; 'microsoft/SDN' ***@***.***> Cc: 'Author' ***@***.***> Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Further to my last email, if I try to get both networks setup on the same logical switch by using Embedded teaming I can’t then assign a different uplink port profile to each physical NIC. So I’m at a complete loss at the moment. We can’t change the physical connections of the servers, we need to run a network controller that will have IPs assigned on the management network, but control the VM network (two physically different networks both connected). Any suggestions? This seems like a huge problem in the flexibility of the system as far as I can see, and as we have 1000 VMs in production we can’t simply change physical networking around. Thanks, Will From: William Kruss ***@***.*** ***@***.***> > Sent: Wednesday, June 7, 2023 4:00 PM To: 'microsoft/SDN' ***@***.*** ***@***.***> >; 'microsoft/SDN' ***@***.*** ***@***.***> > Cc: 'Author' ***@***.*** ***@***.***> > Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Okay, that helps, the problem I’ve got is because we setup the physical infrastructure in 2012 the recommendation was at the time to have separate networks for VM network and host management network. Our networks are physically completely different (traffic literally has to pass to our edge firewall and back when a VM is talking to a host server for example). This works brilliantly, but also means we haven’t had to setup logical switches – just the logical network for VM communication, and host management network the hosts are given static IPs. We still have redundant domain controllers and such running on the VM network, but their communication with our physical DCs on the management networks goes through our edge firewall and back. This means we cannot use NIC teaming, as both networks are not connected. If we cannot use NIC teaming, and we setup the NCs on our host management network (easy enough). The problem is I create a switch on the management network which is used when provisioning the network controllers. But then I cannot create a virtual switch for the VM network as I get the error below: Error (50208) Cannot create virtual switch on the host 'VM1.TESTLAB.local' because there already exists a virtual switch on the host that is managed by Microsoft Network Controller. Recommended Action Ensure that the host does not have any other virtual switch managed by Microsoft Network Controller. So how do I get it so that the NCs are provisioned in my management network, but so that the VM network is controlled by the network controller so I can use network virtualization? I cannot use network virtualization in a network that isn’t controlled by the network controller as then I cannot upgrade to 2019 (we are running 2016 at this time). Does this explain what the issues I’m facing are? I’ve tried to provision the network controllers to the VM network instead of management network but then of course they aren’t provisioned with correct networking. I’m really at a loss how to proceed. Thanks, Will From: Anirban Paul ***@***.*** ***@***.***> > Sent: Wednesday, June 7, 2023 5:36 AM To: microsoft/SDN ***@***.*** ***@***.***> > Cc: willkruss ***@***.*** ***@***.***> >; Author ***@***.*** ***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will The Network Controller VMs need to have access to the Management network since they communicate with hosts to push policy and learn about VMs on the host. Network Controller does not need access to the VM NIC network. This is how it works: 1. NC VMs get IPs from the management network. If this is different from the host management network, ensure that there is routing between the two networks. 2. Hosts are assigned IP Addresses from the HNVPA network by the Network Controller. If IP is not getting assigned, there is some communication issue between the hosts and the Network Controller. 3. The HNVPA network is the underlying physical network for forwarding the virtual network traffic. So, your tenant VMs would get IPs from a virtual network (Which can be a completely fictitious network with no presence in the underlying physical network), your hosts will get IPs from management and HNV PA networks (latter being assigned by the Network Controller), and your NC VMs will get IP from the management network. There are a few sample topologies for NC here: Plan to deploy Network Controller - Azure Stack HCI | Microsoft Learn<https://learn.microsoft.com/en-us/azure-stack/hci/concepts/network-controller#network-controller-requirements> Thanks Anirban From: willkruss ***@***.*** <mailto:***@***.***> > Sent: Monday, June 5, 2023 8:26 PM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Can you please answer me this question: We have 3 NICs on our host servers: 1. SAN NIC - Hosts use this to connect to the cluster SANs 2. Management NIC - We have no logical network or switch created in SCVMM for this. All IPs are statically assigned to the hosts. 3. VM NIC - This is created using a Logical Network with no management access and is for VM public NICs, also assigning IPs from Pools, and lastly for isolated HNV networks between VMs. I have been trying to install the network controllers on the VM NIC network where the logical network is setup. If I create a new logical network for management and install the network controllers on the Management network it tells me the network controllers are not assigned to the physical network adapter that the VMs are using so I cannot control any VM networking. If I install the network controllers on the VM Logical Network (Physical VM NIC) there seems to be issues with networking and speaking to the hosts properly. Where am I supposed to install the network controllers, and how do I get them to be able to manage networks on the VM Network so I can use HNV there? Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***> > Sent: Saturday, June 3, 2023 9:12 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: willkruss ***@***.*** <mailto:***@***.***> >; Author ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will Is this issue resolved. If not, can you send email to ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > Thanks Anirban - Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NGRPU6DSFEN2ZC7Z5LXJJXMFANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NHHYNPLMC4JDG2CVPLXJJXMFA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS527IUU.gif> Message ID: ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63OAPXAARWNHUKW27MLXJ2PMRANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> > — Reply to this email directly, <#572 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AA7W7NGTAG5A3PT4Z3XONC3XJ6BCJANCNFSM6AAAAAAX23GHYQ> unsubscribe. You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NBQEF7DO4KJ7FE5JMTXJ6BCJA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6ELGD6.gif> Message ID: < ***@***.***> ***@***.***>

Hi Will I can understand the issue. I have reached out to the VMM team. I will respond as soon as I hear back. Can you also reach out to the email alias provided at the bottom of this link: SDN Troubleshooting: UDP Communication failures and changing the Network Controller Certificate - Microsoft Community Hub<https://techcommunity.microsoft.com/t5/networking-blog/sdn-troubleshooting-udp-communication-failures-and-changing-the/ba-p/339694> Thanks Anirban From: willkruss ***@***.***> Sent: Wednesday, June 7, 2023 8:02 PM To: microsoft/SDN ***@***.***> Cc: Anirban Paul ***@***.***>; Comment ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, I know you are going to be sick of hearing from me, but it seems it's simply not possible to have a different physical management and VM tenant network with the network controller. Since the switch cannot manage two networks and allow you to specify different port uplinks per for each NIC, I provisioned the network controllers using a standard switch for the management network, and have the logical switch on the VM Network. This looks fine on paper, the network controllers create without issue and the netcontroller is accessible. However, you cannot provision it as it errors saying: Network controller VMs part of service instance NetController should all be connected to instances of the same logical switch. Recommended Action Connect all VMs to management VM network through instances of a common logical switch and retry. I'm at a complete loss how to get this to work. Can I add a second NIC to the network controllers and assign that to the VM Network on the Logical Switch? Thanks, Will From: William Kruss ***@***.***> Sent: Thursday, June 8, 2023 10:56 AM To: 'microsoft/SDN' ***@***.***>; 'microsoft/SDN' ***@***.***> Cc: 'Author' ***@***.***> Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Further to my last email, if I try to get both networks setup on the same logical switch by using Embedded teaming I can't then assign a different uplink port profile to each physical NIC. So I'm at a complete loss at the moment. We can't change the physical connections of the servers, we need to run a network controller that will have IPs assigned on the management network, but control the VM network (two physically different networks both connected). Any suggestions? This seems like a huge problem in the flexibility of the system as far as I can see, and as we have 1000 VMs in production we can't simply change physical networking around. Thanks, Will From: William Kruss ***@***.*** ***@***.***> > Sent: Wednesday, June 7, 2023 4:00 PM To: 'microsoft/SDN' ***@***.*** ***@***.***> >; 'microsoft/SDN' ***@***.*** ***@***.***> > Cc: 'Author' ***@***.*** ***@***.***> > Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Okay, that helps, the problem I've got is because we setup the physical infrastructure in 2012 the recommendation was at the time to have separate networks for VM network and host management network. Our networks are physically completely different (traffic literally has to pass to our edge firewall and back when a VM is talking to a host server for example). This works brilliantly, but also means we haven't had to setup logical switches - just the logical network for VM communication, and host management network the hosts are given static IPs. We still have redundant domain controllers and such running on the VM network, but their communication with our physical DCs on the management networks goes through our edge firewall and back. This means we cannot use NIC teaming, as both networks are not connected. If we cannot use NIC teaming, and we setup the NCs on our host management network (easy enough). The problem is I create a switch on the management network which is used when provisioning the network controllers. But then I cannot create a virtual switch for the VM network as I get the error below: Error (50208) Cannot create virtual switch on the host 'VM1.TESTLAB.local' because there already exists a virtual switch on the host that is managed by Microsoft Network Controller. Recommended Action Ensure that the host does not have any other virtual switch managed by Microsoft Network Controller. So how do I get it so that the NCs are provisioned in my management network, but so that the VM network is controlled by the network controller so I can use network virtualization? I cannot use network virtualization in a network that isn't controlled by the network controller as then I cannot upgrade to 2019 (we are running 2016 at this time). Does this explain what the issues I'm facing are? I've tried to provision the network controllers to the VM network instead of management network but then of course they aren't provisioned with correct networking. I'm really at a loss how to proceed. Thanks, Will From: Anirban Paul ***@***.*** ***@***.***> > Sent: Wednesday, June 7, 2023 5:36 AM To: microsoft/SDN ***@***.*** ***@***.***> > Cc: willkruss ***@***.*** ***@***.***> >; Author ***@***.*** ***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will The Network Controller VMs need to have access to the Management network since they communicate with hosts to push policy and learn about VMs on the host. Network Controller does not need access to the VM NIC network. This is how it works: 1. NC VMs get IPs from the management network. If this is different from the host management network, ensure that there is routing between the two networks. 2. Hosts are assigned IP Addresses from the HNVPA network by the Network Controller. If IP is not getting assigned, there is some communication issue between the hosts and the Network Controller. 3. The HNVPA network is the underlying physical network for forwarding the virtual network traffic. So, your tenant VMs would get IPs from a virtual network (Which can be a completely fictitious network with no presence in the underlying physical network), your hosts will get IPs from management and HNV PA networks (latter being assigned by the Network Controller), and your NC VMs will get IP from the management network. There are a few sample topologies for NC here: Plan to deploy Network Controller - Azure Stack HCI | Microsoft Learn<https://learn.microsoft.com/en-us/azure-stack/hci/concepts/network-controller#network-controller-requirements> Thanks Anirban From: willkruss ***@***.*** <mailto:***@***.***> > Sent: Monday, June 5, 2023 8:26 PM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Can you please answer me this question: We have 3 NICs on our host servers: 1. SAN NIC - Hosts use this to connect to the cluster SANs 2. Management NIC - We have no logical network or switch created in SCVMM for this. All IPs are statically assigned to the hosts. 3. VM NIC - This is created using a Logical Network with no management access and is for VM public NICs, also assigning IPs from Pools, and lastly for isolated HNV networks between VMs. I have been trying to install the network controllers on the VM NIC network where the logical network is setup. If I create a new logical network for management and install the network controllers on the Management network it tells me the network controllers are not assigned to the physical network adapter that the VMs are using so I cannot control any VM networking. If I install the network controllers on the VM Logical Network (Physical VM NIC) there seems to be issues with networking and speaking to the hosts properly. Where am I supposed to install the network controllers, and how do I get them to be able to manage networks on the VM Network so I can use HNV there? Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***> > Sent: Saturday, June 3, 2023 9:12 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: willkruss ***@***.*** <mailto:***@***.***> >; Author ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will Is this issue resolved. If not, can you send email to ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > Thanks Anirban - Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NGRPU6DSFEN2ZC7Z5LXJJXMFANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NHHYNPLMC4JDG2CVPLXJJXMFA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS527IUU.gif> Message ID: ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63OAPXAARWNHUKW27MLXJ2PMRANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> > - Reply to this email directly, <#572 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AA7W7NGTAG5A3PT4Z3XONC3XJ6BCJANCNFSM6AAAAAAX23GHYQ> unsubscribe. You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NBQEF7DO4KJ7FE5JMTXJ6BCJA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6ELGD6.gif> Message ID: < ***@***.***> ***@***.***> - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63OGBVMDETXQHRMNEUTXKE6B7ANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.***>

Hi Anirban, The page you linked to is under maintenance, looks like the whole techcommunity website is unavailable? Thanks, Will From: Anirban Paul ***@***.***> Sent: Friday, June 9, 2023 4:36 AM To: microsoft/SDN ***@***.***> Cc: willkruss ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will I can understand the issue. I have reached out to the VMM team. I will respond as soon as I hear back. Can you also reach out to the email alias provided at the bottom of this link: SDN Troubleshooting: UDP Communication failures and changing the Network Controller Certificate - Microsoft Community Hub<https://techcommunity.microsoft.com/t5/networking-blog/sdn-troubleshooting-udp-communication-failures-and-changing-the/ba-p/339694> Thanks Anirban From: willkruss ***@***.*** <mailto:***@***.***> > Sent: Wednesday, June 7, 2023 8:02 PM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, I know you are going to be sick of hearing from me, but it seems it's simply not possible to have a different physical management and VM tenant network with the network controller. Since the switch cannot manage two networks and allow you to specify different port uplinks per for each NIC, I provisioned the network controllers using a standard switch for the management network, and have the logical switch on the VM Network. This looks fine on paper, the network controllers create without issue and the netcontroller is accessible. However, you cannot provision it as it errors saying: Network controller VMs part of service instance NetController should all be connected to instances of the same logical switch. Recommended Action Connect all VMs to management VM network through instances of a common logical switch and retry. I'm at a complete loss how to get this to work. Can I add a second NIC to the network controllers and assign that to the VM Network on the Logical Switch? Thanks, Will From: William Kruss ***@***.*** <mailto:***@***.***> > Sent: Thursday, June 8, 2023 10:56 AM To: 'microsoft/SDN' ***@***.*** <mailto:***@***.***> >; 'microsoft/SDN' ***@***.*** <mailto:***@***.***> > Cc: 'Author' ***@***.*** <mailto:***@***.***> > Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Further to my last email, if I try to get both networks setup on the same logical switch by using Embedded teaming I can't then assign a different uplink port profile to each physical NIC. So I'm at a complete loss at the moment. We can't change the physical connections of the servers, we need to run a network controller that will have IPs assigned on the management network, but control the VM network (two physically different networks both connected). Any suggestions? This seems like a huge problem in the flexibility of the system as far as I can see, and as we have 1000 VMs in production we can't simply change physical networking around. Thanks, Will From: William Kruss ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > Sent: Wednesday, June 7, 2023 4:00 PM To: 'microsoft/SDN' ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > >; 'microsoft/SDN' ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > Cc: 'Author' ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Okay, that helps, the problem I've got is because we setup the physical infrastructure in 2012 the recommendation was at the time to have separate networks for VM network and host management network. Our networks are physically completely different (traffic literally has to pass to our edge firewall and back when a VM is talking to a host server for example). This works brilliantly, but also means we haven't had to setup logical switches - just the logical network for VM communication, and host management network the hosts are given static IPs. We still have redundant domain controllers and such running on the VM network, but their communication with our physical DCs on the management networks goes through our edge firewall and back. This means we cannot use NIC teaming, as both networks are not connected. If we cannot use NIC teaming, and we setup the NCs on our host management network (easy enough). The problem is I create a switch on the management network which is used when provisioning the network controllers. But then I cannot create a virtual switch for the VM network as I get the error below: Error (50208) Cannot create virtual switch on the host 'VM1.TESTLAB.local' because there already exists a virtual switch on the host that is managed by Microsoft Network Controller. Recommended Action Ensure that the host does not have any other virtual switch managed by Microsoft Network Controller. So how do I get it so that the NCs are provisioned in my management network, but so that the VM network is controlled by the network controller so I can use network virtualization? I cannot use network virtualization in a network that isn't controlled by the network controller as then I cannot upgrade to 2019 (we are running 2016 at this time). Does this explain what the issues I'm facing are? I've tried to provision the network controllers to the VM network instead of management network but then of course they aren't provisioned with correct networking. I'm really at a loss how to proceed. Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > Sent: Wednesday, June 7, 2023 5:36 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > Cc: willkruss ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > >; Author ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will The Network Controller VMs need to have access to the Management network since they communicate with hosts to push policy and learn about VMs on the host. Network Controller does not need access to the VM NIC network. This is how it works: 1. NC VMs get IPs from the management network. If this is different from the host management network, ensure that there is routing between the two networks. 2. Hosts are assigned IP Addresses from the HNVPA network by the Network Controller. If IP is not getting assigned, there is some communication issue between the hosts and the Network Controller. 3. The HNVPA network is the underlying physical network for forwarding the virtual network traffic. So, your tenant VMs would get IPs from a virtual network (Which can be a completely fictitious network with no presence in the underlying physical network), your hosts will get IPs from management and HNV PA networks (latter being assigned by the Network Controller), and your NC VMs will get IP from the management network. There are a few sample topologies for NC here: Plan to deploy Network Controller - Azure Stack HCI | Microsoft Learn<https://learn.microsoft.com/en-us/azure-stack/hci/concepts/network-controller#network-controller-requirements> Thanks Anirban From: willkruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Sent: Monday, June 5, 2023 8:26 PM To: microsoft/SDN ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Can you please answer me this question: We have 3 NICs on our host servers: 1. SAN NIC - Hosts use this to connect to the cluster SANs 2. Management NIC - We have no logical network or switch created in SCVMM for this. All IPs are statically assigned to the hosts. 3. VM NIC - This is created using a Logical Network with no management access and is for VM public NICs, also assigning IPs from Pools, and lastly for isolated HNV networks between VMs. I have been trying to install the network controllers on the VM NIC network where the logical network is setup. If I create a new logical network for management and install the network controllers on the Management network it tells me the network controllers are not assigned to the physical network adapter that the VMs are using so I cannot control any VM networking. If I install the network controllers on the VM Logical Network (Physical VM NIC) there seems to be issues with networking and speaking to the hosts properly. Where am I supposed to install the network controllers, and how do I get them to be able to manage networks on the VM Network so I can use HNV there? Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Sent: Saturday, June 3, 2023 9:12 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Cc: willkruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> >; Author ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will Is this issue resolved. If not, can you send email to ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Thanks Anirban - Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NGRPU6DSFEN2ZC7Z5LXJJXMFANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NHHYNPLMC4JDG2CVPLXJJXMFA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS527IUU.gif> Message ID: ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63OAPXAARWNHUKW27MLXJ2PMRANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > - Reply to this email directly, <#572 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AA7W7NGTAG5A3PT4Z3XONC3XJ6BCJANCNFSM6AAAAAAX23GHYQ> unsubscribe. You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NBQEF7DO4KJ7FE5JMTXJ6BCJA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6ELGD6.gif> Message ID: < ***@***.*** <mailto:***@***.***> > ***@***.*** <mailto:***@***.***> > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63OGBVMDETXQHRMNEUTXKE6B7ANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> > — Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NHGRVPOMBT7AVYQJMTXKILRJANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NFJQBCOPO76GTUNMITXKILRJA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6LTUDW.gif> Message ID: ***@***.*** ***@***.***> >

Strange. It is working for me. Can you try this: Azure Stack HCI with SDN - Microsoft Q&A<https://learn.microsoft.com/en-us/answers/questions/544626/azure-stack-hci-with-sdn?orderby=newest>. There is an alias at the bottom of my response. From: willkruss ***@***.***> Sent: Friday, June 9, 2023 2:01 AM To: microsoft/SDN ***@***.***> Cc: Anirban Paul ***@***.***>; Comment ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, The page you linked to is under maintenance, looks like the whole techcommunity website is unavailable? Thanks, Will From: Anirban Paul ***@***.***> Sent: Friday, June 9, 2023 4:36 AM To: microsoft/SDN ***@***.***> Cc: willkruss ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will I can understand the issue. I have reached out to the VMM team. I will respond as soon as I hear back. Can you also reach out to the email alias provided at the bottom of this link: SDN Troubleshooting: UDP Communication failures and changing the Network Controller Certificate - Microsoft Community Hub<https://techcommunity.microsoft.com/t5/networking-blog/sdn-troubleshooting-udp-communication-failures-and-changing-the/ba-p/339694> Thanks Anirban From: willkruss ***@***.*** <mailto:***@***.***> > Sent: Wednesday, June 7, 2023 8:02 PM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, I know you are going to be sick of hearing from me, but it seems it's simply not possible to have a different physical management and VM tenant network with the network controller. Since the switch cannot manage two networks and allow you to specify different port uplinks per for each NIC, I provisioned the network controllers using a standard switch for the management network, and have the logical switch on the VM Network. This looks fine on paper, the network controllers create without issue and the netcontroller is accessible. However, you cannot provision it as it errors saying: Network controller VMs part of service instance NetController should all be connected to instances of the same logical switch. Recommended Action Connect all VMs to management VM network through instances of a common logical switch and retry. I'm at a complete loss how to get this to work. Can I add a second NIC to the network controllers and assign that to the VM Network on the Logical Switch? Thanks, Will From: William Kruss ***@***.*** <mailto:***@***.***> > Sent: Thursday, June 8, 2023 10:56 AM To: 'microsoft/SDN' ***@***.*** <mailto:***@***.***> >; 'microsoft/SDN' ***@***.*** <mailto:***@***.***> > Cc: 'Author' ***@***.*** <mailto:***@***.***> > Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Further to my last email, if I try to get both networks setup on the same logical switch by using Embedded teaming I can't then assign a different uplink port profile to each physical NIC. So I'm at a complete loss at the moment. We can't change the physical connections of the servers, we need to run a network controller that will have IPs assigned on the management network, but control the VM network (two physically different networks both connected). Any suggestions? This seems like a huge problem in the flexibility of the system as far as I can see, and as we have 1000 VMs in production we can't simply change physical networking around. Thanks, Will From: William Kruss ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > Sent: Wednesday, June 7, 2023 4:00 PM To: 'microsoft/SDN' ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > >; 'microsoft/SDN' ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > Cc: 'Author' ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Okay, that helps, the problem I've got is because we setup the physical infrastructure in 2012 the recommendation was at the time to have separate networks for VM network and host management network. Our networks are physically completely different (traffic literally has to pass to our edge firewall and back when a VM is talking to a host server for example). This works brilliantly, but also means we haven't had to setup logical switches - just the logical network for VM communication, and host management network the hosts are given static IPs. We still have redundant domain controllers and such running on the VM network, but their communication with our physical DCs on the management networks goes through our edge firewall and back. This means we cannot use NIC teaming, as both networks are not connected. If we cannot use NIC teaming, and we setup the NCs on our host management network (easy enough). The problem is I create a switch on the management network which is used when provisioning the network controllers. But then I cannot create a virtual switch for the VM network as I get the error below: Error (50208) Cannot create virtual switch on the host 'VM1.TESTLAB.local' because there already exists a virtual switch on the host that is managed by Microsoft Network Controller. Recommended Action Ensure that the host does not have any other virtual switch managed by Microsoft Network Controller. So how do I get it so that the NCs are provisioned in my management network, but so that the VM network is controlled by the network controller so I can use network virtualization? I cannot use network virtualization in a network that isn't controlled by the network controller as then I cannot upgrade to 2019 (we are running 2016 at this time). Does this explain what the issues I'm facing are? I've tried to provision the network controllers to the VM network instead of management network but then of course they aren't provisioned with correct networking. I'm really at a loss how to proceed. Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > Sent: Wednesday, June 7, 2023 5:36 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > Cc: willkruss ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > >; Author ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will The Network Controller VMs need to have access to the Management network since they communicate with hosts to push policy and learn about VMs on the host. Network Controller does not need access to the VM NIC network. This is how it works: 1. NC VMs get IPs from the management network. If this is different from the host management network, ensure that there is routing between the two networks. 2. Hosts are assigned IP Addresses from the HNVPA network by the Network Controller. If IP is not getting assigned, there is some communication issue between the hosts and the Network Controller. 3. The HNVPA network is the underlying physical network for forwarding the virtual network traffic. So, your tenant VMs would get IPs from a virtual network (Which can be a completely fictitious network with no presence in the underlying physical network), your hosts will get IPs from management and HNV PA networks (latter being assigned by the Network Controller), and your NC VMs will get IP from the management network. There are a few sample topologies for NC here: Plan to deploy Network Controller - Azure Stack HCI | Microsoft Learn<https://learn.microsoft.com/en-us/azure-stack/hci/concepts/network-controller#network-controller-requirements> Thanks Anirban From: willkruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Sent: Monday, June 5, 2023 8:26 PM To: microsoft/SDN ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Can you please answer me this question: We have 3 NICs on our host servers: 1. SAN NIC - Hosts use this to connect to the cluster SANs 2. Management NIC - We have no logical network or switch created in SCVMM for this. All IPs are statically assigned to the hosts. 3. VM NIC - This is created using a Logical Network with no management access and is for VM public NICs, also assigning IPs from Pools, and lastly for isolated HNV networks between VMs. I have been trying to install the network controllers on the VM NIC network where the logical network is setup. If I create a new logical network for management and install the network controllers on the Management network it tells me the network controllers are not assigned to the physical network adapter that the VMs are using so I cannot control any VM networking. If I install the network controllers on the VM Logical Network (Physical VM NIC) there seems to be issues with networking and speaking to the hosts properly. Where am I supposed to install the network controllers, and how do I get them to be able to manage networks on the VM Network so I can use HNV there? Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Sent: Saturday, June 3, 2023 9:12 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Cc: willkruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> >; Author ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will Is this issue resolved. If not, can you send email to ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Thanks Anirban - Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NGRPU6DSFEN2ZC7Z5LXJJXMFANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NHHYNPLMC4JDG2CVPLXJJXMFA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS527IUU.gif> Message ID: ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63OAPXAARWNHUKW27MLXJ2PMRANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > - Reply to this email directly, <#572 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AA7W7NGTAG5A3PT4Z3XONC3XJ6BCJANCNFSM6AAAAAAX23GHYQ> unsubscribe. You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NBQEF7DO4KJ7FE5JMTXJ6BCJA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6ELGD6.gif> Message ID: < ***@***.*** <mailto:***@***.***> > ***@***.*** <mailto:***@***.***> > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63OGBVMDETXQHRMNEUTXKE6B7ANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> > - Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NHGRVPOMBT7AVYQJMTXKILRJANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NFJQBCOPO76GTUNMITXKILRJA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6LTUDW.gif> Message ID: ***@***.*** ***@***.***> > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63KHV2REUARLQFLO5QDXKLQ3NANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.***>

Thanks Anirban, I’ll reach out to that email also. Cheers, Will From: Anirban Paul ***@***.***> Sent: Saturday, June 10, 2023 2:05 AM To: microsoft/SDN ***@***.***> Cc: willkruss ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Strange. It is working for me. Can you try this: Azure Stack HCI with SDN - Microsoft Q&A<https://learn.microsoft.com/en-us/answers/questions/544626/azure-stack-hci-with-sdn?orderby=newest>. There is an alias at the bottom of my response. From: willkruss ***@***.*** <mailto:***@***.***> > Sent: Friday, June 9, 2023 2:01 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, The page you linked to is under maintenance, looks like the whole techcommunity website is unavailable? Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***> > Sent: Friday, June 9, 2023 4:36 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: willkruss ***@***.*** <mailto:***@***.***> >; Author ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will I can understand the issue. I have reached out to the VMM team. I will respond as soon as I hear back. Can you also reach out to the email alias provided at the bottom of this link: SDN Troubleshooting: UDP Communication failures and changing the Network Controller Certificate - Microsoft Community Hub<https://techcommunity.microsoft.com/t5/networking-blog/sdn-troubleshooting-udp-communication-failures-and-changing-the/ba-p/339694> Thanks Anirban From: willkruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Sent: Wednesday, June 7, 2023 8:02 PM To: microsoft/SDN ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, I know you are going to be sick of hearing from me, but it seems it's simply not possible to have a different physical management and VM tenant network with the network controller. Since the switch cannot manage two networks and allow you to specify different port uplinks per for each NIC, I provisioned the network controllers using a standard switch for the management network, and have the logical switch on the VM Network. This looks fine on paper, the network controllers create without issue and the netcontroller is accessible. However, you cannot provision it as it errors saying: Network controller VMs part of service instance NetController should all be connected to instances of the same logical switch. Recommended Action Connect all VMs to management VM network through instances of a common logical switch and retry. I'm at a complete loss how to get this to work. Can I add a second NIC to the network controllers and assign that to the VM Network on the Logical Switch? Thanks, Will From: William Kruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Sent: Thursday, June 8, 2023 10:56 AM To: 'microsoft/SDN' ***@***.*** <mailto:***@***.***> <mailto:***@***.***> >; 'microsoft/SDN' ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Cc: 'Author' ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Further to my last email, if I try to get both networks setup on the same logical switch by using Embedded teaming I can't then assign a different uplink port profile to each physical NIC. So I'm at a complete loss at the moment. We can't change the physical connections of the servers, we need to run a network controller that will have IPs assigned on the management network, but control the VM network (two physically different networks both connected). Any suggestions? This seems like a huge problem in the flexibility of the system as far as I can see, and as we have 1000 VMs in production we can't simply change physical networking around. Thanks, Will From: William Kruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > > Sent: Wednesday, June 7, 2023 4:00 PM To: 'microsoft/SDN' ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > >; 'microsoft/SDN' ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > > Cc: 'Author' ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > > Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Okay, that helps, the problem I've got is because we setup the physical infrastructure in 2012 the recommendation was at the time to have separate networks for VM network and host management network. Our networks are physically completely different (traffic literally has to pass to our edge firewall and back when a VM is talking to a host server for example). This works brilliantly, but also means we haven't had to setup logical switches - just the logical network for VM communication, and host management network the hosts are given static IPs. We still have redundant domain controllers and such running on the VM network, but their communication with our physical DCs on the management networks goes through our edge firewall and back. This means we cannot use NIC teaming, as both networks are not connected. If we cannot use NIC teaming, and we setup the NCs on our host management network (easy enough). The problem is I create a switch on the management network which is used when provisioning the network controllers. But then I cannot create a virtual switch for the VM network as I get the error below: Error (50208) Cannot create virtual switch on the host 'VM1.TESTLAB.local' because there already exists a virtual switch on the host that is managed by Microsoft Network Controller. Recommended Action Ensure that the host does not have any other virtual switch managed by Microsoft Network Controller. So how do I get it so that the NCs are provisioned in my management network, but so that the VM network is controlled by the network controller so I can use network virtualization? I cannot use network virtualization in a network that isn't controlled by the network controller as then I cannot upgrade to 2019 (we are running 2016 at this time). Does this explain what the issues I'm facing are? I've tried to provision the network controllers to the VM network instead of management network but then of course they aren't provisioned with correct networking. I'm really at a loss how to proceed. Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > > Sent: Wednesday, June 7, 2023 5:36 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > > Cc: willkruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > >; Author ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will The Network Controller VMs need to have access to the Management network since they communicate with hosts to push policy and learn about VMs on the host. Network Controller does not need access to the VM NIC network. This is how it works: 1. NC VMs get IPs from the management network. If this is different from the host management network, ensure that there is routing between the two networks. 2. Hosts are assigned IP Addresses from the HNVPA network by the Network Controller. If IP is not getting assigned, there is some communication issue between the hosts and the Network Controller. 3. The HNVPA network is the underlying physical network for forwarding the virtual network traffic. So, your tenant VMs would get IPs from a virtual network (Which can be a completely fictitious network with no presence in the underlying physical network), your hosts will get IPs from management and HNV PA networks (latter being assigned by the Network Controller), and your NC VMs will get IP from the management network. There are a few sample topologies for NC here: Plan to deploy Network Controller - Azure Stack HCI | Microsoft Learn<https://learn.microsoft.com/en-us/azure-stack/hci/concepts/network-controller#network-controller-requirements> Thanks Anirban From: willkruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > Sent: Monday, June 5, 2023 8:26 PM To: microsoft/SDN ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Can you please answer me this question: We have 3 NICs on our host servers: 1. SAN NIC - Hosts use this to connect to the cluster SANs 2. Management NIC - We have no logical network or switch created in SCVMM for this. All IPs are statically assigned to the hosts. 3. VM NIC - This is created using a Logical Network with no management access and is for VM public NICs, also assigning IPs from Pools, and lastly for isolated HNV networks between VMs. I have been trying to install the network controllers on the VM NIC network where the logical network is setup. If I create a new logical network for management and install the network controllers on the Management network it tells me the network controllers are not assigned to the physical network adapter that the VMs are using so I cannot control any VM networking. If I install the network controllers on the VM Logical Network (Physical VM NIC) there seems to be issues with networking and speaking to the hosts properly. Where am I supposed to install the network controllers, and how do I get them to be able to manage networks on the VM Network so I can use HNV there? Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > Sent: Saturday, June 3, 2023 9:12 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > Cc: willkruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> >; Author ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will Is this issue resolved. If not, can you send email to ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > Thanks Anirban - Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NGRPU6DSFEN2ZC7Z5LXJJXMFANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NHHYNPLMC4JDG2CVPLXJJXMFA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS527IUU.gif> Message ID: ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63OAPXAARWNHUKW27MLXJ2PMRANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > - Reply to this email directly, <#572 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AA7W7NGTAG5A3PT4Z3XONC3XJ6BCJANCNFSM6AAAAAAX23GHYQ> unsubscribe. You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NBQEF7DO4KJ7FE5JMTXJ6BCJA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6ELGD6.gif> Message ID: < ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63OGBVMDETXQHRMNEUTXKE6B7ANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > - Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NHGRVPOMBT7AVYQJMTXKILRJANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NFJQBCOPO76GTUNMITXKILRJA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6LTUDW.gif> Message ID: ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63KHV2REUARLQFLO5QDXKLQ3NANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> > — Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NDTM7YLLS7WR6RALVTXKNCS7ANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NEJ3GJJSHQNSN7UMKTXKNCS7A5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6OZWTQ.gif> Message ID: ***@***.*** ***@***.***> >

Hi Anirban, I’ve send an email to that sdn feedback address as requested. I’ve also retested just upgrading to 2019 with no luck as I can’t use network virtualization without a network controller: Error (50362) Logical networks that use network virtualization and are not managed by Network Controller are not supported on the selected host ('VM1.TESTLAB.local') OS version. Recommended Action Logical Networks that use Network Virtualization without Network Controller are not supported on Windows Server 2019 and above. Please manage the logical network using Network Controller for Network Virtualization. So I’m really stuck now. I need a solution as per my previous emails where I can use a network controller, and assign a different physical network adapter to different port profiles. I’m not sure if there is a powershell solution, and honestly it seems ridiculous that the network manager can’t manage a physical network connected to the cluster without it being physically assigned to the network controller VMs. The network controller VMs surely only need to be able to talk to the hosts and SCVMM, so it really doesn’t make sense to me. This is all very very simple with VMWare, but given we have 1000 VMs in Hyper-V Clustering already we would ideally stick with it if we can find a suitable upgrade path. Please let me know a contact at the VMM team, or at the Hyper-V networking team as support for 2016 is coming to an end and we need to figure out this upgrade path in the near future. Thanks, Will Kruss From: Will Kruss ***@***.***> Sent: Saturday, June 10, 2023 9:26 AM To: 'microsoft/SDN' ***@***.***>; 'microsoft/SDN' ***@***.***> Cc: 'Author' ***@***.***> Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Thanks Anirban, I’ll reach out to that email also. Cheers, Will From: Anirban Paul ***@***.*** ***@***.***> > Sent: Saturday, June 10, 2023 2:05 AM To: microsoft/SDN ***@***.*** ***@***.***> > Cc: willkruss ***@***.*** ***@***.***> >; Author ***@***.*** ***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Strange. It is working for me. Can you try this: Azure Stack HCI with SDN - Microsoft Q&A<https://learn.microsoft.com/en-us/answers/questions/544626/azure-stack-hci-with-sdn?orderby=newest>. There is an alias at the bottom of my response. From: willkruss ***@***.*** <mailto:***@***.***> > Sent: Friday, June 9, 2023 2:01 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, The page you linked to is under maintenance, looks like the whole techcommunity website is unavailable? Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***> > Sent: Friday, June 9, 2023 4:36 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> > Cc: willkruss ***@***.*** <mailto:***@***.***> >; Author ***@***.*** <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will I can understand the issue. I have reached out to the VMM team. I will respond as soon as I hear back. Can you also reach out to the email alias provided at the bottom of this link: SDN Troubleshooting: UDP Communication failures and changing the Network Controller Certificate - Microsoft Community Hub<https://techcommunity.microsoft.com/t5/networking-blog/sdn-troubleshooting-udp-communication-failures-and-changing-the/ba-p/339694> Thanks Anirban From: willkruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Sent: Wednesday, June 7, 2023 8:02 PM To: microsoft/SDN ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, I know you are going to be sick of hearing from me, but it seems it's simply not possible to have a different physical management and VM tenant network with the network controller. Since the switch cannot manage two networks and allow you to specify different port uplinks per for each NIC, I provisioned the network controllers using a standard switch for the management network, and have the logical switch on the VM Network. This looks fine on paper, the network controllers create without issue and the netcontroller is accessible. However, you cannot provision it as it errors saying: Network controller VMs part of service instance NetController should all be connected to instances of the same logical switch. Recommended Action Connect all VMs to management VM network through instances of a common logical switch and retry. I'm at a complete loss how to get this to work. Can I add a second NIC to the network controllers and assign that to the VM Network on the Logical Switch? Thanks, Will From: William Kruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Sent: Thursday, June 8, 2023 10:56 AM To: 'microsoft/SDN' ***@***.*** <mailto:***@***.***> <mailto:***@***.***> >; 'microsoft/SDN' ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Cc: 'Author' ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Further to my last email, if I try to get both networks setup on the same logical switch by using Embedded teaming I can't then assign a different uplink port profile to each physical NIC. So I'm at a complete loss at the moment. We can't change the physical connections of the servers, we need to run a network controller that will have IPs assigned on the management network, but control the VM network (two physically different networks both connected). Any suggestions? This seems like a huge problem in the flexibility of the system as far as I can see, and as we have 1000 VMs in production we can't simply change physical networking around. Thanks, Will From: William Kruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > > Sent: Wednesday, June 7, 2023 4:00 PM To: 'microsoft/SDN' ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > >; 'microsoft/SDN' ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > > Cc: 'Author' ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > > Subject: RE: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Okay, that helps, the problem I've got is because we setup the physical infrastructure in 2012 the recommendation was at the time to have separate networks for VM network and host management network. Our networks are physically completely different (traffic literally has to pass to our edge firewall and back when a VM is talking to a host server for example). This works brilliantly, but also means we haven't had to setup logical switches - just the logical network for VM communication, and host management network the hosts are given static IPs. We still have redundant domain controllers and such running on the VM network, but their communication with our physical DCs on the management networks goes through our edge firewall and back. This means we cannot use NIC teaming, as both networks are not connected. If we cannot use NIC teaming, and we setup the NCs on our host management network (easy enough). The problem is I create a switch on the management network which is used when provisioning the network controllers. But then I cannot create a virtual switch for the VM network as I get the error below: Error (50208) Cannot create virtual switch on the host 'VM1.TESTLAB.local' because there already exists a virtual switch on the host that is managed by Microsoft Network Controller. Recommended Action Ensure that the host does not have any other virtual switch managed by Microsoft Network Controller. So how do I get it so that the NCs are provisioned in my management network, but so that the VM network is controlled by the network controller so I can use network virtualization? I cannot use network virtualization in a network that isn't controlled by the network controller as then I cannot upgrade to 2019 (we are running 2016 at this time). Does this explain what the issues I'm facing are? I've tried to provision the network controllers to the VM network instead of management network but then of course they aren't provisioned with correct networking. I'm really at a loss how to proceed. Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > > Sent: Wednesday, June 7, 2023 5:36 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > > Cc: willkruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > >; Author ***@***.*** <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will The Network Controller VMs need to have access to the Management network since they communicate with hosts to push policy and learn about VMs on the host. Network Controller does not need access to the VM NIC network. This is how it works: 1. NC VMs get IPs from the management network. If this is different from the host management network, ensure that there is routing between the two networks. 2. Hosts are assigned IP Addresses from the HNVPA network by the Network Controller. If IP is not getting assigned, there is some communication issue between the hosts and the Network Controller. 3. The HNVPA network is the underlying physical network for forwarding the virtual network traffic. So, your tenant VMs would get IPs from a virtual network (Which can be a completely fictitious network with no presence in the underlying physical network), your hosts will get IPs from management and HNV PA networks (latter being assigned by the Network Controller), and your NC VMs will get IP from the management network. There are a few sample topologies for NC here: Plan to deploy Network Controller - Azure Stack HCI | Microsoft Learn<https://learn.microsoft.com/en-us/azure-stack/hci/concepts/network-controller#network-controller-requirements> Thanks Anirban From: willkruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > Sent: Monday, June 5, 2023 8:26 PM To: microsoft/SDN ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > Cc: Anirban Paul ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> >; Comment ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Anirban, Can you please answer me this question: We have 3 NICs on our host servers: 1. SAN NIC - Hosts use this to connect to the cluster SANs 2. Management NIC - We have no logical network or switch created in SCVMM for this. All IPs are statically assigned to the hosts. 3. VM NIC - This is created using a Logical Network with no management access and is for VM public NICs, also assigning IPs from Pools, and lastly for isolated HNV networks between VMs. I have been trying to install the network controllers on the VM NIC network where the logical network is setup. If I create a new logical network for management and install the network controllers on the Management network it tells me the network controllers are not assigned to the physical network adapter that the VMs are using so I cannot control any VM networking. If I install the network controllers on the VM Logical Network (Physical VM NIC) there seems to be issues with networking and speaking to the hosts properly. Where am I supposed to install the network controllers, and how do I get them to be able to manage networks on the VM Network so I can use HNV there? Thanks, Will From: Anirban Paul ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > Sent: Saturday, June 3, 2023 9:12 AM To: microsoft/SDN ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > Cc: willkruss ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> >; Author ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > Subject: Re: [microsoft/SDN] Fails invoking script command Pre-Install_6 (Issue #572) Hi Will Is this issue resolved. If not, can you send email to ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > Thanks Anirban - Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NGRPU6DSFEN2ZC7Z5LXJJXMFANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NHHYNPLMC4JDG2CVPLXJJXMFA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS527IUU.gif> Message ID: ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63OAPXAARWNHUKW27MLXJ2PMRANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> <mailto:***@***.***> <mailto:***@***.***> > - Reply to this email directly, <#572 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AA7W7NGTAG5A3PT4Z3XONC3XJ6BCJANCNFSM6AAAAAAX23GHYQ> unsubscribe. You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NBQEF7DO4KJ7FE5JMTXJ6BCJA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6ELGD6.gif> Message ID: < ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63OGBVMDETXQHRMNEUTXKE6B7ANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> <mailto:***@***.***> > - Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NHGRVPOMBT7AVYQJMTXKILRJANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NFJQBCOPO76GTUNMITXKILRJA5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6LTUDW.gif> Message ID: ***@***.*** <mailto:***@***.***> ***@***.*** <mailto:***@***.***> > > - Reply to this email directly, view it on GitHub<#572 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBB63KHV2REUARLQFLO5QDXKLQ3NANCNFSM6AAAAAAX23GHYQ>. You are receiving this because you commented.Message ID: ***@***.*** <mailto:***@***.***> > — Reply to this email directly, view it on GitHub <#572 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7W7NDTM7YLLS7WR6RALVTXKNCS7ANCNFSM6AAAAAAX23GHYQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AA7W7NEJ3GJJSHQNSN7UMKTXKNCS7A5CNFSM6AAAAAAX23GHYSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6OZWTQ.gif> Message ID: ***@***.*** ***@***.***> >