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
487 stars 541 forks source link

Gateway clean up failed #445

Open BuggeXX opened 4 years ago

BuggeXX commented 4 years ago

I have deployed SDN with the powershell express module. anything seems fine, except that the 2 gateway vms keeps rebooting and Get-NetworkControllerGateway showing for both "Source": "ResourceGlobal", "Message": "Gateway clean up failed", "Code": "HostUnreachable" Now i have tried to connect to the GW from any NC via PSRemoting just fine. Connection from GW to HVs works also visa versa.

Get-NetworkControllerVirtualServer shows that both gws are configured to use NCHostUser while the two muxes uses NCHostCert

can somebody please point our what else i could check?

rhochmayr commented 4 years ago

Hi there,

same issue here. Just deployed another PoC on Windows Server 2019 & VMM 2019 UR1 by using the VMM Service Templates.

Everything is working fine (NC & SLB MUXes) except the RAS gateways. Also seeing following message on all 3 GWs:

"Message": "Gateway clean up failed", "Code": "HostUnreachable"

Also spotted that the gateways have been configured to use "credentialType": "usernamePassword" while SLBs use "credentialType": "X509Certificate".

Any ideas?

Thanks, Rob

rhochmayr commented 4 years ago

Hi again,

Just FYI, got this working by adding the NetworkController Managment Account to the local Administrator Groups on the RAS GWs.

Eventlogs in the "Network-Controller Framework", "NetworkController-GatewayManager" on the NCs and Security Logs on the RAS GWs gave the hint.

Don't know why Certificate based authentication is not used between NCs and GWs but once someone tells us how to change this you can get it working with above "workaround".

Thanks, Rob

BuggeXX commented 4 years ago

To bad i wiped allready anything off and started to validate vmm :)

But i dont think that the management account off the NC was in my case the problem, as i used the default domainadmin for it. as the gw join the domain via script the domainadmin should be added automatically to the local administrator group of the vm.

Regards