14
Configuration backup
As a best practice, back up the next-startup configuration file on a device before adding the device to
an IRF fabric as a subordinate device.
A subordinate device's next-startup configuration file might be overwritten if the master and the
subordinate use the same file name for their next-startup configuration files. You can use the backup
file to restore the original configuration after removing the subordinate from the IRF fabric.
Setup and configuration task list
To set up an IRF fabric, perform the following tasks:
Tasks at a glance
Remarks
1.
(Required.)
N/A
2.
(Required.)
Assigning a member ID to each IRF member device
Perform this task on each
member device.
3.
(Optional.)
Specifying a priority for each member device
Perform this task on one or
multiple member devices to affect
the master election result.
4.
(Required.)
Connecting IRF physical interfaces
For information about connecting
the crosslink ports, see the user
manual for the enclosure.
5.
(Required.)
Binding physical interfaces to IRF ports
Perform this task on each
member device.
When you complete IRF port
binding and activation on all IRF
member devices, the IRF fabric is
formed.
6.
(Required.)
When you log in to the IRF fabric,
you are placed at the master's
CLI, where you complete
subsequent IRF settings and
configure other features for the
member devices as if they were
one device.
7.
(Optional.)
Configuring a member device description
N/A
8.
(Optional.)
Configuring IRF link load sharing mode
Configuring the global load sharing mode
Configuring a port-specific load sharing mode
N/A
9.
(Optional.)
Configuring IRF bridge MAC persistence
N/A
10.
(Optional.)
Enabling software auto-update for software image
As a best practice, enable
software auto-update to ensure
system software image
synchronization.
11.
(Optional.)
Setting the IRF link down report delay
N/A
12.
(Required.)
MAD mechanisms are
independent of one another. You
can configure multiple MAD
mechanisms for an IRF fabric.
