Vous êtes sur la page 1sur 53

H3C S5500-EI & S5500-SI Series Ethernet Switches IRF Configuration Guide

Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com

Copyright 2003-2010, 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, , Aolynk, , H3Care, , TOP G, , IRF, NetPilot, Neocean, NeoVTL,

SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V2G, VnG, 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.

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.

Environmental Protection
This product has been designed to comply with the requirements on environmental protection. The storage, use, and disposal of this product must meet the applicable national laws and regulations.

Preface
The H3C S5500-EI & S5500-SI Series documentation set includes 13 configuration guides, which describe the software features for the H3C S5500-EI & S5500-SI 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. This preface includes: Audience Conventions About the H3C S5500-EI & S5500-SI Series Documentation Set Obtaining Documentation Documentation Feedback

Audience
This documentation is intended for: Network planners Field technical support and servicing engineers Network administrators working with the S5500-EI & S5500-SI series

Conventions
This section describes the conventions used in this documentation set.

Command conventions
Convention
Boldface italic [] { x | y | ... } [ x | y | ... ] { x | y | ... } * [ x | y | ... ] * &<1-n> #

Description
Bold text represents commands and keywords that you enter literally as shown. Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional. Braces enclose a set of required syntax choices separated by vertical bars, from which you select one. Square brackets enclose a set of optional syntax choices separated by vertical bars, from which you select one or none. Asterisk marked braces enclose a set of required syntax choices separated by vertical bars, from which you select at least one. Asterisk marked square brackets enclose optional syntax choices separated by vertical bars, from which you may select multiple choices or none. 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
Button names are inside angle brackets. For example, click <OK>. Window names, menu items, data table and field names are inside square brackets. For example, pop up the [New User] window. Multi-level menus are [File/Create/Folder]. separated by forward slashes. For example,

Symbols
Convention Description
Means reader be extremely careful. Improper operation may cause bodily injury. Means reader be careful. Improper operation may cause data loss or damage to equipment. Means an action or information that needs special attention to ensure successful configuration or good performance. Means a complementary description. Means techniques helpful for you to make configuration with ease. 4

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.

About the H3C S5500-EI & S5500-SI Series documentation set


Category
Product description and specifications

Documents
Marketing brochures Technology white papers Card datasheets Compliance and safety manual Quick start

Purposes
Describe product specifications and benefits. Provide an in-depth description of software features and technologies. Describe card specifications, features, and standards. Provides regulatory information and the safety instructions that must be followed during installation. Guides you through initial installation and setup procedures to help you quickly set up and use your device with the minimum configuration. Provides a complete guide to hardware installation and hardware specifications. Provide the hardware specifications of cards. Guides you through installing and remodeling H3C cabinets. Guides you through installing SFP/SFP+/XFP transceiver modules. Guides you through installing adjustable slider rails to a rack. Describes the hot-swappable modules available for the H3C high-end network products, their external views, and specifications. Describe software features and configuration procedures. Provide a quick reference to all available commands. Describe typical network scenarios and provide configuration examples and instructions. Explains the system log messages. Explains the trap messages. Describes the MIBs for the software release. Provide information about the product release, including the version history, hardware and software compatibility matrix, version upgrade information, technical support information, and software upgrading. Explains the error codes. 6

Installation guide Card manuals Hardware specifications and installation H3C Cabinet Installation and Remodel Introduction H3C Pluggable SFP [SFP+][XFP] Transceiver Modules Installation Guide Adjustable Slider Rail Installation Guide H3C High-End Network Products Hot-Swappable Module Manual Configuration guides Software configuration Command references Configuration examples System log messages Trap messages MIB Companion Operations and maintenance Release notes

Error code reference

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.

Documentation feedback
You can e-mail your comments about product documentation to info@h3c.com. We appreciate your comments.

Table of Contents
Preface 3
Audience 3 Conventions 4 About the H3C S5500-EI & S5500-SI Series documentation set 6

IRF Configuration 10
IRF overview 10 Introduction 10 Application 10 Basic concepts 11 Working process 12 Physical connections 12 Topology collection 17 Role election 18 IRF virtual device management and maintenance 18 IRF virtual device configuration task list 24 Configuring an IRF virtual device 25 Configuring IRF ports 25 Setting a member ID for a device 26 Specifying a priority for a member device 27 Specifying the preservation time of the bridge MAC address 27 Enabling auto upgrade of boot files 28 Setting the delay time for the link layer to report a link-down event 29 Accessing an IRF virtual device 30 Accessing the master 30 Accessing a subordinate 30 Displaying and maintaining an IRF virtual device 31 IRF virtual device configuration examples 31 IRF virtual device configuration example 31

Obtaining support for your product 33


Register your product 33 Purchase value-added services 33 Troubleshoot online 33 Access software downloads 34 Telephone technical support and repair 34 Contact us 35

Acronyms 36 Index 51

IRF Configuration
IRF overview
Introduction
The H3C Intelligent Resilient Framework provides a new method to connect multiple devices through physical IRF ports. Individual devices join to form a distributed device called IRF virtual device. IRF enables the cooperation, unified management, and non-stop maintenance of multiple devices.

Application
As shown in Figure 1, a master and a subordinate form an IRF virtual device, which is a single device to the upper and lower layer devices. Figure 1 IRF networking
IP network IP network

Master

Subordinate Equal to IRF link

IRF virtual device

10

Basic concepts
Role
The devices that form an IRF virtual device are called member devices. Each of them plays one of the following two roles:

Master: Manages the IRF virtual device. Subordinate: All members that operate as backups of the master are called subordinates. When the master fails, the IRF virtual device automatically elects a new master from one of the subordinates.

Master and subordinates are elected through the role election mechanism. An IRF virtual device has only one master at a time. For more information about election process, see Role election.

IRF port
An IRF port is a logical port dedicated to the internal connection of an IRF virtual device. An IRF port can be numbered as IRF-port1 or IRF-port2. An IRF port is effective only after it is bound to a physical IRF port.

Physical IRF port


Physical ports used for connecting members of an IRF virtual device are called physical IRF ports. Physical IRF ports can be ports dedicated to the IRF virtual device, Ethernet ports, or optical ports. The device model determines which ports can serve as physical IRF ports. Typically, an Ethernet port or optical port forwards packets to the network. When an Ethernet or optical port is 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 member devices.

IRF virtual device merge


IRF virtual devices operate independently of each other. You can connect them and enter the necessary configurations to make them form one IRF virtual device. This process is called IRF virtual device merge. See Figure 2. Figure 2 IRF virtual device merge

11

IRF virtual device partition


When an IRF virtual device is formed, the loss of the IRF link causes a disconnection between the two members, and the IRF virtual device is divided into two virtual IRF devices. This process is called IRF virtual device partition. See Figure 3. Figure 3 IRF virtual device partition

Member priority
Member priority determines the role of a member during a role election process. A member with a higher priority is more likely to be a master. The priority of a device defaults to 1. You can modify the priority at the command line interface.

Working process
IRF virtual device management involves the following stages:

Physical connections Topology collection Role election IRF virtual device management and maintenance

First, physically connect the members of an IRF virtual device. The members then perform topology collection and role election to establish an IRF virtual device, which then enters the IRF virtual device management and maintenance stage.

Physical connections
Connection medium
To establish an IRF virtual device, connect the physical IRF ports of the member devices. For the S5500-EI series, the 10 GE interface modules can be inserted into the expansion module slots on the rear panel of the switch to provide physical IRF ports. The following 10 GE interface modules can be used to provide physical IRF ports:

