Deploy the VM-Series Firewall from Google Cloud Platform Marketplace
Table of Contents
9.1 (EoL)
Expand all | Collapse all
-
- VM-Series Deployments
- VM-Series in High Availability
- Enable Jumbo Frames on the VM-Series Firewall
- Hypervisor Assigned MAC Addresses
- Custom PAN-OS Metrics Published for Monitoring
- Interface Used for Accessing External Services on the VM-Series Firewall
- PacketMMAP and DPDK Driver Support
-
- VM-Series Firewall Licensing
- Create a Support Account
- Serial Number and CPU ID Format for the VM-Series Firewall
-
- Activate Credits
- Transfer Credits
- Create a Deployment Profile
- Manage a Deployment Profile
- Provision Panorama
- Migrate Panorama to a Software NGFW License
- Renew Your Software NGFW Credits
- Amend and Extend a Credit Pool
- Deactivate License (Software NGFW Credits)
- Delicense Ungracefully Terminated Firewalls
- Create and Apply a Subscription-Only Auth Code
- Migrate to a Flexible VM-Series License
-
- Generate Your OAuth Client Credentials
- Manage Deployment Profiles Using the Licensing API
- Create a Deployment Profile Using the Licensing API
- Update a Deployment Profile Using the Licensing API
- Get Serial Numbers Associated with an Authcode Using the API
- Deactivate a VM-Series Firewall Using the API
- Use Panorama-Based Software Firewall License Management
- What Happens When Licenses Expire?
- Install a Device Certificate on the VM-Series Firewall
-
- Supported Deployments on VMware vSphere Hypervisor (ESXi)
-
- Plan the Interfaces for the VM-Series for ESXi
- Provision the VM-Series Firewall on an ESXi Server
- Perform Initial Configuration on the VM-Series on ESXi
- Add Additional Disk Space to the VM-Series Firewall
- Use VMware Tools on the VM-Series Firewall on ESXi and vCloud Air
- Use vMotion to Move the VM-Series Firewall Between Hosts
- Use the VM-Series CLI to Swap the Management Interface on ESXi
-
-
- VM-Series Firewall for NSX-V Deployment Checklist
- Install the VMware NSX Plugin
- Apply Security Policies to the VM-Series Firewall
- Steer Traffic from Guests that are not Running VMware Tools
- Add a New Host to Your NSX-V Deployment
- Dynamically Quarantine Infected Guests
- Migrate Operations-Centric Configuration to Security-Centric Configuration
- Use Case: Shared Compute Infrastructure and Shared Security Policies
- Use Case: Shared Security Policies on Dedicated Compute Infrastructure
- Dynamic Address Groups—Information Relay from NSX-V Manager to Panorama
-
- Supported Deployments of the VM-Series Firewall on VMware NSX-T (North-South)
- Components of the VM-Series Firewall on NSX-T (North-South)
-
- Install the Panorama Plugin for VMware NSX
- Enable Communication Between NSX-T Manager and Panorama
- Create Template Stacks and Device Groups on Panorama
- Configure the Service Definition on Panorama
- Deploy the VM-Series Firewall
- Direct Traffic to the VM-Series Firewall
- Apply Security Policy to the VM-Series Firewall on NSX-T
- Use vMotion to Move the VM-Series Firewall Between Hosts
- Extend Security Policy from NSX-V to NSX-T
-
- Components of the VM-Series Firewall on NSX-T (East-West)
- VM-Series Firewall on NSX-T (East-West) Integration
- Supported Deployments of the VM-Series Firewall on VMware NSX-T (East-West)
-
- Install the Panorama Plugin for VMware NSX
- Enable Communication Between NSX-T Manager and Panorama
- Create Template Stacks and Device Groups on Panorama
- Configure the Service Definition on Panorama
- Launch the VM-Series Firewall on NSX-T (East-West)
- Add a Service Chain
- Direct Traffic to the VM-Series Firewall
- Apply Security Policies to the VM-Series Firewall on NSX-T (East-West)
- Use vMotion to Move the VM-Series Firewall Between Hosts
- Extend Security Policy from NSX-V to NSX-T
- Use Migration Coordinator to Move Your VM-Series from NSX-V to NSX-T
-
-
- Deployments Supported on AWS
-
- Planning Worksheet for the VM-Series in the AWS VPC
- Launch the VM-Series Firewall on AWS
- Launch the VM-Series Firewall on AWS Outpost
- Create a Custom Amazon Machine Image (AMI)
- Encrypt EBS Volume for the VM-Series Firewall on AWS
- Use the VM-Series Firewall CLI to Swap the Management Interface
- Enable CloudWatch Monitoring on the VM-Series Firewall
- VM-Series Firewall Startup and Health Logs on AWS
- Use Case: Secure the EC2 Instances in the AWS Cloud
- Use Case: Use Dynamic Address Groups to Secure New EC2 Instances within the VPC
-
-
- What Components Does the VM-Series Auto Scaling Template for AWS (v2.0) Leverage?
- How Does the VM-Series Auto Scaling Template for AWS (v2.0 and v2.1) Enable Dynamic Scaling?
- Plan the VM-Series Auto Scaling Template for AWS (v2.0 and v2.1)
- Customize the Firewall Template Before Launch (v2.0 and v2.1)
- Launch the VM-Series Auto Scaling Template for AWS (v2.0)
- SQS Messaging Between the Application Template and Firewall Template
- Stack Update with VM-Series Auto Scaling Template for AWS (v2.0)
- Modify Administrative Account and Update Stack (v2.0)
-
- Launch the Firewall Template (v2.1)
- Launch the Application Template (v2.1)
- Create a Custom Amazon Machine Image (v2.1)
- VM-Series Auto Scaling Template Cleanup (v2.1)
- SQS Messaging Between the Application Template and Firewall Template (v2.1)
- Stack Update with VM-Series Auto Scaling Template for AWS (v2.1)
- Modify Administrative Account (v2.1)
- Change Scaling Parameters and CloudWatch Metrics (v2.1)
-
-
- Enable the Use of a SCSI Controller
- Verify PCI-ID for Ordering of Network Interfaces on the VM-Series Firewall
-
- Deployments Supported on Azure
- Deploy the VM-Series Firewall from the Azure Marketplace (Solution Template)
- Deploy the VM-Series Firewall from the Azure China Marketplace (Solution Template)
- Deploy the VM-Series Firewall on Azure Stack
- Enable Azure Application Insights on the VM-Series Firewall
- Set up Active/Passive HA on Azure
- Use the ARM Template to Deploy the VM-Series Firewall
-
- About the VM-Series Firewall on Google Cloud Platform
- Supported Deployments on Google Cloud Platform
- Create a Custom VM-Series Firewall Image for Google Cloud Platform
- Prepare to Set Up VM-Series Firewalls on Google Public Cloud
-
- Deploy the VM-Series Firewall from Google Cloud Platform Marketplace
- Management Interface Swap for Google Cloud Platform Load Balancing
- Use the VM-Series Firewall CLI to Swap the Management Interface
- Enable Google Stackdriver Monitoring on the VM Series Firewall
- Enable VM Monitoring to Track VM Changes on GCP
- Use Dynamic Address Groups to Secure Instances Within the VPC
- Locate VM-Series Firewall Images in the GCP Marketplace
-
- Prepare Your ACI Environment for Integration
-
-
- Create a Virtual Router and Security Zone
- Configure the Network Interfaces
- Configure a Static Default Route
- Create Address Objects for the EPGs
- Create Security Policy Rules
- Create a VLAN Pool and Domain
- Configure an Interface Policy for LLDP and LACP for East-West Traffic
- Establish the Connection Between the Firewall and ACI Fabric
- Create a VRF and Bridge Domain
- Create an L4-L7 Device
- Create a Policy-Based Redirect
- Create and Apply a Service Graph Template
-
- Create a VLAN Pool and External Routed Domain
- Configure an Interface Policy for LLDP and LACP for North-South Traffic
- Create an External Routed Network
- Configure Subnets to Advertise to the External Firewall
- Create an Outbound Contract
- Create an Inbound Web Contract
- Apply Outbound and Inbound Contracts to the EPGs
- Create a Virtual Router and Security Zone for North-South Traffic
- Configure the Network Interfaces
- Configure Route Redistribution and OSPF
- Configure NAT for External Connections
-
-
- Choose a Bootstrap Method
- VM-Series Firewall Bootstrap Workflow
- Bootstrap Package
- Bootstrap Configuration Files
- Generate the VM Auth Key on Panorama
- Create the bootstrap.xml File
- Prepare the Licenses for Bootstrapping
- Prepare the Bootstrap Package
- Bootstrap the VM-Series Firewall on AWS
- Bootstrap the VM-Series Firewall on Azure
- Bootstrap the VM-Series Firewall on Google Cloud Platform
- Verify Bootstrap Completion
- Bootstrap Errors
End-of-Life (EoL)
Deploy the VM-Series Firewall from Google Cloud Platform
Marketplace
Use Google® Cloud Platform Marketplace to deploy the
VM-Series firewall with a minimum of three interfaces (Management,
Trust, and Untrust).
You can use Google® Cloud Platform Marketplace to deploy the VM-Series firewall on
a fixed vCPU capacity license (VM-Series Models). The licensed
images available from public clouds are:
See Deploy the VM-Series Firewall from Google Cloud Platform Marketplace for more about
these license options.
The Marketplace deploys an
instance of the VM-Series firewall with a minimum of one management
interface and two dataplane interfaces (Trust and Untrust). You can
add additional dataplane interfaces for up to five Google Compute
Engine instances in your virtual private cloud (VPC).
Before
you deploy the VM-Series firewall, you must create or choose a project
in your organization and create any networks and subnets that will
connect to the firewall, as described in VPC
Network Planning and Network
Interface Planning.
You cannot attach multiple network
interfaces to the same VPC network. Every interface you create must
have a dedicated network with at least one subnet. Ensure that your
networks include any additional dataplane instances you create.
- Locate the VM-Series firewall listing in the Marketplace.
- Log in to the Google Cloud Console.
- From the Products and Services menu, selectMarketplace.
- Search forVM-Series.
- Select one of the VM-Series firewall licensing options.
- ClickLaunch on Compute Engine.
- Name the instance and choose resources.
- Enter theDeployment Name(this name is displayed in the Deployment Manager). The name must be unique and cannot conflict with any other deployment in the project.
- Select aZone. See Regions and Zones for a list of supported zones.
- Select aMachine Typebased on the VM-Series System Requirements for your license and the Minimum System Requirements for the VM-Series Firewall on Google Cloud Platform.
- Specify instance metadata.The optionsBootstrap BucketandInterface Swapaffect the initial configuration the first time the VM-Series firewall boots.
- Bootstrap Bucket(Optional)—If you plan to use a bootstrap file, enter the name of a storage bucket, or the path to a folder within the storage bucket, that contains the bootstrap package. You need permission to access the storage bucket. For example:vmseries-bootstrap-gce-storagebucket=<bucketname>orvmseries-bootstrap-gce-storagebucket=<bucketname/directoryname>
- Interface Swap(Optional)—Swap the Management interface (eth0) and the first dataplane interface (eth1) at deployment time. Interface swap is only necessary when you deploy the VM-Series firewall behind Google Cloud Platform HTTP(S) Load Balancing. For details, see Management Interface Swap for Google Cloud Platform Load Balancing.
- SSH key—Paste in the public key from an SSH key pair. Follow the instructions for your OS in SSH Key Pair, to create, copy, and paste the key. Windows users must view the key in PuTTY, copy from the user interface, and paste into Marketplace deployment.If the key is not formatted properly, the VM-Series firewall does not allow you to log in. You must delete the deployment and start over.
- ClickMoreto reveal additional metadata options. The optionsblockProjectKeys, andenableSerialConsoleare properties of the instance; you can change these metadata values after a successful deployment.
- blockProjectKeys(Optional)—If you Block Project Keys, you can use only the public SSH key you supply to access the instance.
- enableSerialConsole(Optional)—Interacting with the Serial Console enables you to monitor instance creation and perform interactive debugging tasks.
- Specify custom metadata.If you choose to bootstrap with custom metadata, add any key-value pairs that you did not add in Step 5. See init-cfg.txt File Components for the list of key-value pairs. For example:
- Configure the boot disk.
- Boot disk type—Select from SSD Persistent disk or Standard Persistent Disk. See Storage Options.
- Enter theBoot disk size—60GB is the minimum size. You can edit the disk size later but you must stop the VM to do so.
- Configure the management interface.
- Management VPC Network name—Choose an existing network
- Management Subnet name—Choose an existing subnet.
- Enable External IP for Management interface(Optional)—If you enable this option, you can use the IP address assigned to the VM-Series firewall management interface to use SSH to access the VM-Series firewall web interface.
- Enable GCP Firewall rule for connections to Management interface(Optional)—This option automatically creates a GCP firewall Allow rule for an external source IP address that you supply.
- Source IP in GCP Firewall rule for connections to Management Interface—If youEnable GCP Firewall rule for connections to Management interface, enter a source IP address or a CIDR block.
- Do not use 0.0.0.0/0. Supply an IP address or a CIDR block that corresponds to your dedicated management IP addresses or network. Do not make the source network range larger than necessary.
- Verify the address to ensure that you do not lock yourself out.
- Configure the Untrust dataplane interface.
- Untrust VPC Network name—Choose an existing network.
- Untrust Subnet name—Choose an existing subnet.
- Enable External IP for Untrust—Enable GCP to provide an ephemeral IP address to act as the external IP address.
- Configure the Trust dataplane interface.
- Trust VPC Network name—Choose an existing network.
- Trust Subnet name—Choose an existing network.
- Enable External IP for Trust—Enable GCP to provide an ephemeral IP address to act as the external IP address.
- Configure additional interfaces. You must enter the number of dataplane interfaces you want to add; the default is 0 (none). The deployment page always displays fields for five additional dataplanes numbered 4 through 8.
- Additional Dataplane interfaces—Enter the number of additional dataplane instances.If this number is 0 (default), dataplane numbers 4 through 8 are ignored even if you fill out the interface fields. If, for example, you specify 2 and then fill out information for three interfaces, only the first two are created.
- Additional Dataplane # VPC name—Choose an existing network.
- Dataplane # Subnet name—Choose a subnet that exists.
- Enable External IP for dataplane # interface—Enable GCP to provide an ephemeral IP address to act as the external IP address.
- Deploythe instance.
- Use Google Cloud Deployment Manager to view and manage your deployment.
- Use the CLI to change the administrator password on the firewall.
- Log in to the VM-Series firewall from the command line. In your SSH tool, connect to the External IP for the management interface, and specify the path to your private key.Windows users: Use PuTTY to connect to the VM-Series firewall and issue command line instructions. To specify the path to the private key, select. InConnectionSSHAuthPrivate key file for authentication: clickBrowseto select your private key.
- Enter configuration mode:VMfirewall>configure
- Enter the following command:VMfirewall#set mgt-config users admin password
- Enter and confirm a new password for the administrator.
- Commit your new password:VMfirewall#commit
- Return to command mode:VMfirewall#exit
- (Optional) If you used a bootstrap file for interface swap, use the following command to view the interface mapping:VMfirewall>debug show vm-series interfaces all
- Access the VM-Series firewall web interface.
- In a browser, create a secure (https) connection to the IP address for the management interface.If you get a network error, check to see that you have a GCP firewall rule that allows the connection.
- When prompted, enter the username (admin) and the administrator password you specified from the CLI.
- (Optional) If you bootstrapped, then Verify Bootstrap Completion.If you see problems, search the log information on the VM-Series firewall. Chooseand, in the manual search field, enterMonitorSystemdescription contains 'bootstrap'and look for a message in the results that indicates that the bootstrap was successful.
After you log in to the firewall, you can add administrators and create interfaces, zones, NAT rules, and policy rules, just as you would on a physical firewall.