Symptom:
"When I select the Vnet and then the subnet it uses the .4 IP , which is already allocated to another device. The .4 address is the next available IP within the CIDR, but it is not available for use.
Is it possible to change that IP to something else on the same subnet and vNet ?"
Workaround:
There are few workarounds to tackle this issue.
- When you deploy a CSR through portal and reach on summary page then after validation you will see “download template and parameters” tab at the bottom of screen. Click on this tab and you will be presented with a template in json format. Download this template by clicking on "Download Template" button. It will download template in zip format. You need to unzip and update a file template.json using any json editor. Modify following 2 lines in template.json:
"privateIPAddress": "[parameters('subnet1StartAddress')]"
"privateIPAddress": "[parameters('subnet2StartAddress')]"
Change this to "privateIPAddress": "[parameters('<your desired private IPaddress>')]".
After making these changes do not forget to run json validation to make sure contents of this file are valid.
After you update the template, go to Azure Portal. Click on (left side column) NEW-->Template Deployment-->Create. Here in Template Deployment windows you need to copy and paste the template.json file. Now, UI will ask you the parameters to enter. At this point, you can from parameters.json file.
- You can use azure CLI or poweshell commands to create CSR. I can provide you sample CLI configuration to deploy the CSR.
Cisco is working on fixing this issue and will be updating the CSR deployment templates soon....