One-port 10 GE XFP interface module Dual-port 10 GE XFP interface module Short-haul dual-port 10 GE CX4 interface module Dual-port 10 GE SFP+ interface module
12

For more information about an interface module, refer to its user manual.

You can connect physical IRF ports of the S5500-EI series with either the CX4/SFP+ dedicated cables or fibers, according to the interface type on the interface module. Dedicated cables provide higher reliability and performance, whereas fibers connect physical devices located very far from each other and provide flexible application. The physical IRF ports are numbered according to their physical locations on the rear panel of the S5500-EI series. With the rear panel facing you, the physical IRF ports are numbered successively from left to right: ports on the interface module in slot 1 are numbered 1 and 2, and ports on the interface module in slot 2 are numbered 3 and 4. Figure 4 illustrates an example of inserting a CX4 dual-port interface module. Figure 4 Numbering physical IRF ports

If you insert a one-port interface module into the slot, the number of the physical IRF port corresponding to the module in slot 1 is 1, and the number of the physical IRF port corresponding to the module in slot 2 is 3. For the number of physical IRF ports, see Configuring IRF ports. Physical IRF ports can be used for both IRF connection and service data transmission. When establishing an IRF virtual device, you need to specify that the physical IRF ports are used for the IRF. That is, bind them with IRF ports to implement IRF connection and establishment.

Connection requirements
IRF-Port1 on one device can only be connected to the physical port bound to IRF-Port2 of a neighbor device. Otherwise, an IRF virtual device cannot be formed. See Figure 5. Figure 5 IRF virtual device physical connection

13

IRF topology
An IRF virtual device typically adopts daisy chain connection or ring connection.

A daisy chain connection is mainly used in a network where member devices are distributed locally. 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. In a ring connection, however, the failure of a link results in a daisy chain connection, which does not affect IRF services.

Figure 6 IRF connections IRF virtual


Master

devic e
IRF-Port2

Master

IRF-Port1

IRF-Port1

IRF-Port2

Slave
IRF-Port2

IRF virtual device


IRF-Port2 IRF-Port1

IRF-Port1

Subordinate

IRF-Port1

IRF-Port2

Subordinate

Subordinate

Daisy chain connection

Ring connection

You can connect at most nine S5500-EI series switches to form an IRF virtual device.

Correspondence between an IRF port and a physical IRF port


The connection of IRF ports is based on that of physical IRF ports. Therefore, you need to bind an IRF port with physical IRF ports. An IRF port can be bound to one physical IRF port or, to realize link backup and bandwidth expansion, it can be bound to two physical IRF ports (aggregated as an aggregate IRF port). You need to specify the correspondence between an IRF port and physical IRF ports through the command line. When you specify that an IRF port is bound to one physical IRF port, the serial number of the physical IRF port bound to IRF port 1 must be smaller than that of the physical IRF port bound to IRF port 2. When you specify that an IRF port is bound to two physical IRF ports (aggregate IRF port), these two physical IRF ports must be on the same module. As shown in Figure 7, Switch A connects to Switch B and Switch C through IRF ports IRF-port 1 and IRF-port 2, respectively.
14

Figure 7 IRF port correspondence


IRF-port1 IRF-port2 Switch B Switch A IRF-port1 IRF-port2 Switch C

Based on the type and number of the interface module inserted on Switch A, you can adopt one of the following typical correspondences to establish an IRF connection.

The dual-port 10 GE CX4 interface module is used in the following examples to introduce correspondence between the IRF port and the physical IRF ports. When the dual-port 10 GE SFP interface module is used, the correspondence between the IRF port and the physical IRF ports is similar.

IRF port correspondence for one interface module


Figure 8 IRF port correspondence for one interface module

When a dual-port interface module is installed, you need to bind IRF-port 1 to physical IRF port 1, and IRF-port 2 to physical IRF port 2 (as shown in Figure 8), because the serial number of the physical IRF port bound to IRF-port 1 must be smaller than that of the physical IRF port bound to IRF-port 2. Therefore, you cannot bind IRF-port 1 to physical IRF port 2, and IRF-port 2 to physical port 1.

If only one single-port interface module is installed, the device can be used only as Switch B or Switch C in Figure 7. That is, the device should be at either end of a bus connection. In this situation, because only one IRF port is needed on Switch B or Switch C, IRF-port 2 or IRF-port 1 can be bound to any physical port on the device.

15

IRF port correspondence for two interface modules

Correspondence in non-aggregate mode

Figure 9 Correspondence in non-aggregate mode for two interface modules

When two dual-port interface modules are installed, if the correspondence is not in the aggregate mode, you can bind an IRF port to any physical IRF port (Figure 9 shows only one possibility). However, you must ensure that the serial number of the physical IRF port bound to IRF-port 1 is smaller than that of the physical IRF port bound to IRF-port 2; namely, the physical IRF port bound to IRF-port 2 should be located on the right side of the physical IRF port bound to IRF-port 1. The two physical IRF ports bound to the IRF ports can be located either on one interface module or on different interface modules.

If two single-port interface modules are installed, you need to bind IRF-port 1 to physical IRF port 1, and IRF-port 2 to physical IRF port 3. If one dual-port interface module and one single-port interface module are installed, the correspondence is the same as when you install two dual-port interface modules. In this situation, IRF-port 2 or IRF-port 1 can be bound to any physical port on the device because only one IRF port is needed on Switch B or Switch C.

Correspondence in aggregate mode

16

Figure 10 Correspondence in aggregate mode for two interface modules

Because the two physical IRF ports bound to an aggregate IRF port must be located on the same interface module, two IRF ports (that is, two aggregate IRF ports) can only be bound to the two physical IRF ports on each of the two interface modules respectively (as shown in Figure 10). In addition, you can only bind IRF-port 1 to physical IRF ports 1 and 2, and IRF-port 2 to physical ports 3 and 4.

If one dual-port interface module and one single-port interface module are installed, you can bind two physical IRF ports on the dual-port interface module to the IRF port in aggregate mode. You can also bind the physical IRF port on the single-port interface module to the other IRF port in non-aggregate mode. In this situation, IRF-port 2 or IRF-port 1 can be bound to any physical port on the device because only one IRF port is needed on Switch B or Switch C.

Topology collection
Each member exchanges hello packets with the directly connected neighbors to collect topology of the IRF virtual device. The IRF hello packets carry the topology information, including IRF port connection states, member IDs, priorities, and bridge MAC addresses. Each member records its known topology information locally. At the startup of a member device, the member device records topology information of the local device. When an IRF port of a member comes up, the member device sends its known topology information from this port periodically. Upon receiving the topology information from the directly connected neighbor, the member device updates the local topology information. After topology collection lasts until all members have obtained the complete topology information (known as topology convergence), the IRF virtual device enters the next stage: role election.

17

Role election
The process of defining the role (master or subordinate) of members is role election. Role election is held when the topology changes, such as forming an IRF virtual device, adding a new member, leaving or failure of the master, or IRF virtual device merge. The master is elected based on 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 and all member devices consider themselves as the master, this principle is skipped.) A member with a higher priority. A member with the longest system up-time. (The system up-time information of each member device is delivered through IRF hello packets.) A member with the lowest bridge MAC address.

Then, the IRF virtual device is formed and enters the next stage: IRF virtual device management and maintenance.

