HPE FlexFabric 5700 Series Configuration Manual page 12

MAD
mechanism
ARP MAD
ND MAD
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 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
Advantages
•
No intermediate device is
required.
•
Intermediate device, if
used, can come from any
vendor.
•
Does not require MAD
dedicated ports.
•
No intermediate device is
required.
•
Intermediate device, if
used, can come from any
vendor.
•
Does not require MAD
dedicated ports.
Figure 5, LACP MAD has the following requirements:
Disadvantages
a BFD MAD link to the
intermediate device.
•
Detection speed is
slower than BFD MAD
and LACP MAD.
•
The spanning tree
feature must be
enabled if common
Ethernet ports are used
for ARP MAD links.
•
Detection speed is
slower than BFD MAD
and LACP MAD.
•
The spanning tree
feature must be
enabled.
"Collision
8
Application scenario
BFD, see High
Availability Configuration
Guide.
If common Ethernet ports
are used, this MAD
mechanism is applicable
only to the spanning
tree-enabled non-link
aggregation IPv4
network scenario.
For information about
ARP, see Layer 3—IP
Services Configuration
Guide.
Spanning tree-enabled
non-link aggregation
IPv6 network scenario.
handling."