H3C S5820X&S5800 Series Ethernet Switches

Transcription

1 H3C S5820X&S5800 Series Ethernet Switches High Availability Configuration Guide Hangzhou H3C Technologies Co., Ltd. Document Version: 6W Product Version: Release 1110

2 Copyright , 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,, H 3 Care,, TOP G,, IRF, NetPilot, Neocean, NeoVTL, SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V 2 G, V n 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. 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.

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. The High Availability Configuration Guide describes high availability fundamentals and configuration. The high availability technologies include fault detection and fault failover. Failure detection technologies focus on fault detection and isolation. Failover technologies focus on network recovery. This preface includes: Audience Document Organization Conventions About the H3C S5820X&S5800 Documentation Obtaining Documentation Documentation Feedback Audience This documentation set is intended for: Network planners Field technical support and servicing engineers Network administrators working with the S5800 and S5820X series Document Organization The High Availability Configuration Guide comprises these parts: High Availability Overview Ethernet OAM Configuration CFD Configuration DLDP Configuration RRPP Configuration Smart Link Configuration Monitor Link Configuration VRRP Configuration BFD Configuration Track Configuration Conventions This section describes the conventions used in this documentation set. Command conventions Convention Boldface italic [ ] 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.

4 Convention { x y... } [ x y... ] { x y... } * [ x y... ] * &<1-n> Description 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 Boldface > Convention Description Window names, button names, field names, and menu items are in Boldface. For example, the New User window appears; click OK. Multi-level menus are separated by angle brackets. For example, File > Create > Folder. Symbols Convention 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 a complementary description. About the H3C S5820X&S5800 Documentation Set The H3C S5800&S5820X documentation set also includes: Category Documents Purposes Product description and specifications Pluggable module description Marketing brochures Technology white papers PSR150-A [ PSR150-D ] Power Modules User Manual PSR300-12A [ PSR300-12D1 ] Power Modules User Manual Describe product specifications and benefits. Provide an in-depth description of software features and technologies. Describes the appearances, features, specifications, installation, and removal of the pluggable 150W power modules available for the products. Describes the appearances, features, specifications, installation, and removal of the pluggable 300W power modules available for the products.

5 Category Documents Purposes Power configuration Hardware installation PSR750-A [ PSR750-D ] Power Modules User Manual RPS User Manual LSW1FAN and LSW1BFAN Installation Manual LSW148POEM Module User Manual S5820X [ S5800 ] Series Ethernet Switches Interface Cards User Manual H3C OAP Cards User Manual H3C Low End Series Ethernet Switches Pluggable Modules Manual S C-PWR Ethernet Switch Hot Swappable Power Module Ordering Guide RPS Ordering Information for H3C Low-End Ethernet Switches S5800 Series Ethernet Switches Quick Start S5820X Series Ethernet Switches Quick Start S5800 Series Ethernet Switches CE DOC S5820X Series Ethernet Switches CE DOC S5800 Series Ethernet Switches Quick Start S5820X Series Ethernet Switches Quick Start S5800 Series Ethernet Switches Installation Manual S5820X Series Ethernet Switches Installation Manual Pluggable SFP[SFP+][XFP] Transceiver Modules Installation Guide S C-PWR Switch Video Installation Guide S5820X-28C Switch Video Installation Guide Describes the appearances, features, specifications, installation, and removal of the pluggable 750W power modules available for the products. Describes the appearances, features, and specifications of the RPS units available for the products. Describes the appearances, specifications, installation, and removal of the pluggable fan modules available for the products. Describes the appearance, features, installation, and removal of the pluggable PoE module available for the products. Describes the models, hardware specifications, installation, and removal of the interface cards available for the products. Describes the benefits, features, hardware specifications, installation, and removal of the OAP cards available for the products. Describes the models, appearances, and specifications of the pluggable modules available for the products. Guides you through ordering the hot-swappable power modules available for the S C-PWR switches in different cases. Provides the RPS and switch compatibility matrix and RPS cable specifications. 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. Guides you through installing SFP/SFP+/XFP transceiver modules. Shows how to install the H3C S C-PWR and H3C S5820X-28C Ethernet switches.

6 Category Documents Purposes Software configuration Operations and maintenance Configuration guide Command reference H3C Series Ethernet Switches Login Password Recovery Manual Release notes Describe software features and configuration procedures. Provide a quick reference to all available commands. Tells how to find the lost password or recover the password when the login password is lost. Provide information about the product release, including the version history, hardware and software compatibility matrix, version upgrade information, technical support information, and software upgrading. Obtaining Documentation You can access the most up-to-date H3C product documentation on the World Wide Web at 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 your comments about product documentation to info@h3c.com. We appreciate your comments.