The precision of the system up-time is six minutes. For example, if two devices with the same priority values reboot one after another within six minutes, they will have the same system up-time, and the last role election principle will be followed. That is, the one with the lowest bridge MAC address wins. During an IRF virtual device merge, an IRF election is held, and role election rules are followed. Members of the losing side reboot and join the winning side as subordinates. Whether the device reboots automatically or reboots with the execution of a command depends on the device model. To ensure the same configuration as that on the master, a device uses the masters configuration to initialize and boot itself as long as it is elected as a subordinate, regardless of its original configuration or whether its current configuration is saved.

IRF virtual device management and maintenance


After role election, an IRF virtual device is established: all member devices operate as one virtual device, and all resources on the member devices are processed by this virtual device and managed by the master.

Member ID
An IRF virtual device uses member IDs to uniquely identify and manage its members. For example, when the device operates independently, the slot number in the interface number is typically 1; after it joins an IRF virtual device, the slot number will become the member ID. In addition, member IDs are used in file management. Therefore, member IDs in an IRF virtual device must be unique.

18

If member IDs are not unique, an IRF virtual device cannot be established. A member having the same member ID as an existing one cannot join the IRF virtual device. To ensure the uniqueness of member IDs, use the following two methods:
1. 2.

Before establishing an IRF virtual device, plan and configure member IDs for members. Adopt the member ID collision processing mechanism, which is described as follows: During the establishment of an IRF virtual device, when two devices that form the IRF virtual device have duplicated member IDs, the master is numbered the first. Then, for a daisy chain connection, subordinates connected to IRF port 1 of the master are numbered from near to far, and then those connected to IRF port 2 of the master are numbered the same way. For a ring connection, the subordinate connected to IRF port 1 of the master is numbered first, and then other subordinates are numbered from near to far, and the subordinate connected to IRF port 2 of the master is numbered last. For example, Device A, Device B, Device C, and Device D use their default member IDs (the value is 1) and form an IRF. Suppose Device B has the highest priority and is therefore elected as the master. The IRF virtual device first numbers the master as member device 1, and then other devices are numbered one by one. If the four devices form a ring connection, their member IDs are 2, 1, 3, and 4, as shown in Figure 11. If the four devices form a daisy chain connection, the their member IDs are 2, 1, 4, and 3, as shown in Figure 12. When an IRF virtual device is established, if the newly added device and another member have duplicate member IDs, the existing member's member ID remains unchanged, and the IRF virtual device assigns the smallest available member ID to the new member.

Figure 11 Automatic numbering for a ring connection


MemberID =1 MemberID=1 MemberID=1 MemberID= 1

Device A

Device B

Device C
Suppose Device B is elected as the master when the IRF virtual device is formed .

Device D

MemberID=2

MemberID=1
IRF-Port1 IRF- Port2

MemberID=3

MemberID= 4

Device A (Subordinate)

Device B ( Master)

Device C (Subordinate)

Device D (Subordinate)

19

Figure 12 Automatic numbering for a daisy chain connection


MemberID=1 MemberID=1 MemberID=1 =1 MemberID

Device A

Device B

Device C
Suppose Device B is elected as the master when the IRF virtual device is formed .

Device D

MemberID=2 Device A (Subordinate)

MemberID=3 Device D (Subordinate)

IRF-Port1 IRF-Port2

MemberID=1 Device B (Master)

MemberID=4 Device C (Subordinate)

Interface name
For a device operating independently (that is, a device that does not belong to any IRF virtual device), the interface name is in the following format: member ID/slot number/interface serial number, where:

By default, member ID is 1. After a device leaves an IRF virtual device, it continues using the member ID from when it was in the IRF virtual device as its device ID. Subslot number is the number of the slot in which the LPU resides. For a box-type device, LPUs are fixed on the device, so the slot number is a fixed value. On the S5500-EI series, the subslot on the front panel is numbered 0, and subslots of the two expansion slots on the rear panel are numbered 1 and 2 from left to right. Interface serial number is dependent on the number of interfaces supported by the device. Look at the number on the interface card for the number of supported interfaces.

20

For example, GigabitEthernet 1/0/1 is an interface on the independently operating device Sysname. To set the link type of GigabitEthernet 1/0/1 to trunk, perform the following steps:
<Sysname> system-view [Sysname] interface gigabitethernet 1/0/1 [Sysname-GigabitEthernet1/0/1] port link-type trunk

For an IRF member, the interface name also adopts the previously introduced format: member ID/slot number/interface serial number, where:

The member ID identifies the IRF member on which the interface resides. The meaning and value of the subslot number and the interface serial number are the same as those on an independently operating device.

For example, Ethernet 1/0/1 is an interface on IRF member subordinate 3 (member ID is 3). To set the link type of GigabitEthernet 1/0/1 to trunk, perform the following steps:
<Master> system-view [Master] interface gigabitethernet 3/0/1 [Master-GigabitEthernet3/0/1] port link-type trunk

File system name


You can use the name of the storage device to access the file system of an independently operating device. For the naming rules of a storage device, see File Management Configuration in the Fundamentals Configuration Guide. For example, flash is the storage device on the independently operating device Sysname. To back up the file aa.cfg under the root directory of the flash to the test folder, perform the following steps:
<Sysname> mkdir test ... %Created dir flash:/test.

<Sysname>copy aa.cfg test/aa(20080714).cfg Copy flash:/aa.cfg to flash:/test/aa(20080714).cfg?[Y/N]:y .. %Copy file flash:/aa.cfg to flash:/test/aa(20080714).cfg...Done. <Sysname> cd test <Sysname> dir Directory of flash:/test/ 0 -rw1568 Jul 14 2008 11:54:04 aa(20080714).cfg

30861 KB total (20956 KB free)

To access the file system of the master, use the name of the storage device. To access the file system of a subordinate, use the name in the following format: Member-ID#Storage-device-name.

21

For example: To access the test folder under the root directory of the flash on the master, perform the following steps:
<Master> mkdir test ... %Created dir flash:/test. <Master> dir Directory of flash:/ 0 1 2 -rw-rwdrw10105088 2445 Apr 26 2000 13:44:57 Apr 26 2000 15:18:19 Jul 14 2008 15:20:35 test.bin config.cfg test

30861 KB total (20961 KB free)

To create and access the test folder under the root directory of the flash on IRF member subordinate 3, perform the following steps:
<Master> mkdir slot3#flash:/test %Created dir slot3#flash:/test. <Master> cd slot3#flash:/test <Master> pwd slot3#flash:/test

Or:
<Master> cd slot3#flash:/ <Master> mkdir test %Created dir slot3#flash:/test.

To copy the test.bin file on the master to the root directory of the flash on IRF member subordinate 3, perform the following steps:
<Master> pwd slot3#flash:

//The above information indicates that the current working path is the root directory of the flash on subordinate 3.
<Master> cd flash:/ <Master> pwd flash:

// The above operations indicate that the current working path is the root directory of the flash on the master.
<Master> copy test.bin slot3#flash:/ Copy flash:/test.bin to slot3#flash:/test.bin?[Y/N]:y %Copy file flash:/test.bin to slot3#flash:/test.bin...Done.

22

Configuration file management


Configuration file synchronization
IRF uses a strict configuration file synchronization mechanism to ensure that devices in an IRF virtual device can work as a single device on the network, and to ensure that after the master fails, the other devices can operate normally.

When a subordinate starts up, it automatically discovers the master, synchronizes the master's configuration file, and executes the configuration file. If all devices in an IRF virtual device start up simultaneously, the subordinates synchronize the master's initial configuration file and execute it. When the IRF virtual device operates normally, all your configurations will be recorded into the current configuration file of the master, and they are synchronized to each device in the IRF virtual device. When you save the current configuration file of the master as the initial configuration file by using the save command, all subordinates execute the same saving operation to make the initial configuration files of all devices consistent.

