SDWAN Cloud onRamp in IaaS Azure using existing Transit VNET

[abelriveron]

Hi there.

Could anyone please clarify whether the Cisco Cloud OnRamp for IaaS solution creates a New Transit VPC/VNET where the WAN cEdges are placed in, or it can uses an existing Transit VPC/VNET and adds the WAN cEdges there?

All Cisco documentation I have reviewed so far only mention the creation of a NEW Transit VPC/VNET via vManage.

On the vManage Cisco Cloud OnRamp for IaaS wizard, there is no option to select an existing Transit VPC/VNET, but only a field to set the name of a new Transit VNET.

The above concern comes because a customer has an existing Azure environment (one Transit VNET and two Host VNETs) and wants to migrate to Cisco SDWAN using CSR1000v, so the question is whether Cloud onRamp IaaS can be used to spin up the two CSRs in the existing customer Transit VNET. 

Any advise regarding this topic is very appreciated.

Abel

[Kanan Huseynli]

Hi,

based on documentation SD-WAN devices are used in Transit VPC/VNET and they connect to VPG/VPN GW via standard IPSEC and BGP (if needed). Hence, if your customer have 2 routers in Azure as Transit VNET, then can migrate them to SD-WAN. Basically, routers will have overlay connection in SD-WAN and connection to host VPC/VNET via IPSec+BGP.

https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/cloudonramp/vedge-20-x/cloud-onramp-book-vedge/m-cloud-onramp-iaas.html

HTH,

[abelriveron]

Hi Kanan,

Thanks for your reply. Currently, the customer does not have any router in its Transit VNET. 

Basically, what I need to confirm is whether the Cloud OnRamp configuration process via vManage will provide any option to select an existing customer Transit VNET (based on the customer Azure account/credentials entered) where the CSR1K routers will be spin up. Or, if vManage will create a completely New Transit VNET where the CSR1K routers will be spin up.