Cisco ASAv in Microsoft Azure only can deploy in more than /24 address range virtual network (VNET)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2020 07:51 AM
When deploy Cisco ASAv in Microsoft Azure, it only can deploy or implement more than /24 address range existing VNET or new VNET.
But for my current VNET in Azure only created for /27 address range.
Can i contact Cisco support to allow me deploy Cisco ASAv in /27 address range VNET? Or contact Microsoft Support to allow it?
- Labels:
-
Cloud Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2020 09:00 PM
I personally worked with aws but not azure too much with asav.
Do you mean the asa provisioning fails when using /27?
Do you have a particular message?
I don’t see anything in Cisco documentation that /27 is restriction. TAC might be able to help.
Thanks
Francesco
PS: Please don't forget to rate and select as validated answer if this answered your question
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2020 09:07 PM
Hi Francesco,
As below image, the Azure show the Virtual Network for Cisco ASAv prefix must be smaller than or equal to 24.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2020 07:07 PM
Instead of writing it using cidr mask have you tried configuring it using the range like it shows in the screen:
172.31.154.0 - 172.31.154.31
Thanks
Francesco
PS: Please don't forget to rate and select as validated answer if this answered your question
