8
MAD
mechanism
Advantages Disadvantages
Application
scenario
to each other.
•
If an intermediate
device is used, every
IRF member must have
a BFD MAD link to the
intermediate device.
geographically
close to one
another.
For information about
BFD, see
High
Availability Configuration
Guide
.
•
No intermediate device is
required.
•
Intermediate device, if
used, can come from any
vendor.
•
Does not require MAD
dedicated ports.
•
Detection speed is
slower than BFD MAD
and LACP MAD.
•
The spanning tree
feature must be
enabled.
Spanning tree-enabled
non-link aggregation
IPv4 network scenario.
For information about
ARP, see
Layer 3—IP
Services Configuration
Guide
.
•
No intermediate device is
required.
•
Intermediate device, if
used, can come from any
vendor.
•
Does not require MAD
dedicated ports.
•
Detection speed is
slower than BFD MAD
and LACP MAD.
•
The spanning tree
feature must be
enabled.
Spanning tree-enabled
non-link aggregation
IPv6 network scenario.
For information about
ND, see
Layer 3—IP
Services Configuration
Guide
.
LACP MAD
As shown in
, LACP MAD has the following requirements:
•
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 a device that supports extended LACP for MAD.
The IRF member devices send extended LACPDUs that convey 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 active IDs 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 "
