Irf Virtual Device Management And Maintenance - 3Com Switch 4800G 24-Port Configuration Manual

the rules below, in the order specified. If the first rule does not apply, a second rule is tried, and so on,
until the only winner is found.
The current master, even if a new member has a higher priority. (When an IRF virtual device is
being formed, and all member devices consider themselves as the master, so this principle is
skipped)
A member with a higher priority.
A member with the longest system up-time. (The system up-time information of each member
device is delivered through IRF hello packets)
A member with the lowest bridge MAC address.
Then, the IRF virtual device is formed and enters the next stage: IRF virtual device management and
maintenance.
The precision of the system up-time is six minutes. For example, if two devices with the same
priority values reboot one after another within six minutes, they will have the same system up-time
and the last role election principle will be followed, that is, the one with the lowest bridge MAC
address wins.
During an IRF virtual device merge, an IRF election is held, and role election rules are followed.
Members of the loser side reboot and join the winner side as slaves. Whether the device reboots
automatically or reboots with the execution of a command depends on the device model.
To ensure the same configuration as that on the master, a device uses the master's configuration
to initialize and boot itself as long as it is elected as a slave, regardless of its original configuration
or whether its current configuration is saved.

IRF Virtual Device Management and Maintenance

After role election, an IRF virtual device is established: all member devices operate as one virtual
device, and all resources on the member devices are processed by this virtual device and managed by
the master.
Member ID
An IRF virtual device uses member IDs to uniquely identify and manage its members. For example,
when the device operates independently, the slot number in the interface number is typically 1; after it
joins an IRF virtual device, the slot number will become the member ID. In addition, member IDs are
used in file management. Therefore, member IDs in an IRF virtual device must be unique.
If member IDs are not unique, an IRF virtual device cannot be established. A member having the same
member ID as an existing one cannot join the IRF virtual device. To ensure the uniqueness of member
IDs, use the following two methods:
1) Before establishing an IRF virtual device, plan and configure member IDs for members. Adopt the
member ID collision processing mechanism, which is described as follows:
During the establishment of an IRF virtual device, when two devices that form the IRF virtual
device have duplicated member IDs, the master is numbered the first. Then, for a daisy chain
1-9