What is the Cisco 8000v instance size, as part of the "create a Network Virtual Appliance" process

Imroz Khan 0

I am onboarding the Cisco SD-WAN 8000v routers in Azure portal as part of create a Network Virtual Appliance (NVA) and it takes me to the Azure market place page "Cisco SD-WAN for Azure Virtual WAN".

However it doesnot allow me to choose the instance size of 8000v being selected as part of this process in Azure portal.

I am looking to onboard 8000v's with F32SV2* instance, can you please advise

GitaraniSharma-MSFT 49,011 Reputation points Microsoft Employee

2023-09-28T11:17:22.4366667+00:00

Hello @Imroz Khan ,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

I understand you are trying to onboard the Cisco SD-WAN 8000v NVA into your Azure Virtual WAN hub and it takes you to the Azure marketplace page for "Cisco SD-WAN for Azure Virtual WAN", however it doesn't allow you to choose the instance size of 8000v being selected as part of this process.

Cisco Catalyst 8000V Edge Software (Cisco Catalyst 8000V) is supported as a network virtual appliance (NVA) in Azure Virtual WAN hubs.

Refer: https://video2.skills-academy.com/en-us/azure/virtual-wan/about-nva-hub#partners

And if you check the Cisco SD-WAN Cloud OnRamp, Cisco IOS XE Release 17.x configuration guide for Microsoft Azure Virtual WAN Integration, you can find the below Azure supported Cisco Catalyst 8000V instances:

Refer: https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/cloudonramp/ios-xe-17/cloud-onramp-book-xe/cloud-onramp-multi-cloud-azure.html#Supported-azure-instances

I don't see F32SV2* instance in the supported list.

Regards,

Gita
Imroz Khan 0 Reputation points

2023-09-28T12:07:40.79+00:00

Hi Gitarani,

Thanks for your response, I completely understand that F32s_v2 is not supported as part of Cisco Cloud onramp for Multicloud automation workflow with Azure.

However if you look at the below links from Cisco, they mention 8000v is available for manual onboarding process with Azure instance F32s_v2.

https://www.cisco.com/c/en/us/td/docs/routers/C8000V/Azure/deploying-cisco-catalyst-8000v-on-microsoft-azure/c8000v_microsoftazure_overview.html

https://www.cisco.com/c/en/us/solutions/enterprise-networks/promotions-free-trials/catalyst-8000V-free-trial.html#~promotion-details

Therefore I am looking for a manual process to onboard my 8000v SD-WAN routers with F32s_v2 instance size, and therefore was trying to find if this can be done using the below link create a Network Virtual Appliance (NVA).

Once the NVA are spined up in the Azure cloud using the manual process within the vhub, I could manually configure the BGP configuration between the VWAN hubs and 8000v router. By doing this I will not require the Cisco Cloud onramp for Multicloud automation workflow at all.

Can you please advise if this can be done.
GitaraniSharma-MSFT 49,011 Reputation points Microsoft Employee

2023-09-28T12:47:14.9466667+00:00

Hello @Imroz Khan ,

If you search for Cisco Catalyst 8000V Edge Software in Azure Marketplace, you will find the below options:

If you choose the "Cisco SD-WAN for Azure Virtual WAN" option, then it will not give an option to choose the F32s_v2 instance size, as it is a managed application for Azure Virtual WAN.

But if you select the other 2 options - "Cisco Catalyst 8000V Edge Software" or "Cisco Catalyst 8000V Edge Software (PAYG)" for manual deployment, you will find the F32s_v2 instance size as below:

Regards,

Gita
Imroz Khan 0 Reputation points

2023-09-28T13:05:21.48+00:00

If I onboard the 8000v instance F32v using the manual process, can I onboard them directly into the vhub (similar to the Cisco cloud onramp workflow) or they have to be onboarded into a transit vnet and then a BGP endpoint peering has to be established to the transit vnet with the vhub.
GitaraniSharma-MSFT 49,011 Reputation points Microsoft Employee

