SOLVED

CCE register appliance failure

%3CLINGO-SUB%20id%3D%22lingo-sub-88493%22%20slang%3D%22en-US%22%3ECCE%20register%20appliance%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-88493%22%20slang%3D%22en-US%22%3E%3CP%3EIm%20attempting%20to%20register%20a%20CCE%20appliance%20but%20the%20cmdlet%20fails%20with%20the%20error%20msg%20highlighted%20in%20bold%20below.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPS%20C%3A%5CUsers%5Cshawn%26gt%3B%20Register-CcAppliance%3CBR%20%2F%3EThe%20RegisterInstance%20log%20is%20in%20C%3A%5CUsers%5Cshawn%5CCloudConnector%5CApplianceRoot%5CLog%5Cazhyperv_RegisterInstance%2B00_00_2017_07_19_12_11_55.log.%3CBR%20%2F%3ETask%3ARegisterInstance%20starts%20at%202017-07-19T12%3A11%3A55.5867815%2B00%3A00%3CBR%20%2F%3EThe%20current%20scripts%20version%20is%206.0.9319.377.%3CBR%20%2F%3EThere%20are%20no%20instances%20currently%20running.%3CBR%20%2F%3EStarted%20Initializing%20the%20account%20for%20CceService...%3CBR%20%2F%3EUser%3A%20CceService%20exists.%3CBR%20%2F%3EUser%3A%20CceService%20is%20already%20a%20member%20of%20the%20local%20Administrators%20group.%3CBR%20%2F%3EUser%3A%20CceService%20is%20already%20a%20member%20of%20the%20Hyper-V%20Administrators%20group..%3CBR%20%2F%3EInitialize%20CceService%20account%20finished.%3CBR%20%2F%3E%3CSTRONG%3ENew-ManagementAddressAllocator%20%3A%20The%20management%20IP%20prefix%20will%20be%20deleted%20based%20on%20the%20prefix%20length%20setting.%20Pleaseupdate%20the%20.ini%20file%2C%20and%20then%20run%20it%20again.At%20C%3A%5CProgram%20Files%5CWindowsPowerShell%5CModules%5CCloudConnector%5CInternal%5CMtConfigurations.ps1%3A200%20char%3A35%2B%20...%20Allocator%20%3D%20New-ManagementAddressAllocator%20%24managementIpPrefix%20%24manag%20...%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%2B%20CategoryInfo%20%3A%20NotSpecified%3A%20(%3A)%20%5BWrite-Error%5D%2C%20WriteErrorException%2B%20FullyQualifiedErrorId%20%3A%20Microsoft.PowerShell.Commands.WriteErrorException%2CNew-ManagementAddressAllocator%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3ENew-ManagementAddressAllocator%20%3A%20The%20management%20IP%20prefix%20will%20be%20deleted%20based%20on%20the%20prefix%20length%20setting.%20Please%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3Eupdate%20the%20.ini%20file%2C%20and%20then%20run%20it%20again.%3C%2FSTRONG%3E%3CBR%20%2F%3EAt%20C%3A%5CProgram%20Files%5CWindowsPowerShell%5CModules%5CCloudConnector%5CInternal%5CMtConfigurations.ps1%3A200%20char%3A35%3CBR%20%2F%3E%2B%20...%20Allocator%20%3D%20New-ManagementAddressAllocator%20%24managementIpPrefix%20%24manag%20...%3CBR%20%2F%3E%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3CBR%20%2F%3E%2B%20CategoryInfo%20%3A%20NotSpecified%3A%20(%3A)%20%5BWrite-Error%5D%2C%20WriteErrorException%3CBR%20%2F%3E%2B%20FullyQualifiedErrorId%20%3A%20Microsoft.PowerShell.Commands.WriteErrorException%2CNew-ManagementAddressAllocator%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20management%20switch%20config%20from%20my%20.ini%20file%20is%20below%3A-%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E%3B%20The%20management%20switch%20to%20provide%20network%20connectivity%20of%20host%20and%20VMs.%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3B%20ManagementIPPrefix%20in%20MUST%20be%20configured%20as%20different%20subnet%20from%20other%20internal%20IPs.%20%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3B%20Just%20as%20the%20default%20value%20shown%2C%20ManagementIPPrefix%20is%20192.168.213.0%2C%20while%20AD%20IPAddress%20is%20192.168.0.238%20%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3B%20The%20ManagementIPPrefixLength%20should%20be%20a%20value%20in%20range%20%5B8%2C%2029%5D.%20%3C%2FEM%3E%3CBR%20%2F%3E%3CU%3E%3CEM%3EManagementSwitchName%3DManagementSwitch%3C%2FEM%3E%3C%2FU%3E%3CBR%20%2F%3E%3CU%3E%3CEM%3EManagementIPPrefix%3D192.168.1.2%3C%2FEM%3E%3C%2FU%3E%3CBR%20%2F%3E%3CU%3E%3CEM%3EManagementIPPrefixLength%3D24%3C%2FEM%3E%3C%2FU%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHaving%20not%20installed%20CCE%20before%20im%20unsure%20what%20the%20problem%20is.%20I've%20already%20created%20the%20vSwitch%20(ManagementSwitch)%20and%20the%20vSwitch's%20IP%20address%20doesnt%20clash%20with%20the%20IP%20address%20in%20the%20.ini.%20Its%20a%20%2F24%20network%20also%20so%20no%20problem%20there%20from%20what%20i%20can%20see%3F%20Any%20ideas%20what%20im%20doing%20wrong%20or%20what%20the%20problem%20may%20be%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-88493%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EVoice%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-88823%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20CCE%20register%20appliance%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-88823%22%20slang%3D%22en-US%22%3EYeah%20does%20make%20you%20wonder%20who%20named%20that%20and%20why%3F%20Hardly%20intuitive.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-88817%22%20slang%3D%22en-US%22%3ERE%3A%20CCE%20register%20appliance%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-88817%22%20slang%3D%22en-US%22%3EThere%20should%20be%20an%20RFC%20for%20naming%20standards%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-88770%22%20slang%3D%22en-US%22%3ERe%3A%20CCE%20register%20appliance%20failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-88770%22%20slang%3D%22en-US%22%3E%3CP%3EI%20didnt%20twig%20the%20%3CU%3E%3CEM%3EManagementIPPrefix%3D%20%3C%2FEM%3E%3C%2FU%3EIs%20supposed%20to%20be%20the%20subnet%20hence%20the%20error%20message%20i%20was%20seeing.%20After%20changing%20this%20to%20x.x.x.0%20the%20Register-CcAppliance%20completed%20fine.%20Shout%20out%20to%20Max%20Sanna!%20Cheers%20dude!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Im attempting to register a CCE appliance but the cmdlet fails with the error msg highlighted in bold below.

 