7 Table of Contents 1 High Availability Overview 1-1 Availability Requirements 1-1 Availability Evaluation 1-1 High Availability Technologies 1-2 Fault Detection Technologies 1-2 Protection Switchover Technologies Ethernet OAM Configuration 2-1 Ethernet OAM Overview 2-1 Background 2-1 Major Functions of Ethernet OAM 2-1 Ethernet OAMPDUs 2-2 How Ethernet OAM Works 2-3 Standards and Protocols 2-6 Ethernet OAM Configuration Task List 2-6 Configuring Basic Ethernet OAM Functions 2-7 Configuring Link Monitoring 2-7 Configuring Errored Symbol Event Detection 2-7 Configuring Errored Frame Event Detection 2-8 Configuring Errored Frame Period Event Detection 2-8 Configuring Errored Frame Seconds Event Detection 2-9 Enabling OAM Remote Loopback 2-9 Displaying and Maintaining Ethernet OAM Configuration 2-10 Ethernet OAM Configuration Example CFD Configuration 3-1 Overview 3-1 Basic Concepts in CFD 3-1 CFD Functions 3-4 Protocols and Standards 3-5 CFD Configuration Task List 3-5 Configuring Basic CFD Settings 3-6 Enabling CFD 3-6 Configuring the CFD Protocol Version 3-6 Configuring Service Instances 3-6 Configuring MEPs 3-7 Configuring MIP Generation Rules 3-8 Configuring CFD Functions 3-9 Configuration Prerequisites 3-9 Configuring CC on MEPs 3-9 Configuring LB on MEPs 3-10 Configuring LT on MEPs 3-10 i

8 Displaying and Maintaining CFD 3-11 CFD Configuration Example DLDP Configuration 4-1 Overview 4-1 Background 4-1 How DLDP Works 4-2 DLDP Configuration Task List 4-9 Enabling DLDP 4-10 Setting DLDP Mode 4-10 Setting the Interval for Sending Advertisement Packets 4-11 Setting the DelayDown Timer 4-11 Setting the Port Shutdown Mode 4-12 Configuring DLDP Authentication 4-12 Resetting DLDP State 4-13 Displaying and Maintaining DLDP 4-14 DLDP Configuration Examples 4-14 Automatically Shutting Down Unidirectional Links 4-14 Manually Shutting Down Unidirectional Links 4-17 Troubleshooting DLDP RRPP Configuration 5-1 RRPP Overview 5-1 Background 5-1 Basic Concepts in RRPP 5-2 RRPPDUs 5-4 RRPP Timers 5-5 How RRPP Works 5-5 Typical RRPP Networking 5-7 Protocols and Standards 5-10 RRPP Configuration Task List 5-10 Creating an RRPP Domain 5-11 Configuring Control VLANs 5-11 Configuring Protected VLANs 5-12 Configuring RRPP Rings 5-13 Configuring RRPP Ports 5-13 Configuring RRPP Nodes 5-14 Activating an RRPP Domain 5-16 Configuring RRPP Timers 5-17 Configuring an RRPP Ring Group 5-17 Displaying and Maintaining RRPP 5-18 RRPP Configuration Examples 5-19 Single Ring Configuration Example 5-19 Intersecting Ring Configuration Example 5-21 Intersecting-Ring Load Balancing Configuration Example 5-25 Troubleshooting 5-33 ii

9 6 Smart Link Configuration 6-35 Smart Link Overview 6-35 Background 6-35 Terminology 6-36 How Smart Link Works 6-37 Smart Link Collaboration Mechanisms 6-38 Smart Link Configuration Task List 6-38 Configuring a Smart Link Device 6-39 Configuration Prerequisites 6-39 Configuring Protected VLANs for a Smart Link Group 6-39 Configuring Member Ports for a Smart Link Group 6-40 Configuring Role Preemption for a Smart Link Group 6-40 Enabling the Sending of Flush Messages 6-41 Configuring an Associated Device 6-42 Enabling the Receiving of Flush Messages 6-42 Displaying and Maintaining Smart Link 6-42 Smart Link Configuration Examples 6-43 Single Smart Link Group Configuration Example 6-43 Multiple Smart Link Groups Load Sharing Configuration Example Monitor Link Configuration 7-1 Overview 7-1 Terminology 7-1 How Monitor Link Works 7-2 Configuring Monitor Link 7-2 Configuration Prerequisites 7-2 Creating a Monitor Link Group 7-2 Configuring Monitor Link Group Member Ports 7-3 Displaying and Maintaining Monitor Link 7-3 Monitor Link Configuration Example VRRP Configuration 8-1 VRRP Overview 8-1 VRRP Standard Protocol Mode 8-2 Introduction to VRRP Group 8-2 VRRP Timers 8-4 Packet Format 8-5 Principles of VRRP 8-6 VRRP Tracking 8-6 VRRP Application (Taking IPv4-Based VRRP for Example) 8-7 VRRP Load Balancing Mode 8-9 Overview 8-9 Assigning Virtual MAC Addresses 8-9 Virtual Forwarder 8-11 Packet Types 8-13 Configuring VRRP for IPv VRRP for IPv4 Configuration Task List 8-14 iii

