Public Cloud Connectivity - Edit connector
In this guide, we will walk you through the steps to modify a cloud connector in designed status.
From the Inventory, select the cloud connector
Only a cloud connector in Designed status can be modified.
Select the cloud connector in the list and click on the tree dots on the right and click on "Edit connector":
Cloud connector inventory.
Step 1 : Project
Update connector form step 1.
You can't change the project attached to a cloud connector.
You have to create a new cloud connector with the corresponding project.
Step 2 : Modify Cloud connector parameters
The journey is quite the same as the creation one, except for the flavor option which can’t be changed.
After clicking on Next, the following form will be displayed:
Update connector form step 2.
Step 3 : Technical Virtual Private Network and Orange Business POP configuration
Update connector form step 3.
You can update the following parameters:
- The Orange POP from which you want to build the Cloud connector. (standard connection One POP, for HA select primary and secondary POP)
- The reserved bandwidth you need for it.
- The configured bandwidth you need for it.
Step 4 : The Network settings
Update connector form step 4.
The existing cloud resources are displayed, giving you the ability to modify cloud parameters such as the region, resource group, and VNET.
| Parameter | Description |
|---|---|
| Azure ASN (AS Number) | BGP Private ASN allocated by the customer to identify AZURE IP routes announced to Orange Business Network. This ASN has to be unique in the whole customer network. Private ASN range is 64512 to 65535. 65515 to 65520 are excluded as there are used by Microsoft Azure for internal use. |
| Network ASN (AS Number) | BGP Private ASN allocated by the customer to identify Orange Business IP routes announced to AZURE Network. This ASN has to be unique in the whole customer network. Private ASN range is 64512 to 65535. 65515 to 65520 are excluded as there are used by Microsoft Azure for internal use. |
| Network Gateway Subnet | A /29 IPv4 address allocated by the customer. This /29 have to be unique in the whole customer private network (including VNET/VPC in Cloud) |
| Azure Gateway Subnet | a /27 IPv4 address subnet for VPNGW addressing within the VNET addressing plan in AZURE. CIDR notation (i.e something like 192.xxx.xxx.xxx/27). |
Select the Cloud credentials to be used for the CSP VNET resources to reach, then select the CSP region, resource group and VNET.
The resource group and VNET are retrieved from the customer CSP environment linked to the Cloud credentials selected.
If a VNET is already used with a VPN gateway, it won’t be displayed in the VNET list.
Update cloud resources and then click on Next button.
Step 5 : Summary and pricing
Update connector form step 5.
- On this screen you have on the right a summary of the cloud connector configuration.
- Soon you will have an estimated pricing for this configured cloud connector.
Click on Save as designed if you want to save your new configuration.
You will be able to provision the cloud connector from Cloud Connector Inventory. See Provisioning .
When you choose Save as Designed your cloud connector is not deployed and running yet and can still be modified.
If you click on Back to the dashboard, you can see your updated cloud connector in the inventory.
Cloud Connector inventory with an edited Cloud Connector.