2023-09-29T15:17:52.25+00:00

@Imroz Khan , let me check with the Azure Virtual WAN Product Group team on this and get back to you. Will keep you posted.
Imroz Khan 0 Reputation points

2023-10-01T22:04:55.1266667+00:00

Hi Gita,

Checking to find out if you heard from the concerned team
GitaraniSharma-MSFT 49,011 Reputation points Microsoft Employee

2023-10-04T10:35:07.47+00:00

Hello @Imroz Khan ,

Apologies for the delay in response.

I'm still waiting for an update regarding this. Please allow me some more time and I will get back to you soon.

Regards,

Gita
GitaraniSharma-MSFT 49,011 Reputation points Microsoft Employee

2023-10-04T15:37:30.13+00:00

@Imroz Khan , looks like only the NVAs listed in the Partners section can be deployed into the Virtual WAN hub and not any other NVA from Azure marketplace.

Refer: https://video2.skills-academy.com/en-us/azure/virtual-wan/about-nva-hub#can-i-deploy-any-nva-from-azure-marketplace-into-the-virtual-wan-hub

So, you need to onboard the Cisco Catalyst 8000v instance F32v using the manual process into a transit Vnet, connect the transit Vnet to the Virtual hub and then enable BGP peering between the NVA and Virtual hub.

https://video2.skills-academy.com/en-us/azure/virtual-wan/scenario-bgp-peering-hub

https://video2.skills-academy.com/en-us/azure/virtual-wan/create-bgp-peering-hub-portal

Kindly let us know if the above helps or you need further assistance on this issue.

Regards,

Gita
Imroz Khan 0 Reputation points

2023-10-04T23:46:07.2966667+00:00

Thanks, I will wait for your response
GitaraniSharma-MSFT 49,011 Reputation points Microsoft Employee

2023-10-05T12:09:02.5633333+00:00

@Imroz Khan , I've added the answer below.

Kindly let us know if the below helps or you need further assistance on this issue.

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

1 answer

GitaraniSharma-MSFT 49,011 Reputation points Microsoft Employee

2023-10-05T12:08:24.8333333+00:00

Hello @Imroz Khan ,

I understand you are trying to onboard the Cisco SD-WAN 8000v NVA into your Azure Virtual WAN hub and it takes you to the Azure marketplace page for "Cisco SD-WAN for Azure Virtual WAN", however it doesn't allow you to choose the instance size of 8000v being selected as part of this process. You wanted to onboard 8000v with F32SV2* instance size.

Cisco Catalyst 8000V Edge Software (Cisco Catalyst 8000V) is supported as a network virtual appliance (NVA) in Azure Virtual WAN hubs.

Refer: https://video2.skills-academy.com/en-us/azure/virtual-wan/about-nva-hub#partners

And if you check the Cisco SD-WAN Cloud OnRamp, Cisco IOS XE Release 17.x configuration guide for Microsoft Azure Virtual WAN Integration, you can find the below Azure supported Cisco Catalyst 8000V instances:

F32SV2* is not supported in this managed Cisco SD-WAN.

Refer: https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/cloudonramp/ios-xe-17/cloud-onramp-book-xe/cloud-onramp-multi-cloud-azure.html#Supported-azure-instances

But you mentioned that Cisco Catalyst 8000v is available for manual onboarding process with Azure instance F32s_v2 and you wanted to know that if you onboard the 8000v instance F32s_v2 using the manual process, can you onboard them directly into the vHub (similar to the Cisco cloud onramp workflow) or they have to be onboarded into a transit Vnet and then a BGP endpoint peering has to be established to the transit Vnet with the vHub.

I checked into it and found the below in NVA in a Virtual WAN hub FAQ,

Can I deploy any NVA from Azure Marketplace into the Virtual WAN hub? Only partners listed in the Partners section can be deployed into the Virtual WAN hub.

