search

microsoft / SDN

This repo includes PowerShell scripts and VMM service templates for setting up the Microsoft Software Defined Networking (SDN) Stack using Windows Server 2016
Other
485 stars 541 forks source link

SDN-Express don't like Windows Server 2019 Datacenter Core? #355

Open ghost opened 5 years ago

ghost commented 5 years ago

Hi. I'm trying to set up a SDN via SDN-Express Script on my Hyper-V and the stage 1 went fine. But if it's trying to connect to the Network Controller in stage 2 the first time it won't connect. Instead it give's out an error. Here's the log: VERBOSE: [20190425-11:05:31] STAGE 2: Network Controller Configuration VERBOSE: [20190425-11:05:31] Waiting for SDN-NC01 to become active. VERBOSE: [20190425-11:05:31] Attempting to contact SDN-NC01. VERBOSE: [20190425-11:05:31] SDN-NC01 is not active, sleeping for 10 seconds.

My setup: Microsoft Windows Server 2019 Datacenter with Hyper-V and HCI on HP Server with a physical NIC and IP in 10.X network for management. And one virtual NIC with VLAN 192 (Management SDN) and 192.168.82.201 IP. The SDN Express Scripts build one Network Controller based on windows server 2019 datacenter core with an 192.168.82.10 IP in VLAN 192 (Management SDN). I got a sophos vm with two vNICs. One vNIC have the VLANs configured so the sophos works as router/gateway/firewall in the VLANs (IP is x.x.x.1 in each vlan). One vNIC is configured for WAN communication.

I can ping the Network Controller vm from my hyper-v host via it's vNIC and vice versa. Both can ping the sophos and vice versa. I can log in to the NC-VM and i have already turned down the firewall (on hyper-v and on NC-VM) and actived the winrm and psremote function.

Strange.

Kind Regards, Lars

ghost commented 5 years ago

I think i found some bugs. You forgot to add the VMs in the TrustedHosts list on the host from witch the sdn-express scripts run. And you think the administrator from the hyper-v is in the same domain as the vm's. But if they're freshly installed they won't be in any domain so you need to add in the "waitforcomputertobeready" routine at "new-pssession" the "-credential" stuff. Could you check it please?