H3C SR6600 SPE-FWM User manual

H3C SR6600/SR6600-X Routers
Virtual Technologies Configuration Guide(V7)
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: SR6602X-CMW710-R7103
SR6600X-CMW710-R7103-RSE3
SR6600-CMW710-R7103-RPE3
Document version: 20150715-6PW100

Copyright © 2007-2015, Hangzhou H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior
written consent of Hangzhou H3C Technologies Co., Ltd.
Trademarks
H3C, , H3CS, H3CIE, H3CNE, Aolynk, , H3Care, , IRF, NetPilot, Netflow,
SecEngine, SecPath, SecCenter, SecBlade, Comware, ITCMM and HUASAN are trademarks of
Hangzhou H3C Technologies Co., Ltd.
All other trademarks that may be mentioned in this manual are the property of their respective owners
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Preface
The H3C SR6600/SR6600-X documentation set includes 14 configuration guides, which describe the
software features for the H3C SR6600/SR6600-X Routers and guide you through the software
configuration procedures. These configuration guides also provide configuration examples to help you
apply software features to different network scenarios.
The Virtual Technologies Configuration Guide describes how to use devices to create an IRF fabric based
on the IRF technology.
This preface includes:
•Audience
•Conventions
•About the H3C SR6600/SR6600-X documentation set
•Obtaining documentation
•Technical support
•Documentation feedback
Audience
This documentation is intended for:
•Network planners
•Field technical support and servicing engineers
•Network administrators working with the routers
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Descri
p
tion
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars, from
which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select at least one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical

bars, from which you select one choice, multiple choices, or none.
&<1-n> The argument or keyword and argument combination before the ampersand (&) sign can
be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Convention Descri
p
tion
Boldface Window names, button names, field names, and menu items are in Boldface. For
example, the New User window appears; click OK.
> Multi-level menus are separated by angle brackets. For example, File > Create > Folder.
Symbols
Convention Descri
p
tion
WARNING An alert that calls attention to important information that if not understood or followed can
result in personal injury.
CAUTION An alert that calls attention to important information that if not understood or followed can
result in data loss, data corruption, or damage to hardware or software.
IMPORTANT An alert that calls attention to essential information.
NOTE An alert that contains additional or supplementary information.
TIP An alert that provides helpful information.
Network topology icons
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports
Layer 2 forwarding and other Layer 2 features.
Represents an access controller, a unified wired-WLAN module, or the access controller
engine on a unified wired-WLAN switch.
Represents an access point.
Represents a mesh access point.
Represents omnidirectional signals.
Represents directional signals.
Represents a security product, such as a firewall, UTM, multiservice security gateway, or
load balancing device.





Represents a security card, such as a firewall, load balancing, NetStream, SSL VPN, IPS,
or ACG card.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your device.
About the H3C SR6600/SR6600-X documentation
set
The H3C SR6600/SR6600-X documentation set includes:
Cate
g
or
y
Documents Pur
p
oses
Product description and
specifications
Marketing brochures Describe product specifications and benefits.
Technology white papers
Provide an in-depth description of software features
and technologies.
Card datasheets Describe card specifications, features, and
standards.
Hardware specifications
and installation
Compliance and safety
manual
Provides regulatory information and the safety
instructions that must be followed during installation.
Installation guide Provides a complete guide to hardware installation
and hardware specifications.
Card manuals Provide the hardware specifications of cards.
H3C N68 Cabinet
Installation and Remodel
Introduction
Guides you through installing and remodeling H3C
N68 cabinets.
Software configuration
Configuration guides Describe software features and configuration
procedures.
Command references Provide a quick reference to all available
commands.
Operations and
maintenance
H3C SR6602 Release
notes
Provide information about the product release,
including the version history, hardware and software
compatibility matrix, version upgrade information,
technical support information, and software
upgrading.
H3C SR6608 Release
notes
Obtaining documentation
You can access the most up-to-date H3C product documentation on the World Wide Web
at http://www.h3c.com.
Click the links on the top navigation bar to obtain different categories of product documentation:
[Technical Support & Documents > Technical Documents] – Provides hardware installation, software
upgrading, and software feature configuration and maintenance documentation.
[Products & Solutions] – Provides information about products and technologies, as well as solutions.

