locked
Installing the devkit - Error at step .20 RRS feed

  • Question

  • I've been trying to get the devkit working on a system with 3 ssd's and 3 spindle disks all SATA based on a supermicro motherboard for testing purposes. its a system with 192GB of ram, 16 cores ssd's are of a 250gb size and the spindles are 2tb. offcourse the OS disk is 500 GB. I have 1 nic active in DHCP the other is disabled. (disks are all correctly visible as SSD and HDD)

    The environment gets to step .20 and crashes with the following verbose information:

    VERBOSE: [Storage:Deployment] Validating number of disks meets minimum requirement : 3 - 7-8-2017
    08:05:46
    VERBOSE: [Storage:Deployment] Validation completed - Passed. Number of disks found is 6 - 7-8-2017
     08:05:49
    VERBOSE: [Storage:Deployment] Create the Storage Cluster - 7-8-2017 08:05:49
    VERBOSE: [Storage:Deployment] Get-NetworkMap: BEGIN on WIN-D2QSN942RT2 as
    AZURESTACK\AzureStackAdmin - 7-8-2017 08:05:50
    VERBOSE: [Storage:Deployment] Get Network Map for nodes WIN-D2QSN942RT2 - 7-8-2017 08:05:50
    VERBOSE: [Storage:Deployment] Test-NetworkMap: BEGIN on WIN-D2QSN942RT2 as
    AZURESTACK\AzureStackAdmin - 7-8-2017 08:05:50
    VERBOSE: [Storage:Deployment] Find out which NICs are able to connect on each node. - 7-8-2017
    08:05:50
    VERBOSE: [Storage:Deployment] + WIN-D2QSN942RT2 | Storage1 - 7-8-2017 08:06:28
    VERBOSE: [Storage:Deployment] + WIN-D2QSN942RT2 | Deployment - 7-8-2017 08:07:00
    VERBOSE: [Storage:Deployment] + WIN-D2QSN942RT2 | Management - 7-8-2017 08:07:16
    VERBOSE: [Storage:Deployment] Test-NetworkMap: END on WIN-D2QSN942RT2 as
    AZURESTACK\AzureStackAdmin - 7-8-2017 08:07:16
    VERBOSE: [Storage:Deployment] Get-NetworkMap: END on WIN-D2QSN942RT2 as AZURESTACK\AzureStackAdmin
     - 7-8-2017 08:07:16
    VERBOSE: [Storage:Deployment] Creating the Storage cluster S-Cluster.azurestack.local with hosts
    WIN-D2QSN942RT2 and IP - 192.168.200.66 192.168.200.66. - 7-8-2017 08:07:17
    VERBOSE: [Storage:Deployment] There is no default route with nexthop of 192.168.200.1. Creating
    this route so that cluster can be created. - 7-8-2017 08:07:17
    WARNING: Task: Invocation of interface 'Deployment' of role 'Cloud\Infrastructure\Storage' failed:


    Type 'Deployment' of Role 'Storage' raised an exception:

    Static address '192.168.200.66' was not found on any cluster network.
    at New-MasCluster, C:\CloudDeployment\Classes\Storage\StorageHelpers.psm1: line 160
    at Deployment, C:\CloudDeployment\Classes\Storage\Storage.psm1: line 172
    at <ScriptBlock>, <No file>: line 18
    at <ScriptBlock>, <No file>: line 16 - 7-8-2017 08:07:18
    Invoke-EceAction : Static address '192.168.200.66' was not found on any cluster network.
    At line:5 char:2
    +  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start Physi ...
    +  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidArgument: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : PSArgument,Microsoft.FailoverClusters.PowerShell.NewClusterCommand,
       CloudEngine.Cmdlets.InvokeCmdlet
    VERBOSE: Step: Status of step 'PhysicalMachineAndInitialConfiguration.20 - (STO) Configure Storage
     Cluster' is 'Error'. - 7-8-2017 08:07:18
    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently
    in progress: 'PhysicalMachineAndInitialConfiguration.20'. - 7-8-2017 08:07:18
    VERBOSE: Action: Action plan 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' failed. Finish
    running all steps that are currently in progress before exiting. - 7-8-2017 08:07:18
    VERBOSE: Draining all steps that are still in progress. The following steps are still in progress
    or just completed: 'PhysicalMachineAndInitialConfiguration.20'. - 7-8-2017 08:07:18
    VERBOSE: Action: Action plan 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' failed. - 7-8-2017
    08:07:18
    Invoke-EceAction : Action: Invocation of step PhysicalMachineAndInitialConfiguration.20 failed. St
    opping invocation of action plan. - 7-8-2017 08:07:18
    At line:5 char:2
    +  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start Physi ...
    +  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: Action: Status of 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' is 'Error'. - 7-8-2017
    08:07:18
    COMPLETE: Task Cloud - Deployment-Phase0-DeployBareMetalAndBGPAndNAT
    VERBOSE: Task: Status of action 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' of role 'Cloud' is
     'Error'. - 7-8-2017 08:07:18
    VERBOSE: Step: Status of step 'PhysicalMachineAndInitialConfiguration - Phase 0 - Configure
    physical machine and external networking' is 'Error'. - 7-8-2017 08:07:18
    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently
    in progress: 'PhysicalMachineAndInitialConfiguration'. - 7-8-2017 08:07:18
    VERBOSE: Action: Action plan 'Deployment' failed. Finish running all steps that are currently in
    progress before exiting. - 7-8-2017 08:07:18
    VERBOSE: Draining all steps that are still in progress. The following steps are still in progress
    or just completed: 'PhysicalMachineAndInitialConfiguration'. - 7-8-2017 08:07:18
    VERBOSE: Action: Action plan 'Deployment' failed. - 7-8-2017 08:07:18
    Invoke-EceAction : Action: Invocation of step PhysicalMachineAndInitialConfiguration failed. Stopp
    ing invocation of action plan. - 7-8-2017 08:07:18
    At line:5 char:2
    +  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start Physi ...
    +  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    any help would be appreciated.

    Regards,

    Monday, August 7, 2017 6:07 PM

Answers

  • Hello Reinout,

    It's a dual socket requirement that's the issue.  The issue is your processor only has 8 Core =  8 Threads and needs at least 12 Cores/threads to run the 13 Infrastructure and Host. 

    12 Core/Threads barely enough to get the deployment to complete.  8 Cores is 33% less than the minimum.

    Unfortunately, 8 Cores does not provide enough resources to Start Up 13 VMs, run Host Processes, Hyper-V and Storage Spaces.

    PS C:\> get-vm

    Name         State   CPUUsage(%) MemoryAssigned(M)
    ----         -----   ----------- -----------------
    AzS-ACS01    Running 0           8192
    AzS-ADFS01   Running 0           1640
    AzS-BGPNAT01 Running 0           1102
    AzS-CA01     Running 0           810
    AzS-DC01     Running 0           4096
    AzS-ERCS01   Running 3           2048
    AzS-Gwy01    Running 0           2048
    AzS-NC01     Running 0           4096
    AzS-SLB01    Running 0           2048
    AzS-Sql01    Running 0           4096
    AzS-WAS01    Running 0           4096
    AzS-WASP01   Running 0           8192
    AzS-Xrp01    Running 0           8192

      Thanks,


    Gary Gallanes


    Monday, August 14, 2017 11:40 PM