10 Configuring a VRRP Working Mode 8-15 Specifying the Type of MAC Addresses Mapped to Virtual IP Addresses 8-15 Creating a VRRP Group and Configuring Virtual IP Address 8-16 Configuring Router Priority, Preemptive Mode and Tracking Function 8-17 Configuring VF Tracking 8-18 Configuring VRRP Packet Attributes 8-19 Enabling the Trap Function for VRRP 8-20 Displaying and Maintaining VRRP for IPv Configuring VRRP for IPv VRRP for IPv6 Configuration Task List 8-21 Specifying the Type of MAC Addresses Mapped to Virtual IPv6 Addresses 8-22 Creating a VRRP Group and Configuring a Virtual IPv6 Address 8-23 Configuring Router Priority, Preemptive Mode and Tracking Function 8-24 Configuring VF Tracking 8-25 Configuring VRRP Packet Attributes 8-26 Displaying and Maintaining VRRP for IPv IPv4-Based VRRP Configuration Examples 8-28 Single VRRP Group Configuration Example 8-28 VRRP Interface Tracking Configuration Example 8-30 VRRP with Multiple VLANs Configuration Example 8-34 VRRP Load Balancing Mode Configuration Example 8-36 IPv6-Based VRRP Configuration Examples 8-44 Single VRRP Group Configuration Example 8-44 VRRP Interface Tracking Configuration Example 8-47 VRRP with Multiple VLANs Configuration Example 8-51 VRRP Load Balancing Mode Configuration Example 8-54 Troubleshooting VRRP BFD Configuration 9-1 Introduction to BFD 9-1 How BFD Works 9-1 BFD Packet Format 9-4 Supported Features 9-6 Protocols and Standards 9-6 Configuring BFD Basic Functions 9-6 Configuration Prerequisites 9-6 Configuration Procedure 9-7 Enabling Trap 9-8 Displaying and Maintaining BFD Track Configuration 10-1 Track Overview 10-1 Background 10-1 Introduction to Track 10-1 Collaboration Fundamentals 10-2 Track Application Example 10-3 Track Configuration Task List 10-3 iv

11 Associating the Track Module with a Detection Module 10-3 Associating Track with NQA 10-3 Associating Track with BFD 10-4 Associating Track with Interface Management 10-5 Associating the Track Module with an Application Module 10-5 Associating Track with VRRP 10-5 Associating Track with Static Routing 10-7 Displaying and Maintaining Track Entries 10-9 Track Configuration Examples 10-9 VRRP-Track-NQA Collaboration Configuration Example (The Master Monitors the Uplink) 10-9 Configuring BFD for a VRRP Backup to Monitor the Master Configuring BFD for the VRRP Master to Monitor the Uplinks Static Routing-Track-NQA Collaboration Configuration Example Static Routing-Track-BFD Collaboration Configuration Example VRRP-Track-Interface Management Collaboration Configuration Example (The Master Monitors the Uplink Interface) Index 11-1 v

12 1 High Availability Overview With the wide deployment of various types of value-added services such as IPTV and video conference, communication interruption may affect these services and result in serious lost. Therefore, as the carrier of services, the availability of basic network infrastructures is becoming a great concern. In an actual network, increasing fault tolerance capabilities of a system, increasing fault recovery speed, and reducing impact of faults on services are effective ways to enhance system availability. Availability Requirements Availability requirements fall into three levels based on purpose and implementation, as shown in Table 1-1. Table 1-1 Availability requirements Level Purpose Implementation 1 2 Decrease system software and hardware faults Protect system functions from being affected if faults occur Hardware: Simplifying circuit design, enhancing production techniques, and performing reliability tests. Software: Reliability design and test Device and link redundancy and deployment of switchover strategies 3 Enable the system to recover fast even if system functions are affected. Providing fault detection, diagnosis, isolation, and recovery technologies Among the availability requirements, the availability requirement of level 1 should be considered during the design and production process of network devices; the availability requirement of level 2 should be considered at the design of network infrastructure; the availability requirement of level 3 should be met by adopting corresponding high availability technologies during the deployment of a network according to the network infrastructure and service characteristics. This manual describes these high availability technologies. Availability Evaluation Typically, Mean Time Between Failures (MTBF) and Mean Time to Repair (MTTR) are used to evaluate the availability of a network. MTBF MTBF is the predicted elapsed time between inherent failures of a system during operation. It is typically in the unit of hours. A higher MTBF means a high availability. 1-1

13 MTTR MTTR is the average time required to repair a failed system. MTTR in a broad sense also involves spare parts management and customer services. MTTR = fault detection time + hardware replacement time + system initialization time + link recovery time + routing time + forwarding recovery time. A smaller value of each item, a smaller MTTR and a higher availability. High Availability Technologies As previously mentioned, increasing MTBF or decreasing MTTR can enhance the availability of a network. The high availability technologies described in this section meet the level 3 high availability requirements in the aspect of decreasing MTTR. High availability technologies can be classified into fault detection technologies and protection switchover technologies. Fault Detection Technologies Fault detection technologies enable detection and diagnosis of network faults. CFD, DLDP and Ethernet OAM are data link layer fault detection technologies; BFD is a generic fault detection technology that can be used at any layer; NQA is used for diagnosis and evaluation of network quality; Monitor Link and Track work along with other high availability technologies to detect faults through a collaboration mechanism. See Table 1-2 for the details of these technologies. Table 1-2 Fault detection technologies Technology Introduction Reference CFD DLDP Connectivity Fault Detection (CFD), which conforms to IEEE 802.1ag Connectivity Fault Management (CFM) and ITU-T Y.1731, is an end-to-end per-vlan link layer Operations, Administration and Maintenance (OAM) mechanism used for link connectivity detection, fault verification, and fault location. The Device link detection protocol (DLDP) deals with unidirectional links that may occur in a network. On detecting a unidirectional link, DLDP, as configured, can shut down the related port automatically or prompt users to take actions to avoid network problems. High Availability Configuration Guide/CFD Configuration High Availability Configuration Guide/DLDP Configuration Ethernet OAM As a tool monitoring Layer 2 link status, Ethernet OAM is mainly used to address common link-related issues on the last mile. You can monitor the status of the point-to-point link between two directly connected devices by enabling Ethernet OAM on them. High Availability Configuration Guide/Ethernet OAM Configuration BFD Bidirectional forwarding detection (BFD) provides a single mechanism to quickly detect and monitor the connectivity of links or IP forwarding in networks. To improve network performance, devices must quickly detect communication failures to restore communication through backup paths as soon as possible. High Availability Configuration Guide/BFD Configuration 1-2

