Configure Link Aggregation Control Protocol
Table of Contents
PAN.OS 11.1 & Later
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
-
- Licensing and Prerequisites for Virtual Systems Support on VM-Series
- System Requirements for Virtual Systems Support on VM-Series
- Enable Multiple Virtual Systems Support on VM-Series Firewall
- Enable Multiple Virtual Systems Support on VM-Series in Panorama Console
- Enable Multiple Virtual Systems Support Using Bootstrap Method
-
- 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
-
- 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
- Configure Link Aggregation Control Protocol
-
-
- 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 AWS Secrets Manager to Store VM-Series Certificates
- 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
- Enable Session Resiliency on VM-Series for GCP
-
- 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
Configure Link Aggregation Control Protocol
Configure link aggregation in ESXi and KVM environments.
Link aggregation involves configuring a link aggregation interface group and
configuring the Link Aggregation Control Protocol. An aggregate interface
group uses IEEE 802.1AX link aggregation to combine multiple Ethernet interfaces
into a single virtual interface that connects the firewall to another network device
or firewall. This aggregate group increases bandwidth between peers by
load-balancing traffic across the combined interfaces. It also provides redundancy;
when one interface fails, the remaining interfaces continue supporting traffic.
By default, interface failure detection is automatic only at the physical layer
between directly connected peers. However, if you enable the Link Aggregation
Control Protocol, failure detection is automatic at the physical and data link
layers even if the peers are directly connected. LACP also enables automatic
failover to standby interfaces if you configured hot spares.
To configure an aggregate interface group and LACP, see Configure an Aggregate Interface Group.
Create an Aggregate Ethernet Interface using Panorama
Don't add Panorama VMs associated with virtual functions from the same physical
function to the same Aggregate Ethernet interface. Doing so creates a loop. Create
an Aggregate Ethernet interface:
- Configure an Aggregate Ethernet interface:
- Select Network>Interfaces>Ethernet and Add Aggregate Group.In the field adjacent to the read-only Interface Name, enter a number to identify the aggregate group. The range is 1 to the maximum number of aggregate interface groups supported by the firewall.For the Interface Type, select HA, Virtual Wire, Layer 2, or Layer 3.Configure the remaining parameters for the Interface Type you selected.Commit your changes.After creating the aggregate interface, add links to it.
Add Links to the Aggregate Ethernet Interface
To add links to the Aggregate Ethernet interface:- On Panorama, aggregate an Ethernet interface to act as listener in passive mode for the peer. Select Network > Interface.Select an Ethernet interface to act as a peer.In the Aggregate Ethernet Interface screen, select LACP.Click Enable LACP.Ensure that the mode is Passive.Click OK.Commit your changes in Panorama.Confirm the configuration change. Click Yes.
Create the Aggregate Ethernet Interface Using the CLI
Use the following CLI commands to create an Aggregate Ethernet interface:admin@PA-VM# set network interface aggregate-ethernet ae1 ae1 <value> Aggregate interface name: ae1 - ae16For example,admin@PA-VM# set network interface aggregate-ethernet ae1Associate a Secondary Interface Using the CLI
Use the following CLI commands to associate a secondary interface:admin@PA-VM# set network interface ethernet ethernet1/1 aggregate-group ae1 aggregate-ethernet ae1 <value> Aggregate interface groupFor example,set network interface ethernet ethernet1/1 aggregate-group ae1Display the Interface Configuration Using the CLI
Use the following CLI commands to display the interface configuration:admin@PA-VM> show interface all total configured hardware interfaces: 4 name id speed/duplex/state mac address -------------------------------------------------------------------------------- ethernet1/1 16 10000/full/up ba:db:ee:fb:ad:30 ethernet1/2 17 10000/full/up 52:54:00:ce:8a:f5 ethernet1/3 18 10000/full/up ba:db:ee:fb:ad:30 ae1 48 [n/a]/[n/a]/up ba:db:ee:fb:ad:30 aggregation groups: 1 ae1 members: ethernet1/1 ethernet1/3 total configured logical interfaces: 2 name id vsys zone forwarding tag address ------------------- ----- ---- ---------------- ------------------------ ------ ------------------ ethernet1/2 17 1 trust vr:default 0 192.168.20.196/24 ae1 48 1 untrust vr:default 0 192.168.10.110/24Display the Aggregate Ethernet Interface Configuration Using the CLI
Use the following CLI commands to display the Aggregate Ethernet interface configuration:admin@PA-VM> show interface ae1 -------------------------------------------------------------------------------- Name: ae1, ID: 48 Link status: Runtime link speed/duplex/state: [n/a]/[n/a]/up Configured link speed/duplex/state: auto/auto/auto MAC address: Port MAC address ba:db:ee:fb:ad:30 Aggregate group members: 2 ethernet1/1 ethernet1/3 Operation mode: layer3 Untagged sub-interface support: no -------------------------------------------------------------------------------- Name: ae1, ID: 48 Operation mode: layer3 Virtual router default Interface MTU 1500 Interface IP address: 192.168.10.110/24 Interface management profile: ae-mgmt-profile ping: yes telnet: no ssh: yes http: yes https: yes snmp: no response-pages: no userid-service: no Service configured: Zone: untrust, virtual system: vsys1 Adjust TCP MSS: no Ignore IPv4 DF: no Policing: no -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- Physical port counters read from MAC: -------------------------------------------------------------------------------- rx-broadcast 0 rx-bytes 7874426 rx-multicast 0 rx-unicast 151353 tx-broadcast 0 tx-bytes 9320 tx-multicast 0 tx-unicast 130 -------------------------------------------------------------------------------- Hardware interface counters read from CPU: -------------------------------------------------------------------------------- bytes received 3920 bytes transmitted 7406 packets received 40 packets transmitted 123 receive incoming errors 0 receive discarded 0 receive errors 0 packets dropped 0 -------------------------------------------------------------------------------- Logical interface counters read from CPU: -------------------------------------------------------------------------------- bytes received 7854114 bytes transmitted 7700 packets received 150927 packets transmitted 130 receive errors 0 packets dropped 150614 packets dropped by flow state check 0 forwarding errors 0 no route 0Configure Link Aggregation on the Switch Using the CLI
Activate link aggregation on the switch:int eth1/4 channel-group 1 mode on int eth1/8 channel-group 1 mode onVerify the configuration:show running-config interface Ethernet 1/4 interface Ethernet 1/4 no lldp transmit no lldp receive no switchport Channel-group 1 mode on show running-config interface Ethernet 1/8 interface Ethernet 1/8 no lldp transmit no lldp receive no switchport Channel-group 1 mode on