R3303-HP HSR6800 Routers IRF Configuration Guide

12
• Assign each member a unique IRF member ID to make sure they can merge. You must reboot the
members to validate the IRF member ID settings.
• Assign the highest member priority to the device you want to use as the master.
• Save any configuration you have made to the startup configuration file before rebooting the IRF
member devices.
Setup and configuration task list
HP recommends the following IRF fabric setup and configuration procedure:
Task Remarks
1. Planning the IRF fabric setup
Required.
2. Preconfiguring IRF member devices in standalone mode:
{ Assigning a member ID to each IRF member device
{ Specifying a priority for each member device
{ Binding physical ports to IRF ports
Required.
3. Saving configuration to the next-startup configuration file
Required.
4. Connecting physical IRF ports
Required.
Make sure that they are
interoperable.
5. Setting the operating mode to IRF mode
Required.
6. Accessing the IRF fabric:
{ Accessing the global active MPU of the IRF fabric
{ Accessing a standby MPU in the IRF fabric
Login to the global active MPU is
required.
From the active MPU, you can log in
to a standby MPU to execute a
limited set of maintenance
commands.
7. Configuring IRF member devices in IRF mode:
{ Assigning an IRF domain ID to the IRF fabric
{ Changing the member ID of a device
{ Changing the priority of a member device
{ Adding physical ports to an IRF port
{ Enabling IRF auto merge
{ Configuring a member device description
{ Configuring IRF bridge MAC persistence
{ Enabling software auto-update for system software image
synchronization
{ Setting the IRF link down report delay
{ Configuring MAD
All these tasks are optional.
If IRF ports have not been configured
when a member device operating in
standalone mode, you must
configure its IRF ports.
CAUTION:
After an IRF fabric is set up, you can
modify the IRF port, member ID, and
member priority settings for a
member device, but must make sure
you fully understand the impact on
the live network. For example, a
member ID change can void
member ID-related settings, a priority
change might cause master
re-election, and a reconfiguration of
IRF port settings or bindings might
cause an IRF split or merge.