14 Technology Introduction Reference NQA Network Quality Analyzer (NQA) analyzes network performance, services and service quality through sending test packets, and provides you with network performance and service quality parameters such as jitter, TCP connection delay, FTP connection delay and file transfer rate. Network Management and Monitoring Configuration Guide/NQA Configuration Monitor Link Monitor link is a port collaboration function. It is usually used in conjunction with Layer 2 topology protocols. The idea is to monitor the states of uplink ports and adapt the up/down state of downlink ports to the up/down state of uplink ports, triggering link switchover on the downstream device in time. High Availability Configuration Guide/Monitor Link Configuration Track The track module is used to implement collaboration between different modules. The collaboration here involves three parts: the application modules, the track module, and the detection modules. These modules collaborate with one another through collaboration entries. That is, the detection modules trigger the application modules to perform certain operations through the track module. More specifically, the detection modules probe the link status, network performance and so on, and inform the application modules of the detection result through the track module. Upon aware of the changes of network status, the application modules deal with the changes accordingly to avoid communication interruption and network performance degradation. High Availability Configuration Guide/Track Configuration Protection Switchover Technologies Protection switchover technologies aim at recovering network faults. They back up hardware, link, routing, and service information for switchover in case of network faults to ensure continuity of network services. See Table 1-3 for the details of protection switchover technologies. Table 1-3 Protection switchover technologies Technology Introduction Reference Ethernet Link Aggregation Ethernet link aggregation, most often simply called link aggregation, aggregates multiple physical Ethernet links into one logical link to increase link bandwidth beyond the limits of any one single link. This logical link is called an aggregate link. It allows for link redundancy because the member physical links can dynamically back up one another. Layer 2 - LAN Switching Configuration Guide /Ethernet Link Aggregation Configuration 1-3

15 Technology Introduction Reference Smart Link MSTP Smart Link is a feature developed to address the slow convergence issue with STP. It provides link redundancy as well as fast convergence in a dual uplink network, allowing the backup link to take over quickly when the primary link fails. As a Layer 2 management protocol, the Multiple Spanning Tree Protocol (MSTP) eliminates Layer 2 loops by selectively blocking redundant links in a network, and in the mean time, allows for link redundancy. High Availability Configuration Guide/Smart Link Configuration Layer 2 - LAN Switching Configuration Guide /MSTP Configuration RRPP The Rapid Ring Protection Protocol (RRPP) is a link layer protocol designed for Ethernet rings. RRPP can prevent broadcast storms caused by data loops when an Ethernet ring is healthy, and rapidly restore the communication paths between the nodes in the event that a link is disconnected on the ring. High Availability Configuration Guide/RRPP Configuration GR VRRP Graceful Restart (GR) ensures the continuity of packet forwarding when a protocol, such as BGP, IS-IS, OSPF, restarts or during an active/standby switchover process. It needs other devices to implement routing information backup and recovery. Virtual Router Redundancy Protocol (VRRP) is an error-tolerant protocol, which provides highly reliable default links on multicast and broadcast LANs such as Ethernet, avoiding network interruption due to failure of a single link. Related chapters in Layer 3 - IP Routing Configuration Guide High Availability Configuration Guide/VRRP Configuration A single high availability technology cannot solve all availability problems in more and more complex network environments. Therefore, various availability technologies are required to enhance network availability on a basis of detailed analysis of network environments and user requirements. For example, at the distribution layer, a redundancy mechanism should be adopted on edge nodes to connect them to the corresponding nodes, and at the core layer, nodes should be meshed. Therefore, to achieve complete high availability, network designers and managers need to take into full consideration during the design, construction, and maintenance of a network. 1-4

