
11
MAD
mechanism
Advantages Disadvantages Application scenario
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.
• 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.
• The spanning tree feature
must be enabled.
Spanning tree-enabled
non-link aggregation IPv6
network scenario.
BFD MAD (centralized IRF devices)
BFD MAD can work with or without intermediate devices. Figure 7 shows a typical BFD MAD application
scenario.
To use BFD MAD:
• Set up a dedicated BFD MAD link between each pair of IRF members or between each IRF member
and the intermediate device. Do not use the BFD MAD links for any other purposes.
• Create a Layer 3 aggregate interface for BFD MAD, and assign a MAD IP address to each member
on the aggregate interface.
NOTE:
The MAD addresses identify the member devices and must belong to the same subnet.
• Assign the ports connected by BFD MAD links to the aggregation group for the Layer 3 aggregate
interface.
With BFD MAD, the master tries to establish BFD sessions with other member devices by using its MAD
IP address as the source IP address.
• If the IRF fabric is integrated, only the MAD IP address of the master is effective. The master cannot
establish a BFD session with any other members. If you execute the display bfd session command,
the state of the BFD sessions is Down.
• When the IRF fabric splits, the IP addresses of the masters in the split IRF fabrics take effect. The
masters can establish a BFD session. If you execute the display bfd session command, the state of
the BFD session between the two devices is Up.
Comentários a estes Manuais