Verify PCI-ID for Ordering of Network Interfaces on the VM-Series Firewall
Table of Contents
                    
					11.0 (EoL)
						
				
		
  Expand all | Collapse all
  - 
          
                
- VM-Series Deployments
 - VM-Series in High Availability
 - IPv6 Support on Public Cloud
 - 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 Tier and Memory
 - Activate Credits
 - Create a Deployment Profile
 - Activate the 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
 - Deactivate License (Software NGFW Credits)
 - Delicense Ungracefully Terminated Firewalls
 - Set the Number of Licensed vCPUs
 - 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
 
 - Simplified Onboarding of VM-Series Firewall on AWS
 - 
      
            
 - Use AWS Secrets Manager to Store VM-Series Certificates
 - AWS Shared VPC Monitoring
 - Use Case: Secure the EC2 Instances in the AWS Cloud
 - Use Case: Use Dynamic Address Groups to Secure New EC2 Instances within the VPC
 
 - 
          
                
- Intelligent Traffic Offload
 - Software Cut-through Based 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 Azure Key Vault to Store VM-Series Certificates
 - 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 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
 - Verify Bootstrap Completion
 - Bootstrap Errors
 
 
                            End-of-Life (EoL)
                        
                    Verify PCI-ID for Ordering of Network Interfaces on the VM-Series Firewall
Regardless of whether you use a virtual interfaces (Linux/OVS
bridge) or PCI devices (PCI-passthrough or SR-IOV capable adapter)
for connectivity to the VM-Series firewall, the VM-Series firewall
treats the interface as a PCI device. The assignment of an interface
on the VM-Series firewall is based on PCI-ID which is a value that
combines the bus, device or slot, and function of the interface.
The interfaces are ordered starting at the lowest PCI-ID, which
means that the management interface (eth0) of the firewall is assigned
to the interface with the lowest PCI-ID.
Let's say you assign four interfaces to the VM-Series firewall,
three virtual interfaces of type virtio and e1000 and the fourth
is a PCI device. To view the PCI-ID for each interface, enter the
command virsh dumpxml $ domain <name of the VM-Series firewall> on
the Linux host to view the list of interfaces attached to the VM-Series
firewall. In the output, check for the following networking configuration:
<interface type='bridge'> 
      <mac address='52:54:00:d7:91:52'/> 
      <source bridge='mgmt-br'/> 
      <model type='virtio'/> 
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> 
    </interface> 
     
   <interface type='bridge'> 
      <mac address='52:54:00:f4:62:13'/> 
      <source bridge='br8'/> 
      <model type='e1000'/> 
      <address type='pci' domain='0x0000' bus='0x00' slot='0x10' function='0x0'/> 
    </interface> 
     
   <interface type='bridge'> 
      <mac address='52:54:00:fe:8c:80'/> 
      <source bridge='br8'/> 
      <model type='e1000'/> 
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> 
    </interface> 
    
   <hostdev mode='subsystem' type='pci' managed='yes'> 
      <source> 
        <address domain='0x0000' bus='0x08' slot='0x10' function='0x1'/> 
      </source> 
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> 
    </hostdev> In this case, the PCI-ID of each interface is as follows:
- First virtual interface PCI-ID is 00:03:00
 - Second virtual interface PCI-ID is 00:10:00
 - Third virtual interface PCI-ID is 00:06:00
 - Fourth interface PCI-ID is 00:07:00
 
Therefore, on the VM-Series firewall, the interface with PCI-ID
of 00:03:00 is assigned as eth0 (management interface), the interface
with PCI-ID 00:06:00 is assigned as eth1 (ethernet1/1), the interface
with PCI-ID 00:07:00 is eth2 (ethernet1/2) and the interface with
PCI-ID 00:10:00 is eth3 (ethernet1/3).