Through the real-time synchronization, all devices in the IRF virtual device keep the same configuration file. If the master fails, all the other devices can execute various functions according to the same configuration file.

Configuration file application


The configuration file can be divided into two parts: global configuration and port configuration. When a subordinate applies these two kinds of configurations of the master, it deals with them in different ways:

Global configuration: All subordinates execute the current global configuration on the master exactly. That is, all members in the IRF virtual device apply the same global configuration. Port configuration: When a subordinate applies the port configuration on the master, it cares about the configuration related to its own port. For example, the subordinate with the member ID of 3 only cares about the configuration related to the GigabitEthernet 3/0/x port on the master. If there is a configuration related to its own port, it will apply the configuration; if not, no matter what configuration has been made to the port before the subordinate joins the IRF virtual device, the subordinate will function using null-configuration.

IRF virtual device topology maintenance


In an IRF, direct neighbors exchange hello packets periodically (the period is 200 ms). Without receiving any hello packet from a direct neighbor for ten periods, a member considers that the hello packets timed out, and the IRF isolates the expired device in the topology and updates its topology database. When an IRF port of a member becomes down, the member broadcasts the information to all the other members immediately. If the IRF port of the master is down, an election is triggered.

23

IRF virtual device configuration task list


Before configuring an IRF virtual device, you need to define the roles and functions of all the members for better planning. Because the configuration of some parameters takes effect after device reboot, H3C recommends that you first configure parameters, power off the devices, connect devices physically, and then power on the devices. The devices will then join in the IRF virtual device automatically. After an IRF virtual device is formed, you can configure and manage the IRF virtual device by logging into any device in the IRF virtual device. The operations you make take effect on the master and will be applied to the member devices in the IRF virtual device. For easy fault location and device maintenance, the S5500-EI switch provides subordinate view, where you can execute the display, terminal, and debug commands. Complete the following tasks to configure IRF: Task
Configuring IRF ports Setting a member ID for a device Specifying a priority for a member device Configuring an IRF virtual device Specifying the preservation time of the bridge MAC address Enabling auto upgrade of boot files Setting the delay time for the link layer to report a linkdown event

Remarks
Required Optional Required Optional Optional Optional

Connect the physical IRF ports of devices by using IRF cables (a ring connection is recommended) or fibers, and then power on the devices. Accessing device an IRF virtual Accessing the master Accessing a subordinate Required Optional

24

Configuring an IRF virtual device


Configuring IRF ports
IRF ports are logical. IRF can be enabled on a device only after the IRF ports are configured (in other words, the IRF ports are bound to physical IRF ports). For information about how to bind the IRF port and physical IRF ports) on an S5500-EI series, see Correspondence between an IRF port and a physical IRF port. Follow these steps to configure IRF ports To do
1. Enter system view 2. Bind physical IRF ports to an IRF port, and enable IRF on the current device

Use the command


system-view irf member member-id irf-port irfport-id port port-list

Remarks
Required By default, configured. no IRF port is

The above configuration takes effect after the reboot of the device. An IRF port that is bound with multiple physical IRF ports is an aggregation IRF port, which increases the bandwidth and reliability on the IRF port. If you specify multiple physical IRF ports with the port-list argument, you can configure an aggregation IRF port. You can configure at most two physical IRF ports as an aggregation IRF port for an S5500-EI series switch, and you can only aggregate physical IRF ports 1 and 2 and physical IRF ports 3 and 4. The irf-port-id argument represents the IRF port number. The port-list argument represents the physical IRF port number. For the correspondence of IRF ports, refer to Correspondence between an IRF port and a physical IRF port. When you insert a one-port interface module into the slot on the rear panel, if the interface module is in slot 1, the port on it will be numbered 1; and if the interface module is in slot 2, the port on it will be numbered 3.

25

Setting a member ID for a device


The member ID of a device defaults to 1. During the establishment of an IRF virtual device, when the devices that form the IRF have duplicated member IDs, the member ID of the master is decided first, and then the member IDs of subordinates are decided by the member ID collision processing mechanism. After the IRF virtual device is established, if the newly added device and another member have duplicated IDs, the IRF system assigns the smallest available ID to the new member. You can also set the member IDs according to network planning. For a device that is already in an IRF virtual device, you can use commands in Table 1 to modify the member ID of the device. This modification will be effective after the reboot of the device. For a device that is not in an IRF virtual device, H3C recommends that you set its member ID in the following way:
1. 2. 3.

Plan the member IDs in advance. You can view the member IDs of an IRF virtual device and find an unused ID for the new device. Log in to the device to be added into the IRF virtual device, and change its member ID to the unused ID found in step 1. Save the current configuration. Power off the device, connect the device with IRF cables, and then power it on. Use the configuration introduced in this section to enable IRF on the device, and add it into the IRF virtual device.

Table 1 Set a member ID for a device To do


1. Enter system view 2. Set a member ID for a device

Use the command


system-view irf member member-id renumber new-id

Remarks
Optional The member ID of a device defaults to 1.

The above setting takes effect after the reboot of the device. You can use the display irf configuration command to view the current member ID of the device, and the member ID will be used after the device reboot. Member IDs are used to identify members of an IRF virtual device. Therefore, modifying a member ID may cause device configuration change or even loss. Please modify member IDs with caution. For example, three members (of the same device model) with the member IDs of 1, 2, and 3 are connected to an IRF port. Suppose that each member has several ports: change the member ID of device 2 to 3, change that of device 3 to 2, reboot both devices, and add them into the IRF virtual device again. Then device 2 will use the original port configurations of device 3, and device 3 will use those of device 2.

26

Specifying a priority for a member device


The greater the priority value, the higher the priority. A member with a higher priority is more likely to be a master. Follow these steps to specify a priority for a member device: To do
1. Enter system view 2. Specify a priority for a member of an IRF virtual device

Use the command


system-view irf member priority member-id priority

Remarks

Optional
The priority of a member defaults to 1.

The setting of priority takes effect right after your configuration without the need to reboot the device.

Specifying the preservation time of the bridge MAC address


A device uses the bridge MAC address when it communicates with the external networks as a bridge. Some Layer 2 protocols (like LACP) use bridge MAC addresses to identify different devices. During Layer 2 packet forwarding, if the destination MAC address of a packet is the bridge MAC address of a device, the packet is sent to this device; otherwise, the packet is discarded. Therefore, a bridge device on your network must have a unique bridge MAC address. If two devices on your network have the same bridge MAC address, bridge MAC address collision occurs, and the communication fails. An IRF virtual device communicates with external networks as a single device. Therefore, it also has a bridge MAC address. Typically, an IRF virtual device uses the bridge MAC address of the master as its bridge MAC address. Bridge MAC address collision causes communication failure, and bridge MAC address switching causes traffic interruption. Configure the preservation time of the bridge MAC address of the IRF virtual device in this way:

Preserve for six minutes: When the master leaves, the bridge MAC address does not change within six minutes. If the master does not come back when the preserve time is expired, the IRF virtual device uses the bridge MAC address of the newly elected master as its bridge MAC address. If the master leaves the IRF for a short time due to device reboot or link failure, this configuration can reduce unnecessary switch of bridge MAC address and thereby avoid traffic interruption. Preserve permanently: Whether the master leaves the IRF virtual device or not, the bridge MAC address of the IRF virtual device remains unchanged. Not preserved: As soon as the master leaves, the IRF virtual device uses the bridge MAC address of the newly elected master as its bridge MAC address.
27

