H3C Routers

Ethernet OAM Configuration Examples

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Contents

Introduction· 1

Prerequisites· 1

Example: Configuring Ethernet OAM·· 1

Network configuration· 1

Analysis· 2

Software versions used· 2

Restrictions and guidelines· 2

Procedures· 2

Configuring Device A· 2

Configuring Device B· 3

Verifying the configuration· 3

Configuration files· 4

Related documentation· 5

 

Introduction

The following information provides an example for using Ethernet OAM to monitor link performance.

Ethernet Operation, Administration, and Maintenance (OAM) is a tool that monitors the status of the link between two directly connected devices.

Prerequisites

The configuration examples were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.

This document assumes that you have basic knowledge of Ethernet OAM.

Example: Configuring Ethernet OAM

Network configuration

As shown in Figure 1, the enterprise network and the ISP network are connected through their respective edge devices, Device A and Device B. Configure Ethernet OAM to monitor the status of the link between Device A and Device B, which helps identify whether the ISP network reliability meets the Service Level Agreement (SLA) with the enterprise customer. The specific requirements are as follows:

·     Enable Ethernet OAM on Device A and Device B to auto-detect link errors between the two devices.

·     Enable the administrator to identify whether a critical link event occurs for the link between Device A and Device B.

·     Enable the administrator to dynamically obtain the link status by observing Ethernet OAM link error event statistics.

Figure 1 Network diagram

‌

Analysis

To set up an OAM connection between Device A and Device B, you must set at least the interface on one end to operate in active mode. You can skip this configuration, because all interfaces on the device operate in active Ethernet OAM mode by default. In this example, configure GigabitEthernet 0/0/1 on Device A to operate in active Ethernet OAM mode, and configure GigabitEthernet 0/0/1 on Device B to operate in passive Ethernet OAM mode.

The Ethernet OAM link error events that can be monitored by Ethernet OAM include errored symbol events, errored frame events, errored frame period events, and errored frame seconds events. By default, an interface enabled with Ethernet OAM adopts the global link error detection settings. You can edit the detection settings as needed based on actual network conditions. This example takes the configuration of the errored frame event detection settings for illustration.

Software versions used

This configuration example was created and verified on R9141P16 of the MSR2630E-X1 device.

Restrictions and guidelines

To change the Ethernet OAM mode on an Ethernet OAM-enabled interface, first disable Ethernet OAM on the interface.

Procedures

Configuring Device A

# Configure GigabitEthernet 0/0/1 to operate in active Ethernet OAM mode (default setting), and enable Ethernet OAM for it.

<DeviceA> system-view

[DeviceA] interface gigabitethernet 0/0/1

[DeviceA-GigabitEthernet0/0/1] undo shutdown

[DeviceA-GigabitEthernet0/0/1] oam mode active

[DeviceA-GigabitEthernet0/0/1] oam enable

# Set the errored frame event detection window to 20000 milliseconds, and set the errored frame event triggering threshold to 10.

[DeviceA-GigabitEthernet0/0/1] oam errored-frame window 200

[DeviceA-GigabitEthernet0/0/1] oam errored-frame threshold 10

[DeviceA-GigabitEthernet0/0/1] quit

Configuring Device B

# Configure GigabitEthernet 0/0/1 to operate in passive Ethernet OAM mode, and enable Ethernet OAM for it.

<DeviceB> system-view

[DeviceB] interface gigabitethernet 0/0/1

[DeviceB-GigabitEthernet0/0/1] undo shutdown

[DeviceB-GigabitEthernet0/0/1] oam mode passive

[DeviceB-GigabitEthernet0/0/1] oam enable

[DeviceB-GigabitEthernet0/0/1] quit

Verifying the configuration

# Display global Ethernet OAM configuration and  Ethernet OAM configuration on the interfaces that do not use the default settings on Device A.

[DeviceA] display oam configuration

---------------- [Global] ----------------

 OAM timers

   Hello timer        : 1000 milliseconds

   Keepalive timer    : 5000 milliseconds

 Link monitoring

   Errored symbol period

     Window           : 100 x 1000000 symbols

     Threshold        : 1 error symbols

   Errored frame

     Window           : 10 x 100 milliseconds

     Threshold        : 1 error frames

   Errored frame period

     Window           : 1000 x 10000 frames

     Threshold        : 1 error frames

   Errored frame seconds

     Window           : 600 x 100 milliseconds

     Threshold        : 1 error seconds

 

----------- [GigabitEthernet0/0/1] -----------

 OAM timers

   Hello timer        : 1000 milliseconds

   Keepalive timer    : 5000 milliseconds

 Link monitoring

   Errored symbol period

     Window           : 100 x 1000000 symbols

     Threshold        : 1 error symbols

   Errored frame

     Window           : 200 x 100 milliseconds

     Threshold        : 10 error frames

   Errored frame period

     Window           : 1000 x 10000 frames

     Threshold        : 1 error frames

   Errored frame seconds

     Window           : 600 x 100 milliseconds

     Threshold        : 1 error seconds

# Display the statistics of Ethernet OAM critical link events on Device A.

[DeviceA] display oam critical-event

----------- [GigabitEthernet0/0/1] -----------

 Local link status   : UP

 Event statistics

   Link fault        : Not occurred

   Dying gasp        : Not occurred

   Critical event    : Not occurred

The output shows that no critical link event occurred on the link between Device A and Device B.

# Display Ethernet OAM link event statistics on the local end of Device A.

[DeviceA] display oam link-event local

----------- [GigabitEthernet0/0/1] -----------

 Link status: UP

 OAM local errored frame event

   Event time stamp        : 5789 x 100 milliseconds

   Errored frame window    : 200 x 100 milliseconds

   Errored frame threshold : 10 error frames

   Errored frame           : 13 error frames

   Error running total     : 350 error frames

   Event running total     : 17 events

The output shows that 350 errors occurred after Ethernet OAM is enabled on Device A, among which 17 errors were caused by error frames. The link is unstable.

 

NOTE: If the link detection result shows that the link performance is unstable, contact H3C Support for help.

 

Configuration files

·     Device A

#

interface GigabitEthernet0/0/1

 port link-mode bridge

 oam errored-frame window 200

 oam errored-frame threshold 10

 oam enable

·     Device B

#

interface GigabitEthernet0/0/1

 port link-mode bridge

 oam mode passive

 oam enable

Related documentation

·     High Availability Configuration Guide in H3C MSR1000[2600][3600] Routers Configuration Guides(V9)

·     High Availability Command Reference in H3C MSR1000[2600][3600] Routers Command References(V9)