paloaltonetworks/azure

VM-Series ARM Templates for Microsoft Azure

VM-Series for Microsoft Azure

This is a repository for Azure Resoure Manager (ARM) templates to deploy VM-Series Next-Generation firewall from Palo Alto Networks in to the Azure public cloud.

VM-Series in Azure Marketplace:

• Bring Your Own License - BYOL
• Pay-As-You-Go (PAYG) Hourly Bundle 1 and Bundle 2

Documentation

• Technical documentation
• VM-Series Datasheet PDF
• Deploying ARM Templates

NOTE:

• Deploying ARM templates requires some expertise and customization of the ARM JSON template. Please review the basic structure of ARM templates.
• Most of the templates in this repository typically use the BYOL version of VM-Series. If you want to use a different SKU then you can edit the azureDeploy.json template to set the "imageSku" variable to use "byol", "bundle1" or "bundle2":

"imagePublisher": "paloaltonetworks",
"imageSku":       "byol",
"imageOffer" :    "vmseries1",
"imageVersion":   "latest"

• By default, if "imageVersion" is not specified then the latest PAN-OS version available in Azure Marketplace is used (equivalent to writing "imageVersion": "latest"). To use a specific PAN-OS version available in the Azure Marketplace, set it as "imageVersion": "8.0.0" or "imageVersion": "7.1.1". For an example on setting the PAN-OS version see the following template: https://github.com/PaloAltoNetworks/azure/tree/master/vmseries-avset

• Before you use the custom ARM templates here, you must first deploy the related VM from the Azure Marketplace into the intended/destination Azure location. This enables programmatic access (i.e. template-based deployment) to deploy the VM from Azure Marketplace. You can then delete the Marketplace-based deployment if you don't need it.

• For example, if you plan to use a custom ARM template to deploy a BYOL VM of VM-Series into Australia-East, then first deploy the BYOL VM from Marketplace into Australia. This is needed only the first time. You can then delete this VM and its related resources. Now your ARM templates, from GitHub or via CLI, will work.

• The older Marketplace listing VM-Series (BYOL) Solution Template is deprecated; please do not use this template. Use the above listings in the Marketplace.

Proceed with Caution:

These repositories contain default password information and should be used for Proof of Concept purposes only. If you wish to use this template in a production environment it is your responsibility to change the default passwords.

azure's Issues

Cannot deploy template - validating DNS names in form gives error.

When I try to this template I get an error will filling in the requested info on the first form where it requests storage accoutn name, resource group etc.

It hangs on the DNS names for the fw and the NATVM:

In the region North Europe I see several instances of this template deployed so that means the prerequisite to deploy it via the marketplace once per region has already been fulfilled.

Is there a bug in this template, am I doing something wrong or is there an issue with Azure?

Thx,
Tom

template for available zone

this template is for available set.do you have the version for available zone? some Azure region support multi-zone

baseUrl: Page not Found

The reference file for baseUrl is nowhere to be found.

Parameters: baseUrl

"defaultValue": "https://raw.githubusercontent.com/PaloAltoNetworks/azure/master/vmseries-avset"

Cannot Deploy with Private Marketplace

The vmseries1 offer is no longer visible in the marketplace, it's only vmseries-ngfw.

If the client tries to deploy and private marketplace is enabled, this error appears:

But the "vmseries1" offer appears to be delisted from the marketplace so it cannot be added. Please provide the offer ID info so that it can be added to a private marketplace via Set-AzMarketplacePrivateStoreOffer

Where's the 10.5.5.0/24 network?