[Technical Support & Documents > Software Download] – Provides the documentation released with the
software version.
Technical support
servic[email protected]
http://www.h3c.com
Documentation feedback
You can e-mail your comments about product documentation to [e-mail].
We appreciate your comments.

i
Contents
IRF overview ································································································································································· 1
Application scenario·························································································································································1
Network topology ·····························································································································································1
IRF functionality ·································································································································································1
Simplified topology ··················································································································································1
Single point of management ···································································································································2
Node redundancy ····················································································································································2
Link redundancy ·······················································································································································3
Configuration synchronization································································································································3
Basic concepts···································································································································································3
Operating mode·······················································································································································3
IRF member roles ······················································································································································3
IRF member ID···························································································································································3
MPU roles··································································································································································4
IRF port ······································································································································································4
IRF physical interface ···············································································································································4
MAD ··········································································································································································4
IRF domain ID ···························································································································································5
IRF split ······································································································································································5
IRF merge ··································································································································································6
Member priority························································································································································6
Master election··································································································································································6
Multi-active handling procedure······································································································································7
Detection ···································································································································································7
Collision handling ····················································································································································7
Failure recovery ························································································································································7
MAD mechanisms ·····························································································································································8
LACP MAD ································································································································································8
BFD MAD ··································································································································································9
Setting up an IRF fabric ·············································································································································11
Hardware compatibility················································································································································· 11
General restrictions and configuration guidelines······································································································ 11
IRF fabric size ························································································································································ 11
Software requirements ·········································································································································· 11
MPU requirements ················································································································································· 11
IRF physical interface requirements ····················································································································· 11
Connecting IRF ports ············································································································································· 13
Licensing requirements·········································································································································· 13
Configuration backup ··········································································································································· 13
Setup and configuration task list ·································································································································· 13
Planning the IRF fabric setup········································································································································· 14
Preconfiguring IRF member devices in standalone mode ·························································································· 14
Assigning a member ID to each IRF member device························································································· 14
Specifying a priority for each member device··································································································· 15
Binding physical interfaces to IRF ports ·············································································································· 15
Saving configuration to the next-startup configuration file ························································································ 16
Connecting IRF physical interfaces······························································································································· 16
Setting the operating mode to IRF mode ····················································································································· 17

ii
Accessing the IRF fabric ················································································································································ 18
Configuring IRF member devices in IRF mode ············································································································ 18
Assigning an IRF domain ID to the IRF fabric····································································································· 18
Changing the member ID of a device················································································································· 19
Changing the priority of a member device ········································································································ 19
Adding physical interfaces to an IRF port··········································································································· 19
Enabling IRF auto-merge······································································································································· 21
Configuring a member device description ········································································································· 22
Configuring IRF bridge MAC persistence··········································································································· 22
Enabling software auto-update for software image synchronization······························································· 23
Setting the IRF link down report delay ················································································································ 24
Configuring MAD·················································································································································· 24
Recovering an IRF fabric······································································································································· 28
Displaying and maintaining an IRF fabric··················································································································· 29
Configuration examples ················································································································································ 29
LACP MAD-enabled IRF configuration example································································································· 30
BFD MAD-enabled IRF configuration example··································································································· 32
Configuration example for restoring standalone mode ···················································································· 35
Index ···········································································································································································38

