search

bfrankMS / CreateHypervVms

9 stars 8 forks source link

Minor issue with NAT setup on DC #7

Open heinejeppesen opened 2 months ago

heinejeppesen commented 2 months ago

Hi,

Thanks for creating this framework, allowing me to easily try out Azure Stack HCI ;-)

I couldn't get the network traffic flowing from the two HCI hosts, so I did a little digging around to make it work.

In "step_PrepareAdminbox.ps1" in line 46 / 47 is says: add interface name="EXTERNAL" mode=FULL add interface name="INTERNAL" mode=PRIVATE

But the network interfaces are called "EXT" and "aMGMT" in the setup generated with the scripts.

So replacing with: add interface name="EXT" mode=FULL add interface name="aMGMT" mode=PRIVATE

or just running the commands like this after starting NetSH.exe as admin on the DC. pushd routing ip nat add interface name="EXT" mode=FULL add interface name="aMGMT" mode=PRIVATE

NAT immediately started working from the HCI nodes, after doing so. Hopefully this can be changed in the repo or help others trying the framework out.

heinejeppesen commented 2 months ago

Are you asking about what to put in ScriptArguments in line 12?

It's the subnet your Azure Stack infrastructure run on and IP addresses for DNS servers to resolve addresses externally. I just use Cloudflare's 1.1.1.1 or Google's 8.8.8.8 for external DNS when playing around with something. Which subnet to specify only you can know, since it's on your network.

And please don't hijack existing threads for unrelated questions.

bfrankMS commented 2 months ago

Hi,

Thanks for creating this framework, allowing me to easily try out Azure Stack HCI ;-)

I couldn't get the network traffic flowing from the two HCI hosts, so I did a little digging around to make it work.

In "step_PrepareAdminbox.ps1" in line 46 / 47 is says: add interface name="EXTERNAL" mode=FULL add interface name="INTERNAL" mode=PRIVATE

But the network interfaces are called "EXT" and "aMGMT" in the setup generated with the scripts.

So replacing with: add interface name="EXT" mode=FULL add interface name="aMGMT" mode=PRIVATE

or just running the commands like this after starting NetSH.exe as admin on the DC. pushd routing ip nat add interface name="EXT" mode=FULL add interface name="aMGMT" mode=PRIVATE

NAT immediately started working from the HCI nodes, after doing so. Hopefully this can be changed in the repo or help others trying the framework out.

Hi,

thanks for posting this however IMHO this should not be required as the strings "EXTERNAL" and "INTERNAL" should be replaced using parameters passed in - see lines 51,52: $netshFile = $netshFile -replace "EXTERNAL",$externalAdapterName $netshFile = $netshFile -replace "INTERNAL",$internalAdapterName

but you are right some folks reported issues with the RRAS setup - so I might justify investigating for a more robust setup.

thx, B

bfrankMS commented 2 months ago

Are you asking about what to put in ScriptArguments in line 12?

It's the subnet your Azure Stack infrastructure run on and IP addresses for DNS servers to resolve addresses externally. I just use Cloudflare's 1.1.1.1 or Google's 8.8.8.8 for external DNS when playing around with something. Which subnet to specify only you can know, since it's on your network.

And please don't hijack existing threads for unrelated questions.

Yeah - have a look a the picture in https://github.com/bfrankMS/CreateHypervVms/blob/master/Scenario-AzStackHCI/docs/overview.png it explains the values I used. -> you need to tweak the settings to your system to give the DC an IP for it's Ext(ernal) adapter that is valid on YOUR network and choose whatever upstream DNS server that is valid for you ;-)