H3C S5500-SI Series Configuration manual

H3C S5500-SI Series Ethernet Switches

High Availability

Configuration Guide

Hangzhou H3C Technologies Co., Ltd.

http://www.h3c.com

Document Version: 20100722-C-1.03

Product Version: Release 2202

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.

Preface

The H3C S5500-SI documentation set includes 9 configuration guides, which describe the software

features for the 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.

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:

z Audience

z Document Organization

z Conventions

z About the H3C S5500-SI Documentation Set

z Obtaining Documentation

z Documentation Feedback

Audience

This documentation set is intended for:

z Network planners

z Field technical support and servicing engineers

z Network administrators working with the S5500-SI 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 Track Configuration

Conventions

This section describes the conventions used in this documentation set.

Command conventions

Convention Description

Boldface Bold text represents commands and keywords that you enter literally as shown.

italic

Italic text represents arguments that you replace with actual values.

[ ]

Square brackets enclose syntax choices (keywords or arguments) that are

optional.

{ x | y | ... }

Braces enclose a set of required syntax choices separated by vertical bars,

from which you select one.

Convention Description

[ x | y | ... ]

Square brackets enclose a set of optional syntax choices separated by vertical

bars, from which you select one or none.

{ x | y | ... } *

Asterisk marked braces enclose a set of required syntax choices separated by

vertical bars, from which you select at least one.

[ x | y | ... ] *

Asterisk marked square brackets enclose optional syntax choices separated by

vertical bars, from which you may select multiple choices or none.

&<1-n>

The argument or keyword and argument combination before the ampersand (&)

sign can be entered 1 to n times.

# A line that starts with a pound (#) sign is comments.

GUI conventions

Convention Description

Boldface

Window names, button names, field names, and menu items are in Boldface.

For example, the New User window 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 S5500-SI Documentation Set

The H3C S5500-SI documentation set also includes:

Category Documents Purposes

Marketing brochures Describe product specifications and benefits.

Technology white papers

Provide an in-depth description of software features

and technologies.

RPS User Manual

Describes the appearances, features, and

specifications of the RPS units available for the

products.

RPS Ordering Information for

H3C Low-End Ethernet Switches

Provides the RPS and switch compatibility matrix and

RPS cable specifications.

H3C Low End Series Ethernet

Switches Pluggable Modules

Manual

Describes the models, appearances, and

specifications of the pluggable modules available for

the products.

Product

description and

specifications

Interface Card User Manual

Describes the appearance and specifications of the

interface card.

Category Documents Purposes

H3C S5500-SI Quick Start

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.

S5500-SI Series Ethernet

Switches Installation Manual

Provides a complete guide to hardware installation

and hardware specifications.

Pluggable SFP[SFP+][XFP]

Transceiver Modules Installation

Guide

Guides you through installing SFP/SFP+/XFP

transceiver modules.

Hardware

installation

Interface Card User Manual Describes how to install the interface card.

Configuration guides

Describe software features and configuration

procedures.

Software

configuration

Command references Provide a quick reference to all available commands.

H3C Series Ethernet Switches

Login Password Recovery

Manual

Tells how to find the lost password or recover the

password when the login password is lost.

Operations and

maintenance

Release notes

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

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 [email protected].

We appreciate your comments.

i

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····························································································1-3

2 Ethernet OAM Configuration·················································································································2-1

Ethernet OAM Overview······················································································································2-1

Background ··································································································································2-1

Major Functions of Ethernet OAM································································································2-1

Ethernet OAMPDUs ·····················································································································2-1

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-8

Enabling OAM Remote Loopback········································································································2-9

Displaying and Maintaining Ethernet OAM Configuration··································································2-10

Ethernet OAM Configuration Example·······························································································2-11

3 CFD Configuration ·································································································································3-1

Overview··············································································································································3-1

Basic Concepts in CFD ················································································································3-1

Basic Functions of CFD················································································································3-4