1
IRF overview
H3C Intelligent Resilient Framework (IRF) technology combines multiple physical devices into one virtual
system to provide data center class availability and scalability.
IRF virtualizes devices at the same layer into one node. This node is called an IRF fabric.
Application scenario
Figure 1 shows an IRF fabric that has two devices, which appear as a single node to the upper-layer and
lower-layer devices.
Figure 1 IRF application scenario
Network topology
The device only supports daisy-chain topology for IRF fabrics. For information about connecting IRF
member devices, see "Connecting IRF physical interfaces."
IRF functionality
Simplified topology
Devices in an IRF fabric appear as one node. For redundancy and load balancing, a downstream or
upstream device can connect to the IRF fabric through multichassis link aggregation. Together with link
aggregation, IRF creates a loop-free Layer 2 network. The spanning tree feature is not needed among

2
devices in the IRF fabric or on the link aggregations. IRF also simplifies the Layer 3 network topology
because it reduces the number of routing peers.
The network topology does not change when a device is added to or removed from the IRF fabric.
As shown in Figure 2, Device A and Device B form a two-chassis IRF fabric. The fabric has four MPUs (one
active and three standbys), and two times the number of interface cards that a single device provides.
The IRF fabric manages the physical and software resources of Device A and Device B in a centralized
manner.
Figure 2 Two-chassis IRF fabric implementation schematic diagram
Single point of management
An IRF fabric is accessible at a single IP address on the network. You can use this IP address to log in
through any network port to manage all the devices in the fabric.
For an SNMP NMS, an IRF fabric is one managed network node.
Node redundancy
In an IRF fabric, one member works as the master to manage and control the entire IRF fabric. All the
other members process services while backing up the master. When the master fails, all the other
member devices elect a new master from among them to take over without interrupting services.
IRF link
An IRF
fabric is
formed.
Master
(Member ID=1)
Subordinate
(Member ID=2)
Active MPU
Device A
(Member ID=1) Device B
(Member ID=2)
IRF physical
interfaces IRF physical
interfaces
IRF-port 2 IRF-port 1
Network
interfaces
Network
interfaces
IRF
Standby MPU
Active MPU
Standby MPU
IRF’s master MPU
IRF’s standby MPU
IRF’s standby MPU
IRF’s standby MPU

3
Link redundancy
IRF link aggregation
You can use multiple physical links to connect two IRF member devices. IRF automatically aggregates the
physical links for redundancy and load balancing.
The IRF links in an aggregation can be located on different cards.
Multichassis link aggregation
You can use the Ethernet link aggregation feature to aggregate the physical links between an upstream
or downstream device and multiple devices in the IRF fabric.
Configuration synchronization
IRF uses a strict running-configuration synchronization mechanism. In an IRF fabric, all devices obtain
and run the running configuration of the master. Any configuration change is automatically propagated
from the master to the remaining devices. The configuration files of these devices are retained, but the
files do not take effect. The devices use their own startup configuration files only after they are removed
from the IRF fabric.
For more information about configuration management, see Fundamentals Configuration Guide.
Basic concepts
Operating mode
The device operates in one of the following modes:
•Standalone mode—The device cannot form an IRF fabric with other devices.
•IRF mode—The device can form an IRF fabric with other devices.
IRF member roles
IRF uses two member roles: master and standby (called subordinate throughout the documentation).
When devices form an IRF fabric, they elect a master to manage and control the IRF fabric, and all the
other devices back up the master. When the master device fails, the other devices automatically elect a
new master. For more information about master election, see "Master election."
IRF member ID
An IRF fabric uses member IDs to uniquely identify and manage its members. This member ID information
is included as the first part of interface numbers and file paths to uniquely identify interfaces and files in
an IRF fabric. Two devices cannot form an IRF fabric if they use the same member ID. A device cannot join
an IRF fabric if its member ID has been used in the fabric.
For example, after you assign a device with a member ID of 2 to an IRF fabric, the name of interface
GigabitEthernet 3/0/1 changes to GigabitEthernet 2/3/0/1. The file path changes from
slot1#flash:/test.cfg to chassis2#slot1#flash:/test.cfg.