Follow these steps to specify the preservation time of the bridge MAC address of an IRF virtual device: To do
1. Enter system view 2. a. Configure the bridge MAC address of the IRF virtual device to be preserved permanently when the master leaves b. Specify the preservation time of the bridge MAC address of the IRF virtual device as 6 minutes when the master leaves c. Configure the bridge MAC address of the IRF virtual device to change as soon as the master leaves irf mac-address always persistent Optional By default, IRF bridge MAC address is preserved for 6 minutes after the master leaves.

Use the command


system-view

Remarks

irf mac-address persistent timer

undo irf mac-address persistent

Bridge MAC address change may cause a temporary traffic interruption. If two IRF virtual devices have the same bridge MAC address, they cannot be merged into one IRF virtual device.

Enabling auto upgrade of boot files

If auto upgrade of boot files is disabled, when the software of subordinates and that of the master are in different versions, the new member or the member with a low priority will not boot normally. Update the device version and add the device into the IRF virtual device again. If auto upgrade of boot file is enabled, as soon as a device is added into an IRF virtual device, the IRF virtual device compares its software version with that of the master. If the versions are not consistent, the device automatically downloads the boot file from the master, reboots with the new boot file, and joins the IRF virtual device again. If the downloaded boot file and the local boot file have duplicate file names, the local file is overwritten.

Follow these steps to enable auto upgrade of boot files for an IRF virtual device: To do
1. Enter system view 2. Enable auto upgrade of boot files for an IRF virtual device

Use the command


system-view irf auto-update enable

Remarks
Optional Enabled by default.

28

Although IRF supports the auto upgrade of boot files, to shorten the time for IRF virtual device establishment and reduce the influences caused by the IRF virtual device establishment to the network, H3C recommends that you ensure that the device and the master have the same software version before adding a device into an IRF virtual device. After automatically loading the masters boot file, a subordinate configures the file as the boot file to be used at the next boot and reboots automatically. To make the auto upgrade succeed, ensure that there is enough space on the storage media of the subordinate.

Setting the delay time for the link layer to report a link-down event
After you set the delay time for the link layer to report a link-down event:

If the IRF link state changes from up to down, the port does not immediately report the link state changes to the IRF virtual device. If the IRF link state is still down when the configured time is reached, the port reports the link state changes to the IRF virtual device, which then handles the problem accordingly. If the link state changes from down to up, the link layer immediately reports the event to the IRF virtual device.

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
1. Enter system view 2. Set the delay time for the link layer to report a link-down event of an IRF virtual device

Use the command


system-view irf link-delay interval

Remarks
Optional The function default. is disabled by

Do not set the delay time to a very long time. If you do, the IRF virtual device will not be aware of the IRF topology changes in time, and the service will be recovered slowly.

29

Accessing an IRF virtual device


Accessing the master
Access an IRF virtual device in either of the following ways:

Local login: Log in through the AUX or console port of a member device. Remote login: Configure an IP address for a Layer 3 Ethernet interface of a member device and make sure that the route is reachable. Then access the IRF virtual device remotely through Telnet, Web, or SNMP.

When you log in to the IRF virtual device, actually you log in to the master. The master is the configuration and control center of an IRF virtual device. When you configure the IRF virtual device on the master, the IRF virtual device synchronizes the configurations to the subordinates.

Accessing a subordinate
When you log in to an IRF virtual device, you actually log in to the master. The operation interface of the access terminal displays the master console. To print the logs or debugging information of a subordinate, redirect to the specified subordinate device. After that, the user access terminal displays the console of the subordinate device instead of that of the master device. The system enters user view of the subordinate device, and the command prompt is changed to <Sysname-Slave#X>, where X is the member ID of the device. For example, <Sysname-Slave#2>. What you have entered on the access terminal will be redirected to the specified subordinate device for processing. At present, only the following commands are allowed to be executed on a subordinate device:

display quit return system-view debugging terminal debugging terminal trapping terminal logging

To return to the master console, use the quit command. The master console is then reactivated and can output logs. Follow the steps below to log in to the specified subordinate device: To do
Log in to the specified subordinate device of an IRF virtual device

Use the command

Remarks
Required By default, you actually log in to the master when you log in to the IRF virtual device. Available in user view.

irf switch-to member-id

30

Because users login to the IRF system occupies a large amount of memory, an IRF system allows at most six users to log in at the same time. The permitted login user types are console and virtual type terminal (VTY).

Displaying and maintaining an IRF virtual device


To do
Display related information about the IRF virtual device Display topology information about the IRF virtual device Display all members configurations that take effect after device reboots Display the master/subordinate switchover states of IRF members

Use the command


display irf display irf topology display irf configuration display switchover state [ member-id ]

Remarks
Available in any view. Available in any view. Available in any view. Available in any view.

IRF virtual device configuration examples


IRF virtual device configuration example
Network requirements
Three S5500-EI series switches in an IRF form a daisy chain connection. Their member IDs are 1, 2, and 3, as shown in Figure 13. Figure 13 Network diagram for IRF virtual device configuration example
1 2 3 4 Switch 1

Switch 2

Switch 3

31

Configuration procedure
1.

The three devices are not connected. Power them on and configure them separately.

Configure Switch 1.
<Switch1> system-view [Switch1] irf member 1 renumber 1 Warning: Renumbering the switch number may result in configuration change or loss. Continue?[Y/N]:y [Switch1] irf member 1 irf-port 1 port 2

Configure Switch 2.
<Switch2>system-view [Switch2] irf member 1 renumber 2 Warning: Renumbering the switch number may result in configuration change or loss. Continue?[Y/N]:y [Switch2] irf member 1 irf-port 1 port 2 [Switch2] irf member 1 irf-port 2 port 3

Configure Switch 3.
<Switch3> system-view [Switch3] irf member 1 renumber 3 Warning: Renumbering the switch number may result in configuration change or loss. Continue?[Y/N]:y [Switch3] irf member 1 irf-port 2 port 3 2.

Power off the three devices. Connect them as shown in Figure 13 with IRF cables. Power them on, and the IRF virtual device is formed.

32

Obtaining support for your product


Register your product
Warranty and other service benefits start from the date of purchase, so it is important to register your product quickly to ensure you get full use of the warranty and other service benefits available to you. Warranty and other service benefits are enabled through product registration. Register your product at http://www.h3cnetworks.com, go to Support, Product Registration. Support services are based on accounts that you create or have authorization to access. First time users must apply for a user name and password that provides access to a number of eSupport features including Product Registration, Repair Services, and Service Request. If you have trouble registering your product, please contact 3Com Global Services for assistance.

Purchase value-added services


To enhance response times or extend warranty benefits, contact 3Com or your authorized reseller. Value-added services like ExpressSM and GuardianSM can include 24x7 telephone technical support, software upgrades, onsite assistance or advance hardware replacement. Experienced engineers are available to manage your installation with minimal disruption to your network. Expert assessment and implementation services are offered to fill resource gaps and ensure the success of your networking projects. More information on 3Com maintenance and Professional Services is available at http://www.h3cnetworks.com. Contact your authorized reseller or 3Com for a complete list of the value-added services available in your area.

Troubleshoot online
You will find support tools posted on the web site at http://www.h3cnetworks.com/ under Support, Knowledgebase. The Knowledgebase helps you troubleshoot H3C products. This query-based interactive tool contains thousands of technical solutions.

33

