microsoft/SDN

is not a valid argument for ‘addressPrefix’ of a subnet

DCoates-InnovateLtd opened this issue · 1 comments

Good morning,

Does anyone have a fix for this issue? I have had a play around with the script and functions and they all seem to be working fine and returns what i would expect is the correct results. I have attached the config file.

any help will be much appreciated.

C:\temp\SDN-master\SDN-master\SDNExpress\scripts\SDNExpress.ps1 : Exception calling "ProcessRecord" with "1"
argument(s): "{
"error": {
"code": "InvalidParameterValue",
"message": "‘10.200.6.50/27’ is not a valid argument for ‘addressPrefix’ of a subnet., Target: LogicalSubnet",
"target": "LogicalSubnet"
}
}"
At line:1 char:1

  • . .\SDNExpress.ps1 -ConfigurationDataFile .\MultiNodeSampleConfig.psd ...
  •   + CategoryInfo          : NotSpecified: (:) [SDNExpress.ps1], MethodInvocationException
      + FullyQualifiedErrorId : CmdletInvocationException,SDNExpress.ps1
    
    

MultiNodeSampleConfigv12.txt

Hi
Thanks for reporting this issue. Couple of comments:

  1. You need to increase the PA pool size in the configuration file. Right now, you have 8 addresses in the PA pool. Each physical host takes 2 addresses from the PA pool, and each SLB MUX and GW VM takes 1 address from the PA pool. So, you will need at least 12 addresses, and best to keep some buffer in case you want to add more infrastructure at a later point of time.
  2. I see that your private VIP subnet is part of your PA subnet. This may cause issues. Ideally, your public and private VIP subnets can be anything, as long as they don't overlap with any other subnets in your network. We advertise these subnets over BGP, so these subnets do not need to be pre-exist on your physical network.