Protocols and Standards··············································································································3-4

CFD Configuration Task List················································································································3-4

Basic Configuration Tasks···················································································································3-5

Configuring Service Instance ·······································································································3-5

Configuring MEP ··························································································································3-6

Configuring MIP Generation Rules·······························································································3-7

Configuring CC on MEPs·····················································································································3-8

Configuration Prerequisites··········································································································3-8

Configuring Procedure ·················································································································3-8

Configuring LB on MEPs ·····················································································································3-9

Configuration Prerequisites··········································································································3-9

Configuration Procedure ··············································································································3-9

Configuring LT on MEPs······················································································································3-9

ii

Configuration Prerequisites········································································································3-10

Finding the Path Between a Source MEP and a Target MEP····················································3-10

Enabling Automatic LT Messages Sending················································································3-10

Displaying and Maintaining CFD ·······································································································3-10

CFD Configuration Examples ············································································································3-11

Configuring Service Instance ·····································································································3-11

Configuring MEP and Enabling CC on it ····················································································3-12

Configuring the Rules for Generating MIPs················································································3-14

Configuring LB on MEPs············································································································3-15

Configuring LT on MEPs ············································································································3-15

4 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 ······················································································································4-21

5 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

iii

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-26

Troubleshooting·································································································································5-35

6 Smart Link Configuration····················································································································6-36

Smart Link Overview··························································································································6-36

Background ································································································································6-36

Terminology································································································································6-37

How Smart Link Works···············································································································6-38

Smart Link Collaboration Mechanisms·······················································································6-39

Smart Link Configuration Task List····································································································6-39

Configuring a Smart Link Device·······································································································6-40

Configuration Prerequisites········································································································6-40

Configuring Protected VLANs for a Smart Link Group·······························································6-40

Configuring Member Ports for a Smart Link Group····································································6-41

Configuring Role Preemption for a Smart Link Group································································6-41

Enabling the Sending of Flush Messages··················································································6-42

Configuring an Associated Device·····································································································6-43

Enabling the Receiving of Flush Messages ···············································································6-43

Displaying and Maintaining Smart Link······························································································6-43

Smart Link Configuration Examples ··································································································6-44

Single Smart Link Group Configuration Example·······································································6-44

Multiple Smart Link Groups Load Sharing Configuration Example············································6-47

7 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····································································································7-4

8 Track Configuration·······························································································································8-1

Track Overview····································································································································8-1

Collaboration Between the Track Module and the Detection Modules·········································8-1

Collaboration Between the Track Module and the Application Modules······································8-2

Track Configuration Task List··············································································································8-2

Configuring Collaboration Between the Track Module and the Detection Modules·····························8-2

Configuring Track-NQA Collaboration··························································································8-2

Configuring Collaboration Between the Track Module and the Application Modules··························8-3

Configuring Track-Static Routing Collaboration···········································································8-3

iv

Displaying and Maintaining Track Object(s)························································································8-4

Track Configuration Examples·············································································································8-4

Static Routing-Track-NQA Collaboration Configuration Example················································8-4

9 Index························································································································································9-1

1-1

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

Decrease system software and

hardware faults

z Hardware: Simplifying circuit design, enhancing

production techniques, and performing reliability tests.

z Software: Reliability design and test

2

Protect system functions from being

affected if faults occur

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-2

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; 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

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.

High Availability

Configuration

Guide/CFD

Configuration

DLDP

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/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

1-3

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-4

Technology Introduction Reference

Smart Link

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.

High Availability

Configuration

Guide/Smart Link

Configuration

MSTP

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.

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

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.

2-1

2 Ethernet OAM Configuration

When configuring the Ethernet OAM function, go to these sections for information you are interested

in:

z Ethernet OAM Overview

z Ethernet OAM Configuration Task List

z Configuring Basic Ethernet OAM Functions

z Configuring Link Monitoring

z Enabling OAM Remote Loopback