4
By default, the standby MPU of a device is automatically assigned the same ID as the active MPU.
MPU roles
Each IRF member device has one or two MPUs. The following are MPU roles:
Role Descri
p
tion
Master MPU Active MPU of the master device. It is also called the global active MPU. You
configure and manage the entire IRF fabric at the CLI of the global active MPU.
Active MPU
Active MPU on each member device. An active MPU performs the following
operations:
•Manages the local device, including synchronizing configuration with the
local standby MPU, processing protocol packets, and creating and
maintaining route entries.
•Processes IRF-related events, such as master election and topology collection.
Standby MPU
For the master MPU, all other MPUs are standby MPUs, including active MPUs
on subordinate devices.
If a member device has two MPUs, the MPU backing up the local active MPU is
the local standby MPU from the perspective of the member device.
IRF port
An IRF port is a logical interface that connects IRF member devices. Every IRF-capable device has two IRF
ports.
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 nis 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 when 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 "IRF physical interface
requirements."
MAD
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.

5
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 Figure 3, IRF fabric 1 contains Device A and Device B, and IRF fabric 2 contains Device C
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.
Figure 3 A network that contains two IRF domains
IRF split
IRF split occurs when an IRF fabric breaks up into multiple IRF fabrics because of IRF link failures, as
shown in Figure 4. The split IRF fabrics operate with the same IP address. IRF split causes routing and
forwarding problems on the network. To quickly detect a multi-active collision, configure a minimum of
one MAD mechanism (see "Configuring MAD").
Figure 4 IRF split

6
IRF merge
IRF merge occurs when two split IRF fabrics reunite or when two independent IRF fabrics are united, as
shown in Figure 5.
Figure 5 IRF merge
Member priority
Member priority determines the possibility of a member device to be elected the master. A member with
higher priority is more likely to be elected the master.
Master election
Master election occurs each time the IRF fabric topology changes in the following situations:
•The IRF fabric is established.
•The master device fails or is removed.
•The IRF fabric splits.
•Independent IRF fabrics merge.
NOTE:
Master election does not occur when two split IRF fabrics merge.
Master election selects a master in descending order:
1. Current master, even if a new member has higher priority.
When an IRF fabric is being formed, all members consider themselves as the master. This rule is
skipped.
2. Member with higher priority.
3. Member with the longest system uptime.
Two members are considered to start up at the same time if the difference between their startup
times is equal to or less than 10 minutes. For these members, the next tiebreaker applies.
4. Member with the lowest CPU MAC address.
For the setup of a new IRF fabric, the subordinate devices must reboot to complete the setup after the
master election.
For an IRF merge, devices must reboot if they are in the IRF fabric that fails the master election. The reboot
can be performed automatically or manually.