Access software downloads


Software Updates are the bug fix / maintenance releases for the version of software initially purchased with the product. In order to access these Software Updates you must first register your product on the web site at http://www.h3cnetworks.com, go to Support, Product Registration. First time users will need to apply for a user name and password. A link to software downloads can be found at http://www.h3cnetworks.com, under Support, Drivers and downloads. Software Upgrades are the software releases that follow the software version included with your original product. In order to access upgrades and related documentation you must first purchase a service contract from 3Com or your reseller.

Telephone technical support and repair


To enable telephone support and other service benefits, you must first register your product at http://www.h3cnetworks.com/ Warranty and other service benefits start from the date of purchase, so it is important to register your product quickly to ensure you get full use of the warranty and other service benefits available to you. When you contact 3Com for assistance, please have the following information ready: Product model name, part number, and serial number Proof of purchase, if you have not pre-registered your product A list of system hardware and software, including revision level Diagnostic error messages Details about recent configuration changes, if applicable To send a product directly to 3Com for repair, you must first obtain a return authorization number (RMA). Products sent to 3Com, without authorization numbers clearly marked on the outside of the package, will be returned to the sender unopened, at the senders expense. If your product is registered and under warranty, you can obtain an RMA number online at http://www.h3cnetworks.com under support, Repair & Replacement Request. First time users will need to apply for a user name and password.

34

Contact us
3Com offers telephone, e-mail and internet access to technical support and repair services. To access these services for your region, use the appropriate telephone number, URL or e-mail address. Find a current directory of contact information posted on the web http://www.h3cnetworks.com under Support, Technical Support Contact. site at

35

Acronyms
#ABCDEFGHIKLMNOPQRSTUVWXZ
Acronym
# 10GE A AAA ABC ABR AC ACK ACL ACS ADSL AF AFI ALG AM AMB ANSI AP ARP AS ASBR ASCII ASE ASIC ASM ASN AT AT ATM Authentication, Authorization and Accounting Activity Based Costing Area Border Router Alternating Current Acknowledgement Access Control List Auto-Configuration Server Asymmetric Digital Subscriber Line Assured Forwarding Address Family Identifier Application Layer Gateway Accounting Management Active Main Board American National Standard Institute Access Point Address Resolution Protocol Autonomous System Autonomous System Boundary Router American Standard Code for Information Interchange Application service element Application Specific Integrated Circuit Any-Source Multicast Auxiliary Signal Network Advanced Technology Adjacency Table Asynchronous Transfer Mode 36 Ten-GigabitEthernet Return

Full spelling
Return

Acronym
AUX AVF B BC BDR BE BFD BGP BIMS BOOTP BPDU BRI BSR BT BS BT C C-BSR C-RP CA CA CAR CBS CBT CBQ CBR CBT CCITT CDP CE CF-Card CFD CFM CHAP

Full spelling
Auxiliary (port) Active Virtual Forwarder Return Bearer Control Backup Designated Router Best Effort Bidirectional Forwarding Detection Border Gateway Protocol Branch Intelligent Management System Bootstrap Protocol Bridge Protocol Data Unit Basic Rate Interface Bootstrap Router BitTorrent BSR State Burst Tolerance Return Candidate Bootstrap Router Candidate Rendezvous Point Call Appearance Certificate Authority Committed Access Rate Committed Burst Size Core-Based Tree Class Based Queuing Constant Bit Rate Core-Based Tree International Telephone and Telegraph Consultative Committee Cisco Discovery Protocol Customer Edge Compact Flash Card Connectivity Fault Detection Configuration File Management Challenge Handshake Authentication Protocol 37

Acronym
CIDR CIR CIST CLI CLV CLNP CPE CPOS CPU CQ CR CRC CR-LSP CR-LDP CSMA/CD CSNP CSPF CST CT CV CVLAN D DAD DAR DCE DD DDN DHCP DiffServ DIS DLCI DLDP DNS DoD

Full spelling
Classless Inter-Domain Routing Committed Information Rate Common and Internal Spanning Tree Command Line Interface Code/Length/Value Connectionless Network Protocol Customer Premise Equipment Channelized POS Central Processing Unit Custom Queuing Carriage Return Cyclic Redundancy Check Constraint-based Routing LSP Constraint-based Routing LDP Carrier Sense Multiple Access/Collision Detect Complete SNP Constraint Shortest Path First Common Spanning Tree Call Transfer Connectivity Verification Customer Virtual Local Area Network Return Duplicate Address Detection Deeper Application Recognition Data Circuit-terminal Equipment Database Description Digital Data Network Dynamic Host Configuration Protocol Differentiated Service Designated Intermediate System Data Link Connection Identifier Device Link Detection Protocol Domain Name System Downstream on Demand 38

Acronym
DoS DR DSCP DSP DTE DU DUID DUID-LL D-V DVMRP DWDM E EBGP EACL EAD EAP EAPOL EBS EF EGP ES ES-IS F FCoE FC FCS FDB FDDI FDI FEC FFD FG FIB FIFO

Full spelling
Denial of Service Designated Router Differentiated Services Code point Priority Digital Signal Processor Data Terminal Equipment Downstream Unsolicited DHCP Unique Identifier DUID based Link Layer address Distance Vector Routing Algorithm Distance Vector Multicast Routing Protocol Dense Wavelength Division Multiplexing Return External Border Gateway Protocol Enhanced ACL Endpoint Admission Defense Extensible Authentication Protocol Extensible Authentication Protocol over LAN Excess Burst Size Expedited Forwarding Exterior Gateway Protocol End System End System-Intermediate System Return Fabric Channel over Ethernet Forwarding Class Frame Check Sequence Forwarding Database Fiber Distributed Data Interface Forward Defect Indication Forwarding Equivalence Class Fast Failure Detection Forwarding Group Forwarding information base First In First Out 39

Acronym
FQDN FR FRR FRTT FSM FT FTP G GARP GE GR GRE GTS GVRP H HA HABP HDLC HEC HMAC HoPE HoVPN HQoS HSB HTTP H-VPLS HVRP HWTACACS I IA IANA IBGP IBM ICMP

Full spelling
Full Qualified Domain Name Frame Relay Fast Reroute Fairness Round Trip Time Finite State Machine Functional Test File Transfer Protocol Return Generic Attribute Registration Protocol Gigabit Ethernet Graceful Restart Generic Routing Encapsulation Generic Traffic Shaping GARP VLAN Registration Protocol Return High Availability HW Authentication Bypass Protocol High-level Data Link Control Header Error Control Hash-based Message Authentication Code Hierarchy of PE Hierarchy of VPN Hierarchical Quality of Service Hot Standby Hyper Text Transport Protocol Hierarchy of VPLS Hierarchy VLAN Register Protocol HUAWEI Terminal Access Controller Access Control System Return Incoming Access or Identity Association Internet Assigned Number Authority Internal Border Gateway Protocol International Business Machines Internet Control Message Protocol 40

Acronym
ICPIF ICMPv6 ID IEEE IETF IGMP IGMP-Snooping IGP ILM ILS IN IntServ IP IPC IPng IPSec IPTN IPv6 IPX IRDP IRF IS ISATAP ISDN IS-IS ISO ISP ISSU IST ITU-T K KB KEK