Only the NVAs listed in the Partners section of Azure documentation can be deployed into the Virtual WAN hub and not any other NVA from Azure marketplace.

So, to onboard the Cisco Catalyst 8000v instance F32v using the manual process, you will have to deploy it into a transit Vnet, connect the transit Vnet to the Virtual hub and then enable BGP peering between the NVA and Virtual hub.

https://video2.skills-academy.com/en-us/azure/virtual-wan/scenario-bgp-peering-hub

https://video2.skills-academy.com/en-us/azure/virtual-wan/create-bgp-peering-hub-portal

Kindly let us know if the above helps or you need further assistance on this issue.

Please don’t forget to close the thread by clicking "Accept the answer", as this can be beneficial to other community members.
Please sign in to rate this answer.
GitaraniSharma-MSFT 49,011 Reputation points Microsoft Employee

2023-10-06T15:41:56.1566667+00:00

Hello @Imroz Khan , adding some more information below:

The Azure Virtual WAN Product Group team confirmed that the Cisco SD-WAN 8000v NVA in the virtual hub is a managed solution, and you cannot bring in another set of instances.

But they are discussing with Cisco team to check for any possibility of adding high core instances to achieve higher throughput. This is still under discussion, and we don't have any ETA to share.

So, in the meantime, to onboard the Cisco Catalyst 8000v instance F32v using the manual process, you will have to deploy it into a transit Vnet, connect the transit Vnet to the Virtual hub and then enable BGP peering between the NVA and Virtual hub.

Kindly let us know if you need further assistance on this issue.

Regards,

Gita

Imroz Khan 0 Reputation points

2023-10-11T05:57:55.0466667+00:00

Hi Gita,

Thanks for the response. one more question, is there any difference in the instance bandwidth or throughput between the vhub - 8000v, if I proceed with spinning the 8000v using the vhub managed solution vs using the manual process to onboard the same instance type in a transit vNet.

Or are there any other difference except for the below one's:

With vhub managed solution the process is more automated.

With manual onboard the 8000v are spinned in a transit vnet.

GitaraniSharma-MSFT 49,011 Reputation points Microsoft Employee

2023-10-11T14:45:36.4466667+00:00

Hello @Imroz Khan , if you use the manual process to onboard the same instance type of Cisco v8000 NVA in a transit Vnet as the managed solution, then there should not be any noticeable difference in the bandwidth or throughput.

But I believe the managed solution is more optimized.

As you can see in the below doc:

The Catalyst 8000V is optimized for the Cisco SD-WAN. For enterprises, this means that business-critical applications run faster, with more reliability and reduced Operating Expenditure (OpEx).

Refer: https://www.cisco.com/c/en/us/products/collateral/routers/catalyst-8000v-edge-software/datasheet-c78-744101.html#CiscoSoftwareDefinedWANSDWAN

However, I will get it confirmed with the Azure Virtual WAN Product Group team and provide an update soon.

Regards,

Gita

GitaraniSharma-MSFT 49,011 Reputation points Microsoft Employee

2023-10-12T16:39:26.1366667+00:00

Hello @Imroz Khan , I discussed this with the Azure Virtual WAN Product Group team and Cisco Team and below is their reponse:

C8000V instance throughput depends on the instance type (CPU and Memory resources) and doesn’t depend on whether it is running as managed NVA in vHub or standalone deployment in a transit VNet.

And have asked the below:

Could you please let us know why you are looking for F32s_v2 instance in vHub? If throughput is the requirement, we can deploy up to 80 scale units C8000V NVA in a vHub and scale up to 40 Gbps throughput.

Request you to share your exact requirement and why F32s_v2 instance is needed, so that I can share the details with the Cisco team for future improvements.

Regards,

Gita
Sign in to comment

Share via

What is the Cisco 8000v instance size, as part of the "create a Network Virtual Appliance" process

1 answer