HP 6125XLG R2306-HP 6125XLG Blade Switch IRF Configuration Guide - Page 29

ARP MAD, and ND MAD together., mechanism, Advantages, Application scenario

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 29 highlights

• ND MAD LACP MAD handles collisions in a different way than BFD MAD, ARP MAD, and ND MAD. To avoid conflicts, do not use LACP MAD together with any of those mechanisms. However, you can use BFD MAD, ARP MAD, and ND MAD together. Table 1 provides a reference for you to make a MAD mechanism selection decision. Table 1 A comparison of the MAD mechanisms MAD mechanism LACP MAD BFD MAD ARP MAD ND MAD Advantages Disadvantages Application scenario • Detection speed is fast. Requires an intermediate • Requires no MAD-dedicated device that supports physical ports or interfaces. extended LACP for MAD. Link aggregation is used between the IRF fabric and its upstream or downstream device. For information about LACP, see Layer 2-LAN Switching Configuration Guide. • No special requirements for • Requires MAD dedicated network scenarios. physical ports and Layer • If no intermediate 3 interfaces, which device is used, this • Detection speed is fast. cannot be used for transmitting user traffic. • No intermediate device is required. • If no intermediate device is used, the IRF members • Intermediate device, if used, must be fully meshed. can come from any vendor. • If an intermediate device is used, every IRF mechanism is only suitable for IRF fabrics that have a small number of members that are geographically close to one another. member must connect to For information about the intermediate device. BFD, see High Availability Configuration Guide. • No intermediate device is required. Spanning tree-enabled • Detection speed is slower non-link aggregation IPv4 • Intermediate device, if used, can come from any vendor. than BFD MAD and LACP network scenario. MAD. For information about • Requires no MAD dedicated ports. • The spanning tree feature must be enabled. ARP, see Layer 3-IP Services Configuration Guide. • No intermediate device is required. Spanning tree-enabled • Detection speed is slower non-link aggregation IPv6 • • Intermediate device, if used, can come from any vendor. Requires no MAD dedicated ports. • than BFD MAD and LACP MAD. The spanning tree feature must be enabled. network scenario. For information about ND, see Layer 3-IP Services Configuration Guide. 25

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
25
•
ND MAD
LACP MAD handles collisions in a different way than BFD MAD, ARP MAD, and ND MAD. To avoid
conflicts, do not use LACP MAD together with any of those mechanisms. However, you can use BFD MAD,
ARP MAD, and ND MAD together.
Table 1
provides a reference for you to make a MAD mechanism selection decision.
Table 1
A comparison of the MAD mechanisms
MAD
mechanism
Advantages
Disadvantages
Application scenario
LACP MAD
•
Detection speed is fast.
•
Requires no MAD-dedicated
physical ports or interfaces.
Requires an intermediate
device that supports
extended LACP for MAD.
Link aggregation is used
between the IRF fabric
and its upstream or
downstream device.
For information about
LACP, see
Layer 2—LAN
Switching Configuration
Guide
.
BFD MAD
•
Detection speed is fast.
•
No intermediate device is
required.
•
Intermediate device, if used,
can come from any vendor.
•
Requires MAD dedicated
physical ports and Layer
3 interfaces, which
cannot be used for
transmitting user traffic.
•
If no intermediate device
is used, the IRF members
must be fully meshed.
•
If an intermediate device
is used, every IRF
member must connect 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.
•
Requires no 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.
•
Requires no 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
.