In standalone mode, the IRF ports are named IRF-port 1 and IRF-port 2.
In IRF mode, the IRF ports are named IRF-port n/1 and IRF-port n/2, where n is the member ID of the
device. The two IRF ports are referred to as IRF-port 1 and IRF-port 2 in this book.
To use an IRF port, you must bind a minimum of one physical interface to it. The physical interfaces
assigned to an IRF port automatically form an aggregate IRF link. An IRF port goes down only if all its IRF
physical interfaces are down.
IRF physical interface
IRF physical interfaces connect IRF member devices and must be bound to an IRF port. They forward
traffic between member devices, including IRF protocol packets and data packets that must travel across
IRF member devices.
For more information about physical interfaces that can be used for IRF links, see
An IRF link failure causes an IRF fabric to split in two IRF fabrics operating with the same Layer 3 settings,
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.
IRF domain ID
One IRF fabric forms one IRF domain. IRF uses IRF domain IDs to uniquely identify IRF fabrics and prevent
IRF fabrics from interfering with one another.
As shown in
and Device D. Both fabrics use the LACP aggregate links between them for MAD. When a member
device receives an extended LACPDU for MAD, it checks the domain ID to see whether the packet is from
the local IRF fabric. Then, the device can handle the packet correctly.
3, IRF fabric 1 contains Device A and Device B, and IRF fabric 2 contains Device C
"IRF physical interface