I see a route to this but is nowhere in the diagram (unless I just don't see it).

Error when deploying using Powershell

Hello,

I am trying to deploy your AVSet template and when it tries I get the following error:

New-AzureRmResourceGroupDeployment : 2:09:01 PM - Error: Code=InvalidTemplate; Message=Deployment template validation failed: 'The template parameters 'imageVersion, availabilitySetName' in the parameters file are not valid; they are not present in the original template and can therefore not be provided at deployment time. The only supported parameters for this template are 'location, vmName, imageSku, imageOffer, imagePublisher, nicName, vmSize, adminUsername, adminPassword, newStorageAccount, sshKey'. Please see https://aka.ms/arm-deploy/#parameter-file for usage details.'.

I checked the template file and the parameters file and I cannot find any issues.
The template file clearly identifies both of the parameters it is complaining about.

I can deploy this template fine if I use the web gui but not through powershell.
Let me know if you require further details

Hard coded IP ranges

IP ranges are hardcoded into the two-tier-sample template, meaning the template usually requires reworking for each environment, as opposed to just working with the parameters file.

It would be useful if we could deploy "VM-Series Next-Generation Firewall from Palo Alto Networks" from Azure marketplace (azure portal) into an availability set or availability zone; unfortunately the deployment wizard doesn't include the option - so we have to use ARM or delete the VM and recreate it from disk in an availability set.

Does this handle NATing multiple public IP addresses?

Does this handle NATing multiple public IP addresses to unique addresses on the firewall? If so, what needs to be edited?

Where does $1 come from?

Is this script intended to be run just once when the VM is set up, or does it need to go into a startup script?

Links to Azure marketplace and PaloAlto documentation in readme are broken

Documentation link

readme of PaloAltoNetworks/azure

Describe the problem

There are stale links in the readme for the Azure marketplace and the PaloAlto technical documentation.

Suggested fix

Provide updated links to current content/documentation

S

Webserver can't get out to the internet.

Describe the bug

Freshly deployed two-tier-sample template. Can't reach the webserver from it's public DNS name. SSH into the webserver from the FW, unable to get out to the internet.

Expected behavior

Navigating to the webServerURL output from the template should bring me to the website.

Current behavior

Navigating to the webServerURL output from the template returns a connection timeout.

Possible solution

Steps to reproduce

1. Deploy template
2. Open web browser
3. Navigate to the webServerURL output from the template
4. Observe result

Screenshots

Context

Your Environment

• Version used:
• Environment name and version (e.g. Chrome 59, node.js 5.4, python 3.7.3):
• Operating System and version (desktop or mobile):
• Link to your project:

Deployment suceeds but firewall dosent start properly

Describe the bug

Password requirement inconsistency, palo alto portal and terraform images differ in availability.

I am deploying via terraform so my deployment is consistent. I normally use the latest tag for the PA image.

  vm_size                      = "Standard_D3_v2"
  sku                             = "bundle2"
  publisher                    = "paloaltonetworks"
  product                      = "vmseries1"
  version                       = "latest"

I recently updated my password to be alpha numeric 32 characters.
E.g. Password1234password1234password1234.
If i try and set a password without a capital letter, i get the following error

Error: compute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="InvalidParameter" Message="The supplied password must be between 6-72 characters long and must satisfy at least 3 of password complexity requirements from the following:\r\n1) Contains an uppercase character\r\n2) Contains a lowercase character\r\n3) Contains a numeric digit\r\n4) Contains a special character\r\n5) Control characters are not allowed" Target="adminPassword"

So the password policy is 6-72 characters with numbers, capital and lower case letters.

If i set the password to Password1234password1234password1234 the deployment succeeds, but i cannot log in via the SSH prompt (says incorrect password) despite the password conforming with the password policy. The web UI never loads, i always get a HTTP timeout.

I tried to deploy via the portal and i couldnt find a suitable version. It only gives me an option of 9.1.2 and not the large option list i get via terraform.
I also noticed that via the portal the VM type that gets deployed is vmseries-flexible and not vmseries1 or vmseries2. I cant find any documentation on this type. Im assuming flexible means that its either 1 or 2.

So i changed my deployment to:

  vm_size                      = "Standard_D3_v2"
  sku                            = "bundle1"
  publisher                    = "paloaltonetworks"
  product                      = "vmseries-flex"
  version                       = "9.1.2"

With password Password1234password1234password1234 i get the same behaviour, but with password Password1234 the web UI loads and the SSH prompt allows me to log in!

Expected behavior

32 length character password dosent cause deployment issues despite conforming to password requirements.

Current behavior

A long password somehow breaks the deployment.

Possible solution

The current workaround i have is to use a small (12 character) alpha numeric password rather than a 32 character one.

Your Environment

experienced with:

  vm_size                      = "Standard_D3_v2"
  sku                             = "bundle2"
  publisher                    = "paloaltonetworks"
  product                      = "vmseries1"
  version                       = "latest"

and also:

  vm_size                      = "Standard_D3_v2"
  sku                            = "bundle1"
  publisher                    = "paloaltonetworks"
  product                      = "vmseries-flex"
  version                       = "9.1.2"

With deployments via the portal and by terraform. Seems to be a problem with the core palo alto images.

Unable to deploy Marketplace image

PA Networks,

I don't believe this is an issue with the image itself. However, I wanted to inform you that when attempting to purchase your product within the Azure Marketplace, we receive an HTTP 503 error when deploying your virtual machine

    "statusCode": "InternalServerError",
    "statusMessage": {
      "error": {
        "code": "InternalBillingError",
        "message": "There was a problem communicating with the billing service. Diagnostic information: timestamp '20190308T202824Z'

I believe this is an issue on MS side of things. However, I wanted you all to be aware of the issue, if you weren't already.

Prisma Cloud IaC Scan - Error occurred during scan

Prisma credentials not configured properly. Please reinstall and complete the configuration.

Deployment validation failed.

Hi All,

I'm getting the following error when trying to deploy

Deployment validation failed.
Additional details from the underlying API that might be helpful: The template deployment 'Microsoft.Template' is not valid according to the validation procedure. The tracking id is '7a8ad30b-1c22-44fb-bcb6-204d43004a20'. See inner errors for details. Please see https://aka.ms/arm-deploy for usage details.

Any ideas?

Thanks in advance,
Chris

Deployment failed

I get this error when trying to deploy:
Deployment to resource group '2-tier-demo-rg' failed.
Additional details from the underlying API that might be helpful: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"Conflict","message":"{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "VMExtensionProvisioningError",\r\n "message": "VM has reported a failure when processing extension 'db-vm-customscript'. Error message: \"Enable failed: failed to execute command: command terminated with exit status=1\n[stdout]\n\n[stderr]\nE: can not open /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial_InRelease - fopen (2: No such file or directory)\nTraceback (most recent call last):\n File \"config_mysql.py\", line 190, in \n main()\n File \"config_mysql.py\", line 36, in main\n if (config_mysql() == 'false'):\n File \"config_mysql.py\", line 64, in config_mysql\n looger.info(\"[ERROR]: apt-get update error\")\nNameError: global name 'looger' is not defined\n\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionCSELinuxTroubleshoot "\r\n }\r\n ]\r\n }\r\n}"}]}