16 2 Ethernet OAM Configuration This chapter includes these sections: Ethernet OAM Overview Ethernet OAM Configuration Task List Configuring Basic Ethernet OAM Functions Configuring Link Monitoring Enabling OAM Remote Loopback Displaying and Maintaining Ethernet OAM Configuration Ethernet OAM Configuration Example Ethernet OAM Overview Background With features such as ease of use and low price, Ethernet has gradually become the major underlying technology for today s local area networks (LANs). Recently, with the emergence of Gigabit Ethernet and 10-Gigabit Ethernet, Ethernet is gaining popularity in metropolitan area networks (MANs) and wide area networks (WANs) as well. In the beginning, Ethernet is mainly used in LANs, which have low reliability and stability requirements. This is why an effective management and maintenance mechanism for Ethernet has been absent all along, hindering the usage of Ethernet in MANs and WANs. Implementing Operation, Administration and Maintenance (OAM) on Ethernet networks has now become an urgent matter. As a tool monitoring Layer 2 link status, Ethernet OAM is mainly used to address common link-related issues on the last mile. You can monitor the status of the point-to-point link between two directly connected devices by enabling Ethernet OAM on them. Major Functions of Ethernet OAM Ethernet OAM effectively promotes your management and maintenance capabilities over Ethernet networks, guaranteeing the stability of the networks. Its major functions include: Link performance monitoring: Monitors the performance indices of a link, including packet loss, delay, and jitter, and collects traffic statistics of various types. Fault detection and alarm: Checks the connectivity of a link by sending OAM protocol data units (OAMPDUs) and reports to the network administrators when a link error occurs. Remote loopback: Checks the link quality and locates link errors by monitoring the looped back frames. 2-1

17 Ethernet OAMPDUs Ethernet OAM works on the data link layer. Ethernet OAM reports the link status by periodically exchanging OAMPDUs between devices, so that the administrator can effectively manage the network. Figure 2-1 shows the formats of different types of OAMPDUs. Figure 2-1 Formats of different types of Ethernet OAMPDUs The fields in an OAMPDU are described as follows: Table 2-1 Description of the fields in an OAMPDU Field Description Destination MAC address of the Ethernet OAMPDU. Dest addr It is a slow protocol multicast address 0180c As slow protocol packet cannot be forwarded by bridges, Ethernet OAMPDUs cannot be forwarded. Source MAC address of the Ethernet OAMPDU. Source addr Type Subtype Flags Code It is the bridge MAC address of the sending side and is a unicast MAC address. Type of the encapsulated protocol in the Ethernet OAMPDU. The value is 0x8809. The specific protocol being encapsulated in the Ethernet OAMPDU. The value is 0x03. Status information of an Ethernet OAM entity. Type of the Ethernet OAMPDU Throughout this document, a port with Ethernet OAM enabled is called an Ethernet OAM entity or an OAM entity. 2-2

18 Table 2-2 shows the function of the three types of OAMPDUs. Table 2-2 Functions of different types of OAMPDUs OAMPDU type Information OAMPDU Event Notification OAMPDU Loopback Control OAMPDU Function Used for transmitting state information of an Ethernet OAM entity (including the information about the local device and remote devices, and customized information) to the remote Ethernet OAM entity and maintaining OAM connections Used by link monitoring to notify the remote OAM entity when it detects problems on the link in between. Used for remote loopback control. By inserting the information used to enable/disable loopback to a loopback control OAMPDU, you can enable/disable loopback on a remote OAM entity. How Ethernet OAM Works This section describes the working procedures of Ethernet OAM. Ethernet OAM connection establishment Ethernet OAM connection is the base of all the other Ethernet OAM functions. OAM connection establishment is also known as the Discovery phase, where an Ethernet OAM entity discovers remote OAM entities and establishes sessions with them. In this phase, interconnected OAM entities notify the peer of their OAM configuration information and the OAM capabilities of the local nodes by exchanging Information OAMPDUs and determine whether Ethernet OAM connections can be established. An Ethernet OAM connection can be established only when the settings concerning loopback, link detecting, and link event of the both sides match. After an Ethernet OAM connection is established, Ethernet OAM takes effect on both sides. As for Ethernet OAM connection establishment, an Ethernet OAM entity operates in active Ethernet OAM mode or passive Ethernet OAM mode. Table 2-3 compares active Ethernet OAM mode with passive Ethernet OAM mode. Table 2-3 Active Ethernet OAM mode and passive Ethernet OAM mode Item Active Ethernet OAM mode Passive Ethernet OAM mode Initiating OAM Discovery Available Unavailable Responding to OAM Discovery Available Available Transmitting Information OAMPDUs Available Available Transmitting Event Notification OAMPDUs Available Available Transmitting Information OAMPDUs without any TLV Available Available 2-3

19 Item Active Ethernet OAM mode Passive Ethernet OAM mode Transmitting Loopback Control OAMPDUs Responding to Loopback Control OAMPDUs Available Available (if both sides operate in active OAM mode) Unavailable Available OAM connections can be initiated only by OAM entities operating in active OAM mode, while those operating in passive mode wait and respond to the connection requests sent by their peers. No OAM connection can be established between OAM entities operating in passive OAM mode. After an Ethernet OAM connection is established, the Ethernet OAM entities on both sides exchange Information OAMPDUs periodically to keep the Ethernet OAM connection valid. If an Ethernet OAM entity receives no Information OAMPDU for five seconds, the Ethernet OAM connection is disconnected. The interval to send Information OAMPDUs is determined by a timer. Up to ten Information OAMPDUs can be sent in a second. Link monitoring Error detection in an Ethernet is difficult, especially when the physical connection in the network is not disconnected but network performance is degrading gradually. Link monitoring is used to detect and indicate link faults in various environments. Ethernet OAM implements link monitoring through the exchange of Event Notification OAMPDUs. Upon detecting a link error event listed in Table 2-4, the local OAM entity sends an Event Notification OAMPDU to notify the remote OAM entity. With the log information, network administrators can keep track of network status in time. Table 2-4 describes the link events. Table 2-4 Ethernet OAM link error events Ethernet OAM link events Errored symbol event Errored frame event Description An errored symbol event occurs when the number of detected symbol errors over a specific detection interval exceeds the predefined threshold. An errored frame event occurs when the number of detected error frames over a specific interval exceeds the predefined threshold. 2-4

