Lacp Mad - HP FlexFabric 12900 Series Configuration Manual

For a comparison of the MAD mechanisms, see
Collision handling
When MAD detects a multi-active collision, it allows one IRF fabric to forward traffic and sets all the other
IRF fabrics to the Recovery state. The Recovery-state IRF fabrics are inactive and cannot forward traffic.
LACP MAD uses the following process to handle a multi-active collision:
1. Compares the number of members in each fabric.
2. Allows the fabric that has the most members to forward traffic, and sets all other fabrics to the
Recovery state.
3. Compares the member IDs of their masters if all IRF fabrics have the same number of members.
4. Allows the IRF fabric that has the lowest numbered master to forward traffic, and sets all other
fabrics to the Recovery (inactive) state.
5. Shuts down all physical network ports in the Recovery-state fabrics except for the following ports:
IRF physical interfaces.
Ports you have specified with the mad exclude interface command.
In contrast, BFD MAD does not compare the number of members in fabrics. BFD MAD uses the following
process to handle a multi-active collision:
1. Allows the IRF fabric that has the lowest numbered master to forward traffic.
2. Sets all other fabrics to the Recovery state.
3. Takes the same action on the network ports in Recovery-state fabrics as LACP MAD.
Failure recovery
To merge two split IRF fabrics, first repair the failed IRF link and remove the IRF link failure.
If the IRF fabric in Recovery state fails before the failure is recovered, repair the failed IRF fabric and
•
the failed IRF link.
If the active IRF fabric fails before the failure is recovered, enable the inactive IRF fabric to take over
•
the active IRF fabric. Then, recover the MAD failure.

LACP MAD

As shown in
Every IRF member must have a link with an intermediate device.
•
All the links form a dynamic link aggregation group.
•
The intermediate device must be an HP device that supports extended LACP for MAD.
•
The IRF member devices send extended LACPDUs with a domain ID and an active ID. The intermediate
device transparently forwards the extended LACPDUs received from one member device to all the other
member devices.
If the domain IDs and the active IDs in the extended LACPDUs sent by all the member devices are
•
the same, the IRF fabric is integrated.
If the extended LACPDUs convey the same domain ID but different active IDs, a split has occurred.
•
LACP MAD handles this situation as described in
Figure 6, LACP MAD has the following requirements:
"Configuring MAD."
"Collision handling."
10