H3C MSR 5600 User manual

H3C MSR 5600 Routers
Comware 7 Virtual Technologies
Configuration Guide
New H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: MSR-CMW710-R0809
Document version: 6W400-20200823

Copyright © 2020, New 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 New H3C Technologies Co., Ltd.
Trademarks
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this
document are the property of their respective owners.
Notice
The information in this document is subject to change without notice. All contents in this document, including
statements, information, and recommendations, are believed to be accurate, but they are presented without
warranty of any kind, express or implied. H3C shall not be liable for technical or editorial errors or omissions
contained herein.

Preface
This configuration guide describes the IRF features.
This preface includes the following topics about the documentation:
•
Audience.
•
Conventions.
•
Documentation feedback.
Audience
This documentation is intended for:
•
Network planners.
•
Field technical support and servicing engineers.
•
Network administrators.
Conventions
The following information describes the conventions used in the documentation.
Command conventions
Convention
Description
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 a minimum of 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
Description
Boldface Window names, button names, field names, and menu items are in Boldface. For
example, the New User window opens; click OK.
> Multi-level menus are separated by angle brackets. For example, File > Create >
Folder.

Symbols
Convention
Description
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
Convention
Description
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 wireless terminator unit.
Represents a wireless terminator.
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 module, such as a firewall, load balancing, NetStream, SSL
VPN, IPS, or ACG module.
Examples provided in this document
Examples in this document might use devices that differ from your device in hardware model,
configuration, or software version. It is normal that the port numbers, sample output, screenshots,
and other information in the examples differ from what you have on your device.
T
T
T
T

Documentation feedback
You can e-mail your comments about product documentation to inf[email protected].
We appreciate your comments.

i
Contents
Configuring an IRF fabric···············································································1
About IRF···························································································································································1
IRF network model·····································································································································1
IRF benefits················································································································································2
Basic concepts···········································································································································3
IRF network topology·································································································································5
Master election···········································································································································5
Interface naming conventions····················································································································6
File system naming conventions················································································································6
Configuration synchronization····················································································································7
Multi-active handling procedure·················································································································7
MAD mechanisms······································································································································9
Restrictions and guidelines: IRF configuration·································································································12
Hardware compatibility with IRF···············································································································12
Software requirements for IRF·················································································································12
IRF fabric size··········································································································································12
Candidate IRF physical interfaces ···········································································································12
Transceiver modules and cables selection for IRF··················································································13
IRF port connection··································································································································13
IRF physical interface configuration restrictions and guidelines ······························································13
Feature compatibility and configuration restrictions with IRF···································································14
Licensing requirements for IRF················································································································14
Configuration rollback restrictions············································································································14
IRF tasks at a glance·······································································································································15
Planning the IRF fabric setup···························································································································16
Setting up an IRF fabric ···································································································································16
Assigning a member ID to each IRF member device···············································································16
Specifying a priority for each member device··························································································16
Binding physical interfaces to IRF ports···································································································17
Saving configuration to the next-startup configuration file ·······································································17
Connecting IRF physical interfaces··········································································································17
Setting the operating mode to IRF mode·································································································17
Accessing the IRF fabric··························································································································18
Configuring MAD··············································································································································19
Restrictions and guidelines for MAD configuration ··················································································19
Configuring LACP MAD ···························································································································19
Configuring BFD MAD······························································································································20
Excluding interfaces from the shutdown action upon detection of multi-active collision··························24
Recovering an IRF fabric ·························································································································24
Optimizing IRF settings for an IRF fabric·········································································································25
Changing the member ID of a member device ························································································25
Changing the priority of a member device ·······························································································25
Adding physical interfaces to an IRF port ································································································26
Bulk-configuring basic IRF settings for a member device········································································27
Enabling IRF auto-merge·························································································································28
Configuring a member device description································································································28
Configuring the IRF bridge MAC address································································································28
Enabling software auto-update for software image synchronization························································29
Setting the IRF link down report delay·····································································································30
Removing an expansion interface card that has IRF physical interfaces·················································30
Replacing an expansion interface card that has IRF physical interfaces·················································31
Display and maintenance commands for IRF··································································································31
IRF configuration examples ·····························································································································31
Example: Configuring an LACP MAD-enabled two-chassis IRF fabric····················································31
Example: Configuring a BFD MAD-enabled two-chassis IRF fabric························································34
Example: Restoring standalone mode·····································································································37

ii

1
Configuring an IRF fabric
About IRF
The Intelligent Resilient Framework (IRF) technology virtualizes multiple physical devices at the
same layer into one virtual fabric to provide data center class availability and scalability. IRF
virtualization technology offers processing power, interaction, unified management, and
uninterrupted maintenance of multiple devices.
IRF network model
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
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.
IP network
IRF fabric
IP network
IRF link Simplified to
Master Subordinate

2
Figure 2 Two-chassis IRF fabric implementation schematic diagram
IRF benefits
IRF provides the following benefits:
•
Simplified topology and easy management—An IRF fabric appears as one node and is
accessible at a single IP address on the network. You can use this IP address to log in at any
member device to manage all the members of the IRF fabric. In addition, you do not need to run
the spanning tree feature among the IRF members.
•
1:N redundancy—In an IRF fabric, one member acts 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 aggregation—You can assign several physical links between neighboring members
to their IRF ports to create a load-balanced aggregate IRF connection with redundancy.
•
Multichassis link aggregation—You can use the Ethernet link aggregation feature to
aggregate the physical links between the IRF fabric and its upstream or downstream devices
across the IRF members.
•
Network scalability and resiliency—Processing capacity of an IRF fabric equals the total
processing capacities of all the members. You can increase ports, network bandwidth, and
processing capacity of an IRF fabric simply by adding member devices without changing the
network topology.
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
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. Adevice cannot join an IRF fabric if its member ID has been used in the fabric.
MPU roles
Each IRF member device has one or two MPUs. The following are MPU roles:
Role Description
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
tasks:
•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.
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.
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.