topic Re: aggregate interface in General Topics

aggregate interface

GnContente — Thu, 20 Jan 2022 11:24:13 GMT

Hi all,

I would like to have the community opinion on two different setups and which one is the recommended by PA, i have looked for documentation about this and i cannot find a straight answer. All i could find was:

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u0000008V36CAE&lang=en_US%E2%80%A9

This document states, if i am interpreting it correctly that i should disable the option "Enable in HA Passive State" has this option from my understading is to be used for AE interfaces between firewalls, and causes issues on downstream AE interfaces.

On my setup I have two firewalls in HA that connect to a downstream switch. What would be the best approach?

To configure a port-channel for each firewall on the downstream switch without having to worry if the "Enable in HA Passive State" is checked or unchecked. If so what would be consequences of this configurations in terms of traffic forwarding since the two port-channels on the switch will be up.

Or is to configure one unique port-channel on the downstream switch and uncheck the "Enable in HA Passive State"?

TIA

Re: aggregate interface

JoergSchuetter — Thu, 20 Jan 2022 12:44:52 GMT

Hello @GnContente

We have the option "Enable in HA Passive State" enabled. Each of the nodes has a dedicated port-channel (per firewall ae) on the switch.

If you share a port-channel with both nodes, then the fail over (measured on how long there is no traffic) will take much longer.

Re: aggregate interface

GnContente — Thu, 20 Jan 2022 13:35:40 GMT

Hi @JoergSchuetter

Thanks for replying, if i have a port-channel for each firewall on the downstream switch, i do not fully grasp why do i need "Enable in HA Passive State"?

TIA

Re: aggregate interface

JoergSchuetter — Thu, 20 Jan 2022 17:29:02 GMT

Hello

This flag ensures that L2 is up all the time.

If that wouldn't be the case, then the node needs to bring up the channel (plus L2). This takes a while (up to a few seconds).

If the port-channel and L2 are kept up (but simply not presenting the relevant MAC), it's just a matter of fraction of a second to have it fully active.