PacketMMAP and DPDK Driver Support
Table of Contents
                    
  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
 - Enable NUMA Performance Optimization on the VM-Series
 - Enable ZRAM on the VM-Series Firewall
 
 - 
          
                
- VM-Series Firewall Licensing
 - Create a Support Account
 - Serial Number and CPU ID Format for the VM-Series Firewall
 - Use Panorama-Based Software Firewall License Management
 - 
      
            
- Maximum Limits Based on Memory
 - Activate Credits
 - Create a Deployment Profile
 - Manage a Deployment Profile
 - Register the VM-Series Firewall (Software NGFW Credits)
 - Provision Panorama
 - Migrate Panorama to a Software NGFW License
 - Transfer Credits
 - Renew Your Software NGFW Credits
 - Amend and Extend a Credit Pool
 - Deactivate License (Software NGFW Credits)
 - Delicense Ungracefully Terminated Firewalls
 - Set the Number of Licensed vCPUs
 - Create and Apply a Subscription-Only Auth Code
 - Customize Dataplane Cores
 - Migrate a Firewall 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
 
 
 - What Happens When Licenses Expire?
 
 - 
          
                
- 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
 
 
 - 
          
                
- 
      
            
- 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
 
 - 
      
            
- 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)
 - Create Dynamic Address Groups
 - Create Dynamic Address Group Membership Criteria
 - Generate Steering Policy
 - Generate Steering Rules
 
 - Delete a Service Definition from Panorama
 - Migrate from VM-Series on NSX-T Operation to Security Centric Deployment
 - Extend Security Policy from NSX-V to NSX-T
 - Use In-Place Migration 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)
 
 
 - 
      
            
 
 - 
          
                
- Intelligent Traffic Offload
 
 - 
          
                
- 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 with the Azure Gateway Load Balancer
 - Create a Custom VM-Series Image for Azure
 - Deploy the VM-Series Firewall on Azure Stack
 - Deploy the VM-Series Firewall on Azure Stack HCI
 - 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
 - Prepare to Set Up VM-Series Firewalls on Google Public Cloud
 - Create a Custom VM-Series Firewall Image for Google Cloud Platform
 - 
      
            
- 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 Google Cloud Platform (GCP)
 - Use Dynamic Address Groups to Secure Instances Within the VPC
 - Use Custom Templates or the gcloud CLI to Deploy the VM-Series Firewall
 
 
 - 
          
                
- 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 Azure Stack HCI
 - Bootstrap the VM-Series Firewall on Google Cloud Platform
 - Bootstrap the VM-Series Firewall on OCI
 - Verify Bootstrap Completion
 - Bootstrap Errors
 
 
PacketMMAP and DPDK Driver Support
Learn about PacketMMAP and DPDK driver support.
    Single-root input/output virtualization
(SR-IOV) relies on communication between virtual function (VF) drivers
on the VM-Series firewall, and physical function (PF) drivers on
the host (the hypervisor). The host uses PF drivers to talk to its
physical NICs, and the VM-Series firewall uses VF drivers to talk
to the PF drivers.
The following diagram is a simple visualization
of that concept. 
                
            SR-IOV
Why use SR-IOV? SR-IOV is a packet
acceleration technology that allows a virtual machine to directly
access packets from the NIC. In contrast, when using a virtual switch,
the host processes the packets, send the packets through a virtual
switch, and then the virtual machine receives its packets.
In
the Compatibility Matrix, PacketMMAP Driver Versions lists
both the host version and the native driver version on the VM-Series
firewall. For example, i40e on the host, and on the firewall, i40e
(for PCI-passthrough) and i40evf (for SR-IOV). 
For SR-IOV,
let's consider a NIC that uses the i40e PF driver. The host communicates with
the NIC via the i40e driver. The VM-Series firewall can use its
VF driver (i40evf) to directly communicate with the host's PF driver.
This allows VM-Series firewall direct access, which improves packet
processing speed. To ensure compatibility, install a host PF driver
version that is later than the native PF driver version.
PCI-Passthrough
Why does VM-Series firewall
have native PF drivers? As mentioned in Options for Attaching VM-Series
on the Network, when using PCI-passthrough, the NIC is reserved
for the VM-Series firewall, so the host (or other guests on the
host) cannot access the NIC. In a PCI-passthrough configuration,
the VM-Series firewall uses its native PF driver to communicate
directly with the host NIC. 
DPDK
PAN-OS has two packet
processing modes—DPDK (default) and MMAP—and each mode has a corresponding
native driver on the VM-Series firewall. For example, if the firewall
is in DPDK mode, the firewall uses the DPDK i40evf driver version
to communicate with the host's i40e driver (when using SR-IOV).
Alternatively, when the firewall is Packet MMAP, it will use a different
i40evf driver version to communicate with the host's i40e driver. 
You can enable DPDK on the host (the hypervisor),
or on the guest (the VM-Series firewall). Enabling both yields the
best results. 
- Compiling OVS with DPDK is part of enabling DPDK on the host.Refer to Configure OVS and DPDK on the Host.
 - VM-Series DPDK enables the native DPDK driver on the VM-Series firewall, so DPDK does not need to be enabled on the host, but it is recommended for best performance.