Full spelling
Calculated Planning Impairment Factor Internet Control Message Protocol for IPv6 Identification/Identity Institute of Electrical and Electronics Engineers Internet Engineering Task Force Internet Group Management Protocol Internet Group Management Protocol Snooping Interior Gateway Protocol Incoming Label Map Internet Locator Service Intelligent Network Integrated Service Internet Protocol Inter-Process Communication IP Next Generation IP Security IP Phone Telephony Network Internet protocol version 6 Internet Packet Exchange ICMP Router Discovery Protocol Intelligent Resilient Framework or Intermediate Routing Function Intermediate System Intra-Site Automatic Tunnel Addressing Protocol Integrated Services Digital Network Intermediate System-to-Intermediate information exchange protocol System intra-domain routing

International Organization for Standardization Internet service provider In Service Software Upgrade Internal Spanning Tree International Telecommunication Standardization Sector Union Telecommunication Return Kilobyte Key-encrypting key 41

Acronym
L L2TP L2VPN L3VPN LACP LACPDU LAN LCP LDAP LDP LER LFIB LIB LLC LLDP LLDPDU LOC LOG LR LRTT LS LSA LSAck LSDB LSP LSPAGENT LSPDU LSPM LSR LSR LSR-ID LSU LVF M

Full spelling
Return Layer 2 Tunneling Protocol Layer 2 Virtual Private Network Layer 3 Virtual Private Network Link Aggregation Control Protocol Link Aggregation Control Protocol Data Unit Local Area Network Link Control Protocol Lightweight Directory Access Protocol Label Distribution Protocol Label Edge Router Label Forwarding Information Base Label Information Base Link Layer Control Link Layer Discovery Protocol Link Layer Discovery Protocol Data Units Loss of continuity Call Logging Line Rate Loop Round Trip Time Link State Link State Advertisement Link State Acknowledgment Link State Database Label Switch Path Label Switched Path AGENT Link State Protocol Data Unit Label Switch Path Management Link State Request or Label Switching Route Label Switch Router Label Switch Router Identity Link State Update Listening Virtual Forwarder Return 42

Acronym
MAC MAD MAN MaxBC MBGP MCE MD MDI MDS MDT MED MFF MIB MLD MLD-Snooping MMC MODEM MOS MP MP-BGP MPE MP-group MPLS MPLSFW MPM MSC MSDP MSOH MSTI MSTP MT MTBF MTI MTTR

Full spelling
Media Access Control Multi-Active Detection Metropolitan Area Network Max Bandwidth Constraints Multicast Border Gateway Protocol Multi-VPN instance Customer Edge Multicast Domain Medium Dependent Interface Message-Digest Algorithm 5 Multicast Distribution Tree Multi-Exit Discriminator MAC Forced Forwarding Management Information Base Multicast Listener Discovery Protocol Multicast Listener Discovery Snooping Meet-Me Conference Modulator/Demodulator Mean Opinion Scores Multilink PPP Multiprotocol extensions for BGP-4 Middle-level PE Multilink Point to Point Protocol group Multiprotocol Label Switching Multi-protocol Label Switch Forward Multicast Port Management Mobile Switching Center Multicast Source Discovery Protocol Multiplex Section Overhead Multi-Spanning Tree Instance Multiple Spanning Tree Protocol Multicast Tunnel Mean Time Between Failure Multicast Tunnel Interface Mean Time To Repair 43

Acronym
MTU MVRF N NAPT NAPT-PT NAS NAT NBMA NBT NCP ND NDA NDC NDP NET NetBIOS NHLFE NLB NLPID NLRI NMS NPDU NPE NQA NS NSAP NSC N-SEL NSR NSSA NTDP NTP O OAM

Full spelling
Maximum Transmission Unit Multicast VPN Routing and Forwarding Return Network Address Port Translation Network Address Port Translation Protocol Translation Network Access Server Net Address Translation Non Broadcast Multi-Access NetBIOS over TCP/IP Network Control Protocol Neighborhood discovery NetStream Data Analyzer Network Data Collector Neighbor Discovery Protocol Network Entity Title Network Basic Input/Output System Next Hop Label Forwarding Entry Network Load Balancing Network Layer Protocol Identifier Network Layer Reachability Information Network Management Station Network Protocol Data Unit Network Provider Edge Network Quality Analyzer Neighbor Solicitation Network Service Access Point NetStream Collector NSAP Selector Non-Stop Routing Not-So-Stubby Area Neighbor Topology Discovery Protocol Network Time Protocol Return Operation Administration and Maintenance 44

Acronym
OAMPDU OC-3 OID OL OSI ORF OSPF P P P2MP P2P PAP PBR PCB PCM PD PDU PE PHP PHY PIM PIM-DM PIM-SM PIR PKCS PKI PMTU PoE POP POS PPP PPTP PPVPN PQ

Full spelling
OAM Protocol Data Units OC-3 Object Identifier Optical Line Open Systems Interconnection Outbound Route Filter Open Shortest Path First Return Provider Point to MultiPoint Point To Point Password Authentication Protocol Policy-based Route Printed Circuit Board Pulse Code Modulation Powered Device, Prefix Delegation or Pure Data Protocol Data Unit Provider Edge, Provider Edge Device Penultimate Hop Popping Physical layer Protocol Independent Multicast Protocol Independent Multicast-Dense Mode Protocol Independent Multicast-Sparse Mode Peak Information Rate Public Key Cryptography Standards Public Key Infrastructure Path MTU Power over Ethernet Point Of Presence Packet Over SDH Point-to-Point Protocol Point to Point Tunneling Protocol Provider-provisioned Virtual Private Network Priority Queuing 45

Acronym
PRC PRI PS PSE PSNP PTMP or P2MP PTP or P2P PVC PW PXE Q QACL QinQ QoS QQIC QRV R RA RADIUS RAM RD RD RED RFC RIP RIPng RM RMON ROM RP RPC RPF RPR RPT

Full spelling
Primary Reference Clock Primary Rate Interface Protection Switching Power Sourcing Equipment Partial SNP Point-to-Multipoint Point-to-Point Permanent Virtual Channel Pseudo wires Pre-boot Execution Environment Return QoS/ACL 802.1Q in 802.1Q Quality of Service Querier's Query Interval Code Querier's Robustness Variable Return Registration Authority or Router Advertisement Remote Authentication Dial in User Service random-access memory Routing Domain Router Distinguisher Random Early Detection Request For comments Routing Information Protocol RIP next generation Route management Remote Monitoring Read Only Memory Rendezvous Point Remote Procedure Call Reverse Path Forwarding Resilient Packet Ring Rendezvous Point Tree 46

Acronym
RRPP RS RSB RSOH RSTP RSVP RSVP-TE RT RTCP RTE RTP RTP S SA SBM SCFF SD SDH SEL SETS SF SFM SFTP Share-MDT SIP Site-of-Origin SLA SMB SMTP SNAP SNMP SNP SNPA SOH

Full spelling
Rapid Ring Protection Protocol Router Solicitation Reservation State Block Regenerator Section Overhead Rapid Spanning Tree Protocol Resource Reservation Protocol Resource Reservation Protocol Traffic Engineering Route Target Real-time Transport Control Protocol Route Table Entry Real-time Transport Protocol Real-time Transport Protocol Return Source Active or Suppress Advertisement Sub-network Bandwidth Management Single Choke Fairness Frame Signal Degrade Synchronous Digital Hierarchy Selector Synchronous Equipment Timing Source Sampling Frequency Source-Filtered Multicast Secure FTP Share-Multicast Distribution Tree Session Initiation Protocol Site-of-Origin Service Level Agreement Standby Main Board Simple Mail Transfer Protocol Sub Network Access Point Simple Network Management Protocol Sequence Number Packet Sub-network Points of Attachment Section Overhead 47

