21Default command level3: Manage levelUsage guidelinesLACP MAD uses extended LACP packets for detecting multi-active collisions and requires an intermediateH3C device that also supports LACP MAD packets.When you use LACP MAD, follow these guidelines:• The intermediate device must be an H3C device that support extended LACP for MAD.• If one IRF fabric uses another IRF fabric as the intermediate device for LACP MAD, you must assignthe two IRF fabrics different domain IDs for correct split detection. False detection causes IRF split.• Use dynamic link aggregation mode. MAD is LACP dependent. Even though LACP MAD can beconfigured on both static and dynamic aggregate interfaces, it takes effect only on dynamicaggregate interfaces.• Configure link aggregation settings also on the intermediate device.Examples# Enable LACP MAD on Bridge-Aggregation 1, a Layer 2 dynamic aggregate interface. system-view[Sysname] interface bridge-aggregation 1[Sysname-Bridge-Aggregation1] mad enable# Enable LACP MAD on Route-Aggregation 1, a Layer 3 dynamic aggregate interface. system-view[Sysname] interface route-aggregation 1[Sysname-Route-Aggregation1] mad enablemad exclude interfaceUse mad exclude interface to exclude a physical network port from being shut down when the IRF fabrictransitions to the Recovery state upon detection of a multi-active collision.Use undo mad exclude interface to restore the default MAD action on a physical network port.Syntaxmad exclude interface interface-type interface-numberundo mad exclude interface interface-type interface-numberDefaultAll physical network ports but the IRF physical ports shut down when the IRF fabric transitions to theRecovery state.ViewsSystem viewDefault command level3: Manage levelParametersinterface-type interface-number: Specifies a port by its type and number.