PS C:\Users\shawn> Register-CcAppliance
The RegisterInstance log is in C:\Users\shawn\CloudConnector\ApplianceRoot\Log\azhyperv_RegisterInstance+00_00_2017_07_19_12_11_55.log.
Task:RegisterInstance starts at 2017-07-19T12:11:55.5867815+00:00
The current scripts version is 6.0.9319.377.
There are no instances currently running.
Started Initializing the account for CceService...
User: CceService exists.
User: CceService is already a member of the local Administrators group.
User: CceService is already a member of the Hyper-V Administrators group..
Initialize CceService account finished.
New-ManagementAddressAllocator : The management IP prefix will be deleted based on the prefix length setting. Please
update the .ini file, and then run it again.
At C:\Program Files\WindowsPowerShell\Modules\CloudConnector\Internal\MtConfigurations.ps1:200 char:35
+ ... Allocator = New-ManagementAddressAllocator $managementIpPrefix $manag ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-ManagementAddressAllocator

New-ManagementAddressAllocator : The management IP prefix will be deleted based on the prefix length setting. Please
update the .ini file, and then run it again.
At C:\Program Files\WindowsPowerShell\Modules\CloudConnector\Internal\MtConfigurations.ps1:200 char:35
+ ... Allocator = New-ManagementAddressAllocator $managementIpPrefix $manag ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-ManagementAddressAllocator

 

My management switch config from my .ini file is below:-

 

; The management switch to provide network connectivity of host and VMs.
; ManagementIPPrefix in MUST be configured as different subnet from other internal IPs.
; Just as the default value shown, ManagementIPPrefix is 192.168.213.0, while AD IPAddress is 192.168.0.238
; The ManagementIPPrefixLength should be a value in range [8, 29].
ManagementSwitchName=ManagementSwitch
ManagementIPPrefix=192.168.1.2
ManagementIPPrefixLength=24

 

Having not installed CCE before im unsure what the problem is. I've already created the vSwitch (ManagementSwitch) and the vSwitch's IP address doesnt clash with the IP address in the .ini. Its a /24 network also so no problem there from what i can see? Any ideas what im doing wrong or what the problem may be?

3 Replies
Best Response confirmed by shawn harry (Contributor)
Solution

I didnt twig the ManagementIPPrefix= Is supposed to be the subnet hence the error message i was seeing. After changing this to x.x.x.0 the Register-CcAppliance completed fine. Shout out to Max Sanna! Cheers dude!

There should be an RFC for naming standards :)
Yeah does make you wonder who named that and why? Hardly intuitive.