20 Ethernet OAM link events Errored frame period event Errored frame seconds event Description An errored frame period event occurs if the number of frame errors in specific number of received frames exceeds the predefined threshold. When the number of error frame seconds detected on a port over a detection interval reaches the error threshold, an errored frame seconds event occurs. The system transforms the period of detecting errored frame period events into the maximum number of 64-byte frames that a port can send in the specific period, that is, the system takes the maximum number of frames sent as the period. The maximum number of frames sent is calculated using this formula: the maximum number of frames = interface bandwidth (bps) errored frame period event detection period (in ms)/( ) If errored frames appear in a certain second, this second is called an errored frame second. Remote fault detection Information OAMPDUs are exchanged periodically among Ethernet OAM entities across established OAM connections. In a network where traffic is interrupted due to device failures or unavailability, the flag field defined in information OAMPDUs allows an Ethernet OAM entity to send error information (the critical link error event type) to its peer. In this way, you can keep track of link status in time through the log information and troubleshoot in time. Table 2-5 lists the critical link events and the transmission frequencies of the corresponding OAMPDUs. Table 2-5 Critical link error events Type Description OAMPDU transmission frequencies Link Fault Peer link signal is lost. Once per second Dying Gasp An unexpected fault, such as power failure, occurred. Non-stop Critical event An undetermined critical event happened. Non-stop 2-5

21 The support of S5800&S5820X series Ethernet switches for information OAMPDUs carrying critical link events is as follows: S5800&S5820X series Ethernet switches are able to receive information OAMPDUs carrying the critical link events listed in Table 2-5. Only the Gigabit optical ports are able send information OAMPDUs carrying Link Fault events. S5800&S5820X series Ethernet switches are able to send information OAMPDUs carrying Dying Gasp events when the device is rebooted or relevant ports are manually shut down. Physical IRF ports, however, are unable to send this type of OAMPDUs. For more information about physical IRF ports, see IRF Configuration in the IRF Configuration Guide. S5800&S5820X series Ethernet switches are unable to send information OAMPDUs carrying Critical Events. Remote loopback Remote loopback is available only after the Ethernet OAM connection is established. With remote loopback enabled, the Ethernet OAM entity operating in active Ethernet OAM mode sends non-oampdus to its peer. After receiving these frames, the peer does not forward them according to their destination addresses. Instead, it returns them to the sender along the original path. Remote loopback enables you to check the link status and locate link failures. Performing remote loopback periodically helps to detect network faults in time. Furthermore, performing remote loopback by network segments helps to locate network faults. Standards and Protocols Ethernet OAM is defined in IEEE 802.3h (Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications). Ethernet OAM Configuration Task List Complete the following tasks to configure Ethernet OAM: Task Remarks Configuring Basic Ethernet OAM Functions Configuring Errored Symbol Event Detection Required Optional Configuring Link Monitoring Configuring Errored Frame Event Detection Configuring Errored Frame Period Event Detection Configuring Errored Frame Seconds Event Detection Optional Optional Optional Enabling OAM Remote Loopback Optional 2-6

22 Configuring Basic Ethernet OAM Functions As for Ethernet OAM connection establishment, an Ethernet OAM entity operates in active mode or passive mode. Only an Ethernet OAM entity in active mode can initiate connection establishment. After Ethernet OAM is enabled on an Ethernet port, according to its Ethernet OAM mode, the Ethernet port establishes an Ethernet OAM connection with its peer port. Follow these steps to configure basic Ethernet OAM functions: To do Use the command Remarks Enter system view System-view Enter Ethernet port view interface interface-type interface-number Optional Set the Ethernet OAM mode oam mode { active passive } The default is active Ethernet OAM mode. Enable Ethernet OAM on the current port oam enable Required Ethernet OAM is disabled by default. To change the Ethernet OAM mode on an Ethernet OAM-enabled port, you must first disable Ethernet OAM on the port. Configuring Link Monitoring After Ethernet OAM connections are established, the link monitoring periods and thresholds configured in this section take effect on all Ethernet ports automatically. Configuring Errored Symbol Event Detection An errored symbol event occurs when the number of detected symbol errors over a specific detection interval exceeds the predefined threshold. Follow these steps to configure errored symbol event detection: 2-7

