Well, after building my first Nano Server I blogged about in this I got some inspiration to play around with it a bit more.
For this post, my goal was to make a Scale Out File Server cluster with two Nano Server nodes.
So my thought is to provision an iSCSI target first. I went into a completely different direction by deploying a Ubuntu 15.10 server and configure it as an iSCSI target. I used the guidelines at https://www.howtoforge.com/using-iscsi-on-ubuntu-10.04-initiator-and-target and https://linhost.info/2012/05/configure-ubuntu-to-serve-as-an-iscsi-target/ to deliver a 150 GB iSCSI target volume.
After creating two Nano Server .vhd files I noticed that the network cards had no DNS servers specified, they were also not registered in DNS so I wasn’t able to access them remotely using Server Manager. After establishing a remote PowerShell session I used the netsh command to add a DNS server to the network cards using the following command: netsh interface ip set dnsservers name=”Ethernet” static 172.16.0.1 primary
Just to be sure I restarted the machines to make sure the DNS registration takes place. Restarting occurs quickly because the OS is very small and a limited amount of services will be started. The next step was adding the machines to the TrustedHost list for WinRM.
After that I was successfully able to add the machines to Server Manager on my DC. This verifies I can access the machines remotely next to PowerShell remoting.
So let’s try to build a cluster. I used Failover Cluster Manager to build a cluster. So let’s get started.
Let’s do a cluster validation first.
I added the servers, I used the default settings for validating the cluster.
Cluster validation is running, time for something to drink or a small toilet break 😉
It’s good to see that the cluster validation test passed. The warning on networking is purely for the fact that only network card is available which is not a recommended practice. But hey, we’re in a lab…
So let’s build that cluster.
Let’s give the cluster a name and an IP address and proceed…
So all is set to create that cluster. I unchecked the Add all eligible storage to the cluster checkbox since I haven’t connected anything yet. Time to build that cluster.
The cluster is ready.
After building the cluster I configured a network share as a disk witness.
So the next step is adding storage by using iSCSI. And here’s the part where my cluster becomes useless. The current Nano Server packages do not include anything iSCSI Initiator related, so I have no iSCSI Initiator service running nor can I create an iSCSI based disk since the PowerShell cmdlets for the iSCSI Initiator are simply not there. So that’s a dead end here.
Nevertheless, it was quite a satisfying exercise to build this cluster using Nano Server and should provide some inspiration to build a cluster for a different purpose, i.e. Hyper-V. But that’s for a different post…