4forwarding problems on the network. To quickly detect a multi-active collision, configure at least oneMAD mechanisms (see "IRF multi-active detection").Figure 3 IRF splitIRF mergeIRF merge occurs when two split IRF fabrics reunite or when you configure and connect two independentIRF fabrics to be one IRF fabric, as shown in Figure 4.Figure 4 IRF mergeMember priorityMember priority determines the possibility of a member device to be elected the master. A member withhigher priority is more likely to be elected the master.The default member priority is 1. You can change the member priority of a member device to affect themaster election result.Interface naming conventionsAn interface is named in the format of chassis-id/slot-number/port-index, where:• slot-number—Represents the slot number of the interface card. This argument takes 0 for the fixedports on the front panel, and takes 1 and 2 for the two interface cards (from left to right) on the rearpanel.• port-index—Port index depends on the number of ports available on the switch. To identify theindex of a port, look at its port index mark on the chassis.For one example, on the standalone switch Sysname, GigabitEthernet 1/0/1 represents the first fixedport on the front panel. Set its link type to trunk, as follows: system-view[Sysname] interface gigabitethernet 1/0/1[Sysname-GigabitEthernet1/0/1] port link-type trunkFor another example, on the IRF fabric Master, GigabitEthernet 3/0/1 represents the first fixed port onthe front panel of member switch 3. Set its link type to trunk, as follows: system-viewIRF linkDevice A Device BDevice A Device BIRF 1 IRF 2 IRF+ =