23 To do Use the command Remarks Enter system view system-view Configure the errored symbol event detection interval oam errored-symbol period period-value Optional 1 second by default Configure the errored symbol event triggering threshold oam errored-symbol threshold threshold-value Optional 1 by default Configuring Errored Frame Event Detection An errored frame event occurs when the number of detected error frames over a specific interval exceeds the predefined threshold. Follow these steps to configure errored frame event detection: To do Use the command Remarks Enter system view system-view Configure the errored frame event detection interval Configure the errored frame event triggering threshold oam errored-frame period period-value oam errored-frame threshold threshold-value Optional 1 second by default Optional 1 by default Configuring Errored Frame Period Event Detection An errored frame period event occurs if the number of frame errors in specific number of received frames exceeds the predefined threshold. Follow these steps to configure errored frame period event detection: To do Use the command Remarks Enter system view system-view Configure the errored frame period event detection period oam errored-frame-period period period-value Optional 1000 milliseconds by default Configure the errored frame period event triggering threshold oam errored-frame-period threshold threshold-value Optional 1 by default 2-8

24 Configuring Errored Frame Seconds Event Detection An errored frame seconds event occurs when the number of error frame seconds detected on a port over a detection interval exceeds the error threshold. Follow these steps to configure errored frame seconds event detection: To do Use the command Remarks Enter system view system-view Configure the errored frame seconds event detection interval oam errored-frame-seconds period period-value Optional 60 second by default Configure the errored frame seconds event triggering threshold oam errored-frame-seconds threshold threshold-value Optional 1 by default Make sure the errored frame seconds triggering threshold is less than the errored frame seconds detection interval. Otherwise, no errored frame seconds event can be generated. Enabling OAM Remote Loopback After enabling OAM remote loopback on a port, you can send test frames from the port to a remote port and then observe how many of these test frames are returned. In this way, you can calculate the packet loss ratio on the link, thus evaluating the link performance. Follow these steps to enable Ethernet OAM remote loopback: To do Use the command Remarks Enter system view System-view Enter Ethernet port view Enable Ethernet OAM remote loopback interface interface-type interface-number oam loopback Required Disabled by default. Because enabling Ethernet OAM remote loopback impacts other services, use this function with caution. 2-9

25 Ethernet OAM remote loopback is available only after the Ethernet OAM connection is established and can be performed only by the Ethernet OAM entities operating in active Ethernet OAM mode. Remote loopback is available only on full-duplex links that support remote loopback at both ends. Ethernet OAM remote loopback needs the support of the peer hardware. Enabling Ethernet OAM remote loopback interrupts data communications. After Ethernet OAM remote loopback is disabled, all the ports involved will shut down and then come up. Ethernet OAM remote loopback is disabled when you execute the undo oam enable command to disable Ethernet OAM, when you execute the undo oam loopback command to disable Ethernet OAM remote loopback, or when the Ethernet OAM connection times out. Ethernet OAM remote loopback is only applicable to individual links. It is not applicable to link aggregation member ports or service loopback group member ports. In addition, you cannot assign ports where Ethernet OAM remote loopback is being performed to link aggregation groups or service loopback groups. For more information about link aggregation groups and service loopback groups, refer to Ethernet Link Aggregation Configuration and Service Loopback Group Configuration in the Layer 2 - LAN Switching Configuration Guide. Enabling internal loopback test on a port in remote loopback test can terminate the remote loopback test. For more information about loopback test, refer to Ethernet Port Configuration in the Layer 2 - LAN Switching Configuration Guide. Displaying and Maintaining Ethernet OAM Configuration To do Use the command Remarks Display global Ethernet OAM configuration display oam configuration Display the statistics on critical events after an Ethernet OAM connection is established Display the statistics on Ethernet OAM link error events after an Ethernet OAM connection is established Display the information about an Ethernet OAM connection display oam critical-event [ interface interface-type interface-number ] display oam link-event { local remote } [ interface interface-type interface-number ] display oam { local remote } [ interface interface-type interface-number ] Available in any view Clear statistics on Ethernet OAM packets and Ethernet OAM link error events reset oam [ interface interface-type interface-number ] Available in user view only 2-10

26 Ethernet OAM Configuration Example Network requirements Enable Ethernet OAM on Device A and Device B to auto-detect link errors between the two devices. Monitor the performance of the link between Device A and Device B by collecting statistics about the error frames received by Device A. Figure 2-2 Network diagram for Ethernet OAM configuration Configuration procedure 1) Configure Device A # Configure GigabitEthernet 1/0/1 to operate in passive Ethernet OAM mode and enable Ethernet OAM for it. <DeviceA> system-view [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] oam mode passive [DeviceA-GigabitEthernet1/0/1] oam enable [DeviceA-GigabitEthernet1/0/1] quit # Set the errored frame detection interval to 20 seconds and set the errored frame event triggering threshold to 10. [DeviceA] oam errored-frame period 20 [DeviceA] oam errored-frame threshold 10 2) Configure Device B # Configure GigabitEthernet 1/0/1 to operate in active Ethernet OAM mode (the default) and enable Ethernet OAM for it. <DeviceB> system-view [DeviceB] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] oam mode active [DeviceB-GigabitEthernet1/0/1] oam enable [DeviceB-GigabitEthernet1/0/1] quit 3) Verify the configuration Use the display oam configuration command to display the Ethernet OAM configuration. For example: # Display the Ethernet OAM configuration on Device A. [DeviceA] display oam configuration Configuration of the link event window/threshold : Errored-symbol Event period(in seconds) : 1 Errored-symbol Event threshold : 1 Errored-frame Event period(in seconds) :