7
Multi-active handling procedure
The multi-active handling procedure includes detection, collision handling, and failure recovery.
Detection
MAD identifies each IRF fabric with a domain ID and an active ID (the member ID of the master). If
multiple active IDs are detected in a domain, MAD determines that an IRF collision or split has occurred.
For more information about the MAD mechanisms and their application scenarios, see "MAD
mechanisms."
Collision handling
MAD mechanisms remove multi-active collisions by setting one IRF fabric to the Detect state and other IRF
fabrics to the Recovery state. The Detect-state IRF fabric is active. The Recovery-state IRF fabric is inactive.
Only members in the Detect-state fabric can continue to forward traffic.
LACP MAD uses the following process to handle a multi-active collision:
1. Compares the number of members in each fabric.
2. Sets the fabric that has the most members to the Detect state, and all other fabrics to the Recovery
state.
3. Compares the member IDs of their masters if all IRF fabrics have the same number of members.
4. Sets the IRF fabric that has the lowest numbered master to the Detect state, and all other fabrics to
the Recovery (disabled) state.
5. Shuts down all physical network ports in the Recovery-state fabrics except for the following ports:
{IRF physical interfaces.
{Ports you have specified with the mad exclude interface command.
In contrast, BFD MAD does not compare the number of members in fabrics. The MAD mechanism uses
the following process to handle a multi-active collision:
6. Sets the IRF fabric that has the lowest numbered master to the Detect state.
7. Sets all other fabrics to the Recovery state.
8. Takes the same action on the network ports in Recovery-state fabrics as LACP MAD.
Failure recovery
To merge two split IRF fabrics, first repair the failed IRF link and remove the IRF link failure.
•If the IRF fabric in Recovery state fails before the failure is recovered, repair the failed IRF fabric and
the failed IRF link.
•If the active IRF fabric fails before the failure is recovered, enable the inactive IRF fabric to take over
the active IRF fabric. Then, recover the MAD failure.

8
MAD mechanisms
IRF provides MAD mechanisms by extending LACP and BFD.
IMPORTANT:
Do not configure both BFD MAD and LACP MAD, because they handle collisions differently.
Table 1 compares the MAD mechanisms and their application scenarios.
Table 1 Comparison of MAD mechanisms
MAD
mechanism Advantages Disadvantages Application scenario
LACP MAD
•Detection speed is fast.
•Does not require
MAD-dedicated physical
links or Layer 3 interfaces.
Requires an intermediate
device that supports
extended LACP for MAD.
Link aggregation is used
between the IRF fabric
and its upstream or
downstream device.
For information about
LACP, see Layer 2—LAN
Switching Configuration
Guide.
BFD MAD
•Detection speed is fast.
•No intermediate device is
required.
•Intermediate device, if used,
can come from any vendor.
•Requires MAD dedicated
physical links and Layer 3
interfaces, which cannot
be used for transmitting
user traffic.
•If no intermediate device
is used, the IRF members
must be fully meshed.
•If an intermediate device
is used, every IRF
member must connect to
the intermediate device.
•No special
requirements for
network scenarios.
•If no intermediate
device is used, this
mechanism is only
suitable for IRF fabrics
that have members
that are
geographically close
to one another.
For information about
BFD, see High
Availability
Configuration Guide.
LACP MAD
As shown in Figure 6, LACP MAD has the following requirements:
•Every IRF member must have a link with an intermediate device.
•All the links form a dynamic link aggregation group.
•The intermediate device must be a device that supports extended LACP for MAD.
The IRF member devices send extended LACPDUs that convey a domain ID and an active ID. The
intermediate device transparently forwards the extended LACPDUs received from one member device to
all the other member devices.
•If the domain IDs and active IDs sent by all the member devices are the same, the IRF fabric is
integrated.

9
•If the extended LACPDUs convey the same domain ID but different active IDs, a split has occurred.
LACP MAD handles this situation as described in "Collision handling."
Figure 6 LACP MAD scenario
BFD MAD
BFD MAD can work with or without intermediate devices. Figure 7 shows a typical BFD MAD application
scenario.
To use BFD MAD:
•Set up dedicated BFD MAD link between each pair of IRF members or between each IRF member
and the intermediate device. Do not use the BFD MAD links for any other purposes.
•Create a Layer 3 aggregate interface for BFD MAD, and assign a MAD IP address to each member
on the aggregate interface.
NOTE:
The MAD addresses identify the member devices and must belong to the same subnet.
•Assign the ports connected by BFD MAD links to the Layer 3 aggregation group.
On the intermediate device (if any), create a VLAN and assign the ports on BFD MAD links to the
VLAN. Do not assign the ports to an aggregate interface.
With BFD MAD, the master tries to establish BFD sessions with other member devices by using its MAD
IP address as the source IP address.
Device
Master Subordinate
IRF
Internet
Customer
premise
network
IRF link
Common traffic path
LACP MAD traffic path
LACP-enabled dynamic
link aggregation
LACP-enabled dynamic
link aggregation

10
•If the IRF fabric is integrated, only the MAD IP address of the master is effective. The master cannot
establish a BFD session with any other member. If you execute the display bfd session command,
the state of the BFD sessions is Down.
•When the IRF fabric splits, the IP addresses of the masters in the split IRF fabrics take effect. The
masters can establish a BFD session. If you execute the display bfd session command, the state of
the BFD session between the two devices is Up.
Figure 7 BFD MAD scenario

11
Setting up an IRF fabric
This chapter guides you through the IRF fabric setup procedure.
Hardware compatibility
An SR6602-X router can form an IRF fabric only with SR6602-X routers. Other H3C SR6600 routers can
form an IRF fabric with devices in the same series.
General restrictions and configuration guidelines
For a successful IRF setup, follow the restrictions and guidelines in this section and the setup procedure
in "Setup and configuration task list."
IRF fabric size
An SR6600 IRF fabric can contain a maximum of two chassis.
Software requirements
All IRF member devices must run the same software image version. Make sure the software auto-update
feature is enabled on all member devices.
MPU requirements
Every IRF member must have a minimum of one MPU.
IRF physical interface requirements
IRF physical interface location
On SR6602-X routers, use the following ports for IRF links:
•SR6602-X1—The four fixed GE ports.
•SR6602-X2—The four fixed GE ports and the two fixed 10-GE ports.
On SR6604, SR6608, SR6616, SR6604-X, SR6608-X, or SR6616-X routers, follow these guidelines when
you select IRF physical interfaces:
•You can use physical interfaces from a maximum of two modules in Table 2 for IRF links on a
member device.
Table 2 Candidate IRF physical interfaces
Module Candidate IRF
p
h
y
sical interfaces
SR6604/SR6608/SR6616:

12
Module Candidate IRF
p
h
y
sical interfaces
FIP-240 The two GE ports.
FIP-300 The 12 GE ports.
FIP-310 The four GE ports and the two 10GBASE-R/W ports.
SAP-20GE2XP The four GE ports with the highest port numbers and the two SFP+ fiber
ports.
SAP-28GE The 12 GE ports with the highest port numbers.
SR6604-X/SR6608-X/SR6616-X:
SAP-4EXP The four 10GBASE-R/W ports.
SAP-8EXP The four 10GBASE-R/W ports with the lowest port numbers and the four
10GBASE-R ports with the highest port numbers.
SAP-16EXP The four 10GBASE-R/W ports with the lowest port numbers and the 12
10GBASE-R ports with the highest port numbers.
SAP-2QGP The two 40-GE QSFP+ ports.
FIP-240 The two GE ports.
FIP-300 The 12 GE ports.
FIP-310 The four GE ports and the two 10GBASE-R/W ports.
SAP-20GE2XP The four GE ports with the highest port numbers and the two
10GBASE-R/W ports.
SAP-28GE The 12 GE ports with the highest port numbers.
•Make sure an IRF port and the IRF ports at two ends of IRF connections contain physical interfaces
from the same category of modules. The modules are categorized into high-speed modules and
low-speed modules.
{High-speed modules—SAP-4EXP, SAP-8EXP, SAP-16EXP, and SAP-2QGP.
{Low-speed modules—FIP-240, FIP-300, FIP-310, SAP-28GE, and SAP-20GE2XP.
•If the device contains a FIP-600 module, you can use only the physical interfaces on the following
modules for IRF links:
{SAP-4EXP.
{SAP-8EXP.
{SAP-16EXP.
{SAP-2QGP.
Selecting transceiver modules and cables
When you select transceiver modules and cables, follow these restrictions and guidelines:
•Use straight-through or crossover copper Ethernet cables to connect copper Ethernet ports for a
short-distance connection.
•Use transceiver modules and fibers to connect fiber Ethernet ports for a long-distance connection.
•Make sure the transceiver modules at the two ends of an IRF link are the same type. For more
information about transceiver modules, see the device installation guide.