You want to upgrade a re-provisioned Mobility Gateway that is currently using LACP.

LACP fallback is specifically designed to preserve connectivity when a device connected to an LACP-enabled LAG is temporarily unable to participate in LACP negotiation. This is particularly relevant to an HPE Aruba Networking Mobility Gateway during provisioning, reprovisioning, or an upgrade cycle, when the Gateway can temporarily operate without its normal LACP configuration.

HPE Aruba Networking ' s validated campus design guidance states that LAGs with LACP Fallback allow an active LACP interface to establish forwarding behavior before receiving LACP protocol data units from its peer. In Gateway deployments, Aruba also recommends enabling LACP fallback on the attached switching infrastructure to accommodate periods during which the Gateway does not yet have its LACP configuration available. Aruba Networks

This eliminates the operational requirement to remove the physical interfaces from the LAG merely to preserve connectivity during the transition. Once the Gateway resumes sending valid LACP PDUs, normal dynamic LAG negotiation and aggregation can resume.

LACP active and passive only determine which participant initiates LACP negotiation. They do not provide forwarding when the peer is temporarily unable to negotiate LACP. A static LAG likewise changes the aggregation method rather than providing transitional LACP behavior.

Study Guide References: Link Aggregation; LACP Operation; LACP Fallback; Gateway Port Channels; VSX MC-LAG; Gateway Provisioning and Reprovisioning.

===============