LnetDynamicAllocationBlockedIfLessThanV6
N0rthg4t3 opened this issue · 1 comments
Hi there,
while trying to roll out an SDN testing environment with SDN Express based closely on the MultiNodeSampleConfig upon Azure Stack HCI 22H2, some error that I have never seen before terminates all ongoing operations after "Creating frontend nic" to the MUXes with the following description:
VERBOSE: [20240415-16:16:46] STAGE 5.1: Create Gateway VMs
VERBOSE: [20240415-16:16:46] Enter Function: Initialize-SDNExpressGateway
VERBOSE: [20240415-16:16:46] -FrontEndAddressPrefix: XXX.XXX.XX.X/XX
VERBOSE: [20240415-16:16:46] -HostName: XXX-XXX-XXX
VERBOSE: [20240415-16:16:46] -JoinDomain: XXXXXXXXXXXXX
VERBOSE: [20240415-16:16:46] -ComputerName: XXXXXXXXXXXXXX
VERBOSE: [20240415-16:16:46] -RestName: sdn.XXXXXXXXXXXXXXXXX
VERBOSE: [20240415-16:16:46] -FrontEndLogicalNetworkName: HNVPA
VERBOSE: [20240415-16:16:46] -Credential: System.Management.Automation.PSCredential
VERBOSE: [20240415-16:16:46] Unbound Arguments:
VERBOSE: [20240415-16:16:46] ParameterSet: Default
VERBOSE: [20240415-16:16:46] Found logical subnet XXX.XXX.XX.X_XX
VERBOSE: [20240415-16:16:46] Backend MAC Address is 020100000109
VERBOSE: [20240415-16:16:46] Creating frontend NIC
C:\SDN-master\SDNExpress\scripts\SDNExpress.ps1 : Exception calling "ProcessRecord" with "1" argument(s): "{
"error": {
"code": "LnetDynamicAllocationBlockedIfLessThanV6",
"message": "LogicalNetwork dynamic IP address allocation is not supported for NRP API versions less than 5.",
"innerError": "Microsoft.WindowsAzure.Networking.Nrp.Frontend.Common.ValidationException: LogicalNetwork dynamic IP address allocation is not supported for NRP API versions less than 5.\r\n
at Microsoft.Windows.Networking.NetworkController.RestApi.Tenant.Operations.PutNetworkInterfaceOperation.Execute()\r\n at
Microsoft.Windows.Networking.NetworkController.RestApi.Common.Operations.Operation`1.Run()"
}
}"
At line:1 char:1
+ .\SDNExpress.ps1 -ConfigurationDataFile .\AHCImucSDNConfig.psd1 -Verb ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [SDNExpress.ps1], MethodInvocationException
+ FullyQualifiedErrorId : CmdletInvocationException,SDNExpress.ps1
I have also created more classical rollouts before during which I waived rolling out the SLB / MUX and gateway part. In these constellations, the error does logically not appear because there is no such configuration needed.
I am unsure on how to approach troubleshooting with this since the error or some things connected with it seem to be very elusive while researching the web. Also I am unable to find any references as of yet in this github repository.
While I am sure that this might be either rooted in some misconfiguration or software dependencies, I am still unsure how to get a little bit closer to troubleshooting the stack.
Has anyone ever seen this and can help me out on this?
I will also try to dive a little bit deeper into the powershell modules that are used for provisioning.