Issue with LACP in VirtualWire


Changes to the LIVEcommunity experience are coming soon... Here's what you need to know.

L4 Transporter

Issue with LACP in VirtualWire



Im having an issue upgrading PA. Im starting to think this is a config deployment issue. We have a cluster Active/passive. This FWs are connected to CISCO nexus. Both FWs are in differents datacenter. The FWs are in 8.0.13 and we are trying to upgrade to 8.1.10. The issue is that when we upgrade the passive node to 8.1.10 the VirtualWires (ae interfaces) are not getting up in nexus, we can see the VW OK in FW. And if we failover to the passive node upgraded we lost the service. This is the interface/Vw config:



ethernet1/5 68 1000/full/up 
ethernet1/6 69 1000/full/up 
ethernet1/7 70 10000/full/up 
ethernet1/8 71 10000/full/up 
ethernet1/9 72 1000/full/up 
ethernet1/10 73 1000/full/up 


ae1 16 1 vr:default 0 N/A
ae1.110 128 1 untrust vr:default 110
ae1.111 129 1 untrust vr:default 111
ae1.112 142 1 untrust vr:default 112
ae1.170 133 1 trust vr:default 113
ae2 17 1 vw-in vwire:ae3 0 N/A
ae3 18 1 vw-out vwire:ae2 0 N/A


aggregation groups: 3
ae1 members:
ethernet1/7 ethernet1/8
ae2 members:
ethernet1/9 ethernet1/10
ae3 members:
ethernet1/5 ethernet1/6

Is there any limitation with ae interfaces in Virtualwire Palo Alto?. We can see the interfaces OK in Palo ALto, but in nexus the interfaces are down. 


any idea? 


Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!