HPE 6127XLG, Irf Configuration Manual

Page: 12 / 56

8
MAD
mechanism
Advantages Disadvantages Application scenario
BFD MAD
•
Detection speed is
fast.
•
No intermediate
device is required.
•
Intermediate
device, if used,
can come from any
vendor.
•
Requires MAD dedicated
physical links and Layer 3
interfaces, which cannot be
used for transmitting user
traffic.
•
If no intermediate device is
used, any two IRF
members must have a BFD
MAD link to each other.
•
If an intermediate device is
used, every IRF member
must have a BFD MAD link
to the intermediate device.
•
No special
requirements for
network scenarios.
•
If no intermediate
device is used, this
mechanism is only
suitable for IRF fabrics
that have a small
number of members
that are geographically
close to one another.
For information about BFD,
see
High Availability
Configuration Guide .
ARP MAD
•
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 .
ND MAD
•
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.
LACP MAD
As shown in Figure 6 , 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 "
Collision handling ."