27 Errored-frame Event threshold : 10 Errored-frame-period Event period(in ms) : 1000 Errored-frame-period Event threshold : 1 Errored-frame-seconds Event period(in seconds) : 60 Errored-frame-seconds Event threshold : 1 According to the above output information, the detection period of errored frame events is 20 seconds, the detection threshold is 10 seconds, and all the other parameters use the default values. You can use the display oam critical-event command to display the statistics of Ethernet OAM critical link events. For example: # Display the statistics of Ethernet OAM critical link events on all the ports of Device A. [DeviceA] display oam critical-event Port : GigabitEthernet1/0/1 Link Status : Up Event statistic : Link Fault :0 Dying Gasp : 0 Critical Event : 0 According to the above output information, no critical link event occurred on the link between Device A and Device B. You can use the display oam link-event command to display the statistics of Ethernet OAM link error events. For example: # Display Ethernet OAM link event statistics of the remote end of Device B. [DeviceB] display oam link-event remote Port :GigabitEthernet1/0/1 Link Status :Up OAMRemoteErrFrameEvent : (ms = milliseconds) Event Time Stamp : 5789 Errored FrameWindow : 10(100ms) Errored Frame Threshold : 1 Errored Frame : 3 Error Running Total : 35 Event Running Total : 17 The above information indicates that 35 errors occurred since Ethernet OAM is enabled on Device A, 17 of which are caused by error frames. The link is instable. 2-12

28 3 CFD Configuration This chapter includes these sections: Overview CFD Configuration Task List Configuring Basic CFD Settings Configuring CFD Functions Displaying and Maintaining CFD CFD Configuration Example Overview Connectivity Fault Detection (CFD), which conforms to Connectivity Fault Management (CFM) defined by IEEE 802.1ag, is an end-to-end per-vlan link layer Operations, Administration and Maintenance (OAM) mechanism used for link connectivity detection, fault verification, and fault location. Basic Concepts in CFD Maintenance domain A maintenance domain (MD) defines the network where CFD plays its role. The MD boundary is defined by some maintenance association end points (MEPs) configured on the ports. An MD is identified by an MD name. To accurately locate faults, CFD introduces eight levels (from 0 to 7) to MDs. The bigger the number, the higher the level and the larger the area covered. Domains can touch or nest (if the outer domain has a higher level than the nested one) but cannot intersect or overlap. MD levels facilitate fault location and make fault location more accurate. As shown in Figure 3-1, MD_A in light blue nests MD_B in dark blue. If a connectivity fault is detected at the boundary of MD_A, any of the devices in MD_A, including Device A through Device E, may fail. In this case, if a connectivity fault is also detected at the boundary of MD_B, the failure points may be any of Device B through Device D. If the devices in MD_B operate normally, you can be sure that at least Device C is operational. 3-1

29 Figure 3-1 Two nested MDs CFD exchanges messages and performs operations on a per-domain basis. By planning MDs properly in a network, you can use CFD to rapidly locate failure points. Maintenance association A maintenance association (MA) is a set of maintenance points (MPs) in an MD. An MA is identified by the MD name + MA name. You can configure multiple MAs in an MD as needed. An MA serves a VLAN. Packets sent by the MPs in an MA carry the corresponding VLAN tag. An MP can receive packets sent by other MPs in the same MA. Maintenance point An MP is configured on a port and belongs to an MA. MPs fall into two types: maintenance association end points (MEPs) and maintenance association intermediate points (MIPs). MEP Each MEP is identified by an integer called a MEP ID. The MEPs of an MD define the range and boundary of the MD. The MA and MD that a MEP belongs to define the VLAN attribute and level of the packets sent by the MEP. MEPs fall into inward-facing MEPs and outward-facing MEPs. The level of a MEP determines the levels of packets that the MEP can process. The packets transmitted from a MEP carry the level of the MEP. A MEP forwards packets at a higher level and processes packet of its level or lower. The processing procedure is specific to packets in the same VLAN. Packets of different VLANs are independent. The direction of a MEP (outward-facing or inward-facing) determines the position of the MD relative to the port. Figure 3-2 Outward-facing MEP 3-2

30 As shown in Figure 3-2, an outward-facing MEP sends packets to its host port. Figure 3-3 Inward-facing MEP As shown in Figure 3-3, an inward-facing MEP does not send packets to its host port. Rather, it sends packets to other ports on the device. MIP A MIP is internal to an MD. It cannot send CFD packets actively; however, it can handle and respond to CFD packets. The MA and MD to which a MIP belongs define the VLAN attribute and level of the packets received. By cooperating with MEPs, a MIP can perform a function similar to ping and traceroute. Like a MEP, a MIP forwards packets at a higher level without any processing and only processes packet of its level or lower. Figure 3-4 demonstrates a grading example of the CFD module. In the figure, there are six devices, labeled A through F respectively. Suppose each device has two ports, and MEPs and MIPs are configured on some of these ports. Four levels of MDs are designed in this example, the bigger the number, the higher the level and the larger the area covered. In this example, Port 1 of device B is configured with the following MPs: a level 5 MIP, a level 3 inward-facing MEP, a level 2 inward-facing MEP, and a level 0 outward-facing MEP. 3-3