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

Configuration synchronization mechanism, Master election, IRF multi-active detection

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 11 highlights

Configuration synchronization mechanism IRF uses a strict running-configuration synchronization mechanism so all chassis in an IRF fabric can work as a single node, and after the master fails, other members can operate correctly. In an IRF fabric, all chassis get and run the running configuration of the master. Any configuration you have made is propagated to all members. For more information about configuration management, see Fundamentals Configuration Guide. Master election Master election is held each time the IRF fabric topology changes, for example, when the IRF fabric is established, the master device fails or is removed, the IRF fabric splits, or IRF fabrics merge. Master election does not occur when you add new member device to an IRF fabric or two split IRF fabrics merge. Master election uses the following rules in descending order: 1. Current master, even if a new member has higher priority. When an IRF fabric is being formed, all members consider themselves as the master, and this rule is skipped. 2. Member with higher priority. 3. Member with the longest system uptime. Two members are considered starting up at the same time if the difference between their startup times is equal to or less than 10 minutes. For these members, the next tiebreaker applies. 4. Member with the lowest CPU MAC address. The IRF fabric is formed on election of the master. During an IRF merge, members of the IRF fabric that has failed the master election reboot automatically to rejoin the IRF fabric that wins the election. After a master election, all subordinate members reboot with the configuration on the master. The configuration files of the subordinate members are still retained, but these files do not take effect in the IRF fabric. IRF multi-active detection An IRF link failure causes an IRF fabric to split in two IRF fabrics operating with the same Layer 3 configurations, including the same IP address. To avoid IP address collision and network problems, IRF uses multi-active detection (MAD) mechanisms to detect the presence of multiple identical IRF fabrics, handle collisions, and recover from faults. Multi-active handling procedure The multi-active handling procedure includes detection, collision handling, and failure recovery. Detection The device's MAD implementation detects active IRF fabrics with the same Layer 3 global configuration by extending the LACP, BFD, ARP, or IPv6 ND protocol. 7

  • 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
7
Configuration synchronization mechanism
IRF uses a strict running-configuration synchronization mechanism so all chassis in an IRF fabric can work
as a single node, and after the master fails, other members can operate correctly.
In an IRF fabric, all chassis get and run the running configuration of the master. Any configuration you
have made is propagated to all members.
For more information about configuration management, see
Fundamentals Configuration Guide
.
Master election
Master election is held each time the IRF fabric topology changes, for example, when the IRF fabric is
established, the master device fails or is removed, the IRF fabric splits, or IRF fabrics merge. Master
election does not occur when you add new member device to an IRF fabric or two split IRF fabrics merge.
Master election uses the following rules in descending order:
1.
Current master, even if a new member has higher priority.
When an IRF fabric is being formed, all members consider themselves as the master, and this rule
is skipped.
2.
Member with higher priority.
3.
Member with the longest system uptime.
Two members are considered starting up at the same time if the difference between their startup
times is equal to or less than 10 minutes. For these members, the next tiebreaker applies.
4.
Member with the lowest CPU MAC address.
The IRF fabric is formed on election of the master.
During an IRF merge, members of the IRF fabric that has failed the master election reboot automatically
to rejoin the IRF fabric that wins the election.
After a master election, all subordinate members reboot with the configuration on the master. The
configuration files of the subordinate members are still retained, but these files do not take effect in the
IRF fabric.
IRF multi-active detection
An IRF link failure causes an IRF fabric to split in two IRF fabrics operating with the same Layer 3
configurations, including the same IP address. To avoid IP address collision and network problems, IRF
uses multi-active detection (MAD) mechanisms to detect the presence of multiple identical IRF fabrics,
handle collisions, and recover from faults.
Multi-active handling procedure
The multi-active handling procedure includes detection, collision handling, and failure recovery.
Detection
The device's MAD implementation detects active IRF fabrics with the same Layer 3 global configuration
by extending the LACP, BFD, ARP, or IPv6 ND protocol.