H3C MSR 5600 Configuration Manual
Comware 7 virtual technologies
Hide thumbs
Also See for MSR 5600:
- Comware 7 vxlan command reference (45 pages) ,
- Preparing for installation (8 pages) ,
- Command reference manual (8 pages)
Subscribe to Our Youtube Channel
Related Manuals for H3C MSR 5600
Summary of Contents for H3C MSR 5600
- Page 1 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...
- Page 2 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.
- Page 3 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. •...
- Page 4 Symbols Convention Description An alert that calls attention to important information that if not understood or followed WARNING! can result in personal injury. An alert that calls attention to important information that if not understood or followed CAUTION: can result in data loss, data corruption, or damage to hardware or software. An alert that calls attention to essential information.
- Page 5 Documentation feedback You can e-mail your comments about product documentation to info@h3c.com. We appreciate your comments.
-
Page 6: Table Of Contents
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 ····················································································································... -
Page 8: Configuring An Irf Fabric
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. -
Page 9: Irf Benefits
Figure 2 Two-chassis IRF fabric implementation schematic diagram Device A Device B (Member ID=1) (Member ID=2) Active MPU Active MPU Standby MPU Standby MPU IRF-port 2 IRF-port 1 IRF link Network IRF physical IRF physical Network interfaces interfaces interfaces interfaces An IRF fabric is formed. -
Page 10: Basic Concepts
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). - Page 11 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.
-
Page 12: Irf Network Topology
Figure 5 A network that contains two IRF domains Core network IRF fabric 1 (domain 10) Device A Device B IRF link IRF fabric 2 Device D Device C (domain 20) IRF link Access network IRF network topology An IRF fabric can use a daisy-chain topology, as shown in Figure IMPORTANT: No relay devices are allowed between IRF member devices. -
Page 13: Interface Naming Conventions
• The IRF fabric splits. • Independent IRF fabrics merge. NOTE: Master election does not occur when split IRF fabrics merge. For information about the master device of the merged IRF fabric, see "Failure recovery." Master election selects a master in descending order: Current master, even if a new member has higher priority. -
Page 14: Configuration Synchronization
For example: • To create and access the test folder under the root directory of the flash memory on the global active MPU: <Master> mkdir test Creating directory flash:/test... Done. <Master> cd test <Master> dir Directory of flash:/test The directory is empty. 524288 KB total (29832 KB free) •... - Page 15 Collision handling When MAD detects a multi-active collision, it sets all IRF fabrics except one to the Recovery state. The fabric that is not placed in Recovery state can continue to forward traffic. The Recovery-state IRF fabrics are inactive and cannot forward traffic. LACP MAD and BFD MAD use the following process to handle a multi-active collision: Compare the number of members in each fabric.
-
Page 16: Mad Mechanisms
Figure 8 Active IRF fabric fails before the IRF link is recovered IP network IP network IRF fabric 2 IRF fabric 2 (Recovery) (Recovery) Execute the mad fabric 1 IRF fabric 1 restore command (Active) IRF fabric 1 fails on IRF fabric 2 fails before because of physical... - Page 17 Application Advantages Disadvantages mechanism scenarios that are geographically close to one another. LACP MAD As shown in Figure 9, 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. •...
- Page 18 You can use common or management Ethernet ports for BFD MAD. If management Ethernet ports are used, BFD MAD has the following requirements: • An intermediate device is required and each IRF member device must have a BFD MAD link to the intermediate device.
-
Page 19: Restrictions And Guidelines: Irf Configuration
Figure 10 BFD MAD scenario with an intermediate device Device BFD MAD link IRF fabric BFD MAD link 192.168.1.2/24 192.168.1.3/24 IRF link Subordinate Master Figure 11 BFD MAD scenario without an intermediate device IRF fabric BFD MAD link VLAN 2 VLAN 2 192.168.1.2/24 192.168.1.3/24... -
Page 20: Transceiver Modules And Cables Selection For Irf
H3C Transceiver Modules User Guide. NOTE: The transceiver modules and DAC cables available for the switch are subject to change over time. For the most up-to-date list of transceiver modules and DAC cables, contact your H3C sales representative. IRF port connection When you connect two neighboring IRF members, follow these restrictions and guidelines: •... -
Page 21: Feature Compatibility And Configuration Restrictions With Irf
For more information about these commands, see Ethernet interface configuration in Interface Command Reference. Suppressing SNMP notifications of packet drops on IRF physical interfaces Before an IRF member device forwards a packet, it examines its forwarding path in the IRF fabric for a loop. -
Page 22: Irf Tasks At A Glance
• Member device description (set by using the command). irf member description • Member device priority (set by using the command). irf member priority • IRF physical interface and IRF port bindings (set by using the port group interface command). For more information about the configuration rollback feature, see configuration file management in Fundamentals Configuration Guide. -
Page 23: Planning The Irf Fabric Setup
Planning the IRF fabric setup Consider the following items when you plan an IRF fabric: • Hardware compatibility and restrictions. • IRF fabric size. • Master device. • Member ID and priority assignment scheme. • Fabric topology and cabling scheme. •... -
Page 24: Binding Physical Interfaces To Irf Ports
Binding physical interfaces to IRF ports About this task In standalone mode, IRF port binding operations do not affect the current configuration of the interface. However, when the operating mode changes to IRF mode, the default configuration is restored on the physical interface. Restrictions and guidelines Make sure the IRF physical interfaces of an IRF port use the same binding mode. -
Page 25: Accessing The Irf Fabric
During the reboot, you may choose to have the system automatically convert the startup configuration file. Automatic configuration conversion prevents slot- or interface-related settings from becoming invalid. For example, the system adds member ID information to interface numbers and file paths in IRF mode. Restrictions and guidelines Upon an operating mode change, the system automatically converts interface names by adding or deleting the first number segment (the member ID) in the interface number. -
Page 26: Configuring Mad
Configuring MAD Restrictions and guidelines for MAD configuration Assigning IRF domain IDs An IRF fabric has only one IRF domain ID. You can change the IRF domain ID by using the command. The IRF irf domain mad enable domain IDs configured by using the commands overwrite each other. If LACP MAD runs between two IRF fabrics, assign each fabric a unique IRF domain ID. -
Page 27: Configuring Bfd Mad
interface range name name [ interface { interface-type interface-number [ to interface-type interface-number ] } &<1-24> ] To assign a range of ports to the aggregation group, enter interface range view. To assign one port to the aggregation group, enter Ethernet interface view. Assign the Ethernet port or the range of Ethernet ports to the specified aggregation group. - Page 28 Category Restrictions and guidelines • Make sure the Layer 3 aggregate interface operates in static aggregation mode. • Make sure the member ports in the aggregation group do not exceed the BFD MAD-enabled Layer 3 maximum number of Selected ports allowed for an aggregation group. If aggregate interface the number of member ports exceeds the maximum number of Selected ports, some member ports cannot become Selected.
- Page 29 (Optional.) Assign a domain ID to the IRF fabric. irf domain domain-id By default, the domain ID of an IRF fabric is 0. Create a VLAN dedicated to BFD MAD. vlan vlan-id By default, only VLAN 1 exists. Return to system view. quit Enter Ethernet interface view or interface range view.
- Page 30 Create a Layer 3 aggregate interface for BFD MAD. interface route-aggregation interface-number Return to system view. quit Enter interface view or interface range view. Enter Ethernet interface view. interface interface-type interface-number Enter interface range view. Choose one of the following commands: ...
-
Page 31: Excluding Interfaces From The Shutdown Action Upon Detection Of Multi-Active Collision
By default, no MAD IP addresses are configured. Excluding interfaces from the shutdown action upon detection of multi-active collision About this task When an IRF fabric transits to the Recovery state, the system automatically excludes the following network interfaces from being shut down: •... -
Page 32: Optimizing Irf Settings For An Irf Fabric
Optimizing IRF settings for an IRF fabric Changing the member ID of a member device Restrictions and guidelines CAUTION: In IRF mode, an IRF member ID change can invalidate member ID-related settings and cause data loss. Make sure you fully understand its impact on your live network. The new member ID takes effect at reboot. -
Page 33: Adding Physical Interfaces To An Irf Port
Adding physical interfaces to an IRF port Restrictions and guidelines Make sure the IRF physical interfaces of an IRF port use the same binding mode. In IRF mode, IRF physical interfaces of an IRF port cannot be configured to use different binding modes. Procedure Enter system view. -
Page 34: Bulk-Configuring Basic Irf Settings For A Member Device
10. Return to system view. quit 11. Save the running configuration. save Activating IRF port settings causes IRF merge and reboot. To avoid data loss, save the running configuration to the startup configuration file before you perform the operation. 12. Activate the configuration on the IRF port. irf-port-configuration active After this step is performed, the state of the IRF port changes to UP. -
Page 35: Enabling Irf Auto-Merge
Enabling IRF auto-merge About this task When two IRF fabrics merge, you must reboot the member devices in the IRF fabric that fails in the master election. The auto-merge feature enables the IRF fabric to automatically reboot all its member devices to complete the merge. If this feature is disabled, you must manually reboot the devices that failed the master election to complete the merge. -
Page 36: Enabling Software Auto-Update For Software Image Synchronization
Configuring IRF bridge MAC persistence Enter system view. system-view Configure IRF bridge MAC persistence. Retain the bridge MAC address permanently even if the address owner has left the fabric. irf mac-address persistent always Retain the bridge MAC address for 6 minutes after the address owner leaves the fabric. ... -
Page 37: Setting The Irf Link Down Report Delay
If sufficient storage space is not available, the MPU automatically deletes the current software images. If the reclaimed space is still insufficient, the MPU cannot complete the auto-update. You must reboot the device that holds the MPU, and then access the BootWare menu to delete files. Procedure Enter system view. -
Page 38: Replacing An Expansion Interface Card That Has Irf Physical Interfaces
Replacing an expansion interface card that has IRF physical interfaces Replacing the old card with a different model replacement card Shut down the IRF physical interfaces on the old card by using the command. shutdown Remove the IRF port bindings that contain the physical interfaces. Remove the old card, and then install the replacement card. - Page 39 Configure LACP MAD on the multichassis aggregation to Device C, which supports extended LACP. Figure 13 Network diagram Device C IP network XGE1/0/1 XGE1/0/2 XGE1/2/0/2 XGE2/2/0/2 XGE1/2/0/1 XGE2/2/0/1 XGE1/3/0/1 XGE2/3/0/1 Device A Device B (IRF-port1/2) (IRF-port2/1) Procedure Configure Device A: # Assign member ID 1 to Device A, and bind Ten-GigabitEthernet 2/0/1 and Ten-GigabitEthernet 3/0/1 to IRF-port 2.
- Page 40 # Assign member ID 2 to Device B, and bind Ten-GigabitEthernet 2/0/1 and Ten-GigabitEthernet 3/0/1 to IRF-port 1. <Sysname> system-view [Sysname] irf member 2 [Sysname] irf-port 1 [Sysname-irf-port1] port group interface ten-gigabitethernet 2/0/1 [Sysname-irf-port1] port group interface ten-gigabitethernet 3/0/1 [Sysname-irf-port1] quit # Save the configuration.
-
Page 41: Example: Configuring A Bfd Mad-Enabled Two-Chassis Irf Fabric
[Sysname] interface ten-gigabitethernet 2/2/0/2 [Sysname-Ten-GigabitEthernet2/2/0/2] port link-aggregation group 2 Configure Device C as the intermediate device: CAUTION: If the intermediate device is also an IRF fabric, assign the two IRF fabrics different domain IDs for correct split detection. False detection causes IRF split. # Create a dynamic aggregate interface. - Page 42 Figure 14 Network diagram (IRF-port1/2) (IRF-port2/1) Device A Device B XGE1/2/0/1 XGE2/2/0/1 XGE1/3/0/1 XGE2/3/0/1 XGE1/2/0/2 XGE2/2/0/2 BFD link …… Procedure Configure Device A: # Assign member ID 1 to Device A, and bind Ten-GigabitEthernet 2/0/1 and Ten-GigabitEthernet 3/0/1 to IRF-port 2. <Sysname>...
- Page 43 Saved the current configuration to mainboard device successfully. Slot 1: Save next configuration file successfully. Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in IRF mode? [Y/N]:y Now rebooting, please wait... Configure Device B: # Assign member ID 2 to Device B, and bind Ten-GigabitEthernet 2/0/1 and Ten-GigabitEthernet 3/0/1 to IRF-port 1.
-
Page 44: Example: Restoring Standalone Mode
[Sysname-Ten-GigabitEthernet2/2/0/2] quit # Assign a MAD IP address to each member device on the aggregate interface. [Sysname] interface route-aggregation 1 [Sysname-Route-Aggregation1] mad bfd enable [Sysname-Route-Aggregation1] mad ip address 192.168.2.1 24 member 1 [Sysname-Route-Aggregation1] mad ip address 192.168.2.2 24 member 2 [Sysname-Route-Aggregation1] quit Example: Restoring standalone mode Network configuration... - Page 45 The output shows that Device A is the master. Examine the configuration for VLAN interfaces. If a VLAN interface has member ports on different member devices, change the IP address for the interface on each device to be unique. Shut down IRF physical interfaces to disconnect all IRF links. In this example, shut down Ten-Gigabitethernet 1/2/0/1 and Ten-GigabitEthernet 1/3/0/1.
- Page 46 Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in stand-alone mode? [Y/N]:y Now rebooting, please wait... Device B automatically reboots to complete the operating mode change.
Need help?
Do you have a question about the MSR 5600 and is the answer not in the manual?
Questions and answers