Acronym
SONET SOO SP SPE SPF SPT SRPT SSH SSM SSM ST STM-1 STM-16 STM-16c STM-4c STP SVC SVLAN Switch-MDT SYN T TA TACACS TDM TCP TCN TE TEDB TFTP TLS TLV ToS TP TPID

Full spelling
Synchronous Optical Network Site-of-Origin Strict Priority Queuing Superstratum PE/Sevice Provider-end PE Shortest Path First Shortest Path Tree Sub-ring Packet Tunnel Secure Shell Synchronization Status Marker Source-Specific Multicast Shared Tree SDH Transport Module -1 SDH Transport Module -16 SDH Transport Module -16c SDH Transport Module -4c Spanning Tree Protocol Signaling Virtual Connection Service Provider Virtual Local Area Network Switch-Multicast Distribution Tree Synchronize Return Terminal Adapter Terminal Access Controller Access Control System Time Division Multiplexing Transmission Control Protocol Topology Change Notification Traffic Engineering Traffic Engineering Database Trivial File Transfer Protocol Transparent LAN Service Type-Length-Value Type of Service Traffic Policing Tag Protocol Identifier 48

Acronym
TRIP TS TTL TTY U U/L UDP UPE URL URPF USM V VBR VCI VE VF VFS VLAN VLL VOD VoIP VOS VPDN VPDN VPI VPLS VPN VRID VRRP VSI VT VTY W WAN

Full spelling
Trigger RIP Traffic Shaping Time to Live True Type Terminal Return Universal/Local User Datagram Protocol Under-layer PE or User-end PE Uniform Resource Locators Unicast Reverse Path Forwarding User-Based Security Model Return Variable Bit Rate Virtual Channel Identifier Virtual Ethernet Virtual Forwarder Virtual File System Virtual Local Area Network Virtual Leased Lines Video On Demand Voice over IP Virtual Operate System Virtual Private Dial-up Network Virtual Private Data Network Virtual Path Identifier Virtual Private Local Switch Virtual Private Network Virtual Router ID Virtual Router Redundancy Protocol Virtual Switch Interface Virtual Tributary Virtual Type Terminal Return Wide Area Network 49

Acronym
WFQ WINS WLAN WRED WRR WTR WWW X XGE Z ZBR

Full spelling
Weighted Fair Queuing Windows Internet Naming Service wireless local area network Weighted Random Early Detection Weighted Round Robin Wait-to-Restore World Wide Web Return Ten-GigabitEthernet Return Zone Border Router

50

Index
accessing master (IRF).............................................. 30 subordinate (IRF) ...................................... 30 virtual device (IRF) .................................... 30 application IRF........................................................... 10 auto upgrade boot file (IRF)............................28 concept IRF basics ................................................. 1 1 configuring IRF........................................................... 10 IRF virtual device ....................................... 31 ports (IRF) .................................................25 virtual device (IRF) ............................... 24, 25 connection medium (IRF) ............................................. 12 physical (IRF) ............................................ 12 requirements (IRF) ...................................... 13 correspondence between an IRF port and a physical IRF port . 14 device accessing (IRF) ......................................... 30 accessing master (IRF) ............................... 30 accessing subordinate (IRF)........................ 30 configuring (IRF) .................................. 24, 25 displaying (IRF) ......................................... 31 maintaining (IRF) ....................................... 31 maintaining topology (IRF) .......................... 23 displaying IRF virtual device ....................................... 31
51

enabling boot file auto upgrade (IRF) ........................ 28 event link-down (IRF) .......................................... 29 facilities connection medium (IRF) ............................ 12 file enabling auto upgrade of boot file (IRF) ....... 28 managing configuration file (IRF)................. 23 system name (IRF)...................................... 21 interface name (IRF)................................................ 20 IRF accessing master ...................................... 30 accessing subordinate ............................... 30 accessing virtual device ............................. 30 application............................................... 10 basic concepts........................................... 1 1 configuration ............................................ 10 configuration file management .................... 23 configuring ports....................................... 25 configuring virtual device ................ 24, 25, 31 connection medium ................................... 12 connection requirements ............................ 13 correspondence between an IRF port and a physical IRF port .................................... 14 displaying virtual device ............................ 31 enabling boot file auto upgrade ................. 28 file system name ....................................... 21 interface name ......................................... 20

maintaining virtual device........................... 31 member ID ............................................... 18 member priority ........................................ 12 physical connection ................................... 12 physical port ............................................. 1 1 port ......................................................... 1 1 role ......................................................... 1 1 role election .............................................. 18 setting link layer report delay time ...............29 specifying MAC address bridge preservation time...................................................... 27 specifying priority for member device........... 27 topology .................................................. 14 topology collection .................................... 17 virtual device maintenance ......................... 18 virtual device management ......................... 18 virtual device merge .................................. 1 1 virtual device partition................................ 12 virtual device topology maintenance ............ 23 working process ........................................ 12 link setting layer report delay time (IRF) ..............29 link-down event (IRF) ......................................29 MAC address specifying bridge preservation time (IRF) ...... 27 maintaining IRF virtual device ....................................... 31 virtual device (IRF) ..................................... 18 virtual device topology (IRF) ........................ 23 managing configuration file (IRF) ................................ 23 virtual device (IRF) ..................................... 18 member ID (IRF) ..................................................... 18
52

setting ID for device (IRF) ............................ 26 specifying priority for device (IRF) ................ 27 member priority (IRF) .................................... 12 merging virtual device (IRF) ......................................1 1 name file system (IRF) ......................................... 21 interface (IRF) ........................................... 20 network management connection medium (IRF) ............................ 12 connection requirements (IRF) ..................... 13 topology (IRF) ........................................... 14 topology collection (IRF) ............................. 17 virtual device configuration (IRF).................. 31 partitioning virtual device (IRF) ..................................... 12 physical port (IRF) .......................................... 1 1 port configuring (IRF)........................................ 25 correspondence between an IRF port and a physical IRF port .................................... 14 port (IRF) ...................................................... 1 1 preservation time of bridge MAC address (IRF) 27 priority member (IRF) ............................................ 12 procedure accessing virtual device (IRF) ...................... 30 accessing virtual device master (IRF) ............ 30 accessing virtual device subordinate (IRF) ..... 30 configuring an IRF virtual device ................. 32 configuring ports (IRF) ................................ 25 enabling boot file auto upgrade (IRF)........... 28 setting link layer report delay time (IRF) ........ 29 setting member ID for device (IRF) ............... 26

specifying MAC address bridge preservation time (IRF) ............................................... 27 specifying priority for member device (IRF) .... 27 process working (IRF) ............................................ 12 role election (IRF) ............................................. 18 role (IRF) ...................................................... 1 1 setting link layer report delay time (IRF) ..................29 member ID for device (IRF) .......................... 26 specifying MAC address bridge preservation time (IRF) . 27 priority for member device (IRF) ................... 27 switching

setting member ID for device (IRF) ............... 26 specifying priority for member device (IRF) ... 27 topology IRF ..................................................... 14, 17 maintaining virtual device (IRF) ................... 23 role election (IRF) ...................................... 18 virtual device accessing (IRF) .......................................... 30 accessing master (IRF) ............................... 30 accessing subordinate (IRF) ........................ 30 configuring (IRF)............................. 24, 25, 31 displaying (IRF) ......................................... 31 maintaining (IRF) ....................................... 31 merge (IRF)................................................ 1 1 partition (IRF) ............................................ 12

53

Vous aimerez peut-être aussi