z Displaying and Maintaining Ethernet OAM Configuration

z 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 can effectively promote your management and maintenance capabilities over Ethernet

networks, guaranteeing the stability of the networks. Its major functions include:

z Link performance monitoring: Monitors the performance indices of a link, including packet loss,

delay, and jitter, and collects traffic statistics of various types.

z 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.

z Remote loopback: Checks link quality and locates link errors by looping back OAMPDUs.

Ethernet OAMPDUs

Figure 2-1 shows the formats of different types of OAMPDUs.

2-2

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

Dest addr

Destination MAC address of the Ethernet OAMPDU.

It is a slow protocol multicast address 0180c2000002. As slow protocol

packet cannot be forwarded by bridges, Ethernet OAMPDUs cannot be

forwarded.

Source addr

Source MAC address of the Ethernet OAMPDU.

It is the bridge MAC address of the sending side and is a unicast MAC

address.

Type

Type of the encapsulated protocol in the Ethernet OAMPDU.

The value is 0x8809.

Subtype

The specific protocol being encapsulated in the Ethernet OAMPDU.

The value is 0x03.

Flags Status information of an Ethernet OAM entity.

Code Type of the Ethernet OAMPDU

Throughout this document, a port with Ethernet OAM enabled is called an Ethernet OAM entity or an

OAM entity.

Table 2-2 shows the function of the three types of OAMPDUs.

2-3

Table 2-2 Functions of different types of OAMPDUs

OAMPDU type Function

Information

OAMPDU

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

Event Notification

OAMPDU

Used by link monitoring to notify the remote OAM entity when it detects problems on the

link in between.

Loopback Control

OAMPDU

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 it.

As for Ethernet OAM connection establishment, a device can operate 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 with the

Data/Pad field being empty

Available Available

Transmitting Loopback Control OAMPDUs Available Unavailable

2-4

Item Active Ethernet OAM mode

Passive Ethernet OAM

mode

Responding to Loopback Control OAMPDUs

Available (if both sides operate in

active OAM mode)

Available

z 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.

z 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 Description

Errored symbol event

An errored symbol event occurs when the number of detected symbol

errors over a specific detection interval exceeds the predefined

threshold.

Errored frame event

An errored frame event occurs when the number of detected error

frames over a specific interval exceeds the predefined threshold.

Errored frame period event

An errored frame period event occurs if the number of frame errors in

specific number of received frames exceeds the predefined threshold.

2-5

Ethernet OAM link events Description

Errored frame seconds event

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.

z 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)/(64 × 8 × 1000)

z 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 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

Ethernet OAM link events Description

Link Fault Peer link signal is lost.

Dying Gasp An unexpected fault, such as power failure, occurred.

Critical event An undetermined critical event happened.

2-6

The support of S5500-SI series Ethernet switches for information OAMPDUs carrying critical link

events is as follows:

z S5500-SI series Ethernet switches are able to receive information OAMPDUs carrying the critical

link events listed in

Table 2-5.

z Only the Gigabit optical ports are able send information OAMPDUs carrying Link Fault events.

z S5500-SI 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.

z S5500-SI 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 PDUs, 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 Required

Configuring Errored Symbol Event Detection Optional

Configuring Errored Frame Event Detection Optional

Configuring Errored Frame Period Event Detection Optional

Configuring Link

Monitoring

Configuring Errored Frame Seconds Event Detection Optional

Enabling OAM Remote Loopback Optional

2-7

Configuring Basic Ethernet OAM Functions

As for Ethernet OAM connection establishment, a device can operate in active mode or passive mode.

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

—

Set Ethernet OAM operating mode

oam mode

{

active

|

passive

}

Optional

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 operating mode on an Ethernet OAM-enabled port, you need to 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:

To do… Use the command… Remarks

Enter system view

system-view

—

Page is loading ...

H3C S5500-SI Series Configuration manual

H3C S5500-SI Series Configuration manual

Related papers

Other documents