H3C S5820 Configuration Manual
Hide thumbs
Also See for S5820:
- Command reference manual (218 pages) ,
- Oaa command reference (24 pages)
Subscribe to Our Youtube Channel
Related Manuals for H3C S5820
Summary of Contents for H3C S5820
- Page 1 H3C S5820X&S5800 Series Ethernet Switches Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Document Version: 6W103-20100716 Product Version: Release 1110...
- Page 2 SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V G, V G, PSPT, XGbus, N-Bus, TiGem, InnoVision 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.
- Page 3 Preface The H3C S5800&S5820X documentation set includes 11 configuration guides, which describe the software features for the S5800&S5820X Series Ethernet Switches 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.
- Page 4 Description Means reader be careful. Improper operation may cause data loss or damage to equipment. Means a complementary description. About the H3C S5820X&S5800 Documentation Set The H3C S5800&S5820X documentation set also includes: Category Documents Purposes Marketing brochures Describe product specifications and benefits.
- Page 5 Interface Cards User available for the products. Manual Describes the benefits, features, hardware H3C OAP Cards User specifications, installation, and removal of the OAP Manual cards available for the products. H3C Low End Series...
- Page 6 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 &...
-
Page 7: Table Of Contents
Table of Contents 1 IRF Configuration ······································································································································1-1 IRF Overview ··········································································································································1-1 Introduction······································································································································1-1 Advantages······································································································································1-1 Application and Advantages············································································································1-2 Basic Concepts ·······································································································································1-2 Working Process ·····································································································································1-3 Physical Connections ······················································································································1-4 Topology Collection ·························································································································1-6 Role Election ···································································································································1-6 IRF Virtual Device Management ·····································································································1-7 IRF Multi-Active Detection (MAD) Mechanism ··············································································1-10 IRF Virtual Device Configuration Task List ···························································································1-11 IRF Virtual Device Configuration···········································································································1-12 Specifying a Domain ID for an IRF Virtual Device ········································································1-12... -
Page 8: Irf Configuration
IRF Overview Introduction Developed by H3C, Intelligent Resilient Framework (IRF) provides a new method to connect multiple devices. Individual devices join to form a distributed device. IRF realizes the cooperation, unified management, and non-stop maintenance of multiple devices. -
Page 9: Application And Advantages
the upper or lower layer devices can be aggregated, and thus the reliability of the IRF virtual device is increased through link backup. Powerful network expansion capability. By adding member devices, the number of IRF ports and network bandwidth of the IRF virtual device can be easily expanded. Each member device has its own CPU and they can independently process and forward protocol packets;... -
Page 10: Working Process
Physical IRF port Physical ports used for connecting members of an IRF virtual device are called physical IRF ports. Typically, an Ethernet port or optical port forwards packets to the network. When bound to an IRF port, it acts as a physical IRF port and forwards data traffic such as IRF-related negotiation packets and data traffic among members. -
Page 11: Physical Connections
S5820X and S5800 series switches, use SFP+ ports on the front panel or SFP+ ports on an interface card as physical IRF ports. For details of SFP+ ports and interface cards used on different device models, refer to H3C S5800 Series Ethernet Switches Installation Manual and H3C S5820X Series Ethernet Switches Installation Manual. - Page 12 Table 1-2 Correspondence between an IRF port and physical IRF port(s) for different device models Device model Physical IRF port IRF port correspondence Physical IRF ports are provided on All physical IRF ports bound to the same S5800-60C-PWR the two interface cards on the front IRF port must be located on the same panel.
-
Page 13: Topology Collection
IRF topology An IRF virtual device typically adopts daisy chain connection or ring connection, as shown in Figure 1-5. A daisy chain connection is mainly used in a network where member devices are distributedly located. A ring connection is more reliable than the daisy chain connection. In a daisy chained IRF virtual device, the failure of one link can cause the IRF virtual device to partition into two independent IRF virtual devices;... -
Page 14: Irf Virtual Device Management
the rules below, in the order specified. If the first rule does not apply, a second rule is tried, and so on, until the only winner is found. The current master, even if a new member has a higher priority. (When an IRF virtual device is being formed, all member devices consider themselves as the master, so this principle is skipped) A member with a higher priority. - Page 15 inserted with cards, and each card has its own power supply unit (PSU), fan, CPU, console port and Ethernet ports. Figure 1-6 IRF virtual device Interface name For a device that operates independently (in other words, the device does not belong to any IRF virtual device), its interface name is in the format of member ID/slot number/interface serial number, where: The default member ID is 1.
- Page 16 File naming rules You can use the name of a storage medium to access files on an independently operating device. For the naming rules of a storage medium, see File Management Configuration in the Configuration Fundamentals Configuration Guide. To access the files of the master, use the name of the storage medium; to access files of a slave, use the name in the following format: Member-ID#Storage-device-name.
-
Page 17: Irf Multi-Active Detection (Mad) Mechanism
IRF uses a strict configuration file synchronization mechanism to ensure that the members of an IRF virtual device can work as a single device and that when the master fails, the other devices can operate normally. When a slave starts up, it automatically searches for the master, synchronizes the master's configuration file, and executes the configuration file. -
Page 18: Irf Virtual Device Configuration Task List
(disabled) and all physical ports (usually the service ports) in them are shut down except for the reserved ones to make sure that these IRF virtual devices cannot forward data traffic. Failure recovery: An IRF link failure triggers IRF virtual device partition and thus causes multi-active collision. -
Page 19: Irf Virtual Device Configuration
easy fault location and device maintenance, the S5820X series or S5800 series provides slave view, where you can execute the display, terminal, and debug commands. Complete the following tasks to configure an IRF virtual device: Task Remarks Specifying a Domain ID for an IRF Virtual Device Optional Setting a Member ID for a Device Optional... - Page 20 Figure 1-8 Network diagram for multiple domains Core network IRF virtual device 1 (domain 10) Switch A Switch B IRF link IRF virtual device 2 Switch D Switch C (domain 20) IRF link Access network Assigning a domain ID to an IRF virtual device If LACP MAD detection is applied for multiple IRF virtual devices and LACP MAD detection links exist among the IRF virtual devices, assign different domain IDs for the IRF virtual devices.
-
Page 21: Setting A Member Id For A Device
You must assign a domain ID for an IRF virtual device before enabling LACP MAD detection. Although devices with different domain IDs can form an IRF virtual device, you are recommended to assign the same domain ID to the members of the same IRF virtual device; otherwise, the LACP MAD detection function cannot function properly. -
Page 22: Configuring Irf Ports
Member ID change takes effect at the reboot of a device. To view the current member ID of a device, use the display irf configuration command. The member ID takes effect at the device reboot. Member IDs are not only used to identify members of an IRF virtual device, but also used to identify the port configurations on different members. - Page 23 To do… Use the command… Remarks Optional When you physically connect the devices and bind physical IRF port(s) to an IRF port whose link Activate configurations on all IRF irf-port-configuration active state is DIS or DOWN, which you ports on the device can display with the display irf topology command, this step is required to establish an IRF...
- Page 24 Follow these steps to configure global IRF port load sharing mode: To do… Use the command… Remarks Enter system view system-view — Required By default, S5800-56C S5800-56C-PWR switches use the inbound port number as the hash key. Other models of the S5820X series irf-port load-sharing mode and S5800 series switches use the Configure global IRF port...
-
Page 25: Specifying A Priority For A Member
To do… Use the command… Remarks Required By default, S5800-56C S5800-56C-PWR switches use the inbound port number as the hash Other models of the S5820X series and S5800 series switches use the combination of the source and irf-port load-sharing mode destination MAC addresses as the Configure load sharing mode { destination-ip | destination-mac |... -
Page 26: Specifying The Preservation Time Of The Bridge Mac Address
The priority setting takes effect right after your configuration without the need of rebooting the device. Specifying the Preservation Time of the Bridge MAC Address A device uses the bridge MAC address when it communicates with external networks as a bridge. Some Layer 2 protocols (like LACP) use bridge MAC addresses to identify different devices. -
Page 27: Enabling Auto Upgrade Of Boot Files
Bridge MAC address change may cause a temporary traffic interruption. Enabling Auto Upgrade of Boot Files If auto upgrade of boot files is disabled, when the boot files of slaves and the boot file of the master are in different versions, the new member or the member with a low priority will not boot normally. You need to manually update the device version and add the device into the IRF virtual device again. -
Page 28: Configuring Mad Detection
Use this function to avoid unnecessary IRF virtual device partition and merge caused by frequent link state changes of a port in a short time. Follow these steps to set the delay time for the link layer to report a link-down event of an IRF virtual device: To do…... - Page 29 commonly used networking diagram is as shown in Figure 1-9: the member devices exchange LACPDUs through Device. Figure 1-9 Network diagram for LACP MAD detection Terminal network Device Dynamic aggregation group on Device, used for LACP MAD and data traffic forwarding. IRF virtual Dynamic aggregation group on device...
-
Page 30: Configuring Bfd Mad
To do… Use the command… Remarks Required Disabled by default. Even though this command can be configured on both static and Enable LACP MAD detection mad enable dynamic aggregate interfaces, it takes effect only on dynamic aggregate interfaces. This is because this detection approach depends on LACP. - Page 31 Figure 1-10 Network diagram for BFD MAD detection Terminal network Device Aggregation group on Device, used for data traffic forwarding. BFD MAD link Vlan2 Vlan2 192.168.1.2/24 192.168.1.3/24 IRF link Slave Master Internet Configuring BFD MAD detection Configure BFD MAD detection in the following order: Create a VLAN dedicated for BFD MAD detection;...
-
Page 32: Excluding A Port From The Shut Down Action Upon Detection Of Multi-Active Collision
To do… Use the command… Remarks Access port port access vlan vlan-id Required You can select one approach Trunk port port trunk permit vlan vlan-id according to the port type. Assign the port BFD MAD detection has no to the VLAN requirement on the link type of dedicated for the detection port, and you do... -
Page 33: Manually Recovering An Irf Virtual Device
Follow these steps to configure a port not to shut down when the IRF virtual device transits to recovery state: To do… Use the command… Remarks Enter system view system-view — Optional Specify the reserved ports, which By default, no reserved port is are ports that are not disabled mad exclude interface interface-type specified. - Page 34 Figure 1-11 Auto-recovery of the IRF virtual device when the IRF link is repaired If the IRF virtual device in the active state fails due to exceptions (a member fails or link failure occurs, for example) before the IRF link is recovered, as shown in Figure 1-12, enable IRF virtual device 2 (in the recovery state) at the CLI by executing the mad restore command.
-
Page 35: Logging In To An Irf Virtual Device
If you change the state of an IRF virtual device from recovery to active and recover the failed IRF virtual device whose original state was active, an election is held, and then members of the loser side reboot and join the winner side as slaves. Logging In to an IRF Virtual Device Logging In to the Master To access an IRF virtual device, perform either of the following two ways:... -
Page 36: Displaying And Maintaining An Irf Virtual Device
To do… Use the command… Remarks Required By default, you actually log in to the Log in to the specified slave irf switch-to member-id master when you log in to an IRF virtual device. Concurrent user login to an IRF virtual device occupies large memory space. Therefore, an IRF virtual device allows at most 15 concurrent virtual type terminal (VTY) users. - Page 37 Figure 1-13 Network diagram for an IRF virtual device that uses LACP MAD detection Configuration procedure Set member IDs # Keep the default member ID of Device A unchanged. # Set the member ID of Device B to 2. <Sysname> system-view [Sysname] irf member 1 renumber 2 Warning: Renumbering the switch number may result in configuration change or loss.
-
Page 38: Configuration Example Of Using The Bfd Mad Detection
[Sysname-Ten-GigabitEthernet2/0/26] quit [Sysname] irf-port-configuration active Two devices reboot automatically. Then, an IRF virtual device is established. Configure LACP MAD detection # Create a dynamic aggregation interface and enable LACP MAD detection. <Sysname> system-view [Sysname] interface bridge-aggregation 2 [Sysname-Bridge-Aggregation2] link-aggregation mode dynamic [Sysname-Bridge-Aggregation2] mad enable [Sysname-Bridge-Aggregation2] quit # Add ports GigabitEthernet 1/0/1 and GigabitEthernet 2/0/1 to the aggregation interface and they are... - Page 39 # Keep the default member ID of Device A unchanged. # Set the member ID of Device B to 2. <Sysname> system-view [Sysname] irf member 1 renumber 2 Warning: Renumbering the switch number may result in configuration change or loss. Continue? [Y/N]:y [Sysname] Power off the two devices and connect IRF links and BFD MAD detection links according to...
- Page 40 [Sysname-Vlan-interface3] mad ip address 192.168.2.1 24 member 1 [Sysname-Vlan-interface3] mad ip address 192.168.2.2 24 member 2 [Sysname-Vlan-interface3] quit 1-33...
-
Page 41: Index
Index Advantages Setting a Member ID for a Device 1-14 Application and Advantages Setting the Delay Time for the Link Layer to Report a Link-Down Event 1-20 Specifying a Domain ID for an IRF Virtual Configuration Example of Using the BFD Device 1-12 MAD Detection...
Need help?
Do you have a question about the S5820 and is the answer not in the manual?
Questions and answers