Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steps unclear when creating the 2nd Node (Node02) #35

Closed
thetoppy opened this issue Aug 5, 2020 · 1 comment
Closed

Steps unclear when creating the 2nd Node (Node02) #35

thetoppy opened this issue Aug 5, 2020 · 1 comment

Comments

@thetoppy
Copy link

thetoppy commented Aug 5, 2020

Hi Team,

When creating the 1st Node (Node 01) the instruct mentioned to created 4 Disk of 100 GB there (Data01,Data02,Data03,Data04)

  1. It doesn't mention why we we need 4 disks here
  2. When create the 2nd Node - do we need to repeat 4 Disks for Node02 as well? Data01.vhdx, Data02.vhdx and so on.

It is unclear in this steps.

The powershell - Copy and Paste doesnt seem to work.

Error:

Invoke-Command : Cannot validate argument on parameter 'VMName'. The argument is null or empty. Provide an argument
that is not null or empty, and then try the command again.
At line:1 char:24

  • Invoke-Command -VMName "$nodeName" -Credential $domainCreds -ScriptBl ...
  •                    ~~~~~~~~~~~
    
    • CategoryInfo : InvalidData: (:) [Invoke-Command], ParameterBindingValidationException
    • FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.InvokeCommandCommand
@mattmcspirit
Copy link
Contributor

Hi - Yep, each of your nodes should have the 4 data disks.

When you get to the "repeat creation process", bounce back up to the top, specifically to the https://github.com/Azure/AzureStackHCI-EvalGuide/blob/main/nested/steps/3b_AzSHCINodesPS.md#create-the-azshcinode01-vm-using-powershell stage, and run all the scripts again. The only thing you need to adjust is the $nodeName = "AZSHCINODE01", which you'll find in a few places. Simply change this to 02 instead of 01, and all should work fine. I chose to split up the scripts and explain a bit more about each one, so people would understand what's happening, however if you copy them all to a PowerShell ISE, you may find that easier.

If you make a mistake and want to recreate the VM, simply delete it from Hyper-V Manager, then navigate to C:\VMs and delete the folder that contains the VM you wish to delete.

Hope that helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants