none
ASDK deployment code

    Question

  • Hi,

    Is the ASDK deployment open source? If not can it be :)

    I have noticed what I think is a bug with the network configuration on the BGPNAT box. Despite supplying a /28 a /24 has been configured. 

    If I could see the code I could check if I am correct, raise an issue and potentially propose a fix.

    Thanks

    Charlie

    Tuesday, November 28, 2017 6:50 AM

All replies

  • Hi Charlie,

    Can you elaborate a bit more about where you're trying to configure the subnet?  If you're trying to specify an IP address on the BGPNAT instance using the ASDK deployment UI, and are providing a Static IP for the BGPNAT using CIDR notation (e.g. 10.50.107.20/28), and that is somehow being converted to 10.50.107.20/24 then yes this not only a bug, but a bug that nobody has seen or reported yet and that we are unable to reproduce on our side.  

    Is this what you're trying to do?  Or are you trying to do something else?

    Thanks,

    Scott

    Thursday, November 30, 2017 7:20 PM
  • Hello Charlie,

    The ASDK-Installer 'Static IP Address' field requires the subnet mask be formatted in the address (with no spaces).

      

    Example:
    IP:  10.0.120.32
    subnet mask:   255.255.255.0

     

    would be formatted as:  10.0.120.32/24

     

    To determine how many bits to set for your subnet see the chart below
    or http://www.subnet-calculator.com
        
    Class B IP Subnetting
    /16 = 255.255.0.0
    /17 = 255.255.128.0
    /18 = 255.255.192.0
    /19 = 255.255.224.0
    /20 = 255.255.240.0
    /21 = 255.255.248.0
    /22 = 255.255.252.0
    /23 = 255.255.254.0

    Class C IP Subnetting
    /24 = 255.255.255.0  
    /25 = 255.255.255.128
    /26 = 255.255.255.192
    /27 = 255.255.255.224 

      

    Also - You can still deploy from command-line although it is not recommended as the ASDK-Installer forces valid parameters.

     

    ADFS Example

     

    cdC:\CloudDeployment\Setup

    $adminpass= ConvertTo-SecureString "Changeme" -AsPlainText -Force

    .\InstallAzureStackPOC.ps1  -AdminPassword $adminpass -UseADFS -NATIPv4Subnet 10.184.224.0/26 -NATIPv4Address `

    10.184.224.59-NATIPv4DefaultGateway 10.184.224.1 -DNSForwarder 111.111.111.111 -TimeServer 10.218.96.115

      

    Azure Cloud Example

     

    cdC:\CloudDeployment\Setup

    $adminpass= ConvertTo-SecureString "Changeme" -AsPlainText -Force

    $aadpass= ConvertTo-SecureString "Changeme" -AsPlainText -Force

    $aadcred= New-Object System.Management.Automation.PSCredentia ("MyADAdmin@MyAzureAD.onmicrosoft.com", $aadpass)

    .\InstallAzureStackPOC.ps1-AdminPassword $adminpass -InfraAzureDirectoryTenantAdminCredential $aadcred -InfraAzureDirectoryTenantName "MyAzureAD.onmicrosoft.com" `

    -NATIPv4Subnet10.184.224.0/26 -NATIPv4Address 10.184.224.59 -NATIPv4DefaultGateway 10.184.224.1 -DNSForwarder 111.111.111.111 -TimeServer 10.218.96.115

     

      

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

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

         

     Thanks


    Gary Gallanes

    Friday, December 01, 2017 12:43 AM
    Moderator
  • Hey Gary,

    I have had a chance to redploy and can confirm I think this is a bug. During the deployment I specify a static address for the NAT box which I define with a /28 as the subnet size. However when running get-netnat and ipconfig show that a /24 is defined.

    This should not be the case it should use a /28 as defined.

    

    Could you also answer whether the deployment code is available to view?

    Thanks

    Charlie

    Wednesday, December 06, 2017 11:54 AM