Assigning a static IP to a Meraki vpn concentrator (VMX) in Azure - is it possible?

Question

Can a SME from MS-Azure either confirm or deny that I can/can't assign a static public IP and static private IP to a VM-Cisco Meraki or do I have to take the DHCP assignment handed out by MS?

They aren't sure on the Cisco forum and I need a definitive answer.

Thanks in advance
Sharyn

Answer 1

Hi @Sharyn Schmidt

I just wanted to make my last comment on this case scenario. Please review the observation shown below:

• For instance, I was taking the time and review this in deep so, The first thing that brought my attention was that this NVA(Network Virtual Appliance) is Cisco Vendor as well as this is a managed application VM(Which is managed by CISCO).

Review Managed application definition from Azure library/Documentation.
An Azure managed application plan is one way to publish an Azure application offer in Azure Marketplace. If you haven't already done so, read Plan an Azure Application offer for the commercial marketplace.
Managed applications are transact offers that are deployed and billed through Azure Marketplace. The listing option that a user sees is Get It Now.
Use an Azure Application: Managed application plan when the following conditions are required:
You will deploy a subscription-based solution for your customer using either a virtual machine (VM) or an entire infrastructure as a service (IaaS)-based solution.
You or your customer requires the solution to be managed by a partner. For example, a partner can be a systems integrator or a managed service provider (MSP).

-Furthermore, I did mention to you that I have my own FW vendor image but this one is not Managed application which let me to add/modify/change my NIC settings.

See images below.

That PIP(Public IP) is for Remote Access as well as other interfaces(NIC's) assigned for untrust/trust zones like most FW's.

-I have been saying that when you deploy a resource and it requires to use PIP's, you can use a PIP already provisioned before or at the moment of resource creation to choose the option create new one

-Another way to retain PIP's is to use the feature IP prefix which you can select different ranges for you like:

-Having said that, I am not sure if your task is to perform a software/Firmware upgrade or Recreate this existing vMX in a newer version. If you were going to recreate this NVA, I wonder if you have considered this option from the vMX appliance itself:

Answer 2

Hello @Sharyn Schmidt

Thank you for your feedback.

I am wondering if you have tried to do it like this:

For instance, I have a PA FW and I do not have those issue... Try to get it done like the image shown above.

Looking forward to your feedback,

Best Regards,

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Answer 3

Hi @Sharyn Schmidt

Here is the answer for this concern below:

Looking forward to your feedback,

Best Regards,

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.