All replies

  • Hello,

    It looks like the deployment is failing early in setting up the prerequisites for fabric deployment.

    There may be an issue with the available resources in your environment.

     

    Can you please run the ASDK Pre-requisite checker scriptto validate your environment meets the minimum  requirements?

    https://gallery.technet.microsoft.com/Deployment-Checker-for-50e0f51b

     

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.  If you continue experience any issues with ASDK release, feel free to contact us.

      

    PowerShell giving you the Blues? Try my Azure Stack PowerShell Helper scripts

    ASDK: Install/Import Azure Stack Modules 1.2.10 & AzureStack-Tools

    ASDK: Config PowerShell & set AdminStackAdmin/User ARM Endpoints

      

     Thanks,


    Gary Gallanes

    Tuesday, August 8, 2017 4:37 PM
  • Strange, I noticed that the deployment mentions the IP address 192.168.200.66 twice instead of once!

    [Storage:Deployment] Creating the Storage cluster S-Cluster.azurestack.local with hosts
    WIN-D2QSN942RT2 and IP - 192.168.200.66 192.168.200.66. - 7-8-2017 08:07:17

    My log....

    [Storage:Deployment] Creating the Storage cluster S-Cluster.azurestack.local with hosts WIN-4AMFIAF1HIR and IP - 192.168.200.66.

    Check your network configuration and try to -rerun.


    Cheers,

    Ruud
    Twitter:    Blog: AzureStack.Blog  LinkedIn:    
    Note: Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

    Tuesday, August 8, 2017 6:10 PM
  • Hi Gary and Ruud, I ran the precheck and only got a cpu warning. Due to having a single socket cpu , i tweaked the xml files to accept the xeon due to it having lesser cores. This worked for the previous TP releases, i retan it 10 times Ruud. Did clean retry's from scratch. It gets to step 20 and has already created the az-dc vm why would it fail in sooner then?
    Tuesday, August 8, 2017 6:50 PM
  • [ 16:31:56 ]  -- Check physical disks passed successfully. Note that ASDK handles situations where there is a pre-existing storage pool, and will delete/recreate it.
    [ 16:31:56 ] Checking Memory...
    [ 16:31:56 ]  -- Memory on this server = 192
    [ 16:31:56 ]  -- System memory check passed successfully. ASDK requires a minimum of 96 GB of RAM, with 128 GB recommend
    ed.
    [ 16:31:56 ] Checking processor information...
    [ 16:31:57 ]  -- Number of CPU sockets =
    [ 16:31:57 ]  -- Number of physical cores =
    [ 16:31:57 ]  -- CPU count must be 2 or higher, Core count must be 12 or higher (16 cores recommended).
    [ 16:31:57 ] Checking Hyper-V support on the host...
    [ 16:31:59 ]  -- This server supports the hardware virtualization required to enable Hyper-V.
    [ 16:31:59 ]  Checking free space for extracting the ASDK files...
    [ 16:31:59 ]  -- Listing disks and their free space

    [ 16:32:01 ] FAILURE: 1 prerequisite check(s) failed out of 7 . Please review previous entries to understand where the requirements are not met.
    [ 16:32:01 ] Deployment Checker has finished checking Azure Stack Development Kit requirements

    This is the output: It failed on the CPU only. (Like i said i changed the the baremetal-test.ps1 to accept less cpu's. and the onenode.xml)

    (It is a lab environment after all.) I only have one socket with a xeon with 16 cores (8 cpu / 8 hyperthreading)

    Thursday, August 10, 2017 2:40 PM
  • Hello,

    The ASDK requirements have increased since the release of TP2 & TP3.

    Unfortunately, I’m not authorized to support an ASDK deployment that doesn’t meet the minimum requirements.  

     

    I understand the install script can be tweaked to skip the requirements checks and force the deployment to complete. Please know that this is not a supported configuration and will not provide a realistic depiction of the Azure Stack user experience.  

      

    You should be aware of these points with Azure Stack Development Kit:

    -Azure Stack Development Kit must not be used as a production environment and should only be used for testing, evaluation, and demonstration.

    -Your deployment of Azure Stack is associated with a single Azure Active Directory or Active Directory Federation Services identity provider.

    -You can create multiple users in this directory and assign subscriptions to each user.

    -With all components deployed on the single machine, there are limited physical resources available for tenant resources.

    -This configuration is not intended for scale or performance evaluation.

    -Networking scenarios are limited due to the single host/NIC requirement.

     

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

    If you continue experience any issues with ASDK release, feel free to contact us.

      

    PowerShell giving you the Blues? Try my Azure Stack PowerShell Helper scripts

    ASDK: Install/Import Azure Stack Modules 1.2.10 & AzureStack-Tools

    ASDK: Config PowerShell & set AdminStackAdmin/User ARM Endpoints

      

     Thanks,


    Gary Gallanes


    Thursday, August 10, 2017 4:26 PM
  • I understand the concept of the devkit. Still i would like to be able to use it for lab purposes. I understand i won't get any guarantees but could you atleast point out what the new limits are? As the specifications haven't changed...Or did you hard code the cpu limit?
    • Edited by ReinoutPen Friday, August 11, 2017 12:42 PM
    Friday, August 11, 2017 10:15 AM
  • ASDK Requirements

      

    Component

      
      

    Minimum

      
      

    Recommended

      

    Disk drives: Operating System

    1 OS disk with minimum of 200 GB available for system   partition (SSD or HDD)

    1 OS disk with minimum of 200 GB available for system   partition (SSD or HDD)

    Disk drives: General development kit data*

    4 disks. Each disk provides a minimum of 140 GB of capacity   (SSD or HDD). All available disks will be used.

    4 disks. Each disk provides a minimum of 250 GB of capacity   (SSD or HDD). All available disks will be used.

    Compute: CPU

    Dual-Socket: 12 Physical Cores (total)

    Dual-Socket: 16 Physical Cores (total)

    Compute: Memory

    96 GB RAM

    128 GB RAM (This is the minimum to support PaaS resource   providers.)

    Compute: BIOS

    Hyper-V Enabled (with SLAT support)

    Hyper-V Enabled (with SLAT support)

    Network: NIC

    Windows Server 2012 R2 Certification required for NIC; no   specialized features required

    Windows Server 2012 R2 Certification required for NIC; no   specialized features required

    HW logo certification

    Certified   for Windows Server 2012 R2

    Certified   for Windows Server 2012 R2

       

    ASDK has new capabilities that will enrich your Azure-consistency experience. Learn more about Azure Stack innovation at our launch blog.

    More resources:

     

    Azure Stack Development Kit

    Microsoft Azure Stack Development Kit is a single-node version of Azure Stack, which you can use to evaluate and learn about Azure Stack.

     

    You can also use Azure Stack Development Kit as a developer environment, where you can develop using consistent APIs and tooling.

     

    You should be aware of these points with Azure Stack Development Kit:

     

    Azure Stack Development Kit must not be used as a production environment and should only be used for testing, evaluation, and demonstration.

     

    Your deployment of Azure Stack is associated with a single Azure Active Directory or Active Directory Federation Services identity provider.

     

    You can create multiple users in this directory and assign subscriptions to each user.

    With all components deployed on the single machine, there are limited physical resources available for tenant resources.

     

    Networking scenarios are limited due to the single host/NIC requirement.

     

     Thanks,


    Gary Gallanes

    Friday, August 11, 2017 5:09 PM
  • Hi Gary,

    Thanks for showing me the specs, but i have a single socket Xeon with 8 physical cores? Is it the dual core that's the issue? So must it be a dual socket motherboard containing a total of 12+ cores or is a single socket also enough when its 12 cores?  I'm matching all the other specs....Please answer the question specificly... :)

    Regards,

    Reinout


    • Edited by ReinoutPen Monday, August 14, 2017 8:09 PM
    Friday, August 11, 2017 6:35 PM
  • Hello Reinout,

    It's a dual socket requirement that's the issue.  The issue is your processor only has 8 Core =  8 Threads and needs at least 12 Cores/threads to run the 13 Infrastructure and Host. 

    12 Core/Threads barely enough to get the deployment to complete.  8 Cores is 33% less than the minimum.

    Unfortunately, 8 Cores does not provide enough resources to Start Up 13 VMs, run Host Processes, Hyper-V and Storage Spaces.

    PS C:\> get-vm

    Name         State   CPUUsage(%) MemoryAssigned(M)
    ----         -----   ----------- -----------------
    AzS-ACS01    Running 0           8192
    AzS-ADFS01   Running 0           1640
    AzS-BGPNAT01 Running 0           1102
    AzS-CA01     Running 0           810
    AzS-DC01     Running 0           4096
    AzS-ERCS01   Running 3           2048
    AzS-Gwy01    Running 0           2048
    AzS-NC01     Running 0           4096
    AzS-SLB01    Running 0           2048
    AzS-Sql01    Running 0           4096
    AzS-WAS01    Running 0           4096
    AzS-WASP01   Running 0           8192
    AzS-Xrp01    Running 0           8192

      Thanks,


    Gary Gallanes


    Monday, August 14, 2017 11:40 PM
  • Ok so recap, you need two socket single socket cpu isn't supported even if it's a 12 or 16 physical core cpu. (with hyper-threading it would be 32)

    Thanks so far for your patience.

    Tuesday, August 15, 2017 6:57 AM