Pre-Existing Network Configuration

Is anyone working on adapting this template to use a pre-existing VNET? Or know of one. Prefer to know prior to adapting this one.

Fix onborading validation

Describe the bug

The validation of the template fails. is based on restrictions

Expected behavior

Should not fail on the validation.

Current behavior

code": "InvalidTemplateDeployment",
"message": "The template deployment failed with error: 'The resource with id: '/subscriptions/d53bdfc8-4709-4943-bb57-f34c53495ea5/resourceGroups/test7/providers/Microsoft.Compute/virtualMachines/pan-fw' failed validation with message: 'The requested size for resource '/subscriptions/d53bdfc8-4709-4943-XXXX-f34cXXXXXX/resourceGroups/test7/providers/Microsoft.Compute/virtualMachines/pan-fw' is currently not available in location 'northcentralus' zones '' for subscription 'd53bdfc8-4709-4943-XXXXX-f34cXXXXXXX'. Please try another size or deploy to a different location or zones. See https://aka.ms/azureskunotavailable for details.'.'."

Possible solution

I changed on the template the size of the web server and dbserver. Looks like that VMs sizes are not available anymore on some regions.
I change the line: "gvmSize": "Standard_B1ls",

Steps to reproduce

Run the template on a PAYG license on different US locations

[Community Health Assessment] Changes needed

This issue was opened by a bot called Community Health (PANW) because this repo has failed too many community health checks.

Repo maintainers: Please take the time to fix the issues in the table to reach the target score. These improvements will help others find your work and contribute to it. This issue will update as your score improves until it hits the target score.

Click More info for instructions to fix each item.

Health Check	Pass	Score	More Info
Contains a meaningful README.md file	✅	20 / 20	More info
SUPPORT.md file exists	❌	0 / 20	More info
Repo has a description	✅	15 / 15	More info
Has a recognized open source license	❌	0 / 15	More info
Has a descriptive repo name	❌	0 / 15	More info
Required topics attached to repo	✅	15 / 15	More info
CONTRIBUTING.md file with contribution guidelines	❌	0 / 5	More info
Has custom issue and pull request templates	❌	0 / 5	More info

Current score: 50
Target threshold: 100
Total possible: 110

Cannot deploy the VM Series on existing vNet

Describe the bug

Hello,

I tried the use this custom template directly on Azure.
I have already the Hub-And-Spokes design on my Azure and I want to add the Palo Alto.
Unfortunately, the deployment fails because it wants to delete the existing vNet and just using it.
I tried with these repos :

• https://github.com/PaloAltoNetworks/azure/tree/master/vmseries-avset
• https://github.com/PaloAltoNetworks/azure/tree/master/vmseries-simple-template

Tried to edit the ARM code but didn't succeed either, it still wants to delete to recreate but not to just use existing vnet.

Expected behavior

Create the Palo Alto VM Series on the existing vNet

Current behavior

The custom template tries to delete the existing vNet

Steps to reproduce

1. Create a vNet with the subnets trust, untrust, mgmt
2. Launch the custom template
3. Add the parameters and specify the already created vNet

Context

Adding a Palo Alto VM series on a existing hub and spokes design on Azure