www.raisecom.

com

iTN8800 (P100R002)
Configuration Guide
(Rel_07)
Raisecom Technology Co., Ltd. provides customers with comprehensive technical support and services. For any
assistance, please contact our local office or company headquarters.
Website: http://www.raisecom.com
Tel: 8610-82883305
Fax: 8610-82883056
Email: export@raisecom.com
Address: Raisecom Building, No. 11, East Area, No. 10 Block, East Xibeiwang Road, Haidian District, Beijing,
P.R.China
Postal code: 100094

-----------------------------------------------------------------------------------------------------------------------------------------

Notice
Copyright © 2019
Raisecom
All rights reserved.
No part of this publication may be excerpted, reproduced, translated or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in Writing from Raisecom
Technology Co., Ltd.

is the trademark of Raisecom Technology Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.
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.
Raisecom
iTN8800 (P100R002) Configuration Guide Preface

Preface

Objectives
This document introduces features and related configurations supported by the iTN8800,
including basic principles and configuration procedures of IP routing, MPLS, MPLS-TP, VPN,
Ethernet, QoS, OAM, and security. In addition, this document provides related configuration
examples. The appendix provides terms, acronyms, and abbreviations involved in this guide.
This document helps you master principles and configurations of the iTN8800 systematically,
as well as networking with the iTN8800.

Versions
The following table lists the product versions related to this document.

Product name Product version Chassis version Software version

iTN8800 P100R002C20 A.00 or later V6.4.30 or later

Conventions
Symbol conventions
The symbols that may be found in this document are defined as below.

Symbol Description
Indicate a hazard with a medium or low level of risk which, if
not avoided, could result in minor or moderate injury.

Indicate a potentially hazardous situation that, if not avoided,

could cause equipment damage, data loss, and performance
degradation, or unexpected results.
Provide additional information to emphasize or supplement
important points of the main text.

Raisecom Proprietary and Confidential

i
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide Preface

Symbol Description
Indicate a tip that may help you solve a problem or save time.

General conventions
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Arial Paragraphs in Warning, Caution, Notes, and Tip are in Arial.
Boldface Names of files, directories, folders, and users are in boldface.
For example, log in as user root.
Italic Book titles are in italics.
Lucida Console Terminal display is in Lucida Console.
Book Antiqua
Heading 1, Heading 2, Heading 3, and Block are in Book
Antiqua.

Command conventions
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in square brackets [ ] are
optional.
{ x | y | ... } Alternative items are grouped in braces and separated by
vertical bars. Only one is selected.
[ x | y | ... ] Optional alternative items are grouped in square brackets and
separated by vertical bars. One or none is selected.
{ x | y | ... } * Alternative items are grouped in braces and separated by
vertical bars. A minimum of one or a maximum of all can be
selected.
[ x | y | ... ] * Optional alternative items are grouped in square brackets and
separated by vertical bars. A minimum of none or a maximum
of all can be selected.

Raisecom Proprietary and Confidential

ii
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide Preface

Configuration mode prompt conventions

Convention Description
/* Indicate the interface ID/slot ID. For example, "Raisecom(config-
eth/1)" indicates Ethernet interface 1 and "Raisecom(config-slot/4)"
indicates slot 4.
/*/* The first "/*" indicates the slot ID and the second "/*" indicates the
interface ID. For example, "Raisecom(config-eth/1/1)" indicates
Ethernet interface 1 of slot 1.

Interface type and value range conventions

Convention Description
interface-type Interface type:
 vlan: VLAN interface
 loopback: Loopback interface
 tunnel: Tunnel interface
 gigaethernet: Layer 2 physical interface/Layer 3 physical

interface/sub-interface
 fastethernet: out-of-band network management interface
 port-channel: Trunk interface/sub-interface
 tdm: TDM interface
 NULL: Null0 interface

interface-number Interface ID based on the device model and interface type:

 vlan: 1–4094
 loopback: 1–16
 tunnel: 1/1/1–1/1/4095
 gigaethernet unit/slot/port: 1/1/1–1/1/4 or 1/2/1–1/2/12 (Layer

2/Layer 3 physical interface)

 gigaethernet unit/slot/port.sub-interface: 1/1/1.1–1/1/1.4094 or

1/1/2.1–1/1/2.4094 and so on (sub-interface)

 fastethernet: 1/0/1
 port-channel: 1–16
 When the interface is a TDM interface, for 1/slot/port, slot-id is the

slot ID, which is an integer and ranges from 1 to 8. The port is the
interface ID, which is an integer and ranges from 1 to 16.
 When the interface is a NULL interface. The interface ID is an

integer and is 0.

Interface configuration mode conventions

In screen outputs described in this document, we use Raisecom(config-port) to indicate
that we have entered interface configuration mode.
However, based on the interface type, the actual screen outputs are in the form of
Raisecom(config-interface-type interface-number). The interface-type and interface-

Raisecom Proprietary and Confidential

iii
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide Preface

number parameters indicate the interface type and interface ID. For details about interface
types and interface IDs, see interface type and value range conventions.
Actual screen outputs are shown as below.

Screen outputs in configuration Description

modes of interfaces

Raisecom(config-fastethernet Entered out-of-band interface configuration

unit/slot/port)# mode. The interface ID is unit/slot/port, such
as Raisecom(config-fastethernet1/0/1)#.
Raisecom(config-gigaethernet Entered Gigabit Ethernet interface
unit/slot/port)# configuration mode. The interface ID is
unit/slot/port, such as Raisecom(config-
gigaethernet1/4/1)#.
Raisecom(config-gigaethernet Entered Gigabit Ethernet sub-interface
unit/slot/port.sub)# configuration mode. The interface ID is
unit/slot/port.sub, such as Raisecom(config-
gigaethernet1/4/1.1)#.
Raisecom(config-vlan port)# Entered VLAN interface configuration mode.
The interface ID is an integer, such as
Raisecom(config-vlan1)#.

Raisecom(config-port-channel Entered Trunk interface configuration mode.

port)# The interface ID is an integer, such as
Raisecom(config-port-channel1)#.

Raisecom(config-port-channel Entered Trunk sub-interface configuration

port.sub)# mode. The interface ID is port.sub, such as
Raisecom(config-port-channel1.1)#.

Raisecom(config-tunnel Entered Tunnel interface configuration mode.

unit/slot/port)# The interface ID is unit/slot/port, such as
Raisecom(config-tunnel1/1/1)#.
Raisecom(config-loopback port)# Entered Loopback interface configuration
mode. The interface ID is an integer, such as
Raisecom(config-loopback1)#.
Raisecom(config-tdm unit/slot/port)# Entered TDM interface configuration mode.
The interface ID is unit/slot/port, such as
Raisecom(config-tdm1/3/1)#.

Raisecom(config-tdm Entered TDM sub-interface configuration

unit/slot/port.sub)# mode. The interface ID is unit/slot/port.sub,
such as Raisecom(config-tdm1/3/1.1)#.
Raisecom(config-NULL0)# Entered NULL interface configuration mode.
The interface ID is 0.

Raisecom Proprietary and Confidential

iv
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide Preface

Change history
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.

Issue 07 (2019-01-10)
Seventh commercial release
 Modified the command line for the loopback function.
 Modified Y.1546 configurations.
 Fixed known bugs.

Issue 06 (2018-02-10)
Sixth commercial release
 Added configurations of the multi-interface U0.
 Added configurations of hierarchical bandwidths.
 Added configurations of remote zero-configuration dual-uplink NAT.
 Upgraded configurations of interface management.
 Added configurations of Proxy ARP.
 Added configurations of MPLS load balancing.
 Upgraded configurations of MPLS VPN.

Issue 05 (2017-03-30)
Fifth commercial release
 Added LDP MD5.
 Added support for EBGP by L3VPN PE-CE.
 Added terminal virtualization.

Issue 04 (2016-09-30)
Fourth commercial release
 Added commands for configuring IP equal-cost multi-path load balancing.
 Added commands for configuring RIP.
 Added commands for configuring IPv6 ACL.
 Added commands for configuring IPv6 ISIS.
 Added commands for configuring H-QoS.
 Added commands for maximizing the OSPF LSA metric value.
 Added commands for configuring OSPFv3.
 Added commands for configuring IPv6 address and IPv6 neighbor discovery.
 Added commands for configuring ARP active acknowledgement and updated the chapter
Configuring ARP.
 Added commands for configuring MLD.
 Added commands for configuring PIM.
Raisecom Proprietary and Confidential
v
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide Preface

 Added commands for configuring IP FRR.

 Added commands for configuring IPv6 static routes.
 Added commands for configuring static route BFD.
 Added the configurations of using sub-interface to encapsulate VLAN section.
 Revised the upgrade description in the Bootroom mode.
 Added commands for configuring the RCLink remote management.
 Added commands for configuring GRE.
 Added commands for configuring RMON.
 Added commands for configuring Banner.
 Added commands for configuring LDP FRR and BFD for LDP.
 Added commands for configuring PTP clock synchronization.
 Updated chapter Configuring MPLS TE.
 Added commands for configuring SLA Y.1564.
 Added commands for configuring VPN FRR.
 Added commands for configuring dot.1x.
 Updated chapter Configuring SLA.
 Added commands for configuring PRBS.
 Added commands for configuring IGMP.

Issue 03 (2015-08-20)
Third commercial release
 Added commands for overall upgrade.
 Added commands for suppressing MAC address drifting.
 Added the function of supporting LAG mirroring.
 Added the function of supporting LAG loopback.
 Added zero-configuration on the OSPF DCN remote device.
 Upgraded commands for configuring interfaces.
 Added the commands for interface backup.
 Added commands for configuring ISIS.
 Added commands for configuring VLAN mapping.
 Added commands for configuring URPF.
 Added commands for configuring L2CP.
 Added commands for configuring the SDH interface.
 Added commands for configuring clock synchronization.
 Added contents in basic configuration, memory monitoring, CPU monitoring, device
monitoring, fault detection, optical module DDM, and other chapters.

Issue 02 (2015-03-20)
Second commercial release
 Added the following features: DHCP, MPLS-TP OAM, SLA, TDMoP, VRRP, loop
detection, Loopback, link aggregation, mLACP, ELPS, ERPS, MPLS linear protection,
ICCP, and HA.
Raisecom Proprietary and Confidential
vi
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide Preface

 Fixed known bugs.

Issue 01 (2014-01-20)
Initial commercial release

Raisecom Proprietary and Confidential

vii
Copyright © Raisecom Technology Co., Ltd.
 Raisecom
iTN8800 (P100R002) Configuration Guide Contents

Contents

1 Basic configurations ..................................................................................................................... 1

1.1 CLI ................................................................................................................................................................... 1
1.1.1 Overview ................................................................................................................................................. 1
1.1.2 Levels ...................................................................................................................................................... 2
1.1.3 Modes...................................................................................................................................................... 2
1.1.4 Shortcut keys ........................................................................................................................................... 6
1.1.5 Acquiring help ......................................................................................................................................... 7
1.2 Accessing device ............................................................................................................................................ 10
1.2.1 Accessing device through Console interface ......................................................................................... 10
1.2.2 Accessing device through Telnet ........................................................................................................... 11
1.2.3 Accessing device through SSHv2 ......................................................................................................... 13
1.3 Backup and upgrade ....................................................................................................................................... 14
1.3.1 Introduction ........................................................................................................................................... 14
1.3.2 Backing up files .................................................................................................................................... 16
1.3.3 Upgrading files...................................................................................................................................... 16
1.3.4 Checking configurations ....................................................................................................................... 19
1.3.5 Overall upgrade ..................................................................................................................................... 19
1.4 Device management ....................................................................................................................................... 20
1.4.1 Introduction ........................................................................................................................................... 20
1.4.2 Preparing for configurations ................................................................................................................. 21
1.4.3 Confiurating SNMP basic functions...................................................................................................... 21
1.4.4 Configuring Trap ................................................................................................................................... 22
1.4.5 Configuring KeepAlive Trap packets .................................................................................................... 23
1.4.6 Checking configurations ....................................................................................................................... 24
1.5 Configuring RMON ....................................................................................................................................... 24
1.5.1 Introduction ........................................................................................................................................... 24
1.5.2 Preparing for configurations ................................................................................................................. 24
1.5.3 Configuring RMON alarm group .......................................................................................................... 25
1.5.4 Configuring RMON event group .......................................................................................................... 25
1.5.5 Configuring RMON statistics ............................................................................................................... 25
1.5.6 Configuring RMON history statistics ................................................................................................... 26
1.5.7 Checking configurations ....................................................................................................................... 26

Raisecom Proprietary and Confidential

viii
Copyright © Raisecom Technology Co., Ltd.
 Raisecom
iTN8800 (P100R002) Configuration Guide Contents

1.6 Configuration examples ................................................................................................................................. 26

1.6.1 Example for upgrading system software (in privileged EXEC mode) .................................................. 26
1.6.2 Example for upgrading system software (in BootROM mode) ............................................................. 27

2 System management ................................................................................................................... 30

2.1 User management ........................................................................................................................................... 30
2.1.1 Configuring user management .............................................................................................................. 31
2.1.2 Checking configurations ....................................................................................................................... 31
2.2 Device management ....................................................................................................................................... 31
2.2.1 Chassis management ............................................................................................................................. 31
2.2.2 Fan management ................................................................................................................................... 31
2.2.3 Rebooting cards .................................................................................................................................... 32
2.2.4 Checking configurations ....................................................................................................................... 32
2.3 Time management .......................................................................................................................................... 32
2.3.1 Configuring time and time zone ............................................................................................................ 32
2.3.2 Configuring DST .................................................................................................................................. 33
2.3.3 Configuring SNTP ................................................................................................................................ 33
2.3.4 Checking configurations ....................................................................................................................... 34
2.4 Log management ............................................................................................................................................ 34
2.4.1 Basic configurations of log management .............................................................................................. 34
2.4.2 Configuring log discriminator ............................................................................................................... 34
2.4.3 Configuring log storage ........................................................................................................................ 35
2.4.4 Checking configurations ....................................................................................................................... 35
2.4.5 Maintenance .......................................................................................................................................... 35
2.5 File management ............................................................................................................................................ 36
2.5.1 Introduction ........................................................................................................................................... 36
2.5.2 Managing configuration files ................................................................................................................ 37
2.6 Alarm management ........................................................................................................................................ 37
2.6.1 Configuring alarm inhibition ................................................................................................................ 39
2.6.2 Configuring alarm delay ....................................................................................................................... 40
2.6.3 Configuring alarm storage modes ......................................................................................................... 40
2.6.4 Configuring alarm auto-report .............................................................................................................. 40
2.6.5 Configuring alarm inverse .................................................................................................................... 41
2.6.6 Configuring alarm monitoring .............................................................................................................. 41
2.6.7 Configuring alarm output ...................................................................................................................... 42
2.6.8 Checking configurations ....................................................................................................................... 42
2.6.9 Maintenance .......................................................................................................................................... 42
2.7 Configuring device monitoring ...................................................................................................................... 43
2.7.1 Configuring temperature monitoring .................................................................................................... 43
2.7.2 Fan monitoring ...................................................................................................................................... 43
2.7.3 Checking configurations ....................................................................................................................... 43
2.8 Configuring fault detection ............................................................................................................................ 43

Raisecom Proprietary and Confidential

ix
Copyright © Raisecom Technology Co., Ltd.
 Raisecom
iTN8800 (P100R002) Configuration Guide Contents

2.8.1 Configuring task scheduling ................................................................................................................. 43

2.8.2 Ping ....................................................................................................................................................... 44
2.8.3 Traceroute ............................................................................................................................................. 44
2.9 Configuring Banner ........................................................................................................................................ 45
2.9.1 Preparing for configurations ................................................................................................................. 45
2.9.2 Configuring Banner............................................................................................................................... 45
2.9.3 Enabling Banner display ....................................................................................................................... 46
2.9.4 Checking configurations ....................................................................................................................... 46
2.10 Configuring RCLink remote management ................................................................................................... 46
2.10.1 Preparing for configurations ............................................................................................................... 46
2.10.2 Configuring basic information about remote device ........................................................................... 47
2.10.3 Configuring interface parameters of remote device ............................................................................ 48
2.10.4 Checking configurations ..................................................................................................................... 49
2.11 Configuring terminal virtualization .............................................................................................................. 50
2.11.1 Preparing for configurations................................................................................................................ 50
2.11.2 Working principle ................................................................................................................................ 50
2.11.3 Configuring management IP address of U0 device ............................................................................. 51
2.11.4 Configuring SPF of OSPF process ...................................................................................................... 51
2.11.5 Configuring loopback among DCN sub-interfaces ............................................................................. 52
2.11.6 Remote management of U0 devices .................................................................................................... 52
2.11.7 Saving preconfigurations of U0 device ............................................................................................... 53
2.12 Example for configurations .......................................................................................................................... 54
2.12.1 Example for configuring hardware monitoring alarms output ............................................................ 54

3 Interface management ................................................................................................................ 56

3.1 Basic configurations of interface .................................................................................................................... 56
3.1.1 Configuring basic information of interface ........................................................................................... 56
3.1.2 Configuring interface working mode .................................................................................................... 57
3.1.3 Configuring Jumboframe of interface ................................................................................................... 57
3.1.4 Configuring MTU of interface .............................................................................................................. 58
3.1.5 Configuring vibration suppression of interface ..................................................................................... 58
3.1.6 Configuring MAC address of interface ................................................................................................. 58
3.2 Configuring Ethernet interface ....................................................................................................................... 59
3.3 Configuring Ethernet sub-interface ................................................................................................................ 59
3.4 Configuring VLAN interface ......................................................................................................................... 60
3.5 Configuring optical module DDM ................................................................................................................. 60
3.5.1 Preparing for configurations ................................................................................................................. 60
3.5.2 Enabling optical module DDM ............................................................................................................. 60
3.5.3 Checking configurations ....................................................................................................................... 60
3.6 Configuring loopback interface ...................................................................................................................... 61
3.7 Configuring interface statistics ....................................................................................................................... 61
3.8 Configuring loopback ..................................................................................................................................... 61

Raisecom Proprietary and Confidential

x
Copyright © Raisecom Technology Co., Ltd.
 Raisecom
iTN8800 (P100R002) Configuration Guide Contents

3.8.1 Preparing for configurations ................................................................................................................. 61

3.8.2 Configuring interface loopback............................................................................................................. 62
3.9 Checking configurations ................................................................................................................................ 63

4 Zero-configuration ...................................................................................................................... 64
4.1 Configuring CO zero-configuration ............................................................................................................... 64
4.1.1 Preparing for configurations ................................................................................................................. 64
4.1.2 Configuring zero-configuration Server based on extended OAM......................................................... 65
4.1.3 Configuring zero-configuration Server based on DHCP....................................................................... 67
4.1.4 Configuring zero-configuration based on DCN NMS self-connection ................................................. 72
4.1.5 Checking configurations ....................................................................................................................... 74
4.2 Configuration examples ................................................................................................................................. 74
4.2.1 Example for configuring remote zero-configuration in private network under IP RAN CO device ..... 74

5 Ethernet ......................................................................................................................................... 78
5.1 Configuring VLAN ........................................................................................................................................ 78
5.1.1 Preparing for configurations ................................................................................................................. 78
5.1.2 Configuring VLAN properties .............................................................................................................. 79
5.1.3 Configuring VLANs based on Access interface .................................................................................... 79
5.1.4 Configuring VLANs based on Trunk interface ..................................................................................... 80
5.1.5 Checking configurations ....................................................................................................................... 80
5.2 Configuring MAC address table..................................................................................................................... 81
5.2.1 Preparing for configurations ................................................................................................................. 81
5.2.2 Configuring static MAC address table .................................................................................................. 81
5.2.3 Configuring dynamic MAC address table ............................................................................................. 81
5.2.4 Configuring blackhole MAC address .................................................................................................... 82
5.2.5 Checking configurations ....................................................................................................................... 82
5.2.6 Maintenance .......................................................................................................................................... 83
5.3 Configuring QinQ .......................................................................................................................................... 83
5.3.1 Preparing for configurations ................................................................................................................. 83
5.3.2 Configuring basic QinQ ........................................................................................................................ 84
5.3.3 Configuring QinQ VLAN mapping ...................................................................................................... 84
5.3.4 Checking configurations ....................................................................................................................... 85
5.4 Configuring LLDP ......................................................................................................................................... 85
5.4.1 Preparing for configurations ................................................................................................................. 85
5.4.2 Enabling global LLDP .......................................................................................................................... 85
5.4.3 Enabling interface LLDP ...................................................................................................................... 86
5.4.4 Configuring LLDP basic functions ....................................................................................................... 86
5.4.5 Configuring LLDP Trap ........................................................................................................................ 86
5.4.6 Checking configurations ....................................................................................................................... 87
5.5 Configuring loop detection ............................................................................................................................. 87
5.5.1 Preparing for configurations ................................................................................................................. 87
5.5.2 Configuring loop detection ................................................................................................................... 87

Raisecom Proprietary and Confidential

xi
Copyright © Raisecom Technology Co., Ltd.
 Raisecom
iTN8800 (P100R002) Configuration Guide Contents

5.5.3 Checking configurations ....................................................................................................................... 88

5.5.4 Maintenance .......................................................................................................................................... 88
5.6 Configuring L2CP .......................................................................................................................................... 88
5.6.1 Preparing for configurations ................................................................................................................. 88
5.6.2 Configuring L2CP ................................................................................................................................. 89
5.6.3 Checking configurations ....................................................................................................................... 89

6 Clock synchronization ............................................................................................................... 90

6.1 Configuring clock synchronization based on SyncE ...................................................................................... 90
6.1.1 Preparing for configurations ................................................................................................................. 90
6.1.2 Configuring properties of SyncE clock source ..................................................................................... 91
6.1.3 Manually choosing SyncE clock source................................................................................................ 91
6.1.4 Checking configurations ....................................................................................................................... 91
6.2 Configuring PTP-based clock synchronization .............................................................................................. 92
6.2.1 Preparing for configurations ................................................................................................................. 92
6.2.2 Configuring PTP clock modes .............................................................................................................. 92
6.2.3 Configuring properties of PTP clock..................................................................................................... 93
6.2.4 Configuring packet transmission........................................................................................................... 93
6.2.5 (Optional) configuring properties of PTP clock interface ..................................................................... 94
6.2.6 Inputting/Outputting clock signals on 1pps-tod interface ..................................................................... 95
6.2.7 Inputting/Outputting clock signals on 1pps interface ............................................................................ 96
6.2.8 Checking configurations ....................................................................................................................... 96
6.3 Maintenance ................................................................................................................................................... 97
6.4 Configuration examples ................................................................................................................................. 97
6.4.1 Examples for configuring clock synchronization based on SyncE ....................................................... 97

7 TDMoP ........................................................................................................................................ 100

7.1 Configuring TDM interface.......................................................................................................................... 100
7.1.1 Preparing for configurations ............................................................................................................... 100
7.1.2 Configuring link type of TDM interfaces............................................................................................ 101
7.1.3 Configuring TDM sub-interface.......................................................................................................... 101
7.1.4 Configuring TDM interface loopback ................................................................................................. 101
7.1.5 Checking configurations ..................................................................................................................... 102
7.2 Configuring SDH interface .......................................................................................................................... 102
7.2.1 Preparing for configurations ............................................................................................................... 102
7.2.2 Configuring SDH interface ................................................................................................................. 102
7.2.3 Configuring SDH sub-interface .......................................................................................................... 104
7.2.4 Checking configurations ..................................................................................................................... 105
7.3 Configuring Tunnel ...................................................................................................................................... 105
7.3.1 Preparing for configurations ............................................................................................................... 105
7.3.2 Configuring MPLS Tunnel .................................................................................................................. 105
7.4 Configuring PW ........................................................................................................................................... 105
7.4.1 Preparing for configurations ............................................................................................................... 105

Raisecom Proprietary and Confidential

xii
Copyright © Raisecom Technology Co., Ltd.
 Raisecom
iTN8800 (P100R002) Configuration Guide Contents

7.4.2 Configuring static L2VC ..................................................................................................................... 106

7.4.3 Configuring dynamic L2VC ............................................................................................................... 106
7.4.4 Checking configurations ..................................................................................................................... 107
7.5 Configuring TDMoP clock ........................................................................................................................... 107
7.5.1 Preparing for configurations ............................................................................................................... 107
7.5.2 Configuring Tx clock source of TDM interface .................................................................................. 108
7.5.3 Configuring sub-interface of adaptive recovery clock ........................................................................ 108
7.5.4 Checking configurations ..................................................................................................................... 108
7.6 Maintenance ................................................................................................................................................. 108

8 IP services ................................................................................................................................... 109

8.1 Configuring interface ................................................................................................................................... 109
8.1.1 Preparing for configurations ............................................................................................................... 109
8.1.2 Configuring interface information ...................................................................................................... 109
8.1.3 Checking configurations ..................................................................................................................... 110
8.2 Configuring fault detection .......................................................................................................................... 110
8.2.1 Configuring task scheduling ............................................................................................................... 110
8.2.2 PING ................................................................................................................................................... 111
8.2.3 Traceroute ........................................................................................................................................... 111
8.3 Configuring ARP .......................................................................................................................................... 111
8.3.1 Preparing for configurations ............................................................................................................... 111
8.3.2 Configuring ARP ................................................................................................................................ 112
8.3.3 Configuring proxy ARP ...................................................................................................................... 112
8.3.4 Configuring proxy ARP/NDP for PW ................................................................................................. 113
8.3.5 Checking configurations ..................................................................................................................... 114
8.4 Configuring DHCP v4 Relay........................................................................................................................ 115
8.4.1 Preparing for configurations ............................................................................................................... 115
8.4.2 Configuring DHCP v4 Relay .............................................................................................................. 115
8.4.3 Configuring destination IP address of DHCP v4 Relay ...................................................................... 115
8.4.4 Checking configurations ..................................................................................................................... 116
8.5 Configuring DHCP v4 Server ...................................................................................................................... 116
8.5.1 Preparing for configurations ............................................................................................................... 116
8.5.2 Creating and configuring IPv4 address pool ....................................................................................... 116
8.5.3 Configuring DHCP v4 Server on interface ......................................................................................... 117
8.5.4 Checking configurations ..................................................................................................................... 117
8.5.5 Checking configurations ..................................................................................................................... 117
8.6 Maintenance ................................................................................................................................................. 117
8.7 Configuration examples ............................................................................................................................... 118
8.7.1 Example for configuring DHCP v4 Relay........................................................................................... 118
8.7.2 Example for configuring DHCP v4 Server ......................................................................................... 119

9 IP routing .................................................................................................................................... 121

9.1 Configuring routing management ................................................................................................................ 121

Raisecom Proprietary and Confidential

xiii
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide Contents

9.1.1 Configuring routing management ....................................................................................................... 121

9.1.2 Configuring IP FRR ............................................................................................................................ 121
9.1.3 Configuring BFD ................................................................................................................................ 122
9.1.4 Checking configurations ..................................................................................................................... 122
9.2 Configuring static route ................................................................................................................................ 122
9.2.1 Preparing for configurations ............................................................................................................... 122
9.2.2 Configuring static route ...................................................................................................................... 123
9.2.3 Checking configurations ..................................................................................................................... 123
9.3 Configuring routing policy ........................................................................................................................... 124
9.3.1 Configuring IP prefix-list .................................................................................................................... 124
9.3.2 Configuring route mapping table ........................................................................................................ 124
9.3.3 Checking configurations ..................................................................................................................... 127
9.4 Configuring OSPFv2 .................................................................................................................................... 127
9.4.1 Configuring OSPF basic functions ...................................................................................................... 127
9.4.2 Configuring OSPF route properties .................................................................................................... 128
9.4.3 Configuring OSPF administrative distance ......................................................................................... 128
9.4.4 Configuring device to be compatible with RFC1583 .......................................................................... 129
9.4.5 Configuring load balancing ................................................................................................................. 129
9.4.6 Maximizing LSA metric ...................................................................................................................... 129
9.4.7 Configuring OSPF network ................................................................................................................ 130
9.4.8 Optimizing OSPF network .................................................................................................................. 131
9.4.9 Configuring OSPF authentication mode ............................................................................................. 133
9.4.10 Configuring Stub area ....................................................................................................................... 134
9.4.11 Controlling OSPF routing information.............................................................................................. 135
9.4.12 Configuring OSPF routing policy ..................................................................................................... 136
9.4.13 Configuring BFD for OSPF .............................................................................................................. 138
9.4.14 Configuring OSPF for MPLS-TE ..................................................................................................... 139
9.4.15 Checking configurations ................................................................................................................... 139
9.4.16 Maintenance ...................................................................................................................................... 140
9.5 Configuring ISIS .......................................................................................................................................... 140
9.5.1 Configuring ISIS basic function.......................................................................................................... 140
9.5.2 Configuring ISIS routing .................................................................................................................... 141
9.5.3 Configuring ISIS network ................................................................................................................... 142
9.5.4 Optimizing ISIS network .................................................................................................................... 144
9.5.5 Configure ISIS authentication ............................................................................................................. 146
9.5.6 Controlling ISIS routing information .................................................................................................. 146
9.5.7 Configuring ISIS BFD ........................................................................................................................ 148
9.5.8 Configuring ISIS GR .......................................................................................................................... 148
9.5.9 Configuring ISIS TE ........................................................................................................................... 149
9.5.10 Checking configurations ................................................................................................................... 149
9.5.11 Maintenance ...................................................................................................................................... 150
9.6 Configuring BGP ......................................................................................................................................... 150

Raisecom Proprietary and Confidential

xiv
Copyright © Raisecom Technology Co., Ltd.
 Raisecom
iTN8800 (P100R002) Configuration Guide Contents

9.6.1 Configuring BGP basic functions........................................................................................................ 150

9.6.2 Configuring BGP route advertisement ................................................................................................ 150
9.6.3 Configuring BGP redistributed routes ................................................................................................. 150
9.6.4 Configuring BGP routing .................................................................................................................... 152
9.6.5 Configuring BGP network .................................................................................................................. 155
9.6.6 Configuring BGP GR .......................................................................................................................... 157
9.6.7 Configuring BFD for BGP .................................................................................................................. 158
9.6.8 Configuring BGP authentication ......................................................................................................... 158
9.6.9 Checking configurations ..................................................................................................................... 158
9.6.10 Maintenance ...................................................................................................................................... 159
9.7 Configuring RIP ........................................................................................................................................... 159
9.7.1 Configuring basic RIP functions ......................................................................................................... 159
9.7.2 Configuring RIP version ..................................................................................................................... 159
9.7.3 Redistributing external routes ............................................................................................................. 160
9.7.4 Configuring timer ................................................................................................................................ 161
9.7.5 Configuring loop suppression ............................................................................................................. 161
9.7.6 Configuring authentication ................................................................................................................. 162
9.7.7 Configuring routing policy.................................................................................................................. 162
9.7.8 Configuring route calculation ............................................................................................................. 162
9.7.9 Configuring alarms ............................................................................................................................. 163
9.7.10 Checking configurations ................................................................................................................... 163
9.7.11 Maintenance ...................................................................................................................................... 163

10 MPLS ......................................................................................................................................... 164

10.1 Configuring MPLS basic functions ............................................................................................................ 164
10.1.1 Preparing for configurations ............................................................................................................. 164
10.1.2 Configuring MPLS basic functions ................................................................................................... 164
10.1.3 Configuring MPLS Tunnel basic functions ....................................................................................... 165
10.1.4 Configuring MPLS Tunnel policy ..................................................................................................... 165
10.1.5 Checking configurations ................................................................................................................... 166
10.2 Configuring static LSP ............................................................................................................................... 166
10.2.1 Preparing for configurations ............................................................................................................. 166
10.2.2 Configuring static unidirectional LSP with IP capability .................................................................. 167
10.2.3 Configuring static unidirectional LSP without IP capability ............................................................. 167
10.2.4 Configuring static bidirectional LSP with IP capability .................................................................... 168
10.2.5 Configuring static bidirectional LSP without IP capability ............................................................... 169
10.2.6 Checking configurations ................................................................................................................... 170
10.3 Configuring LDP LSP ................................................................................................................................ 170
10.3.1 Preparing for configurations ............................................................................................................. 170
10.3.2 Configuring global LDP.................................................................................................................... 171
10.3.3 Configuring LDP on interface ........................................................................................................... 171
10.3.4 Configuring LDP remote session ...................................................................................................... 171

Raisecom Proprietary and Confidential

xv
Copyright © Raisecom Technology Co., Ltd.
 Raisecom
iTN8800 (P100R002) Configuration Guide Contents

10.3.5 Configuring LDP MD5 ..................................................................................................................... 172

10.3.6 Configuring BFD for TLDP .............................................................................................................. 172
10.3.7 Configuring LDP FRR ...................................................................................................................... 173
10.3.8 Checking configurations ................................................................................................................... 173
10.4 Configuring MPLS TE ............................................................................................................................... 174
10.4.1 Preparing for configurations ............................................................................................................. 174
10.4.2 Enabling RSVP-TE ........................................................................................................................... 174
10.4.3 Enabling CSPE.................................................................................................................................. 174
10.4.4 Configuring explicit path and Tunnel................................................................................................ 175
10.4.5 Configuring TE protection ................................................................................................................ 176
10.4.6 Configure BFD for RSVP-TE ........................................................................................................... 177
10.4.7 Checking configurations ................................................................................................................... 177
10.5 Configuring MPLS fault detection ............................................................................................................. 178
10.5.1 Preparing for configurations ............................................................................................................. 178
10.5.2 Configuring MPLS fault acknowledgment ....................................................................................... 178
10.5.3 Configuring MPLS fault location ...................................................................................................... 179
10.6 Configuring GRE Tunnel ........................................................................................................................... 179
10.6.1 Preparing for configurations ............................................................................................................. 179
10.6.2 Configuring GRE Tunnel basic functions ......................................................................................... 179
10.6.3 Checking configurations ................................................................................................................... 180
10.7 Configuring MPLS load balancing ............................................................................................................. 180
10.7.1 Preparing for configurations ............................................................................................................. 180
10.7.2 Configuring MPLS load balancing parameters ................................................................................. 181
10.7.3 Checking configurations ................................................................................................................... 181
10.8 Configuration examples ............................................................................................................................. 182
10.8.1 Example for configuring static bidirectional LSP without IP capability ........................................... 182
10.8.2 Example for configuring LDP-based dynamic LSP .......................................................................... 187
10.8.3 Example for configuring RSVP-TE-based dynamic LSP ................................................................. 189
10.8.4 Example for configuring manual LDP FRR ...................................................................................... 192
10.8.5 Example for configuring automatic LDP FRR .................................................................................. 198
10.8.6 Example for configuring MPLS-TE FRR link protection ................................................................. 206
10.8.7 Example for configuring MPLS-TE FRR node protection ............................................................... 213

11 VPN ............................................................................................................................................ 219

11.1 Configuring MPLS VPWS ......................................................................................................................... 219
11.1.1 Preparing for configurations .............................................................................................................. 219
11.1.2 Configuring static L2VC ................................................................................................................... 222
11.1.3 Configuring dynamic L2VC.............................................................................................................. 223
11.1.4 Configuring MS-PW ......................................................................................................................... 224
11.1.5 (Optional) configuring BFD for PW ................................................................................................. 225
11.1.6 Configuring ARP for PW and NDP for PW ...................................................................................... 226
11.1.7 Checking configurations ................................................................................................................... 226

Raisecom Proprietary and Confidential

xvi
Copyright © Raisecom Technology Co., Ltd.
 Raisecom
iTN8800 (P100R002) Configuration Guide Contents

11.2 Configuring MPLS VPLS .......................................................................................................................... 227

11.2.1 Preparing for configurations .............................................................................................................. 227
11.2.2 Configuring VSI ................................................................................................................................ 227
11.2.3 Checking configurations ................................................................................................................... 228
11.3 Configuring VPWS to access VPLS ........................................................................................................... 228
11.3.1 Preparing for configurations .............................................................................................................. 228
11.3.2 Configuring VSI to access VPWS ..................................................................................................... 228
11.3.3 Checking configurations ................................................................................................................... 229
11.4 Configuring MPLS L3VPN........................................................................................................................ 229
11.4.1 Preparing for configurations .............................................................................................................. 229
11.4.2 Configuring VRF basic attributes ...................................................................................................... 230
11.4.3 Binding VRF with interfaces ............................................................................................................. 230
11.4.4 Configuring public routes.................................................................................................................. 231
11.4.5 Configuring public Tunnel ................................................................................................................ 231
11.4.6 Configuring MP-IBGP peer .............................................................................................................. 231
11.4.7 Configuring PE-CE route switching.................................................................................................. 232
11.4.8 Configuring VRF fault detection ....................................................................................................... 234
11.4.9 Checking configurations ................................................................................................................... 234
11.5 Maintainance .............................................................................................................................................. 235
11.6 Configuration examples ............................................................................................................................. 235
11.6.1 Example for configuring static Tunnel to carry static VPWS services .............................................. 235
11.6.2 Example for configuring RSVP-TE-based dynamic Tunnel to carry dynamic VPWS services ........ 238
11.6.3 Example for configuring MPLS L2VPN typical networking ............................................................ 241
11.6.4 Examples for configuring MPLS L3VPN typical networking .......................................................... 252

12 QoS ............................................................................................................................................. 262

12.1 Configuring ACL ....................................................................................................................................... 262
12.1.1 Preparing for configurations ............................................................................................................. 262
12.1.2 Configuring ACL .............................................................................................................................. 262
12.1.3 Configuring filter .............................................................................................................................. 264
12.1.4 Checking configurations ................................................................................................................... 264
12.2 Configuring priority trust and priority mapping ......................................................................................... 265
12.2.1 Preparing for configurations ............................................................................................................. 265
12.2.2 Configuring priority trust .................................................................................................................. 265
12.2.3 Configuring mapping between DSCP priority and local priority based on interface ........................ 265
12.2.4 Configuring mapping between CoS priority and local priority based on interface ........................... 266
12.2.5 Configuring mapping between Exp and local priority ...................................................................... 266
12.2.6 Configuring DSCP priority remarking .............................................................................................. 267
12.2.7 Configuring CoS priority remarking ................................................................................................. 267
12.2.8 Configuring Exp remarking .............................................................................................................. 267
12.2.9 Checking configurations ................................................................................................................... 268
12.3 Configuring traffic classification and traffic policy ................................................................................... 268

Raisecom Proprietary and Confidential

xvii
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide Contents

12.3.1 Preparing for configurations ............................................................................................................. 268

12.3.2 Creating and configuring traffic classification .................................................................................. 268
12.3.3 Creating and configuring traffic policing profile .............................................................................. 269
12.3.4 Creating and configuring traffic policy ............................................................................................. 270
12.3.5 Checking configurations ................................................................................................................... 271
12.4 Configuring congestion avoidance and queue shaping .............................................................................. 271
12.4.1 Preparing for configurations ............................................................................................................. 271
12.4.2 Configuring WRED profile ............................................................................................................... 271
12.4.3 Configuring flow profile ................................................................................................................... 272
12.4.4 Configuring queue shaping ............................................................................................................... 272
12.4.5 Checking configurations ................................................................................................................... 272
12.5 Configuring rate limiting ............................................................................................................................ 273
12.5.1 Preparing for configurations ............................................................................................................. 273
12.5.2 Configuring interface-based rate limiting ......................................................................................... 273
12.5.3 Checking configurations ................................................................................................................... 274
12.6 Configuring bandwidth rate limiting .......................................................................................................... 274
12.6.1 Preparing for configurations ............................................................................................................. 274
12.6.2 Default configurations of bandwidth rate limiting ............................................................................ 274
12.6.3 Configuring bandwidth guarantee ..................................................................................................... 274
12.6.4 Configuring hierarchical bandwidth gaurantee ................................................................................. 275
12.6.5 Checking configurations ................................................................................................................... 276
12.7 Configuring MPLS QoS CAR .................................................................................................................... 277
12.7.1 Preparing for configurations ............................................................................................................. 277
12.7.2 Configuring LSP QoS CAR .............................................................................................................. 277
12.7.3 Configuring PWE3 QoS CAR .......................................................................................................... 277
12.7.4 Configuring VPLS QoS CAR ........................................................................................................... 278
12.7.5 Checking configurations ................................................................................................................... 278
12.8 Configuring L3VPN QoS ........................................................................................................................... 278
12.8.1 Preparing for configurations ............................................................................................................. 278
12.8.2 Configuring VRF QoS ...................................................................................................................... 279
12.8.3 Checking configurations ................................................................................................................... 279
12.9 Configuring MPLS H-QoS......................................................................................................................... 279
12.9.1 Preparing for configurations ............................................................................................................. 279
12.9.2 Configuring H-QoS of LSP ............................................................................................................... 280
12.9.3 Configuring H-QoS of PWE3 ........................................................................................................... 280
12.9.4 Configuring H-QoS of VPLS. ........................................................................................................... 281
12.9.5 Checking configurations ................................................................................................................... 281
12.10 Maintenance ............................................................................................................................................. 281
12.11 Configuration examples............................................................................................................................ 282
12.11.1 Example for configuring rate limiting based on traffic policy ........................................................ 282
12.11.2 Example for configuring queue scheduling and congestion avoidance ........................................... 285
12.11.3 Example for configuring interface-based rate limiting.................................................................... 288

Raisecom Proprietary and Confidential

xviii
Copyright © Raisecom Technology Co., Ltd.
 Raisecom
iTN8800 (P100R002) Configuration Guide Contents

12.11.4 Examples for configuring MPLS H-QoS ........................................................................................ 289

12.11.5 Examples for configuring MPLS QoS CAR ................................................................................... 292

13 OAM .......................................................................................................................................... 295

13.1 Configuring EFM ....................................................................................................................................... 295
13.1.1 Preparing for configurations ............................................................................................................. 295
13.1.2 Configuring EFM basic functions ..................................................................................................... 295
13.1.3 Configuring EFM active functions .................................................................................................... 296
13.1.4 Configuring EFM passive functions ................................................................................................. 297
13.1.5 Configuring link monitoring and fault indication ............................................................................. 298
13.1.6 Configuring extended OAM ............................................................................................................. 299
13.1.7 Checking configurations ................................................................................................................... 300
13.2 Configuring CFM ....................................................................................................................................... 300
13.2.1 Preparing for configurations ............................................................................................................. 300
13.2.2 Enabling CFM ................................................................................................................................... 301
13.2.3 Configuring CFM basic functions ..................................................................................................... 301
13.2.4 Configuring fault detection ............................................................................................................... 302
13.2.5 Configuring fault acknowledgement ................................................................................................. 303
13.2.6 Configuring fault location ................................................................................................................. 304
13.2.7 Configuring AIS ................................................................................................................................ 305
13.2.8 Configuring LCK .............................................................................................................................. 306
13.2.9 Configuring CSF ............................................................................................................................... 307
13.2.10 Checking configurations ................................................................................................................. 307
13.3 Configuring MPLS-TP OAM ..................................................................................................................... 308
13.3.1 Preparing for configurations ............................................................................................................. 308
13.3.2 Enabling MPLS-TP CFM.................................................................................................................. 309
13.3.3 Configuring MPLS-TP CFM ............................................................................................................ 309
13.3.4 Configuring MPLS-TP fault detection .............................................................................................. 310
13.3.5 Configuring MPLS-TP fault acknowledgement ................................................................................ 311
13.3.6 Configuring MPLS-TP fault location ................................................................................................ 311
13.3.7 Configuring MPLS-TP AIS ............................................................................................................... 312
13.3.8 Configuring MPLS-TP CSF .............................................................................................................. 312
13.3.9 Configuring MPLS-TP LCK ............................................................................................................. 313
13.3.10 Configuring MPLS-TP SLA operation............................................................................................ 313
13.3.11 Configuring SLA scheduling and enabling operation scheduling ................................................... 314
13.3.12 Configuring fault relay based on MPLS-TP OAM and BFD alarm linkage ................................... 314
13.3.13 Checking configurations ................................................................................................................. 315
13.4 Configuring BFD ....................................................................................................................................... 315
13.4.1 Preparing for configurations ............................................................................................................. 315
13.4.2 Configuring BFD session binding ..................................................................................................... 315
13.4.3 Configuring BFD session parameters ............................................................................................... 316
13.4.4 Checking configurations ................................................................................................................... 318

Raisecom Proprietary and Confidential

xix
Copyright © Raisecom Technology Co., Ltd.
 Raisecom
iTN8800 (P100R002) Configuration Guide Contents

13.5 Configuring SLA ........................................................................................................................................ 318

13.5.1 Preparing for configurations ............................................................................................................. 318
13.5.2 Configuring Y.1731-based test .......................................................................................................... 319
13.5.3 Configuring RFC2544 test ................................................................................................................ 321
13.5.4 Configuring alarm threshold ............................................................................................................. 322
13.5.5 Configuring SLA operation scheduling............................................................................................. 322
13.5.6 Checking configurations ................................................................................................................... 323
13.6 Configuring Y.1564 .................................................................................................................................... 323
13.6.1 Configuring service test .................................................................................................................... 324
13.6.2 Configuring service performance test ............................................................................................... 324
13.6.3 Scheduling test .................................................................................................................................. 325
13.6.4 Checking configurations ................................................................................................................... 326
13.7 Configuring link quality alarm ................................................................................................................... 326
13.7.1 Perparing for configurations ............................................................................................................. 326
13.7.2 Configuring link detection ................................................................................................................ 326
13.7.3 Checking configurations ................................................................................................................... 327
13.8 Maintenance ............................................................................................................................................... 327
13.9 Configuration examples ............................................................................................................................. 328
13.9.1 Examples for configuring BFD for sub-interface directly-connected single hop detection .............. 328
13.9.2 Examples for configuring BFD for IP single-hop detection .............................................................. 330
13.9.3 Examples for configuring BFD for PW detection ............................................................................. 332
13.9.4 Examples for configuring Y.1564 test ............................................................................................... 335

14 Security...................................................................................................................................... 342
14.1 Configuring storm control .......................................................................................................................... 342
14.1.1 Preparing for configurations ............................................................................................................. 342
14.1.2 Configuring storm control ................................................................................................................. 343
14.1.3 Checking configurations ................................................................................................................... 343
14.2 Configuring CPU protection ...................................................................................................................... 343
14.2.1 Preparing for configurations ............................................................................................................. 343
14.2.2 Configuring global CPU CAR .......................................................................................................... 344
14.2.3 Configuring interface CPU CAR ...................................................................................................... 344
14.2.4 Checking configurations ................................................................................................................... 344
14.3 Configuring memory monitoring ............................................................................................................... 345
14.3.1 Preparing for configurations ............................................................................................................. 345
14.3.2 Configuring memory monitoring ...................................................................................................... 345
14.3.3 Checking configurations ................................................................................................................... 345
14.4 Configuring CPU monitoring ..................................................................................................................... 345
14.4.1 Preparing for configurations ............................................................................................................. 345
14.4.2 Viewing CPU monitoring information .............................................................................................. 346
14.4.3 Configuring CPU monitoring alarm .................................................................................................. 346
14.4.4 Checking configruations ................................................................................................................... 346

Raisecom Proprietary and Confidential

xx
Copyright © Raisecom Technology Co., Ltd.
 Raisecom
iTN8800 (P100R002) Configuration Guide Contents

14.5 Configuring RADIUS ................................................................................................................................ 346

14.5.1 Preparing for configurations ............................................................................................................. 346
14.5.2 Configuring RADIUS authentication ................................................................................................ 347
14.5.3 Configuring RADIUS accounting ..................................................................................................... 347
14.5.4 Checking configurations ................................................................................................................... 348
14.6 Configuring TACACS+ .............................................................................................................................. 348
14.6.1 Preparing for configurations ............................................................................................................. 348
14.6.2 Configuring TACACS+ authentication ............................................................................................. 348
14.6.3 Configuring TACACS+ accounting .................................................................................................. 349
14.6.4 Checking configurations ................................................................................................................... 349
14.7 Configuring dot.1x ..................................................................................................................................... 349
14.7.1 Preparing for configurations ............................................................................................................. 349
14.7.2 Configuring dot.1x ............................................................................................................................ 350
14.7.3 Checking configurations ................................................................................................................... 350
14.8 Configuring interface isolation ................................................................................................................... 351
14.8.1 Preparing for configurations ............................................................................................................. 351
14.8.2 Configuring interface isolation ......................................................................................................... 351
14.8.3 Checking configurations ................................................................................................................... 351
14.9 Configuring port mirroring ......................................................................................................................... 351
14.9.1 Preparing for configurations ............................................................................................................. 351
14.9.2 Configuring port mirroring ............................................................................................................... 352
14.9.3 Checking configurations ................................................................................................................... 352
14.10 Configuring URPF ................................................................................................................................... 353
14.10.1 Preparing for configurations ........................................................................................................... 353
14.10.2 Configuring URPF .......................................................................................................................... 353
14.11 Maintenance ............................................................................................................................................. 353
14.12 Configuration examples ........................................................................................................................... 354
14.12.1 Examples for configuring storm control ......................................................................................... 354
14.12.2 Examples for configuring RADIUS ................................................................................................ 355
14.12.3 Examples for configuring TACACS+ ............................................................................................. 356

15 Reliability ................................................................................................................................. 357

15.1 Configuring link aggregation ..................................................................................................................... 357
15.1.1 Preparing for configurations ............................................................................................................. 357
15.1.2 Configuring manual link aggregation ............................................................................................... 358
15.1.3 Configuring static LACP link aggregation ........................................................................................ 359
15.1.4 Configuring mLACP link aggregation .............................................................................................. 360
15.1.5 Configuring manual backup link aggregation ................................................................................... 361
15.1.6 Configuring static LACP backup link aggregation ........................................................................... 361
15.1.7 Checking configurations ................................................................................................................... 362
15.2 Configuring interface backup ..................................................................................................................... 363
15.2.1 Preparing for configurations ............................................................................................................. 363

Raisecom Proprietary and Confidential

xxi
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide Contents

15.2.2 Configuring interface backup group ................................................................................................. 363

15.2.3 Checking configurations ................................................................................................................... 364
15.3 Configuring ELPS ...................................................................................................................................... 364
15.3.1 Preparing for configurations ............................................................................................................. 364
15.3.2 Creating protection pair .................................................................................................................... 364
15.3.3 Configuring ELPS fault detection modes .......................................................................................... 365
15.3.4 (Optional) configuring ELPS switching control ............................................................................... 366
15.3.5 Checking configurations ................................................................................................................... 367
15.4 Configuring ERPS ...................................................................................................................................... 367
15.4.1 Preparing for configurations ............................................................................................................. 367
15.4.2 Creating ERPS protection ring .......................................................................................................... 368
15.4.3 (Optional) creating ERPS protection sub-ring .................................................................................. 370
15.4.4 Configuring ERPS fault detection modes ......................................................................................... 371
15.4.5 (Optional) configuring ERPS switching control ............................................................................... 372
15.4.6 Checking configurations ................................................................................................................... 372
15.5 Configuring PW redundancy protection ..................................................................................................... 372
15.5.1 Preparing for configurations ............................................................................................................. 372
15.5.2 Configuring PW redundancy protection ........................................................................................... 373
15.5.3 Configuring service PW to be bound with management PW ............................................................ 373
15.5.4 Checking configurations ................................................................................................................... 374
15.6 Configuring MPLS linear protection switching ......................................................................................... 374
15.6.1 Preparing for configurations ............................................................................................................. 374
15.6.2 Configuring MPLS linear protection switching ................................................................................ 374
15.6.3 Checking configurations ................................................................................................................... 375
15.7 Configuring PW dual-homed protection switching .................................................................................... 376
15.7.1 Preparing for configurations ............................................................................................................. 376
15.7.2 Configuration flows .......................................................................................................................... 376
15.7.3 Configuring ICCP channel ................................................................................................................ 377
15.7.4 Configuring PW ................................................................................................................................ 378
15.7.5 Configuring PW dual-homed protection group ................................................................................. 378
15.7.6 Configuring PW dual-homed protection switching attributes ........................................................... 379
15.8 Configuring VPN FRR ............................................................................................................................... 380
15.8.1 Preparing for configurations ............................................................................................................. 380
15.8.2 Configuring VPN FRR ...................................................................................................................... 381
15.9 Configuring HA hot backup ....................................................................................................................... 382
15.9.1 Preparing for configurations ............................................................................................................. 382
15.9.2 Configuring HA switching ................................................................................................................ 382
15.9.3 Checking configurations ................................................................................................................... 382
15.10 Configuring VRRP ................................................................................................................................... 382
15.10.1 Preparing for configurations ........................................................................................................... 382
15.10.2 Configuration procedure ................................................................................................................. 383
15.10.3 Configuring VRRP backup group ................................................................................................... 383

Raisecom Proprietary and Confidential

xxii
Copyright © Raisecom Technology Co., Ltd.
 Raisecom
iTN8800 (P100R002) Configuration Guide Contents

15.10.4 (Optional) configuring ping function of VRRP virtual IP address .................................................. 384
15.10.5 Configuring VRRP monitoring interface ........................................................................................ 384
15.10.6 Configuring VRRP fast switching ................................................................................................... 384
15.10.7 Checking configurations ................................................................................................................. 385
15.11 Configuring PRBS test ............................................................................................................................. 385
15.11.1 Preparing for configurations ............................................................................................................ 385
15.11.2 Configuring PRBS .......................................................................................................................... 385
15.11.3 Checking configurations ................................................................................................................. 386
15.12 Maintenance ............................................................................................................................................. 386
15.13 Configuration examples ........................................................................................................................... 386
15.13.1 Example for configuring manual link aggregation .......................................................................... 386
15.13.2 Example for configuring static LACP link aggregation .................................................................. 389
15.13.3 Example for configuring PW dual-homed protection switching ..................................................... 390
15.13.4 Examples for configuring PW redundancy protection .................................................................... 397

16 Appendix .................................................................................................................................. 408

16.1 Terms .......................................................................................................................................................... 408
16.2 Acronyms and abbreviations ...................................................................................................................... 410

Raisecom Proprietary and Confidential

xxiii
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide Figures

Figures

Figure 1-1 Configuring parameters for Hyper Terminal ...................................................................................... 11

Figure 1-2 Working as the Telnet server ............................................................................................................... 12

Figure 1-3 Working as the Telnet client ............................................................................................................... 12

Figure 2-1 Networking with RClink remote management ................................................................................... 47

Figure 2-2 Networking with hardware monitoring alarms output ........................................................................ 54

Figure 4-1 Networking with remote zero-configuration in the private network under the IP RAN CO device ... 75

Figure 6-1 Configuring clock synchronization based on SyncE .......................................................................... 97

Figure 8-1 Application scenario of Proxy ARP .................................................................................................. 113

Figure 8-2 Application scenario of proxy ARP/DNP for PW ............................................................................. 114

Figure 8-3 Configuring DHCP v4 Relay ............................................................................................................ 118

Figure 8-4 Configuring DHCP v4 server ........................................................................................................... 119

Figure 10-1 Configuring static bidirectional LSP without IP capability ............................................................ 182

Figure 10-2 Configuring LDP-based dynamic LSP ........................................................................................... 187

Figure 10-3 Configuring RSVP-TE-based dynamic LSP ................................................................................... 190

Figure 10-4 Configuring manual LDP FRR ....................................................................................................... 193

Figure 10-5 Configuring automatic LDP FRR ................................................................................................... 199

Figure 10-6 Configuring TE FRR ...................................................................................................................... 206

Figure 10-7 Configuring TE FRR node protection ............................................................................................ 213

Figure 11-1 MPLS L3VPN network topology ................................................................................................... 229

Figure 11-2 Configuring static Tunnel to carry static VPWS services ............................................................... 236

Figure 11-3 Configuring RSVP-TE-based dynamic Tunnel to carry dynamic VPWS services ......................... 238
Figure 11-4 Configuring MPLS L2VPN services .............................................................................................. 241

Figure 11-5 Configuring L3VPN networking .................................................................................................... 253

Figure 12-1 Configuring rate limiting based on traffic policy ........................................................................... 282

Figure 12-2 Configuring queue scheduling and congestion avoidance .............................................................. 285

Figure 12-3 Configuring interface-based rate limiting ....................................................................................... 288

Raisecom Proprietary and Confidential

xxiv
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide Figures

Figure 12-4 MPLS H-QoS networking .............................................................................................................. 290

Figure 12-5 MPLS H-QoS priority scheduling .................................................................................................. 290

Figure 12-6 MPLS QoS CAR networking ......................................................................................................... 293

Figure 13-1 BFD for sub-interface directly-connected single hop detection ..................................................... 328

Figure 13-2 BFD for IP single-hop detection ..................................................................................................... 330

Figure 13-3 Configuring BFD for PW detection ................................................................................................ 332

Figure 13-4 Y.1564 test ...................................................................................................................................... 335

Figure 14-1 Configuring storm control .............................................................................................................. 354

Figure 14-2 Configuring RADIUS ..................................................................................................................... 355

Figure 14-3 Configuring TACACS+ .................................................................................................................. 356

Figure 15-1 PW dual-home protection application scenario .............................................................................. 376

Figure 15-2 Flow for configuring PW dual-homed protection switching .......................................................... 377

Figure 15-3 CE dual-homed networking ............................................................................................................ 381

Figure 15-4 VRRP configuration procedure....................................................................................................... 383

Figure 15-5 Configuring manual link aggregation ............................................................................................. 387

Figure 15-6 Configuring LACP link aggregation ............................................................................................... 389

Figure 15-7 Configuring PW dual-homed protection switching ........................................................................ 391

Figure 15-8 CE accessing multi-section PWs asymmetrically ........................................................................... 398

Figure 15-9 Data preparation ............................................................................................................................. 398

Raisecom Proprietary and Confidential

xxv
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

1 Basic configurations

This chapter describes basic information and configuration procedures of the iTN8800, as
well as related configuration examples, including following sections:
 CLI
 Accessing device
 Backup and upgrade
 Device management
 Configuring RMON
 Configuration examples

1.1 CLI
1.1.1 Overview
The Command Line Interface (CLI) is a medium for you to communicate with the iTN8800.
You can configure, monitor, and manage the iTN8800 through the CLI.
You can log in to the iTN8800 through the terminal equipment or through a computer that
runs the terminal emulation program. Enter commands at the system prompt.
The CLI supports the following features:
 Configure the iTN8800 locally through the Console interface.
 Configure the iTN8800 locally or remotely through Telnet/Secure Shell v2 (SSHv2).
 Commands are classified into different levels. You can execute the commands that
correspond to your level only.
 The commands available to you depend on which mode you are currently in.
 Shortcut keys can be used to execute commands.
 Check or execute a historical command by checking command history. The last 20
historical commands can be saved on the iTN8800.
 Enter a question mark (?) at the system prompt to obtain online help.
 The iTN8800 supports multiple intelligent analysis methods, such as fuzzy match and
context association.

Raisecom Proprietary and Confidential

1
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

1.1.2 Levels
The iTN8800 classifies commands into 16 levels in a descending order:
 0–4: checking level. You can execute basic commands, such as clear and history, for
clearing system information and showing command history.
 5–10: monitoring level. You can execute commands, such as show, for system
maintenance.
 11–14: configuration level. You can execute commands for configuring services, such as
Virtual Local Area Network (VLAN) and Internet Protocol (IP) routing.
 15: management level. You can execute commands for system running.

1.1.3 Modes
The command mode is an environment where a command is executed. A command can be
executed in one or multiple certain modes. The commands available to you depend on which
mode you are currently in.
After connecting the iTN8800, if the iTN8800 adopts default configurations, a Login prompt
will be displayed. Enter the user name (raisecom) and password (raisecom) to enter the user
EXEC mode, where the following command is displayed:

Raisecom>

Enter the enable command and press Enter. Then enter the correct password, and press Enter
to enter privileged EXEC mode. The default password is raisecom.

Raisecom>enable
Password:
Raisecom#

In privileged EXEC mode, enter the config command to enter global configuration mode.

Raisecom#config
Raisecom(config)#

 The CLI prompts Raisecom is a default host name. You can modify it by executing
the hostname string command in privileged EXEC mode.
 Commands executed in global configuration mode can also be executed in other
modes. The functions vary on command modes.
 You can enter the exit or quit command to return to the upper command mode.
However, in privileged EXEC mode, you need to execute the disable command to
return to user EXEC mode. In address family configuration mode, you need to
execute the exit-address-family command to return to BGP configuration mode.

Raisecom Proprietary and Confidential

2
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

 You can enter the end command to return to privileged EXEC mode from any
modes but user EXEC mode and privileged EXEC mode.
Command modes supported by the iTN8800 are listed in the following table.

Mode Entry Prompt

User EXEC Log in to the iTN8800, and then enter Raisecom>
the correct user name and password.
Privileged EXEC In user EXEC mode, use the enable Raisecom#
command and correct password.
Global configuration In privileged EXEC mode, use the Raisecom(config)#
config command.
Interface In global configuration mode, use the Raisecom(config-
configuration interface ethernet unit/slot/port port)#
command.
In global configuration mode, use the
interface fastethernet unit/slot/port
command.
In global configuration mode, use the
interface gigethernet unit/slot/port
command.
In global configuration mode, use the
interface tengigethernet unit/slot/port
command.
Sub-interface In global configuration mode, use the Raisecom(config-
configuration interface ethernet unit/slot/port.sub- subif)#
interface command.
VLAN interface In global configuration mode, use the Raisecom(config-
configuration interface vlan vlan-id command. vlanif)#

Tunnel interface In global configuration mode, use the Raisecom(config-

configuration interface tunnel tunnel-id command. tunnel)#

Loopback interface In global configuration mode, use the Raisecom(config-

configuration interface loopback interface-number loopback)#
command.
VRF configuration In global configuration mode, use the Raisecom(config-
ip vrf vrf-name command. vrf)#

Route mapping In global configuration mode, use the Raisecom(config-

configuration route-map map-name { permit | route-map)#
deny } number command.
OSPF configuration In global configuration mode, use the Raisecom(config-
router ospf process-id [ router-id router-ospf)#
router-id ] command.

Raisecom Proprietary and Confidential

3
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Mode Entry Prompt

OSPFv3 configuration In global configuration mode, use the Raisecom(config-
ipv6 router ospf process-id [ router- ospf6)#
id router-id ] command.
BGP configuration In global configuration mode, use the Raisecom(config-
router bgp [ as-id ] command. router)#

BGP VPNv4 address In BGP configuration mode, use the Raisecom(config-

family configuration address-family vpnv4 [ unicast ] router-af)#
command.
BGP VPN instance In BGP configuration mode, use the Raisecom(config-
IPv4 unicast address address-family ipv4 vrf vrf-name router-af)#
family configuration command.
ILSP configuration In global configuration mode, use the Raisecom(config-
mpls bidirectional static-lsp ingress ingress-lsp)#
lsp-name lsr-id egress-lsr-id tunnel-id
tunnel-id command.
ELSP configuration In global configuration mode, use the Raisecom(config-
mpls bidirectional static-lsp egress egress-lsp)#
lsp-name lsr-id ingress-lsr-id tunnel-
id tunnel-id command.
TLSP configuration In global configuration mode, use the Raisecom(config-
mpls bidirectional static-lsp transit transit-lsp)#
lsp-name lsr-id ingress-lsr-id egress-
lsr-id tunnel-id tunnel-id [ standby ] ]
command.
Explicit path In global configuration mode, use the Raisecom(config-
configuration mpls explicit-path path-name mpls-exp-path)#
command.
Tunnel policy In global configuration mode, use the Raisecom(config-
configuration tunnel-policy policy-name command. tunnelpolicy)#

Remote peer In global configuration mode, use the Raisecom(config-

configuration mpls ldp targeted neighbour ip- ldp-remote-peer)#
address command.
VSI configuration In global configuration mode, use the Raisecom(config-
mpls vsi vsi-name static command. vsi)#

VLAN configuration In global configuration mode, use the Raisecom(config-

vlan vlan-id command. vlan)#

Basic IP ACL In global configuration mode, use the Raisecom(config-

configuration access-list acl-number command. The acl-ipv4-basic)#
acl-number parameter ranges from
1000 to 1999.

Raisecom Proprietary and Confidential

4
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Mode Entry Prompt

Extended IP ACL In global configuration mode, use the Raisecom(config-
configuration access-list acl-number command. The acl-ipv4-
acl-number parameter ranges from advanced)#
2000 to 2999.
MAC ACL In global configuration mode, use the Raisecom(config-
configuration access-list acl-number command. The acl-mac)#
acl-number parameter ranges from
3000 to 3999.
MPLS ACL In global configuration mode, use the Raisecom(config-
configuration access-list acl-number command. The acl-mpls)#
acl-number parameter ranges from
4000 to 4999.
User ACL In global configuration mode, use the Raisecom(config-
configuration access-list acl-number command. The acl-map)#
acl-number parameter ranges from
5000 to 5999.
cos-remark In global configuration mode, use the Raisecom(cos-
configuration mls qos mapping cos-remark profile- remark)#
id command.
cos-to-pri In global configuration mode, use the Raisecom(cos-to-
configuration mls qos mapping cos-to-local- pri)#
priority profile-id command.
dscp-mutation In global configuration mode, use the Raisecom(dscp-
configuration mls qos mapping dscp-mutation mutation)#
profile-id command.
dscp-to-pri In global configuration mode, use the Raisecom(dscp-to-
configuration mls qos mapping dscp-to-local- pri)#
priority profile-id command.
exp-to-pri In global configuration mode, use the Raisecom(exp-to-
configuration mls qos mapping exp-to-local- pri)#
priority profile-id command.
pri-to-exp In global configuration mode, use the Raisecom(pri-to-
configuration mls qos mapping local-priority-to- exp)#
exp profile-id command.
WRED profile In global configuration mode, use the Raisecom(wred)#
configuration mls qos wred profile profile-id
command.
Flow profile In global configuration mode, use the Raisecom(flow-
configuration mls qos flow-queue profile command. queue)#

CMAP configuration In global configuration mode, use the Raisecom(config-

class-map class-map-name command. cmap)#

Raisecom Proprietary and Confidential

5
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Mode Entry Prompt

Traffic monitoring In global configuration mode, use the Raisecom(traffic-
profile configuration mls qos policer-profile policer-name policer)#
[ single ] command.
PMAP configuration In global configuration mode, use the Raisecom(config-
policy-map policy-map-name pmap)#
command.
Traffic policy bound In PMAP configuration mode, use the Raisecom(config-
with traffic class-map class-map-name command. pmap-c)#
classification
configuration
Service instance In global configuration mode, use the Raisecom(config-
configuration service csi-id level md-level command. service)#

BFD session In global configuration mode, use the Raisecom(config-

configuration bfd session-id command. bfd-session)#

In global configuration mode, use the

bfd session-id bind peer-ip ip-address
ip-mask [ vrf-name vrf-name ]
command.
In global configuration mode, use the
bfd session-id bind peer-ip ip-address
interface gigaethernet interface-
number command.
In global configuration mode, use the
bfd session-id bind ldp-lsp peer-ip ip-
address ip-mask nexthop ip-address
command.
In global configuration mode, use the
bfd session-id bind mpls interface
tunnel tunnel-if cr-lsp command.
In global configuration mode, use the
bfd session-id bind pw vc-id peer-ip
[ pw-ttl ttl ] command.

1.1.4 Shortcut keys

The iTN8800 supports the following shortcut keys.

Shortcut key Description

Press the up arrow (↑) key. The previous command is displayed. If no previous
command is available, no change is shown on the
screen after you press the key.

Raisecom Proprietary and Confidential

6
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Shortcut key Description

Press the down arrow (↓) key. The next command is displayed. If no previous
command is available, no change is shown on the
screen after you press the key.
Press the left arrow (←) key. Move the cursor back one character. If the cursor is in
front of the command, no change is shown on the
screen after you press the key.
Press the right arrow (→) key. Move the cursor forward one character. If the cursor is
behind the command, no change is shown on the
screen after you press the key.
Press the Backspace key. Erase the character to the left of the cursor. If the
cursor is in front of the command, no change is shown
on the screen after you press the key.
Press the Tab key. When you press it after entering an incomplete
keyword, the system automatically executes some
commands:
 If the incomplete keyword matches a unique
complete keyword, the unique complete keyword
replaces the incomplete keyword, with the cursor
forward a space from the unique complete keyword.
 If the incomplete keyword matches more complete
keywords, you can press the Tab key to alternate the
matched complete keywords.
 If the incomplete keyword matches no complete key
word, you can press the Tab key to wrap, and then
error information is displayed.
Press Ctrl+A. Move the cursor to the beginning of the command line.
Press Ctrl+D or the Delete key. Delete the character at the cursor.
Press Ctrl+E. Move the cursor to the end of the command line.
Press Ctrl+K. Delete all characters from the cursor to the end of the
command line.
Press Ctrl+X. Delete all characters from the cursor to the beginning
of the command line.
Press Ctrl+Z. Return to privileged EXEC mode from the current
mode (excluding user EXEC mode).

1.1.5 Acquiring help

Complete help
You can acquire complete help under following three conditions:
 You can enter a question mark (?) at the system prompt to display a list of commands
and brief descriptions available for each command mode.

Raisecom Proprietary and Confidential

7
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Raisecom>?

The output is displayed as below:

clear Clear screen

enable Turn on privileged mode command
exit Exit current mode and down to previous mode
help Message about help
history Most recent history command
language Language of help message
list List command
quit Exit current mode and down to previous mode
show Show running system information
terminal Configure terminal

 After you enter a keyword, press the Space bar and enter a question mark (?), all
correlated commands and their brief descriptions are displayed if the question mark (?)
matches another keyword.

Raisecom(config)#show ?

The output is displayed as below:

access-list Access list

acl Access control list
alarm Alarm
arp ARP table information
banner banner
bfd Bidirectional Forwarding Detection

 After you enter a parameter, press the Space bar and enter a question mark (?),
associated parameters and descriptions of these parameters are displayed if the question
mark (?) matches a parameter.

Raisecom(config)#interface tunnel ?

The output is displayed as below:

<1-1024> Tunnel interface number

Raisecom Proprietary and Confidential

8
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Incomplete help
You can acquire incomplete help under following three conditions:
 After you enter part of a particular character string and a question mark (?), a list of
commands that begin with a particular character string is displayed.

Raisecom(config)#c?

The output is displayed as below:

cfm Connectivity fault management protocol
class-map Set class map
clear Clear screen
command-log Log the command to the file
cpu Configure cpu parameters
create Create static VLAN
cspf Cspf capability

 After you enter a command, press the Space, and enter a particular character string and a
question mark (?), a list of commands that begin with a particular character string is
displayed.

Raisecom(config)#show li?

The output is displayed as below:

license license
link-aggregation Link aggregation

 After you enter a partial command name and press the Tab, the full form of the keyword
is displayed if there is a unique match command. Otherwise, after you press the Tab,
different keywords will be displayed circularly and you can select one as required.

Error messages
The following table lists error messages that you may encounter while configure the iTN8800
on the CLI.

Error message Description

% Incomplete command. The input command is incomplete.
Error input in the position market by The keyword marked with "^" is invalid or does
'^' not exist.

Raisecom Proprietary and Confidential

9
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

1.2 Accessing device

1.2.1 Accessing device through Console interface

The Console interface of the iTN8800 is a Universal Serial Bus (USB) A-shaped
female interface, which is translated into a Universal Asynchronous
Receiver/Transmitter (UART) in the device.
The Console interface is used as an interface for the iTN8800 being connected to a PC that
runs the terminal emulation program. You can configure and manage the iTN8800 through
this interface. This management method does not involve network communication.
You must log in to the iTN8800 through the Console interface under the following 2
conditions:
 The iTN8800 is powered on for the first time.
 You cannot log in to the iTN8800 through Telnet.
To log in to the iTN8800 through the Console interface, follow these steps:

Before logging in to the iTN8800 through the USB interface, install the driver for
translating the USB interface into the UART interface to the PC.
Step 1 Use the configuration cable with dual USB male interfaces to connect the Console interface of
the iTN8800 with the USB interface of the PC.
Step 2 Run the terminal emulation program on the PC, such as Hyper Terminal on Microsoft
Windows XP. Enter the connection name at the Connection Description dialog box and then
click OK.
Step 3 Select COM N (N refers to the COM interface ID into which the USB interface is translated.)
at the Connect To dialog box and then click OK.
Step 4 Configure parameters as shown in Figure 1-1 and then click OK

Raisecom Proprietary and Confidential

10
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Figure 1-1 Configuring parameters for Hyper Terminal

Step 5 Enter the configuration interface and then enter the user name and password to log in to the
iTN8800. By default, both the user name and password are set to raisecom.

Hyper Terminal is not available on Windows Vista or Windows 7 Operating System

(OS). For these OSs, download Hyper Terminal package and install it.

1.2.2 Accessing device through Telnet

Through Telnet, you can remotely log in to the iTN8800 through a PC. In this way, it is not
necessary to prepare a PC for each iTN8800.
The iTN8800 provides the following Telnet services:
 Telnet Server: as shown in Figure 1-2, connect the PC and the iTN8800 and ensure that
the route between them is reachable. You can log in to and configure the iTN8800 by
running Telnet Client program on a PC.

Raisecom Proprietary and Confidential

11
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Figure 1-2 Working as the Telnet server

Before logging in to the iTN8800 through Telnet, you must log in to the iTN8800
through the Console interface and configure the IP address of the SNMP interface.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface fastethernet Enter SNMP interface configuration mode.
1/0/1
3 Raisecom(config-fastethernet1/0/1)#ip Configure the IP address of the SNMP
address ip-address [ ip-mask ] interface and return to global configuration
Raisecom(config-fastethernet1/0/1)#exit mode.
By default, it is 192.168.4.28.
4 Raisecom(config)#telnet-server accept (Optional) configure the interface that
interface-type interface-list supports Telnet.
5 Raisecom(config)#telnet-server close (Optional) close the specified Telnet session.
terminal-telnet session-number
6 Raisecom(config)#telnet-server max- (Optional) configure the maximum number of
session session-number Telnet sessions supported by the iTN8800.
By default, it is 5.
7 Raisecom(config)#telnet-server listen vrf Configure VRF monitored by Telnet to
vpn-instance-name manage VRFs.

 Telnet Client: after connecting the iTN8800 through the terminal emulation program
running on the PC, you can log in to another device by entering the telnet command and
then configure and manage the device. As shown in Figure 1-3, iTN A works as Telnet
Server and Telnet Client.

Figure 1-3 Working as the Telnet client

Raisecom Proprietary and Confidential

12
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Step Command Description

1 Raisecom#telnet ip-address [ port port-number] Log in to another device through Telnet.

1.2.3 Accessing device through SSHv2

Telnet is an authentication mode that is lack of security. In addition, it adopts Transmission
Control Protocol (TCP) to transmit the password and data in clear text. It will cause malicious
attack, such as Deny of Service (DoS), IP address spoofing, and route spoofing because only
Telnet service is provided. With more attention is put on network security, the traditional
modes (Telnet and FTP) for transmitting the password and data in clear text are not accepted
gradually.
Secure Shell (SSH) is a protocol, which is used to provide secure remote login and other
security network services in an insecure network. When you log in to a device in an insecure
network environment, SSH will encrypt the data automatically when you transmit these data.
When data is transmitted to the destination, the SSH will decrypt the data automatically.
Therefore, SSH can provide secure information assurance. SSH can prevent devices from
being attacked by clear text password intercepting and middleman, as well as prevent Domain
Name Server (DNS) spoofing and IP spoofing. Because the transmitted data is compressed,
the SSH can provide the greater transmission speed.
SSH adopts the client-server mode. The SSH server receives requests from SSH clients and
then begin to authenticate them. After successful authentication, SSH connection is
established. Therefore, you can log in to the SSH server through the SSH client. The
authentication is a series of key processing actions performed between the server and client.
At present, SSH has a new version of SSHv2. The iTN8800 supports SSHv2.
Before accessing the iTN8800 through SSHv2, you must log in to the iTN8800 through the
Console interface and enable SSH service.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#generate ssh- Generate local SSHv2 key pair and designate its length.
key length
3 Raisecom(config)#ssh2 server Start the SSHv2 server.
4 Raisecom(config)#ssh2 server (Optional) configure SSHv2 authentication method.
authentication { password |
rsa-key }
5 Raisecom(config)#ssh2 server (Optional) when the rsa-key authentication method is
authentication public-key adopted, type the public key of clients to the iTN8800.
6 Raisecom(config)#ssh2 server (Optional) configure SSHv2 authentication timeout. The
authentication-timeout period iTN8800 refuses to authenticate and open the connection
when client authentication time exceeds the upper threshold.
7 Raisecom(config)#ssh2 server (Optional) configure the allowable times for SSHv2
authentication-retries times authentication failure. The iTN8800 refuses to authenticate
and open the connection when client authentication failure
times exceed the upper threshold.

Raisecom Proprietary and Confidential

13
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Step Command Description

8 Raisecom(config)#ssh2 server (Optional) configure the SSHv2 listening port ID.
port port-id

When configuring the SSHv2 listening port ID, the

input parameter cannot take effect immediately
without rebooting the SSHv2 service.
9 Raisecom(config)#ssh2 server (Optional) enable SSHv2 session.
session session-list enable

1.3 Backup and upgrade

1.3.1 Introduction
The iTN8800 uses the file system to manage system files. The file system is used to create,
delete, and modify files and directories.
System files refer to files required for operating the iTN8800, including the BootROM file,
License file, Paf file, patch file, log file, configuration file, and system software. Based on the
download location, these files are saved to the memory of the NXU card or service card.

System file
System files refer to the software and files required for operating the iTN8800, including the
BootROM file, system configuration file, system startup file and FPGA file. These files are
saved to the memory of the iTN8800.
File management includes backup, update, load and deletion of files.

System Bootrom file

The system Bootrom file (BootROM software) is used to boot the device. After the device is
powered on, the BootROM software is running to initialize the iTN8800. You can upgrade the
BootROM software if a new version is available.

System startup file

The system startup file (with the .z suffix) is used to start and operate the iTN8800, support
normal operating, and implement functions.
You can upgrade the system startup file if a new version is available. In addition, to prevent a
system fault, you can back up the system startup file.
The iTN8800 supports 2 sets of system startup software simultaneously, providing primary
and secondary switching between dual systems.

Raisecom Proprietary and Confidential

14
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

PAF file
PAF is used to control functions and specifications of the device. The PAF file defines all
specification parameters supported by the device, such as, local and remote zero-configuration
mode. It is able to confirm specifications supported by the device according to the parameter
range. The following examples show several important parameter ranges:
 ZERO_CONFIG_MODE_CLIENT: the value 0 indicates disabling remote zero-
configuration while the value 1 indicates enabling remote zero-configuration.
 ZERO_CONFIG_MODE_CLIENT: if ZERO_CONFIG_MODE_CLIENT=1, the value
0 indicates disabling China Telecom zero-configuration while the value 1 indicates
enabling China Telecom zero-configuration. The zero-configuration scheme for China
Telecom is to request the IP address on the first uplink interface.
 ZERO_CONFIG_MANAGE_VLAN: the value 0 indicates that the VLAN management
is not configured. All VLANs are covered when the IP address is automatically obtained.
After configuring parameters is complete, you could download parameters to the device
through the download command and reboot the iTN8800 through the reboot command. Then
the iTN8800 will take effect.
Other functions of the PAF file are as below:
 Support customizing the default IP address of the NMS interface.
 Support the naming convention of the product version, such as "product version.paf" for
the PAF file.

System configuration file

The system configuration file (with the .cfg suffix) is configuration items to be loaded when
the device is booted at this time or next time.
After being powered on, the iTN8800 reads the configuration file from the memory for
initialization. If there is no configuration file in the memory, the iTN8800 will use the default
configuration file.
Configuration parameters in the configuration file are divided into the following 2 types:
 Configuration parameters used for initialization are startup configurations.
 Configuration parameters used when a device is running properly are running
configurations.
You can modify running configurations through CLI. To make these modified running
configurations as startup configurations when the iTN8800 is powered on next time, you
should save running configurations to the memory (by using the write command) as a
configuration file.
Operations on the system configuration file include loading, upgrading, backing up, and
deleting the system configuration file.

Backup
Backup means saving system files by copying them from the device memory and save them
into the server memory to recover files if the iTN8800 fails. By doing so, the iTN8800 will
run normally as before. The pervious system file should be restored under the following
conditions:
 System files are lost or damaged due to the device fault.
Raisecom Proprietary and Confidential
15
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

 The device fails due to failure in system upgrade.

The iTN8800 supports backing up system configuration files, system startup files, and system
log files.

Upgrade
After features are added or known bugs are fixed, a new software version will be released.
Then you can upgrade the software.
The iTN8800 supports 2 upgrade modes:
 FTP upgrade in BootROM mode
 FTP/TFTP upgrade in system configuration mode
The iTN8800 complies with FTP/TFTP based on IPv4.

1.3.2 Backing up files

You need to establish a FTP/TFTP environment before backing up system files. Generally,
you can use a PC to serve as the FTP/TFTP server and the iTN8800 as the client, with the
basic requirements as below:
 Connect the iTN8800 to the PC through the NEG interface.
 Configure the IP address of the PC to interconnect with the iTN8800.

Step Command Description

1 Raisecom#upload { logging-file | startup-config } Upload the system bootstrap files
{ ftp ip-address user-name password file-name | and system configuration files to
tftp ip-address file-name } the backup server.

1.3.3 Upgrading files

Upgrading files in privileged EXEC mode

You need to establish a FTP/TFTP environment before upgrading system files. Generally, you
can use a PC to serve as the FTP/TFTP server and the iTN8800 to be the client, with the basic
requirements as below:
 Connect the iTN8800 to the PC through the NEG interface.
 Configure the IP address of the PC to interconnect with the iTN8800.
Step Command Description
1 Raisecom#download { boot | file | Download system files through FTP or TFTP.
license | paf | patch | system-boot
| startup-config } { ftp ip-address
username password filename | tftp
ip-address filename }
2 Raisecom#boot next-startup file-name Specify the next bootstrap file for the device.
3 Raisecom#reboot [ now ] Restart the device. The device will automatically
load the downloaded system startup file.

Raisecom Proprietary and Confidential

16
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Upgrading files in BootROM mode

Under the following conditions, you need to upgrade system software through BootROM
mode.
 First startup
 System file damage
 Startup failure
You need to establish a FTP environment before upgrading system software in BootROM
mode. Generally, you can use a PC to serve as the FTP server and the iTN8800 to be the client,
with the basic requirements as below:
 Connect the iTN8800 to the FTP server through NEG interface.
 Configure the FTP server to make it available.

Step Operation
1 Log in to the iTN8800 with the identity of an administrator and then enter privileged EXEC mode.
Restart the iTN8800 through the reboot command.

Raisecom#reboot
Please input 'yes' to confirm:yes
Rebooting ...

begin...

ram size:128M testing...done

Init flash ...Done

iTN8800_BOOTSTRAP_5.1.5_20151224, Raisecom Compiled Dec 24 2015,18:05:41

Base Ethernet MAC address: 00:0e:5e:45:45:45

Press space into Bootstrap menu...

0

Raisecom Proprietary and Confidential

17
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Step Operation
2 When it prompts "Press space into Bootstrap menu...", press Space bar to enter the [raisecom] page.
Enter "?" to show the command lists.

[Raisecom]:?
? print this list
h print this list
b boot system
uf filename upload file
ls list files
R filename remove file
i modify network manage port ip address
r reboot system
ss switch system
u update system
ub update bootrom
ul update license

The entered letter should be case sensitive.

3 Enter " u " to download the system startup file through FTP and then replace the startup file. It will
show information as below:

Index Partition Free Size(byte)

--------------------------------------------------
1 core/ 36143104
Please select a partition: 1
choose mode for updating core file.
-----------------------------------
- 1. | serial -
-----------------------------------
- 2. | network -
-----------------------------------
please input your choice:2
configure network information ...
host ip address: 1.1.1.1
user: raisecom
password: raisecom
filename: iTN8800_package.z
Loading... Done
Saving file to flash...

Ensure that the accuracy of the entered file name. The length of the file name should be
not more than 80 bytes.

Raisecom Proprietary and Confidential

18
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Step Operation
4 Enter "ss" to select the system startup file which is to be loaded by the device during next startup.

[Raisecom]:ss
Current boot info:
primary:core/iTN8800_package.z
current:core/iTN8800_package.z
Index Partition Free Size(byte)
--------------------------------------------------
1 core/ 36143104
Please select a partition: 1
Index Filename system-version
---------------------------------------------------------------------------
1 iTN8800_package.z v1.0.0_20140619
Please select a image for next booting: 1
Save boot info...successful!
5 Enter "r" to rapidly execute the bootstrap file. The iTN8800 will automatically restart and load the
downloaded system startup file,

When upgrading files in BootROM file, ensure that the iTN8800-II-NXU is inserted
into slot 1.

1.3.4 Checking configurations

No. Command Description
1 Raisecom#show running-config Show running configurations of the system.
2 Raisecom#show startup-config Show the startup configuration file.
3 Raisecom#show version [ product | slot Show version information.
slot-id ]

1.3.5 Overall upgrade

The iTN8800 allows you to upgrade the entire device or service cards through the SD card.
Step 2 and Step 3 are optional. Choose one of them for upgrade.

No. Command Description

1 Raisecom#download file { ftp ip-address Download the system upgrade package to
username password | tftp ip-address } the sd0/ directory.
filename sd0/
2 Raisecom#upgrade system slot all version (Optional) upgrade the entire device.
version
3 Raisecom#upgrade system slot slot-id (Optional) upgrade the service card.
filename

Raisecom Proprietary and Confidential

19
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

1.4 Device management

1.4.1 Introduction
Simple Network Management Protocol (SNMP) is designed by the Internet Engineering Task
Force (IETF) to solve problems in managing network devices connected to the Internet.
Through SNMP, a NMS can manage all network devices that support SNMP, including
monitoring network status, modifying configurations of a network device, and receiving
network alarms. SNMP is the most widely used network management protocol in TCP/IP
networks

Working mechanism
SNMP is divided into two parts: Agent and NMS. The Agent is someone being managed in
the SNMP network while the NMS is the manager for the SNMP network. The Agent and
NMS communicate with each other by sending SNMP packets through UDP.
The iTN8800 communicates with the NView NNM system through SNMP packets. Raisecom
Nview NNM system can provide friendly Human Machine Interface (HMI) to facilitate
network management. The following functions can be implemented through it:
 Send request packets to the iTN8800.
 Receive reply packets and Trap packets from the iTN8800, and show result.
The Agent is a program installed in the iTN8800, implementing the following functions:
 Receive/reply request packets from Nview NNM system
 Read/write packets and generate response packets according to the packets type, then
return the result to Nview NNM system
Define trigger condition according to protocol modules, enter/exit from system or reboot
device when conditions are satisfied; the replying module sends Trap packets to NView NNM
system through Agent to report current status of device.

An Agent can be configured with several versions concurrently, and different versions
communicate with different NMSs. However, the SNMP version of the NMS must be
consistent with that of the connected agent so that they can intercommunicate
properly.

Protocol versions
Till now, SNMP has three versions: v1, v2c, and v3, described as below.
 SNMPv1 uses community name authentication mechanism. The community name, a
string defined by an agent, acts like a password. The NMS can visit the agent only by
specifying its community name correctly. If the community name carried in a SNMP
packet is not authenticated by the iTN8800, the packet will be dropped.
 Compatible with SNMPv1, SNMPv2c also uses community name authentication
mechanism. SNMPv2c supports more operation types, data types, and errored codes, and
thus better identifying errors.
 SNMPv3 uses User-based Security Model (USM) and View-based Access Control Model
(VACM) security mechanism. You can configure whether USM authentication is enabled

Raisecom Proprietary and Confidential

20
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

and whether encryption is enabled to provide higher security. USM authentication

mechanism is used to authenticate the senders so that illegal users will not be able to
access them. Encryption is to encrypt packets transmitted between the NMS and agents,
thus preventing interception.
The iTN8800 supports SNMP v1, SNMP v2c, and SNMP v3.

MIB
Management Information Base (MIB) is the collection of all objects managed by NMS. It
defines attributes for the managed objects:
 Name
 Access right
 Data type
The device-related statistic contents can be reached by accessing data items. Each proxy has
its own MIB. MIB can be taken as an interface between NMS and Agent, through which NMS
can read/write every managed object in Agent to manage and monitor the iTN8800.
MIB stores information in a tree structure, with unnamed root on the top. Nodes of the tree are
the managed objects, which take a unique path starting from root (OID) for identification.
SNMP protocol packets can access network devices by checking the nodes in MIB tree
directory.
The iTN8800 supports standard MIB and Raisecom-customized MIB.

1.4.2 Preparing for configurations

Scenario
To log in to the iTN8800 through the NMS, you should first configure SNMP basic functions.

Prerequisite
 Configure the IP addresses on the SNMP interface.
 Configure static router to link iTN8800 and NMS through the router.

1.4.3 Confiurating SNMP basic functions

For SNMP v3, SNMP v1 or SNMP v2c, you should configure them respectively:
Configure SNMP v3 on the target device as below.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#snmp-server access group-name Create and configure the SNMP
[ read view-name ] [write view-name ] [notify access groups.
view-name ][ context context-name { exact |
prefix } ] usm { noauthnopriv | authnopriv |
authpriv }
3 Raisecom(config)#snmp-server group name user user (Optional) configure the mapping
usm between users and access groups.

Raisecom Proprietary and Confidential

21
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Step Command Description

4 Raisecom(config)#snmp-server contact syscontact (Optional) configure the ID and
contact of network administrators.
5 Raisecom(config)#snmp-server host ip-address Configure the IP address of the
version 3 { noauthnopriv | authnopriv | authpriv } SNMP target host.
user-name [ udpport udpport ]
6 Raisecom(config)#snmp-server location sysLocation (Optional) specify the location for
placing the iTN8800.
7 Raisecom(config)#snmp-server user user-name Create a user and configure its
[ remote engine-id ] authentication { md5 | sha } authentication method.
key-word
8 Raisecom(config)#snmp-server view view-name oid- Configure SNMP view.
tree [ mask] { included | excluded }

Configure SNMP v1 or v2c on the target device as below.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#snmp-server community Create a community name and configure its
name [ view view ] { ro | rw } corresponding view and access priority.
3 Raisecom(config)#snmp-server contact (Optional) configure the ID and contact of
contact network administrators.
4 Raisecom(config)#snmp-server host ip- Configure the IP address of the SNMP target
address version { 1 | 2c } community- host.
string [ udpport port-id ]
5 Raisecom(config)#snmp-server location (Optional) specify the location for placing
location the iTN8800.
6 Raisecom(config)#snmp-server traps enable (Optional) enable the threshold crossing
cpu-threshold alarm on CPU utilization ratio.

1.4.4 Configuring Trap

Configuration steps in SNMP v1, v2c and v3 are the same except the configuration of
the target host. Choose it as required.
A Trap is used by the iTN8800 to send unrequested information to the NView NNM system
automatically, which is used to report some critical events.
Finish the following tasks before configuring Trap:
 Configure SNMP basic functions. SNMP v3 requires configuring the user name and
SNMP view.
 Configure routing protocols, and ensure routing between the iTN8800 and the NView
NNM system is available.
Raisecom Proprietary and Confidential
22
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter Layer 3 physical interface
interface-number configuration mode.
3 Raisecom(config-port)#ip address ip-address
vlan-id Configure the IP address of the iTN8800.

4 Raisecom(config-port)#exit Exit Layer 3 physical interface configuration

mode. Enter global configuration mode.
5 Raisecom(config)#snmp-server host ip-
address version 3 { noauthnopriv | (Optional) configure the SNMPv3 Trap
authnopriv | authpriv } name [ udpport
target host.
udpport ]
6 Raisecom(config)#snmp-server host ip- (Optional) configure the SNMP v1 and
address version { 1 | 2c } name [udpport SNMP v2c Trap target host.
udpport ]

1.4.5 Configuring KeepAlive Trap packets

By sending KeepAlive Trap packets, the iTN8800 makes the NMS discovery it in a short time
to improve working efficiency of the NMS and reduce workloads of network administrators.
The prerequisite for configuring KeepAlive Trap packets is that the route between the
iTN8800 and the NMS is reachable.

To avoid multiple devices to concurrently send KeepAlive Trap in the same period
and overburdened network management, configure the KeepAlive Trap packets to be
sent within a random period of "sending period+5s".
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#snmp-server Enable sending KeepAlive Trap packets.
keepalive-trap enable
By default, it is disable to send KeepAlive Trap packets.
3 Raisecom(config)#snmp-server (Optional) configure the period for sending KeepAlive
keepalive-trap interval period Trap packets.
By default, the period for sending KeepAlive Trap
packets is 300s.
4 Raisecom(config)#snmp-server (Optional) suspend the sending of KeepAlive Trap
keepalive-trap pause packets.

Raisecom Proprietary and Confidential

23
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

1.4.6 Checking configurations

No. Command Description
1 Raisecom#show snmp access Show configurations of the SNMP access group.
2 Raisecom#show snmp community Show configurations of the SNMP community.
3 Raisecom#show snmp config Show SNMP basic configurations.
4 Raisecom#show snmp group Show mapping between SNMP user and access group.
5 Raisecom#show snmp host Show information about the SNMP target host.
6 Raisecom#show snmp statistics Show SNMP statistics.
7 Raisecom#show snmp user Show SNMP user information.
8 Raisecom#show snmp view Show SNMP view information.
9 Raisecom#show keepalive Show KeepAlive configurations.

1.5 Configuring RMON

1.5.1 Introduction
Remote Network Monitoring (RMON) is a standard stipulated by IETF (Internet Engineering
Task Force) for network data monitoring through different network Agent and NMS. RMON
is derived from SNMP. Compared with SNMP, RMON can monitor remote devices more
actively and more effectively, network administrators can track the network, network segment
or device malfunction more quickly. This approach reduces the data flows between NMS and
Agent, makes it possible to manage large networks simply and powerfully, and makes up the
limitations of SNMP in the ever-growing distributed Internet.
RMON implements 4 function groups: statistics group, history group, alarm group, and event
group.
 Statistics group: gather statistics on each interface, including number of received packets
and packet size distribution statistics.
 History group: similar with the statistics group, but it only collects statistics in an
assigned detection period.
 Alarm group: monitor an assigned MIB object, configure the upper and lower thresholds
in an assigned time interval, and trigger an event if the monitored object exceeds the
threshold.
 Event group: cooperating with the alarm group, when alarm triggers an event, it records
the event, such as sending Trap or writing it into the log, and so on.

1.5.2 Preparing for configurations

Scenario
RMON helps monitor and gather statistics about network traffics.
Raisecom Proprietary and Confidential
24
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Compared with SNMP, RMON is a more high-efficient monitoring method. After you specify
an alarm threshold, the iTN8800 actively sends alarms when the threshold is exceeded
without obtaining variable information. This helps reduce traffic of Central Office (CO) and
managed devices and facilitates network management.

Prerequisite
The route between the iTN8800 and the NView NNM system is reachable.

1.5.3 Configuring RMON alarm group

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#rmon alarm alarm- Configure related parameters of
id mibvar [ interval second ] the RMON alarm group.
{ absolute | delta } rising-
threshold rising-num [ rising-
event ] falling-threshold falling-
num [ falling-event ] [ owner
owner-name ]

1.5.4 Configuring RMON event group

Step Command Description
1 Raisecom#config Enter global configuration
mode.
2 Raisecom(config)#rmon event event-id Configure related parameters of
[ log ] [ trap ] [ description the RMON event group.
string ] [ ownerowner-name ]

1.5.5 Configuring RMON statistics

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#rmon Enable RMON statistics on an interface
statistics { interface-type and configure related parameters.
interface-number | ip if-
number }[ owner owner-name ] By default, RMON statistics on all
interfaces is enabled.

Raisecom Proprietary and Confidential

25
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

1.5.6 Configuring RMON history statistics

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#rmon history Enable RMON history statistics on
{ interface-type interface-number an interface and configure related
| ip if-number }[ shortinterval parameters.
period ] [ longinterval period ]
[ buckets buckets-number ] By default, RMON history statistics
[ ownerstring ] on all interfaces is disabled.

1.5.7 Checking configurations

Use the following commands to check configuration results.

No. Command Description

1 Raisecom#show rmon Show RMON configurations.
2 Raisecom#show rmon alarms Show information about the RMON
alarm group.
3 Raisecom#show rmon events Show information about the RMON
event group.
4 Raisecom#show rmon statisttics Show information about the RMON
statistics group.
5 Raisecom#show rmon history Show information about the RMON
interface-type interface- history group.
number

1.6 Configuration examples

1.6.1 Example for upgrading system software (in privileged EXEC
mode)
Step 1 Run the FTP client software installed on the PC and configure the FTP user name, password,
and file path. In this section, the user name is configured to 111111 and the password is
configured to 111111.
Step 2 Configure the IP address of the SNMP interface and ensure that the IP address is in the same
network segment with the IP address of the PC. In this section, the IP address of the SNMP
interface is configured to 192.168.27.98 and the IP address of the PC is configured to
192.168.27.72.

Raisecom#config

Raisecom Proprietary and Confidential

26
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Raisecom(config)#interface fastethernet 1/0/1

Raisecom(config-fastethernet1/0/1)#ip address 192.168.27.98 255.255.255.0
Set successfully

Step 3 Download the system software.

Raisecom(config)#exit
Raisecom#download system ftp 192.168.27.72 111111 111111 iTN8800-NXU.z

Step 4 Wait for downloading the file. The file is downloaded successfully when the prompt "Set
successfully" is displayed.

Waiting...Start
OK
OK
Downloading 12204KK
Set successfully

Step 5 Configure the file to the system file used for rebooting the device at the next time.

Raisecom#boot slot 1 next-startup iTN8800-NXU.z

Slot 1 upgrade success.

Step 6 Reboot the device and enter yes.

Raisecom#reboot
Please input 'yes' to confirm:yes

1.6.2 Example for upgrading system software (in BootROM mode)

When upgrading files in BootROM file, ensure the iTN8800-II-NXU is inserted into
slot 1.
Step 1 Power on or reboot the device.

Raisecom#reboot

Raisecom Proprietary and Confidential

27
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

Step 2 Press Space to enter BootROM configuration mode when "Press space into Bootrom menu..."
appears on the screen.
Step 3 Input "i" to configure the IP address of the device. Ensure that the IP address is in the same
network segment with the IP address of the PC.

[Raisecom]:i

Step 4 Input the IP address and subnet mask of the device.

start look up old ip addr...

old ip address: 192.168.4.28
old ip mask address: 255.255.255.0
new ip address: 192.168.27.98
new ip mask address: 255.255.255.0

Step 5 Input "u" to upgrade the file.

[Raisecom]:u

Step 6 Input "2" to select transmitting the file through FTP, that is, transmitting the file through the
network. Compared with the mode for transmitting the file through the serial interface, this
mode provides a greater speed.

choose mode for updating core file.

-----------------------------------
- 1. | serial -
-----------------------------------
- 2. | network -
-----------------------------------

please input mode choose...

2

Step 7 Input the IP address of the PC.

config network infor ...

host ip address: 192.168.27.72

Step 8 Input the FTP user name, password, and file name.

Raisecom Proprietary and Confidential

28
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 1 Basic configurations

usr:111111
passwd:111111
filename:iTN8800-NXU.z

Step 9 Input "y" to confirm the operation.

starting connect host,please waiting...

Do you want to update image file?<Y/N>y

Step 10 Wait for downloading the file. The file is downloaded successfully when the prompt of
success is displayed.

start update core , please wait some minutes...

success.

Step 11 Input "r" to reboot the device.

[Raisecom]:r

Raisecom Proprietary and Confidential

29
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

2 System management

This chapter describes principles and configuration procedures of system management,

including following sections:
 User management
 Device management
 Time management
 Log management
 File management
 Alarm management
 Configuring device monitoring
 Configuring fault detection
 Configuring Banner
 Configuring RCLink remote management
 Configuring terminal virtualization
 Example for configurations

2.1 User management

When you start the iTN8800 for the first time, connect the PC through Console interface to
the device, input the initial user name and password in Hyper Terminal to log in to and
configure the iTN8800.

By default, both the user name and password are raisecom.

If there is not any privilege restriction, any remote can log in to the iTN8800 through Telnet,
when the Simple Network Management Protocol (SNMP) interface or other service interfaces
of device are configured with IP addresses. This is unsafe to the iTN8800 and network.
Creating user and setting password and privilege help to manage the login users and ensure
network and device security.

Raisecom Proprietary and Confidential

30
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

2.1.1 Configuring user management

Step Command Description
1 Raisecom#user name user-name password Create or modify the user name and password.
password
You can delete a created user through the no
username command.
2 Raisecom#user name user-name privilege Configure the level and privilege of the user.
privilege-level

2.1.2 Checking configurations

No. Command Description
1 Raisecom#show user [ detail ] Show user information.

2.2 Device management

2.2.1 Chassis management
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#device assetid assetid- Configure the asset ID of the device.
string
3 Raisecom(config)#device description Configure descriptions about the device.
description
4 Raisecom(config)#device shelf assetid Configure the asset ID of the chassis.
assetid-string
5 Raisecom(config)#device shelf description Configure descriptions about the chassis.
description

2.2.2 Fan management

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#fan work mode Configure the working mode of the fan.
{ intelligent | non-intelligent }
By default, it is non-intelligent.

Raisecom Proprietary and Confidential

31
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

2.2.3 Rebooting cards

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#reset { all | slot Rebooting all cards (including the NXU card)
slot-id } or the card inserted into a specified slot.

2.2.4 Checking configurations

No. Command Description
1 Raisecom(config)#show fans Show fan information.
2 Raisecom#show heartbeat info [ slot Show heartbeat information about the device.
slot-id ]
3 Raisecom#show manufacture info [ slot Show default information about the device.
slot-id | all ]
4 Raisecom(config)#show power Show information about the power supply.
5 Raisecom#show shelf Show information about the device and chassis.
6 Raisecom#show slot Show operating information about all cards.
7 Raisecom(config)#show temperature Show the device temperature.
8 Raisecom#show version [slot slot-id ] Show the version of the device/cards.

2.3 Time management

2.3.1 Configuring time and time zone
To ensure that the iTN8800 can cooperate with other devices, you need to configure system
time and time zone precisely for the iTN8800.
The iTN8800 supports 3 system time modes: default mode, timestamp mode, and auxiliary
time mode. The number and type of supported modes, as well as the precision and accuracy of
the system time depends on the hardware. You need to manually select the optimum system
time mode based on the actual condition.

Step Command Description

1 Raisecom#clock mode { auxiliary | Configure the system time mode.
default | timestamp }
2 Raisecom#clock display { default Configure the display mode of the system clock.
| utc }
By default, it is default.

Raisecom Proprietary and Confidential

32
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

Step Command Description

3 Raisecom#clock set hour minute Configure the system time.
second year month day
By default, the system time is 8:00:00, Jan 1, 1970.
4 Raisecom#clock timezone { + | - } Configuring system time zone.
hour minute
By default, it is GMT+8:00.

2.3.2 Configuring DST

Daylight Saving Time (DST) is set locally to save energy. About 110 countries around the
world apply DST in summer, but vary in details. Thus, you need to consider detailed DST
rules locally before configuration.

Step Command Description

1 Raisecom#clock summer-time enable Enable DST on the iTN8800.
By default, DST is disabled.
2 Raisecom#clock summer-time recurring { start-week Configure the begin time, end time,
| last } { sun | mon | tue | wed | thu | fri | and offset of DST.
sat } start-month start-hour start-minute { end-
week | last } { sun | mon | tue | wed | thu | fri
| sat } end-month end-hour end-minute offset-mm

 For example, if DST starts from 02:00 a.m. second Monday of April to 02:00 a.m.
second Monday of September, the clock is moved ahead 60 minutes. Thus, the
period between 02:00 and 03:00 second Monday of April does not exist.
Configuring time during this period will fail.
 DST in the Southern Hemisphere is opposite to that in the Northern Hemisphere.
It is from September this year to April next year. If the starting month is later than
the ending month, the system judges that it is located in the Southern Hemisphere.

2.3.3 Configuring SNTP

Network Time Protocol (NTP) is a time synchronization protocol defined by RFC1305. It is
used to perform time synchronization between the distributed time server and clients. Rfc1361
simplifies the NTP and brings Simple Network Time Protocol (SNTP).
Compared with NTP, SNTP supports the server/client mode. In the server/client mode, the
client sends the clock synchronization packet to different servers. After receiving the packet,
servers will work in the server mode automatically and send respond packets. After receiving
respond packets, the client filters and select the clock and is synchronized to the selected
server. In the server/client mode, the client can be synchronized to the server but the server
fails to be synchronized to the client.

Step Command Description

1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

33
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

Step Command Description

2 Raisecom(config)#sntp server ip- Configure the SNTP server address for the device that
address works in the SNTP client mode.

2.3.4 Checking configurations

No. Command Description
1 Raisecom#show clock [ summer-time Show configurations of the system time, time
recurring ] zone, and DST.
2 Raisecom#show sntp Show SNTP configurations.

2.4 Log management

2.4.1 Basic configurations of log management
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#logging on Enable global system log.
By default, global system log is enabled.
3 Raisecom(config)#logging rate- Configure the rate limiting value of logs.
limit number
By default, it is 0. It means that no rate is configured on
logs.
4 Raisecom(config)#logging Configure the log to display the sequence number.
sequence-number
By default, the sequence number is not displayed.
5 Raisecom(config)#logging buginf Configure the level of the Debug information.
[ high | low | none | normal ]
By default, it is none.

2.4.2 Configuring log discriminator

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#logging discriminator number Configure the log discriminator.
{ facility | mnemonics | msg-body } { none |
{ drops | includes } string }

Raisecom Proprietary and Confidential

34
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

Step Command Description

3 Raisecom(config)#logging { buffered | console Associate the log buffer, Console log, log
| file | host ip-address | monitor | trap } file, log host, as well as terminal log and
discriminator number Trap and the log discriminator.

2.4.3 Configuring log storage

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#logging buffered size size Configure the size of the log buffer.
By default, it is 4 kBytes.
3 Raisecom(config)#logging file Save logs to the log file.
4 Raisecom(config)#logging facility { alert | Configure the facility type of logs in the log
audit | auth | clock | cron | daemon | ftp host.
| kern | local0 | local1 | local2 | local3
| local4 | local5 | local6 | local7 | lpr | By default, it is local7.
mail | news | ntp | security | syslog |
user | uucp }
5 Raisecom(config)#logging history Save logs to the historical log table.
6 Raisecom(config)#logging history size size Configure the size of the historical log table.
By default, it is 1.

2.4.4 Checking configurations

No. Command Description
1 Raisecom#show logging Show system log configurations.
2 Raisecom#show logging buffer Show buffer parameters of the system log.
3 Raisecom#show logging discriminator Show configurations of log discriminator.
4 Raisecom#show logging file Show log files.
5 Raisecom#show logging history Show information about the historical log table.

2.4.5 Maintenance
No. Command Description
1 Raisecom(config)#clear logging buffer Clear contents from the log buffer.

Raisecom Proprietary and Confidential

35
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

2.5 File management

2.5.1 Introduction

System files
System files are the software/files required for running, including the system Bootrom file,
system configuration file, system startup file, and FPGA file. In general, these files are saved
to the memory of the device.
File management refers to backing up, upgrading, loading, and deleting system files.

System Bootrom file

The system Bootrom file (BootROM software) is used to initialize the device. After the device
is powered on, the BootROM software is running to initialize the device. You can upgrade the
BootROM software if a new version is available. For details, see section 1.3 Backup and
upgrade.

System startup file

The system startup file (with the .z suffix) is used to start and operate the device, support
normal operating, and realize functions of the device. You can upgrade the system startup file
if a new version is available. In addition, to prevent a system fault, you can back up the
system startup file. For details, see section 1.3 Backup and upgrade.
The iTN8800 supports 2 sets of system startup software simultaneously, providing primary
and secondary switching of dual systems.

System configuration file

The system configuration file (with the .cfg suffix) is configuration items to be loaded when
the device is booted at this time or next time.
After being powered on, the device reads the configuration file from the memory for
initialization. If there is no configuration file in the memory, the device will use the default
configuration file.
Configuration parameters in the configuration file are divided into the following 2 types:
 Configuration parameters used for initialization are startup configurations.
 Configuration parameters used when a device is running properly are running
configurations.
You can modify running configurations through CLI. To make these modified running
configurations as startup configurations when the device is powered on next time, you should
save running configurations to the memory (by using the write command) to form a
configuration file.
Operations on the system configuration file include loading, upgrading, backing up, and
deleting the system configuration file. For details about loading, upgrading, and backing up
the configuration file, see section 1.3 Backup and upgrade.

Raisecom Proprietary and Confidential

36
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

2.5.2 Managing configuration files

No. Command Description
1 Raisecom#config Enable automatically saving configurations.
Raisecom(config)#auto-write enable
2 Raisecom#erase [ file-name ] Delete files from the memory.
3 Raisecom#show startup-config Show configurations to be loaded when the iTN8800
is started.
4 Raisecom#show running-config Show running configurations of the iTN8800.
5 Raisecom#dir Show system files.
6 Raisecom#show startup Show system startup files.

2.6 Alarm management

An alarm refers to information generated by the system based on module failures when a fault
is generated on the iTN8800 or some working condition changes.
The alarm is used to report some urgent and important events and notify them to the network
administrator promptly, which provides strong support for monitoring device operation and
diagnosing faults.
The alarm is stored in the alarm buffer. If the NView NNM system is configured, the alarm
will be sent to it through SNMP. The information sent to the NView NNM system is called
Trap.

Alarm classification
There are 3 kinds of alarms according to properties of an alarm:
 Fault alarm: alarms generated because of hardware failure or anomaly of important
functions, such as port Down alarm
 Recovery alarm: alarms generated when device failure or abnormal function returns to
normal, such as port Up alarm;
 Event alarm: prompted alarms or alarms that are generated because the fault alarm and
recovery alarm cannot be related, such as alarms generated because of failing to Ping.
Alarms are divided into 4 types according to functions:
 Service quality alarm: alarms caused by service quality degradation, including
congestion, performance decline, high resource utilization rate, and the bandwidth
reducing
 Processing error alarm: alarms caused by software or processing errors, including
software errors, memory overflow, version mismatching, and abnormal program aborts
 Environmental alarm: alarms caused by equipment location-related problems, including
the temperature, humidity, ventilation. and other abnormal working conditions
 Device alarm: alarms caused by failure of physical resources, including the power supply,
fan, processor, clock, input/output interface, and other hardware.
Raisecom Proprietary and Confidential
37
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

Alarm output
There are 2 alarm output modes:
 Alarm buffer: alarms are recorded in tabular form, including the current alarm table and
history alarm table.
– Current alarm table: records alarms which are not cleared or restored.
– History alarm table: consists of restored alarms and records the cleared and auto-
restored alarms.
 Trap: alarms sent to the NView NNM system when the NView NNM system is
configured
Alarms will be broadcasted according to various terminals configured on the iTN8800,
including CLI terminal and NView NNM system.

Related concepts
Related concepts about alarm management are displayed as below:
 Alarm inhibition
The iTN8800 only records root-cause alarms but incidental alarms when enabling alarm
inhibition. For example, the generation of alarm A will inevitably produce alarm B, then
alarm B is inhibited and does not appear in the alarm buffer when enabling alarm inhibition.
By enabling alarm inhibition, the iTN8800 can effectively reduce the number of alarms.
The root-cause alarm and all other incidental alarms will be recorded on the iTN8800 when
alarm inhibition is disabled.
 Alarm auto-report
Auto-report refers that an alarm will be reported to the NView NNM system automatically
with its generation and the NView NNM system does not need to query or synchronize alarms
actively.
You can set auto-report to some alarm, some alarm source, or the specified alarm from
specified alarm source.

The alarm source refers to an entity that generates related alarms, such as interfaces,
devices, or cards.
 Alarm monitoring
Alarm monitoring is used to process alarms generated by modules:
– When alarm monitoring is enabled, the alarm module will receive alarms generated
by modules, and process them according to configurations of the alarm module, such
as recording alarm in the alarm buffer, etc.
– When alarm monitoring is disabled, the alarm module will discard alarms generated
by modules without follow-up treatment. In addition, alarms will not be recorded on
the iTN8800.
You can perform alarm monitoring on some alarm, alarm source, or specified alarm from
specified alarm source.
 Alarm inverse

Raisecom Proprietary and Confidential

38
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

Alarm inverse (taking alarms of the interface for examples) refers that the reported alarm
status of the interface is opposite to the actual alarm status. The interface will not report an
alarm if it is unused but it will report alarms if it is used. If the interface returns to the unused
status, the reported alarm will be cleared. There are 3 alarm inverse modes available:
– Non- inverse mode: alarms are reported normally
– Manual inverse mode: in this mode, whatever the current alarm status of the interface
is, the reported alarm status of the interface is changed to the one opposite to the
actual alarm status. It means that the interface reports the related recovery alarm if
there is an alarm and reports an alarm if there is no alarm.
– Auto inverse mode: in this mode, if there is no alarm to be inversed, operations are
configured successfully but not take effect. If there is an alarm to be inversed,
operations are configured successfully. The related recovery alarm is reported and the
interface will enter the inverse mode, which means status of all reported alarms is
opposite to the real one. After the alarm is completed, the interface enters the non-
inverse mode automatically and reports alarms properly.
 Alarm delay
Alarm delay refers that the device will record alarms and report them to the NView NNM
system after a delay but not immediately when alarms generate. Delay for recording and
reporting alarms are identical.
By default, an alarm is reported 5s later after it is generated and an alarm is cleared 5s later
after it is finished.
 Alarm storage mode
Alarm storage mode refers to how to record new generated alarms when the alarm buffer is
full. There are two ways:
− stop: stop mode, when the alarm buffer is full, new generated alarms will be
discarded without recording.
− loop: loop mode, when the alarm buffer is full, the new generated alarms will replace
old alarm information and take rolling records.
For the iTN8800, the current alarm table can record up to 1000 alarms and the historical alarm
table can record up to 500 alarms. Use the configured alarm storage mode to deal with newly-
generated alarms when the alarm table is full.
 Alarm clearance
Clear the current alarm, which means deleting current alarms from the current alarm table.
The cleared alarms will be saved to the historical alarm table.
 Viewing alarms
The administrator can view alarms and monitor alarms directly on the iTN8800. If the
iTN8800 is configured with the NView NNM system, the administrator can monitor alarms
on the NView NNM system.

2.6.1 Configuring alarm inhibition

The iTN8800 only records root-cause alarms but incidental alarms when enabling alarm
inhibition. For example, the generation of alarm A will inevitably produce alarm B, then
alarm B is inhibited and does not appear in the alarm buffer or record the log information
when enabling alarm inhibition. By enabling alarm inhibition, the iTN8800 can effectively

Raisecom Proprietary and Confidential

39
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

reduce the number of alarms. The root-cause alarm and all other incidental alarms will be
recorded on the iTN8800 when alarm inhibition is disabled.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#alarm inhibit enable Enable alarm inhibition.
By default, it is enabled.

2.6.2 Configuring alarm delay

The alarm delay can be divided into alarm generation delay and alarm clearance delay.
 Alarm generation delay refers to the delay after an alarm is generated.
 Alarm clearance delay refers to the delay after an alarm is finished.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#alarm active delay second Configure the alarm generation delay.
By default, it is 0s.
3 Raisecom(config)#alarm clear delay second Configure the alarm clearance delay.
By default, it is 0s.

2.6.3 Configuring alarm storage modes

Alarm storage modes are modes for Network Elements (NEs) storing alarms, which can be
divided into loop and stop modes.
 In stop alarm storage mode, if there is no more capacity for alarms stored by NEs,
newly-reported alarms will be discarded.
 In loop alarm storage mode, if there is no more capacity for alarms stored by NEs,
newly-reported alarms will overwrite the old ones and will be stored at the initial
position of the memory.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#alarm active storage- Configure the alarm storage mode.
mode { loop | stop }
By default, it is stop.

2.6.4 Configuring alarm auto-report

Auto-report refers that the device will automatically report an alarm to the NView NNM
system when the alarm is generated, without querying or synchronizing the alarm. Trap is the

Raisecom Proprietary and Confidential

40
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

information sent by the device to the NView NNM system. Trap is used to report some
emergent and critical events (for example, the managed device is restarted).

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#alarm auto-report Enable alarm auto-report based on interface and
interface-type interface-number its function modules.
[ module_name [ group-name ] ] enable
By default, it is enabled.
3 Raisecom(config)#alarm auto-report Enable alarm auto-report for a function module.
[ module_name [ group-name ] ] enable
By default, it is enabled.
4 Raisecom(config)#alarm auto-report all Enable alarm auto-report for all alarm.
enable
By default, it is enabled.

2.6.5 Configuring alarm inverse

Alarm inverse (taking alarms of the interface for examples) refers that the reported alarm
status of the interface is opposite to the actual alarm status. The interface will not report an
alarm if it is unused but it will report alarms if it is used. If the interface returns to the unused
status, the reported alarm will be cleared.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#alarm inverse interface-type Configure the alarm inverse mode.
interface-number { auto | manual | none }

2.6.6 Configuring alarm monitoring

Alarm monitoring is used to process alarms generated by all modules.
 After alarm monitoring is enabled, the alarm module will receive alarms generated by all
modules and process them based on configurations of the alarm module, such as, saving
alarms to the alarm buffer.
 After alarm monitoring is disabled, the alarm module will discard alarms generated by
all modules without processing them. These alarms will not be record to the device.
You can perform alarm monitoring on some module, interface, or a module on an interface.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#alarm monitor Enable alarm monitoring based on interface and its
interface-type interface-number function modules.
[ module_name [ group-name ] ]
enable By default, it is enabled.

Raisecom Proprietary and Confidential

41
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

Step Command Description

3 Raisecom(config)#alarm monitor Enable alarm monitoring based on a function module.
[ module_name [ group-name ] ]
enable By default, it is enabled.
4 Raisecom(config)#alarm monitor Enable alarm monitoring for all alarms.
all enable
By default, it is enabled.

2.6.7 Configuring alarm output

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#alarm syslog enable Enable alarm syslog.
By default, it is enabled.

2.6.8 Checking configurations

No. Command Description
1 Raisecom#show alarm active [ module_name | Show currently active alarms.
severity severity ]
2 Raisecom#show alarm cleared [ module_name | Show historical alarms.
severity severity ]
3 Raisecom#show alarm management Show alarm management configurations.
[ module_name ]
4 Raisecom#show alarm management statistics Show alarm statistics.
5 Raisecom#show alarm log Show alarm logs.

2.6.9 Maintenance
No. Command Description
1 Raisecom(config)#alarm clear interface-type interface- Clear specified alarms.
number [ module_name [ group-name ] ]
Raisecom(config)#alarm clear index index

Raisecom(config)#alarm clear module_name [ group-name ]

Raisecom Proprietary and Confidential

42
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

2.7 Configuring device monitoring

2.7.1 Configuring temperature monitoring
No. Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#temperature Configure the high temperature alarm threshold.
alarm threshold high value
By default, it is 65°C.
3 Raisecom(config)#temperature Configure the lower temperature alarm threshold.
alarm threshold low value
By default, it is -10°C.

2.7.2 Fan monitoring

When placed in a hot environment, the iTN8800 has its heat dissipation to be effected. As a
result, fan monitoring should be configured to enable the iTN8800 to automatically adjust the
rotational speed of the fan according to the environment temperature and thus ensure its
normal operation.

No. Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#fan work mode (Optional) configure the working mode of the fan.
{ intelligent | non-intelligent }
By default, it is intelligent.

2.7.3 Checking configurations

No. Command Description
1 Raisecom#show fan Show fan monitoring configurations.
2 Raisecom#show temperature Show device temperature.
3 Raisecom#show power Show power status.

2.8 Configuring fault detection

2.8.1 Configuring task scheduling
To use some commands periodically, configure task scheduling.

Raisecom Proprietary and Confidential

43
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

The iTN8800 supports realizing task scheduling by combining the program list to commands.
You just need to specify the start time of the task, period, and end time in the program list, and
then bind the program list with commands to implement periodical execution of commands.

No. Command Description

1 Raisecom#config Enter global
configuration mode.
2 Raisecom(config)#schedule-list list-number start date-time Create and configure
mm-dd-yyyy hh:mm:ss the schedule list.
Raisecom(config)#schedule-list list-number start date-time
mm-dd-yyyy hh:mm:ss every { day | week } stop mm-dd-yyyy
hh:mm:ss

Raisecom(config)#schedule-list list-number start date-time

mm-dd-yyyy hh:mm:ss every days-interval time-interval [ stop
mm-dd-yyyy hh:mm:ss ]

Raisecom(config)#schedule-list list-number start up–time

days-after-startup hh:mm:ss

Raisecom(config)#schedule-list list-number start up–time

days-after-startup hh:mm:ss every days-interval time-
interval [ stop days-after-startup hh:mm:ss ]

3 Raisecom#show schedule-list Show configurations

of the schedule list.

2.8.2 Ping
No. Command Description
1 Raisecom#ping ip-address [ count Check connectivity of the IPv4 network through the
count ] [ size size ] [ waittime ping command.
period ] [ source ip-address ]
Raisecom#ping ipv6 ipv6-address
[ count count ] [ size size ]
Check the connectivity of the IPv6 network through
[ waittime time ] [ interface
the ping command.
interface-type interface-number ]
[ source ipv6-address ]

No other operations can be done during executing the ping command. You have to
wait till the end of the process or forcedly interrupt it by pressing Ctrl+B.

2.8.3 Traceroute
Before using this function, you should configure the IP address and default gateway.

Raisecom Proprietary and Confidential

44
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

No. Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter Layer 3 physical interface configuration mode.
interface-type if interface-number
3 Raisecom(config-port)#ip address Configure the IP address of the interface.
ip-address [ ip-mask ] vlan-id
4 Raisecom(config-port)#exit Exit interface configuration mode. Enter global
configuration mode.
5 Raisecom#traceroute { ip-address | Check connectivity of the IPv4 network and view
ipv6 ipv6-address } [ firstttl network nodes which packets pass by.
fitst-ttl ] [ maxttl max-ttl ]
[ port port-number ] [ waittime By default,
period ] [ count times ] [ size  The initial TTL is 1.
size ]  The maximum TTL is 30.
 The interface ID is 33433.
 The timeout is 3s.
 The number of probe packets is 3.

2.9 Configuring Banner

2.9.1 Preparing for configurations

Scenario
Banner is a prompt displayed when you log in to or exit the iTN8800, such as the precautions
or disclaimer.
You can configure the Banner of the iTN8800 as required. In addition, the iTN8800 provides
the Banner switch. After Banner display is enabled, the configured Banner information
appears when you log in to or exit the iTN8800.
After configuring Banner, you should use the write command to save configurations.
Otherwise, Banner information will be lost when the iTN8800 is restarted.

Prerequisite
N/A

2.9.2 Configuring Banner

Step Command Description
1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

45
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

Step Command Description

2 Raisecom(config)#ba Configure the Banner contents. Enter the banner
nner login word login and word, press Enter, enter the Banner
Press Enter. contents, and then end with the word character.
Enter text message
followed by the
character ’word’ to
 The word parameter is a 1-byte character. It is the
finish.User can
stop configuration
beginning and end mark of the Banner contents.
by inputing’
These 2 marks must be the identical characters. We
Ctrl+c’
recommend selecting the specified character that
message word will not occur at the message.
 The message parameter is the Banner contents. Up

to 2560 characters are supported.

3 Raisecom(config)#cl (Optional) clear contents of the Banner.
ear banner login

2.9.3 Enabling Banner display

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ba Enable Banner display.
nner enable
By default, Banner display is disabled.

2.9.4 Checking configurations

No. Command Description
1 Raisecom#show Show Banner status and contents of the configured Banner.
banner login

2.10 Configuring RCLink remote management

2.10.1 Preparing for configurations

Scenario
RCLink, a protocol developed by Raisecom, is used to manage remote transceivers. As shown
in Figure 2-1, the iTN8800 is connected to the remote transceiver RC512-FE (B) through the
iTN8800-RF8. RCLink works between the CO device and remote device to implement remote
configuration and management, including configuring parameters of the optical/electrical
interface, Maximum Transmission Unit (MTU), flow control, device restarting, link-state
tracking, and showing device information. RCLink supports the following transceivers:
Raisecom Proprietary and Confidential
46
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

 RC512-FE (B), RC512-FE (H)

 RC512-FE-S (B), RC512-FE-S (H)
 RC532-FE (A), RC532-FE (H)
 RC531-FE (A), RC531-FE (H)
 RC513-FE (B), RC513-FE (H)
 RC522E-FE (A), RC522E-FE (H)
 RC521E-FE (A), RC521E-FE (H)
 RC521H-FE (A), RC521H-FE (H)
 RC511-4FE (B), RC511-4FE (H)
 RM531-FE (A), RM531-FE (B)
 RM531i-FE (B), RM531i-FE (H)

Figure 2-1 Networking with RClink remote management

Prerequisite
The iTN8800-RF8 is in position.

2.10.2 Configuring basic information about remote device

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter iTN8800-RF8 physical interface configuration
fastethernet interface-number mode.
3 Raisecom(config-port)#rclink enable Enable RCLink.
By default, RCLink is disabled.
4 Raisecom(config-port)#remote-device Enter RCLink remote configuration mode.
rclink

Raisecom Proprietary and Confidential

47
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

Step Command Description

5 Raisecom(config-remote)#max-frame- Configure the maximum forwarding framelength of
length { 1916 | 1536 } the remote device. Only the RC512-FE (B), RC512-
FE-S (B), and RC513-FE (B) support this
configuration.
By default, it is 1916 bytes.
6 Raisecom(config-remote)#{ req-info- Enable the remote device to start or stop gathering
start | req-info-over } statistics.
7 Raisecom(config-remote)#flow- Enable flow control on the remote device. Only the
control on remote device with the hardware version H supports
this configuration.
By default, flow control is enabled.
8 Raisecom(config-remote)#fault-pass Enable link-state tracking on the remote device.
eth enable
By default, link-state tracking is disabled.
9 Raisecom(config-remote)#reset (Optional) reset the remote device without clearing
configurations. This configuration resets the chip only.

2.10.3 Configuring interface parameters of remote device

Parameters of electrical interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface fastethernet Enter iTN8800-RF8 physical layer interface
interface-number configuration mode.
3 Raisecom(config-port)#rclink enable Enable RCLink.
4 Raisecom(config-port)#remote-device Enter RCLink remote configuration mode.
rclink
5 Raisecom(config-remote)#interface eth 1 Enter remote electrical interface configuration
mode.
6 Raisecom(config-remote/eth)#speed { 10 (Optional) configure the rate and duplex mode of
| 100 } duplex { full-duplex | half- the electrical interface on the remote device.
duplex }
By default, the rate of the remote electrical
interface is 100 Mbit/s with full duplex mode.

Use the no autonegotiate command to

disabled auto-negotiation and then you can
use this command.

Raisecom Proprietary and Confidential

48
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

Step Command Description

Raisecom(config- (Optional) enable auto-negotiation on the remote
remote/eth)#autonegotiate electrical interface.
By default, auto-negotiation on the remote
electrical interface is enabled.

When executing both the transceiver DIP

configuration and CLI together, prioritize
DIP configurations.
7 Raisecom(config-remote/eth)#{ rx-rate- Configure rate limiting on the electrical interface
limit | tx-rate-limit } rate on the remote device.
8 Raisecom(config-remote/eth)#shutdown (Optional) shut down the electrical interface on
the remote device.

Parameters of optical interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface fastethernet Enter iTN8800-RF8 physical layer interface
interface-number configuration mode.
3 Raisecom(config-port)#rclink enable Enable RCLink.
4 Raisecom(config-port)#remote-device Enter RCLink remote configuration mode.
rclink
5 Raisecom(config-remote)#interface fx- Enter remote optical interface configuration
eth 1 mode.
6 Raisecom(config-remote/fx-eth)#als Enable ALS on the optical interface on the
enable remote device.
By default, ALS is disabled.

2.10.4 Checking configurations

No. Command Description
1 Raisecom(config-remote)#show info Show information about the remote device.
2 Raisecom(config-remote)#show manufacture Show the SN of the remote device.
3 Raisecom(config-port)#show rclink status Show RCLink status of the interface.
4 Raisecom(config-remote)#show version Show the version of the remote device.

Raisecom Proprietary and Confidential

49
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

No. Command Description

5 Raisecom(config-remote/port)#show Show information about the optical interface
interface and electrical interface on the remote device,
such as status and packet statistics.

2.11 Configuring terminal virtualization

2.11.1 Preparing for configurations

Scenario
The carrier adopts a third-party integrated NMS. Therefore, the network elements in IP RAN
must comply with the related requirements of the carrier's NMS auto-connection protocol to
implement the plug-and-play and related service management through the third-party NMS.
As a U device, the iTN8800 meets the requirements of the carrier's NMS auto-connection
protocol and can be managed by a third-party NMS upon being connected.
The iTN152 connected upstream to the iTN8800 is a newly developed U0 device by
Raisecom. It can be used for accessing user services on the carrier's network. However, the
U0 devices are IP-free, OSPF-free, and LLDP-free. They are simple devices that do not
support the vast majority of MIB nodes and cannot be managed by a third-party NMS. You
can configure terminal virtualization on the U device so that the U0 device can be managed
by the third-party NMS upon being connected.
Raisecom U0 devices support separate service configuration and device installation. If you
want to unbind the U0 device, you need to log in to the third-party NMS to configure service
limits.

Prerequisite
Establish an extended OAM channel between the U device and U0 device.

2.11.2 Working principle

The U device (iTN8800) is added with a virtualization module which can virtualize the U0
device into a U device, thus making the U0 device able to be managed by the third-party
NMS. The working process is as below:
 Associated performance of U0 installation and service configuration
Step 1 The U device (iTN8800) detects that the extended OAM connection with the remote U0
device is established.
Step 2 The U device can virtualize the information needed by the third-party NMS for the automatic
connection of U0 device, making the U0 device log in to the third-party NMS automatically.
Step 3 After discovering the U0 device, you can manage and configure the U0 device through the
third-party NMS.
 Separate performance of U0 installation and service configuration

Raisecom Proprietary and Confidential

50
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

Step 1 When U0 device is not connected to the U device, you need to configure the U0 device to
make it online on the third-party integrated NMS and save the configurations sent by the
third-party NMS.
Step 2 After the U0 device established extended OAM connections with the U device, the U device
will automatically send the saved configurations to the U0 device.

After extended OAM is enabled on the U device and loopback is enabled among
DCN sub-interfaces on the U device, the system will automatically performs terminal
virtualization of the U0 device. When the default condition is changed or the user has
special requirements, it supports configuring features during the terminal
virtualization process.

2.11.3 Configuring management IP address of U0 device

The terminal virtualization module of the U device can automatically configure a default
management IP address for the U0 device. If your IP address is planned, you can modify the
management IP address.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#remote-device modify ip- Enter the U0 management IP modification
address mode. The ip-address is the original
management IP address of the U0 device. Use
the show running-config command to show
the IP address of the current U0 device.
3 Raisecom(config-port)#ip address ip- Configure the management IP address of the
address [ ip-mask ] [ sub ] U0 device to a new IP address.

2.11.4 Configuring SPF of OSPF process

The Shortest Path First (SPF) is an algorithm for finding the shortest path in the OSPF process
that mainly computes and establishes paths.
 After SPF is enabled, the OSPF process will start SPF calculation. The calculated routes
will be delivered to the global routing table.
 When SPF is disabled, the OSPF route calculated through SPF will be deleted from the
OSPF routing table and so will be the OSPF route in the global routing table.
The terminal virtualization module prohibits SPF route calculation for the OSPF process
virtualized on the U0 device.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Enter OSPF configuration mode.
[ router-id router-id ]

Raisecom Proprietary and Confidential

51
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

Step Command Description

3 Raisecom(config-router-ospf)#spf { enable Configure OSPF SPF calculation.
| disable }
By default, SPF calculation for the OSPF
process virtualized on the U0 device is
disabled. For other OSPF processes, SPF
calculation is enabled.

2.11.5 Configuring loopback among DCN sub-interfaces

The sub-interface 4093 of the U device physical interface connected to the U0 device is
enabled with the virtual OSPF process of the remote U0 device and the 4094 sub-interface is
enabled with the carrier DCN OSPF process. Enable loopback among 4093 sub-interface and
4094 DCN sub-interface to implement OSPF packet interaction between the two OSPF
processes.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
By default, the interface is in L3 physical
interface configuration mode.

This command is suitable for physical

interfaces in L3 interface mode. If the
current physical interface is in L2
interface mode, you can use the no
portswitch command to covert L2
interfaces into L3 interfaces.
3 Raisecom(config-port)#dcn subif loop Configure loopback between sub-interface
{ enable | disable } 4094 and sub-interface 4093 of the physical
interfaces.
By default, it is disabled.

2.11.6 Remote management of U0 devices

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#remote-device ip- Enter U0 interface configuration mode.
address
The ip-address is the IP address of the U0 virtualized
terminal.
3 Raisecom(config-port)#remote-device Enter U0 remote configuration mode.

Raisecom Proprietary and Confidential

52
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

Step Command Description

4 Raisecom(config-remote)#rate-limit Configure bandwidth rate limiting on the line
line interface-num { egress | interface of the U0 device.
ingress } value
Raisecom(config-remote)#line-speed Configure the uplink line interface of the U0 device
auto to auto mode.
Raisecom(config-remote)#rate-limit Configure bandwidth rate limiting on the downlink
client interface-num { egress | client interface of the U0 device.
ingress } value
Raisecom(config-remote)#switch-mode Specify the VLAN ID encapsulated into services
double-tagged-vlan native-vlan vlan- which are accessed to the U0 device through the
id client port-id client interface.
Raisecom(config-remote)#switch-mode Configure transparent transmission of services that
transparent are accessed to the U0 device through the client
interface.
Raisecom(config-remote)#fault-pass Enable link-state tracking from uplink line interface
enable to downlink client interface of the U0 device.
5 Raisecom(config-remote)#interface Enter downlink client interface configuration mode
client port-id of the U0 device.
6 Raisecom(config-remoteport)#speed Configure the rate of the downlink client interface of
{ auto | 10 | 100 } the U0 device.
Raisecom(config-remoteport)#duplex Configure the duplex mode of the downlink client
{ full | half } interface of the U0 device.
Raisecom(config-remoteport)#shutdown Configure the downlink client interface of the U0
device to admin down.
7 Raisecom(config-remoteport)#exit Exit the U0 downlink client interface configuration
mode and enter U0 remote configuration mode.
8 Raisecom(config-remote)#reboot Restart the U0 device after configurations are
finished.

2.11.7 Saving preconfigurations of U0 device

When U0 device installation and service configuration are performed separately, that is, when
U0 device is not connected to the U device, it is allowed that the third-party NMS sends
configurations of the U0 device, which will be saved to the U device.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#remote-device ip- Enter U0 interface configuration mode.
address
The ip-address refers to the management IP address
of the U0 virtualized terminal.
3 Raisecom(config-port)#remote-device Enter U0 remote configuration mode.

Raisecom Proprietary and Confidential

53
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

Step Command Description

4 Raisecom(config-remote)#write local Save the preconfigurations of the U0 device.

2.12 Example for configurations

2.12.1 Example for configuring hardware monitoring alarms output

Networking requirements
As shown in Figure 2-2, you can configure hardware monitoring to monitor the temperature
of the iTN device. When the temperature exceeds the threshold, the alarm Trap will be sent to
the NView NNM system to inform the network administrator to take actions in case of failure.

Figure 2-2 Networking with hardware monitoring alarms output

Configuration steps
Step 1 Configure the IP address of the iTN device.

Raisecom#config
Raisecom(config)#interface gigaethernet 1/1/1
Raisecom(config-gigaethernet 1/1/1)#ip address 20.0.0.6 255.255.255.0
Raisecom(config-gigaethernet 1/1/1)#exit

Step 2 Enable Trap sending on the iTN device.

Raisecom(config)#snmp-server enable traps

Raisecom(config)#snmp-server host 20.0.0.1 version 2c public

Step 3 Configure temperature monitoring on the iTN device.

Raisecom(config)#temperature alarm threshold high 55

Raisecom(config)#temperature alarm threshold low 10

Raisecom Proprietary and Confidential

54
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 2 System management

Checking results
Use the show snmp config command on the iTN device to show configurations of Trap
sending.

Raisecom#show snmp config

Contact information: support@Raisecom.com
Device location : World China Raisecom
SNMP trap status: enable
SNMP engine ID: 800022B603000001020304

Use the show snmp host command to show configurations of the Trap target host.

Raisecom(config)#show snmp host

Index: 0
IP family: IPv4
IP address: 20.0.0.1
Port: 162
User Name: public
SNMP Version: v2c
Security Level: noauthnopriv
TagList: bridge config interface rmon snmp ospf

Raisecom Proprietary and Confidential

55
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 3 Interface management

3 Interface management

This chapter describes principles and configuration procedures of interface management,

including following sections:
 Basic configurations of interface
 Configuring Ethernet interface
 Configuring Ethernet sub-interface
 Configuring VLAN interface
 Configuring optical module DDM
 Configuring loopback
 Configuring interface statistics
 Configuring loopback
 hecking configurations

3.1 Basic configurations of interface

3.1.1 Configuring basic information of interface
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter Layer 3 physical interface
interface-number configuration mode.
3 Raisecom(config-port)#mac mac-address Configure the MAC address of the
interface.
4 Raisecom(config-port)#ip address ip-address Configure the primary and secondary IP
[ ip-mask ] [ sub ] addresses, as well as subnet mask of the
Layer 3 physical interface.
5 Raisecom(config-port)#description string Configure descriptions of the interface.

Raisecom Proprietary and Confidential

56
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 3 Interface management

Step Command Description

6 Raisecom(config-port)#portswitch Switch interface configuration mode.
Switch the interface to Layer 2 physical
interface configuration mode, namely,
the switching mode.
By default, the interface is in Layer 3
physical interface configuration mode,
namely, routing mode.
7 Raisecom(config-port)#sfp fiber-tx track (Optional) configure the tracking status
fiber-rx enable of fiber sending and receiving on the
interface.
8 Raisecom(config-port)#medium-type { auto | (Optional) configure types of Combo
fiber | copper } interface.
9 Raisecom(config-port)#shutdown (Optional) shut down the interface.

3.1.2 Configuring interface working mode

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter Layer 3 physical interface
interface-number configuration mode.
3 Raisecom(config-port)#mode { l2 | l3 } Configure Layer 3 physical interface
working mode.
 L2: access L2VPN.
 L3: access L3VPN.

3.1.3 Configuring Jumboframe of interface

When exchanging high-throughput data, such as transmitting files, the Ethernet interface may
receive the Jumbo frame, whose size is greater than the standard Ethernet frame size. The
system will directly discard Jumbo frames. If you configure to allow Jumbo frames to pass,
the system will continue to process them, when the size of these Jumbo frames is greater than
the standard size but in specified value range.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)#jumboframe Configure the interface to allow Jumbo frames to pass.
frame-size
By default, it is 9600 Bytes.

Raisecom Proprietary and Confidential

57
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 3 Interface management

3.1.4 Configuring MTU of interface

The Maximum Transmission Unit (MTU) is the largest bytes of packets that can be
transmitted in a physical network. After you configure the iTN8800 to allow Jumbo frames to
pass, the IP layer will compare the MTU with the size of the packet to be sent. If the size of
the packet is greater than the MTU, the IP layer will fragment the packet. The fragmented
packet can be smaller than or equal to the MTU. When MTUs of two connected devices are
configured inconsistently, these 2 devices fail to communicate with each other. In this case,
you should adjust MTU configurations.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter Layer 3 physical interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)#mtu size Configure the MTU of the interface.
By default, it is 1500 Bytes.

3.1.5 Configuring vibration suppression of interface

When working on the network, the interface of the device may alternately appear up and
down status due to various reasons, such as, physical signal interference, configuration error
in link layer. Frequency alternation leads routing protocol repetitive vibration and has bad
effects on the device and the network, what's worse, the network and some devices may be
disabled.
You should configure vibration suppression period so as to reduce the switching frequency
between up and down status.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#vibration- Configure suppression period of the interface.
suppress period second
By default, the suppression period is 3s.

3.1.6 Configuring MAC address of interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#mac mac-address Configure the MAC address of the interface.
4 Raisecom(config-port)#shutdown Restart the interface to make the MAC address
Raisecom(config-port)#no shutdown take effect.

Raisecom Proprietary and Confidential

58
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 3 Interface management

3.2 Configuring Ethernet interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
By default, the interface is in Layer 3 physical
interface configuration mode.
3 Raisecom(config-port)#tpid { 8100 | 9100 Configure the TPID of the interface.
| 88a8 }
By default, it is 0x8100.
4 Raisecom(config-port)#speed { auto | 10 | Configure interface rate.
100 | 1000 | 10000 }
5 Raisecom(config-port)#duplex { auto | Configure interface duplex mode.
full | half }

3.3 Configuring Ethernet sub-interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
By default, the interface is in Layer 3 physical
interface configuration mode.
3 Raisecom(config-port)#interface In Layer 3 physical interface configuration mode,
gigaethernet unit/slot/port.sub- enter Gigabit Ethernet sub-interface configuration
interface mode.
4 Raisecom(config-subif)#encapsulation Configure the VLAN ID in the VLAN Tag of the
dot1q vlan-id Gigabit Ethernet sub-interface.
By default, the sub-interface mode is L2.
5 Raisecom(config-subif)#encapsulation Configure encapsulating single-VLAN for the
dot1Q vlan-id-1 [ to vlan-id-n ] Gigabit Ethernet sub-interface. Support
encapsulating single VLAN and VLAN section.
6 Raisecom(config-subif)#encapsulation Configure encapsulating double VLANs for the
qinq svlan svlan-id cvlan cvlan-id-1 Gigabit Ethernet sub-interface. For user-side VLAN,
[ to cvlan-id-n ] it supports encapsulating single VLAN and VLAN
section.
7 Raisecom(config-subif)#vlan In L2VPN mode, configure VLAN mapping of the
translate [ svlan { untag | vlan- Gigabit Ethernet sub-interface.
id } ] [ cvlan { untag | vlan-id } ]

Raisecom Proprietary and Confidential

59
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 3 Interface management

3.4 Configuring VLAN interface

The prerequisite is that the related VLAN ID is created.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface vlan vlan-id Enter VLAN interface configuration mode.
3 Raisecom(config-vlanif)#ip address ip- Configure the primary and secondary IP
address [ ip-mask ] [ sub ] addresses, and the subnet mask of the VLAN
interface.

3.5 Configuring optical module DDM

3.5.1 Preparing for configurations

Scenario
Optical module DDM provides a method to detect SFP performance parameters. You can
predict the service life of optical module, isolate system fault, and check its compatibility
during installation through analyzing monitoring data.

Prerequisite
N/A

3.5.2 Enabling optical module DDM

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
3 Raisecom(config-port)#transceiver ddm enable Enable optical module DDM.
By default, it is disabled.

3.5.3 Checking configurations

No. Command Description
1 Raisecom#show transceiver [interface-type Show history information about optical
interface-number history { 15m | 24h } ] module DDM.

Raisecom Proprietary and Confidential

60
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 3 Interface management

No. Command Description

2 Raisecom#show transceiver ddm interface-type Show information about optical
interface-list [ detail ] module DDM.

3.6 Configuring loopback interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter loopback interface configuration mode.
loopback interface-number
3 Raisecom(config-port)#ip address Configure the primary and secondary IP addresses, and
ip-address [ ip-mask ] [ sub ] the subnet mask of the loopback interface.

3.7 Configuring interface statistics

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
3 Raisecom(config-port)#statistics enable Enable interface statistics.
4 Raisecom(config-port)#clear interface (Optional) clear interface statistics.
statistics

3.8 Configuring loopback

3.8.1 Preparing for configurations

Scenario
Through interface loopback, the network maintenance personnel can detect and analyze faults
of the device and network.

Prerequisite
The interface should be Up.

Raisecom Proprietary and Confidential

61
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 3 Interface management

3.8.2 Configuring interface loopback

Step 2 and Step 3 are optional. You should execute Step 2 when interface loopback is enabled
and execute Step 3 when Link Aggregation Group (LAG) interface loopback is enabled.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode. Enable
type interface-number interface loopback.
Raisecom(config-port)#loopback
 internal: internal loopback
{ internal | external } [ access-list
 external: external loopback
acl-number ] [ swap sip ip-address ]
 access-list: ACL ID
[ swap smac mac-address ] [ swap vcid
 swap sip: specify the source IP address for the
vc-id peerid peer-ip ] [ swap dip-
disable ] [ swap dmac-disable ] [ swap returned loopback packets. The source and
dport-disable ] destination IP addresses of the loopback
packets are translated by default.
 swap smac: specify the source MAC address

for the returned loopback packets. The source

and destination MAC addresses of the
loopback packets are translated by default.
 swap vcid peerid: loop back packets which are

from the specified Peer-IP and match the VC-

ID, which is applicable to the GRE scenario
only.
 swap dip-disable: disable destination IP

translation of multicast/broadcast packets. The

destination IP addresses of the returned
loopback packets keep unchanged. Source and
destination IP addresses are translated by
default.
 swap dmac-disable: disable destination MAC

translation of multicast/broadcast packets. The

destination MAC addresses of the returned
loopback packets keep unchanged. Source and
destination MAC addresses are translated by
default.
 swap dport-disable: disable the translation of

TCP/UDP source and destination interface

IDs of loopback packets. The destination
interface ID of returned loopback packets
keeps unchanged.

Raisecom Proprietary and Confidential

62
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 3 Interface management

Step Command Description

3 Raisecom(config)#interface port-channel Enter link aggregation configuration mode.
channel-number Enable link aggregation group interface
Raisecom(config-port-channel*)#loopback loopback.
{ internal | external } [ access-list
 internal: internal loopback
acl-number ] [ swap sip ip-address ]
 external: external loopback
[ swap smac mac-address ] [ swap vcid
 access-list: ACL ID
vc-id peerid peer-ip ] [ swap dip-
 swap sip: specify the source IP address for the
disable ] [ swap dmac-disable ] [ swap
dport-disable ] returned loopback packets. The source and
destination IP addresses of the loopback
packets are translated by default.
 swap smac: specify the source MAC address

for the returned loopback packets. The source

and destination MAC addresses of the
loopback packets are translated by default.
 swap vcid peerid: loop back packets which are

from the specified Peer-IP and match the VC-

ID, which is applicable to the GRE scenario
only.
 swap dip-disable: disable destination IP

translation of multicast/broadcast packets. The

destination IP addresses of the returned
loopback packets keep unchanged. Source and
destination IP addresses are translated by
default.
 swap dmac-disable: disable destination MAC

translation of multicast/broadcast packets. The

destination MAC addresses of the returned
loopback packets keep unchanged. Source and
destination MAC addresses are translated by
default.
 swap dport-disable: disable the translation of

TCP/UDP source and destination interface

IDs of loopback packets. The destination
interface ID of returned loopback packets
keeps unchanged.

 The first 3 bytes of the destination MAC address cannot be set to 0x0180C2.
 The source MAC address cannot be a multicast/broadcast MAC address.

3.9 Checking configurations

No. Command Description
1 Raisecom#show interface interface-type Show interface status.
interface-number

Raisecom Proprietary and Confidential

63
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 4 Zero-configuration

4 Zero-configuration

This chapter describes principles and configuration procedures of interface management,

including following sections:
 Configuring CO zero-configuration
 Configuration examples

4.1 Configuring CO zero-configuration

4.1.1 Preparing for configurations

Scenario
 When the CO iTN8800 connects with remote devices, the iTN8800 can discover these
remote devices by using the extended OAM protocol and configure the management IP
address, management VLAN, and default route for them. Therefore, the NView NNM
system can quickly manage remote devices through the public IP address and global
interface ID of the iTN8800 without being configured manually.
 When the CO iTN8800 and remote devices are connected directly/indirectly, both the
CO and remote devices can provide zero-configuration through Dynamic Host
Configuration Protocol (DHCP).

Prerequisite
 The iTN8800 is a CO device.
 The CO zero-configuration server is connected to the NView NNM system and remote
devices properly.
 Perform the following operations on the CO device based on extended OAM protocol:
– Create and activate the management VLAN.
– The interface of the remote device used for direct connection is configured to work in
Trunk mode and allows the management VLAN to pass.
– Manually enable the OAM active mode on the interface.
 Based on the DHCP, the remote device is connected to the network and is configured to
the zero-configuration client.
– Create and activate the management VLAN.

Raisecom Proprietary and Confidential

64
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 4 Zero-configuration

4.1.2 Configuring zero-configuration Server based on extended

OAM
The IP RAN local device assigns private IP addresses for remote devices through extended
OAM zero-configuration, ensuring that routes are available between the local and remote
devices. To implement NMS path protection, the remote device is connected to the local
device through dual uplinks.

Configuring management VLAN

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#create vlan Create and activate a VLAN.
vlan-id active
3 Raisecom(config)#oam mng-vlan Configure the remote management VLAN of zero-
vlan-id configuration and configure all downlink interfaces of the
CO device to allow this VLAN to pass.
By default, it is VLAN 0.

After configuring the management VLAN through

this command, do not modify the switching
property of downlink interfaces of the CO device.
Otherwise, it may cause the remote device to be
out of management.
4 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-number
5 Raisecom(config-port)#oam enable Enable OAM.
6 Raisecom(config-port)#oam active Configure the OAM active mode of the interface.

Configuring address pool and gateway

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip oam server pool Configure the address pool of the OAM property
pool-name and enter address pool configuration mode.
3 Raisecom(config-pool)#address start-ip- Configure the IP address range and subnet mask
address end-ip-address mask { mask- of the address pool.
address | mask-length }
4 Raisecom(config-pool)#gateway ip- Configure the gateway of the address pool.
address
Raisecom(config-pool)#exit Exit address pool configuration mode.

Raisecom Proprietary and Confidential

65
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 4 Zero-configuration

Step Command Description

5 Raisecom(config)#interface loopback Enter the loopback interface.
interface-number

Usually loopback interface 1 is used.

6 Raisecom(config-loopbackif)#ip address Configure the IP address of the loopback
ip-address [ ip-mask ] [ sub ] interface, which is the IP address of the
configured gateway of the address pool.
Raisecom(config-loopbackif)#exit Exit loopback interface configuration mode.
7 Raisecom(config)#interface gigaethernet Enter sub-interface configuration mode.
unit/slot/port.sub-interface
8 Raisecom(config-port)#encapsulation Configure the VLAN for encapsulating packets
dot1q vlan-id on the sub-interface to the configured
management VLAN.

Configuring NAT
Network Address Translation (NAT) is used to convert the private management IP address of
the remote device to the public IP address. Through zero-configuration, the remote device
obtains a private IP address from the CO device. NAT can be used to translate the private IP
address into the public IP address of the management network and distinguish different
remote devices in a form of public IP address+global interface ID. Network management
information transmitted between remote devices and the NView NNM system is forwarded
through the public IP address. Therefore, you should configure the public IP address and
related management VLAN of the CO device.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#access-list acl- Create an ACL and enter ACL configuration mode.
number
3 Raisecom(config-acl-ipv4- Configure an ACL filtering rule.
advanced)#rule [ rule-id ] permit ip
source-ip-address source-ip-mask any Sent the packet, whose source IP address complies
with the ACL filtering rule, to the CPU.
Raisecom(config-acl-ipv4- Exit ACL configuration mode.
advanced)#exit
4 Raisecom(config)#interface Enter Layer 3 physical interface configuration mode.
interface-type interface-number
The interface is used to connect the public network.
5 Raisecom(config-port)#ip address ip- Configure the IP address of the public network,
address ip-mask which is used to communicate with the NView NNM
system.
6 Raisecom(config-port)#nat outbound Configure NAT.
acl-number
The ACL ID is identical to the one created at step 2.

Raisecom Proprietary and Confidential

66
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 4 Zero-configuration

4.1.3 Configuring zero-configuration Server based on DHCP

Configuring zero-configuration Server based on Layer 3 physical interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter Layer 3 physical interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)#ip address ip- Configure the IP address of the Layer 3 physical
address interface, which is consistent with the gateway of the
address pool.
Raisecom(config-port)#ip dhcp server Enable DHCP Server on the interface.
By default, it is disabled.
Raisecom(config-port)#exit Exit Layer 3 physical interface configuration mode.
4 Raisecom(config)#ip dhcp server pool Configure the address pool of the DHCP property and
pool-name enter address pool configuration mode.
5 Raisecom(config-pool)#address start- Configure the IP address range and subnet mask of
ip-address end-ip-address mask the address pool.
{ mask-address | mask-length }
6 Raisecom(config-pool)#gateway ip- Configure the default gateway of the address pool.
address
The gateway is identical to the private IP address of
the management IP address assigned to the remote
device by the CO device.
7 Raisecom(config-pool)#lease expired Configure the lease of the address pool.
{ minute | infinite }
By default, it is 30min.
8 Raisecom(config-pool)#option 60 Configure information carried by Option60.
vendor-string
9 Raisecom(config-pool)#trap server-ip Configure the IP address of the SNMP server (NView
ip-address NNM system) to which the Trap is sent.
10 Raisecom(config-pool)#tftp-server-ip Configure the TFTP server related to the address
ip-address pool.
11 Raisecom(config-pool)#exit Exit address pool configuration mode.

If the zero-configuration server assigns management IP addresses to remote devices

based on Layer 3 physical interface, the network management information
exchanged between CO and remote devices is untagged packets.

Raisecom Proprietary and Confidential

67
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 4 Zero-configuration

Configuring zero-configuration based on Layer 3 sub-interface/VLAN interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#create vlan vlan-id Create and activate a VLAN.
active
3 Raisecom(config)#interface interface- Enter sub-interface configuration mode. The sub-
type interface-number interface ID is identical to the created VLAN ID.
Raisecom(config)#interface vlan Enter VLAN interface configuration mode. The
vlan-id VLAN ID is identical to the created VLAN ID.
4 Raisecom(config-port)#ip address ip- Configure the IP address of the sub-interface or
address VLAN interface, which is consistent with the
gateway of the address pool.
5 Raisecom(config-port)#ip dhcp server Enable DHCP Server on the interface.
By default, it is disabled.
Raisecom(config-port)#exit Exit sub-interface or VLAN interface configuration
mode.
6 Raisecom(config)#ip dhcp server pool Configure the address pool of the DHCP property
pool-name and enter address pool configuration mode.
7 Raisecom(config-pool)#address start- Configure the IP address range and subnet mask of
ip-address end-ip-address mask the address pool.
{ mask-address | mask-length }
8 Raisecom(config-pool)#gateway ip- Configure the default gateway of the address pool.
address
The gateway is identical to the private IP address of
the management IP address assigned to the remote
device by the CO device.
9 Raisecom(config-pool)#lease expired Configure the lease of the address pool.
{ minute | infinite }
By default, it is 30min.
10 Raisecom(config-pool)#option 60 Configure information carried by Option60.
vendor-string
11 Raisecom(config-pool)#trap server-ip Configure the IP address of the SNMP server
ip-address (NView NNM system) to which the Trap is sent.
12 Raisecom(config-pool)#tftp-server-ip Configure the TFTP server related to the address
ip-address pool.
13 Raisecom(config-pool)#exit Exit address pool configuration mode.

If the zero-configuration server assigns management IP addresses to remote devices

based on sub-interface or VLAN interface, the network management information
exchanged between CO and remote devices is Tagged packets with the
management VLAN ID.

Raisecom Proprietary and Confidential

68
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 4 Zero-configuration

Configuring NAT
NAT is used to convert the private management IP address of the remote device to the public
IP address. Through zero-configuration, the remote device obtains a private IP address from
the CO device. NAT can be used to translate the private IP address into the public IP address
of the management network and distinguish different remote devices in a form of public IP
address+global interface ID. Network management information transmitted between remote
devices and the NView NNM system is forwarded through the public IP address. Therefore,
you should configure the public IP address and related management VLAN of the CO device.

 By default, the IP address automatically obtained by the Loopback interface is the

NAT public IP address.
 If you delete the IP address of Loopback 1 interface through the no ip address
command, the Loopback 1 interface will automatically adopt the IP address of the
out-of-band SNMP interface or that of the uplink interface as the NAT public IP
address.
 When adopting the IP address of the uplink interface, refer to configurations in
step 5.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#access-list Create an ACL and enter ACL configuration mode.
acl-number
3 Raisecom(config-acl-ipv4- Configure an ACL filtering rule.
advanced)#rule [ rule-id ]
permit { source-ip-address Sent the packet, whose source IP address complies with
source-ip-mask | any } [ vrf the ACL filtering rule, to the CPU.
vrf-id ]
4 Raisecom(config-acl-ipv4- Exit ACL configuration mode.
advanced)#exit
5 Raisecom(config)#interface (Optional) enter Layer 3 physical interface configuration
interface-type interface-number mode.
The interface is used to connect the public network.
6 Raisecom(config-port)#ip address (Optional) configure the IP address of the public network,
ip-address ip-mask which is used to communicate with the NView NNM
system.
7 Raisecom(config-port)#nat Configure NAT.
outbound acl-number
The ACL ID is identical to the one created at step 2.

Configuring dual uplink NAT

The iTN8800 supports NAT in a dual uplink scenario. Dual uplinks refer to that the iTN8800
with two interfaces connected to two devices to implement network management path
protection.
The dual-uplink NAT is implemented by the two uplink interfaces configured with the
outbound function. The two uplink interfaces borrow the same IP address of the loopback 1
interface (other interfaces are all fine) and are associated with the same ACL ID. The IP

Raisecom Proprietary and Confidential

69
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 4 Zero-configuration

address or ACL ID of the two interfaces must be the same. Otherwise, the configuration will
fail.
The two interfaces configured with the Outband function can also borrow the IP addresses of
other Loopback interfaces. For details, see the description in step 7.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#access-list acl-number Create an ACL and enter ACL configuration
mode.
3 Raisecom(config-acl-ipv4-advanced)#rule Configure ACL filtering rules.
[ rule-id ] permit { source-ip-address
source-ip-mask | any } [ vrf vrf-id ] Packets with source IP addresses comply with
ACL filtering rules should be sent to the CPU.
4 Raisecom(config-acl-ipv4-advanced)#exit Exit ACL configuration mode.
5 Raisecom(config)#interface interface- Enter dual-uplink the 1st or 2nd sub-interface
type interface-number.subif1 configuration mode.
6 Raisecom(config-port)#encapsulation Configure the dual-uplink 1st or 2nd sub-
dot1Q vlan-id interface to encapsulate the VLAN ID, where
the VLAN ID is the same as the sub-interface.
7 Raisecom(config-port)#ip address Configure the dual-uplink 1st or 2nd sub-
unnumbered loopback 1 interface to borrow the IP address of the
loopback 1 interface.
They can also borrow the IP addresses of other
loopback interfaces, such as borrowing the IP
address of the Loopback 2 interface.
8 Raisecom(config-port)#ip ospf network Configure OSPF P2P network.
ptp
9 Raisecom(config-port)#nat outbound acl- Configure NAT.
number
The ACL ID should be the same as the one
created in step 2.

Configuring CO device to trigger remote zero-configuration

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#ip dhcp server Configure the CO device to actively trigger
trigger [ remote-mac-address | relay-ip remote zero-configuration.
relay-ip-address ]

Raisecom Proprietary and Confidential

70
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 4 Zero-configuration

(Optional) releasing IP address

When changing a remote device, which has applied for a management IP address, to prevent
the IP address from being occupied for a long time, you should manually release the IP
address at the CO server.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip Release the specified IP address.
dhcp address ip-
address release This command is used to release the lease table and NAT table of the CO
device only without influencing the IP address of the remote device.

(Optional) configuring lease file management

The iTN8800 supports saving and synchronizing the lease file automatically, as well
as deleting the lease file.
When changing the CO zero-configuration server, you can upload assigned IP addresses in a
form of lease to the TFTP/FTP server (such as a PC) for backup. After changing the CO
device, you can download the backup lease file to the local device to confirm that these
assigned IP addresses are not lost.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip dhcp lease save Save the lease file.
3 Raisecom(config)#ip dhcp lease erase (Optional) delete the lease file from
the DHCP server.
4 Raisecom(config)#ip dhcp address release [ pool Release lease of specified address
pool-name ] pool.
5 Raisecom(config)#ip dhcp address ip-address Release lease of the specified IP
release address.
6 Raisecom(config)#exit Exit global configuration mode.
7 Raisecom#upload dhcpLease { ftp ip-address Upload the lease file to the PC
username password filename | tftp ip-address through TFTP/FTP.
filename }
8 Raisecom#download dhcpLease { ftp ip-address Download the lease file from the PC
username password filename | tftp ip-address through TFTP/FTP.
filename }

Raisecom Proprietary and Confidential

71
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 4 Zero-configuration

Configuring DHCP Relay

If the zero-configuration server and the remote device are in the same network segment, the
remote device can obtain the IP address from the DHCP Server. Otherwise, the remote device
can obtain the IP address from the DHCP Server through the device, which is enabled with
DHCP Relay. The zero-configuration server can assign IP addresses to remote devices in
different network segments.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter Layer 3 physical interface configuration mode.
interface-type interface-
number

The Layer 3 physical interface needs to be configured

with the IP address.
3 Raisecom(config-port)#ip dhcp Enable DHCP Relay.
relay
4 Raisecom(config-port)#ip dhcp (Optional) configure the destination IP address. The IP
relay target-ip ip-address address can be either the IP address of DHCP Server or that of
DHCP Relay.
5 Raisecom(config-port)#ip dhcp (Optional) configure DHCP Relay to actively trigger remote
relay trigger [ remote-mac- zero-configuration.
address ]

4.1.4 Configuring zero-configuration based on DCN NMS self-

connection

Configuring DCN on the downlink interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter Layer 3 physical interface
interface-type interface-number configuration mode.
3 Raisecom(config-port)#dcn enable Enable DCN on the downlink interface.

Configuring OSPF DCN process

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf 32 Enable OSPF 32 process and enter OSPF
configuration mode.
3 Raisecom(config-router-ospf)#network (Optical) advertise the interface route on
ip-address wild-card-mask area area-id
Raisecom Proprietary and Confidential
72
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 4 Zero-configuration

Step Command Description

Raisecom(config-router- the public network to the private
ospf)#redistribute connected [ metric network. Enable the configuration under
metric ] [ metric-type { 1 | 2 ] the scenario that the IPRAN local
[ tag tag-value ] [ route-map map- products are connected downlink to a
name ] private network. Choose one mode
Raisecom(config-router- among the three modes.
ospf)#redistribute ospf [ process-id ]
[ vrf vrf-name ] [ metric metric ]
[ metric-type { 1 | 2 ] [ tag tag-
value ] [ route-map map-name ]
4 Raisecom(config-router- Enable the opaque LSA of OSPF.
ospf)#capability opaque
By default, it is disabled.
5 Raisecom(config-router- Enable the NMS self-connection of the
ospf)#capability dcn OSPF.
By default, it is enabled.

Configuring Trap server

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#snmp-server host ip- Configure the IP address of the NMS
address version { 1 | 2c } com-name server. When the CO device receives the
[ udpport port-id ] flooded NE messages from the remote
Raisecom(config)#snmp-server host ip- device, it will inform the NMS server
address version 3 { noauthnopriv | that the remote device is online by
authnopriv } user-name [ udpport port- sending Trap.
id ]

(Optional) configuring NAT

You can configure NAT when the OSPF DCN is connected downlink to the private network.
You have to enable NAT on the interface on the local device in the public network. For details,
see Configuring NAT in section 4.1.2 Configuring zero-configuration Server based on
extended OAM.

When the Raisecom IP RAN CO device is connected downlink to the private network,
you have to configure the Trap Server on the remote device after the remote device
network management channel is established and use the snmp-server keepalive-
trap enable command to enable the Keepalive to prevent the NAT entries from being
aged.

Raisecom Proprietary and Confidential

73
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 4 Zero-configuration

4.1.5 Checking configurations

No. Command Description
1 Raisecom(config)#show ip dhcp server Show configurations of interfaces of the DHCP
server.
2 Raisecom(config)#show ip dhcp server Show assigned IP addresses and information about
lease remote devices.
3 Raisecom(config)#show ip server pool Show configurations of the DHCP or OAM
[ pool-name ] address pool.
4 Raisecom(config)#show ip dhcp server Show statistics of the DHCP server.
statistics
5 Raisecom(config)#show ip dhcp static- Show static binding information about the IP
bind address in the address pool and the MAC address.
6 Raisecom(config)#show oam zero config Show configurations of directly-connected zero-
configurations.
7 Raisecom(config)#show remote config- Show configurations of remote devices in directly-
info all connected zero-configuration server mode.
8 Raisecom(config)#show ip dhcp relay Show configurations of DHCP Relay.
9 Raisecom(config)#show debugging ospf Show NE information collected about the CO
dcn_info [ self ] OSPF DCN zero-configuration server.
10 Raisecom(config)#show nat session Show NAT entries of the CO OSPF DCN zero-
[ config ] [ static ] configuration server.

4.2 Configuration examples

4.2.1 Example for configuring remote zero-configuration in private
network under IP RAN CO device

Networking requirements
As shown in Figure 4-1, as the IP RAN CO device, the iTN8800 is connected downlink to a
private network. The IP address of the NView NNM server and that of the iTN8800 are also
shown. The network management self-connection required through OSPF DCN remote zero-
configuration after the remote device iTN100 is powered on.

Raisecom Proprietary and Confidential

74
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 4 Zero-configuration

Figure 4-1 Networking with remote zero-configuration in the private network under the IP RAN
CO device

Configuration steps
Configure the zero-configuration server iTN8800 as below:
Step 1 Configure the downlink physical interface. Enable DCN.

Raisecom#config
Raisecom(config)#interface gigaethernet 1/1/1
Raisecom(config-gigaethernet1/1/1)# dcn enable

Raisecom(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2

Raisecom(config-gigaethernet1/1/2)#dcn enable

Step 2 Configure the OSPF DCN process.

Raisecom(config)#router ospf 32
Raisecom(config-router-ospf)#network 132.4.4.4 0.0.0.0 area 0.0.0.0
Raisecom(config-router-ospf)#capability opaque
Raisecom(config-router-ospf)#capability dcn

Step 3 Configure the Trap server.

Raisecom(config)#snmp-server host 10.0.0.1 version 2c public

Raisecom Proprietary and Confidential

75
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 4 Zero-configuration

Step 4 Configure NAT.

 Configure packets coming to the private network interface to be sent to the CPU.

Raisecom#config
Raisecom(config)#access-list 2000
Raisecom(config-acl-ipv4-advanced)#rule 10 permit ip any any
Raisecom(config-acl-ipv4-advanced)#exit

Raisecom(config)#class-map c1
Raisecom(config-cmap)#match acl 2000
Raisecom(config-cmap)#exit

Raisecom(config)#policy-map p1
Raisecom(config-pmap)#class-map c1
Raisecom(config-pmap)#forward-to-cpu

Raisecom#config
Raisecom(config)#interface gigaethernet 1/1/1
Raisecom(config-gigaethernet1/1/1)#service-policy ingress p1
Raisecom(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
Raisecom(config-gigaethernet1/1/2)#service-policy ingress p1

 Configure NAT on the public network interface.

Raisecom#config
Raisecom(config)#interface gigaethernet 1/2/1
Raisecom(config-gigaethernet1/2/1)#ip address 10.0.0.2 255.0.0.0
Raisecom(config-gigaethernet1/2/1)#nat outbound 2000

The IP address of the SNMP interface on the connected device cannot be in the
segment of the NView NNM server; otherwise, a static IP address should be
configured.

Checking results
Check NE information collected by the iTN8800 and obtain the IP address of the remote
device (the following example shows information about two remote devices of them).

Raisecom#show debugging ospf dcn_info

DCN info in OSPF Process 32
1. Device from "Raisecom", Model: "iTN185",
NEID is 132.1.1.1, NEIPv4 is 132.1.1.1,
MAC: 000E.5E2F.57B9,

2. Device from "Raisecom", Model: " iTN185",

Raisecom Proprietary and Confidential

76
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 4 Zero-configuration

NEID is 132.2.2.2, NEIPv4 is 132.2.2.2,

MAC: 000E.5E7D.0CDF,
……

After the CO device is configured, log in to each remote device and configure Trap Server and
Keepalive.

Raisecom(config)#snmp-server host 10.0.0.1 version 2c public

Raisecom(config)#snmp-server keepalive-trap interval 120
Raisecom(config)#snmp-server keepalive-trap enable

The NView NNM system receives a Trap that the network management channel of the remote
device is established.
The NView NNM system periodically receives the Keepalive messages, and NAT entries of
the CO device keep being updated and will not be aged.

Raisecom Proprietary and Confidential

77
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 5 Ethernet

5 Ethernet

This chapter describes principles and configuration procedures of Ethernet, including

following sections:
 Configuring VLAN
 Configuring MAC address table
 Configuring QinQ
 Configuring LLDP
 Configuring loop detection
 Configuring L2CP

5.1 Configuring VLAN

5.1.1 Preparing for configurations

Scenario
The main function of VLAN is to carve up logic network segments. There are 2 typical
application modes:
 Small LAN: on one Layer 2 device, the LAN is carved up to several VLANs. Hosts that
connect to the device are carved up by VLANs. So hosts in the same VLAN can
communicate, but hosts between different VLANs cannot communicate. For example,
the financial department needs to be separated from other departments and they cannot
access each other. In general, the port connected to the host is in Access mode.
 Big LAN or enterprise network: multiple Layer 2 devices connect to multiple hosts and
these devices are concatenated. Packets take VLAN Tag for forwarding. Ports of multiple
devices, which have identical VLAN, can communicate, but hosts between different
VLANs cannot communicate. This mode is used for enterprises that have many people
and need a lot of hosts, and the people and hosts are in the same department but different
positions. Hosts in one department can access each other, so you have to partition
VLANs on multiple devices. Layer-3 devices like a router are required if you want to
communicate among different VLANs. The concatenated ports among devices are in
Trunk mode.

Raisecom Proprietary and Confidential

78
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 5 Ethernet

Prerequisite
N/A

5.1.2 Configuring VLAN properties

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#create vlan vlan-list Create a VLAN.
active
By default, there is no VLAN and the interface is
not added to any VLAN.
3 Raisecom(config)#vlan vlan-id Enter VLAN configuration mode.
4 Raisecom(config-vlan)#name vlan-name (Optional) configure the VLAN name.
Raisecom(config-vlan)#exit
5 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
6 Raisecom(config-port)#portswitch Switch the interface to work in Layer 2 mode.
7 Raisecom(config-port)#switchport mode Configure the current interface as the
{ access | trunk } Access/Trunk interface.
By default, all interfaces are Access interfaces.

 VLANs that are created by using the vlan vlan-id command are in active status.
 All configurations of a VLAN cannot take effect until the VLAN is activated.

5.1.3 Configuring VLANs based on Access interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#portswitch Switch the interface to work in Layer 2 mode.
4 Raisecom(config-port)#switchport mode Configure the interface mode to Access.
access

5 Raisecom(config-port)#switchport access Configure the interface Access VLAN.

vlan vlan-id

6 Raisecom(config-port)#switchport access Configure the VLAN list available for the Access
egress-allowed vlan { all | vlan-list } interface.
[ confirm ]

Raisecom Proprietary and Confidential

79
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 5 Ethernet

5.1.4 Configuring VLANs based on Trunk interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#portswitch Switch the interface to work in Layer 2 mode.
4 Raisecom(config-port)#switchport mode Configure the interface mode to Trunk.
trunk

5 Raisecom(config-port)#switchport trunk Configure the interface Native VLAN.

native vlan vlan-id

6 Raisecom(config-port)#switchport trunk (Optional) configure the VLAN list available for

allowed vlan { all | vlan-list } the Trunk interface.
[ confirm ]
7 Raisecom(config-port)#switchport trunk (Optional) configure the Untagged VLAN list
untagged vlan { all | vlan-list } available for the Trunk interface.
[ confirm ]

 The Trunk interface permits Native VLAN packets to pass regardless of

configurations for Trunk Allowed VLAN list and Trunk Untagged VLAN list on the
interface. And forwarded packets do not carry VLAN TAG.
 When configuring a Native VLAN, the system will automatically create and
activate a VLAN if you do not create the VLAN in advance.
 The interface permits Trunk Allowed VLAN packets passing. If the VLAN is a
Trunk Untagged VLAN, the VLAN TAG of the packet is removed on the egress
interface. Otherwise, the packet is not modified.
 If the configured Native VLAN is not the default VLAN and there is no default
VLAN in the VLAN list on the Trunk interface, the interface will not allow packets in
the default VLAN to pass.
 When configuring a Trunk Untag VLAN list, the system automatically adds all
Untagged VLAN to the Trunk allowed VLAN.
 Trunk allowed VLAN list and Trunk Untagged VLAN list are valid for the static
VLAN only.

5.1.5 Checking configurations

No. Command Description
1 Raisecom#show vlan [ vlan-list | static | Show configurations and status of all
dynamic ] [ detail ] VLANs or a specified VLAN.
2 Raisecom#show switchport interface Show interface switching configurations.
interface-type interface-number

Raisecom Proprietary and Confidential

80
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 5 Ethernet

5.2 Configuring MAC address table

5.2.1 Preparing for configurations

Scenario
When configuring the MAC address table, you can configure static MAC addresses for fixed
and important devices to prevent illegal users from accessing the network from other locations.
To avoid saving too many dynamic MAC addresses to the MAC address table and exhausting
resources of the MAC address table, you need to configure the aging time of dynamic MAC
addresses to ensure upgrading dynamic MAC addresses effectively.

Prerequisite
N/A

5.2.2 Configuring static MAC address table

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mac-address static Add a static unicast MAC address to the MAC
unicast mac-address vlan vlan-id address table.
interface-type interface-number

Raisecom(config)#mac-address static
unicast mac-address vsi vsi-name
It must be a unicast MAC address. The
interface-type interface-number local MAC address, multicast address, all-
Raisecom(config)#mac-address static F, and all-0 MAC addresses cannot be set
unicast mac-address vsi vsi-name vc-id to the static MAC address.
vc-id peer ip-address

5.2.3 Configuring dynamic MAC address table

Commands for steps 2, 3, and 4 are used to configure dynamic MAC address limit in interface
configuration mode. Commands for steps 5–10 and 11–12 are used to configure dynamic
MAC address limit in VLAN configuration mode and VSI configuration mode respectively.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)#mac-address Enable MAC address learning.
learning enable
By default, MAC address learning is enabled.

Raisecom Proprietary and Confidential

81
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 5 Ethernet

Step Command Description

4 Raisecom(config-port)#mac-address (Optional) configure dynamic MAC address limit.
threshold threshold-value
By default, no dynamic MAC address limit is
configured.
5 Raisecom(config-port)#mac-address (Optional) configure MAC address flapping
move-restrain enable suppression.
Raisecom(config-port)#exit
By default, it is not configured.
6 Raisecom(config)#vlan vlan-id Enter VLAN configuration mode.
7 Raisecom(config-vlan)#mac-address Enable MAC address learning.
learning enable
Raisecom(config-vlan)#exit
By default, MAC address learning is enabled.
8 Raisecom(config)#mac-address (Optional) configure the aging time of the MAC
aging-time second address.
By default, it is 300s.
9 Raisecom(config)#vlan vlan-id (Optional) enter VLAN configuration mode.
10 Raisecom(config-vlan)#mac-address (Optional) configure dynamic MAC address limit.
threshold threshold-value
By default, no dynamic MAC address limit is
configured.
11 Raisecom(config-vlan)#exit (Optional) exit VLAN configuration mode and enter
global configuration mode.
12 Raisecom(config)#mpls vsi vsi-name (Optional) create a VSI and enter VSI configuration
static mode.
13 Raisecom(config-vsi)#mac-address (Optional) configure dynamic MAC address limit.
threshold threshold-value
By default, no dynamic MAC address limit is
configured.

5.2.4 Configuring blackhole MAC address

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mac-address Create the blackhole MAC address.
blackhole mac-address { vlan vlan-
id | vsi vsi-name } By default, no blackhole MAC address is configured.

5.2.5 Checking configurations

No. Command Description
1 Raisecom#show mac-address count [ vlan vlan-id ] [ interface- Show the number
type interface-number ] of MAC

Raisecom Proprietary and Confidential

82
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 5 Ethernet

No. Command Description

Raisecom#show mac-address count vsi vsi-name [ interface-type addresses.
interface-number]
Raisecom#show mac-address count vsi vsi-name [ vc-id vc-id peer
ip-address ]

2 Raisecom#show mac-address { all | static | dynamic } [ vlan Show MAC

vlan-id ] [ interface-type interface-number ] addresses.
Raisecom#show mac-address { all | static | dynamic } vsi vsi-
name [ interface-type interface-number ]
Raisecom#show mac-address { all | static | dynamic } vsi vsi-
name [ vc-id vc-id peer ip-address ]
Raisecom#show mac-address mac-address [ vlan vlan-id | vsi vsi-
name ]
Raisecom#show mac-address blackhole [ vlan vlan-id | vsi vsi-
name ]
3 Raisecom#show mac-address learning vlan-list Show enabling
information about
Raisecom#show mac-address learning interface [ interface-type MAC address
interface-number ] learning.

5.2.6 Maintenance
No. Command Description
1 Raisecom(config)#clear mac-address dynamic Clear MAC
Raisecom(config)#clear mac-address dynamic [ vlan vlan-id ] addresses.
[ interface-type interface-number ]
Raisecom(config)#clear mac-address dynamic vsi vsi-name
[ interface-type interface-number ]
Raisecom(config)#clear mac-address dynamic vsi vsi-name [ vc-id
vc-id peer ip-address ]
Raisecom(config)#clear mac-address dynamic mac-address [ vlan
vlan-id | vsi vsi-name ]

5.3 Configuring QinQ

5.3.1 Preparing for configurations

Scenario
With basic QinQ, you can add outer VLAN Tag and freely plan your own private VLAN ID.
Therefore, the data between devices on both ends of the Internet Service Provider (ISP)
network can be transparently transmitted, without conflicting with the VLAN ID in the ISP
network.
QinQ-based VLAN mapping can meet the following conditions:

Raisecom Proprietary and Confidential

83
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 5 Ethernet

 N:1 VLAN mapping

 Single-to-double VLAN mapping
 2:2 VLAN mapping
 Double-to-single VLAN mapping

Prerequisite
 Connect interfaces and configure physical parameters of interfaces. Make the physical
layer Up.
 Create a VLAN.

5.3.2 Configuring basic QinQ

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter Layer 2 interface configuration
interface-number mode.
Raisecom(config-port)#portswitch

3 Raisecom(config-port)#dot1q-tunnel Enable basic QinQ on the interface.

4 Raisecom(config-port)#switchport mode access Configure the interface mode to
Raisecom(config-port)#switchport access vlan Access and configure the default
vlan-id VLAN ID of the Access interface.

5.3.3 Configuring QinQ VLAN mapping

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number

3 Raisecom(config-port)#switchport qinq dot1q- Enable basic QinQ on the interface.

tunnel

4 Raisecom(config-port)#vlan-mapping dot1q Configure 1:1 VLAN mapping or N:1

vlan-id-1 [ to vlan-id-2 ] translate vlan- VLAN mapping.
id-after
Raisecom(config-port)#vlan-mapping dot1q Add an outer VLAN Tag.
vlan-id-1 [ to vlan-id-2 ] translate svlan
svlan-id [ cos cos ] cvlan cvlan-id-1 [ to
cvlan-id-2 ]
Raisecom(config-port)#vlan-mapping qinq Configure 2:2 VLAN mapping rules.
svlan svlan-id cvlan cvlan-id-1 [ to cvlan-
id-2 ] translate svlan svlan-id cvlan cvlan-
id-1 [ to cvlan-id-2 ]

Raisecom Proprietary and Confidential

84
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 5 Ethernet

Step Command Description

Raisecom(config-port)#vlan-mapping qinq Translate double VLAN Tags to a single
svlan svlan-id cvlan cvlan-id translate vlan VLAN Tag.
vlan-id
5 Raisecom(config-port)#vlan-mapping miss (Optional) discard the packet when its
discard VLAN Tag fails to match VLAN mapping
rules.

5.3.4 Checking configurations

No. Command Description
1 Raisecom#show dot1q-tunnel Show configurations of basic QinQ.
2 Raisecom#show vlan-mapping interface interface- Show VLAN mapping rules on the
type interface-number interface.

5.4 Configuring LLDP

5.4.1 Preparing for configurations

Scenario
When you obtain connection information between devices through the NView NNM system
for topology discovery, you need to enable LLDP on the iTN8800. Therefore, the iTN8800
can notify its information to the neighbours mutually, and store neighbour information to
facilitate the NView NNM system querying information.

Prerequisite
N/A

5.4.2 Enabling global LLDP

After global LLDP is disabled, you cannot re-enable it immediately. Global LLDP
cannot be enabled unless the restart timer times out.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#lldp enable Enable global LLDP.
By default, it is disabled.

Raisecom Proprietary and Confidential

85
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 5 Ethernet

5.4.3 Enabling interface LLDP

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#lldp enable Enable interface LLDP.
By default, interface LLDP is enabled.

5.4.4 Configuring LLDP basic functions

When configuring the delivery delay timer and the delivery period timer, set the value
of the delivery delay timer to be smaller than or equal to one quarter of the value of
the delivery period timer.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#lldp message- (Optional) configure the delivery period timer of the
transmission interval second LLDP packet.
By default, it is 30s.
3 Raisecom(config)#lldp message- (Optional) configure the delivery delay timer of the
transmission delay second LLDP packet.
By default, it is 2s.
4 Raisecom(config)#lldp message- (Optional) configure the aging coefficient of the
transmission hold-multiplier LLDP packet.
coefficient
By default, it is 4.
5 Raisecom(config)#lldp restart-delay (Optional) configure the restart timer. After global
second LLDP is disabled, it cannot be enabled unless the
restart timer times out.
By default, it is 2s.

5.4.5 Configuring LLDP Trap

When the network changes, you need to enable LLDP Trap to send topology update traps to
the NView NNM system immediately.

Step Command Description

1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

86
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 5 Ethernet

Step Command Description

2 Raisecom(config)#lldp trap- (Optional) configure the LLDP Trap delivery period timer.
interval second
By default, it is 5s.

After enabled with LLDP Trap, the iTN8800 will send Traps after detecting aged
neighbors, newly-added neighbors, and changed neighbor information.

5.4.6 Checking configurations

No. Command Description
1 Raisecom#show lldp local config Show LLDP local configurations.
2 Raisecom#show lldp local system-data Show LLDP local system information.
[ interface-type interface-number ]
3 Raisecom#show lldp remote [ interface-type Show LLDP neighbor information.
interface-number ] [ detail ]
4 Raisecom#show lldp statistic [ interface-type Show LLDP packet statistics.
interface-number ]

5.5 Configuring loop detection

5.5.1 Preparing for configurations

Scenario
In the network, hosts or Layer 2 devices connected to access devices may form a loopback
intentionally or involuntary. Enable loop detection on downlink interfaces of all access
devices to avoid the network congestion generated by unlimited copies of data traffic. Once a
loop is detected on a port, the interface will be blocked.

Prerequisite
Configure physical parameters on an interface and make the physical layer Up.

5.5.2 Configuring loop detection

 Loop detection and STP are mutually exclusive. They cannot be enabled
simultaneously.
 For directly connected devices, you cannot enable loop detection on both ends
simultaneously. Otherwise, interfaces of these 2 devices are blocked.

Raisecom Proprietary and Confidential

87
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 5 Ethernet

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
3 Raisecom(config-port)#portswitch Configure the interface to a switching
interface or a Layer 3 interface working in
Raisecom(config-port)#mold l2
L2 mode.
4 Raisecom(config-port)#loopback-detection Enable loop detection on a required
[ pkt-vlan { untag | vlan-id } ] [ hello- interface.
time second ] [ restore-time second ]
[ action { block | trap-only | shutdown } ]
You can simultaneously configure the
VLAN of the transmitted packet
(optional), hello period (optional), restore
time (optional), and loopback action.
5 Raisecom(config-port)#loopback-detection Manually release the interface blocked
manual restore because of the detected loop.

5.5.3 Checking configurations

No. Command Description
1 Raisecom#show loopback-detection [ statistics ] Show configurations of loop
[ interface-type interface-list ] detection on interfaces.

5.5.4 Maintenance
Command Description
Raisecom(config)#clear loopback-detection statistic Clear statistics of loop detection.
[ interface-type interface-list ]

5.6 Configuring L2CP

5.6.1 Preparing for configurations

Scenario
You can configure the mode for process processing Layer 2 control packets of the customer
network on the access device within MAN according to the services provided by carriers. This
configuration is done on the network-side interface of the customer.

Raisecom Proprietary and Confidential

88
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 5 Ethernet

Prerequisite
N/A

5.6.2 Configuring L2CP

No. Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
3 Raisecom(config-port)#l2cp drop protocol Configure the action to discarding L2CP
{ stp | lacp | oam | dot1x | elmi | lldp packets, which means that the packet will be
| pagp | udld | pvst | cdp | vtp | mac- discarded when the type of the packet or
address mac-address } destination MAC address matches with the
discarding rule.
4 Raisecom(config-port)#l2cp tunnel { pw Configure the action to transparently
vc-id peer ip-address | mac mac-address | transmitting L2CP packets, which means that
vlan vlan-id | port interface-type the packet will be transmitted transparently
interface-number } protocol { stp | lacp when the type of the packet matches with the
| oam | dot1x | elmi | lldp | pagp | udld transparent transmission rule.
| pvst | cdp | vtp }

5.6.3 Checking configurations

No. Command Description
1 Raisecom#show l2cp tunnel statistics Show statistics of the transparent transmission
[ port-name | channel-name ] packets.

Raisecom Proprietary and Confidential

89
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 6 Clock synchronization

6 Clock synchronization

This chapter describes principles and configuration procedures of clock synchronization, as

well as related configuration examples, including the following sections:
 Configuring clock synchronization based on SyncE
 Configuring PTP-based clock synchronization
 Maintenance
 Configuration examples

6.1 Configuring clock synchronization based on SyncE

6.1.1 Preparing for configurations

Scenario
In the PTN, to communicate properly, the sender must put the pulse in the specified timeslot
when sending the digital pulse signal and the receiver can extract the pulse from the specified
timeslot. To realize this, you must resolve the synchronization problem.
The Synchronous Ethernet (SyncE) technology can perform clock synchronization in the PTN.
Because it does not support phase synchronization but frequency synchronization only, it is
applied to Base Stations (BSs), fixed network TDM relay, leased clock network relay, and
radio BSs which have no requirement on phase synchronization, such as Global System for
Mobile Communications (GSM) and Wideband Code Division Multiple Access (WCDMA).
The iTN8800 supports automatically selecting the optimum clock source. You just need to
configure clock source properties of SyncE. In addition, the iTN8800 supports manually
selecting the specified clock source.

Prerequisite
N/A

Raisecom Proprietary and Confidential

90
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 6 Clock synchronization

6.1.2 Configuring properties of SyncE clock source

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#synce enable Enable SyncE.
By default, it is disabled.
3 Raisecom(config)#synce operation-type Configure the working status of SyncE.
{ auto-select | forced-freerun |
forced-holdover } By default, it is forced-freerun, namely, forcible
vibration mode.
4 Raisecom(config)#synce source Configure the SSM quality level of the SyncE
{ internal | interface { clock0 | clock source.
clock1 | interface-type interface-
number } priority priority [ quality-
level level ] [ ring-outside ]
[ lockout ]
5 Raisecom(config)#synce ssm { standard Enable the function of using the SSM quality level
| extend | disable } [ transmit- of the SyncE in selecting source and configure the
threshold threshold ] sending threshold.
6 Raisecom(config)#synce switch-mode (Optional) enable automatic recovery of the
{ revertive [ wtr-time time ] | non- SyncE clock source and configure the WTR of the
revertive } clock source.
By default, automatic recovery of the SyncE clock
source is enabled.
7 Raisecom(config)#synce source hold- Configure the hold-off time of the clock source.
off-time time

6.1.3 Manually choosing SyncE clock source

Step Command Description
1 Raisecom#config Enter global configuration
mode.
2 Raisecom(config)#synce manual-source { internal | Switch the clock source
interface { clock0 | clock1 | interface-type manually.
interface-type interface-number } }
3 Raisecom(config)#synce forced-source { internal | Switch the clock source
interface { clock0 | clock1 | interface-type forcibly.
interface-number } }

6.1.4 Checking configurations

No. Command Description
1 Raisecom#show synce Show global configurations of SyncE.

Raisecom Proprietary and Confidential

91
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 6 Clock synchronization

No. Command Description

2 Raisecom#show synce source Show configurations of the SyncE clock source.
3 Raisecom#show clock interface Show configuration of the clock interface.
4 Raisecom#show synce ssm Show SSM configurations of the SyncE.

6.2 Configuring PTP-based clock synchronization

6.2.1 Preparing for configurations

Scenario
The synchronous Ethernet technology supports frequency synchronization only, which fails to
meet the strict requirements of 3G mobile backhaul and power market on the accuracy of
clock synchronization. However, PTP supports both frequency synchronization and phase
synchronization. Therefore, PTP is adopted for time synchronization over the full-mesh
network.

Prerequisite
The iTN8800-TAU is in position.

6.2.2 Configuring PTP clock modes

Step Command Description
1 Raisecom# config Enter global configuration mode.
2 Raisecom(config)#ptp mode Configure PTP-based time synchronization mode.
{ ordinary | boundary |
p2ptransparent | e2etransparent
By default, the time synchronization mode is ordinary.
| ordinary-p2ptransparent |
ordinary-e2etransparent }
We recommend using the P2P transparent clock
mode to synchronize time and frequency.
3 Raisecom(config)#ptp ordinary (Optical) configure the Ordinary clock card to be in
slave-only Slave mode only.
By default, when the iTN8800 works in the OC clock
model, it can works in the Master mode or the Slave
mode.
4 Raisecom(config)#ptp enable Enable global PTP.
By default, global PTP is disabled.
5 Raisecom(config)#interface Enter the switch interface configuration mode.
interface-type interface-number
6 Raisecom(config-port)#ptp Enable PTP on the interface.
enable
By default, PTP on all interfaces is disabled.

Raisecom Proprietary and Confidential

92
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 6 Clock synchronization

6.2.3 Configuring properties of PTP clock

Step Command Description
1 Raisecom# config Enter global configuration mode.
2 Raisecom(config)#ptp step Configure the Step property of the clock.
{ onestep | twostep }
By default, the Step property of the clock is configured to
onestep.
3 Raisecom(config)#ptp domain (Optional) configure the clock domain of the iTN8800. PTP
domain-number devices with the same clock domain form a PTP synchronization
network. The device only processes PTP packets which have the
same clock domain.
By default, the clock domain of the iTN8800 is configured to 1.
4 Raisecom(config)#ptp Configure priority 1 or priority 2 of the PTP clock.
priority1 priority
[ priority2 priority ] By default, it is 128.
5 Raisecom(config)#ptp Configure the PTP-based clock source. Based on this
timesource { atomic | gps | configuration, determine the best master clock on the network
handset | ntp | oscillator through the BMS algorithm.
| ptp | radio | other }
By default, the clock source of the card is configured to
oscillator.
6 Raisecom(config)#interface Enter the interface configuration mode.
interface-type interface-
number
7 Raisecom(config-port)#ptp (Optional) configure the PTP-based clock source. Based on this
timesource { atomic | gps | configuration, determine the best master clock on the network
handset | ntp | oscillator through the BMS algorithm.
| ptp | radio | other }
By default, the clock source of the interface is configured to gps.
8 Raisecom(config-port)#ptp (Optional) enable frequency adjustment of the PTP clock.
adjust-frequency enable
By default, it is enabled.

6.2.4 Configuring packet transmission

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ptp transmit (Optional) configure the mode for sending PTP packets.
{ appropriate | multicast |
unicast }
By default, it is multicast.
3 Raisecom(config)#ptp protocol (Optional) configure the type of the protocol that
{ ethernet | udp } transmits 1588v2 packets.
By default, it is Ethernet.
4 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-number

Raisecom Proprietary and Confidential

93
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 6 Clock synchronization

Step Command Description

5 Raisecom(config-port)#ptp master (Optional) configure the IP address of the Master which
{ ip ip-address | mac mac-address can be negotiated concurrently. The Slave will
[ vlan vlan-id ] } automatically send unicast request to the configured
Master. After the Master responds, it will send unicast
PTP packets to the interface, thus starting
synchronization.
6 Raisecom(config-port)#ptp (Optional) add the IP address or MAC address of the
peer{ ip ip-address | mac mac- Peer clock device. The device configured with the peer
address [vlan vlan-id] } address pool will actively send Pdelay packets to the
peer.
7 Raisecom(config-port)#ptp (Optional) configure the interval for the interface to send
interval { announce value | delay PTP packets. The interval is 2coefficient.
value | sync value }
By default, it is
 -3 for Announce packets, namely, 1/8s
 0 for Delay_Req packets, namely, 1s
 -4 for Sync packets, namely, 1/16s

 Configure rate limiting on the sync and delay packets:

(1 × number of slave interfaces + 2 × number of master
interfaces) × (upper rate threshold of sending SYNC or
delay packets) < = 112/s
 If the device is from other vendors, it is required that

the rate of sending sync and delay packets to be no

more than 64/s.
8 Raisecom(config-port)#ptp timeout (Optional) configure the timeout alarm time for the clock
announce coefficient interface receiving the announce packet. The real
timeout alarm time is configured to 2 coefficient.
By default, the timeout alarm time for the clock interface
receiving the announce packet is configured to 3. This
value is 3 times longer than the one for the clock
interface sending announce packet.

6.2.5 (Optional) configuring properties of PTP clock interface

Step Command Description
1 Raisecom# config Enter global configuration mode.
2 Raisecom(config)#interface Enter PTP clock interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)#ptpdelay (Optional) configure the delay measurement mode on the
{ end | peer } interface.
By default, it is E2E for the PTP clock interface.

Raisecom Proprietary and Confidential

94
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 6 Clock synchronization

Step Command Description

4 Raisecom(config-port)#ptp (Optional) configure the asymmetric compensation value
asymmetry period of the path for the clock interface, namely the time
difference of path delay between receiving the packets
and sending the packets.

Generally, this command is configured after the

synchronization is successfully. Then narrow the
time difference between the master device and
slave device by configuring the asymmetric
compensation value of the path.
5 Raisecom(config-port)#ptp state (Optional) configure enforced interface status and
{ master | slave | passive } disable BMC algorithm.
By default, no interface is in enforced status. The
interface status is decided by the BMC algorithm.
6 Raisecom(config-port)#external (Optional) configure the value of the external clock
priority1 priority priority on the PTP interface.
By default, the priority ranges from 1 to 128.
7 Raisecom(config-port)#ptp (Optional) configure the clock source on the PTP
timesource { atomic | gps | interface.
handset | ntp | oscillator |
ptp | radio | other } By default, it is gps.
8 Raisecom(config-port)#ptp (Optional) configure the PTP downstream clock domain.
downstream-domain domain-number
By default, it is 0.

6.2.6 Inputting/Outputting clock signals on 1pps-tod interface

Configure the iTN8800 as below. Step 3 and Step 4 are optional. To configure the 1pps-tod
interface to be the input interface of clock source, perform step 3. To configure the 1pps-tod
interface to be the output interface of clock source, perform step 4.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter PTP clock interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)#ptp 1pps- (Optional) enable the input function on the 1pps-tod
tod input interface and input the clock source.
Raisecom(config-port)#ptp input
{ internal | ifname } By default, the input function on the 1pps-tod interface is
enabled and the 1pps-tod signals are taken as the PTP
input clock source.
4 Raisecom(config-port)#ptp 1pps- (Optional) enable the output function on the 1pps-tod
tod output interface.
By default, the output function on the 1pps-tod interface
is enabled.

Raisecom Proprietary and Confidential

95
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 6 Clock synchronization

Step Command Description

5 Raisecom(config-port)#ptp 1pps- (Optional) configure the format for transmitting the 1pps-
tod mode { time-info | time- tod clock signals.
state | nmea-0183 }
By default, the format is nmea-0183.

The format for transmitting the 1pps-tod clock

signals should comply with GPRMC requirement
defined by the NMEA0183.
6 Raisecom(config-port)#ptp 1pps- (Optional) configure the cable compensation or delay
tod input cable-delay-compensate compensation for inputting 1pps-tod clock signals
{ length cable-length | time
time-value } By default, the input cable compensation is 0 meter and
the delay compensation is 0ns.

The 1pps-tod interface is for receiving the GPS time information and transfer the time
information between devices or base stations

6.2.7 Inputting/Outputting clock signals on 1pps interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter clock interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)#ptp 1pps Enable the input/output function on the 1pps clock
{ input | output } interface.
By default, the output function on the 1pps interface is
enabled.

6.2.8 Checking configurations

No. Command Description
1 Raisecom#show ptp { upstream | Show PTP information on the uplink/downlink
downstream } interface of the clock card.
2 Raisecom#show ptp [ clock | Show related configurations about the clock.
foreignmaster | parent | time |
sysn ]
3 Raisecom#show ptp interface-type Show clock configurations of the interface.
interface-number
4 Raisecom#show ptp { 1pps-tod | Show configurations of the external clock interface.
1pps } interface-number

Raisecom Proprietary and Confidential

96
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 6 Clock synchronization

6.3 Maintenance
Command Description
Raisecom#ptp statistics clear Clear statistics of PTP packets on all interfaces.

6.4 Configuration examples

6.4.1 Examples for configuring clock synchronization based on
SyncE

Networking requirements
As shown in Figure 6-1, the Radio Network Controller (RNC) transmits clock signals to iTN
A through the SyncE. iTN A is connected to the carrier's NodeB. Clock signals are transmitted
to the NodeB through the downlink GE interface.

Figure 6-1 Configuring clock synchronization based on SyncE

Configuration steps
Configure properties of the clock source.
 Configure iTN A.

Raisecom#hostname iTNA
iTNA#config
iTNA(config)#synce enable
iTNA(config)#synce ssm standard
iTNA(config)#synce source interface gigaethernet 1/2/1 priority 1
quality-level 2
iTNA(config)#synce operation-type auto-select

Raisecom Proprietary and Confidential

97
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 6 Clock synchronization

 Configure iTN B.

Raisecom#hostname iTNB
iTNB#config
iTNB(config)#synce enable
iTNB(config)#synce ssm standard
iTNB(config)#synce source interface gigaethernet 1/1/1 priority 1 1
iTNB(config)#synce operation-type auto-select

Checking results
Use the show synce command to show configurations of clock synchronization in the SyncE.

iTNA#show synce
Synce : enable
Synce running status(PLL): locked(auto-select)
Current clock source: gigaethernet 1/2/1(Ql:2)
Previous clock source: null(Ql:--)
Revertive mode : enable
Latest switch time : 2000-11-07,02:49:45.083
Holdoff time(ms) : 1800
Wait restore time(min): 5
iTNB#show synce
Synce : enable
Synce running status(PLL): freerun(auto-select)
Current clock source: gigaethernet 1/2/1 (Ql:2)
Previous clock source: null(Ql:--)
Revertive mode : enable
Latest switch time : 2000-11-07,02:49:45.083
Holdoff time(ms) : 1800
Wait restore time(min): 5

Use the show synce ssm command to show SSM status of the SyncE.

iTNA#show synce ssm

Quality level mode : standard
Ssm source name : gigaethernet 1/2/1
Ssm quality level : 2
Transmit quality level threshold: 0
Source Admin-Qlevel Recv-Qlevel Info-Rx Info-Tx
Event-Rx Event-Tx Src-Id Valid Out
-------------------------------------------------------------------------
gigaethernet1/1/1 2 -- 215 245 0
0 0000.0000.0000 True True
iTNB#show synce ssm
Quality level mode : standard
Ssm source name : gigaethernet 1/1/1
Ssm quality level : 2

Raisecom Proprietary and Confidential

98
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 6 Clock synchronization

Transmit quality level threshold: 0

Source Admin-Qlevel Recv-Qlevel Info-Rx Info-Tx
Event-Rx Event-Tx Src-Id Valid Out
-------------------------------------------------------------------------
gigaethernet1/1/1 -- -- 245 215 0
0 0000.0000.0000 True True

Raisecom Proprietary and Confidential

99
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 7 TDMoP

7 TDMoP

This chapter describes principles and configuration procedures of Time Division Multiplex
over Packet (TDMoP), including following sections:
 Configuring TDM interface
 Configuring SDH interface
 Configuring Tunnel
 Configuring PW
 Configuring TDMoP clock
 Maintenance

7.1 Configuring TDM interface

7.1.1 Preparing for configurations

Scenario
The iTN8800 accesses TDM services through the RE16 card. Each interface can be
configured independently. When initiating circuit emulation services, you need to configure
basic properties and related features of TDM interfaces, such as the link type and Rx clock
source of TDM interfaces, and codes of TDM idle timeslots.
Circuit emulation services are encapsulated based on TDM interface type. When a TDM
interface is in framed/multiframed mode, TDM frame structure can be recognized and
structured encapsulation mode is adopted. When a TDM interface is in unframed mode,
unstructured encapsulation mode is adopted.
In structured encapsulation mode, PW can be only related to timeslots that carry services.
Timeslots related to the PW are occupied timeslots and the ones does not carry services are
idle timeslots.

Prerequisite
The RE16 card is inserted into the iTN8800.

Raisecom Proprietary and Confidential

100
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 7 TDMoP

7.1.2 Configuring link type of TDM interfaces

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface tdm Enter TDM interface configuration mode.
1/slot-id/interface-number
3 Raisecom(config-tdm-1/*/*)#tdm- Configure the link type of TDM interfaces.
type { e1-unframed | e1-framed |
e1-crc-framed }
By default, the link type of TDM interfaces is E1
unframed.

7.1.3 Configuring TDM sub-interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter TDM interface configuration mode.
tdm 1/slot-id/interface-
number
3 Raisecom(config-tdm- Configure the link type of TDM interface to E1 framed.
1/*/*)#tdm-type { e1-unframed
| e1-framed | e1-crc-framed } By default, the link type of TDM interfaces is E1 unframed.
4 Raisecom(config-tdm- Enter TDM sub-interface configuration mode.
1/*/*.*)#interface tdm
1/slot-id/interface-
number.sub-interface-number
5 Raisecom(config-tdm-1/*/*.*)# Configure relationship between the TDM sub-interface and
timeslot { timeslot } timeslots.
By default, the TDM interface is in E1 unframed mode and
the sub-interface associates with all timeslots.

7.1.4 Configuring TDM interface loopback

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface tdm 1/slot- Enter TDM interface configuration
id/interface-number mode.
3 Raisecom(config-tdm-1/*/*)#loopback { external | Configure TDM interface loopback.
internal }

Raisecom Proprietary and Confidential

101
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 7 TDMoP

7.1.5 Checking configurations

No. Command Description
1 Raisecom(config)#show interface tdm { 1/slot- Show configurations of the
id/interface-number | 1/slot-id/interface-number.sub- TDM interface.
interface-number }

7.2 Configuring SDH interface

7.2.1 Preparing for configurations

Scenario
The front panel of the RS4 card provides 4 SFP interfaces, which can access 4 ways of STM-1
services or 1 way of STM-4 services. The rate of the first SFP interface can be configured to
STM-1 or STM-4 while the rate of other interfaces is fixed to STM-1.
The iTN8800 accesses SDH services through the RS4 card. You can configure the related
parameters, such as error code threshold and overhead byte, as required.
The STM1 interface on the RS4 card has 63 SDH sub-interfaces. The STM4 interface has 252
sub-interfaces, which can map up to 252 ways of E1 services to the SDH. When configuring
TDM emulation services, you can configure the basic attributes of TDM services on the SDH
sub-interfaces, such as TDM service line type and clock recovery.

Prerequisite
The RS4 card is in position.

7.2.2 Configuring SDH interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter STM interface configuration mode.
stm unit/slot/port
3 Raisecom(config-stm- Configure the threshold of pointer
port)#sdh aupje-threshold justification on AU layer of SDH Higher-
{ positive | negative } order Path (HP).
threshold-value
By default, the threshold of pointer
justification on AU layer of SDH HP within
15min is 65535.

Raisecom Proprietary and Confidential

102
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 7 TDMoP

Step Command Description

4 Raisecom(config-stm- Configure the threshold of SDH Errored
port)#sdh es-threshold Second (ES).
regenerator-section
threshold-value By default, the threshold of SDH ES within
[ multiplex-section 15min is 900.
threshold-value | higher-
path threshold-value |
lower-path threshold-
value ]
5 Raisecom(config-stm- Configure the threshold of SDH Severely
port)#sdh ses-threshold Errored Second (SES).
regenerator-section
threshold-value By default, the threshold of SDH SES within
[ multiplex-section 15min is 900.
threshold-value | higher-
path threshold-value |
lower-path threshold-
value ]
6 Raisecom(config-stm- Configure the threshold of SDH Excessive
port)#sdh exc-threshold Error (EXC) second.
regenerator-section
threshold-value By default, the threshold of SDH EXC second
[ multiplex-section is 3, indicating 10-3.
threshold-value | higher-
path threshold-value ]
7 Raisecom(config-stm- Configure the threshold of SDH signal
port)#sdh sd-threshold degradation.
regenerator-section
threshold-value By default, the threshold of SDH signal
[ multiplex-section degradation is 6, indicating 10-6.
threshold-value | higher-
path threshold-value ]
8 Raisecom(config-stm- Enable MS-AIS insertion.
port)#sdh msais-insert
{ rstim | mssd } enable
By default, MS-AIS insertion is disabled.
9 Raisecom(config-stm- Configure the expected and sent HP C2 bytes.
port)#sdh overhead c2
[ vc4 vc4-number ] By default, both the expected and sent HP C2
{ expected string | bytes are 0x2.
transmit string } *
10 Raisecom(config-stm- Configure the expected and sent regeneration
port)#sdh overhead j0 section trace J0 bytes.
{ expected string |
transmit string } * By default, both the expected and sent
regeneration section trace J0 bytes are
Raisecom-Opcom.
11 Raisecom(config-stm- Configure the expected and sent HP overhead
port)#sdh overhead j1 trace J1 bytes.
[ vc4 vc4-number ]
{ expected string | By default, both the expected and sent HP
transmit string } * overhead trace J1 bytes are Raisecom-Opcom.

Raisecom Proprietary and Confidential

103
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 7 TDMoP

Step Command Description

12 Raisecom(config-stm- Configure the expected and sent Lower-order
port)#sdh overhead j2 Path (LP) overhead trace J2 bytes.
[ vc4 vc4-number ] [ vc12
vc12-number | tu12 tu12- By default, both the expected and sent LP
number ] { expected string overhead trace J2 bytes are Raisecom-Opcom.
| transmit string } *
13 Raisecom(config-stm- Configure the value of S1, K1, and K2 bytes
port)#sdh overhead s1 byte of the sent SDH signals.
[ k1 byte-1 ] [ k2 byte-
2 ] By default, the value of the sent K1 and K2
bytes is 0x0 and the value of the sent S1 byte
is oxf.

7.2.3 Configuring SDH sub-interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter STM sub-interface configuration mode.
stm unit/slot/port.subport
3 Raisecom(config-port)#tdm- Configure the line type of TDM services.
type { e1-unframed | e1-
framed | e1-crc-framed }
By default, the line type of TDM services is
unframed E1 mode.
4 Raisecom(config-port)#clk Configure the Tx clock source of TDM
tx-src { acr | dcr | services.
loopback }
By default, the Tx clock source of TDM
services is the system clock.
5 Raisecom(config-port)#rbit Configure the generation threshold and clear
{ engender | clear } threshold of the Rbit.
threshold threshold
By default, the generation threshold of the
Rbit is 100.
6 Raisecom(config- Configure the timeslot associated with the
port)#timeslot SDH sub-interface.
{ timeslot }

It is valid when the TDM service type is

framed mode. When the TDM service
type is unframed mode, the sub-
interface associates with all timeslots.

Raisecom Proprietary and Confidential

104
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 7 TDMoP

7.2.4 Checking configurations

No. Command Description
1 Raisecom(config-stm-port)#show interface stm Show configurations of the STM
unit/slot/port interface.
2 Raisecom(config-stm-port)#show statistic Show statistics on the 15-minute RS,
{ regenerator-section | multiplex-section | MS, HP, and LP.
higher-path vc4 vc4-number | lower-path vc4
vc4-number vc12 vc12-number } current
3 Raisecom(config-stm-port)#show interface stm Show configurations of the STM sub-
unit/slot/port.subport interface.

7.3 Configuring Tunnel

7.3.1 Preparing for configurations

Scenario
The Tunnel is the tunnel to carry the Pseudo Wire (PW) to traverse the Packet Switching
Network (PSN). Before configuring the PW, you must create the Tunnel.

Prerequisite
N/A

7.3.2 Configuring MPLS Tunnel

For steps about configuring the MPLS Tunnel, see chapter 11 VPN.

7.4 Configuring PW
7.4.1 Preparing for configurations

Scenario
After being received by the TDM interface, TDM service data flows are encapsulated into PW
packets. PW packets of the same type will form PW service flows and traverse the PSN. After
reaching the other end of the PSN, PW service flows are decapsulated to TDM service flows,
which are forwarded through the TDM interface.

Prerequisite
N/A

Raisecom Proprietary and Confidential

105
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 7 TDMoP

7.4.2 Configuring static L2VC

Configure the iTN880 as below:
 When the E1 services are in unframed mode, create L2VC on the interface.
 When the E1 services are in framed mode, create a sub-interface, associate the sub-
interface with timeslots, and then create L2VC.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface tdm Enter TDM interface configuration mode.
1/slot-id/interface-number
3 Raisecom(config-tdm-1/*/*)#tdm-type Configure the link type of TDM interface to E1
{ e1-unframed | e1-framed | e1-crc- framed mode.
framed }
By default, it is E1 unframed mode.
4 Raisecom(config-tdm-1/*/*)#interface Enter TDM sub-interface configuration mode.
tdm 1/slot-id/interface-number.sub-
interface-number

Execute this step only when the line type is E1

framed mode.
5 Raisecom(config-tdm- (Optional) configure the timeslot associated with the
1/*/*.*)#timeslot { timeslot } TDM sub-interface.

Execute this step only when the line type is E1

framed mode. When the line type is E1
unframed mode, the TDM sub-interface is
associated to all timeslots.
6 Raisecom(config-tdm-port)# mpls Configure the static L2VC by specifying the
static-l2vc destination ip-address incoming label and outgoing label.
vc-id vc-id in-label in-label out-
label out-label [ tunnel-policy
policy-name | tunnel tunnel-number ]
[ jitter-buffer buffer ] [ tdm-
encapsulation number ] [ rtp-
header ]

7.4.3 Configuring dynamic L2VC

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface tdm Enter TDM interface configuration mode.
1/slot-id/interface-number
3 Raisecom(config-tdm-1/*/*)#tdm-type Configure the link type of TDM interface to E1
{ e1-unframed | e1-framed | e1-crc- framed mode.
framed }
By default, it is E1 unframed mode.

Raisecom Proprietary and Confidential

106
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 7 TDMoP

Step Command Description

4 Raisecom(config-tdm-1/*/*)#interface Enter TDM sub-interface configuration mode.
tdm 1/slot-id/interface-number.sub-
interface-number

Execute this step only when the line type is

E1 framed mode.
5 Raisecom(config-tdm- (Optional) configure the timeslot associated with the
1/*/*.*)#timeslot { timeslot } TDM sub-interface.

Execute this step only when the line type is

E1 framed mode. When the line type is E1
unframed mode, the TDM sub-interface is
associated to all timeslots.
6 Raisecom(config-tdm-port)# mpls l2vc Configure the dynamic L2VC.
destination ip-address vc-id vc-id
[ tunnel-policy policy-name | tunnel
tunnel-number ] [ jitter-buffer
buffer ] [ tdm-encapsulation
number ] [ rtp-header ]

7.4.4 Checking configurations

No. Command Description
1 Raisecom#show mpls l2vc [ static ] [interface-type Show L2VPN status.
interface-number ]

7.5 Configuring TDMoP clock

7.5.1 Preparing for configurations

Scenario
The TDMoP system supports clock synchronization in nature. The PTN is an STDM-based
best-effort network. It may cause end-to-end delay. TDM services are encapsulated into
Ethernet packets and then are transmitted cross the PTN. This also influences the performance
for de-encapsulating TDM services. However, TDMoP clock recovery technology can reduce
impact caused by PTN delay.
The clock recovery mechanism adopted by the TDMoP system depends on the Rx clock
source of the TDM interface.

Raisecom Proprietary and Confidential

107
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 7 TDMoP

Prerequisite
Create a PW.

7.5.2 Configuring Tx clock source of TDM interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface tdm Enter TDM interface configuration mode.
1/slot-id/interface-number
3 Raisecom(config-tdm-1/*/*)#clk tx- Configure the clock source of a TDM interface.
src { acr| dcr | loopback }
By default, it is system clock.

7.5.3 Configuring sub-interface of adaptive recovery clock

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface tdm Enter TDM interface configuration mode.
1/slot-id/interface-number.sub-
interface-number
3 Raisecom(config-tdm-1/*/*.*)#clk acr Configure the sub-interface of the adaptive recovery
clock.

7.5.4 Checking configurations

No. Command Description
1 Raisecom(config)#show interface tdm Show clock configurations of the current
{ 1/slot-id/interface-number | 1/slot- TDM interface.
id/interface-number.sub-interface-number }

7.6 Maintenance
Command Description
Raisecom(config-tdm- Configure the loopback mode of TDM interfaces.
port)#loopback
{ internal | By default, there is no loopback on the TDM interface.
external | You can use the no loopback command to configure the TDM interface not to
bidirectional } perform loopback.

Raisecom Proprietary and Confidential

108
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 8 IP services

8 IP services

This chapter describes principles and configuration procedures of IP services, as well as

related configuration examples, including following sections:
 Configuring interface
 Configuring fault detection
 Configuring ARP
 Configuring DHCP v4 Relay
 Configuring DHCP v4 Server
 Maintenance
 Configuration examples

8.1 Configuring interface

8.1.1 Preparing for configurations

Scenario
Configure interface information, such as the IP address and the MTU.

Prerequisite
N/A

8.1.2 Configuring interface information

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
3 Raisecom(config-port)#ip address ip-address Configure the IP address of the interface.
[ ip-mask ] [ sub ]
Raisecom(config-port)#ipv6 address ip-
address/prefix-length [ eui-64 ]

Raisecom Proprietary and Confidential

109
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 8 IP services

Step Command Description

4 Raisecom(config-port)#ip address unnumbered (Optional) configure the interface to
interface-type interface-number borrow the IP address of other interfaces.
5 Raisecom(config-port)#mtu max-frame-length Configure the MTU of the interface.

8.1.3 Checking configurations

No. Command Description
1 Raisecom#show interface interface-type interface- Show interface information.
number
2 Raisecom#show ipv6 interface brief [ interface- Show address information about the
type interface-number ] IPv6 interface.

8.2 Configuring fault detection

8.2.1 Configuring task scheduling
When you need to use some commands to perform periodical maintenance on the iTN8800,
you can configure task scheduling. The iTN8800 supports implementing task scheduling
through the schedule list and CLI. You can use commands to perform periodical operation just
by specifying the begin time, period, and end time of a specified task in the schedule list and
bind the schedule list to the CLI.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#schedule-list list-number start Create and configure the schedule
date-time mm-dd-yyyy hh:mm:ss list.
Raisecom(config)#schedule-list list-number start
date-time mm-dd-yyyy hh:mm:ss every { day | week }
stop mm-dd-yyyy hh:mm:ss

Raisecom(config)#schedule-list list-number start

date-time mm-dd-yyyy hh:mm:ss every days-interval
time-interval [ stop mm-dd-yyyy hh:mm:ss ]

Raisecom(config)#schedule-list list-number start

up–time days-after-startup hh:mm:ss

Raisecom(config)#schedule-list list-number start

up–time days-after-startup hh:mm:ss every days-
interval time-interval [ stop days-after-startup
hh:mm:ss ]
3 Raisecom#show schedule-list Show schedule list configurations.

Raisecom Proprietary and Confidential

110
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 8 IP services

8.2.2 PING
Step Command Description
1 Raisecom#ping ip-address [ count count ] (Optional) use the ping command to test
[ size size ] [ waittime period ] [ source- IPv4 network connectivity.
ip ip-address ] [ df-bit ]

The iTN8800 cannot perform other operations in the process of Ping. It can perform
other operations only when Ping is complete or Ping is broken off by pressing Ctrl+C.

8.2.3 Traceroute
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter Layer 3 interface configuration mode.
interface-number
3 Raisecom(config-port)#ip address ip- Configure the IP address of the interface.
address [ ip-mask ]
4 Raisecom(config-port)#exit Exit Layer 3 interface configuration mode and
enter global configuration mode.
5 Raisecom(config)#exit Exit global configuration mode and enter
privileged EXEC mode.
6 Raisecom#traceroute ip-address [ firstttl (Optional) use the traceroute command to
first-ttl ] [ maxttl max-ttl ] [ port test the IPv4 network connectivity and view
port-number ] [ waittime period ] [ count nodes passed by the packet.
times ] [ size size ]
By default, the initial TTL is 1; the maximum
TTL is 30; the interface ID is 33433; the
timeout is 3s; the number of detection packets
is 3.

8.3 Configuring ARP

8.3.1 Preparing for configurations

Scenario
Address Resolution Protocol (ARP) is a protocol used for resolution of IP addresses into
Ethernet MAC addresses (physical addresses).

Raisecom Proprietary and Confidential

111
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 8 IP services

Prerequisite
Configure the IP address of the interface. For details, see section 8.1 Configuring interface.

8.3.2 Configuring ARP

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#arp mode { learn-all | Configure ARP learning mode.
learn-reply-only }
By default, it is learn-all.
3 Raisecom(config)#arp aging-time time (Optional) configure the aging time of dynamic
ARP entries.
By default, it is 1200s.
4 Raisecom(config)#arp active-ack enable Enable ARP active acknowledgement.
By default, it is disabled.
5 Raisecom(config)#arp ip-address mac- (Optional) configure the static ARP entry.
address [ vrf vrf-name | vid vlan-id ]
Raisecom(config)#arp ip-address mac-
address [ vrf vrf-name ] vid vlan-id
[ cevid vlan-id ] [ interface
interface-type interface-number ]
6 Raisecom(config)#interface interface- Enter Layer 3 interface configuration mode.
type interface-number
7 Raisecom(config-port)#arp learning Enable dynamic ARP learning on Layer 3
enable interface.
By default, it is enabled.
8 Raisecom(config-port)#arp max-learning- Configure the maximum number of dynamically-
num number learned ARP entries on Layer 3 interface.

9 Raisecom(config-port)#arp proxy enable Enable ARP proxy on the interface.

By default, it is disabled.
10 Raisecom(config-port)#gratuitous-arp- Configure gratuitous ARP learning on the
learning {enable | disable } interface.
By default, it is enabled.

8.3.3 Configuring proxy ARP

As shown in Figure 8-1, the PE device is configured with interface isolation. R1 and R2
cannot communicate directly. Proxy ARP is enabled on the PE device. When R1 sends an
ARP request to R2, the PE sends an ARP reply packet carrying its own MAC address and the
IP address R2 in place of R2 to R1.

Raisecom Proprietary and Confidential

112
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 8 IP services

Figure 8-1 Application scenario of Proxy ARP

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#arp proxy enable Enable ARP proxy on the interface.
By default, it is disabled.

8.3.4 Configuring proxy ARP/NDP for PW

The ARP for PW is applied to the mobile carrier network. As shown in Figure 8-2, when the
base station requests the ARP of the core gateway G1, the ARP request and response packets
are transmitted through the L2VPN link between them, so that ARP learning is finished.
The ARP packet is sent by the PE and ARP requests are sent to the peer PE device through the
primary PW and then the peer PE sends the ARP request packets to the core gateway. After
receiving the request packet, the core gateway performs local learning and sends response
packets to the source end. The response packets are sent to the source PE1 through the
primary PW, and then sent to the base station which learns the gateway ARP.

Raisecom Proprietary and Confidential

113
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 8 IP services

Figure 8-2 Application scenario of proxy ARP/DNP for PW

The principle of Neighbor Discovery Protocol (NDP) for PW is the same.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface gigaethernet Enter interface configuration mode.
interface-name interface-number
3 Raisecom(config-port)#pw-proxy { enable Enable proxy ARP, namely, proxy ARP for PW
| disable } or proxy NDP for PW on the AC-side interface.

8.3.5 Checking configurations

No. Command Description
1 Raisecom#show arp [ vrf vrf-name ] [ ip-address Show information about ARP.
| interface interface-type interface-number |
static | [ vid vlan-id ] [ cevid vlan-id ] ]
2 Raisecom#show arp learning info Show ARP learning status on the
interface.
3 Raisecom#show arp summary [ all | vrf vrf-name ] Show ARP summary.

Raisecom Proprietary and Confidential

114
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 8 IP services

8.4 Configuring DHCP v4 Relay

8.4.1 Preparing for configurations

Scenario
When the iTN8800 works as the DHCP v4 Relay, the DHCP v4 clients can communicate with
DHCP v4 servers in other network segments through the DHCP v4 Relay to obtain IP
addresses. Therefore, DHCP v4 clients in different network segments can apply for IP
addresses from a DHCP v4 server. This facilitates saving costs and managing all devices
together.

Prerequisite
The iTN8800 is disabled with DHCP v4 Client or DHCP v4 Server.

8.4.2 Configuring DHCP v4 Relay

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)#ip dhcp Enable DHCP v4 Relay on the interface.
relay
By default, it is disabled.

Before enabling DHCP v4 Relay on the interface, ensure that the Layer 3 interface is
not configured by the portswitch command or is not configured to work in mode l2
mode.

8.4.3 Configuring destination IP address of DHCP v4 Relay

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#ip dhcp relay Configure the IP address of the DHCP v4
target-ip ip-address Relay.

Raisecom Proprietary and Confidential

115
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 8 IP services

8.4.4 Checking configurations

No. Command Description
1 Raisecom#show ip dhcp relay Show configurations of DHCP v4 Relay.

8.5 Configuring DHCP v4 Server

8.5.1 Preparing for configurations

Scenario
When the iTN8800 works as the DHCP v4 server, the DHCP v4 client can obtain the IP
address from the iTN8800.

Prerequisite
The iTN8800 is not enabled with DHCP v4 Client. In addition, the DHCP v4 server works in
common DHCP v4 server mode.

8.5.2 Creating and configuring IPv4 address pool

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip dhcp server pool Create the IPv4 address pool and enter address
pool-name pool configuration mode.
3 Raisecom(config-pool)#address start-ip- Configure the range of the IPv4 address pool.
address end-ip-address mask { mask |
mask-length }
4 Raisecom(config-pool)#lease expired Configure the lease of the IPv4 address pool.
{ minute | infinite }
5 Raisecom(config-pool)#dns-server ip- Configure the DNS of the IPv4 address pool.
address [ secondary ]
6 Raisecom(config-pool)#gateway ip-address Configure the default gateway of the IPv4
address pool.
7 Raisecom(config-pool)#option 60 vendor- Configure information carried by Option 60.
string
8 Raisecom(config-pool)#tftp-server ip- Configure the TFTP server of the IPv4 address
address pool.
9 Raisecom(config-pool)#trap server-ip ip- Configure the Trap server of the IPv4 address
address pool.

Raisecom Proprietary and Confidential

116
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 8 IP services

8.5.3 Configuring DHCP v4 Server on interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#ip dhcp server Enable DHCP v4 Server.

8.5.4 Checking configurations

No. Command Description
1 Raisecom(config)#show ip dhcp server Show DHCP server configurations.
2 Raisecom(config)#show ip dhcp server lease Show assigned IPv4 addresses and client
information.
3 Raisecom(config)#show ip dhcp server Show packet statistics of the DHCP v4
statistics server.
4 Raisecom(config)#show ip dhcp static-bind Show DHCP v4 static lease information.

8.5.5 Checking configurations

No. Command Description
1 Raisecom#show interface interface-type Show interface information.
interface-number

8.6 Maintenance
Command Description
Raisecom(config)#clear arp [ all | vrf vrf-name ] [ ip-address | Clearing ARP
interface interface-type interface-number | [ vid vlan-id ] [ cevid entries.
vlan-id ] ]

Raisecom Proprietary and Confidential

117
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 8 IP services

8.7 Configuration examples

8.7.1 Example for configuring DHCP v4 Relay

Networking requirements
As shown in Figure 8-3, the iTN8800 works as the DHCP v4 Relay with the host name being
set to raisecom. The iTN8800 accesses to the DHCP v4 server and the NView NNM system
through the service interface. The DHCP v4 server assigns an IP address to the iTN8800.
Therefore, the NView NNM system can discover and manage the iTN8800.

Figure 8-3 Configuring DHCP v4 Relay

Configuration steps
Step 1 Enable interface DHCP.

Raisecom#config
Raisecom(config)#interface gigaethernet 1/4/1
Raisecom(config-gigaethernet1/4/1)#ip dhcp relay
Raisecom(config-gigaethernet1/4/1)#interface gigaethernet 1/1/2
Raisecom(config-gigaethernet1/4/2)#ip dhcp relay
Raisecom(config-gigaethernet1/4/2)#exit

Step 2 Configure the destination IP address of the DHCP v4 Relay.

Raisecom(config)#interface gigaethernet 1/4/1

Raisecom(config-gigaethernet1/4/1)#ip dhcp relay target-ip 10.0.0.1

Raisecom Proprietary and Confidential

118
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 8 IP services

Checking results
Use the show ip dhcp relay command to show DHCP v4 Relay configurations.

Raisecom#show ip dhcp relay

Interface Status Target Address
-----------------------------------------------------------
gigaethernet1/4/1 Enable 10.0.0.1
gigaethernet1/4/2 Enable --

8.7.2 Example for configuring DHCP v4 Server

Networking requirements
As shown in Figure 8-4, the iTN8800 works as the DHCP v4 Server for assigning IP address
to DHCP v4 clients. Parameters are configured as below:
 Lease time: 8 hours
 Name of IP address pool: pool
 IP address range: 172.31.1.2–172.31.1.100
 IP address of the DNS: 172.31.100.1

Figure 8-4 Configuring DHCP v4 server

Configuration steps
Step 1 Create and configure the IP address pool.

Raisecom#config
Raisecom(config)#ip dhcp server pool pool
Raisecom(config-pool)#address 172.31.1.2 172.31.1.100 mask 24
Raisecom(config-pool)#lease expired 480

Raisecom Proprietary and Confidential

119
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 8 IP services

Raisecom(config-pool)#dns-server 172.31.100.1
Raisecom(config-pool)#exit

Step 2 Configure DHCP Server on the interface.

Raisecom(config)#interface gigaethernet 1/3/1

Raisecom(config-gigaethernet1/3/1)#ip dhcp server
Raisecom(config-gigaethernet1/3/1)#ip address 172.31.1.1

Checking results
Use the show ip dhcp server command to show configurations of DHCP v4 Server.

Raisecom#show ip dhcp server

Interface Status
------------------------------
gigaethernet 1/3/1 Enable

Use the show ip server pool command to show configurations of the IP address pool of the
DHCP v4 server.

Raisecom#show ip server pool

Pool name Pool type
----------------------------------------
pool dhcp
Pools count: 1

Raisecom Proprietary and Confidential

120
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

9 IP routing

This chapter describes principles and configuration procedures of IP routing, including

following sections:
 Configuring routing management
 Configuring static route
 Configuring routing policy
 Configuring OSPFv2
 Configuring ISIS
 Configuring BGP
 Configuring RIP

9.1 Configuring routing management

9.1.1 Configuring routing management
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router id router-id Configure the Router ID.
By default, the Router ID is 192.168.1.1.
3 Raisecom(config)#route recursive- Configure the route for the public network to transmit
lookup tunnel [ ip-prefix unlabeled packets to be recursive to the LSP tunnel.
listname ]

9.1.2 Configuring IP FRR

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip frr route-map map-name Configure IP FRR.
[ wtr-timer timer ]

Raisecom Proprietary and Confidential

121
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

9.1.3 Configuring BFD

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip route ip-address mask- Configure the static route to be bound with
address { next-hop | NULL 0 | interface-type the BFD session, thus implementing fast
interface-num } [ distance distance ] response to faults and route switching
[ description text ] [ tag tag ] [ track through BFD.
bfd-session bfd-session-id ]

9.1.4 Checking configurations

No. Command Description
1 Raisecom#show router id Show the Router ID.
2 Raisecom#show ip route [ all | vrf vrf-name ] Show the routing table.
[ protocol { static | connected | bgp | ospf |
isis | rip } ] [ detail ]
Raisecom#show ipv6 route [ vrf vrf-name ]
[ protocol { static | connected | bgp | ospf |
isis | rip } ] [ detail ]
3 Raisecom#show ip route [ vrf vrf-name ] ip- Show the route between 2 IP
address1 [ mask-address1 ] ip-address2 [ mask- addresses.
address2 ] [ detail ]
4 Raisecom#show { ip | ipv6 } route [ vrf vrf- Show route statistics.
name ] summary

9.2 Configuring static route

9.2.1 Preparing for configurations

Scenario
The static route has the following advantages:
 Consume less time for the CPU to process them.
 Facilitate the administrator to learn the route.
 Be configured easily.
However, when configuring the static route, you need to consider the whole network. If the
network structure is changed, you need to modify the routing table manually. Once the
network scale is enlarged, it will consume lots of time to configure and maintain the network.
In addition, it may cause more errors.
The default route is a specific static route. It will be used when no matched route is found in
the routing table.

Raisecom Proprietary and Confidential

122
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Prerequisite
N/A

9.2.2 Configuring static route

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip route [ vrf vrf-name ] ip- Configure IPv4 static route.
address { mask-address | /mask-length } { next-
hop [ interface-type interface-num ] | NULL 0 |
tunnel tunnel-if-num } * [ distance distance ]
[ description text ] [ tag tag ]
Raisecom(config)#ipv6 route [ vrf vrf-name ] Configure IPv6 static route.
ipv6-address/prefix-length { ipv6-address | NULL
0 } [ distance distance ] [ description text ]
3 Raisecom(config)#ip route static distance (Optional) configure the default
distance administrative distance of IPv4 static
route.
By default, it is 1.
Raisecom(config)#ipv6 route static distance (Optional) configure the default
distance administrative distance of IPv6 static
route.
By default, it is 1.

9.2.3 Checking configurations

Step Command Description
1 Raisecom#show ip route [ all | vrf vrf-name ] [ protocol Show information
{ static | connected | bgp | ospf | isis | rip } ] about the routing
[ detail ] table.
Raisecom#show ipv6 route [ vrf vrf-name ] [ protocol
{ static | connected | bgp | ospf | isis | rip } ]
[ detail ]
2 Raisecom#show ip route [ vrf vrf-name ] ip-address [ mask- Show information
address ] [ longer-prefixes ] about the route for a
Raisecom#show ipv6 route { ipv6-address | ipv6- certain destination.
address/prefix-length }
3 Raisecom#show { ip | ipv6 } route [ vrf vrf-name ] summary Show route statistics.

Raisecom Proprietary and Confidential

123
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

9.3 Configuring routing policy

9.3.1 Configuring IP prefix-list
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip prefix-list prefix- Create an IP prefix-list or add a node to the IP
name [ seq seq-number ] { deny | permit } prefix-list.
any
Raisecom(config)#ip prefix-list prefix-
If no prefix-list ID (seq-number) is
name [ seq seq-number ] { deny | permit }
configured, the system will generate a prefix-
ip-address/mask [ ge min-length ] [ le
list ID automatically. The generated pre-fix
max-length ] list ID has 5 digits.
3 Raisecom(config)#ip prefix-list prefix- Configure descriptions of the IP prefix-list.
name description string
If the length of descriptions exceeds 80
characters, the first 80 characters are
available.

 If one record is in permit type, all mismatched routes are in deny type by default.
Only matched routes can pass filtering of the IP prefix-list.
 If one record is in deny type, all mismatched routes are in deny type by default.
Even matched routes cannot pass filtering of the IP prefix-list. Therefore, you need
to add a permit record after multiple deny records to allow other routes to pass.
 If there are multiple records in the IP prefix-list, there must be a record in permit
type.

9.3.2 Configuring route mapping table

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip as-path access-list (Optional) configure the filter that is based on
access-list-number { permit | deny } AS path of the BGP route.
regexp
3 Raisecom(config)#ip community-list (Optional) configure the filter that is based on
{ standard-list-number | standard standard or advanced community properties of
standard-list-name }{ permit | deny } the BGP route.
community-number [ internet ] [ local-
as ] [ no-advertise ] [ no-export ]
Raisecom(config)#ip community-list
{ expanded-list-number | expanded
expanded-list-name } { permit | deny }
regexp
4 Raisecom(config)#ip extcommunity-list (Optional) configure the filter that is based on
{ standard-list-number | standard standard community properties of the BGP
standard-list-name }{ permit | deny } rt route.
rout-target-number

Raisecom Proprietary and Confidential

124
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

5 Raisecom(config)#ip rd-filter rd-filter- (Optional) configure the filter that is based on
number { permit | deny } rd rd -number RD property of the BGP route.
6 Raisecom(config)#route-map map-name Create the route mapping table and enter route
{ permit | deny } number mapping configuration mode.
7 Raisecom(config-route-map)#description Configure descriptions of the route mapping
string table. If there is any space in descriptions,
descriptions should be within quotes.
8 Raisecom(config-route-map)#on-match next Configure the on-match sub-clause to
continuing to match at the next node.
By default, the process is finished after
matching.
9 Raisecom(config-route-map)#on-match goto Configure the on-match sub-clause to
number continuing to match at some node.
By default, the process is finished after
matching.
10 Raisecom(config-route-map)#call map-name Continue to match routes by scheduling other
routing table after matching the route.
By default, the process is finished after
matching.
11 Raisecom(config-route-map)#match ip next- Configure the match sub-clause to matching
hop acl-number the next hop based on extended IP ACL.
12 Raisecom(config-route-map)#match ip next- Configure the match sub-clause to matching
hop prefix-list prefix-name the next hop based on IP prefix-list.
13 Raisecom(config-route-map)#match ip Configure the match sub-clause to matching
address acl-number the IP address based on extended IP ACL.
14 Raisecom(config-route-map)#match ip Configure the match sub-clause to matching
address prefix-list prefix-name the IP address based on IP prefix-list.
15 Raisecom(config-route-map)#match Configure the match sub-clause to matching
interface name the interface name.
16 Raisecom(config-route-map)#match metric Configure the match sub-clause to the
metric matching rule that is based on route metric
value.
17 Raisecom(config-route-map)#match tag tag Configure the match sub-clause to the
matching rule that is based on Tag field of the
route tagging.
18 Raisecom(config-route-map)#match as-path Configure the match sub-clause to the BGP
path-list-number routing information matching rule that is
based on AS-Path filter.
19 Raisecom(config-route-map)#match Configure the match sub-clause to the BGP
community { community-list-number | routing information matching rule that is
community-list-name } [ exact-match ] based on community filter.

Raisecom Proprietary and Confidential

125
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

20 Raisecom(config-route-map)#extcommunity Configure the match sub-clause to the BGP
{ extcommunity-list-number | routing information matching rule that is
extcommunity-list-name } based on extcommunity filter.
21 Raisecom(config-route-map)#match ip Configure the match sub-clause to the BGP
route-source prefix-list prefix-name routing information matching rule that is
based on prefix-list matching with source
address of the route.
22 Raisecom(config-route-map)# match rd- Configure the match sub-clause to the BGP
filter rd-filter-number routing information matching rule that is
based on RD property filter.
23 Raisecom(config-route-map)#set metric [ + Configure the set sub-clause to modifying the
| - ] metric route metric value after matching.
24 Raisecom(config-route-map)#set metric- Configure the set sub-clause to modifying the
type { type-1 | type-2 } route metric type after matching.
25 Raisecom(config-route-map)#set src ip- Configure the set sub-clause to modifying the
address source IP address after matching.
26 Raisecom(config-route-map)#set ip next- Configure the set sub-clause to modifying the
hop ip-address next-hop IP address of the route after
matching.
27 Raisecom(config-route-map)#set tag tag Configure the set sub-clause to modifying the
routing information tag after matching.
28 Raisecom(config-route-map)#set origin Configure the set sub-clause to modifying the
{ egp as-number | igp | incomplete } route source of the BGP routing information
that matches with the routing policy.
29 Raisecom(config-route-map)#set as-path Configure the set sub-clause to modifying the
prepend as-number as-path property of the BGP routing
information that matches with the routing
policy.
30 Raisecom(config-route-map)#set local- Configure the set sub-clause to modifying the
preference preference local priority of the BGP routing information
that matches with the routing policy.
31 Raisecom(config-route-map)#set community Configure the set sub-clause to setting or
{ community-number | internet | local-as deleting the community property of the BGP
| no-advertise | no-export } * routing information that matches with the
[ additive ] routing policy.
Raisecom(config-route-map)# set community
none
32 Raisecom(config-route-map)#set comm-list Configure the set sub-clause to deleting the
{ community-list-number | community-list- community property of the BGP routing
name }delete information that matches with the routing
policy.

Raisecom Proprietary and Confidential

126
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

33 Raisecom(config-route-map)#set Configure the set sub-clause to adding or
extcommunity rt route-target-number modifying the community property of the
[ additive ] BGP routing information that matches with
the routing policy.

9.3.3 Checking configurations

No. Command Description
1 Raisecom#show ip as-path access-list Show filtering information about the AS-path
access-list-number list.

9.4 Configuring OSPFv2

OSPF runs on L3 interfaces. By default, the interface is in routed mode. If the current
interface is configured to the switch mode, you have to use the no portswitch
command to return the interface to the routed mode.

9.4.1 Configuring OSPF basic functions

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Enable an OSPF process and enter OSPF
[ vrf vrf-name ] [ router-id router-id ] configuration mode.
3 Raisecom(config-router-ospf)#network ip- Configure network segments included in the
address wild-card-mask area area-id OSPF area.

 If you manually configure the router-id parameter through the optional parameters
in the router ospf process-id [ router-id router-id ] command, the OSPF process
will select the router-id parameter first. Otherwise, the parameter is selected
automatically.
 If the OSPF process is configured or selects the router-id parameter, after being
modified, the router-id parameter takes effect after the OSPF process is rebooted.

Raisecom Proprietary and Confidential

127
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

9.4.2 Configuring OSPF route properties

Configuring OSPF cost value of interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter Layer 3 interface configuration mode.
interface-number
3 Raisecom(config-port)#ip ospf cost cost Configure the OSPF cost of the IP interface.

Configuring bandwidth reference value

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Enable an OSPF process and enter OSPF
[ router-id router-id ] configuration mode.
3 Raisecom(config-router-ospf)#reference- Configure the bandwidth reference value of
bandwidth bandwidth the link.

 After the routing cost is manually configured through the ip ospf cost command,
the manually-configured routing cost takes effect.
 If the routing cost is not configured manually but the link bandwidth reference
value is configured, the routing cost is automatically configured based on link
bandwidth reference value. The formula is: cost = link bandwidth reference value
(bit/s) / link bandwidth. If the cost value is greater than 65535, it is configured to
65535. If no link bandwidth reference value is configured, it is configured to 100
Mbit/s by default.

9.4.3 Configuring OSPF administrative distance

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Enable an OSPF process and enter OSPF
[ router-id router-id ] configuration mode.
3 Raisecom(config-router-ospf)#distance Configure the OSPF administrative
administrative-distance distance.
By default, it is 110.

Raisecom Proprietary and Confidential

128
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

4 Raisecom(config-router-ospf)#distance ospf Configure the administrative distance of
{ intra-area | inter-area | external } OSPF specified route.
distance
By default, it is 0. However, it takes 110 as
the standard.

9.4.4 Configuring device to be compatible with RFC1583

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Start an OSPF process and enter OSPF
[ router-id router-id ] configuration mode.
3 Raisecom(config-router-ospf)#compatible Configure the OSPF to be compatible with
rfc1583 RFC1583.
By default, the OSPF is compatible with
RFC1583.

9.4.5 Configuring load balancing

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Start an OSPF process and enter OSPF
[ router-id router-id ] configuration mode.
3 Raisecom(config-router-ospf)#maximum load- Configure the maximum number of IP
balancing number equal-cost multi-path load balancing.

9.4.6 Maximizing LSA metric

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Start an OSPF process and enter OSPF
[ router-id router-id ] configuration mode.
3 Raisecom(config-router-ospf)#max-metric Enable maximum metric of OSPF LSA
router-lsa [ include-stub ] [ on-startup packets. The metric of LSA packet in the
time ] corresponding area will be automatically
configured to 0xFFFF.
By default, it is disabled.

Raisecom Proprietary and Confidential

129
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

9.4.7 Configuring OSPF network

Configuring OSPF network type

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#ip ospf network Configuring the network type of the Layer 3
{ broadcast | non-broadcast | ptmp | interface.
ptp }
By default, it is the broadcast network.

Configuring DR election priority

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#ip ospf priority Configure the DR election priority on the IP
priority interface.
By default, it is 1.

Configuring OSPF NBMA network neighbor

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
3 Raisecom(config-port)#ip ospf network non- Configure the Layer 3 interface network
broadcast mode to NBMA and exit Layer 3
Raisecom(config-port)#exit interface configuration mode.
4 Raisecom(config)#router ospf process-id Enable an OSPF process and enter
[ router-id router-id ] OSPF configuration mode.
5 Raisecom(config-router-ospf)#neighbor ip- Configure the NBMA neighbor and its
address [ priority priority ] priority.
By default, no NBMA neighbor is
configured and the priority is 0 when
you configure the NBMA neighbor.

Raisecom Proprietary and Confidential

130
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Priorities configured by the neighbour and ip ospf priority priority commands are
different:
 The priority configured by the neighbor command indicates that whether the
neighbor has the right to vote. If you set the priority to 0 when configuring the
neighbor, the local router believes that the neighbor has no right to vote and will
not sent Hello packets to the neighbor. This method helps reduce the number of
Hello packets transmitted through the network during DR and BDR election
processes. However, if the local router is a DR or BDR, it will send the Hello
packet to the neighbor, whose priority is configured to 0, to establish the
neighboring relationship.
 The priority configured by the ip ospf priority priority command is used for actual
DR election.

Configuring OSPF NSSA area

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Start an OSPF process and enter the OSPF
[ router-id router-id ] configuration mode.
3 Raisecom(config-router-ospf)#area area-id Configure the area to be NSSA area. Only
nssa [ no-summary ] non-backbone area can be NSSA area.
By default, the non-backbone areas are all
common areas.

9.4.8 Optimizing OSPF network

Configuring OSPF packet timer

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-
number
3 Raisecom(config-port)#ip Configure the OSPF neighbor dead interval.
ospf dead-interval seconds
By default, it is 4 times of Hello packet delivery interval. If no
Hello packet delivery interval is configured, it is 40s for P2P and
Broadcast interfaces and 120s for P2MP and NBMA interfaces by
default.
4 Raisecom(config-port)#ip Configure the ODPF Hello packet delivery interval.
ospf hello-interval
seconds By default, it is 10s for P2P and Broadcast interfaces and 30s for
P2MP and NBMA interfaces
5 Raisecom(config-port)#ip Configure the OSPF Poll timer interval.
ospf poll-interval seconds
By default, it is 120s.

Raisecom Proprietary and Confidential

131
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

6 Raisecom(config-port)#ip Configure the LAS retransmission interval on the IP interface.
ospf retransmit-interval
seconds By default, it is 5s.
7 Raisecom(config-port)#ip Configure the LSA retransmission delay on the IP interface.
ospf transmit-delay
seconds By default, it is 1s.

 When the dead-interval is not manually configured, after hello-interval is

configured, dead-interval and poll-interval is changed to 4 times of hello-interval.
 When the dead-interval is manually configured, after hello-interval is configured,
no effect is brought to the dead-interval and poll-interval. No matter whether you
configure the poll interval or not, the poll-interval changes with the dead-interval.
Therefore, we recommend configure these 3 values in the following order: hello-
interval, dead-interval, and poll-interval.

Configuring SPF calculation interval

When the OSPF Link State Database (LSDB) changes, it needs to re-calculate the shortest
path. If the network changes frequently and it needs to calculate the shortest path immediately,
it will occupy a great amount of system resources and affect efficiency of the router. By
adjusting the SPF calculation interval, you can prevent some effects brought by frequent
network changes.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Enable an OSPF process and enter OSPF
[ router-id router-id ] configuration mode.
3 Raisecom(config-router-ospf)#timers spf Configure the calculation delay and
delay-time hold-time interval of the OSPF route.
By default, the calculation delay is 2s and
the calculation interval is 3s.

Configuring OSPF passive interface

To make some OSPF routing information not obtained by some router on the network, you
can set the interface to an OSFP passive interface to disable the interface to send OSPF
packets.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-number

Raisecom Proprietary and Confidential

132
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

3 Raisecom(config-port)#ip ospf Enable passive interface on the OSPF interface.
passive-interface enable
By default, it is disabled.

Configuring MTU ignorance

By default, the value of MTU domain in the packet is the MTU value of the interface, which
sends the packet. Default MTU values may vary on devices. In addition, if the MTU value of
the packet is greater than the one of the interface, the packet will be discarded. To ensure
receiving the packet properly, enable MTU ignorance to set the MTU value to 0. Therefore,
all devices can receive the packet.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)#ip ospf Enable MTU ignorance on the IP interface.
mtu-ignore enable
By default, MTU ignorance is disabled on the IP
interface to check MTU of the OSPF Hello packet.

9.4.9 Configuring OSPF authentication mode

Configuring OSPF area authentication mode

All routers in an area need to be configured with the identical area authentication mode (non-
authentication, simple authentication, or MD5 authentication). The OSPF area has no
authentication password but adopts the interface authentication password. If no interface
authentication password is configured, the empty password will be used for authentication.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Enable an OSPF process and enter OSPF
[ router-id router-id ] configuration mode.
3 Raisecom(config-router-ospf)#area area-id Configure the area authentication mode.
authentication { md5 | simple }
By default, it is non-authentication.

Configuring OSPF interface authentication mode

Packet authentication prioritizes selecting the interface authentication mode. If the interface
authentication mode is configured to non-authentication mode, the area authentication mode
will be selected. OSPF interfaces cannot establish the neighbor relationship unless the
authentication mode and authentication password are identical.

Raisecom Proprietary and Confidential

133
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
3 Raisecom(config-port)#ip ospf authentication Configure the authentication mode of the
{ md5 | simple } IP interface.
By default, it is non-authentication. It
means adopting the area authentication
mode.
4 Raisecom(config-port)#ip ospf Configure the authentication password of
authentication-key { simple [ 0 | 7 ] the IP interface.
password | md5 { [ key-id [ 0 | 7 ]
password ] | keychain keychain-name } }

9.4.10 Configuring Stub area

For the non-backbone area at the edge of Autonomous System (AS), you can configure the
stub command on all routers in the area to configure the area to a Stub area. In this case,
Type5 LSA, which is used to describe external routes of the AS, cannot be flooded in the Stub
area. This facilitates reducing the routing table size.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router Enable an OSPF process and enter OSPF configuration mode.
ospf process-id [ router-
id router-id ]
3 Raisecom(config-router- Configure the area to a Stub area.
ospf)#area area-id stub
[ no-summary ] The no-summary parameter is used to disable the ABR to send
Summary LSA to the Stub area. It means that it is a Totally Stub
area and the ABR is available for the Stub only.
By default, no area is the Stub area.
4 Raisecom(config-router- Configure the default route cost of the Stub area.
ospf)#area area-id
default-cost cost
This command is available for the ABR in the Stub area only.
By default, it is 1.

 All routers in the Stub area must be configured with the Stub property through the
area area-id stub command.
 To set an area to a Totally Stub area, all routers in the area must be configured by
the area area-id stub command. In addition, all ABRs in the area must be
configured by the area area-id stub no-summary command.
 The backbone area cannot be set to the Stub area.
 ASBR should not be in the Stub area. It means that routers besides the AS cannot
be transmitted in the Stub area.
Raisecom Proprietary and Confidential
134
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

9.4.11 Controlling OSPF routing information

Configuring OSPF redistributed routes

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Enable an OSPF process and enter OSPF
[ router-id router-id ] configuration mode.
3 Raisecom(config-router- Configure OSPF route redistribution polity.
ospf)#redistribute { static | connected
| rip | isis | ospf | bgp } [ metric By default, no external route is redistributed.
metric ] [ metric-type { 1 | 2 ) ] When an external route is redistributed:
[ tag tag-value ] [ route-map map-  When the directly-connected and static route is
name ] redistributed, the metric is 1 by default. When
Raisecom(config-router- other routes are redistributed, take the original
ospf)#redistribute ospf [ process-id ] metric of the external route as the metric of the
[ vrf vrf-name ] [ metric metric ] LSA.
[ metric-type { 1 | 2 ] [ tag tag-  If no Metric-type is specified, the Metric-type

value ] [ route-map map-name ] is Type2 by default.

 If no Tag is specified, take the original Tag of

the external route as the Tag of the LSA.

4 Raisecom(config-router- Configure the threshold of redistributed OSPF
ospf)#redistribute limit limit-number external routes.
By default, no threshold is configured.

Configuring inter-area route aggregation

If there are sequent network segments in the area, you can configure route aggregation on the
ABR to aggregate these network segments to a network segment. When sending routing
information, the ABR generates Type3 LSA by taking the network segment as the unit.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process- Enable an OSPF process and enter OSPF
id [ router-id router-id ] configuration mode.
3 Raisecom(config-router-ospf)#area Configure the inter-area route aggregation.
area-id range ip-address ip-mask
[ not-advertise ]
By default, no inter-area route aggregation is
configured. When you configure the aggregated
route, the cost is the maximum Metric of the LSA by
default. In addition, the aggregated route is
redistributed.

Raisecom Proprietary and Confidential

135
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Aggregating redistributed external routes

After the external route is redistributed, configure route aggregation on the ASBR. The
iTN8800 just puts the aggregated route on the ASE LSA. This helps reduces the number of
LSAs in the LSDB.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Enable an OSPF process and enter OSPF
[ router-id router-id ] configuration mode.
3 Raisecom(config-router-ospf)#summary- Aggregate external routes.
address ip-address ip-mask [ not-
advertise ] [ metric metric ]
By default, external routes are not aggregated.
When external aggregates are aggregated, the
Metric is the maximum Metric of the LSA by
default.

Redistributing default route

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf Enable an OSPF process and enter OSPF configuration
process-id [ router-id router- mode.
id ]
3 Raisecom(config-router- Redistribute the default route.
ospf)#default-information
originate [ always ] [ metric
By default, no default route is generated. When the default
metric ] [ type { 1 | 2 } ] LSA is generated, if the always key word is specified, the
default Metric is 1. If the always key word is not specified,
the Metric is 10.

9.4.12 Configuring OSPF routing policy

Configuring OSPF receiving policy

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip prefix-list list-name Configure the IP prefix-list.
[ index number ] { permit | deny } ip-
address mask-length [ greater-equal ge- You can use the no ip prefix-list list-name
length ] [ less-equal le-length ] [ index number ] command to delete the
configuration.

Raisecom Proprietary and Confidential

136
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

3 Raisecom(config)#ip-access-list acl-number Configure the IP ACL rule.
{ deny | permit } ip any { destination-ip-
address ip-mask At present, the iTN8800 just supports
matching the address prefix information of
the route by specifying the destination IP
address and subnet mask.
4 Raisecom(config)#router ospf process-id Enable an OSPF process and enter OSPF
[ router-id router-id ] configuration mode.
5 Raisecom(config-router-ospf)#distribute-list Configure the OSPF filtering policy for
{ ip-access-list acl-number | prefix-list receiving the OSPF inter-area routes, intra-
list-name } in area routes, and AS external routes.

 Before configuring OSPF receiving policy, ensure that the IP ACL used by the
OSPF receiving policy has been created.
 When the iTN8800 performs filtering based on IP ACL, if the ACL mode is
configured to permit, all routes, which match with the ACL, can pass. Others are
filtered.
 You cannot modify the IP ACL unless it is not used by any routing policy.
 Different from IP ACL, the IP prefix-list can be modified even it is being used.
 If the configured IP prefix-list does not exist, do not filter received routes.

Configuring OSPF releasing policy

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip prefix-list list-name Configure the IP prefix-list.
[ index number ] { permit | deny } ip-address
mask-length [ greater-equal ge-length ] [ less- You can use the no ip prefix-list list-
equal le-length ] name [ index number ] command to
delete the configuration.
3 Raisecom(config)#ip-access-list acl-number Configure the IP ACL rule.
{ deny | permit } ip any { destination-ip-
address ip-mask At present, the iTN8800 just supports
matching the address prefix information
of the route by specifying the
destination IP address and subnet mask.
4 Raisecom(config)# router ospf process-id [ vrf Enable an OSPF process and enter
vrf-name ] [ router-id router-id ] OSPF configuration mode.
5 Raisecom(config-router-ospf)#distribute-list Configure the filtering policy that the
{ ip-access-list acl-number | prefix-list list- OSPF releases 5 types of LSAs to the
name } out AS.
6 Raisecom(config-router-ospf)#distribute-list Configure the OSPF releasing policy.
{ ip-access-list acl-number | prefix-list list-
name } out [ static | connected | rip | isis |
bgp ]

Raisecom Proprietary and Confidential

137
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

Raisecom(config-router-ospf)#distribute-list
{ ip-access-list acl-number | prefix-list list-
name } out ospf process-id [ vrf vrf-name ]

 Before configuring OSPF global releasing policy, ensure that the IP ACL used by
the OSPF global releasing policy has been created.
 You cannot modify the IP ACL unless it is not used by any routing policy.
 Different from IP ACL, the IP prefix-list can be modified even it is being used.
 After global releasing policy is configured, routes cannot be redistributed to the
local LSDB unless it passes the global releasing policy. After protocol releasing
policy is configured, the route can be redistributed through the protocol releasing
policy.
 After protocol releasing policy is configured, the redistributed protocol route can
be redistributed to the local LSDB through the protocol releasing policy. If global
releasing policy is also configured, the route must be redistributed through the
global releasing policy.

Configuring Type3 LSA filtering policy

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip prefix-list list-name Configure the IP prefix-list.
[ index number ] { permit | deny } ip-
address mask-length [ greater-equal ge- You can use the no ip prefix-list list-name
length ] [ less-equal le-length ] [ index number ] command to delete the
configuration.
3 Raisecom(config)#router ospf process-id Enable an OSPF process and enter OSPF
[ router-id router-id ] configuration mode.
4 Raisecom(config-router-ospf)#area area-id Configure Type3 LSA filtering policy in
filter prefix-list list-name { in | out } the area.

If the configured filtering policy does not exist, it believes that the command fails to
configure the filtering policy and no filtering operation is performed on received routes.

9.4.13 Configuring BFD for OSPF

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Enter OSPF configuration mode.
[ router-id router-id ]

Raisecom Proprietary and Confidential

138
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

3 Raisecom((config-router-ospf))#bfd all- Enable global BFD.
interfaces
By default, it is disabled.
4 Raisecom(config-router-ospf)#exit Enter global configuration mode.
5 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
6 Raisecom(config-port)#ip ospf bfd Enable BFD on the interface.
By default, it is disabled.

 If global BFD is enabled through the bfd all-interfaces command, no matter what
BFD configurations are set on the interface, BFD is enabled.
 If global BFD is disabled, BFD configurations on the interface take effect.

9.4.14 Configuring OSPF for MPLS-TE

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Enable an OSPF process and enter OSPF
[ router-id router-id ] configuration mode.
3 Raisecom(config-router-ospf)#capability Enable OSPF opaque LSA.
opaque
By default, it is disabled.
4 Raisecom(config-router-ospf)#mpls traffic- Enable TE in the OSPF area.
eng area area-id
By default, it is disabled.
5 Raisecom(config-router-ospf)#mpls traffic- Configure the Router ID of the MPLS-TE
eng router-id router-id router.

9.4.15 Checking configurations

No. Command Description
1 Raisecom#show ip ospf [ process-id ] Show OSPF basic information.
2 Raisecom#show ip ospf [ process-id ] interface Show OSPF interface information.
[interface-type interface-number ]
3 Raisecom#show ip ospf [ process-id ] neighbor Show OSPF neighbor information.
[interface-type interface-number ] [ neighbor-
id ]
4 Raisecom#show ip ospf [ process-id ] route Show OSPF routing information.
5 Raisecom#show ip ospf [ process-id ] database Show OSPF link status database
[ max-age | self-originate ]

Raisecom Proprietary and Confidential

139
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

No. Command Description

Raisecom#show ip ospf [ process-id ] database information and statistics.
[ router | network | summary | asbr-summary |
external ] [ linkstate-id ] [ adv-router ip-
address | self-originate ]
Raisecom#show ip ospf [ process-id ] database
statistics
6 Raisecom#show ip ospf [ process-id ] border- Show information about routers at edges
routers of the area and AS.
7 Raisecom#show ip ospf [ process-id ] neighbor Show OSPF statistics or OSPF neighbor
statistics statistics.
8 Raisecom#show ip ospf [ process-id ] summay- Show OSPF ASBR external route
address aggregation information.
9 Raisecom#show cspf tedb [ detail ] Show TEDB database information.

9.4.16 Maintenance
Command Description
Rasiecom#clear ip ospf [ process-id | vrf vrf-name ] Restart the OSPF process.
process [ graceful ]

9.5 Configuring ISIS

9.5.1 Configuring ISIS basic function
To run ISIS normally, two steps need to be done: start ISIS process and configure the name of
network entity.
 Use the router isis command to start ISIS process.
 Use the ip router isis or ipv6 router isis command to start ISIS process on the interface.
step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router isis [ area-tag ] Start an ISIS process and enter ISIS
configuration mode.
3 Raisecom(config)#interface interface-type (Optional) enter interface configuration mode.
interface-number
4 Raisecom(config-port)#ip router isis (Optional) start an ISIS process on the
[ area tag ] interface.
Raisecom(config-port)#exit
Raisecom(config-port)#ipv6 router isis
[ area tag ]
Raisecom(config-port)#exit

Raisecom Proprietary and Confidential

140
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

step Command Description

5 Raisecom(config)#router isis [ area-tag ] Enter ISIS configuration mode.
6 Raisecom(config-router-isis)#net network- Configure the network identifier entity of ISIS
entity routing process.

9.5.2 Configuring ISIS routing

Configuring router type

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router isis [ area-tag ] Start an ISIS process and enter ISIS
configuration mode.
3 Raisecom(config-router-isis)#is-type Configure the router type.
{ level-1 | level-1-2 | level-2-only }
By default, it is level-1-2.
4 Raisecom(config-router-isis)#hostname (Optional) enable the switching mechanism
dynamic of dynamic hostname.
By default, it is disabled.

Configuring overhead
The ISIS overhead can be configured automatically or manually. After the automatic
calculation of the overhead on the interface is enabled, the ISIS will automatically calculate
the overhead on the interface according to the following rules:
 When the type of overhead is configured to wide, ISIS will automatically calculate the
value according to the interface rate, the formula is: overhead on the interface =
reference rate/interface rate × 10, and the max value obtained is 16777214.
 When the type of overhead is configured to narrow, the interface overhead is:
– 60 for interface rate between 1 and 10 Mbit/s
– 50 for interface rate between 1 and 100 Mbit/s
– 40 for interface rate between 101 and 155 Mbit/s
– 30 for interface rate between 156 and 622 Mbit/s
– 20 for interface rate between 623 and 2500 Mbit/s
– 10 for other conditions

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router isis [ area- Start an ISIS process and enter ISIS configuration
tag ] mode.

Raisecom Proprietary and Confidential

141
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

3 Raisecom(config-router-isis)#metric- Configure the type of ISIS overhead.
style { narrow | transition | wide }
Raisecom(config-router-isis)#exit By default, it is narrow.
4 Raisecom(config-router-isis)#auto- Enable automatic calculation of overhead on the
metric { enable | disable } interface.
By default, it is disabled.
5 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
6 Raisecom(config-port)#isis metric Configure the overload value on the interface.
metric [ level-1 | level-2 ]
By default, it is 10.

Configuring reference bandwidth

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router isis Start an ISIS process and enter ISIS configuration mode.
[ area-tag ]
3 Raisecom(config-router- Configure reference rate referred to while calculating
isis)#reference-bandwidth technical link overhead.
bandwidth
By default, it is 100 Mbit/s.

Configuring ISIS administrative distance

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router isis Start an ISIS process and enter ISIS configuration mode.
[ area-tag ]
3 Raisecom(config-router- Configure the management distance of ISIS routing.
isis)#distance distance [ ip-
address mask-address ] By default, it is 115.

9.5.3 Configuring ISIS network

Configuring type of ISIS network

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number

Raisecom Proprietary and Confidential

142
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

3 Raisecom(config-port)#isis network Configure the type of interface network to P2P.
point-to-point
By default, it is broadcast.

Adjacencies
This configuration is only applied to Level-1-2 routers.
 If the host is Level-1-2 router, it needs to establish association with peer router in certain
area (Level-1 or Level-2). Configuring an area for establishing adjacency can restrain the
interface from receiving and sending the Hello packet only from that certain area.
 In the point-to-point link, the interface can only receive and send one type of Hello
packet. Configuring an area for establishing adjacency can reduce the processing time
between routers and save bandwidth.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)#isis Configure an area for establishing interface adjacency.
circuit-type { level-1 | level-1-
2 | level-2-only }
By default, it is Level-1-2.

Configuring DIS priority

The Designated Intermedia System (DIS) election of the ISIS is preemptive and predictable.
There is not backup DIS in the ISIS. Therefore, when one DIS does not work, another DIS
will be elected. The rules for electing the DIS are as below:
 The router with highest DIS election priority will be elected. If all routers have the same
priority, the router with biggest MAC address will be elected.
 The DIS in Level-1 and Level-2 are elected respectively but the result may be not the
same IS.
 The interval between sending Hello packet by DIS is 1/3 times of that by common
routers, which can ensure that the invalid DIS be detected in no time.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)#isis Configure the DIS priority on the interface in different
priority priority [ level-1 | areas.
level-2 ]
By default, it is 64.

Raisecom Proprietary and Confidential

143
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

9.5.4 Optimizing ISIS network

Configuring ISIS packet timer

The invalid number of Hello packet is decided by the Holddown time. If the router cannot
receive Hello packet sent by the peer router within the Holddown time, the peer router can be
considered invalid. The Holddown time is configured based on interface and different router
in the same area can set different the Holddown time.
By changing the time interval for sending Hello packet of ISIS or the invalid number of Hello
packet, you can adjust the Holddown time.

Step Command Description

1 Raisecom#config Enter global configuration mode.

2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#isis hello- Configure the interval between sending Hello
interval seconds [ level-1 | level-2 ] packets on the interface of different areas.
By default, it is 10s.
4 Raisecom(config-port)#isis hello- Configure the number of invalid ISIS neighbor
multiplier number [ level-1 | level-2 ] Hello packets on the interface of different areas.
5 Raisecom(config-port)#isis csnp-interval Configure the interval between sending CSNP
seconds [ level-1 | level-2 ] packets on the interface of different areas in the
broadcast network.
By default, it is 10s.

Configuring LSP
Step Command Description

1 Raisecom#config Enter global configuration mode.

2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#isis lsp-interval Configure the interval between sending LSP
milliseconds packets.
By default, it is 33ms.
4 Raisecom(config-port)#isis retransmit- Configure retransmission interval between
interval seconds sending LSP packets on the point-to-point link.
Raisecom(config-port)#exit
By default, it is 5s.
5 Raisecom(config)#router isis [ area- Configure the interval between generating LSP.
tag ]
Raisecom(config-router-isis)#lsp-gen- By default, it is 5s.
interval seconds [ level-1 | level-2 ]

Raisecom Proprietary and Confidential

144
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

6 Raisecom(config-router-isis)#max-lsp- Configure the longest TTL of the LSP

lifetime seconds [ level-1 | level-2 ] generated.
By default, it is 1200s.
7 Raisecom(config-router-isis)#lsp- Configure the refresh time of LSP.
refresh-interval seconds [ level-1 |
level-2 ]
By default, it is 900s.
8 Raisecom(config-router-isis)#ignore-lsp- Enable ignoring the checkout for LSP.
errors
By default, it is disabled.

Configuring interval for calculating SPF

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router isis [ area- Start an ISIS process and enter ISIS
tag ] configuration mode
3 Raisecom(config-router-isis)#spf- Configure the interval for calculating SPF in the
interval seconds [ level-1 | level-2 ] ISIS.
By default, it is 10s.
4 Raisecom(config-router-isis)#set- (Optional) enable overload bit.
overload-bit
By default, it is disabled.

Configure ISIS passive interface

If you do not wish the ISIS routing information to be obtained by the router in a network, you
can configure the interface to ISIS passive interface to prevent it from sending ISIS packets.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
3 Raisecom(config-port)#isis passive Enable the passive function on ISIS interface.
By default, it is disabled.

Configure Hello packet padding

Hello packet padding refers to padding Hello packet with MTU field, thus notifying peer and
local interface of the MTU.

Raisecom Proprietary and Confidential

145
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router isis Start an ISIS process and enter ISIS configuration mode.
[ area-tag ]
3 Raisecom(config-router- Enable Hello Packet padding.
isis)#hello padding
By default, all types of interface are padded with standard
Hello packet.

9.5.5 Configure ISIS authentication

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router isis [ area-tag ] Start an ISIS process and enter ISIS
configuration mode.
3 Raisecom(config-router-isis)#area-password Configure Level-1 area authentication.
{ clear password | md5 password }
[ authenticate snp { send-only | validate } ]
4 Raisecom(config-router-isis)#domain-password Configure Level-2 area authentication.
{ clear password | md5 password }
[ authenticate snp { send-only | validate } ]

Configure ISIS interface authentication

The packet authentication gives preference to interface authentication mode. If the interface
authentication mode is no authentication, the area authentication mode will be selected. Only
when the authentication mode and the password are the same can the ISIS interface establish
neighborship.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
3 Raisecom(config-port)#isis password { clear Configure the ISIS authentication mode
password | md5 password } [ level-1 | level-2 ] and password on the interface.

9.5.6 Controlling ISIS routing information

Configuring ISIS redistributed routes

Step Command Description
1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

146
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

2 Raisecom(config)#router isis Start an ISIS process and enter ISIS configuration
[ area-tag ] mode.
3 Raisecom(config-router- Configure protocol route redistributed policy.
isis)#redistribute { connected |
static | rip | ospf process-id | By default, ISIS does not redistribute other protocol
isis area-tag | bgp } [ route-map routes. If you do not specify the area when it
map-name ] [ level-1 | level-2 | redistributes routes, it will redistribute routes to Level-
level-1-2 ] [ metric metric ] 2 by default.
[ metric-type { external |
internal } ]
4 Raisecom(config-router- Configure ISIS route redistributed policy among areas.
isis)#redistribute isis ip level-2
into level-1 By default, the routing information in level-2 will not
be distributed to Level-1.

Configuring redistributing default route

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router isis [ area-tag ] Start an ISIS process and enter ISIS
configuration mode.
3 Raisecom(config-router-isis)#default- Configure redistributing Level-2
information originate default route.

Configuring ISIS route aggregation

Route aggregation can not only reduce the scale of routing table but also shrink the size of
LSP packet generated by the local router and reduce the scale of LSDB.
 The aggregated route can be the route found by the ISIS and the route redistributed
externally.
 The overload of aggregated route takes the minimum overload among all the routes
aggregated.
 The router only aggregates the route generated in the local LSP.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router isis [ area-tag ] Start an ISIS process and enter ISIS
configuration mode.

Raisecom Proprietary and Confidential

147
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

3 Raisecom(config-router-isis)#summary- Configure route aggregation among areas.
address ip-address mask-address [ level-1
| level-2 | level-2-only ] By default, there is no route aggregation. The
overload while configuring route aggregation
is the maximum Metric in the LSA. And the
route aggregation will be advertised.

Configuring ISIS equal-cost multi-path load balancing

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router isis [ area-tag ] Start an ISIS process and enter ISIS
configuration mode.
3 Raisecom(config-router-isis)#maximum Configure the maximum number of ISIS
load-balancing number equal-cost multi-path load balancing paths.

9.5.7 Configuring ISIS BFD

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router isis [ area-tag ] Start an ISIS process and enter ISIS
configuration mode.
3 Raisecom(config-router-isis)#isis bfd enable Enable global ISIS BFD.
By default, it is disabled.
4 Raisecom(config-router-isis)#bfd all- Enable ISIS BFD on all interfaces.
interfaces
By default, it is disabled.

9.5.8 Configuring ISIS GR

Configure ISIS graceful restart, that is, the switchover ensures no service interruption while
the iTN8800 is rebooted.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router isis [ area-tag ] Start an ISIS process and enter ISIS
configuration mode.
3 Raisecom(config-router-isis)#graceful- Enable ISIS graceful restart.
restart
By default, it is disabled.

Raisecom Proprietary and Confidential

148
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

4 Raisecom(config-router-isis)#graceful- Enable the interval of ISIS graceful restart.
restart interval seconds
By default, it is 300s.
5 Raisecom(config-router-isis)#graceful- Enable ISIS graceful restart to restrain the
restart sa enable neighbor device from advertising routes.
By default, it is enabled.

9.5.9 Configuring ISIS TE

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router isis [ area- Start an ISIS process and enter ISIS configuration
tag ] mode.
3 Raisecom(config-router-isis)#mpls Enable MPLS-TE and configure MPLS-TE level.
traffic-eng { level-1 | level-2 }
By default, it is disabled.
4 Raisecom(config-router-isis)#mpls Configure the Router ID of MPLS-TE router.
traffic-eng router-id router-id
By default, the ISIS Router ID is used.

9.5.10 Checking configurations

Step Command Description
1 Raisecom#show isis interface [ detail ] Show ISIS interface.
2 Raisecom#show isis neighbor [ system-id | Show ISIS neighbors.
detail ]
3 Raisecom#show isis hostname Show the mapping between host name and
system ID.
4 Raisecom#show isis route Show ISIS IPv4 route.
5 Raisecom#show isis topology [ level-1 | Show ISIS topology.
level-2 ]
6 Raisecom#show isis database [ lsp-id | Show database about ISIS link status.
detail ]
7 Raisecom#show isis summary Show basic configurations about ISIS.
8 Raisecom#show isis mpls traffic-eng Show interface advertised by the router.
advertisements

Raisecom Proprietary and Confidential

149
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

9.5.11 Maintenance
No. Command Description
1 Rasiecom#clear isis area-tag [ graceful-restart ] Clear ISIS.
2 Rasiecom#clear isis neighbor [ system-id ] Clear ISIS neighbors.

9.6 Configuring BGP

9.6.1 Configuring BGP basic functions
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp as-id Enable BGP and create a BGP instance.
Enter BGP configuration mode.
3 Raisecom(config-router)#bgp router-id router-id Configure the BGP Router ID.

9.6.2 Configuring BGP route advertisement

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp as-id Enter BGP configuration mode.
3 Raisecom(config-router)#network ip-address Advertise routes to the BGP routing table.
[ mask-address ] [ route-map route-map-
name ]

9.6.3 Configuring BGP redistributed routes

Configuring BGP neighbors

BGP uses the TCP connection. Therefore, when configuring BGP, you need to configure the
IP address of the BGP neighbor. The BGP neighbor can be non-adjacent routers. You can
establish a BGP neighborship. To enhance stability of the BGP connection, we recommend
using the loopback interface address to establish the connection.
Specified IP addresses of BGP neighbors are divided into 2 types:
 Interface IP address of the directly-connected BGP neighbor
 Loopback interface address of the BGP neighbor, where the route can reach. In this mode,
you need to configure the route update source to ensure that the BGP neighbor is
established properly.
Raisecom Proprietary and Confidential
150
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router Enter BGP configuration mode.
bgp as-id
3 Raisecom(config- Create a BGP neighbor and specify the AS ID of the BGP
router)#neighbor ip- neighbor.
address remote-as as-id
By default, there is no BGP neighbor.
4 Raisecom(config- Configure the device to use the specified local source interface
router)#neighbor ip- for establishing the BGP connection.
address1 update-source ip-
address2 The BGP connection can be established successfully when any
Raisecom(config-
end is configured with the update source properly. However, it
router)#neighbor ip-
may take more time to establish the connection. To ensure that
address1 update-source the stability of the connection, we recommend configuring
interface-type interface- update source addresses for both ends.
number
5 Raisecom(config- Configure the weight of the route learned from the BGP
router)#neighbor ip- neighbor.
address weight weight
By default, it is 0.
6 Raisecom(config- Enable the BGP neighbor to exchange the specified address
router)#neighbor ip- family route.
address activate
By default, enable the BGP neighbor to exchange the IPv4
unicast address family route only.
7 Raisecom(config- Enable the feature of sending the default route to the BGP
router)#neighbor ip- neighbor.
address default-originate
By default, do not send the default route to the BGP neighbor.
8 Raisecom(config- Configure descriptions of the BGP neighbor.
router)#neighbor ip-
address description string By default, there is no description of the BGP neighbor.
9 Raisecom(config- Configure the router to modify the next-hop address of the route
router)#neighbor ip- to the IP address of the Tx end, when the router releases the route
address next-hop-self to the BGP neighbor.
By default, when the router releases the route to the BGP
neighbor, the next-hop address of the route is identical to the
next-hop IP address of the route in the local BGP routing table.
10 Raisecom(config- Enable the log which is used to inform the BGP neighbor of state
router)#bgp log-neighbor- change.
changes
By default, it is enabled.
11 Raisecom(config- (Optional) disallow the iTN8800 to establish the BGP connection
router)#neighbor ip- with the specified BGP neighbor.
address shutdown
By default, establishing the BGP connection with the BGP
neighbor is allowed.

Raisecom Proprietary and Confidential

151
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

12 Raisecom(config- (Optional) allow the iTN8800 to establish the EBGP connection
router)#neighbor ip- with BGP neighbors in the indirectly-connected network. In
address ebgp-multihop addition, specify the maximum hops allowable for the specified
[ ttl ] EBGP connection.
By default, only physically directly-connected BGP neighbors
can establish the EBGP connection.
13 Raisecom(config- Redistribute routing information, learned from the IBGP
router)#bgp redistribute- neighbor, to the IGP.
internal
By default, redistributing the IBGP route to the IGP is disabled.

Configuring BGP redistributed routes

The BGP cannot discover the route. Therefore, it needs to redistribute routes based on other
protocols (such as IGP or static route) to the BGP routing table to make these routes be
transmitted in or between ASs.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp as-id Enter BGP configuration mode.
3 Raisecom(config-router)#redistribute Configure the BGP to redistribute routes, which
{ connected | static | ospf | isis } based on other protocols, to the BGP routing table.
[ metric metric ] [ route-map map ]

Redistributing default route

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp as-id Enter BGP configuration mode.
3 Raisecom(config-router)#default-information Configure the BGP to redistribute the
originate default route.

9.6.4 Configuring BGP routing

Configuring BGP administrative distance

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router Enter BGP configuration mode.
bgp as-id

Raisecom Proprietary and Confidential

152
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

3 Raisecom(config- Configure the administrative distance of the BGP route.
router)#distance bgp
 The administrative distance of external routes (routes learned
ebgp distance1 ibgp
distance2 local through the EBGP) is 20 by default.
 The administrative distance of internal routes (routes learned
distance3
through the IBGP) is 200 by default.
 The administrative distance of local routes (BGP routes redistributed

through the aggregation command) is 200 by default.

Configuring BGP path selection policy

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp Enter BGP configuration mode.
as-id
3 Raisecom(config-router)#bgp (Optional) configure the BGP not to consider the receiving
deterministic-med sequence when selecting the route.
By default, the BGP considers the receiving sequence when
selecting the route.
4 Raisecom(config-router)#bgp Configure the BGP to compare the MED for all paths.
always-compare-med
5 Raisecom(config-router)#bgp Configure the BGP optimum path selection policy to selecting
bestpath compare-routerid the route with the minimum Router ID.
By default, the BGP selects the BGP route which is received
earliest.
6 Raisecom(config-router)#bgp Configure the BGP to ignore the AS-PATH property when
bestpath as-path ignore selecting the optimum path.

Configuring BGP and IGP route synchronization

After BGP synchronization is enabled,
 The BGP route can participate into selection if it meets the following requirements. Then,
if it is selected, the RM is applied to the routing table.
– In the RM, the BGP route learned through IBGP can exactly match the route learned
through IGP.
– The administrative distance of the IGP route is shorter than the administrative
distance of the BGP route.
 The BGP route status will flap and it may participate into selection or not, if it meets the
following requirements:
– The BGP route learned through IBGP can exactly match the route learned through
IGP.
– The administrative distance of the IGP route is greater than the administrative
distance of the BGP route.

Raisecom Proprietary and Confidential

153
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp as-id Enter BGP configuration mode.
3 Raisecom(config-router)#synchronization Enable BGP and IGP route synchronization.
By default, it is disabled.

Configuring route dampening

Route flapping is one route instability form. Route flapping refers that a route appears and
then disappears alternatively. Route dampening can be used to overcome route flapping.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#rou Enter BGP configuration mode.
ter bgp as-id
3 Raisecom(config- Enable BGP route dampening or modify the BGP route dampening
router)#bgp parameter.
dampening half-life
reuse suppress max- By default, BGP route dampening is disabled.
suppress-time After BGP dampening is enabled, the default values of all parameters are
shown as below.
 Half-life: 15min
 Reuse value: 750
 Dampening threshold: 2000
 Maximum suppress time: 60min.

Configuring BGP community attribute

The community attribute is an optional delivery attribute of BGP routes and can be added to
the prefix of each route. If a route contains a community attribute, it indicates that the route is
a member of a routing community with routes of one or more the same characteristics.
According to these features, the configuration of the routing policy can be greatly simplified,
and the capability of the routing policy is also enhanced.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp [ as-id ] Enter BGP configuration mode.
3 Raisecom(config-router)#neighbor ip-address Enable the BGP-enabled device to
send-community standard send standard community attribute to
the peer.

Raisecom Proprietary and Confidential

154
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

9.6.5 Configuring BGP network

Configuring RR
Prefix notification rules of the Router Reflector (RR) are shown as below:
 Rule 1: the RR just notifies or reflects the optimum path to which it returns.
 Rule 2: the RR always notifies the prefix to the BGP neighbor.
 Rule 3: when notifying the prefix, the RR client follows the common IBGP loopback
prevention rule.
 Rule 4: to notify the IBGP neighbor, client, or non-client of the prefix, follow rules 5, 6,
and 7.
 Rule 5: the RR will notify all its clients and non-clients of the prefix, which is learned
from the external BGP neighbor.
 Rule 6: the RR will notify all its clients of the prefix, which reaches the RR through a
non-client IBGP neighbor.
 Rule 7: the RR will notify other clients and non-clients of the route, if the prefix reaches
the RR through a client.

In some networks, clients of the RR have established a full-connection. They can

exchange routing information directly without using route reflection. In this case, you
can use the no bgp client-to-client reflection command to disable route reflection
among clients of the RR.
To enhance network reliability and prevent faults from occurring at a node, you need
to configure one or more RR in a cluster. You can configure the identical cluster ID for
all RRs in the cluster to identify the cluster. This helps avoid the loopback.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp as-id Enter BGP configuration mode.
3 Raisecom(config-router)#neighbor Configure the device to the RR and set the specified
ip-address route-reflector-client neighbor as the client of the RR.
By default, route reflection is disabled.
4 Raisecom(config-router)#bgp Enable route reflection among clients of the RR.
client-to-client reflection
By default, route reflection among clients of the RR is
enabled.
5 Raisecom(config-router)#bgp Configure the cluster ID of the RR.
cluster-id cluster-id
By default, it is the Router ID.

Configuring BGP default local priority

Step Command Description
1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

155
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

2 Raisecom(config)#router bgp as-id Enter BGP configuration mode.
3 Raisecom(config-router)#bgp default local- Configure BGP default local priority.
preference priority
By default, it is 100.

Configuring BGP timer

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router Enter BGP configuration mode.
bgp as-id
3 Raisecom(config- Configure the interval for scanning the BGP routing table.
router)#bgp scan-time time
By default, it is 60s.
4 Raisecom(config- Configure the lifetime and maintenance time of the global BGP
router)#timers bgp keep- connection.
alive-time hold-time
By default, the lifetime and maintenance time of the global BGP
connection are configured to 60s and 180s respectively.
5 Raisecom(config- Configure the lifetime and maintenance time of the neighbor.
router)#neighbor ip-
address timers keep-alive- By default, the lifetime and maintenance time of the neighbor are
time hold-time identical to the ones of the global BGP connection.

Configuring BGP route aggregation

 At present, the iTN8800 supports BGP manual aggregation. Manual aggregation is only
valid for existing routes in the BGP local routing table. If there is no route, whose mask
size is greater than 16 bytes, in the BGP routing table, the BGP will not release the
aggregated route even you use the aggregate 10.1.1.1 255.255.0.0 command to aggregate
the route.
 The aggregated route cannot be set to the default route (0.0.0.0/0).
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp as-id Enter BGP configuration mode.
3 Raisecom(config-router)#aggregate- Configure BGP route aggregation and release the
address ip-address mask-address aggregated route and detail route.
4 Raisecom(config-router)#aggregate- Configure BGP route aggregation, release the
address ip-address mask-address aggregated route only and dampens the detail route.
summary-only
5 Raisecom(config-router)#aggregate- Configure BGP route aggregation and set the AS_SET
address ip-address mask-address as- option. The generated aggregated route includes all AS
set IDs in the AS_PATH and takes them as an AS_SET to
prevent the route loop.

Raisecom Proprietary and Confidential

156
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Configuring BGP route filtering

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip as-path access-list Configure the filter of the AS_PATH list.
access-list-number { permit | deny } regexp
3 Raisecom(config)#router bgp [ as-id ] Enter BGP configuration mode.
4 Raisecom(config-router)#neighbor ip-address Configure the BGP route filtering policy
filter-list access-list-number { in | out } based on AS_PATH list.
5 Raisecom(config-router)#neighbor ip-address Apply the routing policy to the specified
route-map map-name { in | out } neighbor to filter or release the route.
6 Raisecom(config-router)#distribute-list Filter BGP routing information based on IP
prefix list-name{ in | out } prefix-list.
7 Raisecom(config-router)#distribute-list Filter routes redistributed to the BGP
prefix list-name out [ connected | static | routing table based on IP prefix-list.
rip | ospf | isis ]
8 Raisecom(config-router)#neighbor ip-address Configure the specified neighbor to filter
prefix-list prefix-list-name { in | out } received or released routes based on IP
prefix-list.

9.6.6 Configuring BGP GR

After being started, BGP Graceful Restart (GR) helps to prevent interrupting the forward
process caused by protocol restart.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp as-id Enter BGP configuration mode.
3 Raisecom(config-router)# bgp Enable BGP GR.
graceful-restart all
4 Raisecom(config-router)#bgp Configure the maximum time used for re-establishing
graceful-restart restart-time the neighboring relationship during the GR process.
seconds
By default, it is 120s.
5 Raisecom(config-router)#bgp Configure the maximum time for the Helper to keep the
graceful-restart stalepath-time Stale route during the GR process.
seconds
By default, it is 360s.

Raisecom Proprietary and Confidential

157
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

9.6.7 Configuring BFD for BGP

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp as-id Enter BGP configuration mode.
3 Raisecom(config-router)#neighbor ip-address Enable BFD for BGP.
fall-over bfd
By default, it is disabled.

9.6.8 Configuring BGP authentication

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp as-id Enter BGP configuration mode.
3 Raisecom(config-router)#neighbor Enable to perform MD5 authentication on the BGP
ip-address password password message when the BGP neighbor establishes the TCP
connection.
By default, it is disabled.

9.6.9 Checking configurations

No. Command Description
1 Raisecom#show ip bgp Show contents of the local BGP routing
table.
2 Raisecom#show ip bgp ip-address [ ip-mask ] Show information about the specified
network in the local BGP routing table.
3 Raisecom#show ip bgp vpnv4 { all | rd rd } Show BGP VPNv4 routing information.
4 Raisecom#show ip bgp vpnv4 all labels Show label information carried by the
BGP VPNv4 route.
5 Raisecom#show ip bgp vpnv4 all network-address Show routing information about the
[ network-mask ] specified BGP VPNv4.
6 Raisecom#show ip bgp dampening dampened-paths Show dampened routing information.
7 Raisecom#show ip bgp dampening parameters Show route dampening parameters.
8 Raisecom#show ip bgp dampening flap-statistics Show route flapping statistics.
9 Raisecom#show ip bgp [ ipv4 unicast | vpnv4 Show summaries of the BGP neighbor.
all ] summary
10 Raisecom#show ip bgp [ ipv4 unicast | vpnv4 Show detailed BGP neighbor status.
all ] neighbors [ ip-address ]

Raisecom Proprietary and Confidential

158
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

9.6.10 Maintenance
Command Description
Rasiecom#clear ip bgp dampening [ network-address Clear all route dampening information.
[ network-mask ] ]
Rasiecom#clear ip bgp { all | ip-address | external Reset all or specified BGP connections of
| internal } [ ipv4 unicast | vpnv4 unicast ] the public network.
Rasiecom#clear ip bgp [ ipv4 unicast | vpnv4
unicast ]as-id
Rasiecom#clear ip bgp { all | ip-address | external Update all or specified BGP routes of the
| internal } [ ipv4 unicast | vpnv4 unicast ] { in public network without breaking the BGP
| out | soft } connecting.
Rasiecom#clear ip bgp [ ipv4 unicast | vpnv4
unicast ] as-id { in | out | soft }

9.7 Configuring RIP

9.7.1 Configuring basic RIP functions
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router rip Enable RIP, and enter RIP configuration mode.
3 Raisecom(config-router-rip)#network Configure a directly-connected and effective
ip-address network based on RIP.
4 Raisecom(config-router-rip)#offset- Configure the additional metrics when the interface
list access-list-name { in | out } receives or sends RIP routes.
offset-value [ interface-type
interface-number ] By default, it is 0.
5 Raisecom(config-router-rip)#passive- (Optional) configure the interface to be a passive
interface { interface-type interface- interface.
number | default }
By default, it is a non-passive interface.

9.7.2 Configuring RIP version

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router rip Enable RIP, and enter RIP configuration mode.

Raisecom Proprietary and Confidential

159
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

3 Raisecom(config-router-rip)#version Configure global RIP version ID.
version-id
By default, global RIP version is not configured. In
this case, interfaces which are configured with RIP but
not configured with the RIP version in the Tx direction
will send V1 packets. Interfaces which are enabled
with RIP but not configured with the RIP version in
the Rx direction will receive packets of any version.
4 Raisecom(config-router-rip)#exit Enter interface configuration mode.
Raisecom(config)#interface
interface-type interface-number
Raisecom(config-port)#
5 Raisecom(config-port)#ip rip Configure the receiving RIP version.
receive version { 1 | 2 }*
By default, the receiving RIP version is subjected to
the global RIP version.
6 Raisecom(config-port)#ip rip send Configure the sending RIP version.
version { 1 | 2 } *
By default, the sending RIP version is subjected to the
global RIP version.
7 Raisecom(config-port)#ip rip v2- Configure the interface which runs RIPv2 to send
broadcast broadcast updates.
By default, it sends multicast updates.

You can configure RIP version globally and on the interface of the iTN8800. If the
interface is configured with RIP version, then this RIP version prevails.

9.7.3 Redistributing external routes

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router rip Enable RIP, and enter RIP configuration mode.
3 Raisecom(config-router-rip)#host- Enable the function of receiving host routes.
route
By default, it is enabled.
4 Raisecom(config-router-rip)#default- Enable broadcasting the default route.
information originate
By default, it is disabled.
5 Raisecom(config-router- Configure the policy for redistributing RIP routes.
rip)#redistribute { static |
connected | isis | bgp | ospf }
[ metric metric ] [ route-map map-
name ] [ tag tag-value ]
6 Raisecom(config-router-rip)#default- Configure the default metrics of redistributing
metric metric external routes.
By default, it is 1.

Raisecom Proprietary and Confidential

160
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

7 Raisecom(config-router-rip)#auto- Enable automatic aggregation (support RIPv2 only).
summary
By default, it is enabled.
8 Raisecom(config-router- Enabled the function of checking the source IP
rip)#validate-update-source address of the received RIP packets.
By default, it is enabled.

9.7.4 Configuring timer

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router rip Enable RIP, and enter RIP configuration mode.
3 Raisecom(config-router-rip)#timers Configure RIP timer.
basic update-time invalid-time
holddown-time flush-time By default, the update interval is 30s. The invalid
interval is 180s. The suppression interval is 120s. The
refreshing interval is 120s.

9.7.5 Configuring loop suppression

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)#ip rip split- Enable split horizon on the interface, that is, the route
horizon learned from one interface will not be broadcasted
back to the interface again.
Be default, it is enabled.
4 Raisecom(config-port)#ip rip Enable poison reverse on the interface, that is, the
poison-reverse route learned from one interface can be advertised to
other interfaces through this interface. However, the
metrics of those routes is configured to 16, namely,
unreachable.
By default, it is disabled.

If poison reverse and split horizon are enabled together, split horizon will be invalid.

Raisecom Proprietary and Confidential

161
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

9.7.6 Configuring authentication

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#ip rip Configure the packet authentication mode on the
authentication mode { text | md5 } interface.
By default, the authentication mode of RIPv2
packets on the interface is no authentication.
4 Raisecom(config-port)#ip rip Configure the interface-associated password.
authentication string password-string
5 Raisecom(config-port)#ip rip Configure the interface-associated authentication
authentication key-chain key-chain-name secret string.

9.7.7 Configuring routing policy

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router rip Enable RIP, and enter RIP configuration
mode.
3 Raisecom(config-router-rip)#distribute-list Configure RIP ingress routing policy.
{ ip-access-list acl-number | prefix-list
list-name | route-map rmap-name } in
[ interface-type interface-number ]
4 Raisecom(config-router-rip)#distribute-list Configure RIP egress routing policy.
{ ip-access-list acl-number | prefix-list
list-name | route-map rmap-name } out
[ interface-type interface-number ]
5 Raisecom(config-router-rip)#distribute-list Execute routing policies on the source
gateway list-name in [ interface-type address of the received packets through
interface-number ] RIP.

9.7.8 Configuring route calculation

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router rip Enable RIP, and enter RIP configuration mode.
3 Raisecom(config-router- Configure the administrative distance of RIP, namely,
rip)#distance administrative- the protocol priority. The shorter the administrative
distance [ ip-address wild-card- distance is, the higher the priority will be.
mask ]
By default, the administrative distance is 120.

Raisecom Proprietary and Confidential

162
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 9 IP routing

Step Command Description

4 Raisecom(config-router-rip)#maximum Configure the maximum number of IP equal-cost
load-balancing number multi-path load balancing paths.

9.7.9 Configuring alarms

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router rip Enable RIP, and enter RIP configuration mode.
3 Raisecom(config-router-rip)#snmp- Enable using RIP to send Trap.
server rip-trap enable
By default, it is disabled.

9.7.10 Checking configurations

No. Command Description
1 Raisecom#show ip rip Show basic information about RIP.
2 Raisecom#show ip rip database Show information about RIP routing database.
3 Raisecom#show ip rip interface Show configurations and status of the interface
which runs RIP.

9.7.11 Maintenance
Command Description
Rasiecom#clear rip database Clear information about RIP routing database.
Rasiecom#clear rip statistics Clear RIP interface statistics.

Raisecom Proprietary and Confidential

163
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

10 MPLS

This chapter describes principles and configuration procedures of MPLS-TP, including

following sections:
 Configuring MPLS basic functions
 Configuring static LSP
 Configuring LDP LSP
 Configuring MPLS TE
 Configuring MPLS fault detection
 Configuring GRE Tunnel
 Configuring MPLS load balancing
 Configuration examples

10.1 Configuring MPLS basic functions

10.1.1 Preparing for configurations

Scenario
Configurations on MPLS basic functions are prerequisites for making other MPLS functions
effective. The Label Switching Router (LSR) is the network device, which can exchange and
forward the MPLS label. The LSR is also called the MPLS node. The LSR is the basic
element in the MPLS network. All LSRs support MPLS. To enable global MPLS function,
you must enable the LSR ID.

Prerequisite
N/A

10.1.2 Configuring MPLS basic functions

Step Command Description
1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

164
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Step Command Description

2 Raisecom(config)#mpls lsr-id lsr-id Configure the LSR ID of the device.
3 Raisecom(config)#mpls enable Enable global MPLS function.

10.1.3 Configuring MPLS Tunnel basic functions

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface tunnel Enter Tunnel interface configuration mode.
interface-number
3 Raisecom(config-tunnelif)#tunnel mode Configure Tunnel mode.
{ gre | mpls }
By default, it is MPLS.
4 Raisecom(config-tunnelif)#description (Optional) configure descriptions of the Tunnel
description interface.
5 Raisecom(config-tunnelif)#destination Configure the destination IP address of the
ip-address Tunnel interface.
6 Raisecom(config-tunnelif)#mpls signal- Configure the protocol type of the Tunnel
protocol { rsvp-te | static } interface.
By default, the protocol type of the Tunnel
interface is the static protocol.
7 Raisecom(config-tunnelif)#mpls tunnel- Configure the Tunnel ID of the Tunnel interface.
id tunnel-id
8 Raisecom(config-tunnelif)#mpls te (Optional) set the current Tunnel to the bypass
bypass-tunnel Tunnel.
9 Raisecom(config-tunnelif)#mpls te hot- (Optional) configure the WTR of the hot standby
standby wtr wtr-time of the Tunnel interface.
By default, it is 10s.
10 Raisecom(config-tunnelif)#mpls te Configure the properties of the Tunnel interface
commit to take effect.

10.1.4 Configuring MPLS Tunnel policy

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#tunnel-policy policy- Enter Tunnel policy configuration mode.
name

Raisecom Proprietary and Confidential

165
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Step Command Description

3 Raisecom(config-tunnelpolicy)#tunnel Configure the selection order of the Tunnel
select-seq { lsp [ cr-lsp ] | cr-lsp policy.
[ lsp ] | gre }
By default, the Tunnel optimization policy
parameter is cr-lsp lsp, which means that the CR-
LSP tunnel will be selected first, followed by
LSP Tunnel. The GRE Tunnel will not be
selected.

10.1.5 Checking configurations

No. Command Description
1 Raisecom#show mpls Show global MPLS configurations.
2 Raisecom#show mpls te tunnel Show Tunnel information.
3 Raisecom#show interface tunnel Show information about the Tunnel interface.
4 Raisecom#show mpls te hot-standby Show information about hot standby of the
state { all | interface tunnel Tunnel interface.
interface-number }

10.2 Configuring static LSP

10.2.1 Preparing for configurations

Scenario
The static LSP is established by the administrator by manually assigning labels for all FECs.
It is suitable for simple and stable small-size network. To manually assign labels, the outgoing
label value of the last node is the incoming label value of the next mode.
The static LSP does not use the label distribution protocol and does not exchange the control
packet. Therefore, it consumes fewer resources. However, the LSP, established by statically
assigning labels, cannot be dynamically adjusted according to the network topology changes.
The administrator needs to manually adjust the static LSP.

Prerequisite
Configure MPLS basic functions.

Raisecom Proprietary and Confidential

166
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

10.2.2 Configuring static unidirectional LSP with IP capability

Step Command Description
1 Raisecom#config Enter global configuration
mode.
2 Raisecom(config)#mpls static-lsp ingress lsp-name Configure the static
dest-network mask nexthop ip-address out-label out- unidirectional LSP Ingress
label lsr-id egress-lsr-id tunnel-id tunnel-id node.
3 Raisecom(config)#mpls static-lsp transit lsp-name in- Configure the static
label in-label nexthop ip-address out-label out-label unidirectional LSP Transit
lsr-id ingress-lsr-id egress-lsr-id tunnel-id tunnel- node.
id
4 Raisecom(config)#mpls static-lsp egress lsp-name in- Configure the static
label in-label lsr-id ingress-lsr-id tunnel-id unidirectional LSP Egress node.
tunnel-id
5 Raisecom(config)#mpls static-lsp egress lsp-name (Optional) configure the
diffserv-mode pipe [ exp-to-local-priority profile- differential service mode of the
number ] static unidirectional LSP Egress
Raisecom(config)#mpls static-lsp egress lsp-name node.
diffserv-mode uniform [ exp-to-local-priority
profile-number ]

10.2.3 Configuring static unidirectional LSP without IP capability

Step Command Description
1 Raisecom#config Enter global configuration
mode.
2 Raisecom(config)#mpls static-lsp ingress lsp-name Configure the static
dest-network nexthop-mac mac-address interface-type unidirectional LSP Ingress
interface-number out-label out-label lsr-id egress- node.
lsr-id tunnel-id tunnel-id
3 Raisecom(config)#mpls static-lsp transit lsp-name in- Configure the static
label in-label nexthop-mac mac-address interface-type unidirectional LSP Transit
interface-number out-label out-label lsr-id ingress- node.
lsr-id egress-lsr-id tunnel-id tunnel-id
4 Raisecom(config)#mpls static-lsp egress lsp-name in- Configure the static
label in-label lsr-id ingress-lsr-id tunnel-id unidirectional LSP Egress node.
tunnel-id
5 Raisecom(config)#mpls static-lsp egress lsp-name (Optional) configure the
diffserv-mode pipe [ exp-to-local-priority profile- differential service mode of the
number ] static unidirectional LSP Egress
Raisecom(config)#mpls static-lsp egress lsp-name node.
diffserv-mode uniform [ exp-to-local-priority
profile-number ]

Raisecom Proprietary and Confidential

167
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

10.2.4 Configuring static bidirectional LSP with IP capability

Configuring static bidirectional LSP Ingress node

Step Command Description
1 Raisecom#config Enter global configuration
mode.
2 Raisecom(config)#mpls bidirectional static-lsp Create the static bidirectional
ingress lsp-name lsr-id egress-lsr-id tunnel-id corouted LSP and enter Ingress
tunnel-id LSP (ILSP) configuration
mode.
3 Raisecom(config-ingress-lsp)#forward dest-network Configure the next hop of the
mask nexthop ip-address out-label out-label Ingress node forward LSP.

4 Raisecom(config-ingress-lsp)#backward in-label in- Configure the incoming label of

label the Ingress node backward LSP.

Configuring static bidirectional LSP Transit node

Step Command Description
1 Raisecom#config Enter global configuration
mode.
2 Raisecom(config)#mpls bidirectional static-lsp Create the static bidirectional
transit lsp-name lsr-id ingress-lsr-id egress-lsr-id corouted LSP and enter TLSP
tunnel-id tunnel-id configuration mode.
3 Raisecom(config-transit-lsp)#forward in-label in- Configure the next hop of the
label nexthop ip-address out-label out-label Transit node forward LSP.

4 Raisecom(config-transit-lsp)#backward in-label in- Configure the incoming label of

label nexthop ip-address out-label out-label the Transit node backward LSP.

Configuring static bidirectional LSP Egress node

Step Command Description
1 Raisecom#config Enter global configuration
mode.
2 Raisecom(config)#mpls bidirectional static-lsp egress Create the static bidirectional
lsp-name lsr-id ingress-lsr-id tunnel-id tunnel-id corouted LSP and enter ELSP
(ELSP) configuration mode.
3 Raisecom(config-egress-lsp)#forward in-label in-label Configure the incoming label of
the Egress node forward LSP.

Raisecom Proprietary and Confidential

168
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Step Command Description

4 Raisecom(config-ingress-lsp)#backward dest-network Configure the outgoing label of
mask nexthop ip-address out-label out-label the Egress node backward LSP.

10.2.5 Configuring static bidirectional LSP without IP capability

To configure static bidirectional LSP without IP capability, you must configure the
physical interface to Layer 3 physical interface mode; otherwise, the configuration will
fail.

Configuring static bidirectional LSP Ingress node

Step Command Description
1 Raisecom#config Enter global configuration
mode.
2 Raisecom(config)#mpls bidirectional static-lsp Create the static bidirectional
ingress lsp-name lsr-id egress-lsr-id tunnel-id corouted LSP and enter ILSP
tunnel-id configuration mode.
3 Raisecom(config-ingress-lsp)#forward dest-network Configure the next hop of the
[ mask ] nexthop-mac mac-address interface-type Ingress node forward LSP.
interface-number out-label out-label
4 Raisecom(config-ingress-lsp)#backward in-label in- Configure the incoming label of
label the Ingress node backward LSP.

Configuring static bidirectional LSP Transit node

Step Command Description
1 Raisecom#config Enter global configuration
mode.
2 Raisecom(config)#mpls bidirectional static-lsp Create the static bidirectional
transit lsp-name lsr-id ingress-lsr-id egress-lsr-id corouted LSP and enter Transit
tunnel-id tunnel-id LSP (TLSP) configuration
mode.
3 Raisecom(config-transit-lsp)#forward in-label in- Configure the next hop of the
label nexthop-mac mac-address interface-type Transit node forward LSP.
interface-number out-label out-label
4 Raisecom(config-transit-lsp)# Raisecom(config- Configure the next hop of the
transit-lsp)#backward in-label in-label nexthop-mac Transit node backward LSP.
mac-address interface-type interface-number out-label
out-label

Raisecom Proprietary and Confidential

169
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Configuring static bidirectional LSP Egress node

Step Command Description
1 Raisecom#config Enter global configuration
mode.
2 Raisecom(config)#mpls bidirectional static-lsp egress Create the static bidirectional
lsp-name lsr-id ingress-lsr-id tunnel-id tunnel-id corouted LSP and enter Egress
LSP configuration mode.
3 Raisecom(config-egress-lsp)#forward in-label in-label Configure the incoming label of
the Egress node forward LSP.
4 Raisecom(config-egress-lsp)#backward dest-network Configure the next hop of the
[ mask ] nexthop-mac mac-address interface-type Egress node backward LSP.
interface-number out-label out-label

10.2.6 Checking configurations

No. Command Description
1 Raisecom#show mpls lsp statistics Show all LSP configurations
2 Raisecom#show mpls bidirectional static-lsp Show static bidirectional LSP
[ lsp-name ] configurations.
3 Raisecom#show mpls static-lsp [ lsp-name ] Show static unidirectional LSP
Raisecom#show mpls static-lsp [ egress | ingress configurations.
| transit ]
4 Raisecom#show mpls lsp static [ ingress | transit Show configurations of static LSP.
| egress ]

10.3 Configuring LDP LSP

10.3.1 Preparing for configurations

Scenario
The LDP is used to dynamically assign labels for LSRs to establish the LSP dynamically. The
LDP is used to exchange label information among LSRs. Therefore, when forwarding the
packet, the LSR can add related Tag to the packet based on label requirement of the next-hop
LSP. Then, the packet can be processed properly at the next-hop LSR.

Prerequisite
Enable MPLS.

Raisecom Proprietary and Confidential

170
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

10.3.2 Configuring global LDP

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls ldp Enable global LDP.
3 Raisecom(config)#lsp-trigger { all | Configure the LDP to dynamically establish the
host | none } LSP trigger policy.

10.3.3 Configuring LDP on interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#mpls ldp Enable LDP on the interface.
4 Raisecom(config-port)#mpls ldp (Optional) set the transport address of the LDP
transport-address interface local session to the IP address of the current
interface.
By default, the transport address of the local
session is LSR ID.
5 Raisecom(config-port)#mpls ldp timer (Optional) configure the Hello-hold timer of the
hello-hold hello-time LDP remote session.
By default, the Hello-hold timer of the LDP remote
session is 45s.
6 Raisecom(config-port)#mpls ldp timer (Optional) configure the Keepalive-hold timer of
keepalive-hold keepalive-time the LDP remote session.
By default, the Keepalive-hold timer of the LDP
remote session is 45s.

10.3.4 Configuring LDP remote session

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls ldp Enable LDP remote discovery and enter remote neighbor
targeted neighbour ip- configuration mode.
address
3 Raisecom(config-ldp-remote- Configure the Hello-hold timer of the LDP remote session.
peer)#mpls ldp timer hello-
hold hello-time
By default, the Hello-hold timer of the LDP remote session is
45s.

Raisecom Proprietary and Confidential

171
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Step Command Description

4 Raisecom(config-ldp-remote- Configure the Keepalive-hold timer of the LDP remote session.
peer)#mpls ldp timer
keepalive-hold keepalive- By default, the Hello-hold timer of the LDP remote session is
time 45s.

10.3.5 Configuring LDP MD5

LDP Message Digest Algorithm 5 (MD5) encryption can generate the unique digest
information for the same information segment. LDP MD5 can implement LDP packet anti-
tampering check to improve information security. This encryption method is stricter than the
TCP in the general sense.
Configure the iTN8800 as below. Step 2 and step 3 can implement different encryption
functions respectively. Choose one as required.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls ldp md5- Configure LDP MD5 cleartext password.
password plain peer-ip-address
password Use the show running-config command to show
the cleartext password.
3 Raisecom(config)#mpls ldp md5- Configure LDP MD5 ciphertext password.
password cipher [ encrpty ] peer-ip-
address password Support cleartext and ciphertext inputs.
 For cleartext input, enter letters, numbers, and
characters. Use the show running-config
command to show the cleartext password which
is displayed in cleartext.
 For ciphertext password, enter the MD5 special
ciphertext password. Use the show running-
config command to show the password which is
displayed in ciphertext.

10.3.6 Configuring BFD for TLDP

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls ldp targeted Enable LDP remote discovery and enter remote
neighbour ip-address symmetric configuration mode.
3 Raisecom(config-ldp-remote-peer)#mpls Enable BFD for TLDP.
ldp bfd enable

Raisecom Proprietary and Confidential

172
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

10.3.7 Configuring LDP FRR

Automatic LDP FRR

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#auto-frr lsp-trigger Configure a policy that the backup route triggers
{ all | host | none } the LDP to create a backup LSP.
By default, the policy to create a backup LSP is
triggered based on host routes.

Static LDP FRR

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#mpls ldp frr Enable LDP FRR and specify the IP address of the
nexthop nexthop-address [ priority next hop.
priority ]
By default, LDP FRR is disabled.

10.3.8 Checking configurations

No. Command Description
1 Raisecom#show mpls ldp Show LDP global information.
2 Raisecom#show mpls ldp interface [ interface- Show LDP interface information.
type interface-number ] [ detail ]
3 Raisecom#show mpls ldp targeted neighbour ip- Show remote neighbor information.
address
4 Raisecom#show mpls ldp session [ detail ] Show LDP session information.
5 Raisecom#show mpls ldp peer Show LDP neighbor information.
6 Raisecom#show mpls ldp lsp Show LDP LSP information.
7 Raisecom#show mpls ldp adjacency Show LDP adjacency information.
8 Raisecom#show mpls lsp [ ldp ] [ ingress | Show master or backup LSP
transit | egress ] configurations.

Raisecom Proprietary and Confidential

173
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

10.4 Configuring MPLS TE

10.4.1 Preparing for configurations

Scenario
MPLS TE is for solving the traffic congestion on the link caused by unbalanced load which
cannot be resolved by traditional routing. It can accurately control traffic paths to avoid
congestion nodes, thus solving the problem of some paths being overloaded but some paths
being unoccupied.
RSVP is used for dynamically creating public network LSP tunnel in the MPLS TE. It can
create, maintain, and remove MPLS TE LSP and provide false alarm.
The device supports choosing the shortest path through Constraint-based Shortest Path First
(CSPE) and supports 32 neighbors at most.

Prerequisite
The MPLS is enabled.

10.4.2 Enabling RSVP-TE

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls rsvp-te Enable global RSVP-TE.
By default, it is disabled.
3 Raisecom(config)#interface Enter Layer 3 physical interface configuration mode.
interface-type interface-number
4 Raisecom(config-port)#mpls rsvp- Enable RSVP-TE on the Layer 3 physical interface.
te
By default, it is disabled.

10.4.3 Enabling CSPE

CSPE is the core of MPLS TE for choosing path and is mainly for calculating and establishing
path. MPLS-TE calculates the shortest path to various nodes on the network through CSPF
algorithm. The CSPF algorithm supports OSPF and ISIS and the multi-process of these two
protocols.

Step Command Description

1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

174
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Step Command Description

2 Raisecom(config)#cspf enable Enable CSPE.
[ isis-preferred | ospf-
 If you choose isis-preferred command, calculation will
preferred ]
be done based on ISIS.
 If you choose ospf-preferred, calculation will be done

based on OSPE protocol.

By default, it is disabled.
3 Raisecom(config)#router ospf process- Start an OSPF process and enter OSPF configuration
id [ vrf vrf-name ] [ router-id router-id ] mode.
4 Raisecom(config-router-ospf)#capability Enable OSPF opaque LSA.
opaque
By default, it is disabled.
5 Raisecom(config-router-ospf)#mpls Enable OSPF TE.
traffic-eng area area-id
By default, it is disabled.
6 Raisecom(config-router-ospf)#mpls Configure the ID of the MPLS-TE router.
traffic-eng router-id router-id

10.4.4 Configuring explicit path and Tunnel

step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls explicit-path Create MPLS-TE explicit path and enter explicit
path-name path configuration mode.
3 Raisecom(config-mpls-exp-path)#next-hop Specify the next node of the explicit path.
ip-address { exclude | loose | strict }
Raisecom(config-mpls-exp-path)#exit Exit explicit path configuration mode.
4 Raisecom(config)#interface tunnel Enter tunnel interface configuration mode.
interface-number
5 Raisecom(config-tunnel)#description (Optional) configure the description information
description about Tunnel interface.
6 Raisecom(config-tunnel)#destination ip- Configure the destination IP address on the
address Tunnel interface.
7 Raisecom(config-tunnel)#mpls signal- Configure the protocol type of Tunnel interface
protocol { rsvp-te | static } and choose RSVP-TE.
By default, it is static protocol.
8 Raisecom(config-tunnel)#mpls tunnel-id Configure Tunnel ID on the Tunnel interface.
tunnel-id
9 Raisecom(config-tunnelif)#mpls Configure binding Tunnel interface with explicit
explicit-path path-name [ secondary ] path or with backup explicit path.
Backup explicit path is used for LSP hot backup
protection.

Raisecom Proprietary and Confidential

175
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

step Command Description

10 Raisecom(config-tunnelif)#mpls te Hand configuration information about MPLS
commit Tunnel interface, including Tunnel ID and
destination IP address.
11 Raisecom(config)#mpls label-advertise Configure the label allocation mode popped up in
{ implicit-null | non-null } the last but one hop.

10.4.5 Configuring TE protection

Configuring FRR protection

The RSVP-TE is enabled and the explicit path and related function of Tunnel is configured.

step Command Description

1 Raisecom#config Enter global configuration mode.

2 Raisecom(config)#interface tunnel Enter Tunnel interface configuration mode.
interface-number
3 Raisecom(config-tunnel)#mpls signal- Configure the protocol type of Tunnel.
protocol { rsvp-te | static }
By default, it is static protocol.
4 Raisecom(config-tunnelif)#mpls te fast- Enable FRR on Tunnel interface.
reroute [ node-protect ]
By default, it is disabled.
5 Raisecom(config-tunnel)#mpls te bypass- (Optical) configure the current Tunnel to bypass
tunnel Tunnel.
6 Raisecom(config-tunnelif)#exit Exit Tunnel interface configuration mode.
7 Raisecom(config)#interface interface- Enter Layer 3 physical interface configuration
type interface-number mode.
Raisecom(config-port)#mpls te backup- Configure FRR bypass Tunnel on Layer 3
path tunnel interface-number physical interface.

Configuring LSP hot backup

The RSVP-TE is enabled and the explicit path and related function of Tunnel is configured.
Both step 3 and step 4 are for configuring hot backup. However, step 3 is for specifying
explicit path and step 4 is for automatic generation mode. If step 3 and step 4 are configured
together, step 3 will prevail.

step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter tunnel interface configuration mode.
tunnel interface-number

Raisecom Proprietary and Confidential

176
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

step Command Description

3 Raisecom(config- Specify the explicit path as the hot backup LSP and enable hot
tunnelif)#mpls explicit- backup protection.
path path-name secondary
4 Raisecom(config- (Optional) configure hot backup switch-back time on MPLS
tunnelif)#mpls te hot- tunnel interface. This function only takes effect on RSVP-TE.
standby wtr interval
By default, the WTR is 10s.

10.4.6 Configure BFD for RSVP-TE

step Command Description

1 Raisecom#config Enter global configuration mode.

2 Raisecom(config)#mpls rsvp-te bfd all-interface Enable BFD based on RSVP-TE
[ detect-multiplier detect-multiplier | min-rx- globally.
interval min-rx-interval | min-tx-interval min-tx-
interval ]
3 Raisecom(config)#interface interface-type interface- Enter interface configuration
number mode.
4 Raisecom(config-port)#mpls rsvp-te bfd Enable BFD based on RSVP-TE
on the interface.

10.4.7 Checking configurations

Step Command Description
1 Raisecom#show mpls rsvp-te Show status of RSVP-TE
globally.
2 Raisecom#show mpls rsvp-te interface [ interface- Show status of RSVP-TE on the
type interface-number ] interface.
3 Raisecom#show mpls rsvp-te session [ destination Show RSVP-TE session.
ip-address tunnel-id tunnel-id ]
4 Raisecom#show interface tunnel Show Tunnel interface.
5 Raisecom#show mpls te tunnel Show Tunnel.
6 Raisecom#show mpls te hot-standby state { all | Show hot backup on Tunnel
interface tunnel interface-number } interface.
7 Raisecom)#show mpls te bypass-tunnel [ interface- Show the bypass Tunnel.
number ]
8 Raisecom#show mpls explicit-path [ path-name ] Show explicit path.
9 Raisecom#show mpls te frr protecting [ bypass- Show FRR protection.
tunnel tunnel interface-number ]
10 Raisecom#show cspf tedb [ detail | ip-address ] Show TEDB database.

Raisecom Proprietary and Confidential

177
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Step Command Description

11 Raisecom#show mpls lsp rsvp-te [ ingress | transit Show MPLS-TE LSP
| egress ] configurations.

10.5 Configuring MPLS fault detection

10.5.1 Preparing for configurations

Scenario
At the MPLS control plane, you cannot detect the fault when the traffic is forwarded along the
LSP. However, you can acknowledge and locate the fault through Ping and Traceroute
operations.

Prerequisite
 Establish the path before the Ping test is performed.
 Establish the path before the Traceroute test is performed.

10.5.2 Configuring MPLS fault acknowledgment

Step Command Description
1 Raisecom#ping mpls ipv4 ip-address/mask [ generic ] [ nexthop ip- Configure the
address ] [ interval interval ] [ count count ] [ waittime MPLS LSP
seconds ] [ ttl ttl ] [ reply dscp dscp-value ] [ reply mode udp Ping test.
| reply mode udp-alert ] [ reply pad-tlv ] [ size size ] [ source
ip-address ] [ tc tc-value ]
2 Raisecom#ping mpls te tunnel tunnel-interface [ interval Configure the
interval ] [ count count ] [ waittime seconds ] [ ttl ttl ] MPLS Tunnel
[ reply dscp dscp-value ] [ reply mode udp | reply mode udp- Ping test.
alert ] [ reply pad-tlv ] [ size size ] [ source ip-address ]
[ tc tc-value ]
3 Raisecom#ping mpls vc-id vc-id destination ip-address [ interval Configure the
interval ] [ count count ] [ waittime seconds ] [ ttl ttl ] MPLS PW Ping
[ reply dscp dscp-value ] [ reply mode udp | reply mode udp-alert test.
| reply mode control-channel ] [ reply pad-tlv ] [ size size ]
[ source ip-address ] [ tc tc-value ]
4 Raisecom#ping mpls vsi vsi-name mac mac-address [ interval Configure the
interval ] [ count count ] [ waittime seconds ] [ ttl ttl ] MPLS VPLS
[ reply dscp dscp-value ] [ reply mode udp | reply mode udp-alert Ping test.
| reply mode control-channel ] [ reply pad-tlv ] [ size size ]
[ source ip-address ] [ tc tc-value ]

Raisecom Proprietary and Confidential

178
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

10.5.3 Configuring MPLS fault location

Step Command Description
1 Raisecom#traceroute mpls ipv4 ip-address/mask [ generic ] Configure the
[ nexthop ip-address ] [ waittime seconds ] [ maxttl ttl] [ reply MPLS LSP
dscp dscp-value ] [ reply mode udp | reply mode udp-alert ] Traceroute test.
[ reply pad-tlv ] [ source ip-address ] [ tc tc-value ] [ flags
fec ]
2 Raisecom#traceroute mpls te tunnel tunnel-interface [ waittime Configure the
seconds ] [ maxttl ttl] [ reply dscp dscp-value ] [ reply mode MPLS Tunnel
udp | reply mode udp-alert ] [ reply pad-tlv ] [ source ip- Traceroute test.
address ] [ tc tc-value ] [ flags fec ]
3 Raisecom#traceroute mpls vc-id vc-id destination ip-address Configure the
[ waittime seconds ] [ maxttl ttl] [ reply dscp dscp-value ] MPLS PW
[ reply mode udp | reply mode udp-alert ] [ reply pad-tlv ] Traceroute test.
[ source ip-address ] [ tc tc-value ] [ flags fec ]
4 Raisecom#traceroute mpls vsi vsi-name mac mac-address [ waittime Configure the
seconds ] [ maxttl ttl] [ reply dscp dscp-value ] [ reply mode MPLS VPLS
udp | reply mode udp-alert ] [ reply pad-tlv ] [ source ip- Traceroute test.
address ] [ tc tc-value ] [ flags fec ]

10.6 Configuring GRE Tunnel

10.6.1 Preparing for configurations

Scenario
MPLS L2VPN can be transmitted through multiple types of Tunnels, such as LSP, LDP LSP,
MPLS-TE, and Generic Routing Encapsulation (GRE) Tunnels. This chapter describes the
function of GRE Tunnel and the configuration process of Tunnel policy.
When configuring L2VPN, you need to select GRE as the Tunnel policy. The destination IP
address of the L2VPN services should be the same as that of the GRE Tunnel. Then L2VPN
services can be transmitted through GRE Tunnel.

Prerequisite
 Configure MPLS LSR-ID
 Enable MPLS.

The iTN8800-II-NXU (Version C or later) supports GRE.

10.6.2 Configuring GRE Tunnel basic functions

Step Command Description
1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

179
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Step Command Description

2 Raisecom(config)#interface tunnel tunnel-if Enter Tunnel interface configuration
mode.
3 Raisecom(config-tunnelif)#ip address ip- Configure the IP address of the Tunnel
address ip-mask interface.
4 Raisecom(config-tunnelif)#tunnel mode { gre | Configure Tunnel mode.
mpls }
By default, it is MPLS.
5 Raisecom(config-tunnelif)#source ip-address Configure the source IP address of the
GRE Tunnel interface.
6 Raisecom(config-tunnelif)#destination ip- Configure the destination IP address of
address the Tunnel interface.
7 Raisecom(config-tunnelif)#diffserv-mode Configure the differential service mode
{ pipe pipe | uniform [ local-priority-to- on the GRE Tunnel interface.
dscp Profile-number ] }
Raisecom(config-tunnelif)#exit Exit Tunnel interface configuration
mode.
8 Raisecom(config)#tunnel-policy policy-name Enter Tunnel policy configuration mode.
9 Raisecom(config-tunnelpolicy)#tunnel select- Configure selecting GRE as the Tunnel
seq gre policy.

10.6.3 Checking configurations

Step Command Description
1 Raisecom#show tunnel-policy policy-name Show configurations of the tunnel policy.
2 Raisecom#show interface tunnel [interface- Show configurations of the tunnel
number ] interface.

10.7 Configuring MPLS load balancing

10.7.1 Preparing for configurations

Scenario
When there are multiple equal-cost paths (ECMP, Equal-Cost MultiPath) between the start PE
and the end PE, the traffic load should be equally allocated on the equal-cost multipath to
implement load balancing of the network so that the network congestion is reduced and the
link bandwidth is fully used. When some of the paths fail, the traffic can be switched to other
paths for forwarding, thus implementing LSP path redundancy backup.

Raisecom Proprietary and Confidential

180
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

For the same forwarding equivalence class, LDP can receive different label mapping
information from different downstream nodes and create corresponding ingress nodes for
these different equal-cost paths. Meanwhile, LDP can send label mapping information to the
upstream nodes and create corresponding Transit nodes for different equal-cost paths, thereby
creating multiple equal-cost LSPs. The IP services that are forwarded from the device or the
services with the MPLS label can be forwarded to different LSPs according to the load
balancing mode to implement load balancing of the MPLS network.
If L2VPN and L3VPN services are needed, you can select multiple LSPs for load balancing
based on the configured tunnel policy.

Prerequisite
 Configure MPLS basic functions.
 Configure LDP LSP.
 Configure L2VPN or L3VPN and specify a tunnel policy.

10.7.2 Configuring MPLS load balancing parameters

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#tunnel-policy policy- Configure a tunnel policy.
name
Load balancing can be performed for L2VPN or
the L3VPN services according to the configured
tunnel policy. The name of the policy is the same
as that of the tunnel policy associated with the
L2VPN or L3VPN.
3 Raisecom(config-tunnelpoicy)#tunnel Configure the tunnel preference policy and the
select-seq { lsp | cr-lsp | gre } * number of tunnels for load balancing.
[ load-balance-number lsp-number ]
The configuration of LSPs, CR-LSPs, and GRE
tunnels can be in any sequence. The earlier the
configuration, the higher the priority.

10.7.3 Checking configurations

Step Command Description
1 Raisecom#show tunnel-policy [ policy-name ] Show information about the tunnel
policy.

Raisecom Proprietary and Confidential

181
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

10.8 Configuration examples

10.8.1 Example for configuring static bidirectional LSP without IP
capability

Networking requirements
As shown in Figure 10-1, the user has branches in areas A and B. Branches need to transmit
point-to-point VPN leased-line services. Because the network scale is small and the topology
is stable, you can configure bidirectional static LSP between PE A and PE B to work as the
public Tunnel of the L2VPN. By default, devices are configured with IP addresses.

Figure 10-1 Configuring static bidirectional LSP without IP capability

Data preparation
Table 10-1 shows data preparation.

Table 10-1 Data preparation

Device LSR-ID Interface IP address
PE A 192.168.1.1 gigaethernet 1/1/1 192.168.1.1/24

loopback 2 1.1.1.1/32

P 192.168.1.2 gigaethernet 1/1/1 192.168.1.2/24

gigaethernet 1/1/2 192.168.4.1/24
loopback 2 2.2.2.2/32
PE B 192.168.4.2 gigaethernet 1/1/1 192.168.4.2/24
loopback 2 3.3.3.3/32

Raisecom Proprietary and Confidential

182
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Configuration steps
Step 1 Configure the IP address of Loopback interface and network-side interface.
 The method for configuring the IP address of PEB and P is the same as that for
configuring PEA.

PEA#config
PEA(config)#interface loopback 2
PEA(config-loopback2)#ip address 1.1.1.1 255.255.255.255
PEA(config-loopback2)#interface gigaethernet 1/1/1
PEA(config-gigaethernet1/1/1)#ip address 192.168.1.1 255.255.255.0
PEA(config-gigaethernet1/1/1)#exit

Step 2 Enable MPLS.

 Configure PE A.

PEA(config)#mpls lsr-id 1.1.1.1

PEA(config)#mpls enable

 Configure P.

P(config)#mpls lsr-id 2.2.2.2

P(config)#mpls enable

 Configure PE B.

PEB(config)#mpls lsr-id 3.3.3.3

PEB(config)#mpls enable

Step 3 Configure Tunnel basic functions.

 Configure PE A.

PEA(config)#interface tunnel 1/1/1

PEA(config-tunnel1/1/1)#destination 192.168.4.2
PEA(config-tunnel1/1/1)#mpls tunnel-id 11
PEA(config-tunnel1/1/1)#mpls te commit
PEA(config-tunnel1/1/1)#exit

 Configure PE B.
PEB(config)#interface tunnel 1/1/1
Raisecom Proprietary and Confidential
183
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

PEB(config-tunnel1/1/1)#destination 192.168.1.1
PEB(config-tunnel1/1/1)#mpls tunnel-id 11PEB(config-tunnel1/1/1)#mpls te
commit
PEB(config-tunnel1/1/1)#exit

Step 4 Configure the static bidirectional LSP.

 Configure Ingress node PE A.

PEA(config)#mpls bidirectional static-lsp ingress lspAB lsr-id

192.168.4.2 tunnel-id 1
PEA(config-ingress-lsp)#forward 192.168.4.0 255.255.255.0 nexthop
192.168.1.2 gigaethernet 1/1/1 out-label 1001
PEA(config-ingress-lsp)#backward in-label 2001

 Configure Transit node P.

P(config)#mpls bidirectional static-lsp transit lspAB lsr-id 192.168.1.1

192.168.4.2 tunnel-id 1
P(config-transit-lsp)#forward in-label 1001 nexthop 192.168.4.2
gigaethernet 1/1/2 line 2 out-label 1002
P(config-transit-lsp)#backward in-label 2002 nexthop 192.168.1.1
gigaethernet 1/1/1 out-label 2001

 Configure Egress node PE B.

PEB(config)#mpls bidirectional static-lsp egress lspAB lsr-id 192.168.1.1

tunnel-id 1
PEB(config-egress-lsp)#forward in-label 1002
PEB(config-egress-lsp)#backward 192.168.1.0 255.255.255.0 nexthop
192.168.4.1 gigaethernet 1/1/1 out-label 2002

Checking configurations
Use the show mpls bidirectional static-lsp command to show configurations of the static
bidirectional LSP on PE A, P, and PE B.
 Configurations on Ingress node PE A are shown as below.

PEA(config)#show mpls bidirectional static-lsp lspAB

LSP-Index: 1
LSP-Name: lspAB
LSR-Role: Ingress
LSP-Flag: Working
Ingress-Lsr-Id: 192.168.1.1

Raisecom Proprietary and Confidential

184
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Egress-Lsr-Id: 192.168.4.2
Forward Destination: 192.168.4.0
Forward In-Label: --
Forward Out-Label: 1001
Forward In-Interface: --
Forward Out-Interface: gigaethernet1/1/1
Forward Next-Hop: --
Forward Next-Mac: 000E.5E11.1112
Forward Vlan-Id: --
Forward XcIndex: 1
Forward Ds mode: Uniform
Forward PipeServClass: --
Forward Exp2LocalPriMap: 0
Forward LocalPri2ExpMap: 0
Backward Destination: --
Backward In-Label: 2001
Backward Out-Label: --
Backward In-Interface: all interfaces
Backward Out-Interface: --
Backward Next-Hop: --
Backward Next-Mac: --
Backward Vlan-Id: --
Backward XcIndex: 1
Backward Ds mode: Uniform
Backward PipeServClass: --
Backward Exp2LocalPriMap: 0
Backward LocalPri2ExpMap: 0
Tunnel-Id: 1
LSP Status: Down

 Configurations on Transit node P are shown as below.

P(config)#show mpls bidirectional static-lsp lspAB

LSP-Index: 1
LSP-Name: lspAB
LSR-Role: Transit
LSP-Flag: Working
Ingress-Lsr-Id: 192.168.1.1
Egress-Lsr-Id: 192.168.4.2
Forward Destination: --
Forward In-Label: 1001
Forward Out-Label: 1002
Forward In-Interface: all interfaces
Forward Out-Interface: gigaethernet1/1/2
Forward Next-Hop: --
Forward Next-Mac: 000E.5E11.1113
Forward Vlan-Id: --
Forward XcIndex: 7
Forward Ds mode: Uniform
Forward PipeServClass: --
Forward Exp2LocalPriMap: 0
Forward LocalPri2ExpMap: 0
Backward Destination: --

Raisecom Proprietary and Confidential

185
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Backward In-Label: 2002

Backward Out-Label: 2001
Backward In-Interface: all interfaces
Backward Out-Interface: gigaethernet1/1/1
Backward Next-Hop: --
Backward Next-Mac: 000E.5E11.1111
Backward Vlan-Id: --
Backward XcIndex: 8
Backward Ds mode: Uniform
Backward PipeServClass: --
Backward Exp2LocalPriMap: 0
Backward LocalPri2ExpMap: 0
Tunnel-Id: 1
LSP Status: Down

 Configurations on Egress node PE B are shown as below.

PEB(config)#show mpls bidirectional static-lsp lspAB

LSP-Index: 1
LSP-Name: lspAB
LSR-Role: Egress
LSP-Flag: Working
Ingress-Lsr-Id: 192.168.1.1
Egress-Lsr-Id: 192.168.4.2
Forward Destination: --
Forward In-Label: 1002
Forward Out-Label: --
Forward In-Interface: all interfaces
Forward Out-Interface: --
Forward Next-Hop: --
Forward Next-Mac: --
Forward Vlan-Id: --
Forward XcIndex: 9
Forward Ds mode: Uniform
Forward PipeServClass: --
Forward Exp2LocalPriMap: 0
Forward LocalPri2ExpMap: 0
Backward Destination: 192.168.1.0
Backward In-Label: --
Backward Out-Label: 2002
Backward In-Interface: --
Backward Out-Interface: gigaethernet1/1/1
Backward Next-Hop: --
Backward Next-Mac: 000E.5E11.1112
Backward Vlan-Id: --
Backward XcIndex: 10
Backward Ds mode: Uniform
Backward PipeServClass: --
Backward Exp2LocalPriMap: 0
Backward LocalPri2ExpMap: 0
Tunnel-Id: 1
LSP Status: Down

Raisecom Proprietary and Confidential

186
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

10.8.2 Example for configuring LDP-based dynamic LSP

Networking requirements
As shown in Figure 10-2, the user has branches in areas A and B. Branches need to transmit
point-to-point VPN leased-line services. To facilitate network maintenance and reduce manual
intervention, you can configure the dynamic LSP between PE A and PE B to work as the
public Tunnel of the L2VPN. By default, devices are configured with IP addresses.

Figure 10-2 Configuring LDP-based dynamic LSP

Data preparation
Table 10-2 shows data preparation.

Table 10-2 Data preparation

Device LSR-ID Interface IP address
PE A 1.1.1.1 gigaethernet 1/1/1 192.168.1.1/24

loopback 2 1.1.1.1/32

P 2.2.2.2 gigaethernet 1/1/1 192.168.1.2/24

gigaethernet 1/1/2 192.168.4.1/24
loopback 2 2.2.2.2/32
PE B 3.3.3.3 gigaethernet 1/1/1 192.168.4.2/24
loopback 2 3.3.3.3/32

Configuration steps
Step 1 Enable MPLS and LDP globally.
 Configure PE A.

PEA(config)#mpls lsr-id 1.1.1.1

Raisecom Proprietary and Confidential

187
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

PEA(config)#mpls enable
PEA(config)#mpls ldp

 Configure P.

P(config)#mpls lsr-id 2.2.2.2

P(config)#mpls enable
P(config)#mpls ldp
 Configure PE B.

PEB(config)#mpls lsr-id 3.3.3.3

PEB(config)#mpls enable
PEB(config)#mpls ldp

Step 2 Enable LDP on the interface and configure LDP basic properties.
 Configure PE A.

PEA(config)#interface gigaethernet 1/1/1

PEA(config-port)#ip address 192.168.1.1 255.255.255.0
PEA(config-port)#mpls ldp
PEA(config-port)#mpls ldp timer hello-hold 3
PEA(config-port)#mpls ldp timer keepalive-hold 30
PEA(config-port)#exit

 Configure P.

P(config)#interface gigaethernet 1/1/1

P(config-port)#ip address 192.168.1.2 255.255.255.0
P(config-port)#mpls ldp
P(config-port)#mpls ldp timer hello-hold 3
P(config-port)#interface gigaethernet 1/1/2
P(config-port)#ip address 192.168.4.1 255.255.255.0
P(config-port)#mpls enable
P(config-port)#mpls ldp
P(config-port)#exit

 Configure PE B.

PEB(config)#interface gigaethernet 1/1/1

PEB(config-port)#ip address 192.168.4.2 255.255.255.0
PEB(config-port)#mpls ldp

Raisecom Proprietary and Confidential

188
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Step 3 PEB(config-port)#exitConfigure the IP address of the Loopback interface and OSPF route.
 Configure PE A.

PEA(config)#interface loopback 2
PEA(config-loopbackif)#ip address 192.168.1.1 255.255.255.0
PEA(config-loopbackif)#exit
PEA(config)#router ospf 1
PEA(config-router-ospf)#network 192.168.1.1 255.255.255.255 0.0.0.0
PEA(config-router-ospf)#network 1.1.1.1 255.255.255.255 0.0.0.0
PEA(config-router-ospf)#exit

 Configure P.

P(config)#interface loopback 2
P(config-loopbackif)#ip address 192.168.1.2
P(config)#router ospf 1
P(config-router-ospf)#network 2.2.2.2 255.255.255.255 area 0.0.0.0
P(config-router-ospf)#network 192.168.1.2 255.255.255.255 area 0.0.0.0
P(config-router-ospf)#network 192.168.4.1 255.255.255.255 area 0.0.0.0
P(config-router-ospf)#exit

 Configure PE B.

PEB(config)#interface loopback 2
PEB(config-loopbackif)#ip address 192.168.4.2 255.255.255.0
PEB(config)#router ospf 1
PEB(config-router-ospf)#network 3.3.3.3 255.255.255.255 area 0.0.0.0
PEB(config-router-ospf)#network 192.168.4.2 255.255.255.255 area 0.0.0.0
PEB(config-router-ospf)#exit

Checking results
Use the show mpls lsp ldp command to show LSP configurations on PE A, P, and PE B.

10.8.3 Example for configuring RSVP-TE-based dynamic LSP

Networking requirements
As shown in Figure 10-3, the user has branches in areas A and B, which communicate with
each other by exchanging point-to-point VPN leased-line services. To provide accurate
bandwidth guarantee, you can configure the RSVP-TE LSP between PE A and PE B to work
as the public Tunnel of the L2VPN. By default, devices are configured with IP addresses.

Raisecom Proprietary and Confidential

189
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Figure 10-3 Configuring RSVP-TE-based dynamic LSP

Data preparation
Table 10-3 shows data preparation.

Table 10-3 Data preparation

Device LSR-ID Interface IP address
PE A 1.1.1.1 gigaethernet 1/1/1 192.168.1.1/24

loopback 2 1.1.1.1/32

P 2.2.2.2 gigaethernet 1/1/1 192.168.1.2/24

gigaethernet 1/1/2 192.168.4.1/24
loopback 2 2.2.2.2/32
PE B 3.3.3.3 gigaethernet 1/1/1 192.168.4.2/24
loopback 2 3.3.3.3/32

Configuration steps
Step 1 Configure RSVP-TE basic functions.
 Configure PE A.

PEA(config)#mpls lsr-id 1.1.1.1

PEA(config)#mpls enable
PEA(config)#mpls rsvp-te
PEA(config)#interface gigaethernet 1/1/1
PEA(config-port)#ip address 192.168.1.1 255.255.255.0
PEA(config-port)#mpls enable
PEA(config-port)#mpls rsvp-te
PEA(config-port)#exit

 Configure P.

Raisecom Proprietary and Confidential

190
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

P(config)#mpls lsr-id 2.2.2.2.2

P(config)#mpls enable
P(config)#mpls rsvp-te
P(config)#interface gigaethernet 1/1/1
P(config-port)#ip address 192.168.1.2 255.255.255.0
P(config-port)#mpls enable
P(config-port)#mpls rsvp-te
P(config-port)#interface gigaethernet 1/1/2
P(config-port)#ip address 192.168.4.1 255.255.255.0
P(config-port)#mpls enable
P(config-port)#rsvp-te
P(config-port)#exit
 Configure PE B.

PEB(config)#mpls lsr-id 3.3.3.3

PEB(config)#mpls enable
PEB(config)#mpls rsvp-te
PEB(config)#interface gigaethernet 1/1/1
PEB(config-port)#ip address 192.168.4.2 255.255.255.0
PEB(config-port)#mpls enable
PEB(config-port)#mpls rsvp-te
PEB(config-port)#exit

Step 2 Configure the explicit path.

 Configure PE A.

PEA(config)#mpls explicit-path PathAB

PEA(config-mpls-exp-path)#next-hop 192.168.1.2 strict
PEA(config-mpls-exp-path)#next-hop 192.168.4.2 strict

 Configure PE B.

PEB(config)#mpls explicit-path PathBA

PEB(config-mpls-exp-path)#next-hop 192.168.4.1 strict
PEB(config-mpls-exp-path)#next-hop 192.168.1.1 strict

Step 3 Configure the RSVP-TE Tunnel.

 Configure PE A.

PEA(config)#interface tunnel 1/1/1

PEA(config-tunnel1/1/1)#destination 192.168.4.2
PEA(config-tunnel1/1/1)#mpls signal-protocol rsvp-te
PEA(config-tunnel1/1/1)#mpls tunnel-id 101
PEA(config-tunnel1/1/1)#mpls explicit-path PathAB

Raisecom Proprietary and Confidential

191
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

PEA(config-tunnel1/1/1)#mpls te commit

 Configure PE B.

PEB(config)#interface tunnel 1/1/1

PEB(config-tunnel1/1/1)#destination 192.168.1.1
PEB(config-tunnel1/1/1)#mpls signal-protocol rsvp-te
PEB(config-tunnel1/1/1)#mpls tunnel-id 101
PEB(config-tunnel1/1/1)#mpls explicit-path PathAB
PEB(config-tunnel1/1/1)#mpls te commit

Checking results
Use the show mpls rsvp-te lsp command to show LSP configurations on PE A, P, and PE B.
 Configurations on PE A

PEA(config)#show mpls rsvp-te lsp

 Configurations on P

P(config)#show mpls rsvp-te lsp

 Configurations on PE B

PEB(config)#show mpls rsvp-te lsp

10.8.4 Example for configuring manual LDP FRR

Networking requirements
Manual LDP FRR is suitable for the stable networks with simple structure. As shown in
Figure 10-4, iTN A↔iTN B serves as the active LDP LSP link while the iTN A↔iTN
C↔iTN B serves as the standby LDP LSP link. When links between iTN A↔iTN B fail, the
devices are required to fast respond to the faults and switch services to the standby route iTN
A↔iTN C↔iTN B to recover services as soon as possible.
After manual LDP FRR is configured, a standby LSP link will be generated. Therefore, when
the active link fails, services can be fast switched to the standby link.

Raisecom Proprietary and Confidential

192
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

The following example shows the manual configuration of LDP FRR. This
configuration will generate a unidirectional backup LSP. For the peer device, the
configuration of generating a backup LSP is similar.

Figure 10-4 Configuring manual LDP FRR

Configuration principle
 Enable OSPF routes on each device respectively and make routes among devices
available.
 Configure LDP sessions on each device respectively and create LDP LSP.
 Configure LDP FRR on the active LSP interface of iTN A and specify the next hop IP
address of the standby FRR LSP.
 Configure dynamic BFD LDP LSP on iTN A and iTN B to implement fast detection of
LSP faults.

Data preparation
Table 10-4 lists the data required for configuring manual LDP FRR.

Table 10-4 Data required for configuring manual LDP FRR

Device Route-ID Interface IP address
iTN A 1.1.1.1 gigaethernet 1/1/1.10 10.10.10.1/24
gigaethernet 1/1/2.20 20.10.10.1/24
loopback 2 1.1.1.1/32
iTN B 2.2.2.2 gigaethernet 1/1/1.10 10.10.10.2/24
gigaethernet 1/1/2.20 30.10.10.2/24
loopback 2 2.2.2.2/32
iTN C 3.3.3.3 gigaethernet 1/1/1.20 20.10.10.2/24
gigaethernet 1/1/2.20 30.10.10.1/24
loopback 2 3.3.3.3/32

Raisecom Proprietary and Confidential

193
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Configuration steps
Step 1 Configure the IP address of the interface.
iTN A

iTNA#config
iTNA(config)#interface loopback 2
iTNA(config-loopback2)#ip address 1.1.1.1 255.255.255.255
iTNA(config-loopback2)#interface gigaethernet 1/1/1.10
iTNA(config-gigaethernet1/1/1.10)#encapsulation dot1Q 10
iTNA(config-gigaethernet1/1/1.10)#ip address 10.10.10.1 255.255.255.0
iTNA(config-gigaethernet1/1/1.10)#interface gigaethernet 1/1/2.20
iTNA(config-gigaethernet1/1/2.20)#encapsulation dot1Q 20
iTNA(config-gigaethernet1/1/2.20)#ip address 20.10.10.1 255.255.255.0
iTNA(config-gigaethernet1/1/2.20)#exit

iTN B

iTNB#config
iTNB(config)#interface loopback 2
iTNB(config-loopback2)#ip address 2.2.2.2 255.255.255.255
iTNB(config-loopback2)#interface gigaethernet 1/1/1.10
iTNB(config-gigaethernet1/1/1.10)#encapsulation dot1Q 10
iTNB(config-gigaethernet1/1/1.10)#ip address 10.10.10.2 255.255.255.0
iTNB(config-gigaethernet1/1/1.10)#interface gigaethernet 1/1/2.20
iTNB(config-gigaethernet1/1/2.20)#encapsulation dot1Q 20
iTNB(config-gigaethernet1/1/2.20)#ip address 30.10.10.2 255.255.255.0
iTNB(config-gigaethernet1/1/2.20)#exit

iTN C

iTNC#config
iTNC(config)#interface loopback 2
iTNC(config-loopback2)#ip address 3.3.3.3 255.255.255.255
iTNC(config-loopback2)#interface gigaethernet 1/1/1.20
iTNC(config-gigaethernet1/1/1.20)#encapsulation dot1Q 10
iTNC(config-gigaethernet1/1/1.20)#ip address 20.10.10.2 255.255.255.0
iTNC(config-gigaethernet1/1/1.20)#interface gigaethernet 1/1/2.20
iTNC(config-gigaethernet1/1/2.20)#encapsulation dot1Q 20
iTNC(config-gigaethernet1/1/2.20)#ip address 30.10.10.1 255.255.255.0
iTNC(config-gigaethernet1/1/2.20)#exit

Step 2 Start an OSPF process, define the interface or network which participates in the OSPF process,
and specify the local area of the interface or network.
iTN A

Raisecom Proprietary and Confidential

194
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

iTNA(config)#router ospf 1
iTNA(config-router-ospf)#network 1.1.1.1 0.0.0.0 area 0
iTNA(config-router-ospf)#network 10.10.10.1 0.0.0.255 area 0
iTNA(config-router-ospf)#network 20.10.10.1 0.0.0.255 area 0
iTNA(config-router-ospf)#exit

iTN B

iTNB(config)#router ospf 1
iTNB(config-router-ospf)#network 2.2.2.2 0.0.0.0 area 0
iTNB(config-router-ospf)#network 10.10.10.2 0.0.0.255 area 0
iTNB(config-router-ospf)#network 30.10.10.2 0.0.0.255 area 0
iTNB(config-router-ospf)#exit

iTN C

iTNC(config)#router ospf 1
iTNC(config-router-ospf)#network 3.3.3.3 0.0.0.0 area 0
iTNC(config-router-ospf)#network 20.10.10.2 0.0.0.255 area 0
iTNC(config-router-ospf)#network 30.10.10.1 0.0.0.255 area 0
iTNC(config-router-ospf)#exit
iTNC(config)#interface gigaethernet 1/1/1.20
/*enter the interface which connects iTN A.*/
iTNC(config-gigaethernet1/1/1.20)#ip ospf cost 10
/*configure the cost value which ensures that the data can optimally
select the active link and arrive at the peer device iTN A.*/
iTNC(config-gigaethernet1/1/1.20)#interface gigaethernet 1/1/2.20
/*enter the interface which connects iTN B.*/
iTNC(config-gigaethernet1/1/2.20)#ip ospf cost 10
/* configure the cost value which ensures that the data can optimally
select the active link and arrive at the peer device iTN B.*/

Step 3 Configure LDP LSP.

iTN A

iTNA(config)#mpls lsr-id 1.1.1.1

iTNA(config)#mpls enable
iTNA(config)#mpls ldp
/*enable global LDP.*/
iTNA(config)#interface gigaethernet 1/1/1.10
iTNA(config-gigaethernet1/1/1.10)#mpls ldp
/*enable LDP on the interface.*/
iTNA(config-gigaethernet1/1/1.10)#interface gigaethernet 1/1/2.20
iTNA(config-gigaethernet1/1/2.20)#mpls ldp
/*enable LDP on the interface.*/
iTNA(config-gigaethernet1/1/2.20)#exit

Raisecom Proprietary and Confidential

195
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

iTN B

iTNB(config)#mpls lsr-id 2.2.2.2

iTNB(config)#mpls enable
iTNB(config)#mpls ldp
/*enable global LDP.*/
iTNB(config)#interface gigaethernet 1/1/1.10
iTNB(config-gigaethernet1/1/1.10)#mpls ldp
/*enable LDP on the interface.*/
iTNB(config-gigaethernet1/1/1.10)#interface gigaethernet 1/1/2.20
iTNB(config-gigaethernet1/1/2.20)#mpls ldp
/*enable LDP on the interface.*/
iTNB(config-gigaethernet1/1/2.20)#exit

iTN C

iTNC(config)#mpls lsr-id 3.3.3.3

iTNC(config)#mpls enable
iTNC(config)#mpls ldp
/*enable global LDP.*/
iTNC(config)#interface gigaethernet 1/1/1.20
iTNC(config-gigaethernet1/1/1.20)#mpls ldp
/*enable LDP on the interface.*/
iTNC(config-gigaethernet1/1/1.20)#interface gigaethernet 1/1/2.20
iTNC(config-gigaethernet1/1/2.20)#mpls ldp
/*enable LDP on the interface.*/
iTNC(config-gigaethernet1/1/2.20)#exit

Step 4 Configure LDP FRR manually on the active LDP LSP interface on the iTN A and specify the
next-hop IP address. After a standby LSP path is generated, specify the next hop IP address.

iTNA(config)#interface gigaethernet 1/1/1.10

/*you must configure standby LSP on the active LSP interface.*/
iTNA(config-gigaethernet1/1/1.10)#mpls ldp frr nexthop 20.10.10.2
iTNA(config-gigaethernet1/1/1.10)#exit

Step 5 (Enabled by default, optional) trigger the device to assign a LSP label for the host route IP
prefix.
iTN A

iTNA(config)#lsp-trigger host

iTN B

Raisecom Proprietary and Confidential

196
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

iTNB(config)#lsp-trigger host

iTN C

iTNc(config)#lsp-trigger host

Step 6 Configure BFD for single-hop IP address on iTN A and iTN B to fast detect LSP faults and
switch services.
iTN A

iTNA(config)#bfd 1 bind peer-ip default-ip interface gigaethernet

1/1/1.10
/*manual LDP FRR only responds to BFD for single-hop default-ip.*/
iTNA(config-bfd-session)#session enable
iTNA(config-bfd-session)#exit

iTN B

iTNB(config)#bfd 1 bind peer-ip default-ip interface gigaethernet

1/1/1.10
iTNB(config-bfd-session)#session enable
iTNB(config-bfd-session)#exit

Checking results
 Use the show ip route command to show the routing table learned by each node.

iTNA(config)#show ip route
Routing Tables: Default-IP-Routing-Table
-------------------------------------------------------------------------
--
Flag: C - connected, S - static, R - RIP, B - BGP, O - OSPF, I - IS-IS
P - Protocol, s - States, > - selected , * - active, Dis - Distance
P&s Destination/Mask Dis/Metric NextHop Age Interface
C>* 1.0.0.0/8 0/0 1.1.1.1 01w2d02h Loopback2
C>* 1.1.1.1/32 0/0 127.0.0.1 01w2d02h lo0
O>* 2.2.2.2/32 110/2 10.10.10.2 02:56:23 GE1/1/1.10
O>* 3.3.3.3/32 110/2 20.10.10.2 00:09:04 GE1/1/2.20
C>* 20.10.10.0/24 0/0 20.10.10.1 01w0d22h GE1/1/2.20
C>* 20.10.10.1/32 0/0 127.0.0.1 01w0d22h lo0
O>* 30.10.10.0/24 110/2 10.10.10.2 00:09:04 GE1/1/1.10

 Use the show mpls lsp command to show the creation status of LDP FRR standby path.

Raisecom Proprietary and Confidential

197
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

iTNA(config)#show mpls lsp

LSR-Type FEC In/Out-Label In/Out-IF Next-Hop
LSP-Status LSP-Type LSP-Flag XCIndex
-------------------------------------------------------------------------
------------------------------------------------------
Egress 1.1.1.1 10391/-- all interfaces/-- --
Up Ldp Working 210
Ingress 2.2.2.2 --/10377 --/GE1/1/1.10
10.10.10.2 Up Ldp Working 214
/*Active LSP path*/
***LDP FRR*** --/10410 --/GE1/1/2.20
20.10.10.2 Up Ldp Working 223
/*LDP FRR standby LSP path*/
Egress 1.1.1.1 10395/-- all interfaces/-- --
Up Ldp Working 215

Common questions
When creating LDP FRR standby path fails, you can operate as below:
 Check whether the IP address of the interface is correctly configured.
 Check whether there is a route to the destination network in the routing table.
 Check whether the egress interface of the routes is the corresponding service interface.
 Check whether the next-hop address of the specified LDP FRR is the IP address of the
service interface of the standby device.

10.8.5 Example for configuring automatic LDP FRR

Networking requirements
As shown in Figure 10-5, enable automatic LDP LSP on the links between iTN A and iTN C.
When links between iTN A↔iTN B↔iTN C fail, the devices are required to fast respond to
the faults and switch services to the standby LSP link which passes through iTN D to recover
services as soon as possible.
After automatic LDP FRR is configured, a standby LSP path will be generated. Therefore,
when the active link fails, services can be fast switched to the standby LSP link, which
protects the active link and avoids data loss.

The following example shows the process of automatic LDP FRR configurations. This
configuration will generate a unidirectional backup LSP. For the peer device, the
configuration of generating a backup LSP is similar.

Raisecom Proprietary and Confidential

198
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Figure 10-5 Configuring automatic LDP FRR

Configuration principle
 Enable OSPF routes on each device respectively and make routes among devices
available.
 Configure LDP sessions on each device respectively and create LDP LSP.
 Configure a routing policy on iTN A and iTN C respectively, enable IP FRR, and
meanwhile apply the policy.
 Configure dynamic BFD LDP LSP on iTN A, iTN B, and iTN C to implement fast
detection of LSP faults.
 Configure all devices to assign active/standby LSP labels based on IP prefix.

Data preparation
Table 10-5 lists the data required for configuring automatic LDP FRR.

Table 10-5 Data required for configuring automatic LDP FRR

Device Route-ID Interface IP address
iTN A 1.1.1.1 gigaethernet 1/1/1 10.10.10.1/24
gigaethernet 1/1/2 30.10.10.1/24
loopback 2 1.1.1.1/32
iTN B 2.2.2.2 gigaethernet 1/1/1 10.10.10.2/24
gigaethernet 1/1/2 20.10.10.1/24
loopback 2 2.2.2.2/32
iTN C 3.3.3.3 gigaethernet 1/1/1 20.10.10.2/24
gigaethernet 1/1/2 40.10.10.2/24
loopback 2 3.3.3.3/32
iTN D 4.4.4.4 gigaethernet 1/1/1 30.10.10.2/24
gigaethernet 1/1/2 40.10.10.1/24
loopback 2 4.4.4.4/32

Raisecom Proprietary and Confidential

199
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Configuration steps
Step 1 Configure the IP address of the interface.
iTN A

iTNA#config
iTNA(config)#interface loopback 2
iTNA(config-loopback2)#ip address 1.1.1.1 255.255.255.255
iTNA(config-loopback2)#interface gigaethernet 1/1/1
iTNA(config-gigaethernet1/1/1)#ip address 10.10.10.1 255.255.255.0
iTNA(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
iTNA(config-gigaethernet1/1/2)#ip address 30.10.10.1 255.255.255.0
iTNA(config-gigaethernet1/1/2)#exit

iTN B

iTNB#config
iTNB(config)#interface loopback 2
iTNB(config-loopback2)#ip address 2.2.2.2 255.255.255.255
iTNB(config-loopback2)#interface gigaethernet 1/1/1
iTNB(config-gigaethernet1/1/1)#ip address 10.10.10.2 255.255.255.0
iTNB(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
iTNB(config-gigaethernet1/1/2)#ip address 20.10.10.1 255.255.255.0
iTNB(config-gigaethernet1/1/2)#exit

iTN C

iTNC#config
iTNC(config)#interface loopback 2
iTNC(config-loopback2)#ip address 3.3.3.3 255.255.255.255
iTNC(config-loopback2)#interface gigaethernet 1/1/1
iTNC(config-gigaethernet1/1/1)#ip address 20.10.10.2 255.255.255.0
iTNC(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
iTNC(config-gigaethernet1/1/2)#ip address 40.10.10.2 255.255.255.0
iTNC(config-gigaethernet1/1/2)#exit

iTN D

iTND#config
iTND(config)#interface loopback 2
iTND(config-loopback2)#ip address 4.4.4.4 255.255.255.255
iTND(config-loopback2)#interface gigaethernet 1/1/1
iTND(config-gigaethernet1/1/1)#ip address 30.10.10.2 255.255.255.0
iTND(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
iTND(config-gigaethernet1/1/2)#ip address 40.10.10.1 255.255.255.0

Raisecom Proprietary and Confidential

200
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

iTND(config-gigaethernet1/1/2)#exit

Step 2 Create an OSPF routing process, and define the interface or network on which OSPF runs and
the local area of the interface or network.
iTN A

iTNA(config)#router opsf 1
iTNA(config-router-ospf)#network 1.1.1.1 0.0.0.0 area 0
iTNA(config-router-ospf)#network 10.10.10.1 0.0.0.0 area 0
iTNA(config-router-ospf)#network 30.10.10.1 0.0.0.0 area 0
iTNA(config-router-ospf)#exit

iTN B

iTNB(config)#router opsf 1
iTNB(config-router-ospf)#network 2.2.2.2 0.0.0.0 area 0
iTNB(config-router-ospf)#network 10.10.10.2 0.0.0.0 area 0
iTNB(config-router-ospf)#network 20.10.10.1 0.0.0.0 area 0
iTNB(config-router-ospf)#exit

iTN C

iTNC(config)#router opsf 1
iTNCconfig-router-ospf)#network 3.3.3.3 0.0.0.0 area 0
iTNC(config-router-ospf)#network 20.10.10.2 0.0.0.0 area 0
iTNC(config-router-ospf)#network 40.10.10.2 0.0.0.0 area 0
iTNC(config-router-ospf)#exit

iTN D

iTND(config)#router opsf 1
iTND(config-router-ospf)#network 4.4.4.4 0.0.0.0 area 0
iTND(config-router-ospf)#network 30.10.10.2 0.0.0.0 area 0
iTND(config-router-ospf)#network 40.10.10.1 0.0.0.0 area 0
iTND(config-router-ospf)#exit

Step 3 Configure LDP LSP.

iTN A

iTNA(config)#mpls lsr-id 1.1.1.1

iTNA(config)#mpls enable

Raisecom Proprietary and Confidential

201
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

iTNA(config)#mpls ldp
/*enable LDP globally.*/
iTNA(config)#interface gigaethernet 1/1/1
iTNA(config-gigaethernet1/1/1)#mpls ldp
/*enable LDP on the interface*/
iTNA(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
iTNA(config-gigaethernet1/1/2)#mpls ldp
/*enable LDP on the interface.*/

iTN B

iTNB(config)#mpls lsr-id 2.2.2.2

iTNB(config)#mpls enable
iTNB(config)#mpls ldp
/*enable LDP globally.*/
iTNB(config)#interface gigaethernet 1/1/1
iTNB(config-gigaethernet1/1/1)#mpls ldp
/*enable LDP on the interface.*/
iTNB(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
iTNB(config-gigaethernet1/1/2)#mpls ldp
/*enable LDP on the interface.*/

iTN C
iTNC(config)#mpls lsr-id 3.3.3.3
iTNC(config)#mpls enable
iTNC(config)#mpls ldp
/*enable LDP globally.*/
iTNC(config)#interface gigaethernet 1/1/1
iTNC(config-gigaethernet1/1/1)#mpls ldp
/*enable LDP on the interface.*/
iTNC(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
iTNC(config-gigaethernet1/1/2)#mpls ldp
/*enable LDP on the interface.P*/

iTN D

iTND(config)#mpls lsr-id 4.4.4

iTND(config)#mpls enable
iTND(config)#mpls ldp
/*enable LDP globally.*/
iTND(config)#interface gigaethernet 1/1/1
iTND(config-gigaethernet1/1/1)#mpls ldp
/*enable LDP on the interface.*/
iTND(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
iTND(config-gigaethernet1/1/2)#mpls ldp
/*enable LDP on the interface.*/

Raisecom Proprietary and Confidential

202
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Step 4 Configure a routing policy which is to match IP address based on IP prefix list and specify the
next-hop IP address of the standby route to implement IP FRR.
iTN A

iTNA(config)#ip prefix-list pfl-1 permit any

/*select the configuration parameters according to the actual need.*/
iTNA(config)#route-map map-1 permit 10
iTNA(config-route-map)#match ip address prefix-list pfl-1
iTNA(config-route-map)#set ip backup-nexthop 30.10.10.2
/* Configure the next hop IP address of the standby route.*/
iTNA(config-route-map)#set ip backup-interface gigaethernet 1/1/2
/* configure the egress interface of the standby route.*/
iTNA(config-route-map)#exit
iTNA(config)#ip frr route-map map-1
/*enable IP FRR through which LDP FRR is implemented.*/

Automatic LDP FRR is implemented through IP FRR. After IP FRR is enabled, the
system will automatically establish a LDP FRR standby LSP path.
Step 5 (Optional) trigger the device to assign LSP labels for all route prefixes and assign labels of the
standby LSP path which is based on automatic LDP FRR.
iTN A

iTNA(config)#lsp-trigger all
/*assign LSP labels for all route prefixes of the device.*/
iTNA(config)#mpls ldp auto-frr lsp-trigger all
/*assign standby LSP labels for all route prefixes of the device.*/

iTN B

iTNB(config)#lsp-trigger all
/*assign LSP labels for all route prefixes of the device.*/
iTNB(config)#mpls ldp auto-frr lsp-trigger all
/*assign standby LSP labels for all route prefixes of the device.*/

iTN C

iTNC(config)#lsp-trigger all
/*assign LSP labels for all route prefixes of the device.*/
iTNC(config)#mpls ldp auto-frr lsp-trigger all
/*assign standby LSP labels for all route prefixes of the device.*/

iTN D

Raisecom Proprietary and Confidential

203
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

iTND(config)#lsp-trigger all
/*assign LSP labels for all route prefixes of the device.*/
iTND(config)#mpls ldp auto-frr lsp-trigger all
/*assign standby LSP labels for all route prefixes of the device.*/

Step 6 Configure BFD for IP single-hop detection to implement fast service switching from the
active path to the standby LSP path.
iTN A

iTNA(config)#bfd 1 bind peer-ip default-ip interface gigaethernet 1/1/1

iTNA(config-bfd-session)#session enable
iTNA(config-bfd-session)#exit

iTN B

iTNB(config)#bfd 1 bind peer-ip default-ip interface gigaethernet 1/1/1

iTNB(config-bfd-session)#session enable
iTNB(config)#bfd 2 bind peer-ip default-ip interface gigaethernet 1/1/2
iTNB(config-bfd-session)#session enable
iTNB(config-bfd-session)#exit

iTN C

iTNc(config)#bfd 2 bind peer-ip default-ip interface gigaethernet 1/1/1

iTNc(config-bfd-session)#session enable
iTNC(config-bfd-session)#exit

Checking results
 Use the show ip route command to show the routing table learned by each node.

iTNA(config)#show ip route
Routing Tables: Default-IP-Routing-Table
-------------------------------------------------------------------------
Flag: C - connected, S - static, R - RIP, B - BGP, O - OSPF, I - IS-IS
P - Protocol, s - States, > - selected , * - active, Dis - Distance
P&s Destination/Mask Dis/Metric NextHop Age Interface
C>* 1.0.0.0/8 0/0 1.1.1.1 01w3d00h Loopback2
C>* 1.1.1.1/32 0/0 127.0.0.1 01w3d00h lo0
O>* 2.2.2.2/32 110/2 10.10.10.2 01:33:00 GE1/1/1
O>* 3.3.3.3/32 110/2 10.10.10.2 01:33:00 GE1/1/1
O>* 4.4.4.4/32 110/2 30.10.10.2 00:00:28 GE1/1/2
C>* 10.10.10.0/24 0/0 10.10.10.1 01:33:49 GE1/1/1
C>* 10.10.10.1/32 0/0 127.0.0.1 01:33:49 lo0

Raisecom Proprietary and Confidential

204
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

C>* 20.10.10.0/24 0/0 20.10.10.1 01w1d19h GE1/1/2

C>* 20.10.10.1/32 0/0 127.0.0.1 01w1d19h lo0
O>* 30.10.10.0/24 110/2 10.10.10.2 01:33:00 GE1/1/1

 Use the show ip route detail command to show active routes and standby routes.

iTNA(config)#show ip route 3.3.3.3 detail

Destination: 3.3.3.3/32
Protocol: ospf Process ID: 1
Distance: 110 Metric: 2
NextHop: 10.10.10.2 Neighbour: 0.0.0.0
NextHopIndex: 14 Interface: GE1/1/1
Label: 0 TunnelID:
State: Active Fib Age: 01:16:31
Tag: 0 XC Index: 0
BKNextHop: 20.10.10.2 BkInterface: GE1/1/2
/*IP FRR backup route*/
BKLabel: 0 BkXCIndex: 0
BKNextHopIndex: 8

 Use the show mpls lsp command to show whether configuration results are correct.

iTNA(config)#show mpls lsp

LSR-Type FEC In/Out-Label In/Out-IF Next-Hop
LSP-Status LSP-Type LSP-Flag XCIndex
-------------------------------------------------------------------------
------------------------------------------------------
Egress 1.1.1.1 10432/-- all interfaces/-- --
Up Ldp Working 268
Ingress 2.2.2.2 --/10412 --/GE1/1/1 10.10.10.2
Up Ldp Working 272
/active LSP path*/
***LDP FRR*** --/10451 --/GE1/1/2 30.10.10.2
Up Ldp Working 331
/*LDP FRR backup LSP path*/
Egress 1.1.1.1 10464/-- all interfaces/-- --
Up Ldp Working 329
Transit 2.2.2.2 10465/10412 all interfaces/GE1/1/1.10
10.10.10.2 Up Ldp Working 330
***LDP FRR*** 10465/10451 all interfaces/GE1/1/2.20
20.10.10.2 Up Ldp Working 332

Common questions
Why do I need to configure IP FRR when configuring automatic LDP FRR?
 Because the device will automatically generate the backup LSP path based on the already
configured IP FRR backup route.

Raisecom Proprietary and Confidential

205
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

10.8.6 Example for configuring MPLS-TE FRR link protection

Networking requirements
As shown in Figure 10-6, enable active LSP links between iTN A↔iTN B↔iTN C↔iTN D.
FRR should be configured to protect the directly connected route between iTN B↔iTN C.
Configure a bypass LSP link through iTN E. The bypass LSP link should be created by the
routes between iTN B↔iTN E↔iTN C. The iTNB serves as a Point of Local Repair (PLR)
and iTN C serves as a Merge Point (MP). The primary tunnel and bypass tunnel should be
created through MPLS-TE.

The following example shows the process of configuring MPLS-TE FRR. This
configuration will generate a unidirectional backup LSP. For the peer device, the
configuration of generating a backup LSP is similar.

Figure 10-6 Configuring TE FRR

Configuration principle
 Enable OSPF routes on each device respectively and make routes among devices
available.
 Configure MPLS basic functions on all devices and enable MPLS TE.
 Configure an active Tunnel on iTN A and configure related attributes of the active
Tunnel, and then enable TE FRR on the active Tunnel interface.
 Create a bypass Tunnel interface on PLR node iTN B and configure related attributes of
the bypass tunnel.
 Bind the active Tunnel egress interface of iTN B, namely, the egress interface of the link
under protection, with the bypass Tunnel.

Data preparation
Table 10-6 lists the data required for configuring manual TE FRR.

Table 10-6 Data required for configuring manual TE FRR

Device Route-ID Interface IP address
iTN A 1.1.1.1 gigaethernet 1/1/1 10.10.10.1/24

Raisecom Proprietary and Confidential

206
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Device Route-ID Interface IP address

loopback 2 1.1.1.1/32
iTN B 2.2.2.2 gigaethernet 1/1/1 10.10.10.2/24
gigaethernet 1/1/2 20.10.10.1/24
gigaethernet 1/1/3 40.10.10.1/24
loopback 2 2.2.2.2/32
iTN C 3.3.3.3 gigaethernet 1/1/1 20.10.10.2/24
gigaethernet 1/1/2 30.10.10.1/24
gigaethernet 1/1/3 50.10.10.2/24
loopback 2 3.3.3.3/32
iTN D 4.4.4.4 gigaethernet 1/1/1 30.10.10.2/24
loopback 2 4.4.4.4/32
iTN E 5.5.5.5 gigaethernet 1/1/1 40.10.10.2/24
gigaethernet 1/1/2 50.10.10.1/24
loopback 2 5.5.5.5/32

Configuration steps
Step 1 Configure the IP address of the interface. The method for configuring the interface IP address
of iTN C, iTN D, and iTN E is similar to that for iTN A and iTN B.
iTN A

iTNA#config
iTNA(config)#interface loopback 2
iTNA(config-loopback2)#ip address 1.1.1.1 255.255.255.255
iTNA(config-loopback2)#interface gigaethernet 1/1/1
iTNA(config-gigaethernet1/1/1)#ip address 10.10.10.1 255.255.255.0
iTNA(config-gigaethernet1/1/1)#exit

iTN B

iTNB#config
iTNB(config)#interface loopback 2
iTNB(config-loopback2)#ip address 2.2.2.2 255.255.255.255
iTNB(config-loopback2)#interface gigaethernet 1/1/1
iTNB(config-gigaethernet1/1/1)#ip address 10.10.10.2 255.255.255.0
iTNB(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
iTNB(config-gigaethernet1/1/2)#ip address 20.10.10.1 255.255.255.0

Raisecom Proprietary and Confidential

207
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

iTNB(config-gigaethernet1/1/2)#interface gigaethernet 1/1/3

iTNB(config-gigaethernet1/1/3)#ip address 40.10.10.1 255.255.255.0
iTNB(config-gigaethernet1/1/3)#exit

Step 2 Enable the OSPF routing process, define the interface or network which participates in the
OSPF process, and define the local area of the specified interface or network.
iTN A

iTNA(config)#router opsf 1
iTNA(config-router-ospf)#network 1.1.1.1 0.0.0.0 area 0
iTNA(config-router-ospf)#network 10.10.10.1 0.0.0.0 area 0
iTNA(config-router-ospf)#exit

iTN B
iTNB(config)#router opsf 1
iTNB(config-router-ospf)#network 2.2.2.2 0.0.0.0 area 0
iTNB(config-router-ospf)#network 10.10.10.2 0.0.0.0 area 0
iTNB(config-router-ospf)#network 20.10.10.1 0.0.0.0 area 0
iTNB(config-router-ospf)#network 40.10.10.1 0.0.0.0 area 0
iTNB(config-router-ospf)#exit

iTN C

iTNC(config)#router opsf 1
iTNCconfig-router-ospf)#network 3.3.3.3 0.0.0.0 area 0
iTNC(config-router-ospf)#network 20.10.10.2 0.0.0.0 area 0
iTNC(config-router-ospf)#network 30.10.10.1 0.0.0.0 area 0
iTNC(config-router-ospf)#network 50.10.10.1 0.0.0.0 area 0
iTNC(config-router-ospf)#exit

iTN D

iTND(config)#router opsf 1
iTND(config-router-ospf)#network 4.4.4.4 0.0.0.0 area 0
iTND(config-router-ospf)#network 30.10.10.2 0.0.0.0 area 0
iTND(config-router-ospf)#exit

iTN E

iTNE(config)#router opsf 1
iTNE(config-router-ospf)#network 5.5.5.5 0.0.0.0 area 0
iTNE(config-router-ospf)#network 40.10.10.2 0.0.0.0 area 0

Raisecom Proprietary and Confidential

208
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

iTNE(config-router-ospf)#network 50.10.10.1 0.0.0.0 area 0

iTNE(config-router-ospf)#exit

Step 3 Configure MPLS basic functions and enable global RSVP-TE and interface RSVP-TE.
iTN A

iTNA(config)#mpls lsr-id 1.1.1.1

iTNA(config)#mpls enable
iTNA(config)#mpls rsvp-te
/*enable RSVP-TE globally.*/

iTNA(config)#interface gigaethernet 1/1/1

iTNA(config-gigaethernet1/1/1)#mpls rsvp-te
/*enable RSVP-TE on the interface.*/

iTN B

iTNB(config)#mpls lsr-id 2.2.2.2

iTNB(config)#mpls enable
iTNB(config)#mpls rsvp-te
/*enable RSVP-TE globally.*/

iTNB(config)#interface gigaethernet 1/1/1

iTNB(config-gigaethernet1/1/1)#mpls rsvp-te
/*enable RSVP-TE on the interface.*/
iTNB(config)#interface gigaethernet 1/1/2
iTNB(config-gigaethernet1/1/2)#mpls rsvp-te
/*enable RSVP-TE on the interface.*/
iTNB(config)#interface gigaethernet 1/1/3
iTNB(config-gigaethernet1/1/3)#mpls rsvp-te
/*enable RSVP-TE on the interface.*/

iTN C

iTNC(config)#mpls lsr-id 3.3.3.3

iTNC(config)#mpls enable
iTNC(config)#mpls rsvp-te
iTNC(config)#interface gigaethernet 1/1/1
iTNC(config-gigaethernet1/1/1)#mpls rsvp-te
iTNC(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
iTNC(config-gigaethernet1/1/2)#mpls rsvp-te
iTNC(config-gigaethernet1/1/2)#interface gigaethernet 1/1/3
iTNC(config-gigaethernet1/1/3)#mpls rsvp-te
iTNC(config-gigaethernet1/1/3)#exit

Raisecom Proprietary and Confidential

209
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

iTN D

iTND(config)#mpls lsr-id 4.4.4.4

iTND(config)#mpls enable
iTND(config)#mpls rsvp-te
iTND(config)#interface gigaethernet 1/1/1
iTND(config-gigaethernet1/1/1)#mpls rsvp-te
iTND(config-gigaethernet1/1/1)#exit

iTN E

iTNE(config)#mpls lsr-id 5.5.5.5

iTNE(config)#mpls enable
iTNE(config)#mpls rsvp-te
iTNE(config)#interface gigaethernet 1/1/1
iTNE(config-gigaethernet1/1/1)#mpls rsvp-te
iTNE(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
iTNE(config-gigaethernet1/1/2)#mpls rsvp-te
iTNE(config-gigaethernet1/1/2)#exit

Step 4 Create an active Tunnel on the ingress node iTN A.

 Configure the active LSP explicit path.

iTNA(config)#mpls explicit-path A-D

iTNA(config-mpls-exp-path)#next-hop 10.10.10.2 strict
iTNA(config-mpls-exp-path)#next-hop 20.10.10.2 strict
iTNA(config-mpls-exp-path)#next-hop 30.10.10.2 strict
iTNA(config-mpls-exp-path)#exit

 Configure the related attributes of the active tunnel interface and bind the active tunnel
with the LSP explicit path.

iTNA(config)#interface tunnel 1/1/1

iTNA(config-tunnel1/1/1)#destination 4.4.4.4
/*the destination address of the active Tunnel is the end of the active
link, namely, iTN D.*/
iTNA(config-tunnel1/1/1)#mpls signal-protocol rsvp-te
iTNA(config-tunnel1/1/1)#mpls tunnel-id 1
iTNA(config-tunnel1/1/1)#mpls explicit-path A-D

 Enable TE FRR and activate the tunnel configurations.

iTNA(config-tunnel1/1/1)#mpls te fast-reroute

Raisecom Proprietary and Confidential

210
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

iTNA(config-tunnel1/1/1)#mpls te commit
iTNA(config-tunnel1/1/1)#exit

Step 5 Configure a bypass tunnel on PLR node iTN B.

 Configure the explicit path of the bypass LSP.

iTNB(config)#mpls explicit-path B-E-C

iTNB(config-mpls-exp-path)#next-hop 40.10.10.2 strict
iTNB(config-mpls-exp-path)#next-hop 50.10.10.2 strict
iTNB(config-mpls-exp-path)#exit

 Configure related attributes of the bypass tunnel and bind the bypass tunnel with the
bypass LSP explicit path.

iTNB(config)#interface tunnel 1/1/2

iTNB(config-tunnel1/1/2)#destination 3.3.3.3
/*the destination address of the bypass tunnel is the end of the link
under protection, namely, iTN C.*/
iTNB(config-tunnel1/1/2)#mpls signal-protocol rsvp-te
iTNB(config-tunnel1/1/2)#mpls te bypass-tunnel
iTNB(config-tunnel1/1/2)#mpls tunnel-id 2
iTNB(config-tunnel1/1/2)#mpls explicit-path B-E-C
iTNB(config-tunnel1/1/2)#mpls te commit
iTNB(config-tunnel1/1/2)#exit

Step 6 Bind the bypass tunnel with the active LSP egress interface of the iTN B.

iTNB(config)#interface gigaethernet 1/1/2

iTNB(config-gigaethernet1/1/2)#mpls te backup-path tunnel 1/1/2

Checking results
 Check tunnel configurations through the show te tunnel command on the ingress node
iTN A and PLR node iTN B respectively.

iTNA(config)#show mpls te tunnel

Interface: tunnel1/1/1
Tunnel state:UP, Is bypass: NO, working LSPID:4
/*the Tunnel is Up, which indicates that the active tunnel is
successfully configured.*/
Primary lsp explicit path Name:a-d status:Ready
LSPID:4, XcIndex:172
Ingress LSR ID:1.1.1.1 Egress LSR ID:4.4.4.4 Tunnel ID: 1

Raisecom Proprietary and Confidential

211
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Signaling Protocol:Rsvp QosMode:-- BandWidth Cir:-- Pir:-- Used:--

Weight:--
DsMode:Uniform Exp2LocalPriMap:Default LocalPri2ExpMap:Default
PipeServClass --
Record Route:YES Record Label:YES
FRR Type: LINK
IncludeAnyAffinity:0 ExcludeAnyAffinity:0

iTNB(config)#show mpls te tunnel

Interface: tunnel1/1/2
Tunnel state:UP, Is bypass: YES, working LSPID:7
/*Tunnel is Up, which indicates that the bypass tunnel is successfully
configured.*/
Primary lsp explicit path Name:a-c status:Ready
LSPID:7, XcIndex:178
Ingress LSR ID:2.2.2.2 Egress LSR ID:3.3.3.3 Tunnel ID: 2
Signaling Protocol:Rsvp QosMode:-- BandWidth Cir:-- Pir:-- Used:--
Weight:--
DsMode:Uniform Exp2LocalPriMap:Default LocalPri2ExpMap:Default
PipeServClass --
Record Route:NO Record Label:NO
FRR Type: --
IncludeAnyAffinity:0 ExcludeAnyAffinity:0

 When links between the iTN B and iTN C run normally, use the show mpls te frr
protecting command to check the information about the bypass tunnel.

iTNB#show mpls te frr protecting

ByPassTunnel Name:tunnel1/1/2 ID:2, Protected
Interface:gigaethernet1/1/1, Status:UP
FRR Protecting Information:
TunnelID IngerssLSPID EgressLSRID LSPID MP-Inlabel Status
-------------------------------------------------------------------------
1 2.2.2.2 3.3.3.3 4 10358 UNUSE
/*disable bypass tunnel.*/

 When the link between the iTN B and iTN C fails, use the show mpls te frr protecting
command to check the information about the bypass tunnel.

iTNB#show mpls te frr protecting

ByPassTunnel Name:tunnel1/1/2 ID:2, Protected
Interface:gigaethernet1/1/1, Status:UP
FRR Protecting Information:
TunnelID IngerssLSPID EgressLSRID LSPID MP-Inlabel Status
-------------------------------------------------------------------------
1 1.1.1.1 2.2.2.2 4 10358 INUSE
/*enable bypass tunnel.*/

Raisecom Proprietary and Confidential

212
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Common questions
After configurations are complete, TE FRR backup link cannot be successfully created.
 Check whether the active Tunnel and bypass Tunnel are Up.
 Check whether the destination address of the bypass Tunnel is on the node of the active
Tunnel path.

10.8.7 Example for configuring MPLS-TE FRR node protection

Networking requirements
As shown in Figure 10-7, enable active LSP links between iTN A↔ iTN B↔iTN C↔iTN D.
The LSP link should pass the FRR protection node iTN Z. Configure a bypass LSP link which
passes the iTN E. The bypass link is created by routes between iTN B↔iTN E↔iTN C. The
iTN B serves as the PLR. The active tunnel and bypass tunnel should be created through
MPLS-TE.

The following example shows the process of configuring MPLS-TE FRR. This
configuration will generate a unidirectional backup LSP. For the peer device, the
configuration of generating a backup LSP is similar.

Figure 10-7 Configuring TE FRR node protection

Configuration principle
 Enable OSPF routes on all devices and make routes among devices available.
 Configure MPLS basic functions on all devices and enable MPLS TE.
 Configure an active Tunnel on iTN A and configure related attributes of the active
Tunnel, and then enable TE FRR on the active Tunnel interface.
 Create a bypass Tunnel interface on PLR node iTN B and configure related attributes of
the bypass tunnel.
 Bind the active Tunnel egress interface of iTN B, namely, the egress interface of the link
under protection, with the bypass Tunnel.

Data preparation
Table 10-7 lists the data required for configuring manual TE FRR.

Raisecom Proprietary and Confidential

213
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Table 10-7 Data required for configuring manual TE FRR

Device Route-ID Interface IP address
iTN A 1.1.1.1 gigaethernet 1/1/1 10.10.10.1/24
loopback 2 1.1.1.1/32
iTN B 2.2.2.2 gigaethernet 1/1/1 10.10.10.2/24
gigaethernet 1/1/2 20.10.10.1/24
gigaethernet 1/1/3 40.10.10.1/24
loopback 2 2.2.2.2/32
iTN Z 6.6.6.6 gigaethernet 1/1/1 20.10.10.2/24
gigaethernet 1/1/2 60.10.10.1/24
loopback 2 6.6.6.6/32
iTN C 3.3.3.3 gigaethernet 1/1/1 60.10.10.2/24
gigaethernet 1/1/2 30.10.10.1/24
gigaethernet 1/1/3 50.10.10.2/24
loopback 2 3.3.3.3/32
iTN D 4.4.4.4 gigaethernet 1/1/1 30.10.10.2/24
loopback 2 4.4.4.4/32
iTN E 5.5.5.5 gigaethernet 1/1/1 40.10.10.2/24
gigaethernet 1/1/2 50.10.10.1/24
loopback 2 5.5.5.5/32

Configuration steps
Step 1 Configure the IP address of the interface. The method for configuring the interface IP address
of iTN C, iTN D, iTN E, and iTN Z is similar to that for iTN A and iTN B.
iTN A

iTNA#config
iTNA(config)#interface loopback 2
iTNA(config-loopback2)#ip address 1.1.1.1 255.255.255.255
iTNA(config-loopback2)#interface gigaethernet 1/1/1
iTNA(config-gigaethernet1/1/1)#ip address 10.10.10.1 255.255.255.0
iTNA(config-gigaethernet1/1/2)#exit

iTN B

Raisecom Proprietary and Confidential

214
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

iTNB#config
iTNB(config)#interface loopback 2
iTNB(config-loopback2)#ip address 2.2.2.2 255.255.255.255
iTNB(config-loopback2)#interface gigaethernet 1/1/1
iTNB(config-gigaethernet1/1/1)#ip address 10.10.10.2 255.255.255.0
iTNB(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
iTNB(config-gigaethernet1/1/2)#ip address 20.10.10.1 255.255.255.0
iTNB(config-gigaethernet1/1/2)#interface gigaethernet 1/1/3
iTNB(config-gigaethernet1/1/3)#ip address 40.10.10.1 255.255.255.0
iTNB(config-gigaethernet1/1/3)#exit

Step 2 Create an OSPF routing process, define the interface or network which participates in the
OSPF process, and specify the local area of the interface or network. The method for
configuring other devices is the similar to that for iTN A and iTN B.
iTN A

iTNA(config)#router opsf 1
iTNA(config-router-ospf)#network 1.1.1.1 0.0.0.0 area 0
iTNA(config-router-ospf)#network 10.10.10.1 0.0.0.0 area 0
iTNA(config-router-ospf)#exit

iTN B

iTNB(config)#router opsf 1
iTNB(config-router-ospf)#network 2.2.2.2 0.0.0.0 area 0
iTNB(config-router-ospf)#network 10.10.10.2 0.0.0.0 area 0
iTNB(config-router-ospf)#network 20.10.10.1 0.0.0.0 area 0
iTNB(config-router-ospf)#network 40.10.10.1 0.0.0.0 area 0
iTNB(config-router-ospf)#exit

Step 3 Configure MPLS basic functions and enable global RSVP-TE and interface RSVP-TE. The
method for configuring other devices is similar to that for iTN A and iTN B.
iTN A

iTNA(config)#mpls lsr-id 1.1.1.1

iTNA(config)#mpls enable
iTNA(config)#mpls rsvp-te
/*enable RSVP-TE globally.*/

iTNA(config)#interface gigaethernet 1/1/1

iTNA(config-gigaethernet1/1/1)#mpls rsvp-te
/*enable RSVP-TE on the interface.*/

iTN B

Raisecom Proprietary and Confidential

215
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

iTNB(config)#mpls lsr-id 2.2.2.2

iTNB(config)#mpls enable
iTNB(config)#mpls rsvp-te
/*enable RSVP-TE globally.*/

iTNB(config)#interface gigaethernet 1/1/1

iTNB(config-gigaethernet1/1/1)#mpls rsvp-te
/*enable RSVP-TE on the interface.*/
iTNB(config)#interface gigaethernet 1/1/2
iTNB(config-gigaethernet1/1/2)#mpls rsvp-te
/*enable RSVP-TE on the interface.*/
iTNB(config)#interface gigaethernet 1/1/3
iTNB(config-gigaethernet1/1/3)#mpls rsvp-te
/*enable RSVP-TE on the interface.*/

Step 4 Create an active Tunnel on the ingress node iTN A.

 Configure the active LSP explicit path.

iTNA(config)#mpls explicit-path A-D

iTNA(config-mpls-exp-path)#next-hop 10.10.10.2 strict
iTNA(config-mpls-exp-path)#next-hop 20.10.10.2 strict
iTNA(config-mpls-exp-path)#next-hop 60.10.10.2 strict
iTNA(config-mpls-exp-path)#next-hop 30.10.10.2 strict
iTNA(config-mpls-exp-path)#exit

 Configure the related attributes of the active tunnel interface and bind the active tunnel
with the LSP explicit path.

iTNA(config)#interface tunnel 1/1/1

iTNA(config-tunnel1/1/1)#destination 4.4.4.4
/*the destination address of the active Tunnel is the end of the active
link, namely, iTN D.*/
iTNA(config-tunnel1/1/1)#mpls signal-protocol rsvp-te
iTNA(config-tunnel1/1/1)#mpls tunnel-id 1
iTNA(config-tunnel1/1/1)#mpls explicit-path A-D

 Enable TE FRR node protection and activate the tunnel configurations.

iTNA(config-tunnel1/1/1)#mpls te fast-reroute node-protect

/*enable FRR node protection.*/
iTNA(config-tunnel1/1/1)#mpls te commit
iTNA(config-tunnel1/1/1)#exit

Step 5 Configure a bypass tunnel on PLR node iTN B.

 Configure the explicit path of the bypass LSP.
Raisecom Proprietary and Confidential
216
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

iTNB(config)#mpls explicit-path B-E-C

iTNB(config-mpls-exp-path)#next-hop 40.10.10.2 strict
iTNB(config-mpls-exp-path)#next-hop 50.10.10.2 strict
iTNB(config-mpls-exp-path)#exit

 Configure related attributes of the bypass tunnel and bind the bypass tunnel with the
bypass LSP explicit path.

iTNB(config)#interface tunnel 1/1/2

iTNB(config-tunnel1/1/2)#destination 3.3.3.3
/*the destination address of the bypass tunnel is the end of the link
under protection, namely, iTN C.*/
iTNB(config-tunnel1/1/2)#mpls signal-protocol rsvp-te
iTNB(config-tunnel1/1/2)#mpls te bypass-tunnel
iTNB(config-tunnel1/1/2)#mpls tunnel-id 2
iTNB(config-tunnel1/1/2)#mpls explicit-path B-E-C
iTNB(config-tunnel1/1/2)#mpls te commit
iTNB(config-tunnel1/1/2)#exit

Step 6 Bind the bypass tunnel with the active LSP egress interface of the iTN B.

iTNB(config)#interface gigaethernet 1/1/2

iTNB(config-gigaethernet1/1/2)#mpls te backup-path tunnel 1/1/2

Checking results
 Check tunnel configurations through the show te tunnel command on the ingress node
iTN A and PLR node iTN B respectively.

iTNA(config)#show mpls te tunnel

Interface: tunnel1/1/1
Tunnel state:UP, Is bypass: NO, working LSPID:4
/*the Tunnel is Up, which indicates that the active tunnel is
successfully configured.*/
Primary lsp explicit path Name:a-d status:Ready
LSPID:4, XcIndex:172
Ingress LSR ID:1.1.1.1 Egress LSR ID:4.4.4.4 Tunnel ID: 1
Signaling Protocol:Rsvp QosMode:-- BandWidth Cir:-- Pir:-- Used:--
Weight:--
DsMode:Uniform Exp2LocalPriMap:Default LocalPri2ExpMap:Default
PipeServClass --
Record Route:YES Record Label:YES
FRR Type: NODE
/*TE FRR node protection*/
IncludeAnyAffinity:0 ExcludeAnyAffinity:0

iTNA(config)#show mpls te tunnel

Raisecom Proprietary and Confidential

217
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 10 MPLS

Interface: tunnel1/1/2
Tunnel state:UP, Is bypass: YES, working LSPID:7
/*Tunnel is Up, which indicates that the bypass tunnel is successfully
configured.*/
Primary lsp explicit path Name:a-c status:Ready
LSPID:7, XcIndex:178
Ingress LSR ID:2.2.2.2 Egress LSR ID:3.3.3.3 Tunnel ID: 2
Signaling Protocol:Rsvp QosMode:-- BandWidth Cir:-- Pir:-- Used:--
Weight:--
DsMode:Uniform Exp2LocalPriMap:Default LocalPri2ExpMap:Default
PipeServClass --
Record Route:NO Record Label:NO
FRR Type: --
IncludeAnyAffinity:0 ExcludeAnyAffinity:0

 When node iTN Z works normally, use the show mpls te frr protecting command to
check the information about the bypass tunnel.

iTNB#show mpls te frr protecting

ByPassTunnel Name:tunnel1/1/2 ID:2, Protected
Interface:gigaethernet1/1/1, Status:UP
FRR Protecting Information:
TunnelID IngerssLSPID EgressLSRID LSPID MP-Inlabel Status
-------------------------------------------------------------------------
1 2.2.2.2 3.3.3.3 4 10358 UNUSE
/* disable bypass tunnel.*/

 When node iTN Z fails, use the show mpls te frr protecting command to check
information about the bypass tunnel.

iTNB#show mpls te frr protecting

ByPassTunnel Name:tunnel1/1/2 ID:2, Protected
Interface:gigaethernet1/1/1.10, Status:UP
FRR Protecting Information:
TunnelID IngerssLSPID EgressLSRID LSPID MP-Inlabel Status
-------------------------------------------------------------------------
1 1.1.1.1 2.2.2.2 4 10358 INUSE
/*enable bypass tunnel.*/

Common questions
After configurations are complete, TE FRR backup link cannot be successfully created.
 Check whether the active Tunnel and bypass Tunnel are Up.
 Check whether the destination address of the bypass Tunnel is on the node of the active
Tunnel path.

Raisecom Proprietary and Confidential

218
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

11 VPN

This chapter describes principles and configuration procedures of MPLS VPN, as well as
related configuration examples, including following sections:
 Configuring MPLS VPWS
 Configuring MPLS VPLS
 Configuring VPWS to access VPLS
 Configuring MPLS L3VPN
 Maintainance
 Configuration examples

11.1 Configuring MPLS VPWS

11.1.1 Preparing for configurations

Scenario
VPWS is a point-to-point L2VPN technology. It forms a service mode that multiple services
can be provided in a network. Therefore, the carrier can provide Layer 2 services and Layer 3
services in a MPLS network.
The access modes for the L2VPN to extract sub-interface services are different. Therefore, the
modes adopted by the system to process the VLAN Tags of Ethernet packets are also
differently, which are divided into symmetric mode and asymmetric mode as shown in Table
11-1 and Table 11-2.

Table 11-1 Extracting sub-interface services in symmetric mode

Type of sub- Function VPWS/VSI
interface
Raw Tagged encapsulation
encapsulation
Dot1q sub- Ingress No action Add the outer Tag to the packet. The TPID and VLAN
interface interface Tag are configurable.
By default, the TPID is 0x8100 and the VLAN Tag is 0.

Raisecom Proprietary and Confidential

219
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Type of sub- Function VPWS/VSI

interface
Raw Tagged encapsulation
encapsulation
Egress No action Remove the outer Tag of the packet.
interface
QinQ sub- Ingress No action Add the outer Tag to the packet. The TPID and VLAN
interface interface Tag are configurable.
By default, the TPID is 0x8100 and the VLAN Tag is 0.
Egress No action Remove the outer Tag of the packet.
interface
Ethernet Ingress No action Replace the outer Tag of the packet. The TPID and
interface interface VLAN Tag are configurable.
By default, the TPID is 0x8100 and the VLAN Tag is 0.
Egress No action Remove the outer Tag of the packet.
interface

Table 11-2 Extracting sub-interface services in asymmetric mode

Type of Function VPWS/VSI
sub-
interface Raw encapsulation Tagged encapsulation

Dot1q sub- Ingress interface Remove the outer Tag of Remove the outer Tag of the packet first
interface the packet. and then add outer Tag according to the
Use the vlan translation interface configurations.
svlan untag command to Use the vlan translation svlan untag
enable the interface to command to enable the interface to remove
remove the outer Tag. the outer Tag. Otherwise, the Tag cannot
Otherwise, the Tag cannot be removed.
be removed. By default, the TPID and the VLAN Tag
of the added outer Tag are 0x8100 and 0
respectively.
Egress interface Add the outer Tag to the Replace the outer Tag of the packet.
packet. Use the vlan translation svlan untag
Use the vlan translation command to enable the interface to add the
svlan untag command to outer Tag. Otherwise, the Tag cannot be
enable the interface to add added. The added Tag is the SVLAN
the outer Tag. Otherwise, encapsulated by the sub-interface.
the Tag cannot be added.
The added Tag is the
SVLAN encapsulated by
the sub-interface.

Raisecom Proprietary and Confidential

220
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Type of Function VPWS/VSI

sub-
interface Raw encapsulation Tagged encapsulation

QinQ sub- Ingress interface Remove the outer Tag of Remove the outer Tag of the packet first
interface the packet. and then add outer Tag according to the
Use the vlan translation interface configurations.
svlan untag command to Use the vlan translation svlan untag
enable the interface to command to enable the interface to remove
remove the outer Tag. the outer Tag. Otherwise, the Tag cannot
Otherwise, the Tag cannot be removed.
be removed. By default, the TPID and the VLAN Tag
of the added outer Tag are 0x8100 and 0
respectively.
Remove the outer Tag of Remove the outer double Tag of the packet
the packet. first and then add outer Tag according to
Use the vlan translation the interface configurations.
svlan untag cvlan untag Use the vlan translation svlan untag
command to enable the cvlan untag command to enable the
interface to remove the interface to remove the outer double Tag.
outer double Tag. Otherwise, the Tag cannot be removed.
Otherwise, the Tag cannot By default, the TPID and the VLAN Tag
be removed. of the added outer Tag are 0x8100 and 0
respectively.
egress interface Add the outer Tag to the Replace the outer Tag of the packet.
packet. Use the vlan translation svlan untag
Use the vlan translation command to enable the interface to add the
svlan untag command to outer Tag. Otherwise, the Tag cannot be
enable the interface to add added. The added Tag is the SVLAN
the outer Tag. Otherwise, encapsulated by the sub-interface.
the Tag cannot be added.
The added Tag is the
SVLAN encapsulated by
the sub-interface.
Remove the outer double Remove the outer Tag of the packet first
Tag of the packet. and then add outer double Tag according
Use the vlan translation to the interface configurations.
svlan untag cvlan untag Use the vlan translation svlan untag
command to enable the cvlan untag command to enable the
interface to add the outer interface to remove the outer Tag and then
double Tag. Otherwise, the add outer double Tag. Otherwise, the Tag
Tag cannot be removed. cannot be added.
The added Tag is the
SVLAN and CVLAN
encapsulated by the
interface.

Raisecom Proprietary and Confidential

221
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Prerequisite
 Configure the basic attributes of Layer 3 physical interface, sub-interface, and LAG
interface.
 Configure MPLS basic functions.
 Configure Tunnel-related functions.

11.1.2 Configuring static L2VC

The Tunnel Tag and PW Tag belong to the same Tag domain, they cannot be
configured together.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter Layer 3 physical interface
interface-number configuration mode.
Raisecom(config)#interface interface-type Enter sub-interface configuration mode.
interface-number.subif
Raisecom(config-port)#encapsulation dot1Q Configure the VLAN ID or segment
vlan-id-1 [ to vlan-id-2 ] VLAN ID encapsulated into the ingress
packets on the sub-interface.
That is, the device supports service
extraction based on VLAN ID or VLAN
ID list.
3 Raisecom(config-port)#mode l2 Configure the VPN mode of Layer 3
physical interface to L2VPN.
By default, it is L3VPN.
4 Raisecom(config-port)#mpls static-l2vc Configure the static L2VC by specifying
destination ip-address raw vc-id vc-id in- the incoming label and outgoing label.
label in-label out-label out-label [ tunnel- Configure the encapsulation mode of the
policy policy-name | tunnel tunnel-number ] PW packet to RAW, that is, no VLAN
[ no-control-word ] [ mtu mtu ] [ tpid tpid ] Tag.
[ backup | bypass ]
Raisecom(config-port)#mpls static-l2vc Configure the static L2VC by specifying
destination ip-address [ tagged ] vc-id vc-id the incoming label and outgoing label.
in-label in-label out-label out-label Configure the encapsulation mode of PW
[ tunnel-policy policy-name | tunnel tunnel- packet to Tagged. You can configure the
number ] [ no-control-word ] [ mtu mtu ] VLAN ID of the service provider as
[ tpid tpid ] [ svlan vlan-id ] [ backup | required.
bypass ]
Raisecom(config-port)# mpls static-l2vc Configure static L2VC based on TDM
destination ip-address vc-id vc-id in-label services.
in-label out-label out-label [ tunnel-policy
policy-name | tunnel tunnel-number ]
[ jitter-buffer buffer ] [ tdm-encapsulation
number ] [ rtp-header ]
5 Raisecom(config-port)#interface interface- (Optional) configure the sub-interface
type interface-number configuration mode.

Raisecom Proprietary and Confidential

222
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Step Command Description

6 Raisecom(config-subif)#l2vpn access-mode (Optional) configure the access mode of
asymmetry the interface to extract L2VPN services
to asymmetric mode.
By default, the access mode of the sub-
interface is symmetric.
7 Raisecom(config-subif)#vlan translation svlan (Optional) configure the sub-interface to
untag encapsulate the outer VLAN Tag.
Raisecom(config-subif)#vlan translation svlan (Optional) configure the sub-interface to
untag cvlan untag encapsulate the outer double VLAN Tag.

11.1.3 Configuring dynamic L2VC

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls l2vpn default martini Enable global Martini.
3 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
Raisecom(config)#interface interface-type Enter sub-interface configuration
interface-number.subif mode.
Raisecom(config-port)#encapsulation dot1Q vlan-
id-1 [ to vlan-id-2 ] Configure the VLAN ID or segment
VLAN ID encapsulated into the
ingress packets on the sub-interface.
That is, the device supports service
extraction based on VLAN ID or
VLAN ID list.
4 Raisecom(config-port)#mode l2 Configure VPN mode of the Layer 3
physical interface to L2VPN.
By default, it is L3VPN.
5 Raisecom(config-port)#mpls l2vc destination ip- Configure dynamic L2VC. Configure
address raw vc-id vc-id [ tunnel-policy policy- the encapsulation mode of PW
name | tunnel-interface tunnel-number ] [ no- packets to Raw, that is, no VLAN
control-word ] [ mtu mtu ] [ backup | bypass ] Tag.
Raisecom(config-port)#mpls l2vc destination ip- Configure dynamic L2VC. Configure
address [ tagged ] vc-id vc-id [ tunnel-policy the encapsulation mode of the PW
policy-name | tunnel-interface tunnel-number ] packet to Tagged. The VLAN ID of
[ no-control-word ] [ mtu mtu ] [ svlan vlan- the service end can be configured
id ] [ backup | bypass ] optionally.
Raisecom(config-port)#mpls l2vc destination ip- Configure dynamic L2VC based on
address vc-id vc-id [ tunnel-policy policy-name TDM services.
| tunnel tunnel-number ] [ jitter-buffer
buffer ] [ tdm-encapsulation number ] [ rtp-
header ]

Raisecom Proprietary and Confidential

223
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

11.1.4 Configuring MS-PW

Steps 2–5 are optional. Configure them as required.

Step Command Description

1 Raisecom#config Enter global
configuration
mode.
2 Raisecom(config)#mpls switch-l2vc ip-address vc-id in-label in- (Optional)
label out-label out-label [ tunnel-policy policy-name | tunnel configure MS-
tunnel-number ] between ip-address vc-id [ in-label in-label PW switching
out-label out-label ] [ tunnel-policy policy-name | tunnel based on
tunnel-number ] { raw | tagged } [ no-control-word ] [ mtu Ethernet
mtu ] encapsulation.
Raisecom(config)#mpls switch-l2vc ip-address vc-id [ tunnel-
policy policy-name | tunnel tunnel-number ] between ip-address
vc-id [ in-label in-label out-label out-label ] [ tunnel-policy
policy-name | tunnel tunnel-number ] { raw | tagged } [ no-
control-word ] [ mtu mtu ]
3 Raisecom(config)#mpls switch-l2vc ip-address vc-id in-label in- (Optional)
label out-label out-label [ tunnel-policy policy-name | tunnel configure MS-
tunnel-number ] between ip-address vc-id [ in-label in-label PW switching
out-label out-label ] [ tunnel-policy policy-name | tunnel based on CES
tunnel-number ] { cesopsn-basic | cesopsn-cas | satop-e1 } encapsulation.
[ tdm-encapsulation frame-number ] [ rtp-header ] [ timeslotnum
timeslotnum ]
Raisecom(config)#mpls switch-l2vc ip-address vc-id [ tunnel-
policy policy-name | tunnel tunnel-number ] between ip-address
vc-id [ in-label in-label out-label out-label ] [ tunnel-policy
policy-name | tunnel tunnel-number ] { cesopsn-basic | cesopsn-
cas | satop-e1 } [ tdm-encapsulation frame-number ] [ rtp-
header ] [ timeslotnum timeslotnum ]
4 Raisecom(config)#mpls switch-l2vc ip-address vc-id in-label in- (Optional)
label out-label out-label [ tunnel-policy policy-name | tunnel configure
tunnel-number ] between ip-address vc-id [ in-label in-label dynamic MS-PW
out-label out-label ] [ tunnel-policy policy-name | tunnel with backup
tunnel-number ] { raw | tagged } [ no-control-word ] [ mtu protection.
mtu ] backup ip-address vc-id [ in-label in-label out-label out-
label ] [ tunnel-policy policy-name | tunnel tunnel-number ]
Raisecom(config)#mpls switch-l2vc ip-address vc-id [ tunnel-
policy policy-name | tunnel tunnel-number ] between ip-address
vc-id [ in-label in-label out-label out-label ] [ tunnel-policy
policy-name | tunnel tunnel-number ] { raw | tagged } [ no-
control-word ] [ mtu mtu ] backup ip-address vc-id [ in-label
in-label out-label out-label ] [ tunnel-policy policy-name |
tunnel tunnel-number ]

Raisecom Proprietary and Confidential

224
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Step Command Description

5 Raisecom(config)#mpls switch-l2vc ip-address vc-id in-label in- Configure MS-
label out-label out-label [ tunnel-policy policy-name | tunnel PW based on
tunnel-number ] between ip-address vc-id [ in-label in-label CES
out-label out-label ] [ tunnel-policy policy-name | tunnel encapsulation
tunnel-number ] { cesopsn-basic | cesopsn-cas | satop-e1 } with backup
[ tdm-encapsulation frame-number ] [ rtp-header ] [ timeslotnum protection.
timeslotnum ] backup ip-address vc-id [ in-label in-label out-
label out-label ] [ tunnel-policy policy-name | tunnel tunnel-
number ]
Raisecom(config)#mpls switch-l2vc ip-address vc-id [ tunnel-
policy policy-name | tunnel tunnel-number ] between ip-address
vc-id [ in-label in-label out-label out-label ] [ tunnel-policy
policy-name | tunnel tunnel-number ] { raw | tagged } [ no-
control-word ] [ mtu mtu ] backup ip-address vc-id [ in-label
in-label out-label out-label ] [ tunnel-policy policy-name |
tunnel tunnel-number ] backup ip-address vc-id [ in-label in-
label out-label out-label ] [ tunnel-policy policy-name | tunnel
tunnel-number ]

MS-PW supports the following switching modes:

 static PW to static PW
 static PW to dynamic PW
 dynamic PW to static PW
 dynamic PW to dynamic PW
In the command line of the above configuration steps, you can distinguish static PW
from dynamic PW by configuring different parameters.
 You need to specify parameters in-label in-label and out-label out-label while
configuring static PW
 You do not need to specify control word and MTU while configuring dynamic PW.

11.1.5 (Optional) configuring BFD for PW

After configuring PW, you can configure PW-based BFD.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#bfd session-id Create BFD session detection PW and enter BFD
bind pw vc-id peer-ip [ pw-ttl session mode.
ttl ]

You have to specify TTL and you can configure

BFD for MS-PW. For example, if TTL is
configured to 2, it means that the packet hops
once on the MS-PW.
3 Raisecom(config)#interface Enter Layer 3 physical interface configuration mode.
interface-type interface-number

Raisecom Proprietary and Confidential

225
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Step Command Description

4 Raisecom(config-port)#mpls l2vpn pw Configure PW-based BFD.
bfd [ min-tx-interval tx-interval ]
[ min-rx-interval rx-interval ]
[ detect-multiplier multiplier ]
[ backup ]

11.1.6 Configuring ARP for PW and NDP for PW

ARP for PW is applied to the mobile operator network. When the base station requests the
ARP from the core network gateway, the ARP request packet and response packet are
transmitted through the L2VPN between them. Therefore, the base station can learn ARP from
the gateway.
The ARP packets are sent to the CPU to be processed on the PE. After buffering the ARP
packets, the PE sends ARP request packets to the peer PE through master/slave PW. The peer
device will send the ARP request packets to the core network gateway. After receiving the
ARP request packets, the core gateway will learn the request packets locally instead of
sending response packets. The response packets will be sent to the local PE through
master/slave PW, and then sent to the CPU for storage, and finally, sent to the base station for
learning the ARP response packets.
The principle of NDP for PW is the same as that of the ARP for PW.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface gigaethernet Enter interface configuration mode.
interface-name interface-number
3 Raisecom(config-port)#pw-proxy { enable Enable ARP proxy at the AC side, namely,
| disable } ARP proxy for PW or NDP proxy for PW.

11.1.7 Checking configurations

No. Command Description
1 Raisecom#show mpls l2vc [ static ] [ interface-type Show L2VPN functions.
interface-number ]
2 Raisecom#show mpls switch-l2vc [ ip-address vc-id ] Show MS-PW information.
3 Raisecom#show pw-proxy { arp | ndp } Show related entries about ARP
proxy.

Raisecom Proprietary and Confidential

226
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

11.2 Configuring MPLS VPLS

11.2.1 Preparing for configurations

Scenario
VPLS is a L2VPN technology which is based on MPLS and Ethernet technology. VPLS can
provide point-to-multipoint VPN networking topology. VPLS provides a more perfect
solution for carriers, who use point-to-point L2VPN services. In addition, it does not need to
manage internal routing information of users, which is required in L3VPN.

Prerequisite
Enable MPLS basic functions.

11.2.2 Configuring VSI

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls vsi vsi-name static Create a VSI and enter VSI configuration
mode.
3 Raisecom(config-vsi)#vsi-id id Configure the VSI ID.
4 Raisecom(config-vsi)#vsi-mtu mtu Configure the VSI MTU.
5 Raisecom(config-vsi)#encapsulation { raw | Configure the encapsulation mode of VSI
tagged } services.
6 Raisecom(config-vsi)#mpls static-peer ip- Configure the VSI static peer. Create a PW
address [ vc-id vc-id ] in-label in-label and specify the Tunnel for the PW to isolate
out-label out-label [ tunnel-policy ACs.
policy-name | tunnel tunnel-number ] [ no-
control-word ] [ upe | upe-isolate ]
7 Raisecom(config-vsi)#mpls peer ip-address Configure the VSI dynamic peer. Create a PW
[ vc-id vc-id ] [ tunnel-policy policy- and specify the Tunnel for the PW to isolate
name | tunnel tunnel-number ] [ no- ACs.
control-word ] [ upe | upe-isolate ]
8 Raisecom(config-vsi)#ratelimit { broadcast Configure VSI rate limiting.
| unknown-multicast | dlf } cir cir-value
[ cbs cbs-value ]
9 Raisecom(config-vsi)#storm-control Enable VSI storm control.
{ broadcast | multicast | dlf | all }
enable
10 Raisecom(config-vsi)#exit Exit VSI configuration mode.
Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
11 Raisecom(config-port)#mpls l2binding vsi Bind VPLS services.
vsi-name [ isolate ]

Raisecom Proprietary and Confidential

227
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

11.2.3 Checking configurations

No. Command Description
1 Raisecom)#show mpls vsi detail [ vsi-name ] Show VSI detailed information.
2 Raisecom#show mpls vsi pw [ vsi-name ] Show VSI PW configurations.
3 Raisecom#show mpls vsi services [ vsi-name ] Show VSI service information.
4 Raisecom#show mpls vsi statistics Show VSI statistics.
5 Raisecom#show mac-address-table [ static ] vsi vsi- Show the VSI-based unicast MAC
name address.

11.3 Configuring VPWS to access VPLS

11.3.1 Preparing for configurations

Scenario
Virtual Pseudo Wire Service (VPWS) provides end-to-end connection between 2 nodes while
VPLS can realize multipoint-to-multipoint interconnection. By accessing VPWS to VPLS,
you can provide services in the following 2 scenarios:
 Point-to-multipoint aggregation access
 Dual-homed protection of 2 destination nodes in the VPLS network accessed by the UPE

Prerequisite
Complete VPLS configurations.

11.3.2 Configuring VSI to access VPWS

Perform following configurations on the nodes in the VPWS network accessed by the VPLS
network.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls vsivsi-name static Enter VSI configuration mode.
3 Raisecom(config/vsi)# mpls static-peer ip-address Configure the VSI to access
[ vc-id vc-id ] [ in-label in-label out-label out- VPWS.
label] [ tunnel-policy policy-name | tunnel tunnel-
number ] [ no-control-word ] [ upe | upe-isolate ]

Raisecom Proprietary and Confidential

228
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

 Perform above configurations on working and protection nodes respectively in the

dual-homed network.
 In point-to-multipoint aggregation access scenario, perform above configurations
on the aggregation node (SPE) multiple times to make all UPEs accessing VPWS.

11.3.3 Checking configurations

No. Command Description
1 Raisecom(config)#show mpls vsi detail [ vsi- Show VSI details.
name ]
2 Raisecom(config)#show mpls vsi pw [ vsi-name ] Show VSI PW configurations.

11.4 Configuring MPLS L3VPN

11.4.1 Preparing for configurations

Scenario
MPLS L3VPN is a PE-based L3VPN technology for ISP's solutions. It uses the BGP to
release the VPN route and uses MPLS to forward VPN packets in the ISP network.
As shown in Figure 11-1, in MPLS L3 VPN topology, the PE device and CE device exchange
routes through EBGP.

Figure 11-1 MPLS L3VPN network topology

MPLS L3VPN provides a flexible networking mode and is of good expansibility. In addition,
it supports MPLS QoS and MPLS TE well. Therefore, it is applied to increasing larger scales.

Raisecom Proprietary and Confidential

229
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Prerequisite
 Configure basic attributes, such as Layer 3 physical interface, sub-interface, and link
aggregation interface.
 Configure MPLS basic functions.
 Configure Tunnel related functions.

11.4.2 Configuring VRF basic attributes

Configure VRF on the PE device in the backbone network and connect the CE to the PE.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip vrf vrf-name Create a VRF and enter VRF configuration mode.
3 Raisecom(config-vrf)#rd rd Configure the VRF RD.
4 Raisecom(config-vrf)#route-target Configure the VRF RT.
[ export | import | both ] rt
5 Raisecom(config)#tunnel-policy policy- (Optional) enter Tunnel policy configuration
name mode.
6 Raisecom(config-tunnelpolicy)#tunnel (Optional) configure Tunnel sequence.
select-seq { lsp | cr-lsp } *

11.4.3 Binding VRF with interfaces

This configuration is for binding the PE UNI in the backbone network with VRF. After
configurations are complete, PE devices can ping through their respectively connected CE
devices. The configuration prerequisite is that the UNIs of PE devices and the interfaces of
CE devices are all configured with IP addresses.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter interface configuration modes.
interface-type interface-number
3 Raisecom(config-port)#ip vrf Apply VRF to the Layer 3 physical interface, VLAN
forwarding vrf-name sub-interface, sub-interface, Port+VLAN interface, and
QinQ sub-interface.

When applying VRF to the Layer 3 sub-interface,

you should configure the encapsulation VLAN of
the sub-interface to Dot1.Q or QinQ.

Raisecom Proprietary and Confidential

230
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

11.4.4 Configuring public routes

Configure IGP routes on the PE and P devices in the backbone network. After configurations
are complete, PE device and P device can establish IGP neighbor relationship, then they can
ping through each other.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Start an OSPF process and enter OSPF
[ vrf vrf-name ] [ router-id router-id ] configuration mode.
3 Raisecom(config-router-ospf)#network ip- Advertise the network, that is, define the IP
address wild-card-mask area area-id address of the interface or the network which
participates in the OSPF process and specify
the area to which the interface or network
belongs.

11.4.5 Configuring public Tunnel

Public network tunnels can be static LSP tunnels or dynamic LDP tunnels. Establish MPLS
tunnels by configuring MPLS basic functions, static LSPs, or MPLS LDP functions on the PE
and P devices in the backbone network. After the configuration is complete, public network
tunnels are established between the PE devices at both ends.
For the configuration of the public network tunnel, see chapter 11 VPN.

11.4.6 Configuring MP-IBGP peer

Configure MP-IBGP VPNv4 neighbor relations on the PE devices at both ends in the
backbone network, transferring VPN routes.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp as-id Enable BGP and create a BGP instance and
enter BGP configuration mode.
3 Raisecom(config-router)#bgp router-id Configure BGP router ID.
router-id
4 Raisecom(config-router)#neighbor ip- Create a MP-IBGP peer and specify the peer
address remote-as as-id AS ID. The peer AS ID should be the same
with the local AS ID.
5 Raisecom(config-router)#neighbor ip- Configure the device to use the specified route
address1 update-source ip-address2 to update the source interface while
establishing BGP connections.
6 Raisecom(config-router)#address-family Enter BGP VPNv4 address family
vpnv4 configuration mode.

Raisecom Proprietary and Confidential

231
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Step Command Description

7 Raisecom(config-router-af)#neighbor ip- Enable the function of exchanging
address activate information about the specified VPNv4
address family among BGP neighbors.
8 Raisecom(config-router-af)#neighbor ip- Enable BGP to send extended community
address send-community extended attributes to the peer.
9 Raisecom(config-router-af)#exit-address- Exit BGP VPNv4 address family
family configuration mode.

11.4.7 Configuring PE-CE route switching

Static routes, EBGP routes, and OSPF routes can be used for PE-CE route switching. Select
one mode according to the actual network requirement.

Configuring PE-CE static routes.

Configure the PE device as below.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip route vrf vrf-name Configure static routes in the specified
destination-address mask-address { next-hop VRF.
| NULL 0 } * [ distance distance ]
[ description text ] [ tag tag ]
3 Raisecom(config)#router bgp as-id Enable BGP. Create a BGP instance and
enter BGP configuration mode.
4 Raisecom(config-router)#address-family ipv4 Specify the IPv4 unicast address family
vrf vrf-name routing table of the specified VPN instance
and enter VPN instance IPv4 unicast
address family configuration mode.
5 Raisecom(config-router-af)#redistribute Redistribute routes to the IPv4 unicast
static address family routing table of the VPN
instance.

Configure the CE device as below.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip route destination-address Configure static routes from CE to
{ mask-address | mask-length } { next-hop | NULL PE.
0 } * [ distance distance ] [ description text ]
[ tag tag ]

Raisecom Proprietary and Confidential

232
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Configure PE-CE EBGP routes

Configure the PE device as below.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp as-id Enter BGP configuration mode.
3 Raisecom(config-router)#address- Create BGP VRF and enter IPv4 unicast address family
family ipv4 vrf vrf-name configuration mode.
4 Raisecom(config-router- Configure the CE to the VPN EBGP peer and specify
af)#neighbor ip-address remote-as the peer AS ID. The peer AS ID is different from the
as-id local AS ID.
By default, there is no BGP peer.
5 Raisecom(config-router- Enable the feature of switching IPv4 unicast address
af)#neighbor ip-address activate family routes with the EBGP peer.
By default, switching IPv4 unicast address family routes
with the EBGP peer is enabled. Switching route
information about other address families is prohibited.
6 Raisecom(config-router- Redistribute CE routes.
af)#redistribute { connected |
static | ospf } [ metric metric ]
Redistribute the CE routes to the VPN routing table to
[ route-map map ] advertise them to the peer PE on the network.
Raisecom(config-router- Advertise local routes.
af)#network ip-address [ mask-
address ] [ route-map route-map- Advertise local routes of the CE in the specified network
name ] segments to the VPN routing table.

Configure the CE device as below.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router bgp as-id Enter BGP configuration mode.
3 Raisecom(config-router)#neighbor Configure the PE as the EBGP peer and specify the peer
ip-address remote-as as-id AS ID.
By default, there is no BGP peer.
4 Raisecom(config- Redistribute VPN routes.
router)#redistribute { connected
| static | ospf } [ metric CE advertises the address of the VPN network segment
metric ] [ route-map map ] that it can arrive to the accessed PE and then PE will
send the information to the peer CE.
Raisecom(config-router)#network Advertise local routes.
ip-address [ mask-address ]
[ route-map route-map-name ]
Advertise the routes of the specified network segment to
the EBGP peer, namely, the accessed PE.

Raisecom Proprietary and Confidential

233
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Configuring PE-CE OSPF routes

Configure the PE device as below:

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Start an OSPF process, bind it with the already-
vrf vrf-name [ router-id router-id ] known VPN instance, and enter OSPF
configuration mode.
3 Raisecom(config-router-ospf))#network Advertise routes, that is, define the interface or
ip-address wild-card-mask area area-id network which participates in the OSPF process
and specify the area to which the interface or
network belongs.

Configure the CE device as below:

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#router ospf process-id Start an OSPF process and enter OSPF
[ router-id router-id ] configuration mode.
3 Raisecom(config-router-ospf))#network Advertise private network routes to the OSPF
ip-address wild-card-mask area area-id process.

11.4.8 Configuring VRF fault detection

Step Command Description
1 Raisecom#ping vrf vpn-name ip-address [ count count ] Configure VRF PING
[ df-bit ] [ size size ] [ source ip-address ] detection.
[ waittime seconds ]

11.4.9 Checking configurations

No. Command Description
1 Raisecom#show ip vrf vrf-name Show VRF information.
2 Raisecom#show tunnel-policy [ policy-name ] Show Tunnel policy information.
3 Raisecom#show ip bgp vpnv4 vrf vrf-name summary Show summary about the VRF-
based BGP peer.
4 Raisecom#show ip bgp vpnv4 vrf vrf-name neighbour Show details about the VRF-based
[ ip-address ] BGP peer.

Raisecom Proprietary and Confidential

234
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

No. Command Description

5 Raisecom#show ip bgp vpnv4 vrf vrf-name network- Show information about VRF-
address [ mask-address ] based BGP routes.
6 Raisecom#show ip ospf [ process-id ] [ vrf vrf- Show information about OSPF
name ] route routes.
7 Raisecom#show ip bgp [ ip-address [ ip-mask ] ] Show information about BGP
routes.

11.5 Maintainance
Command Description

Raisecom(config)#clean pw-proxy { arp | ndp } vpn- Clear the learned ARP and NDP
interface interface-type interface-number entries.

Rasiecom#clear ip bgp [ all | ip-address | external ] Reset all or the specified BGP
vrf vrf-name [ as-id ] connections in VRF.

Rasiecom#clear ip bgp [ all | ip-address | external ] Update all or the specified BGP routes
vrf vrf-name [ as-id ] { in | out | soft } in VRF. Do not disconnect BGP
connections, namely, soft reset.

11.6 Configuration examples

11.6.1 Example for configuring static Tunnel to carry static VPWS
services

Networking requirements
As shown in Figure 11-2, the user has branches in areas A and B. Branches need to exchange
point-to-point VPN leased-line services. Because the network scale is small and the topology
is stable, you can configure bidirectional static LSP between PE A and PE B to work as the
public Tunnel of the L2VPN. By default, devices are configured with IP addresses.

Raisecom Proprietary and Confidential

235
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Figure 11-2 Configuring static Tunnel to carry static VPWS services

Configuration steps
Step 1 Configure the static Tunnel. For details, see section 10.8.1 Example for configuring static
bidirectional LSP without IP capability.
Step 2 Configure static L2VC.
 Configure PE A.

PEA(config)#interface gigaethernet 1/2/1

PEA(config-gigaethernet 1/2/1)#mode l2
PEA(config-gigaethernet 1/2/1)#mpls static-l2vc destination 192.168.4.2
raw vc-id 1 in-label 101 out-label 101 tunnel 1 mtu 9600
PEA(config-gigaethernet 1/2/1)#exit

 Configure PE B.

PEB(config)#interface gigaethernet 1/2/1

PEB(config-gigaethernet 1/2/1)#mode l2
PEB(config-gigaethernet 1/2/1)#mpls static-l2vc destination 192.168.1.1
raw vc-id 1 in-label 101 out-label 101 tunnel 1 mtu 9600
PEB(config-gigaethernet 1/2/1)#exit

Checking results
Use the show mpls l2vc static command to show static VPWS configurations on PE A and
PE B.
 Show static VPWS configurations on PE A.

PEA(config)#show mpls l2vc static

Client interface : gigaethernet1/2/1
Pw index : 2

Raisecom Proprietary and Confidential

236
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Vc id : 101
Encapsulation type : raw
Tunnel type : static
Destination : 192.168.4.2
Tunnel policy : --
Tunnel number : 1
Local vc label : 101
Remote vc label : 101
Ac status : UP
Pw state : UP
Vc state : UP
Vc signal : manual
Local cw : enable
Operational cw : enable
Local vc mtu : 9600
Remote vc mtu : --
Tpid : 0x9100
Svlan : --
Pw role : PrimaryPw
Pw work status : Working
Pw access mode : mesh
Pw QosMode : --
Pw Bandwidth Cir : --
Pw Bandwidth Pir : --
Pw Bandwidth Valid : InValid
Pw Weight : --
Pw Flow Queue : --
Pw DsMode : Uniform
Pw PipeServClass : --
Pw Exp2LocalPriMap : 0
Pw LocalPri2ExpMap : 0
Create time : 2000-11-11,14:38:16
Up time : 0 days, 0 hours, 0 minutes, 0 seconds
Last change time : 2000-11-11,14:38:16

 Show static VPWS configurations on PE B.

PEB(config)#show mpls l2vc static

Client interface : gigaethernet1/2/1

Pw index : 4
Vc id : 1
Encapsulation type : raw
Tunnel type : static
Destination : 192.168.1.1
Tunnel policy : --
Tunnel number : 1
Local vc label : 102
Remote vc label : 102
Ac status : UP
Pw state : UP
Vc state : UP
Vc signal : manual

Raisecom Proprietary and Confidential

237
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Local cw : enable
Operational cw : enable
Local vc mtu : 9600
Remote vc mtu : --
Tpid : 0x9100
Svlan : --
Pw role : PrimaryPw
Pw work status : Working
Pw access mode : mesh
Pw QosMode : --
Pw Bandwidth Cir : --
Pw Bandwidth Pir : --
Pw Bandwidth Valid : InValid
Pw Weight : --
Pw Flow Queue : --
Pw DsMode : Uniform
Pw PipeServClass : --
Pw Exp2LocalPriMap : 0
Pw LocalPri2ExpMap : 0
Create time : 2000-11-11,16:18:27
Up time : 0 days, 0 hours, 0 minutes, 0 seconds
Last change time : 2000-11-11,16:18:27

11.6.2 Example for configuring RSVP-TE-based dynamic Tunnel to

carry dynamic VPWS services

Networking requirements
As shown in Figure 11-3, the user has branches in areas A and B. Branches need to exchange
point-to-point VPN leased-line services. To facilitate network maintenance and reduce manual
intervention, you can configure the RSVP-TE-based dynamic Tunnel to carry dynamic VPWS
services to meet user's leased-line telecommunication requirements. By default, devices are
configured with IP addresses.

Figure 11-3 Configuring RSVP-TE-based dynamic Tunnel to carry dynamic VPWS services

Raisecom Proprietary and Confidential

238
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Configuration steps
Step 1 Configure RSVP-TE-based dynamic Tunnel. For details, see section 10.8.3 Example for
configuring RSVP-TE-based dynamic LSP.
Step 2 Configure dynamic L2VC.
 Configure PE A.

PEA(config)#interface gigaethernet 1/2/1

PEA(config-gigaethernet 1/2/1)#mode l2
PEA(config-gigaethernet 1/2/1)#mpls l2vc destination 20.1.1.1 raw vc-id 1
tunnel 1 mtu 9600
PEA(config-gigaethernet 1/2/1)#exit

 Configure PE B.
PEB(config)#interface gigaethernet 1/2/1
PEB(config-gigaethernet 1/2/1)#mode l2
PEB(config-gigaethernet 1/2/1)#mpls l2vc destination 10.1.1.1 raw vc-id 1
tunnel 1 mtu 9600
PEB(config-gigaethernet 1/2/1)#exit

Checking results
Use the show mpls l2vc command to show static VPWS configurations on PE A and PE B.
 Show static VPWS configurations on PE A.

PEA(config)#show mpls l2vc gigaethernet 1/2/1

Client interface : gigaethernet1/2/1
Pw index : 4
Session State : down
Vc id : 1
Encapsulation type : raw
Tunnel type : mplsTe
Destination : 20.1.1.1
Tunnel policy : --
Tunnel number : 1
Local vc label : 10242
Remote vc label : --
Ac status : down
Pw state : down
Vc state : down
Local statuscode : 0xa
Remote statuscode : 0x0
Vc signal : pwIdFecSignaling
Local cw : enable
Operational cw : enable
Local vc mtu : 9600
Remote vc mtu : --

Raisecom Proprietary and Confidential

239
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Tpid : 0x9100
Svlan : --
Pw role : PrimaryPw
Pw work status : Working
Pw access mode : mesh
Pw QosMode : --
Pw Bandwidth Cir : --
Pw Bandwidth Pir : --
Pw Bandwidth Valid : InValid
Pw Weight : --
Pw Flow Queue : --
Pw DsMode : Uniform
Pw PipeServClass : --
Pw Exp2LocalPriMap : 0
Pw LocalPri2ExpMap : 0
Create time : 2014-07-25,09:58:14
Up time : 0 days, 0 hours, 0 minutes, 0 seconds
Last change time : 2014-07-25,09:58:14
----------------------------------------
 Show static VPWS configurations on PE B.

PEB(config)#show mpls l2vc gigaethernet 1/2/1

Client interface : gigaethernet 1/2/1
Pw index : 4
Session State : down
Vc id : 1
Encapsulation type : raw
Tunnel type : mplsTe
Destination : 10.1.1.1
Tunnel policy : --
Tunnel number : 1
Local vc label : 10243
Remote vc label : --
Ac status : down
Pw state : down
Vc state : down
Local statuscode : 0xa
Remote statuscode : 0x0
Vc signal : pwIdFecSignaling
Local cw : enable
Operational cw : enable
Local vc mtu : 9600
Remote vc mtu : --
Tpid : 0x9100
Svlan : --
Pw role : PrimaryPw
Pw work status : Working
Pw access mode : mesh
Pw QosMode : --
Pw Bandwidth Cir : --
Pw Bandwidth Pir : --
Pw Bandwidth Valid : InValid
Pw Weight : --
Pw Flow Queue : --

Raisecom Proprietary and Confidential

240
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Pw DsMode : Uniform
Pw PipeServClass : --
Pw Exp2LocalPriMap : 0
Pw LocalPri2ExpMap : 0
Create time : 2014-07-25,10:13:17
Up time : 0 days, 0 hours, 0 minutes, 0 seconds
Last change time : 2014-07-25,10:13:17
----------------------------------------

11.6.3 Example for configuring MPLS L2VPN typical networking

Networking requirements
As shown in Figure 11-4, the headquarter G exchanges leased-line services with branch A
over the IP RAN where end-to-end communication is implemented through multi-section PW
and protection implemented by deploying active/standby Tunnel and active/standby PW. In
this networking topology, the IP RAN device is named based on the network where it resides,
which should be the same with the carrier network name. For example, U1 is the client-side
IPRAN access device. A2 is the network-side access device. And B is the aggregation core
layer device.
 Deploy active/standby static PWs between U1-1 and A2-1, and U3 and A2-1.
 Deploy active/standby dynamic PWs between A2-1 and B-1, and A2-2 and B-2.
 Deploy dynamic PWs between B-1 and B-2, and B-3 and B-4.
 Configure static-to-dynamic PW on A2-1 and A2-2 respectively.
 Configure dynamic-to-dynamic PW on B-1, B-2, B-3, and B-4.
 The configuration process is similar, so this section only takes the configurations of B-
1/B-3 device from the branch side to the core network for example. Configurations for
the headquarter-side devices will not be detailed.

Figure 11-4 Configuring MPLS L2VPN services

Configuration principle
 Configure LSR-ID on U1, A2, and B. Enable MPLS globally. Enable LDP on A2 and B
globally.

Raisecom Proprietary and Confidential

241
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

 Configure the IP address of the service interface and loopback interface planned by U1,
A2, and B.
 Configure the active/standby static Tunnel between U1-1 and A2-1 and configure the
active/standby static PW.
 Enable OSPF on A2-1, B-1, and B-3. Advertise and learn routes over the entire network.
 Enable LDP sessions on A2-1, B-1, and B-3 and establish LDP remote sessions
respectively, preparing for the assignment of PW labels.
 Configure active/standby PWs on A2-1, B-1, and B-3 respectively. The labels are
automatically distributed according to LDP.
 Configure the static-to-dynamic PW on A2.
 Enable BFD and establish PW redundancy protection.
 (Optional) configure QoS rate limiting for the PW.

Data preparation
Table 11-3 lists data for configurations.

Table 11-3 Data for configurations

Device LSR-ID Interface IP address
U1-1 1.1.1.1 gigaethernet 1/1/1 10.10.1.1/24
gigaethernet 1/2/1.100 10.10.10.2/24
loopback 2 1.1.1.1/24
A2-1 2.2.2.2 gigaethernet 1/1/1 10.10.1.2/24
gigaethernet 1/1/2 10.10.2.1/24
gigaethernet 1/1/3 100.10.1.1/24
loopback 2 2.2.2.2/32
B-1 3.3.3.3 gigaethernet 1/1/1 10.10.2.2/24
loopback 2 3.3.3.3
B-3 5.5.5.5 gigaethernet 1/1/1 10.10.5.1/24
loopback 2 5.5.5.5/32

Loopback 1 is a dedicated interface for the DCN network management. To prevent

conflicts, loopback 1 interface is prohibited. You can enable another loopback
interface of which the IP address can be used as the IP address of the LSR-ID.
Loopback 2 is used in this example.

Configuration steps
Step 1 Configure MPLS globally.

Raisecom Proprietary and Confidential

242
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

U1-1

U1-1(config)#mpls lsr-id 1.1.1.1

U1-1(config)#mpls enable

A2-1

A2-1(config)#mpls lsr-id 2.2.2.2

A2-1(config)#mpls enable
A2-1(config)#mpls ldp

B-1

B-1(config)#mpls lsr-id 3.3.3.3

B-1(config)#mpls enable
B-1(config)#mpls ldp

B-3

B-3(config)#mpls lsr-id 5.5.5.5

B-3(config)#mpls enable
B-3(config)#mpls ldp

Step 2 Configure the IP address of the planning interface and enable LDP session.
U1-1

U1-1(config)#interface loopback 2
U1-1(config-loopback2)#ip address 1.1.1.1 255.255.255.255
U1-1(config-loopback2)#interface gigaethernet 1/1/1
U1-1(config-gigaethernet1/1/1)#ip address 10.10.1.1 255.255.255.0
U1-1(config-gigaethernet1/1/1)#exit

A2-1

A2-1(config)#interface loopback 2
A2-1(config-loopback2)#ip address 2.2.2.2 255.255.255.255
A2-1(config-loopback2)#interface gigaethernet 1/1/1
A2-1(config-gigaethernet1/1/1)#ip address 10.10.1.2 255.255.255.0
A2-1(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
A2-1(config-gigaethernet1/1/2)#ip address 10.10.2.1 255.255.255.0

Raisecom Proprietary and Confidential

243
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

A2-1(config-gigaethernet1/1/2)#mpls ldp
A2-1(config-gigaethernet1/1/2)#interface gigaethernet 1/1/3
A2-1(config-gigaethernet1/1/3)#ip address 100.10.1.1 255.255.255.0
A2-1(config-gigaethernet1/1/3)#mpls ldp
/*configure the IP address of the interface on the ring and enable LDP.

B-1

B-1(config)#interface loopback 2
B-1(config-loopback2)#ip address 3.3.3.3 255.255.255.255
B-1(config-loopback2)#interface gigaethernet 1/1/1
B-1(config-gigaethernet1/1/1)#ip address 10.10.2.2 255.255.255.0
B-1(config-gigaethernet1/1/1)#mpls ldp

B-3
B-3(config)#interface loopback 2
B-3(config-loopback2)#ip address 5.5.5.5 255.255.255.255
B-3(config-loopback2)#interface gigaethernet 1/1/1
B-3(config-gigaethernet1/1/1)#ip address 10.10.5.1 255.255.255.0
B-3(config-gigaethernet1/1/1)#mpls ldp

Step 3 Configure static active/stanby Tunnel between U1-1 and A2-1.

 Configure active Tunnel on U1-1.

U1-1(config)#interface tunnel 1/1/1

U1-1(config-tunnel1/1/1)#mpls tunnel-id 1
U1-1(config-tunnel1/1/1)#destination 2.2.2.2
U1-1(config-tunnel1/1/1)#mpls te commit
U1-1(config-tunnel1/1/1)#exit
U1-1(config)#mpls bidirectional static-lsp ingress lsp1-1 lsr-id 2.2.2.2
tunnel-id 1
U1-1(config-ingress-lsp)#forward 2.2.2.2 255.255.255.255 nexthop
10.10.1.2 out-label 101
U1-1(config-ingress-lsp)#backward in-label 102
U1-1(config-ingress-lsp)#exit

 Configure a standby Tunnel on U1-1.

U1-1(config)#interface tunnel 1/1/2

U1-1(config-tunnel1/1/2)#mpls tunnel-id 2
U1-1(config-tunnel1/1/2)#destination 2.2.2.2
U1-1(config-tunnel1/1/2)#mpls te commit
U1-1(config-tunnel1/1/2)#exit
U1-1(config)#mpls bidirectional static-lsp ingress lsp1-2 lsr-id 2.2.2.2
tunnel-id 2

Raisecom Proprietary and Confidential

244
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

U1-1(config-ingress-lsp)#forward 2.2.2.2 255.255.255.255 nexthop

10.10.1.2 out-label 103
U1-1(config-ingress-lsp)#backward in-label 104

 Configure active Tunnel on A2-1.

A2-1(config)#interface tunnel 1/1/1

A2-1(config-tunnel1/1/1)#mpls tunnel-id 1
A2-1(config-tunnel1/1/1)#destination 1.1.1.1
A2-1(config-tunnel1/1/1)#mpls te commit
A2-1(config-tunnel1/1/1)#exit
A2-1(config)#mpls bidirectional static-lsp egress lsp1-1 lsr-id 1.1.1.1
tunnel-id 1
A2-1(config-ingress-lsp)#forward in-label 101
A2-1(config-ingress-lsp)#backward 1.1.1.1 255.255.255.255 nexthop
10.10.1.1 out-label 102
 Configure standby Tunnel on A2-1.

A2-1(config)#interface tunnel 1/1/2

A2-1(config-tunnel1/1/1)#mpls tunnel-id 2
A2-1(config-tunnel1/1/1)#destination 1.1.1.1
A2-1(config-tunnel1/1/1)#mpls te commit
A2-1(config-tunnel1/1/1)#exit
A2-1(config)#mpls bidirectional static-lsp egress lsp1-1 lsr-id 1.1.1.1
tunnel-id 2
A2-1(config-ingress-lsp)#forward in-label 103
A2-1(config-ingress-lsp)#backward 1.1.1.1 255.255.255.255 nexthop
10.10.1.1 out-label 104

Step 4 Configure a static PW between U1-1 and A2-1.

U1-1(config)#interface gigaethernet 1/2/1.1

U1-1(config-gigaethernet1/2/1.1)#encapsulation dot1Q 1
U1-1(config-gigaethernet1/2/1.1)#mode l2
U1-1(config-gigaethernet1/2/1.1)#mpls static-l2vc destination 2.2.2.2 raw
vc-id 1 in-label 201 out-label 201 tunnel 1/1/1
U1-1(config-gigaethernet1/2/1.1)#mpls static-l2vc destination 2.2.2.2 raw
vc-id 2 in-label 202 out-label 202 tunnel 1/1/2 backup

Step 5 Enable OSPF on U1, A2, and B and advertise routes.

U1-1

U1-1(config)#router ospf 1
U1-1(config-router-ospf)#network 1.1.1.1 255.255.255.255 area 0
U1-1(config-router-ospf)#network 10.10.1.1 255.255.255.255 area 0

Raisecom Proprietary and Confidential

245
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

U1-1(config-router-ospf)#exit

A2-1

A2-1(config)#router ospf 1
A2-1(config-router-ospf)#network 2.2.2.2 255.255.255.255 area 0
A2-1(config-router-ospf)#network 10.10.1.2 255.255.255.255 area 0
A2-1(config-router-ospf)#network 10.10.2.1 255.255.255.255 area 0
A2-1(config-router-ospf)#network 100.10.1.1 255.255.255.255 area 0
A2-1(config-router-ospf)#exit

B-1

B-1(config)#router ospf 1
B-1(config-router-ospf)#network 3.3.3.3 255.255.255.255 area 0
B-1(config-router-ospf)#network 10.10.2.2 255.255.255.255 area 0
B-1(config-router-ospf)#exit

B-3

B-3(config)#router ospf 1
B-3(config-router-ospf)#network 5.5.5.5 255.255.255.255 area 0
B-3(config-router-ospf)#network 10.10.5.1 255.255.255.255 area 0
B-3(config-router-ospf)#exit

Step 6 Establish LDP sessions between A2-1, B-1, and B-3.

A2-1

A2-1(config)#mpls ldp targeted neighbour 3.3.3.3

/*Configure an active LDP poiting to B-1.*/
A2-1(config)#mpls ldp targeted neighbour 5.5.5.5
/*Configure a standby LDP pointing to B-3.*/

B-1

B-1(config)#mpls ldp targeted neighbour 2.2.2.2

/*Configure a standby LDP pointing to A2-1.*/

B-3

Raisecom Proprietary and Confidential

246
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

B-3(config)#mpls ldp targeted neighbour 2.2.2.2

/*Configure a standby LDP pointing to A2-1.*/

Step 7 Configure a static-to-dynamic PW on A2-1.

A2-1(config)#mpls switch-l2vc 1.1.1.1 1 in-label 201 out-label 201 tunnel

1/1/1 between 3.3.3.3 14 raw
/*static-to-dynamic active PW*/
A2-1(config)#mpls switch-l2vc 1.1.1.1 2 in-label 202 out-label 202 tunnel
1/1/2 between 5.5.5.5 15 raw
/* static-to-dynamic standby PW*/

Step 8 Enable BFD on U1-1 and establish PW FRR redundancy protection.

U1-1(config)#interface gigaethernet 1/2/1.1
U1-1(config-gigaethernet1/2/1.1)#mpls l2vpn pw bfd
U1-1(config-gigaethernet1/2/1.1)#mpls l2vpn pw bfd backup
U1-1(config-gigaethernet1/2/1.1)#mpls l2vpn redundancy master switch-mode
revertive wtr-time 120

Checking results
 After step 4, you can use the show mpls l2vc command to show PW working status.

U1-1#show mpls l2vc

Client interface : gigaethernet1/2/1.1
Pw index : 1
Vc id : 1
Encapsulation type : raw
Access mode : symmetry
Tunnel type : mplsTe
Destination : 2.2.2.2
Tunnel policy : --
Tunnel number : 1/1/1
Local vc label : 201
Remote vc label : 201
Ac status : up(bfd:up, cc:up)
Pw state : up(bfd:up, cc:up)
Vc state : up
/*If the above three items are all Up, the PW is configured successfully
and devices can communicate with each other. If AC is Down, it indicates
that the UNI is not Up. If PW is Down, it indicates that the NNI is not
Up, the PW parameters are inconsistent, or the network-side routes are
non-reachable.*/
Vc signal : manual
Local cw : enable
Operational cw : enable
Local vc mtu : 9600
Remote vc mtu : --

Raisecom Proprietary and Confidential

247
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Tpid : 0x8100
Svlan : --
Pw role : PrimaryPw
Pw work status : Working
Pw access mode : mesh
Pw QosMode : --
Pw Bandwidth Cir : --
Pw Bandwidth Pir : --
Pw Bandwidth Valid : InValid
Pw Weight : --
Pw Flow Queue : --
Pw DsMode : Uniform
Pw PipeServClass : --
Pw Exp2LocalPriMap : Default
Pw LocalPri2ExpMap : Default
Create time : 1970-03-21,12:36:32
Up time : 0 days, 0 hours, 1 minutes, 20 seconds
Last change time : 1970-03-21,12:36:32
----------------------------------------
Client interface : gigaethernet1/2/1.1
Pw index : 3
Vc id : 2
Encapsulation type : raw
Access mode : symmetry
Tunnel type : mplsTe
Destination : 2.2.2.2
Tunnel policy : --
Tunnel number : 1/1/2
Local vc label : 202
Remote vc label : 202
Ac status : up(bfd:up, cc:up)
Pw state : up(bfd:up, cc:up)
Vc state : up
Vc signal : manual
Local cw : enable
Operational cw : enable
Local vc mtu : 9600
Remote vc mtu : --
Tpid : 0x8100
Svlan : --
Pw role : SecondaryPw
Pw work status : NoWorking
Pw access mode : mesh
Pw QosMode : --
Pw Bandwidth Cir : --
Pw Bandwidth Pir : --
Pw Bandwidth Valid : InValid
Pw Weight : --
Pw Flow Queue : --
Pw DsMode : Uniform
Pw PipeServClass : --
Pw Exp2LocalPriMap : Default
Pw LocalPri2ExpMap : Default
Create time : 1970-03-21,12:37:36
Up time : 0 days, 0 hours, 0 minutes, 16 seconds

Raisecom Proprietary and Confidential

248
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Last change time : 1970-03-21,12:37:36

----------------------------------------
Total l2vc : 2 2 up 0 down

 After step 6, you can use the show mpls ldp targeted neighbour command to check
status of LDP neighbor sessions.

A2-1#show mpls ldp targeted neighbor

LDP Remote Entity Information
-------------------------------------------------------------------------
Remote Peer IP : 3.3.3.3 LDP ID : 2.2.2.2:0
Transport Address : 2.2.2.2 LDP AdminStatus : Up
LDP OperStatus : Up Configured Keepalive Timer : 45Sec
Configured Hello Timer : 45 Sec Negotiated Hello Timer : 45Sec
BFD configuration : Disable Bfd Session ID : 0
Hello Packet sent/received : 40698/44929
-------------------------------------------------------------------------
Remote Peer IP : 5.5.5.5 LDP ID : 2.2.2.2:0
Transport Address : 2.2.2.2 LDP AdminStatus : Up
LDP OperStatus : Up Configured Keepalive Timer : 45Sec
Configured Hello Timer : 45 Sec Negotiated Hello Timer : 45Sec
BFD configuration : Disable Bfd Session ID : 0
Hello Packet sent/received : 40698/44929
-------------------------------------------------------------------------
TOTAL : 2 Remote-Peer(s) Found.
/*the remote LDP session exists and it is Up, which indicates that it is
normal.*/

 After step 6, you can use the show mpls ldp interface command to show whether
physical layer interface is enabled with LDP.

A2-1#show mpls ldp interface

LDP Interface Information

-------------------------------------------------------------------------
If-Name LDP STATUS LAM TransportAddress HelloSent/Rcv LDP OperStatus
-------------------------------------------------------------------------
GE1/1/1 Disable DU -- 0/0
GE1/1/2 Enable DU 2.2.2.2 99809/12682 Up
GE1/1/3 Enable DU 2.2.2.2 122206/122129 Up
GE1/1/4 Disable DU -- 0/0 --
GE1/2/1 Disable DU -- 0/0 --

-------------------------------------------------------------------------
LAM: Label Advertisement Mode IF-Name: Interface name

 After step 6, you can use the show mpls ldp session command to show LDP sessions
and the running status.

Raisecom Proprietary and Confidential

249
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

A2-1#show mpls ldp session

LDP Session Information

LDP Session Count : 2
-------------------------------------------------------------------------
Peer-ID Status LAM SsnRole SsnAge KA-Sent/Rcv
-------------------------------------------------------------------------
3.3.3.3:0 Operational DU Passive 0000:06:37 1587/1587
5.5.5.5:0 Operational DU Passive 0000:06:37 1587/1587
-------------------------------------------------------------------------
TOTAL: 2 Session(s) Found.
LAM : Label Advertisement Mode SsnAge Unit : DDDD:HH:MM

 After step 7, you can use the show mpls switch-l2vc command to show configurations
of PW switching.

A2-1#show mpls switch-l2vc

Switch-l2vc type : SVC <---> LDP (BACKUP)
Peer ip address : 1.1.1.1 <---> 3.3.3.3 --
Encapsulation type : raw <---> raw --
/*The RAW/TAG mode of the two PW segments must be the same. */
Vc id : 1 <---> 14 --
Fault relay : off
Vc state : up <---> up --
Local statuscode : 0x0 <---> 0x0 --
Remote statuscode : 0x0 <---> 0x0 --
Pw state : up <---> up --
Bfd state : up <---> up --
Cc state : up <---> up --
Sd state : up <---> up --
In label : 201 <---> 10247 --
Out label : 201 <---> 10241 --
/*The VC-Label of the dynamic PW is automatically assigned. It must have
a value.*/
Local cw : enable <---> enable --
Operational cw : enable <---> enable --
Local vc mtu : 9600 <---> 9600 --
Remote vc mtu : 9600 <---> 9600 --
/*The MTUs of the two PW segments must be the same.*/
Tunnel policy : -- <---> -- --
Tunnel number : 1/1/1 <---> -- --
Out xc index : -- <---> 1522 --
/*LSP interface index, for dynamic PW, this item must have a value.*/
Out ecmp index : -- <---> -- --
Pw QosMode : -- <---> -- --
Pw Bandwidth Cir : -- <---> -- --
Pw Bandwidth Pir : -- <---> -- --
Pw Bandwidth Valid : InValid <---> InValid --
Pw Weight : -- <---> -- --
Pw Flow Queue : -- <---> -- --
Work satus : working <---> working --

Raisecom Proprietary and Confidential

250
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

---------------------------------------------------------------------
Switch-l2vc type : SVC <---> LDP (BACKUP)
Peer ip address : 1.1.1.1 <---> 3.3.3.3 --
Encapsulation type : raw <---> raw --
Vc id : 2 <---> 15 --
Fault relay : off
Vc state : up <---> up --
Local statuscode : 0x0 <---> 0x0 --
Remote statuscode : 0x0 <---> 0x0 --
Pw state : up <---> up --
Bfd state : up <---> up --
Cc state : up <---> up --
Sd state : up <---> up --
In label : 202 <---> 10248 --
Out label : 202 <---> 10242 --
Local cw : enable <---> enable --
Operational cw : enable <---> enable --
Local vc mtu : 9600 <---> 9600 --
Remote vc mtu : 9600 <---> 9600 --
Tunnel policy : -- <---> -- --
Tunnel number : 1/1/2 <---> -- --
Out xc index : -- <---> 1523 --
Out ecmp index : -- <---> -- --
Pw QosMode : -- <---> -- --
Pw Bandwidth Cir : -- <---> -- --
Pw Bandwidth Pir : -- <---> -- --
Pw Bandwidth Valid : InValid <---> InValid --
Pw Weight : -- <---> -- --
Pw Flow Queue : -- <---> -- --
Work satus : working <---> working --

 After all configurations are complete, you can execute the Ping operation based on
MPLS VC to check the connectivity of the L2VPN.

U1-1#ping mpls vc-id 1 destination 2.2.2.2

Sending 5, 200-byte MPLS Echoes to 2.2.2.2,VC ID is 1, timeout is 3
seconds,send interval is 1 seconds,
Press CTRL + C to abort:
Reply from 3.3.3.3: bytes=84, Sequence=1, time<1ms.
Reply from 3.3.3.3: bytes=84, Sequence=2, time<1ms.
Reply from 3.3.3.3: bytes=84, Sequence=3, time<1ms.
Reply from 3.3.3.3: bytes=84, Sequence=4, time<1ms.
Reply from 3.3.3.3: bytes=84, Sequence=5, time<1ms.
---- PING Statistics----
5 packets transmitted,5 packets received,
Success rate is 100 percent(5/5),
round-trip (ms) min/avg/max = 0/0/0

 After step 8, you can use the show bfd state command to show BFD status.

Raisecom Proprietary and Confidential

251
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

U1-1#show bfd state

SessionId State co-Tx-Interval(ms) co-Rx-Interval(ms) co-Detect-
Interval(ms)
------------------------------------------------------------------
129 Up 10 10 30
130 Up 10 10 30

Common questions
After a LDP session is configured, it is not Up.
 Check whether the network-side interface IP address is correctly configured.
 Check whether the OSPF route is enabled and whether routes of the entire network have
been advertised and learned.
 Check whether the NNI is enabled with LDP.
 Check whether the NNI is up.
After static-to-dynamic PW switching is configured, the PW is not Up.
 Check whether the UNI of PE3 is configured with a dynamic PW.
 Check whether the UNI of PE3 is Up.
 Check whether the binding between the static tunnel and the PW is correct in the PW
switching configuration. That is, the tunnel should be bound to the static PW at the local
end.
 Check whether the MTU, Raw/Tag, MTU, TPID, and control word of the two PWs are
the same.
The end-to-end PW cannot be pinged through.
 Check whether the configuration of the tunnel parameters is correct and whether the
status is Up.
 Check whether LDP is Up.
 Check whether the static PW and dynamic PW are up.
 Check whether the interface planning is consistent with the network topology.
 Check whether the configuration process is correct.

11.6.4 Examples for configuring MPLS L3VPN typical networking

Networking requirements
Figure 11-5 shows a mobile backhaul CE+L3VPN network solution. The base station is
connected to device A which functions as the CE on the service network. CE 1 and CE 2
belong to VPN1, which are accessed to the MPLS L3VPN network through PE 1 and PE 2.
The RT of VPN 1 is 1:100. Different VPN users cannot access each other. Run OSPF between
PE 1 and PE 2 and configure interconnection of public network routes. Configure MP-BGP
between PE 1 and PE 2 for advertising L3VPN private network routes. Configure static routes
between PEs and CEs. This completes the deployment of the mobile backhaul network.

Raisecom Proprietary and Confidential

252
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Figure 11-5 Configuring L3VPN networking

Configuration principle
 Configure basic MPLS functions on PE devices and configure VRF.
 Configure the IP addresses of the interfaces on PE and CE devices.
 After configuring the IP address of the PE client-side interface, bind the VRF to the
client-side interface.
 Enable OSPF public network routes between PE 1 and PE 2.
 Configure a MPLS static public network tunnel between PE 1 and PE 2.
 Enable MP-IBGP routes between PE 1 and PE 2, and enable VPNv4.
 Configure a static route between the PE and the CE. Configure the static VRF-based
private network route to the CE on the PE and configure the gateway from the CE to the
PE.

Data preparation
Table 11-4 lists data for configurations.

Table 11-4 Configuration parameters

Device LSR-ID Interface IP address
CE 1 – gigaethernet 1/1/1 10.10.10.1/24
Loopback 2 5.5.5.5/32
PE 1 1.1.1.1 gigaethernet 1/1/1 10.10.10.2/24
gigaethernet 1/1/2 10.10.1.1/24
Loopback 2 1.1.1.1/24
P 2.2.2.2 gigaethernet 1/1/1 10.10.1.2/24
gigaethernet 1/1/2 10.10.3.1/24
Loopback 2 2.2.2.2/32
PE 2 4.4.4.4 gigaethernet 1/1/1 10.10.4.1/24
gigaethernet 1/1/2 10.10.3.2/24

Raisecom Proprietary and Confidential

253
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Device LSR-ID Interface IP address

Loopback 2 4.4.4.4/32
CE 2 – gigaethernet 1/1/1 10.10.4.2/24
Loopback 2 6.6.6.6/32

Configuration steps
Step 1 Configure VRF on PE 1 and PE 2.
PE 1

PE1#config
PE1(config)#ip vrf VPN1
PE1(config-vrf)#rd 100:1
PE1(config-vrf)#route-target import 100:1
PE1(config-vrf)#route-target export 100:1PE1(config-vrf)#exit

PE 2

PE2#config
PE2(config)#ip vrf VPN1
PE2(config-vrf)#rd 100:1
PE2(config-vrf)#route-target import 100:1
PE1(config-vrf)#route-target export 100:1
PE2(config-vrf)#exit

Step 2 Configure the IP address of related interfaces of CE 1, CE 2, PE 1, PE 2, and P.

Configurations are similar, take PE 1 for example.
PE 1

PE1(config)#interface gigaethernet 1/1/2

PE1(config-gigaethernet1/1/2)#ip address 10.10.1.1 255.255.255.0
PE1(config-gigaethernet1/1/2)#interface Loopback 2
PE1(config-Loopback2)#ip address 1.1.1.1 255.255.255.255
PE1(config-Loopback2)#exit

Step 3 Configure the IP address of the customer-side interfaces on the PE 1 and PE 2.

PE 1

PE1(config)#interface gigaethernet 1/1/1

PE1(config-gigaethernet1/1/1)#ip address 10.10.10.2 255.255.255.0

Raisecom Proprietary and Confidential

254
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

PE 2

PE2(config)#interface gigaethernet 1/1/1

PE2(config-gigaethernet1/1/1)#ip address 10.10.4.1 255.255.255.0

Step 4 Bind the customer-side interfaces on PE 1 and PE 2 with VRF.

PE 1

PE1(config)#interface gigaethernet 1/1/1

PE1(config-gigaethernet1/1/1)#ip vrf forwarding vpn1
PE1(config-gigaethernet1/1/1)#exitPE 2

PE 2

PE2(config)#interface gigaethernet 1/1/1

PE2(config-gigaethernet1/1/1)#ip vrf forwarding vpn1
PE2(config-gigaethernet1/1/1)#exit

Step 5 Configure the route of public network between PE 1 and PE 2.

PE 1

PE1(config)#router ospf 1
PE1(config-router-ospf)#network 10.10.1.0 0.0.0.255 area 0
PE1(config-router-ospf)#network 1.1.1.1 0.0.0.0 area 0
PE1(config-router-ospf)#exit

P
P1(config)#router ospf 1
P1(config-router-ospf)#network 10.10.1.0 0.0.0.255 area 0
P1(config-router-ospf)#network 10.10.3.0 0.0.0.255 area 0
P1(config-router-ospf)#network 2.2.2.2 0.0.0.0 area 0
P1(config-router-ospf)#exit

PE 2

PE2(config)#router ospf 1
PE2(config-router-ospf)#network 10.10.3.0 0 0 0.0.0.255 area 0
PE2(config-router-ospf)#network 4.4.4.4 0.0.0.0 area 0
PE2(config-router-ospf)#exit

Raisecom Proprietary and Confidential

255
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Step 6 is for configuring the static public network tunnels. Step 7 is for configuring
dynamic public network tunnels. You can choose one as required.
Step 6 (Optional) configure a static public network tunnel between PE 1 and PE 2.
PE 1

PE1(config)#mpls lsr-id 1.1.1.1

PE1(config)#mpls enable
PE1(config)#interface tunnel 1/1/1
PE1(config-tunnel1/1/1)#destination 4.4.4.4
PE1(config-tunnel1/1/1)#mpls tunnel-id 200
PE1(config-tunnel1/1/1)#mpls te commit
PE1(config-tunnel1/1/1)#exit
PE1(config)#mpls static-lsp ingress lsp12 10.10.3.2 255.255.255.255
nexthop 10.10.1.2 out-label 1001 lsr-id 4.4.4.4 tunnel-id 200
PE1(config)#mpls static-lsp egress lsp21 in-label 2003 lsr-id 4.4.4.4
tunnel-id 200

P1(config)#mpls lsr-id 2.2.2.2

P1(config)#mpls enable
P1(config)#mpls static-lsp transit lsp12 in-label 1001 nexthop 10.10.2.3
out-label 1003 lsr-id 1.1.1.1 4.4.4.4 tunnel-id 200
P1(config)#mpls static-lsp transit lsp21 in-label 2001 nexthop 10.10.1.1
out-label 2003 lsr-id 4.4.4.4 1.1.1.1 tunnel-id 200

PE 2

PE2(config)#mpls lsr-id 4.4.4.4

PE2(config)#mpls enable
PE2(config)#interface tunnel 1/1/1
PE2(config-tunnel1/1/1)#destination 4.4.4.4
PE2(config-tunnel1/1/1)#mpls tunnel-id 200
PE2(config-tunnel1/1/1)#mpls te commit
PE2(config-tunnel1/1/1)#exit
PE2(config)#mpls static-lsp egress lsp12 in-label 1003 lsr-id 1.1.1.1
tunnel-id 200
PE2(config)#mpls static-lsp ingress lsp21 10.10.1.1 255.255.255.0 nexthop
10.10.2.2 out-label 2001 lsr-id 1.1.1.1 tunnel-id 200

Step 7 (Optional) configure a dynamic public network tunnel between PE 1 and PE 2.

PE 1

Raisecom Proprietary and Confidential

256
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

PE1(config)#mpls lsr-id 1.1.1.1

PE1(config)#mpls enable
PE1(config)#interface gigaethernet 1/1/2
PE1(config-gigaethernet1/1/2)#mpls ldp

P(config)#mpls lsr-id 2.2.2.2

P(config)#mpls enable
P(config)#interface gigaethernet 1/1/1
P(config-gigaethernet1/1/1)#mpls ldp
P(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
P(config-gigaethernet1/1/)# mpls ldp

PE 2

PE2(config)#mpls lsr-id 4.4.4.4

PE2(config)#mpls enable
PE2(config)#interface gigaethernet1/1/2
PE2(config-gigaethernet1/1/2)#mpls ldp

Step 8 Establish a MP-IBGP peer between PE 1 and PE 2

PE 1

PE1(config)#router bgp 1
PE1(config-router)#bgp router-id 1.1.1.1
PE1(config-router)#neighbor 4.4.4.4 remote-as 1
/*The ASs at both ends must be the same. If they are the same, the device
is in IBGP routing mode. Otherwise the device is in EBGP mode.*/
PE1(config-router)#neighbor 4.4.4.4 update-source 1.1.1.1
PE1(config-router)#address-family vpnv4
/*Configure a public network neighbor and ensure that the public network
routes are available, that is, the LSR-ID of the peer is reachable. If
there are multiple PE devices, you need to configure multiple public
network neighbors which are irrelevant with IPv4 private network
neighbors.*/
PE1(config-router-af)#neighbor 4.4.4.4 activate
PE1(config-router-af)#neighbor 4.4.4.4 send-community extended
/*You must adopt the extended mode. L3VPN is implemented based on
extended BGP.*/
PE1(config-router-af)#exit-address-family
PE1(config-router)#address-family ipv4 vrf vpn1
/*Configure IPv4 private network neighbors to match VRFs. If there are
multiple VRFs, configure multiple IPv4 neighbors and configure multiple
IPv4 private network neighbors on the peer end. This does not affect
VPNv4 public network neighbors.*/
PE1(config-router-af)#redistribute static

Raisecom Proprietary and Confidential

257
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

PE1(config-router-af)#redistribute connected
PE1(config-router-af)#exit-address-family
PE1(config-router)#exit

PE 2

PE2(config)#router bgp 1
PE2(config-router)#bgp router-id 4.4.4.4
PE2(config-router)#neighbor 1.1.1.1 remote-as 1
PE2(config-router)#neighbor 1.1.1.1 update-source 4.4.4.4
PE2(config-router)#address-family vpnv4
PE2(config-router-af)#neighbor 1.1.1.1 activate
PE2(config-router-af)#neighbor 1.1.1.1 send-community extended
PE2(config-router-af)#exit-address-family
PE2(config-router)#address-family ipv4 vrf vpn1
PE2(config-router-af)#redistribute static
PE2(config-router-af)#redistribute connected
PE2(config-router-af)#exit-address-family
PE2(config-router)#exit

Step 9 Configure a static route pointing to CE 1 on PE 1 and configure a static route pointing to CE 2
on PE 2.
PE 1

PE1(config)#ip route vrf vpn1 5.5.5.5 255.255.255.255 10.10.10.1

PE 2

PE2(config)#ip route vrf vpn1 6.6.6.6 255.255.255.255 10.10.1.2

Step 10 Configure the gateway IP address on CE 1 and CE 2 respectively.

CE 1

CE1(config)#ip route 0.0.0.0 0.0.0.0 10.10.10.2

CE 2

CE2(config)#ip route 0.0.0.0 0.0.0.0 10.10.4.1

Raisecom Proprietary and Confidential

258
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Checking configurations
 Use the show ip vrf detail command to show VRF configurations on PE 1 and PE 2.
PE 1

PE1(config)#show ip vrf detail

Total VRF configured : 1

VRF: vpn1 ID: 1

Creation time: 2016/02/14 03:22:40
Up time: 1d18h04m
Route Distinguisher: 100:1
Import RT: 100:1
Export RT: 100:1
Label policy: label per vrf Label: 10241

PE 2

PE2(config)#show ip vrf detail

Total VRF configured : 1

VRF: vpn1 ID: 1

Creation time: 2016/02/14 03:22:40
Up time: 1d18h04m
Route Distinguisher: 100:1
Import RT: 100:1
Export RT: 100:1
Label policy: label per vrf Label: 10241

 Use the show ip route command to show whether the routes of public network learned
by various PE devices and P devices are correct. Take PE 1 for example.
PE 1

PE1(config)#show ip route
Routing Tables: Default-IP-Routing-Table
-------------------------------------------------------------------------
--
Flag: C - connected, S - static, R - RIP, B - BGP, O - OSPF, I - IS-IS
P - Protocol, s - States, > - selected , * - active, Dis - Distance

P&s Destination/Mask Dis/Metric NextHop Age Interface

C>* 1.0.0.0/8 0/0 1.1.1.2 1d20h13m GE1/1/1

C>* 1.1.1.2/32 0/0 127.0.0.1 1d20h13m lo0
O>* 132.1.84.18/32 110/2 132.1.84.18 00:12:42 GE1/1/1.4094
C>* 10.10.1.0/24 0/0 10.10.1.2 04w4d21h GE1/1/2
C>* 172.16.70.82/32 0/0 127.0.0.1 04w4d21h lo0

Raisecom Proprietary and Confidential

259
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

 Use the show interface tunnel command to show whether Tunnel configurations on PE
1 and PE 2 are correct. Take PE 1 for example.
PE 1

PE1(config)#show interface tunnel

tunnel1/1/1 is DOWN, Admin status is UP
Hardware is NULL, MAC is 0000.0000.0000
Peer Address is 0.0.0.0
MTU 1500 bytes
Last 300 seconds period input rate 0 bytes/sec, 0 packets/sec
Last 300 seconds period output rate 0 bytes/sec, 0 packets/sec
Input Statistics:
0 ifInPkts,
0 ifInBytes,
0 ifInDropPkts,
0 ifInDropBytes,
Output Statistics:
0 ifOutPkts,
0 ifOutBytes,
0 ifOutDropPkts,
0 ifOutDropBytes,

 Use the show ip bgp neighbor command to show whether PE 1 and PE 2 have
established BGP neighbors.

PE1(config)#show ip bgp neighbor

BGP neighbor is 4.4.4.4, remote AS 1, local AS 1, internal link
BGP version 4, remote router ID 0.0.0.0
BGP state = Active
Last read 00:10:57, hold time is 180, keepalive interval is 60 seconds
Message statistics:
Inq depth is 0
Outq depth is 0
Sent Rcvd
Opens: 0 0
Notifications: 0 0
Updates: 0 0
Keepalives: 0 0
Route Refresh: 0 0
Total: 0 0
Minimum time between advertisement runs is 5 seconds

For address family: IPv4 Unicast

0 accepted prefixes

For address family: VPNv4 Unicast

Community attribute sent to this neighbor(extended)
0 accepted prefixes

Connections established 0; dropped 0

Last reset never

Raisecom Proprietary and Confidential

260
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 11 VPN

Next connect timer due in 73 seconds

Read thread: off Write thread: off
BFD session ID:0

 Use the show ip bgp vpnv4 all command to check whether PE devices have learned
vpnv4 neighbor.

PE1(config)#show ip bgp vpnv4 all

Local router ID is 1.1.1.1
Status codes: s - suppressed, d - damped, h - history, * - valid, > -
best, i - internal, S - Stale, R - Removed
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path

Route Distinguisher: 1:1
*> 30.0.0.0 100.0.0.10 0 32768 ?
Routes of vpn-instance: 1

*> 30.0.0.0 100.0.0.10 0 32768 ?

Raisecom Proprietary and Confidential

261
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

12 QoS

This chapter describes principles and configuration procedures of QoS, as well as related
configuration examples, including following sections:
 Configuring ACL
 Configuring priority trust and priority mapping
 Configuring traffic classification and traffic policy
 Configuring congestion avoidance and queue shaping
 Configuring rate limiting
 Configuring bandwidth rate limiting
 Configuring MPLS QoS CAR
 Configuring L3VPN QoS
 Configuring MPLS H-QoS
 Maintenance
 Configuration examples

12.1 Configuring ACL

12.1.1 Preparing for configurations

Scenario
To filter data packets, the device needs to be configured with ACL to identify data packets to
be filtered. Devices allow/disallow related data packets to pass based on pre-configured
policies unless they identify specified data packets.

Prerequisite
N/A

12.1.2 Configuring ACL

Select Steps 3–7 as required.

Raisecom Proprietary and Confidential

262
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#access-list acl-number Create an ACL and enter ACL configuration
mode.
The value of acl-number parameter defines
the type of ACL configuration mode.
 Values 1000–0999: basic IP ACL
 Values 2000–2999: extended IP ACL
 Values 3000–3999: MAC ACL
 Values 4000–4999: MPLS ACL
 Values 5000–5999: MAP ACL
 Values 6000–6999: basic IPv6 ACL
 Vaules 7000–7999: extended IPv6 ACL

3 Raisecom(config-acl-ipv4-basic)#rule (Optional) configure the basic IP ACL rule.

[ rule-id ] { deny | permit } { source-ip-
address source-ip-mask | any } [ vrf vrf-
name ]
4 Raisecom(config-acl-ipv4-advanced)#rule (Optional) configure the extended IP ACL
[ rule-id ] { deny | permit } { protocol-id rule.
| icmp | igmp | ip } { source-ip-address
source-ip-mask | any } { destination-ip-
address destination-ip-mask | any } [ dscp
dscp-value ] [ ttl ttl-value ] [ vrf vrf-
name ]
Raisecom(config-acl-ipv4-advanced)#rule
[ rule-id ] { deny | permit } { tcp | udp }
{ source-ip-address source-ip-mask | any }
[ source-port ]{ destination-ip-address
destination-ip-mask | any } [ destination-
port ] [ dscp dscp-value ] [ ttl ttl-
value ] [ vrf vrf-name ]
5 Raisecom(config-acl-ipv6-basic)#rule (Optional) configure basic IPv6 ACL rules.
[ rule-id ] { deny | permit } { source-ip-
address/prefix-length | any }
6 Raisecom(config-acl-ipv6-advanced)#rule (Optional) configure extended IPv6 ACL
[ rule-id ] { deny | permit } { protocol-id rules.
| ipv6 } { source-ip-address/prefix-length
| any } { destination-ip-address/prefix-
length | any } [ dscp dscp-value ]
Raisecom(config-acl-ipv6-advanced)#rule
[ rule-id ] { deny | permit } { tcp | udp }
{ source-ip-address/prefix-length | any }
[ source-port ]{ destination-ip-address
destination-ip-mask | any } [ destination-
port ] [ dscp dscp-value ]
7 Raisecom(config-acl-mac)#rule [ rule-id ] (Optional) configure the MAC ACL rule.
{ deny | permit } { source-mac-address
source-mac-mask | any } { destination-mac-
address destination-mac-mask | any }
[ ethertype { ethertype [ ethertype-mask ]
| ip | arp } ] [ svlan svlanid svlan-cos
svlan-cos ] [ cvlan cvlanid cvlan-cos
cvlan-cos ]
Raisecom Proprietary and Confidential
263
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Step Command Description

8 Raisecom(config-acl-mpls)#rule [ rule-id ] (Optional) configure the MPLS ACL rule.
{ deny | permit } label { label-value |
any } [ exp exp-value ] [ ttl ttl-value ]
[ second-label { label-value | any }
[ second-exp exp-value ] [ second-ttl ttl-
value ] ] [ third-label { label-value |
any } [ third -exp exp-value ] [ third -ttl
ttl-value ] ]
9 Raisecom(config-acl-map)#rule [ rule-id ] (Optional) configure the MAP ACL rule.
{ deny | permit } [ source-mac source-mac-
address source-mac-mask ] [ dest-mac
destination-mac-address destination-mac-
mask ] [ ethertype { ethertype [ ethertype-
mask ] | ip | arp } ] [ svlan svlanid
svlan-cos svlan-cos ] [ cvlan cvlanid
cvlan-cos cvlan-cos ] rule-string rule-mask
offset
10 Raisecom(config-acl-*)#description string Configure ACL descriptions.
Raisecom(config-acl-*)#exit
11 Raisecom(config)#access-list copy dest-acl- Copy to generate the same ACL rule.
number source-acl-number

12.1.3 Configuring filter

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)#filter Apply the ACL rule to the interface. The ACL rule
{ ingress | egress } access-list cannot be modified once it is applied to the interface and
acl-number [ statistics ] the number of ACL rules must be greater than 0.

12.1.4 Checking configurations

No. Command Description
1 Raisecom#show access-list [ acl-number ] Show ACL information.
2 Raisecom#show acl resource Show ACL resource information.
3 Raisecom#show filter interface Show filter information.
Raisecom#show filter interface interface-type
interface-number [ ingress | egress ]
Raisecom#show filter statistics interface interface-
type interface-number { ingress | egress } access-
list acl-number

Raisecom Proprietary and Confidential

264
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

12.2 Configuring priority trust and priority mapping

12.2.1 Preparing for configurations

Scenario
For packets from upstream devices, you can select to trust the priorities taken by these packets.
For packets whose priorities are not trusted, you can process them with traffic classification
and traffic policy. In addition, you can modify DSCP priorities by configure interface-based
DSCP priority remarking. After configuring priority trust, the iTN8800 can perform different
operations on packets with different priorities, providing related services.
Before performing queue scheduling, you need to assign a local priority for a packet. For
packets from the upstream device, you can map the outer priorities of these packets to various
local priorities. In addition, you can directly configure local priorities for these packets based
on interfaces. And then device will perform queue scheduling on these packets basing on local
priorities.
In general, for IP packets, you need to configure the mapping between DHCP priority and
local priority. For VLAN packets, you need to configure the mapping between CoS priority
and local priority. For MPLS packets, you need to configure the mapping between the Exp
field and the local priority.

Prerequisite
N/A

12.2.2 Configuring priority trust

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#mls qos trust Configure the priority trusted by an interface.
{ cos | dscp }
By default, the Layer 2 interface trusts the CoS
priority and the Layer 3 interface trusts the
DHCP priority.
4 Raisecom(config-port)#mls qos priority Configure the interface priority.
untagged priority
By default, it is 5.

12.2.3 Configuring mapping between DSCP priority and local

priority based on interface
Step Command Description
1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

265
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Step Command Description

2 Raisecom(config)#mls qos mapping dscp-to- Create the DSCP-to-local priority (color)
local-priority profile-id mapping profile and enter dscp-to-pri
configuration mode.
3 Raisecom(dscp-to-pri)#dscp dscp-value to Configure mapping between the DSCP
local-priority localpri-value [ color priority and local priority (color).
{ green | red | yellow } ]
4 Raisecom(dscp-to-pri)#exit Exit dscp-to-pri configuration mode.
Raisecom(config)#interface interface-type
interface-number Enter interface configuration mode.
5 Raisecom(config-port)#mls qos dscp-to-local- Apply the DSCP-to-local priority (color)
priority profile-id mapping profile to an interface.

12.2.4 Configuring mapping between CoS priority and local priority

based on interface
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mls qos mapping cos-to- Create the CoS-to-local priority (color)
local-priority profile-id mapping profile and enter cos-to-pri
configuration mode.
3 Raisecom(dscp-to-pri)#cos cos-value to Configure mapping between the CoS
local-priority localpri-value [ color priority and local priority (color).
{ green | red | yellow } ]
4 Raisecom(dscp-to-pri)#exit Exit cos-to-pri configuration mode.
Raisecom(config)#interface interface-type
interface-number Enter interface configuration mode.
5 Raisecom(config-port)#mls qos cos-to-local- Apply the CoS-to-local priority (color)
priority profile-id mapping profile to an interface.

12.2.5 Configuring mapping between Exp and local priority

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mls qos mapping exp-to- Create the Exp-to-local priority (color)
local-priority profile-id mapping profile and enter exp-to-pri
configuration mode.
3 Raisecom(dscp-to-pri)#exp exp-value to Configure mapping between the Exp and
local-priority localpri-value [ color local priority (color).
{ green | red | yellow } ]

Raisecom Proprietary and Confidential

266
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

12.2.6 Configuring DSCP priority remarking

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mls qos mapping dscp- Create the DSCP remarking profile and
mutation profile-id enter dscp-mutation configuration mode.
3 Raisecom(dscp-to-pri)#dscp dscp-value to Remark the DSCP priority of specified
new-dscp dscp-value packets.
4 Raisecom(dscp-to-pri)#exit Exit dscp-mutation configuration mode.
Raisecom(config)#interface interface-type
interface-number Enter interface configuration mode.
5 Raisecom(config-port)#mls qos dscp-mutation Apply the DSCP remarking profile to an
profile-id interface.

12.2.7 Configuring CoS priority remarking

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mls qos mapping cos-remark Create the CoS remarking profile and enter
profile-id dscp-remark configuration mode.
3 Raisecom(dscp-to-pri)#local-priority Configure the mapping between the local
localpri-value to cos cos-value priority and CoS priority.
4 Raisecom(dscp-to-pri)#exit Exit cos-remark configuration mode.
Raisecom(config)#interface interface-type
interface-number Enter interface configuration mode.
5 Raisecom(config-port)# mls qos cos-remark- Enable local priority-to-CoS mapping.
mapping enable
6 Raisecom(config-port)#mls qos cos-remark Apply the CoS remarking profile to an
profile-id interface.

12.2.8 Configuring Exp remarking

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mls qos mapping local- Create the local priority-to-Exp mapping
priority-to-exp profile-id profile and enter pri-to-exp configuration
mode.
3 Raisecom(dscp-to-pri)#local-priority Configure the mapping between the local
localpri-value to exp exp-value priority and Exp.

Raisecom Proprietary and Confidential

267
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

12.2.9 Checking configurations

No. Command Description
1 Raisecom#show mls qos mapping dscp-to-local- Show information about the DSCP-to-
priority [ default | profile-id ] local priority (color) mapping profile.
2 Raisecom#show mls qos mapping cos-to-local- Show information about the CoS-to-local
priority [ default | profile-id ] priority (color) mapping profile.
3 Raisecom#show mls qos mapping exp-to-local- Show information about the Exp-to-local
priority [ default | profile-id ] priority (color) mapping profile.
4 Raisecom#show mls qos mapping dscp-mutation Show information about the DSCP
[ default | profile-id ] remarking profile.
5 Raisecom#show mls qos mapping cos-remark Show information about the CoS
[ default | profile-id ] remarking profile.
6 Raisecom#show mls qos mapping local-priority- Show information about the local
to-exp [ default | profile-id ] priority-to-Exp mapping profile.
7 Raisecom#show mls qos interface [ interface- Show QoS information on the interface.
type interface-number ]

12.3 Configuring traffic classification and traffic policy

12.3.1 Preparing for configurations

Scenario
Traffic classification is the basis of QoS. For packets from upstream devices, you can classify
them according to ACL rules. After traffic classification, the device can provide related
operations for different packets, providing differentiated services.
After configurations, the traffic classification cannot take effect until being bound to traffic
policy. The selection of traffic policy depends on the packet status and current network load
status. In general, when a packet is sent to the network, you need to limit the speed according
to Committed Information Rate (CIR) and remark the packet according to the service feature.

Prerequisite
N/A

12.3.2 Creating and configuring traffic classification

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#class- Create traffic classification and enter CMAP configuration mode.
map class-map-name

Raisecom Proprietary and Confidential

268
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Step Command Description

3 Raisecom(config- Define the ACL matched with the traffic classification. ACL rules
cmap)#match acl acl- cannot be modified once they are applied to the interface. The
number number of ACL rules must be greater than 0.

12.3.3 Creating and configuring traffic policing profile

To perform traffic policing on packets, you need to configure traffic policing profile and then
quote this profile under the traffic classification, which is bound to traffic policy.
On the traffic policing profile, you can configure traffic policing rules or perform relate
operations on specified packets based on color.
The single bucket does not support the color-sensitive mode or commands with the yellow
key word.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mls qos policer-profile Create the traffic policing profile and enter
policer-name [ single ] traffic policing profile configuration mode.
3 Raisecom(traffic-policer)#color-mode (Optional) configure the color-mode.
{ aware | blind }
By default, the traffic policing profile works
in blind mode.
4 Raisecom(traffic-policer)#drop-color (Optional) discard packets with specified
{ red | yellow } * color.
5 Raisecom(traffic-policer)#set-cos { green (Optional) configure the mapping between
green-value | red red-value | yellow packet color and CoS priority.
yellow-value } *
6 Raisecom(traffic-policer)#set-dscp (Optional) configure the mapping between
{ green green-value | red red-value | packet color and DHCP priority.
yellow yellow-value } *
7 Raisecom(traffic-policer)#set-pri { green (Optional) configure the mapping between
green-value | red red-value | yellow packet color and local priority.
yellow-value } *
8 Raisecom(traffic-policer)#recolor (Optional) re-color the packet.
{ green-recolor { red | yellow } | red-
recolor { green | yellow } | yellow-
QoS use the CAR to classify and color the
recolor { green | red } } * packet. The downstream network can accept
the color result of the upstream network or re-
color the packet based on its classification
standard.
9 Raisecom(traffic-policer)#cir cir cbs cbs (Optional) configure rate limiting parameters.
[ ebs ebs ]
Raisecom(traffic-policer)#cir cir cbs cbs
eir eir ebs ebs [ coupling ]
Raisecom(traffic-policer)#cir cir cbs cbs
pir pir pbs pbs

Raisecom Proprietary and Confidential

269
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

12.3.4 Creating and configuring traffic policy

Steps 5–10 are coordinate. You can select one as required.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#policy-map policy-map- Create a traffic policy and enter PMAP
name configuration mode.
3 Raisecom(config-pmap)#class-map class- Add the traffic classification to the traffic policy
map-name and enter CMAP configuration mode.

The traffic classification, bound with the

traffic policy, must be based on at least one
rule. Otherwise, the binding operation fails.
When the traffic policy is applied to an
interface, you cannot delete the bound
traffic classification or modify its
configuration.
One traffic classification can be applied to
multiple traffic policies.
4 Raisecom(config-pmap-c)#police policer- Import a traffic policing profile (policer) into the
name traffic policy.
5 Raisecom(config-pmap-c)#set { cos cos- (Optional) configure packet remarking.
value | ip dscp ip-dscp-value | local-
priority value }
Raisecom(config-pmap-c)#set { inner-
vlan inner-vlan-id | vlan vlan-id }
6 Raisecom(config-pmap-c)#add outer-vlan (Optional) configure the VLAN ID of the added
vlan-id outer VLAN Tag.
7 Raisecom(config-pmap-c)#redirect-to (Optional) configure the redirection rule to
interface-type interface-number forward matched packets through the specified
interface.
8 Raisecom(config-pmap-c)#copy-to-mirror (Optional) copy the traffic to the mirroring
mirror-group group-id monitoring interface.
9 Raisecom(config-pmap-c)#forward-to-cpu (Optional) forward traffic to the CPU.
10 Raisecom(config-pmap-c)#statistics (Optional) enable traffic statistics.
enable
11 Raisecom(config-pmap-c)#exit Exit CMAP configuration mode.
Raisecom(config-pmap)#exit
Raisecom(config)#interface interface-
Exit PMAP configuration mode.
type interface-number Enter interface configuration mode.
12 Raisecom(config-port)#service-policy Apply the traffic policy to an interface.
{ ingress | egress } policy-map-name

Raisecom Proprietary and Confidential

270
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

12.3.5 Checking configurations

No. Command Description
1 Raisecom#show class-map [ class-map-name ] Show traffic classification
information.
2 Raisecom#show mls qos policer-profile [ policer- Show traffic policing rules.
name ]
3 Raisecom#show policy-map [ policy-map-name ] [ class Show traffic policy information.
class-map-name ]
4 Raisecom#show service-policy interface Show information about applied
policies.
Raisecom#show service-policy interface interface-
type interface-number [ egress | ingress ]
5 Raisecom#show service-policy statistics interface Show statistics about applied
interface-type interface-number { egress | ingress } traffic policies.
policy-map policy-map-name [ class-map class-map-
name ]

12.4 Configuring congestion avoidance and queue shaping

12.4.1 Preparing for configurations

Scenario
To prevent network congestion from occurring and to resolve TCP global synchronization,
you can configure congestion avoidance to adjust the network traffic and resolve network
overload. The iTN8800 supports WRED-based congestion avoidance.
When the interface speed of downstream devices is smaller than the one of upstream devices,
congestion avoidance may occur on interfaces of downstream devices. At this time, you can
configure queue and traffic shaping on the egress interface of upstream devices to shape
upstream traffic.

Prerequisite
N/A

12.4.2 Configuring WRED profile

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mls qos wred Create the WRED profile and enter WRED profile
profile profile-id configuration mode.

Raisecom Proprietary and Confidential

271
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Step Command Description

3 Raisecom(wred)#wred [ color { green Configure WRED profile information.
| red | yellow } ] start-drop-
threshold start-drop end-drop- For non-TCP packets, it does not distinguish the
threshold end-drop max-drop- color. You need to configure the wred start-drop-
probability max-drop threshold/wred color green parameter.

12.4.3 Configuring flow profile

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mls qos flow-queue profile Create a flow profile and enter flow profile
flow-profile-id configuration mode.
3 Raisecom(flow-queue)#scheduler { drr| wrr } Configure the queue scheduling policy.
By default, it is DRR.
4 Raisecom(flow-queue)#queue queue-id [ weight Configure the queue, weight, shaping, and
weight-value ] [ shaping cir cir-value [ cbs WRED information of the flow profile. If
cbs-value ] pir pir-value [ pbs pbs- no weight is configured, SP scheduling
value ] ] [ wred profile profile-id ] mode is adopted.
5 Raisecom(flow-queue)#exit Exit flow profile configuration mode.
Raisecom(config)#interface interface-type
interface-number Enter interface configuration mode.

6 Raisecom(config-port)# mls qos flow-queue Apply the flow profile to an interface.

profile-id

12.4.4 Configuring queue shaping

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
3 Raisecom(config-port)#mls qos shaping Configure queue shaping for queues of the
{ ingress | egress } pir pir-value [ pbs interface.
pbs-value ]

12.4.5 Checking configurations

No. Command Description
1 Raisecom#show mls qos wred profile [ profile- Show WRED profile configurations.
list ]
2 Raisecom#show mls qos flow-queue profile Show flow profile configurations.
flow-profile-list

Raisecom Proprietary and Confidential

272
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

No. Command Description

3 Raisecom#show mls qos queue interface Show interface queue information.
interface-type interface-number
4 Raisecom#show mls qos shaping interface Show queue shaping information.
[ interface-type interface-number [ ingress |
egress ] ]
5 Raisecom#show mls qos queue statistics Show queue statistics of the interface.
interface interface-type interface-number

12.5 Configuring rate limiting

12.5.1 Preparing for configurations

Scenario
To avoid/remit network congestion, you can configure interface-based rate limiting. Rate
limiting is used to make packets transmitted at a relative average speed by controlling the
burst traffic on an interface.

Prerequisite
N/A

12.5.2 Configuring interface-based rate limiting

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number
3 Raisecom(config-port)#rate-limit { egress | Configure interface-based rate
ingress } cir cir-value cbs cbs-value pir pir- limiting.
value pbs pbs-value

 By default, no interface-based rate limiting is configured.

 Adopt the drop processing mode for packets on the ingress interface, if they
exceed the configured rate limiting value.
 When you configure the rate limiting value and burst value for an interface, if the
configured rate limiting value is smaller than 256 Kbit/s, the burst value should not
be much greater. Otherwise, packets may be inconsecutive.
 When the rate limiting value is too small, we recommend that the burst value is 4
times greater than then rate limiting value. If packets are inconsecutive, reduce
the burst value or increase the rate limiting value.

Raisecom Proprietary and Confidential

273
Copyright © Raisecom Technology Co., Ltd.
 Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

12.5.3 Checking configurations

No. Command Description
1 Raisecom#show rate-limit interface Show interface-based rate limiting.
Raisecom#show rate-limit interface
interface-type interface-number [ ingress |
egress ]

12.6 Configuring bandwidth rate limiting

12.6.1 Preparing for configurations

Scenario
Bandwidth rate limiting is for ensuring users' requirements on service bandwidths and
protecting network resources and interests of carriers.

Prerequisite
N/A

12.6.2 Default configurations of bandwidth rate limiting

Default configurations of bandwidth rate limiting are as below.

Function Default value

Color identification Disabled

12.6.3 Configuring bandwidth guarantee

Creating bandwidth guarantee template

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#bandwidth-profile bwp-profile-id Create a bandwidth guarantee
cir cir cbs cbs [ color-aware ] template.
Raisecom(config)#bandwidth-profile bwp-profile-id
cir cir cbs cbs eir eir ebs ebs [ color-aware
[ coupling ] ]

3 Raisecom(config)#bandwidth-profile bwp-profile-id Configure the description of the

description word bandwidth guarantee template.

Raisecom Proprietary and Confidential

274
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

If the bandwidth guanrantee template is quoted by other hierarchical templates or is

applied, you will fail to delete it.

12.6.4 Configuring hierarchical bandwidth gaurantee

Configuring hierarchical CoS bandwidth guarantee

No. Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#bandwidth-profile profile-id cir Create a bandwidth guarantee
cir cbs cbs [ eir eir ebs ebs ] [ color-aware ] template.
3 Raisecom(config)#hierarchy-cos bandwidth-profile Create a hierarchical CoS template
hc-profile-id and enter HCoS configuration mode.
4 Raisecom(config-hcos)#bandwidth coslist cos-list Configure a hierarchical CoS
bwp-profile-id template.
Raisecom(config-hcos)#exit

5 Raisecom(config)#interface interface-type Apply the hierarchical CoS template

interface-number on the sub-interface.
Raisecom(config-port)#bandwidth { ingress |
egress } bwp-profile-id hierarchy-cos hc-profile-
id

Configuring hierarchical DSCP bandwidth guarantee

No. Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#bandwidth-profile profile-id cir Create a bandwidth guarantee
cir cbs cbs [ eir eir ebs ebs ] [ color-aware ] template.
3 Raisecom(config)#hierarchy-dscp bandwidth-profile Create a hierarchical DSCP template
hd-profile-id and enter HDSCP configuration
mode.
4 Raisecom(config-hdscp)#bandwidth dscplist dscp-list Configure a hierarchical DSCP
bwp-profile-id template.
Raisecom(config-hdscp)#exit

5 Raisecom(config)#interface interface-type Apply the hierarchical DSCP

interface-number template to the sub-interface.
Raisecom(config-port)# bandwidth { ingress |
egress } bwp-profile-id hierarchy-dscp hd-
profile-id

Raisecom Proprietary and Confidential

275
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Configuring hierarchical IPP bandwidth guarantee

No. Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#bandwidth-profile profile-id cir Create a bandwidth guarantee
cir cbs cbs [ eir eir ebs ebs ] [ color-aware ] template.
3 Raisecom(config)#hierarchy-ipp bandwidth-profile Create a hierarchical IPP template
hi-profile-id and enter HIPP configuration mode.
4 Raisecom(config-hipp)#bandwidth ipplist ipp-list Configure a hierarchical IPP
bwp-profile-id template.
Raisecom(config-hipp)#exit

5 Raisecom(config)#interface interface-type Apply the hierarchical IPP template

interface-number to the sub-interface.
Raisecom(config-port)# bandwidth { ingress |
egress } bwp-profile-id hierarchy-ipp ipp-
profile-id

If the hierarchical bandwidth guarantee template is alreardy applied, you will fail to
delete or modify it.

12.6.5 Checking configurations

No. Command Description
1 Raisecom#show bandwidth-profile [ bwp-profile- Show information about the bandwidth
id ] guarantee template.
2 Raisecom#show bandwidth interface interface- Show bandwidth guarantee
type interface-number configurations on the interface.
3 Raisecom#show hierarchy-cos-bandwidth profile Show information about the
[ hc-profile-id ] hierarchical CoS bandwidth guarantee
template.
4 Raisecom#show hierarchy-dscp-bandwidth profile Show information about hierarchial
[ hd-profile-id ] DSCP bandwidth gurantee template.

Raisecom Proprietary and Confidential

276
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

12.7 Configuring MPLS QoS CAR

12.7.1 Preparing for configurations

Scenario
The MPLS-TP QoS technology is used to ensure the instantaneity and integrity of services
when the MPLS network is overloaded or congested. In addition, it is used to ensure the
whole MPLS-TP network to run efficiently.

Prerequisite
Connect interfaces and configure physical parameters of interfaces. Make the physical layer
Up.

12.7.2 Configuring LSP QoS CAR

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface tunnel interface- Enter Tunnel interface configuration
number mode.
3 Raisecom(config-tunnel)#bandwidth car [ cir cir- Configure the LSP bandwidth.
value pir pir-value ]
4 Raisecom(config-tunnel)#traffic-statistics Enable LSP statistics.
enable
5 Raisecom(config-tunnel)#diffserv-mode { pipe Configure the Tunnel differential
exp-value | uniform [ local-priority-to-exp service mode.
profile-id ] }
6 Raisecom(config-tunnel)#exit Exit Tunnel interface configuration
Raisecom(config)#mpls static-lsp egress lsp-name mode.
diffserv-mode { pipe [ exp-to-local-priority
profile-id ] | uniform [ exp-to-local-priority Configure Egress differential service
profile-id ] } mode.

12.7.3 Configuring PWE3 QoS CAR

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type interface- Enter interface configuration
number mode.
3 Raisecom(config-port)#mpls l2vpn pw bandwidth car Configure PWE3 applied
[ cir cir-value pir pir-value ] [ backup ] bandwidth.
4 Raisecom(config-port)#mpls l2vpn pw traffic- Enable PW statistics.
statistics enable [ backup ]

Raisecom Proprietary and Confidential

277
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Step Command Description

5 Raisecom(config-port)#mpls l2vpn pw diffserv-mode Configure the PWE3 differential
{ pipe exp-value [ exp-to-local-priority profile- service mode.
id ] | uniform [ exp-to-local-priority profile-id ]
[ local-priority-to-exp profile-id ] } [ backup ]

12.7.4 Configuring VPLS QoS CAR

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls vsi vsi-name static Create a VSI and enter VSI
configuration mode.
3 Raisecom(config-vsi)#mpls peer peer-ip-address Configure VPLS applied bandwidth.
vc-id vc-id bandwidth car [ cir cir-value pir
pir-value ] [ backup ]
4 Raisecom(config-vsi)#mpls peer peer-ip-address Configure the VPLS flow profile.
[ vc-id vc-id ] [ weight weight-value ] [ flow-
queue flow-queue-id ]
5 Raisecom(config-vsi)#traffic-statistics [ peer Enable VPLS statistics.
peer-ip-address [ vc-id vc-id ] ] enable

12.7.5 Checking configurations

No. Command Description
1 Raisecom#show mpls te traffic-statistics tunnel Show LSP statistics.
unit/slot/port
2 Raisecom#show mpls l2vpn pw traffic-statistics Show PW statistics.
interface-type interface-number [ backup ]
3 Raisecom#show mpls vsi traffic-statistics vsi-name Show VPLS statistics.
peer peer-ip-address vc-id vc-id

12.8 Configuring L3VPN QoS

12.8.1 Preparing for configurations

Scenario
To avoid or remit network congestion, you can configure L3VPN QoS.

Prerequisite
N/A

Raisecom Proprietary and Confidential

278
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

12.8.2 Configuring VRF QoS

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip vrf vrf-name Create a VRF and enter VRF
configuration mode.
3 Raisecom(config-vrf)#bandwidth car [ cir cir-value Configure the bandwidth limit
pir pir-value ] peer ip-address based on peer in CAR mode.
Raisecom(config-vrf)#bandwidth hqos [ cir cir-value Configure the bandwidth limit
pir pir-value ] [ weight weight-value ] [ flow- based on peer in H-QoS mode.
queue queue-number ] peer ip-address
4 Raisecom(config-vrf)#traffic-statistics enable Enable L3VPN VRF statistics.
5 Raisecom(config-vrf)#diffserv-mode { pipe exp-value Configure the L3VPN differential
[ exp-to-local-priority profile-id ] | uniform service mode.
[ exp-to-local-priority profile-id ] [ local-
priority-to-exp profile-id ] }
6 Raisecom(config-vrf)#ttl { pipe | uniform } Configure the TTL mode.
By default, it is Pipe mode.

12.8.3 Checking configurations

No. Command Description
1 Raisecom#show vrf traffic-statistics vrf-name Show VPLS statistics.

12.9 Configuring MPLS H-QoS

12.9.1 Preparing for configurations

Scenario
H-QoS is generally used in the conditions which require distinguishing services, users, and
user groups. For example,
 User services are divided into voice and internet services. Users are divided into
department manager and employees. User groups are divided into president office and
property management department. All services are accessed to the upper network
through one interface.
 Through H-QoS, all services in the president office can be prioritized, all services of the
manager in the president office can be prioritized, and all voice services of the manager
in the president office can be prioritized.

Raisecom Proprietary and Confidential

279
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Prerequisite
MPLS QoS CAR and MPLS H-QoS conflict with each other. Make sure that the device is not
configured with MPLS QoS CAR before configuring H-QoS.

12.9.2 Configuring H-QoS of LSP

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface tunnel interface- Enter Tunnel interface configuration
number mode.
3 Raisecom(config-tunnel)#bandwidth hqos [ cir Configure LSP hierarchical
cir-value pir pir-value ] [ weight weight- bandwidth.
value ]
4 Raisecom(config-tunnel)#traffic-statistics Enable LSP statistics.
enable
5 Raisecom(config-tunnel)#diffserv-mode { pipe Configure the differential service
exp-value | uniform [ local-priority-to-exp mode of Tunnel.
profile-id ] }
6 Raisecom(config-tunnel)#exit Exit Tunnel interface configuration
Raisecom(config)#mpls static-lsp egress lsp-name mode.
diffserv-mode { pipe [ exp-to-local-priority
profile-id ] | uniform [ exp-to-local-priority Configure the differential service
profile-id ] } mode of egress.

12.9.3 Configuring H-QoS of PWE3

Configure the iTN8800 as below. Make sure that the corresponding interfaces are configured
with the following services before configuring H-QoS of PWE3.
 The interface should be in the routed mode. By default, it is in the routed mode. If the
interface is configured to the switch mode, use the no portswitch command to switch the
interface to routed mode.
 Use the mode l2 command to enter L2VPN mode to access L2VPN services.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type interface- Enter interface configuration
number mode.
3 Raisecom(config-port)#mpls l2vpn pw bandwidth hqos Configure PWE3 bandwidth
[ cir cir-value pir pir-value ] [ weight weight- template.
value ] [ flow-queue queue-number ]
4 Raisecom(config-port)#mpls l2vpn pw traffic- Enable PW statistics.
statistics enable [ backup ]
5 Raisecom(config-port)#mpls l2vpn pw diffserv-mode Configure the differential
{ pipe exp-value [ exp-to-local-priority profile- service mode of PWE3.
id ] | uniform [ exp-to-local-priority profile-id ]
[ local-priority-to-exp profile-id ] }

Raisecom Proprietary and Confidential

280
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

12.9.4 Configuring H-QoS of VPLS.

Step Command Description
1 Raisecom#config Enter global configuration mode
2 Raisecom(config)#mpls vsi vsi-name static Creat a VSI and enter VSI
configuration mode.
3 Raisecom(config-vsi)#mpls peer peer-ip-address [ vc- Configure a VPLS flow
id vc-id ] bandwidth hqos [ cir cir-value pir pir- template.
value ] [ weight weight-value ] [ flow-queue queue-
number ]
4 Raisecom(config-vsi)#traffic-statistics [ peer peer- Enable VPLS statistics.
ip-address [ vc-id vc-id ] ] enable

12.9.5 Checking configurations

No. Command Description
1 Raisecom#show mpls te tunnel Show LSP H-QoS configurations.
2 Raisecom#show mpls l2vc Show PWE3 H-QoS configurations.
3 Raisecom#show mpls vsi detail Show VPLS H-QoS configurations.

12.10 Maintenance
Command Description
Raisecom(config)#clear service-policy statistics Clearing traffic policy statistics.
interface interface-type interface-number { egress |
ingress }
Raisecom(config)#clear service-policy statistics
interface interface-type interface-number { egress |
ingress } policy-map policy-map-name [ class-map class-
map-name ]
Raisecom(config)#clear mls qos queue statistics interface Clear queue statistics of interfaces.
interface-type interface-number [ queueid queue-id ]
Raisecom(config)#clear filter statistics interface Clear ACL statistics.
interface-type interface-number { ingress | egress }
[ access-list acl-number ]
Raisecom(config)# clear mpls te traffic-statistics tunnel Clear LSP statistics.
tunnel-if-num
Raisecom(config)#clear mpls l2vpn pw traffic-statistics Clear PW statistics.
interface-type interface-number [ backup ]
Raisecom(config)#clear mpls vsi traffic-statistics vsi- Clear VPLS statistics.
name [ peer peer-ip-address vc-id vc-id ]
Raisecom(config)#clear vrf traffic-statistics vrf-name Clear L3VPN VRF statistics.

Raisecom Proprietary and Confidential

281
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

12.11 Configuration examples

12.11.1 Example for configuring rate limiting based on traffic policy

Networking requirements
As shown in Figure 12-1, User A, User B, and User C are respectively connected to the
iTN8800 through Router A, Router B, and Router C.
User A uses voice and video services; User B uses voice, video, and data services; User C
uses video and data services.
According to users' requirements, make the following rules:
 For User A, provide 25 Mbit/s bandwidth; configure the burst traffic to 100 KB, and
discard the redundant traffic.
 For User B, provide 35 Mbit/s bandwidth; configure the burst traffic to 100 KB, and
discard the redundant traffic.
 For User C, provide 30 Mbit/s bandwidth; configure the burst traffic to 100 KB, and
discard the redundant traffic.

Figure 12-1 Configuring rate limiting based on traffic policy

Configuration steps
Step 1 Create and configure traffic classification.

Raisecom#config
Raisecom(config)#access-list 1001
Raisecom(config-acl-ipv4-basic)#rule 1 permit 1.1.1.1 255.255.255.0
Raisecom(config-acl-ipv4-basic)#exit
Raisecom(config)#class-map usera
Raisecom(config-cmap)#match acl 1001

Raisecom Proprietary and Confidential

282
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Raisecom(config-cmap)#exit
Raisecom(config)#access-list 1002
Raisecom(config-acl-ipv4-basic)#rule 2 permit 1.1.2.1 255.255.255.0
Raisecom(config-acl-ipv4-basic)#exit
Raisecom(config)#class-map userb
Raisecom(config-cmap)#match acl 1002
Raisecom(config-cmap)#exit
Raisecom(config)#access-list 1003
Raisecom(config-acl-ipv4-basic)#rule 3 permit 1.1.3.1 255.255.255.0
Raisecom(config-acl-ipv4-basic)#exit
Raisecom(config)#class-map userc
Raisecom(config-cmap)#match acl 1003
Raisecom(config-cmap)#exit

Step 2 Create traffic policing profiles and configure rate limiting rules.

Raisecom(config)#mls qos policer-profile usera single

Raisecom(traffic-policer)#cir 25000 cbs 100
Raisecom(traffic-policer)#drop-color red
Raisecom(traffic-policer)#exit
Raisecom(config)#mls qos policer-profile userb single
Raisecom(traffic-policer)#cir 35000 cbs 100
Raisecom(traffic-policer)#drop-color red
Raisecom(traffic-policer)#exit
Raisecom(config)#mls qos policer-profile userc single
Raisecom(traffic-policer)#cir 30000 cbs 100
Raisecom(traffic-policer)#drop-color red
Raisecom(traffic-policer)#exit

Step 3 Create and configure traffic policies.

Raisecom(config)#policy-map usera
Raisecom(config-pmap)#class-map usera
Raisecom(config-pmap-c)#police usera
Raisecom(config-pmap-c)#exit
Raisecom(config-pmap)#exit
Raisecom(config)#interface gigaethernet 1/2/1
Raisecom(config-port)#service-policy ingress usera
Raisecom(config-port)#exit
Raisecom(config)#policy-map userb
Raisecom(config-pmap)#class-map userb
Raisecom(config-pmap-c)# police userb
Raisecom(config-pmap-c)#exit
Raisecom(config-pmap)#exit
Raisecom(config)#interface gigaethernet 1/2/2
Raisecom(config-port)#service-policy ingress userb
Raisecom(config)#policy-map userc
Raisecom(config-pmap)#class-map userc
Raisecom(config-pmap-c)#police userc
Raisecom(config-pmap-c)#exit

Raisecom Proprietary and Confidential

283
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Raisecom(config-pmap)#exit
Raisecom(config)#interface gigaethernet 1/2/3
Raisecom(config-port)#service-policy ingress userc

Checking results
Use the show class-map command to show configurations of traffic classification.

Raisecom#show class-map usera

Class Map usera (id 0) (ref 1)
Match acl 1001
Raisecom#show class-map userb
Class Map userb (id 1) (ref 1)
Match acl 1002
Raisecom#show class-map userc
Class Map userb (id 2) (ref 0)
Match acl 1003

Use the show mls qos policer-profile command to show configurations of rate limiting rules.

Raisecom#show mls qos policer-profile

single-policer: 123 mode:flow color:blind
cir: 0 kbps cbs: 0 kB

single-policer: po mode:flow color:blind

cir: 25000 kbps cbs: 1005 kB
red drop

single-policer: test2 mode:flow color:blind

cir: 0 kbps cbs: 0 kB

single-policer: user mode:flow color:blind

cir: 0 kbps cbs: 0 kB

single-policer: user0a mode:flow color:blind

cir: 0 kbps cbs: 0 kB

single-policer: usera mode:flow color:blind

cir: 25000 kbps cbs: 100 kB
red drop

Use the show policy-map command to show configurations of the traffic policy.

Raisecom#show policy-map usera

Policy Map usera
Class-map usera
police usera

Raisecom Proprietary and Confidential

284
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Raisecom#show policy-map userb

Policy Map userb
Class-map userb
police userb
Raisecom#show policy-map userc
Policy Map userc
Class-map userc
police userc

12.11.2 Example for configuring queue scheduling and congestion

avoidance

Networking requirements
As shown in Figure 12-2, User A uses voice and video services; User B uses voice, video, and
data services; User C uses video and data services.
CoS priorities for voice, video and, data services are configured to 5, 4, and 2 respectively.
CoS priorities are mapped to local priorities 6, 5, and 2 respectively.
Make the following rules based on service types.
 Perform SP scheduling on the voice service to ensure that the traffic is preferentially
transmitted.
 Perform WRR scheduling on the video service and configure the weight to 50.
 Perform WRR scheduling on the data service and configure the weight to 20. In addition,
you need to configure the discarding threshold to 50 to avoid network congestion caused
by too large instantaneous traffic.

Figure 12-2 Configuring queue scheduling and congestion avoidance

Raisecom Proprietary and Confidential

285
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Configuration steps
Step 1 Create a WRED profile.

Raisecom#config
Raisecom(config)#mls qos wred profile 1
Raisecom(wred)#wred start-drop-threshold 50 end-drop-threshold 90 max-
drop-probability 60
Raisecom(wred)#exit

Step 2 Configure the priority trust and congestion avoidance on interfaces.

Raisecom(config)#mls qos flow-queue profile 6

Raisecom(flow-queue)#scheduler wrr
Raisecom(flow-queue)#queue 6 weight 50
Raisecom(flow-queue)#queue 3 weight 20 wred profile 1
Raisecom(flow-queue)#exit
Raisecom(config)#interface gigaethernet 1/1/1
Raisecom(config-port)# mls qos flow-queue 6
Raisecom(config)#interface gigaethernet 1/2/1
Raisecom(config-port)#mls qos trust cos
Raisecom(config-port)#exit
Raisecom(config)#interface gigaethernet 1/2/2
Raisecom(config-port)#mls qos trust cos

Raisecom(config-port)#exit
Raisecom(config)#interface gigaethernet 1/2/3
Raisecom(config-port)#mls qos trust cos
Raisecom(config-port)#exit

Step 3 Configure the mapping between the CoS priority and local priority.

Raisecom(config)#mls qos mapping cos-to-local-priority 1

Raisecom(cos-to-pri)#cos 5 to local-priority 6
Raisecom(cos-to-pri)#cos 4 to local-priority 5
Raisecom(cos-to-pri)#cos 2 to local-priority 2
Raisecom(cos-to-pri)#exit
Raisecom(config)#interface interface gigaethernet 1/2/1
Raisecom(config-port)#mls qos cos-to-local-priority 1
Raisecom(config-port)#interface interface gigaethernet 1/2/2
Raisecom(config-port)#mls qos cos-to-local-priority 1
Raisecom(config-port)#interface interface gigaethernet 1/2/3
Raisecom(config-port)#mls qos cos-to-local-priority 1
Raisecom(config-port)#exit

Raisecom Proprietary and Confidential

286
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Checking results
Use the show mls qos mapping cos-to-local-priority command to show mapping
configurations on specified priorities.

Raisecom#show mls qos mapping cos-to-local-priority

G:GREEN
Y:Yellow
R:RED
cos-to-localpriority(color)
Index Description CoS: 0 1 2 3 4 5 6 7
-------------------------------------------------------------------------
1 localpri(color): 0(G) 1(G) 2(G) 3(G) 5(G) 6(G) 6(G) 7(G)

Use the show mls qos command to show configurations of priority trust and queue scheduling
mode on specified interfaces.

Raisecom#show mls qos interface gigaethernet 1/2/1

Interface TrustMode UntaggedPriority Cos-PriProfile Dscp-PriProfile
Dscp-Mutation Cos-Remark
-----------------------------------------------------------------------
gigaethernet1/2/1 cos 5 0 0 0
0

Use the show mls qos flow-queue command to show configurations of queue scheduling.

Raisecom#show mls qos flow-queue profile 2

CIR: Committed information rate,unit:Kbps
CBS: Committed burst size,unit:KB
PIR: Peak information rate,unit:Kbps
PBS: Peak burst size,unit:KB
ProfileIndex :2
Flow-Queue-Description :
Flow-Queue-Reference :3
Flow-Queue-Scheduler :wrr
QueueId Weight Wred CIR(Kbps) CBS(KB) PIR(Kbps) PBS(KB)
----------------------------------------------------------------
1 0 0 -- -- -- --
2 0 0 -- -- -- --
3 0 1 -- -- -- --
4 0 0 -- -- -- --
5 0 0 -- -- -- --
6 20 0 -- -- -- --
7 50 0 -- -- -- --
8 0 0 -- -- -- --

Use the show mls qos wred profile command to show configurations of the WRED profile.

Raisecom Proprietary and Confidential

287
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Raisecom#show mls qos wred profile

GSDT:Green Start Drop Threshold
GEDT:Green End Drop Threshold
GDP :Green Drop Probability
YSDT:Yellow Start Drop Threshold
YEDT:Yellow End Drop Threshold
YDP :Yellow Drop Probability
RSDT:Red Start Drop Threshold
REDT:Red End Drop Threshold
RDP :Red Drop Probability
Index Description Ref GSDT GEDT GDP YSDT YEDT YDP RSDT REDT RDP
-------------------------------------------------------------------------
1 3 50 90 60 50 90 60 50 90 60

12.11.3 Example for configuring interface-based rate limiting

Networking requirements
As shown in Figure 12-3, User A, User B, and User C are connected to the iTN8800 through
Switch A, Switch B, and Switch C.
User A uses voice and video services; User B uses voice, video, and data services; User C
uses video and data services.
According to users' requirements, make the following rules:
 For User A, provide 25 Mbit/s bandwidth; configure the burst traffic to 100 KB; set the
PIR to 50 Mbit/s, and configure the PBS to 200 KB.
 For User B, provide 35 Mbit/s bandwidth; configure the burst traffic to 100 KB; set the
PIR to 70 Mbit/s, and configure the PBS to 200 KB.
 For User A, provide 30 Mbit/s bandwidth; configure the burst traffic to 100 KB;
configure the PIR to 60 Mbit/s, and set the PBS to 200 KB.

Figure 12-3 Configuring interface-based rate limiting

Raisecom Proprietary and Confidential

288
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Configuration steps
 Configure interface-based rate limiting.

Raisecom#config
Raisecom(config)#interface gigaethernet 1/2/1
Raisecom(config-port)#rate-limit ingress cir 25000 cbs 100 pir 50000 pbs
200
Raisecom(config)#interface gigaethernet 1/2/2
Raisecom(config-port)# rate-limit ingress cir 35000 cbs 100 pir 70000 pbs
200
Raisecom(config)#interface gigaethernet 1/2/3
Raisecom(config-port)# rate-limit ingress cir 30000 cbs 100 pir 60000 pbs
200

Checking results
Use the show rate-limit interface command to show configurations of interface-based rate
limiting.
Raisecom#show rate-limit interface
Interface Direction Cir(kbps) Cbs(kB) Pir(kbps) Pbs(kB)
CirOper(kbps) CbsOper(kB) PirOper(kbps) PbsOper(kB)
-------------------------------------------------------------------------
-------------------------------------------------
gigaethernet1/2/1 ingress 25000 100 50000 200 25000
100 50000 200
gigaethernet1/2/2 ingress 35000 100 70000 200 35000
100 70000 200
gigaethernet1/2/3 ingress 30000 100 60000 200 30000
100 60000 200

12.11.4 Examples for configuring MPLS H-QoS

Networking requirements
As shown in Figure 12-4, User A, User B, and User C are connected to iTN8800 respectively
through the iTN201. The iTN8800 accesses different types of user services through the sub-
interfaces (all sub-interfaces are configured with the IP address, LSP, and so on).
User A requires voice and video services. User B requires voice, video, and data services.
User C requires video and data services. Services of User A, User B, and User C are
aggregated on the iTN8800 in the headquarter.
The headquarter has purchased the leased line services with 150 Mbit/s bandwidth. According
to the service requirements of different users, the following rules are formulated:
 The total traffic of User A should not exceed 80 Mbit/s, among which the committed
bandwidth is 50 Mbit/s.
 The total traffic of User B should not exceed 50 Mbit/s, among which the committed
bandwidth is 30 Mbit/s.

Raisecom Proprietary and Confidential

289
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

 The total traffic of User C should not exceed 50 Mbit/s, among which the committed
bandwidth is 10 Mbit/s.
 The total traffic of User A, User B, and User C together should not exceed 150 Mbit/s.
 Once the total traffic of User A, User B, and User C is congested, it is required that the
ratio of the high priority service traffic among User A, User B, and User C should be
5:3:1.
 The service priority of all service from high to low is voice, video, and data.
Figure 12-5 shows the priority scheduling of the configuration scheme according to the
above-mentioned networking requirements.

Figure 12-4 MPLS H-QoS networking

Figure 12-5 MPLS H-QoS priority scheduling

Configuration steps
Step 1 Configure the sub-interface to access different user services and configure the service priority
of the user (distinguish the priority of different services according to weight and traffic queue).
The following configurations are based on accessing User B services.

Raisecom Proprietary and Confidential

290
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

 Access the highest-priority VoIP services.

Raisecom#config
Raisecom(config)#interface gigaethernet 1/2/2.1
Raisecom(config-gigaethernet1/2/2.1)#mpls l2vc destination 1.1.4.1 tagged
vc-id 1 tunnel-interface 1 svlan 1
Raisecom(config-gigaethernet1/2/2.1)#mpls l2vpn pw bandwidth hqos weight
5 flow-queue 5

 Access the second-highest-priority IPTV services.

Raisecom#config
Raisecom(config)#interface gigaethernet 1/2/2.2
Raisecom(config-gigaethernet1/2/2.2)#mpls l2vc destination 1.1.4.1 tagged
vc-id 2 tunnel-interface 1 svlan 1
Raisecom(config-gigaethernet1/2/2.2)#mpls l2vpn pw bandwidth hqos weight
3 flow-queue 12

 Access the lowest-priority DATA services.

Raisecom#config
Raisecom(config)#interface gigaethernet 1/2/2.3
Raisecom(config-gigaethernet1/2/2.3)#mpls l2vc destination 1.1.4.1 tagged
vc-id 3 tunnel-interface 1 svlan 1
Raisecom(config-gigaethernet1/2/2.3)#mpls l2vpn pw bandwidth hqos weight
1 flow-queue 21

Step 2 Configure user-level bandwidth guarantee, limit, and weight.

 Configure the H-QoS of User A.

Raisecom#config
Raisecom(config)#interface tunnel 1/2/1
Raisecom(config-tunnel1/2/1)#bandwidth hqos cir 50000 pir 80000 weight 5

 Configure the H-QoS of User B.

Raisecom#config
Raisecom(config)#interface tunnel 1/2/2
Raisecom(config-tunnel1/2/2)#bandwidth hqos cir 30000 pir 50000 weight 3

 Configure the H-QoS of User C.

Raisecom Proprietary and Confidential

291
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Raisecom#config
Raisecom(config)#interface tunnel 1/2/3
Raisecom(config-tunnel1/2/3)#bandwidth hqos cir 30000 pir 50000 weight 1

Step 3 Configure interface-based rate limit.

Raisecom#config
Raisecom(config)#interface gigaethernet 1/1/1
Raisecom(config-gigaethernet1/1/1)#rate-limit egress cir 150000 cbs 100
pir 180000 pbs 200

Checking results
 Use the show mpls l2vpn pw traffic-statistics command to show PW statistics.
 Use the show mpls te traffic-statistics tunnel command to show Tunnel statistics.
 Use the show rate-limit interface command to show whether the interface-based
bandwidth limit configurations are correct.

Raisecom#show rate-limit interface

Interface Direction Cir(kbps) Cbs(kB) Pir(kbps) Pbs(kB)
CirOper(kbps) CbsOper(kB) PirOper(kbps) PbsOper(kB)
-------------------------------------------------------------------------
-------------------------------------------------
gigaethernet1/1/1 egress 150000 100 180000 200 150000
100 150000 200

12.11.5 Examples for configuring MPLS QoS CAR

Networking requirements
As shown in Figure 12-6, User B is connected to the iTN8800 through the iTN201. The
iTN8800 accesses voice, video, and data services of User B through its sub-interface
GE1/2/2.1, GE1/2/2.2, and GE1/2/2.3 (these sub-interfaces are configured with the IP address,
LSP, and so on).
User B has purchased the leased line services with a total bandwidth of 20 Mbit/s. According
to the service requirements, the following rules are formulated:
 Voice service bandwidth: CIR 500 Kbit/s; video service bandwidth: CIR 4.5 Mbit/s; data
service bandwidth: CIR 5 Mbit/s
 The voice service is of the highest priority, followed by the video services, and the data
services.
 The idle bandwidth is shared by the three services. Services which have exceeded PIR
will be dropped.

Raisecom Proprietary and Confidential

292
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Figure 12-6 MPLS QoS CAR networking

Configuration steps
Step 1 Configure the sub-interface to access different user services and configure the bandwidth limit
and priority for the services.
 Configure accessing the highest-priority voice services.

Raisecom#config
Raisecom(config)#interface gigaethernet 1/2/2.1
Raisecom(config-gigaethernet1/2/2.1)#mpls l2vc destination 1.1.4.1 tagged
vc-id 1 tunnel-interface 1 svlan 1
Raisecom(config-gigaethernet1/2/2.1)#mpls l2vpn pw bandwidth car cir 500
pir 10500
Raisecom(config-gigaethernet1/2/2.1)#mpls l2vpn pw diffserv-mode pipe 5

 Configure accessing the second-highest-priority video services.

Raisecom#config
Raisecom(config)#interface gigaethernet 1/2/2.2
Raisecom(config-gigaethernet1/2/2.2)#mpls l2vc destination 1.1.4.1 tagged
vc-id 2 tunnel-interface 1 svlan 1
Raisecom(config-gigaethernet1/2/2.2)#mpls l2vpn pw bandwidth car cir 4500
pir 14500
Raisecom(config-gigaethernet1/2/2.2)#mpls l2vpn pw diffserv-mode pipe 3

 Configure accessing the lowest-priority data services.

Raisecom#config
Raisecom(config)#interface gigaethernet 1/2/2.3
Raisecom(config-gigaethernet1/2/2.3)#mpls l2vc destination 1.1.4.1 tagged
vc-id 3 tunnel-interface 1 svlan 1
Raisecom(config-gigaethernet1/2/2.3)#mpls l2vpn pw bandwidth car cir 5000
pir 15000
Raisecom(config-gigaethernet1/2/2.3)#mpls l2vpn pw diffserv-mode pipe 1

Raisecom Proprietary and Confidential

293
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 12 QoS

Step 2 Configure limit on the total bandwidth of User B, namely, Tunnel bandwidth limit.

Raisecom#config
Raisecom(config)#interface tunnel 1/2/2
Raisecom(config-tunnel1/2/2)#bandwidth car cir 10000 pir 20000

Checking results
 Use the show mpls l2vpn pw traffic-statistics command to show PW statistics.
 Use the show mpls te traffic-statistics tunnel command to show Tunnel statistics.
When sending 10 Mbit/s voice services, 10 Mbit/s video services, and 10 Mbit/s data services
during a test, the user obtained the practical bandwidth, as shown in Table 12-1.

Table 12-1 Bandwidth statistics in the case of MPLS QoS CAR configurations
Service type Voice service Video service Data service Total
Configured 500 kbit/s 4.5 Mbit/s 5 Mbit/s 10 M (PIR
bandwidth CIR is 20
Mbit/s)
Sent bandwidth 10 Mbit/s 10 Mbit/s 10 Mbit/s 30 Mbit/s
Actual bandwidth 10 Mbit/s 5 Mbit/s 5 Mbit/s 20 Mbit/s

The CIR bandwidth (10 Mbit/s in total) of the three services is met first. The amount
of bandwidth of the three services which has exceeded the CIR is 9.5 Mbit/s, 5.5
Mbit/s, and 5 Mbit/s. According to the service priority, 9.5 Mbit/s bandwidth will be
assigned to voice services first, and the left 0.5 Mbit/s will be assigned to the video
services. There is no extra bandwidth for the data services. Therefore, transmitted
traffic is 10 Mbit/s for voice services, 5 Mbit/s for video services, and 5 Mbit/s for data
services.

Raisecom Proprietary and Confidential

294
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

13 OAM

This chapter describes principles and configuration procedures of OAM, as well as related
configuration examples, including following sections:
 Configuring EFM
 Configuring CFM
 Configuring MPLS-TP OAM
 Configuring BFD
 Configuring SLA
 Configuring Y.1564
 Configuring link quality alarm
 Maintenance
 Configuration examples

13.1 Configuring EFM

13.1.1 Preparing for configurations

Scenario
Deploying EFM between directly-connected devices can effectively improve the management
and maintenance capability of Ethernet links and ensure network running smoothly.

Prerequisite
Connect interfaces and configure physical parameters of interfaces. Make the physical layer
Up.

13.1.2 Configuring EFM basic functions

Step Command Description
1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

295
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Step Command Description

2 Raisecom(config)#oam send-period (Optional) configure the OAM PDU delivery
period-number timeout time period and timeout.
By default, the OAM PDU delivery time is 1s (the
parameter is 10, 10 × 100ms = 1s) and the timeout
is 5s.
3 Raisecom(config)#interface Enter Layer 2 or 3 physical interface configuration
gigaethernet interface-number mode.
4 Raisecom(config-port)#oam { active | Configure the working mode of EFM.
passive }
By default, it is passive.
5 Raisecom(config-port)#oam enable Enable EFM OAM of the link.
By default, it is disabled.

13.1.3 Configuring EFM active functions

EFM active functions can be configured when the iTN8800 is in active mode.

(Optional) configuring iTN8800 to initiate EFM remote loopback

 You can discover network faults in time by periodically detecting loopbacks. By

detecting loopbacks in segments, you can locate exact areas where faults occur
and you can troubleshoot these faults.
 When a link is in the loopback status, the iTN8800 returns all packets but OAM
packets received by the link to the peer. At this time, the user data packet cannot
be forwarded properly. Therefore, disable this function immediately when
detection is not required.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter GE interface configuration mode.
gigaethernet interface-number
3 Raisecom(config-port)#oam Enable the interface to initiate remote loopback.
remote-loopback
4 Raisecom(config-port)#oam (Optional) configure the timeout for the interface to initiate
loopback timeout time remote loopback.
By default, it is 3s.
5 Raisecom(config-port)#oam (Optional) configure the retry times for the interface to
loopback retry times initiate remote loopback.
By default, it is 2 times.

Raisecom Proprietary and Confidential

296
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

(Optional) viewing current variable values of peer device

By getting the current variable values of the peer, you can get current link status.
IEEE 802.3 Clause 30 defines and explains supported variables and their denotation
gotten by OAM in details. The variable takes Object as the maximum unit. Each
object contains Package and Attribute. A package contains several attributes.
Attribute is the minimum unit of a variable. When an OAM variable is obtained, object,
package, branch, and leaf description of attributes are defined by Clause 30 to
describe requesting object, and the branch and leaf are followed by variable to
denote object responds variable request. The iTN8800 supports getting OAM
information and interface statistics.
Peer variable cannot be obtained unless EFM connection is established.
Step Command Description
1 Raisecom#show oam peer oam-info [ gigaethernet interface- Show OAM basic
number ] information about the
Raisecom#show oam peer [ gigaethernet interface-number ] peer device.

13.1.4 Configuring EFM passive functions

The passive functions of EFM can be configured regardless of the iTN8800 is in

active or passive mode.

(Optional) configuring iTN8800 to respond to EFM remote loopback

The peer EFM remote loopback will not take effect until the remote loopback
response is configured on the local device.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter GE interface configuration mode.
gigaethernet interface-number
3 Raisecom(config)#oam loopback Configure the interface to ignore/respond to EFM remote
{ ignore | process } loopback sent by the peer device.
By default, the Layer 2 physical interface ignores EFM
remote loopback.

Raisecom Proprietary and Confidential

297
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

13.1.5 Configuring link monitoring and fault indication

(Optional) configuring OAM link monitoring

OAM link monitoring is used to detect and report link errors in different conditions.
When detecting a fault on a link, the iTN8800 provides the peer with the generated
time, window, and threshold, etc. by OAM event notification packets. The peer
receives event notification and reports it to the NView NNM system through SNMP
Trap. Besides, the local device can directly report events to the NView NNM system
through SNMP Trap.
By default, the system sets default value for error generated time, window, and
threshold.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter GE interface configuration mode.
gigaethernet interface-number
3 Raisecom(config-port)#oam Configure the monitor window and threshold for an error
errored-frame window frame event.
framewindow threshold
framethreshold By default, the monitor window is 1s and the threshold is 1
error frame.
4 Raisecom(config-port)#oam Configure the monitor window and threshold for an error
errored-frame-period window frame period event.
frameperiodwindow threshold
frameperiodthreshold By default, the monitor window is 1000ms and the threshold
is 1 error frame.
5 Raisecom(config-port)#oam Configure the monitor window and threshold for an error
errored-frame-seconds window frame seconds event.
framesecswindow threshold
framesecsthreshold By default, the monitor window is 60s and the threshold is
1s.
6 Raisecom(config-port)#oam Configure the monitor window and threshold for an error
errored-symbol-period window symbol event.
symperiodwindow threshold
symperiodthreshold By default, the monitor window is 1s and the threshold is 1
error frame.

(Optional) configuring OAM fault indication

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface gigaethernet Enter GE interface configuration mode.
interface-number

Raisecom Proprietary and Confidential

298
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Step Command Description

3 Raisecom(config-port)#oam notify Enable OAM notification of fault information
{ critical-event | dying-gasp | errored- and OAM link events.
frame | errored-frame-period | errored-
frame-seconds | errored-symbol-period } By default, OAM notification of all links is
enable enabled.
4 Raisecom(config-port)#oam event trap Enable OAM Trap of local OAM link events.
enable
By default, it is disabled.
5 Raisecom(config-port)#oam peer event Enable OAM Trap of peer OAM link events.
trap { enable | disable }
By default, it is disabled.

13.1.6 Configuring extended OAM

Both Layer 2 and Layer 3 interfaces on the iTN8800 support extended OAM. Configuring
OAM on Layer 3 interface does not affect configurations of its sub-interfaces.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interfac Enter physical interface configuration mode.
e interface-type
interface-number
3 Raisecom(config-port)#oam Enable OAM on the interface.
enable
4 Raisecom(config-port)#oam Configure the working mode of OAM.
{ active | passive }
By default, it is passive.
5 Raisecom(config- Enter remote configuration mode.
port)#remote-device
6 Raisecom(config- Configure the host name of the remote device.
remote)#hostname hostname
7 Raisecom(config- Configure the IP address of the remote device.
remote)#ip address ip-
address [ ip-mask ]
[ vlan-id ]
 We recommend that you not use this command together
with zero-configuration, because it may cause the remote
device out of control.
 When the remote device is an IP RAN device, its IP

address should be configured on interface Loopback 1. If

you configure the management VLAN ID, the sub-
interface (the parent interface is enabled with OAM) will
use the IP address of interface Loopback 1, otherwise, it
will not.
 When the remote device is a PTN device, you should

configure its IP address on IP interface 0. If you configure

the management VLAN ID, the VLAN will be associated
with IP interface 0.

Raisecom Proprietary and Confidential

299
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

After entering remote configuration mode, you can show the command list supported
by the remote device by using the list command. Then you can manage the remote
device by using those commands. For example:
 Use the snmp-server community command to configure the network management
for the remote device.
 Use the switch-mode dot1q-vlan native-vlan command to configure VLAN for the
remote device.
 Use the reboot command to reboot the remote device.
 Use the erase command to delete configuration files from the remote device.
There are multiple commands available for you to monitor and manage the remote
device through extended OAM. They are not listed here one by one, and you can use
them as required. Using some commands remotely on the remote device has the
same effect as using these commands locally on the remote device.

13.1.7 Checking configurations

No. Command Description
1 Raisecom#show oam [ gigaethernet interface- Show configurations of OAM basic
number ] functions.
2 Raisecom#show oam event [ gigaethernet Show local OAM link events.
interface-number ] [ critical ]
3 Raisecom#show oam loopback [ gigaethernet Show OAM remote loopback
interface-number ] configurations.
4 Raisecom#show oam notify [ gigaethernet Show OAM notification configurations.
interface-number ]
5 Raisecom#show oam peer event [ gigaethernet Show information about OAM peer events.
interface-number ] [ critical ]
6 Raisecom#show oam peer link-statistic Show peer OAM link statistics.
[ gigaethernet interface-number ]
7 Raisecom#show oam statistics [ gigaethernet Show OAM statistics.
interface-number ]
8 Raisecom#show oam trap [ gigaethernet Show OAM Trap information.
interface-number ]

13.2 Configuring CFM

13.2.1 Preparing for configurations

Scenario
To expand application of Ethernet technologies at a Telecom-grade network, the Ethernet
must ensure the same QoS as the Telecom-grade transport network. CFM solves this problem
by providing overall OAM tools for the Telecom-grade Ethernet.
CFM can provide following OAM functions:

Raisecom Proprietary and Confidential

300
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

 Fault detection (Continuity Check, CC)

 Fault acknowledgement (LoopBack, LB)
 Fault location (LinkTrace, LT)
 Alarm Indication Signal (AIS)
 Ethernet lock signal (Lock, LCK)
 Client Signal Fail (CSF)

Prerequisite
 Connect interfaces and configure physical parameters of the interfaces. Make the
physical layer Up.
 Create a VLAN.
 Add interfaces to the VLAN.

13.2.2 Enabling CFM

 CFM fault detection and CFM fault location functions cannot take effect until the
CFM is enabled.
 To enable CFM on an interface, you need to enable global CFM in global
configuration mode and then enable CFM on the interface.
 When global CFM is disabled, it does not affect enabling/disabling EFM on the
interface.
 Ethernet LM cannot take effect unless CFM is enabled on the ingress interface of
the service packet and MEP-related interfaces.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ethernet cfm enable Enable global CFM.
By default, it is disabled.
3 Raisecom(config)#interface gigaethernet Enter GE interface configuration mode.
interface-number

4 Raisecom(config-port)#ethernet cfm enable Enable CFM on the interface.

By default, it is disabled.

13.2.3 Configuring CFM basic functions

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ethernet cfm mode Configure the CFM working mode.
{ master | slave } By default, it is in slave mode.

Raisecom Proprietary and Confidential

301
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Step Command Description

3 Raisecom(config)#ethernet cfm domain Create a MD.
[ md-name domain-name ] level md-  If a MD name is assigned by the md-name
level parameter, it indicates that the MD is in 802.1ag
style. And all MAs and CCMs in the MD are in
802.1ag style.
 If a MD name is not assigned, the MD is in Y.1731

style and all MAs and CCMs in the MD are in

Y.1731 style.
 Do not support configuring Y.1731 and 802.1ag

CFM concurrently.
 If the MD name is specified, it must be globally

unique.
 Levels of different MDs must be different.

4 Raisecom(config)#service csi-id Create a service instance and enter service instance

level md-level configuration mode.
5 Raisecom(config-service)#service Configure the VLAN related to the MA.
vlan-list vlan-list [ primary vlan-
id ]

6 Raisecom(config-service)#service mep Configure the MEP based on service instance.

[ up | down ] mpid mep-id Before configuring MEP, relating the service
[ interface-type interface-number ] instance to the VLAN.
7 Raisecom(config-service)#service Add static remote MEP of the service instance
remote-mep mep-list interface-type manually.
interface-number

Raisecom(config-service)#service
remote-mep mep-list remote-mac mac- 802.1ag down MEP needs to manually add
address [ interface-type interface- the remote MEP and specify the interface. It
number ] fails to find the remote MEP automatically.
8 Raisecom(config-service)#service (Optional) configure remote MEP learning. Add
remote-mep learning active dynamically learned remote MEPs to the static
remote MEP list.
9 Raisecom(config-service)#service Enable alarm inhibition.
suppress-alarms enable mep { mep-
list | all } By default, it is enabled.

13.2.4 Configuring fault detection

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ethernet cfm remote (Optional) configure the aging time of remote
mep age-time minutes MEPs.

Raisecom Proprietary and Confidential

302
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Step Command Description

3 Raisecom(config)#ethernet cfm errors (Optional) configure the archive-hold time of error
archive-hold-time minutes CCMs.
By default, it is 100min.
4 Raisecom(config)#service csi-id level Enter service instance configuration mode.
md-level

5 Raisecom(config-service)#service cc (Optional) configure the delivery period of CCMs.

interval { 3ms | 10ms | 100ms | 1 |
10 | 60 | 600 }

6 Raisecom(config-service)#service cc Enable MEP to send CCMs.

enable mep { mep-list | all }

7 Raisecom(config-service)#service (Optional) enable checking remote MEPs.

remote-mep cc-check enable By default, it is disabled.
8 Raisecom(config-service)#service (Optional) configure the CVLAN of the MA.
cvlan vlan-id

9 Raisecom(config-service)#service (Optional) configure the priority of CFM OAM

priority priority packets.
By default, it is 7.

13.2.5 Configuring fault acknowledgement

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#service csi-id level md- Enter service instance configuration
level mode.
3 Raisecom(config-service)#ping mac-address Perform Layer 2 Ping for acknowledging
[ count count-number ] [ size size ] faults.
[ source mep-id ] [ timeout time ]
[ padding { null | null-crc | prbs | prbs- By default, 5 LBMs are sent. The TLV
crc } ] length of a packet is 64. The iTN8800
automatically looks for an available
Raisecom(config-service)#ping mep mep-id
source MEP.
[ ttl ttl ] [ count count-number ] [ size
size ] [ source mep-id ] [ timeout time ]
[ padding { null | null-crc | prbs | prbs-
crc } ]
To perform Ping MEP operation,
802.1ag down MEP needs to be
configured with the static remote
MAC address.
4 Raisecom(config-service)#ping ethernet Perform Layer 2 multicast Ping for
multicast [ size size ] [ timeout time ] acknowledging faults.
[ padding { null | null-crc | prbs | prbs-
crc } ]

Raisecom Proprietary and Confidential

303
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

 Before executing this command, ensure that global CFM is enabled. Otherwise,
the Ping operation fails.
 If there is no MEP in a service instance, Ping operation will fail because of failing
to find source MEP.
 Ping operation will fail if the specified source MEP is invalid. For example, the
specified source MEP does not exist or CFM is disabled on the interface where
the specified source MEP is.
 Ping operation will fail if the Ping operation is performed based on specified
destination MEP ID and the MAC address of destination is not found based on
MEP ID.
 Ping operation will fail if other users are using the specified source MEP to
perform Ping operation.
 If the service instance associates with the emulated Ethernet PW, when LB is
performed, you need to enable global CFM and Ethernet CFM on the AC-side
interface.

13.2.6 Configuring fault location

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#service csi- Enter service instance configuration mode.
id level md-level

3 Raisecom(config- Perform Layer 2 Traceroute for locating faults.

service)#traceroute mac-
address [ ttl ttl ] [ source By default, the TLV length of a packet is 64. The iTN8800
mep-id ] automatically looks for an available source MEP.
Raisecom(config-
service)#traceroute mep mep-id
[ ttl ttl ] [ source mep-id ]
To perform Traceroute MEP operation, 802.1ag down
[ interface-mode ] [ timeout
MEP needs to be configured with the static remote
time ]
MAC address.
Raisecom(config- Perform MPLS-TP Traceroute for locating faults.
service)#traceroute mip icc
icc-code code-id [ ttl ttl ]
[ interface-num interface-
number ] [ timeout time ]
Raisecom(config-service)#exit

4 Raisecom(config)#ethernet cfm (Optional) enable LinkTrace cache.

traceroute cache enable When LinkTrace cache is enabled, you can use the show
ethernet cfm traceroute cache command to learn the routes
discovered through the cache storage protocol. When
LinkTrace cache is disabled, the result will be automatically
erased by the traceroute command.
By default, LinkTrace cache is disabled.

Raisecom Proprietary and Confidential

304
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Step Command Description

5 Raisecom(config)#ethernet cfm (Optional) configure the hold time of data in the LinkTrace
traceroute cache { hold-time cache and LinkTrace cache size.
minute | size size }
By default, the hold time is 100min and the LinkTrace cache
size is 100.

 Before executing this command, ensure that global CFM is enabled. Otherwise,
the Traceroute operation fails.
 If there is no MEP in a service instance, Traceroute operation will fail because of
failing to find source MEP.
 Traceroute operation will fail if the specified source MEP is invalid. For example,
the specified source MEP does not exist or CFM is disabled on the interface
where the specified source MEP is.
 Traceroute operation will fail if the Ping operation is performed based on specified
destination MEP ID and the MAC address of destination is not found based on
MEP ID.
 If the CC feature is invalid, you can ensure Layer 2 Traceroute operation works
normally by configuring static RMEP and specifying MAC address.
 Traceroute operation will fail if other users are using the specified source MEP to
perform Traceroute operation.

13.2.7 Configuring AIS

Configuring AIS on server-layer devices

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ethernet cfm domain Create a MD.
[ md-name domain-name ] level md-
level

3 Raisecom(config)#service csi-id Enter service instance configuration mode.

level md-level

4 Raisecom(config-service)#service ais Configure the level of the MD to which AIS is sent.

level md-level

The MD level must be higher than the service

instance level.
5 Raisecom(config-service)#service ais (Optional) configure the AIS delivery period.
period { 1 | 60 }
By default, the AIS delivery period is 1s.
6 Raisecom(config-service)#service ais Enable AIS delivery.
enable
By default, AIS delivery is disabled.

Raisecom Proprietary and Confidential

305
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Configuring AIS on client-layer devices

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ethernet cfm domain [ md- Create a MD.
name domain-name ] level md-level

3 Raisecom(config)#service csi-id level md- Enter service instance configuration mode.

level

4 Raisecom(config-service)#service suppress- Enable alarm inhibition.

alarms enable mep { mep-list | all } By default, alarm inhibition is enabled.

13.2.8 Configuring LCK

Configuring LCK on server-layer devices

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ethernet cfm Create a MD.
domain [ md-name domain-name ]
level md-level

3 Raisecom(config)#service csi-id Enter service instance configuration mode.

level md-level

4 Raisecom(config-service)#service Configure the level for sending the LCK packet. The level
lck level md-level [ vlan vlan- must be higher than the service instance level.
id ]
By default, the level of the MIP is used, which is higher
than the MEP level, to send the LCK packet.
5 Raisecom(config-service)#s (Optional) configure the LCK packet delivery period.
service lck period { 1 | 60 }
By default, it is 1s.
6 Raisecom(config-service)#service Configure the MEP to send the LCK packet.
lck start mep { mep-list | all }
By default, the MEP does not send the LCK packet.

Configuring LCK on client-layer devices

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ethernet cfm domain [ md-name Create a MD.
domain-name ] level md-level

3 Raisecom(config)#service csi-id level md-level Enter service instance configuration

mode.

Raisecom Proprietary and Confidential

306
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Step Command Description

4 Raisecom(config-service)#service suppress- Enable alarm inhibition.
alarms enable mep { mep-list | all } By default, alarm inhibition is enabled.

13.2.9 Configuring CSF

Configuring LCK on server-layer devices

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ethernet cfm domain Create a MD.
[ md-name domain-name ] level md-
level

3 Raisecom(config)#service csi-id level Enter service instance configuration mode.

md-level

4 Raisecom(config-service)#service csf (Optional) configure the CSF packet delivery

period { 1 | 60 } period.
By default, the CSF packet delivery period is 1s.
5 Raisecom(config-service)#service csf Enable the MEP to send the LCK packet.
enable mpid mep-id
6 Raisecom(config-service)#service csf (Optional) enable CSF Trap.
trap enable

13.2.10 Checking configurations

No. Command Description
1 Raisecom#show cfm csf Show CSF information.
2 Raisecom#show ethernet cfm Show CFM global configurations.
3 Raisecom#show ethernet cfm ais [ level md- Show AIS information.
level ] [ source ]

802.1ag MDs do not support AIS.

4 Raisecom#show ethernet cfm domain [ level md- Show MD configurations.
level ]
5 Raisecom#show ethernet cfm errors [ level md- Show error CCM information.
level ]
6 Raisecom#show ethernet cfm lck [ level md- Show LCK information.
level ] [ source ]

802.1ag MDs do not support LCK.

Raisecom Proprietary and Confidential

307
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

No. Command Description

7 Raisecom#show ethernet cfm local-mp Show local MEP configurations.
[ interface interface-type interface-number ]
Raisecom#show ethernet cfm local-mp [ level
md-level ]
8 Raisecom#show ethernet cfm remote-mep [ level Show remote MEP configurations.
md-level [ service csi-id [ mpid mep-id ] ] ]
9 Raisecom#show ethernet cfm remote-mep static Show remote static MEP
[ level md-level ] configurations.
10 Raisecom#show ethernet cfm traceroute-cache Show information about routes in the
LinkTrace cache.

13.3 Configuring MPLS-TP OAM

13.3.1 Preparing for configurations

Scenario
To extend the application of MPLS-TP technology in telecom network, the MPLS-TP network
needs to achieve the same service level as the telecom transport network does. Connectivity
Fault Management (CFM) helps the MPLS-TP network to resolve the problem by providing
complete OAM tools.
CFM can provide the following OAM functions for the MPLS-TP network:
 Fault detection (Continuity Check, CC)
 Fault acknowledgement (LoopBack, LB)
 Fault location (LinkTrace, LT)
 Alarm Indication Signal (AIS)
 Client Signal Fail (CSF)
 Lock (LCK)
 Packet Delay and Packet Delay Variation Measurements (DM)
 Frame Loss Measurements (LM)
The principle of MPLS-TP OAM is similar to the one of Ethernet-based OAM. Only the
carrying modes of related packets are different.
To ensure that users can get quality network services, the carrier and users sign a Service
Level Agreement (SLA). To effectively fulfill the SLA, the carrier needs to deploy the SLA
feature on the device to measure the network performance and takes the measurement result
as the basis for ensuring the network performance.
SLA selects 2 detection points, configures, and schedules the SLA operation on one detection
point to detect the network performance between the 2 detection points.
The SLA feature counts the round-trip packet loss ratio, round-trip/unidirectional (SD/DS)
delay, jitter, jitter variance, and jitter distribution and reports them to the upper monitoring

Raisecom Proprietary and Confidential

308
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

software (such as the NView NNM system). Then the upper monitoring software analyses the
network performance to get a data meeting users' requirements.

Prerequisite
 Connect the interface and configure physical parameters of the interface. Make the
physical layer Up.
 Configure MPLS basic functions.
 Before configuring SLA, deploy CFM between devices that need to detect the network
performance.

13.3.2 Enabling MPLS-TP CFM

By default, the device is enabled with CFM.

13.3.3 Configuring MPLS-TP CFM

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls-tp cfm domain level Create a MPLS-TP MD.
level
3 Raisecom(config)#mpls-tp service ma-name Create a service instance and enter service
level ma-level instance configuration mode.
4 Raisecom(config-service)#service vc-id Associate the service instance to the VC ID.
vc-id destination ip-address [ ttl ttl ]
5 Raisecom(config-service)#service lsp Associate the service instance to the specified
{ bidirection lsp-name | ingress lsp-in ingress, egress, and bidirectional LSP.
egress lsp-out }
6 Raisecom(config-service)#service lsp Create a service instance that is based on LSP
transit bidirection lsp-name lsr-id lsr- subnet connection.
id ttl ttl
Raisecom(config-service)#service lsp
transit forward lsp-in backward lsp-out
ttl ttl
7 Raisecom(config-service)#service pw Associate the service instance to the subnet
transit forward vc-id vc-id destination connection PW.
ip-address backward vc-id vc-id
destination ip-address
8 Raisecom(config-service)#service section Associate the service instance to the section
{ dest-mac mac-address | interface-type and configure the section-layer CC destination
interface-number } MAC address.

The iTN8800-RXG8 does not support

section-layer OAM for now.
9 Raisecom(config-service)#service Enable MEP fault inhibition.
suppress-alarms enable mep { all | mep-
list }

Raisecom Proprietary and Confidential

309
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Step Command Description

10 Raisecom(config-service)#service priority Configure the priority of the CFM packet.
priority
11 Raisecom(config-service)#service remote- Create a static remote MEP.
mep mep-list [ interface-type interface-
number ]
12 Raisecom(config-service)#service lm- Enable LM response.
response enable

Before enabling CFM packet delivery, associate the service instance with the static
L2VC.

13.3.4 Configuring MPLS-TP fault detection

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls-tp cfm remote mep (Optional) configure the aging time of remote
age-time minutes MEPs.
By default, it is 100min.
3 Raisecom(config)#mpls-tp cfm errors (Optional) configure the archive-hold time of
archive-hold-time minutes error CCMs.
By default, it is 100min.
When the new archive-hold time is configured,
the system will check data in the database and
will clear data of which the archive-hold time
expires.
4 Raisecom(config)#mpls-tp service ma-name Enter service instance configuration mode.
level ma-level
5 Raisecom(config-service)#service cc (Optional) configure the interval for sending
interval { 3ms | 10ms | 100ms | 1 | 10 | service instance CC packets.
60 | 600 }
By default, it is 1s.
6 Raisecom(config-service)#service remote- Configure remote MEP learning, after which
mep learning active the dynamically learned MEPs will be added
to the static remote MEP list.
7 Raisecom(config-service)#service mep [ up Configure a MEP based on server instance.
| down ] mpid mep-id
8 Raisecom(config-service)#service cc Enable MEP to send CC packets.
enable mep { mep-list | all }
By default, the MEP does not send CC
packets.

Raisecom Proprietary and Confidential

310
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

13.3.5 Configuring MPLS-TP fault acknowledgement

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls-tp service ma-name Enter service instance configuration mode.
level ma-level
3 Raisecom(config-service)#ping { ingress | Perform MPLS-TP Ping for
egress } ttl ttl [ count count-number ] acknowledging faults.
[ size size ] [ source mep-id ] [ timeout
time ] [ padding { null | null-crc | prbs | By default, 5 LBMs are sent. The TLV
prbs-crc } ] length of a packet is configured to 64. The
Raisecom(config-service)#ping mep mep-id
iTN8800 automatically searches for an
[ ttl ttl ] [ count count-number ] [ size
available source MEP.
size ] [ source mep-id ] [ timeout time ]
[ padding { null | null-crc | prbs | prbs-
crc } ]
Raisecom(config-service)#ping mip icc icc-
code code-id [ interface-num interface-
number ] ttl ttl [ count count-number ]
[ size size ] [ source mep-id ] [ timeout
time ] [ padding { null | null-crc | prbs |
prbs-crc } ]

 If no MEP is configured for the service instance, the Ping operation will fail
because no source MEP is found.
 The Ping operation will fail if the specified source MEP is invalid. For example, the
specified source MEP does not exist or CFM is disabled on the interface where
the specified source MEP is.
 The Ping operation will fail if another user is using the specified source MEP to
initiate the Ping operation.

13.3.6 Configuring MPLS-TP fault location

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls-tp service ma-name Enter service instance configuration
level ma-level mode.
3 Raisecom(config-service)#traceroute ttl ttl Perform MPLS-TP Traceroute for
[ interface-mode ] [ timeout time ] locating faults.
Raisecom(config-service)#traceroute mep mep-
id [ ttl ttl ] [ source mep-id ] [ interface-
mode ] [ timeout time ]
Raisecom(config-service)#traceroute mip icc
icc-code code-id [ ttl ttl ] [ interface-num
interface-number ] [ timeout time ]

Raisecom Proprietary and Confidential

311
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

 If no MEP is configured for the service instance, the Traceroute operation will fail
because no source MEP is found.
 The Traceroute operation will fail if the specified source MEP is invalid. For
example, the specified source MEP does not exist or CFM is disabled on the
interface where the specified source MEP is.
 The Traceroute operation will fail if another user is using the specified source MEP
to initiate the Traceroute operation.

13.3.7 Configuring MPLS-TP AIS

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls-tp service ma- Enter service instance configuration mode.
name level ma-level
3 Raisecom(config-service)#service ais Configure the level of the client-layer MD to
{ level md-level [ vlan vlan-id ] | which the AIS is sent and the AIS delivery
period { 1 | 60 } } period.
 Specify the VLAN only when you configure the
AIS Level in PW service instance.
 When the service instance is configured with

PW OAM and the specified level is configured

with Ethernet OAM, you need to specify the
VLAN when executing this command. In
addition, the specified VLAN is the primary
VLAN of Ethernet OAM.
By default, the AIS delivery period is 1s.
4 Raisecom(config-service)#service ais Enable AIS delivery.
enable
By default, AIS delivery is disabled.
5 Raisecom(config-service)#service Enable alarm inhibition.
suppress-alarms enable mep { mep-list | By default, alarm inhibition is enabled.
all }

13.3.8 Configuring MPLS-TP CSF

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls-tp service ma- Enter service instance configuration mode.
name level ma-level
3 Raisecom(config-service)#service csf Enable CSF packet delivery. It is available for
enable mpid mep-id PW OAM only.
By default, CSF packet delivery is disabled.

Raisecom Proprietary and Confidential

312
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Step Command Description

4 Raisecom(config-service)#service csf Configure the CSF packet delivery period. It is
period { 1 | 60 } available for PW OAM only.
By default, the CSF packet delivery period is
configured to 1s.
5 Raisecom(config-service)#service csf Enable CSF Trap. It is available for PW OAM
trap enable only.
By default, CSF Trap is disabled.

13.3.9 Configuring MPLS-TP LCK

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls-tp service ma- Enter service instance configuration mode.
name level ma-level
3 Raisecom(config-service)#service lck Configure the level for sending LCK packets.
level md-level [ vlan vlan-id ]
By default, use the MIP level which is higher
than the MEP level to send LCK packets. The
period is configured to 1s.
4 Raisecom(config-service)#service lck Configure the LCK packet delivery period.
period { 1 | 60 }
5 Raisecom(config-service)#service lck Enable MEP to send LCK packets.
start mep { mep-list | all }
6 Raisecom(config-service)#service Enable alarm inhibition.
suppress-alarms enable mep { mep-list | By default, alarm inhibition is enabled.
all }

13.3.10 Configuring MPLS-TP SLA operation

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#sla oper-num mpls- Configure the SLA MPLS-Y1731-Jitter
y1731 [latency | pkt-loss] level md- operation.
level { l2vc l2vc-id peer-address ip-
address | lsp-ingress lspingress-name
lsp-egress lspegress-name | section
interface-type interface-number }
[ interval period ] [ packets packets-
num ] [ tc tc ]

Raisecom Proprietary and Confidential

313
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

13.3.11 Configuring SLA scheduling and enabling operation

scheduling
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#sla schedule oper-num Configure the SLA scheduling and enable the
[ life forever | life life-time] SLA scheduling operation. The scheduling is not
[ period period ] enabled by default.

13.3.12 Configuring fault relay based on MPLS-TP OAM and BFD

alarm linkage
By configuring alarm linkage between MPLS-TP OAM and BFD, the fault at the AC side can
be passed to the PW side and vice versa, thus triggering protection switching. In other words,
it switches the traffic on the master link to the slave link. If AC-side devices do not support
MPLS-TP OAM and BFD, the fault at the PW end can be passed to the CE under the
condition that the interface on the PE is Down, thus triggering the switchover.
MS-PW fault linkage is also supported in the PTN-IPRAN networking. The fault at the PTN
end can be passed to the IPRAN end and vice versa, thus triggering protection switching.
By default, the fault relay based on MPLS-TP OAM and BFD alarm linkage is enabled. Refer
to the following configuration steps if you need to implement other fault relay functions.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter Layer 3 physical interface
interface-number configuration mode.
3 Raisecom(config-port)#mode l2 Configure the VPN mode of the Layer 3
interface to L2VPN.
By default, it is L3VPN.
4 Raisecom(config-port)#l2vpn fault-action if- (Optional) when the MPLS-TP OAM
down and BFD are not supported at AC end,
you can use this command to configure
the fault relay when the interface is
Down.
The configuration takes effect on the
physical interface only.
Raisecom(config-port)#exit Exit interface configuration mode.
5 Raisecom(config)#mpls switch-l2vc ip-address Configure fault relay based on MPLS-TP
vc-id fault-relay OAM and BFD alarm linkage in the MS-
PW.

Raisecom Proprietary and Confidential

314
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

13.3.13 Checking configurations

No. Command Description
1 Raisecom(config-service)#show cfm mip Show CFM global configurations.
2 Raisecom(config)#show mpls-tp cfm Show MPLS-TP CFM global
configurations.
3 Raisecom(config)#show mpls-tp cfm ais [ level Show MPLS-TP AIS information.
md-level ] [ source ]
4 Raisecom(config)#show mpls-tp cfm domain Show MD configurations.
[ level md-level ]
5 Raisecom(config)#show mpls-tp cfm errors Show error CCMs.
[ level md-level ]
6 Raisecom(config)#show mpls-tp cfm local-mp Show local MEP configurations.
[ level md-level ]
7 Raisecom(config)#show mpls-tp cfm remote-mep Show remote MEP configurations.
[ level md-level [ service csi-id [ mpid mep-
id ] ] ]
8 Raisecom(config)#show mpls-tp cfm remote-mep Show configurations of the static remote
static [ level md-level ] MEP.
9 Raisecom(config)#show mpls-tp cfm suppress- Show alarm inhibition configurations.
alarms [ level md-level ]
10 Raisecom(config)#show mpls-tp cfm lck [ level Show MPLS-TP LCK configurations.
md-level ] [ source ]

13.4 Configuring BFD

13.4.1 Preparing for configurations

Scenario
To reduce effect of faults on the device and improve network availability, the iTN8800 needs
to detect communication faults with adjacent devices. Therefore, it can take actions
immediately to ensure service being transmitted properly.
BFD is a one-way detection. Therefore, both the local device and the peer device should be
enabled with BFD. Otherwise, detection will fail.

Prerequisite
The DUT is configured with an IP address and routes between all devices are reachable.

13.4.2 Configuring BFD session binding

Step 2 to Step 9 are for creating BFD session detection based on all types of links, you can
perform them as required.

Raisecom Proprietary and Confidential

315
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Step Command Description

1 Raisecom#config Enter global configuration mode.
Raisecom(config)#bfd session-id bind peer-ip  Create BFD session detection IP path
2
ip-address [ source-ip ip-address ] and enter BFD session mode.
 Support configuring the source IP

address.
3 Raisecom(config)#bfd session-id bind peer-ip Create BFD session detection, bind a
default-ip interface interface-type Layer 2 physical interface or Layer 2
interface-number LAG interface, and enter BFD session
mode.
4 Raisecom(config)#bfd session-id bind peer-ip Create static BFD session detection, bind
ip-address interface interface-type Layer 3 physical interface, sub-interface,
interface-number VLAN interface or Layer 3 LAG
interface, and enter BFD session mode.
5 Raisecom(config)#bfd session-id bind peer-ip Create BFD session detection VRF, and
ip-address vrf-name vrf-name enter BFD session mode.
6 Raisecom(config)#bfd session-id bind ldp-lsp Create BFD session detection LDP LSP
peer-ip ip-address ip-mask link, and enter BDF session mode.
7 Raisecom(config)#bfd session-id bind mpls Create BFD session detection CR-LSP
interface tunnel tunnel-if cr-lsp and enter BFD session mode.
Raisecom(config)#bfd session-id bind peer-ip Configure single-hop IP detection.
ip-address interface interface-type
interface-number Use together with BFD CR-LSP.
Otherwise, detection will fail.

when the peer device is configured

with BDD. The BFD CR-LSP will
point to the local PEER IP address.
The peer IP address will point to the
local CR-LSP.
8 Raisecom(config)#bfd session-id bind mpls Create BFD session detection Tunnel and
interface tunnel tunnel-if enter BFD session mode.
9 Raisecom(config)#bfd session-id bind pw vc- Create BFD session detection PW and
id peer-ip [ pw-ttl ttl ] [ type-4 ] enter BFD session mode.
10 Raisecom(config)#bfd trap enable (Optional) enable BFD Trap.
By default, it is disabled.

13.4.3 Configuring BFD session parameters

Step Command Description
1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

316
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Step Command Description

2 Raisecom(config)#bfd Enter BFD session mode.
session-id

You cannot use this command to enter BFD session mode

unless you create the BFD and bind the related path.
3 Raisecom(config-bfd- Configure descriptions of the BFD session.
session)#description
description
4 Raisecom(config-bfd- Configure the local identifier of the BFD session.
session)#local
discriminator value
By default, the local identifier is displayed as 0, which indicates
that no local identifier is configured.

It is automatically generated by the system if not

configured.
5 Raisecom(config-bfd- Configure the minimum delivery interval of the BFD session.
session)#min send-
interval interval
By default, it is 10ms.
6 Raisecom(config-bfd- Configure the minimum receiving interval of the BFD session.
session)#min receive-
interval interval
By default, it is 10ms.
7 Raisecom(config-bfd- Configure the local detection times of the BFD session.
session)#detect-
multiplier multiplier
By default, it is 3 times.
8 Raisecom(config-bfd- Configure the remote identifier of the BFD session.
session)#remote
discriminator value By default, the remote identifier is displayed as 0, which indicates
that no remote identifier is configured.

It is automatically generated by the system if not

configured.
9 Raisecom(config-bfd- Enable BFD session.
session)#session enable
By default, it is disabled.
10 Raisecom(config-bfd- Configure the WTR.
session)#wtr wtr

BFD session is unidirectional. When adopting WTR, you

should configure both ends of the link with the same WTR.
Otherwise, if the session status at one end changes, the
session status at the other end will not be the same.

Raisecom Proprietary and Confidential

317
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

13.4.4 Checking configurations

No. Command Description
1 Raisecom#show bfd Show BFD global configurations.
2 Raisecom#show bfd session-id config Show configurations about the specified BFD
session.
3 Raisecom#show bfd session-id state Show status about the specified BFD session.
4 Raisecom#show bfd session-id statistics Show statistics about the specified BFD session.

13.5 Configuring SLA

13.5.1 Preparing for configurations

Scenario
To provide users with qualified network services, the carrier signs a SLA with users. To carry
out SLA effectively, the ISP needs to deploy SLA feature on devices to measure the network
performance, taking the measured results as an evidence for ensuring the network
performance.
By selecting two detection points (source and destination iTN8800 devices), SLA configures
and schedules SLA operations on a detection point. Therefore, network performance between
these 2 detection points can be detected.
SLA takes statistics on round-trip packet loss ratio, round-trip/unidirectional (SD/DS) delay,
jitter, throughput, and LM packet loss ratio test. In addition, it reports these data to the upper
monitoring software (such as the NView NNM system) to help analyze network performance
for getting an expected result.

When configuring SLA on the iTN8800, note the following matters:

 Up to 16 operations can be configured and scheduled concurrently.
 Before scheduling a SLA operation, establish the CFM environment.
 Do not modify the scheduling information or re-schedule the SLA operation if the
current scheduling does not stop.
 Up to 20 detections are available for one test and up to 5 pieces of statistics
records are shown.

Prerequisite
 When you configure Layer 2 tests, deploy CFM between local and remote devices that
need to be detected. Layer 2 Ping operation succeeds between local and remote devices.
 When you configure Layer 3 tests (icmp-echo and icmp-jitter), Layer 3 Ping operation
succeeds between local and remote devices.

Raisecom Proprietary and Confidential

318
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

13.5.2 Configuring Y.1731-based test

When conducting delay test based on Ethernet, LSP, and PW, you can conduct delay
compensation according to the interface rate and packet length, obtaining a delay/jitter value
close to the actual value. This function can be user-defined.

Configuring SLA test

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#sla oper-num icmp latency [ vrf Create the Layer 3 SLA delay
instance-name ] dest-ipaddr ip-address [ dscp dscp- test.
value ] [ interval period ] [ packets packets-num ]
3 Raisecom(config)#sla oper-num y1731 latency remote- Configure the Y1731-echo delay
mep mep-id level level svlan vlan-id [ cvlan cvlan- test based on destination MEP ID.
id ] [ cos cos-value ] [ interval interval-num ]
[ packets packet-num ] [ dm ]
4 Raisecom(config)#sla oper-num y1731 latency remote- Configure the Y1731-echo delay
mac mac-address level level svlan vlan-id [ cvlan test based on destination MAC
cvlan-id ] [ cos cos-value ] [ interval interval- address.
num ] [ packets packet-num ] [ dm ]
5 Raisecom(config)#sla oper-num y1731 pkt-loss Configure the Y1731-echo packet
remote-mep mep-id level level svlan vlan-id [ cvlan loss ratio test based on destination
cvlan-id ] [ cos cos-value ] [ interval interval- MEP ID.
num ] [ packets packet-num ]

When you perform packet

loss ratio test, we
recommend specifying the
MAC address of the remote
MEP, when you use the
service remote-mep
command to configure it.
6 Raisecom(config)#sla oper-num y1731 pkt-loss Configure the Y1731-echo packet
remote-mac mac-address level level svlan vlan-id loss ratio test based on destination
[ cvlan cvlan-id ] [ cos cos-value ] [ interval MAC address.
interval-num ] [ packets packet-num ]
7 Raisecom(config)#sla oper-num mpls-y1731 latency Configure the MPLS-Y1731 PW
level level vcid vc-id peer-address ip-address delay test.
[ interval period ] [ packets packets-num ] [ tc
tc ] [ size frame-size ]
Raisecom(config)#sla oper-num mpls-y1731 latency Configure the MPLS-Y1731 LSP
level level lsp-ingress lspingress-name lsp-egress delay test.
lspegress-name [ interval period ] [ packets
packets-num ] [ tc tc ] [ size frame-size ]
sla oper-num mpls-y1731 latency level level section Configure the MPLS-Y1731
{ interface-type interface-number | port-channel Section delay test.
port-channel } [ interval period ] [ packets
packets-num ] [ tc tc ] [ size frame-size ]

Raisecom Proprietary and Confidential

319
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Step Command Description

8 Raisecom(config)#sla oper-num mpls-y1731 pkt-loss Configure the MPLS-Y1731 PW
level level vcid vc-id peer-address ip-address packet loss ratio test.
[ interval period ] [ packets packets-num ] [ tc
tc ]
Raisecom(config)#sla oper-num mpls-y1731 pkt-loss Configure the MPLS-Y1731 LSP
level level lsp-ingress lspingress-name lsp-egress packet loss ratio test.
lspegress-name [ interval period ] [ packets
packets-num ] [ tc tc ]
Raisecom(config)#sla oper-num mpls-y1731 pkt-loss Configure the MPLS-Y1731
level level section { interface-type interface- Section packet loss ratio test.
number | port-channel port-channel } [ interval
period ] [ packets packets-num ] [ tc tc ]
9 Raisecom(config)#sla oper-num mpls-y1731 pkt-loss Configure the signal degradation
level level vcid vc-id peer-address ip-address [ tc test on the PW layer of MPLS-
tc ] [ sd ] Y1731.
Raisecom(config)#sla oper-num mpls-y1731 pkt-loss Configure the signal degradation
level level lsp-ingress lspingress-name lsp-egress test on the LSP layer of MPLS-
lspegress-name [ tc tc ] [ sd ] Y1731.
Raisecom(config)#sla oper-num mpls-y1731 pkt-loss Configure the signal degradation
level level section { interface-type test on the section layer of MPLS-
interface-number | port-channel port-channel } Y1731.
[ tc tc ] [ sd ]
10 Raisecom(config)#sla oper-num mpls-y1731-ethpw Configure the MPLS-Y1731
latency level level vcid vc-id peer address ip- emulation Ethernet delay test.
address [ cos cos ] [ interval period ] [ packets
packets-num ] [ size frame-size ]
Raisecom(config)#sla oper-num mpls-y1731-ethpw pkt- Configure the MPLS-Y1731
loss level level vcid vc-id peer address ip-address emulation Ethernet packet loss
[ cos cos ] [ interval period ] [ packets test.
packets-num ] [ size frame-size ]
11 Raisecom(config)#sla private-tlv enable Enable the function of the SLA
test packet to encapsulate private
TLV.

 After configuring one operation (differed by operation ID), you cannot modify or
configure it again. You need to delete the operation in advance if you need to
configure it again.
 SLA supports scheduling up to 16 operations at one time. Before you stop
scheduling the same operation, you cannot modify scheduling information or re-
schedule the operation. If you need to reschedule the operation, you need to finish
the scheduling (reach scheduling life time or stop scheduling) before performing
the next scheduling.
 When configuring LSP-based SLA operation, note the name of lsp-ingress (LSP
Ingress node) is the one of the LSP Ingress node for creating the LSP and the
name of the LSP Egress node is the one of the LSP Egress node for creating the
LSP.

Raisecom Proprietary and Confidential

320
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Configuring parameters of packet loss test

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#sla mpls-y1731-pkt- Enable the MPLS-Y1731 packet loss operation
loss count-all enable packet based on priority statistics.

13.5.3 Configuring RFC2544 test

The RFC2544-based test is generally used for testing the network performance before
activating services or for testing services in the case of network interruption after the services
are activated.

Step Command Description

1 Raisecom#config Enter global
configuration
mode.
2 Raisecom(config)#sla pkt-type { eth dest-mac mac-address Configure the
[ cvlan vlan-id ] [ svlan vlan-id ] [ cos cos ] | ipv4 dest-ip type of the SLA
ip-address [ source-ip ip-address ] [ dest-udp-port port-id ] test packets.
[ source-udp-port port-id ] [ tc tc ] [ ttl ttl ] }
3 Raisecom(config)#sla oper-num rfc2544 latency interface Configure
{ interface-type interface-number | port-channel port-channel } RFC2544 delay
[ eth dest-mac mac-address ] [ cos cos ] [ cvlan vlan-id ] test.
[ svlan vlan-id ] [ pkt-size pkt-size ]
Raisecom(config)#sla oper-num rfc2544 latency interface
interface-type interface-number ipv4 dest-ip ip-address
[ source-ip ip-address ] [ dest-udp-port port-id ] [ source-
udp-port port-id ] [ tc tc ] [ ttl ttl ] [ pkt-size pkt-size ]
Raisecom(config)#sla oper-num rfc2544 latency interface
interface-type interface-number [ pkt-size pkt-size ]
4 Raisecom(config)#sla oper-num rfc2544 pkt-loss interface Configure
{ interface-type interface-number | port-channel port-channel } RFC2544 packet
[ eth dest-mac mac-address ] [ cvlan vlan-id ] [ svlan vlan- loss ratio test.
id ] [ pkt-size pkt-size ] [ rate rate ] [ cos cos ]
Raisecom(config)#sla oper-num rfc2544 pkt-loss interface
{ interface-type interface-number | port-channel port-channel }
{ ipv4 dest-ip ip-address [ source-ip ip-address ] [ dest-udp-
port port-id ] [ source-udp-port port-id ] } [ tc tc ] [ ttl
ttl ] [ pkt-size pkt-size ] [ rate rate ]
Raisecom(config)#sla oper-num rfc2544 pkt-loss interface
{ interface-type interface-number | port-channel port-channel }
[ pkt-size pkt-size ] [ rate rate ]

Raisecom Proprietary and Confidential

321
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Step Command Description

5 Raisecom(config)#sla oper-num rfc2544 throughput interface Configure
{ interface-type interface-number | port-channel port-channel } RFC2544
[ eth dest-mac mac-address ] [ cvlan vlan-id ] [ svlan vlan- throughput test.
id ] [ pkt-size pkt-size ] [ threshold threshold ] [ cos cos ]
Raisecom(config)#sla oper-num rfc2544 throughput interface
{ interface-type interface-number | port-channel port-channel }
{ ipv4 dest-ip ip-address [ source-ip ip-address ] [ dest-udp-
port port-id ] [ source-udp-port port-id ] } [ tc tc ] [ ttl
ttl ] [ pkt-size pkt-size ] [ threshold threshold ]
Raisecom(config)#sla oper-num rfc2544 throughput interface
{ interface-type interface-number | port-channel port-channel }
[ pkt-size pkt-size ] [ threshold threshold ]

13.5.4 Configuring alarm threshold

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#sla oper-num loss- Configure the packet loss rate alarm threshold.
rate-threshold { current | average }
[ ds | sd | twoway ] threshold By default, it is 999999.
3 Raisecom(config)#sla oper-num loss- Enable packet loss rate alarm.
pkt-trap { current | average } enable
By default, it is disabled,
4 Raisecom(config)#sla oper-num delay- Configure delay alarm threshold.
threshold { current | average } [ ds
| sd | two-way ] threshold
By default, it is 5000000us.
5 Raisecom(config)#sla oper-num delay- Enable delay alarm.
trap { current | average } [ ds | sd
| two-way ] enable
By default, it is disabled.
6 Raisecom(config)#sla oper-num Configure jitter alarm threshold.
latency-threshold { current |
average } [ ds | sd | two-way ]
By default, it is 10000000us.
threshold
7 Raisecom(config)#sla oper-num Enable jitter alarm.
latency-trap { current | average }
[ ds | sd | two-way ] enable
By default, it is disabled.

13.5.5 Configuring SLA operation scheduling

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#sla schedule oper- Configure SLA scheduling information, including
num [ life [ forever | life-time] ] the lifetime period and executive interval, and
[ period second ] enable SLA operation scheduling.
By default, SLA operation scheduling is disabled.

Raisecom Proprietary and Confidential

322
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Step Command Description

3 Raisecom(config)#sla schedule oper- Configure the scheduling information about the
num sd bad-seconds bad-seconds good- SLA signal degradation test, such as bad second
seconds good-seconds period and good second period, and enable SLA
scheduling.
By default, the bad second period is 5s and the
good second period is 1080s.

 The operation lifetime should not be shorter than the interval for scheduling the
SLA operation.
 The interval for scheduling the SLA operation should not be shorter than 20s.

13.5.6 Checking configurations

No. Command Description
1 Raisecom#show sla Show SLA global information.
2 Raisecom#show sla { all | oper-num | Show information about SLA operation.
group-id group-id } configuration
3 Raisecom#show sla { all | oper-num | Show information about the last test of an
group-id group-id } result operation.
4 Raisecom#show sla { all | oper-num } Show statistics of operation scheduling.
statistic
5 Raisecom#show sla { all | oper-num } Show threshold of operation scheduling.
threshold

13.6 Configuring Y.1564

In the MPLS network environment, both the initiating end and the loopback end of the
Y.1564 test are PE devices, which are responsible for encapsulating and
decapsulating Y.1564 test packets. The test process is as below:
 The initiating PE encapsulates the Y.1564 test packet into a PW packet and
forwards it to the loopback PE in the MPLS network.
 After receiving the PW packet, the loopback PE decapsulates the packet and
restores it to the Y.1564 test packet.
 After the Y.1564 test packet exchanges source and destination IP addresses, and
source and destination MAC addresses at the loopback PE, it is encapsulated as
a PW packet again.
 The PW packet is forwarded to the initiating PE through the MPLS network,
decapsulated, and restored to the Y.1564 test packet.
 The initiating PE collects and processes the test packets and completes the
Y.1564 test.
Raisecom Proprietary and Confidential
323
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

13.6.1 Configuring service test

Test enviornments are shown below:

 When associating a Layer 2 Ethernet interface is specified, the test environment is
based on Ethernet.
 When associating a physical-layer interface or sub-interface enabled with MPLS is
specified, the test environment is based on MPLS.
 When associating a Layer 3 routing interface is specified, the test environment is
based on Layer 3 networking.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#sla oper-num y1564 throughput Configure the Y.1564 test based on
{ interface | nni-interface } interface-type Layer 2.
interface-number eth dest-mac mac-address
[ cvlan vlan-id [ tpid tpid ] [ cos cos ] ]
[ svlan vlan-id [ tpid tpid ] [ cos cos ] ]
[ pkt-size { pkt-size | increase | random } ]
[ cir cir cbs cbs [ eir eir ebs ebs ] ] [ mode
cir [ step step ] [ eir [ overload ] ] ]
[ group-id group-id ]
3 Raisecom(config)#sla oper-num y1564 throughput Configure Y.1564 test based on Layer
{ interface | nni-interface } interface-type 3.
interface-number ipv4 dest-ip ip-address
source-ip ip-address [ dest-udp-port udp-port ] In a Layer 3 networking scenario, the
[ source-udp-port udp-port ] [ tc tc ] [ svlan destination IP address ipv4 dest-ip ip-
svlan-id ] [ nexthop-ip ip-address ] [ smac address is the IP address of the peer
mac-address ] [ ttl ttl ] [ pkt-size { pkt-size loopback device or the CE connected to
| increase | random } ] [ cir cir cbs cbs [ eir the peer loopback device.
eir ebs ebs ] ] [ mode cir [ step step ] [ eir  When the IP address of the peer
[ overload ] ] ] [ group-id group-id ] loopback device is adopted, you
should configure external loopback
on the peer loopback device.
 When the IP address of the CE
connected to the peer loopback
device is adopted, you can configure
internal loopback or external
loopback on the peer loopback
device.
In the MPLS network scenario, the
value of the IP address has no impact
on the loopback mode.

13.6.2 Configuring service performance test

Test enviornments are shown below:

Raisecom Proprietary and Confidential

324
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

 When associating a Layer 2 Ethernet interface is specified, the test environment is

based on Ethernet.
 When associating a physical-layer interface or sub-interface enabled with MPLS is
enabled, the test environment is based on MPLS.
 When associating a Layer 3 routing interface is specified, the test environment is
based on Layer 3 networking.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#sla oper-num y1564 performance Configure the Y.1564 test based on
{ interface | nni-interface } interface-type Layer 2.
interface-number eth dest-mac mac-address
[ cvlan vlan-id [ tpid tpid ] [ cos cos ] [ cfi
cfi ] ] [ svlan vlan-id [ tpid tpid ] [ cos
cos ] [ cfi cfi ] ] [ pkt-size { pkt-size |
increase | random } ] bandwidth bandwidth-value
tc tc-value group-id group-id
3 Raisecom(config)#sla oper-num y1564 performance Configure Y.1564 test based on Layer
{ interface | nni-interface } interface-type 3.
interface-number ipv4 dest-ip ip-address
source-ip ip-address [ dest-udp-port udp-port ]
In a Layer 3 networking scenario, the
[ source-udp-port udp-port ] [ svlan svlan-id ] destination IP address ipv4 dest-ip ip-
[ nexthop-ip ip-address ] [ smac mac-address ] address is the IP address of the peer
[ ttl ttl ] [ pkt-size { pkt-size | increase | loopback device or the CE connected to
random } ] bandwidth bandwidth-value tc tc- the peer loopback device.
value group-id group-id  When the IP address of the peer
loopback device is adopted, you
should configure external loopback
on the peer loopback device.
 When the IP address of the CE
connected to the peer loopback
device is adopted, you can configure
internal loopback or external
loopback on the peer loopback
device.
In the MPLS network scenario, the
value of the IP address has no impact
on the loopback mode.

13.6.3 Scheduling test

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#sla schedule group-id group-id Schedule the Y.1564 performance test.
[ life { life-time | forever } ] performance
3 Raisecom(config)#sla schedule group-id group-id Schedule the Y.1564 configuration test.
[ period period ] thoughput
4 Raisecom(config)#sla schedule { oper-num | Schedule a certain or all Y.1564 tests.
all }

Raisecom Proprietary and Confidential

325
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

13.6.4 Checking configurations

No. Command Description
1 Raisecom#show sla Show global SLA.
2 Raisecom#show sla { all | oper-num | Show Y.1564 test configurations.
group-id group-id } configuration
3 Raisecom#show sla { all | oper-num } Show information about the latest test of the
result specified operation.
4 Raisecom#show sla group-id group-id Show the test results of the performance or
result { performance | throughput } configuration test group.
5 Raisecom#show sla group-id group-id Show the 5-minute test results of the
result performance latest performance test group.

13.7 Configuring link quality alarm

13.7.1 Perparing for configurations

Scenario
By enabling link quality alarm, you can test the transmission error code rate on the interface.
When the error code rate reaches the preconfigured threshold, it will trigger the link status
alarm, thus monitoring the link quality.

Prerequisite
N/A

13.7.2 Configuring link detection

Link quality detection is based on interface. However, it does not support LAG interface.

No. Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration mode.
interface-number

3 Raisecom(config-port)#link-quality low bit- Configure the error code rate threshold for
error-threshold error-ratio bit-error- triggering link quality alarm and the error
confficient bit-error-power resume-ratio code rate threshold for recovering the link
bit-error-confficient bit-error-power quality.
4 Raisecom(config-port)#bit-error test enable Configure the link quality detection
[ interval interval-value ] [ window window- algorithm and enable detection.
value ] [ period period-value ]

Raisecom Proprietary and Confidential

326
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

13.7.3 Checking configurations

No. Command Description
1 Raisecom#show bit-error-config interface-type Show link quality detection
interface-number configurations.
2 Raisecom#show bit-error-test result interface-type Show link quality detection
interface-number results.

13.8 Maintenance
Command Description

Raisecom(config)#clear oam config Clear OAM configurations.

Raisecom(config-port)#clear oam event Clear OAM event statistics.
Raisecom(config-port)#clear oam statistics Clear OAM statistics.
Raisecom(config)#clear { ais | lck | csf | ccm } Clear AIS, LCK, CSF, and CCM statistics.
packet statistic

Raisecom(config)#clear ethernet cfm errors Clear error CCM records.

[ level md-level ]
Raisecom(config)#clear ethernet cfm remote-mep Clear information about discovered remote
[ level md-level ] MEPs.
Raisecom(config)#clear ethernet cfm suppress- Clear alarm inhibition information about
alarm source MEPs.

Raisecom(config)#clear ethernet cfm traceroute- Clear LinkTrace cache configurations.

cache
Raisecom(config)#clear bfd session-id statistics Clear statistics about specified BFD
sessions.
Raisecom(config)#clear mpls-tp cfm errors [ level Clear MPLS-TP error CCM records.
md-level ]
Raisecom(config)#clear mpls-tp cfm remote-mep Clear configurations about MPLS-TP
[ level md-level ] discovered remote MEPs.
Raisecom(config)#clear cfm suppress-alarm source Clear alarm inhibition information about
MPLS-TP MEPs.
Raisecom(config)#clear mpls-tp cfm suppress-alarm Clear source information about inhibited
source MPLS-TP AIS/LCK alarms.
Raisecom(config)#clear { ais | lck | csf | ccm } Clear MPLS-TP AIS, LCK, CSF, and CCM
packet statistic statistics.

Raisecom Proprietary and Confidential

327
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

13.9 Configuration examples

13.9.1 Examples for configuring BFD for sub-interface directly-
connected single hop detection

Networking requirements
As shown in Figure 13-1, the Gigaethernet 1/5/1.10 on iTN A and the Gigaethernet 1/5/1 on
iTNB are directly connected through Switch E and Switch F, which is for emulating fault
nodes and detecting BFD alarm. Configure BFD for sub-interface detection on the iTN A and
iTN B.

Figure 13-1 BFD for sub-interface directly-connected single hop detection

Configuration steps
The configuration steps of iTN A and iTN B are the same, take iTNA for example.

When configuring the BFD session ID, configure the local end and remote end with
the same ID.
Step 2 Configure the sub-interface to encapsulate the VLAN and IP address. Then iTN A and iTN B
can ping through each other.

Raisecom#hostname iTNA
iTNA#config
iTNA(config)#interface gigaethernet 1/5/1.10
iTNA(config-gigaethernet 1/5/1.10)#encapsulation dot1Q 10
iTNA(config-gigaethernet 1/5/1.10)#ip address 1.1.1.1
iTNA(config-gigaethernet 1/5/1.10)#exit

Step 3 Configure BFD for sub-interface directly-connected single hop detection without configuring
the default value of the parameter.

iTNA(config)#bfd 1 bind peer-ip 1.1.1.2 interface gigaethernet 1/5/1.10

iTNA(config-bfd-session)#local discriminator 30
iTNA(config-bfd-session)#remote discriminator 40
iTNA(config-bfd-session)#session enable
iTNA(config-bfd-session)#exit

Raisecom Proprietary and Confidential

328
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Checking results
 After configuring the IP address of the sub-interface, use the show ip route command to
show the route learning status.

iTNA#show ip route
Routing Tables: Default-IP-Routing-Table
-------------------------------------------------------------------------
Flag: C - connected, S - static, R - RIP, B - BGP, O - OSPF, I - IS-IS
P - Protocol, s - States, > - selected , * - active, Dis - Distance

P&s Destination/Mask Dis/Metric NextHop Age Interface

C>* 1.1.1.0/24 0/0 1.1.1.2 1d05h48m GE1/5/1.10

C>* 172.16.67.132/32 0/0 127.0.0.1 1d05h48m lo0
S>* 172.16.68.0/24 1/0 172.16.67.1 1d05h48m FE1/0/1
S>* 172.16.70.0/24 1/0 172.16.67.1 1d05h48m FE1/0/1

 After configuring BFD for sub-interface, use the show bfd config command to show
BFD configurations.

iTNA#show bfd config

Session Id: 1
Configuration Type: static
Session Description: --
Session Bind Type: single-hop
Interface: gigaethernet1/5/8.10
Peer Ip Address: 1.1.1.2
Source Ip Address: 1.1.1.1
Ldp Lsp: 0.0.0.0, 0.0.0.0
Tunnelif: --
Pw Id: 0/--
Pw TTL: 0
Pw Type: 1
Session Mode: AsyncWithOutEcho
Bind Application: --
Local Discriminator: 30
Remote Discriminator: 40
Min Send Interval(ms): 10
Min Receive Interval(ms): 10
Detection Multiplier: 3
Session Wtr(s): 0
Role State: Active
Enable State: Enable

 Disconnect the link between Switch E and Switch F to create a fault. Use the show bfd
state command to show BFD status.

Raisecom Proprietary and Confidential

329
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

iTNA#show bfd state

SessionId State co-Tx-Interval(ms) co-Rx-Interval(ms) co-Detect-
Interval(ms)
---------------------------------------------------------------
1 AdminUP 1000 1000 --

13.9.2 Examples for configuring BFD for IP single-hop detection

Networking requirements
As shown in Figure 13-2, sub-interface Gigaethernet 1/5/1.10 on iTN A and sub-interface
Gigaethernet 1/5/1 on iTNB are directly connected through Switch E and Switch F which are
for emulating fault nodes and detecting BFD alarm. Configure BFD for IP single-hop
detection on the iTN A and iTN B respectively.

Figure 13-2 BFD for IP single-hop detection

Configuration steps

When configuring the BFD session ID, configure the local end and remote end with
the same ID.
Step 2 Configure the sub-interface to encapsulate the VLAN and IP address. Then iTN A and iTN B
can ping through each other.

iTN A

iTNA#config
iTNA(config)#interface gigaethernet 1/5/1.10
iTNA(config-gigaethernet 1/5/1.10)#encapsulation dot1Q 10
iTNA(config-gigaethernet 1/5/1.10)#ip address 1.1.1.1
iTNA(config-gigaethernet 1/5/1.10)#exit

iTN B

iTNB#config
iTNB(config)#interface gigaethernet 1/5/1.10
iTNB(config-gigaethernet 1/5/1.10)#encapsulation dot1Q 10
iTNB(config-gigaethernet 1/5/1.10)#ip address 1.1.1.2
iTNB(config-gigaethernet 1/5/1.10)#exit

Raisecom Proprietary and Confidential

330
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Step 3 Configure BFD for IP single-hop detection without configuring the default value of the
parameter.

iTN A

iTNA(config)#bfd 1 bind peer-ip 1.1.1.2 interface gigaethernet 1/5/1.10

iTNA(config-bfd-session)#local discriminator 30
iTNA(config-bfd-session)#remote discriminator 40
iTNA(config-bfd-session)#session enable
iTNA(config-bfd-session)#exit

iTN B

iTNB(config)#bfd 1 bind peer-ip 1.1.1.1 interface gigaethernet 1/5/1.10

iTNB(config-bfd-session)#local discriminator 40
iTNB(config-bfd-session)#remote discriminator 30
iTNB(config-bfd-session)#session enable
iTNB(config-bfd-session)#exit

Checking results
 After configuring the IP address of the sub-interface, use the show ip route command to
show the route learning status.

iTNA#show ip route
Routing Tables: Default-IP-Routing-Table
-------------------------------------------------------------------------
Flag: C - connected, S - static, R - RIP, B - BGP, O - OSPF, I - IS-IS
P - Protocol, s - States, > - selected , * - active, Dis - Distance

P&s Destination/Mask Dis/Metric NextHop Age Interface

C>* 1.1.1.0/24 0/0 1.1.1.2 1d05h48m GE1/5/1.10

C>* 172.16.67.132/32 0/0 127.0.0.1 1d05h48m lo0
S>* 172.16.68.0/24 1/0 172.16.67.1 1d05h48m FE1/0/1
S>* 172.16.70.0/24 1/0 172.16.67.1 1d05h48m FE1/0/1

 After configuring BFD for IP, use the show bfd config command to show BFD
configurations.

iTNA#show bfd config

Session Id: 1
Configuration Type: static
Session Description: --
Session Bind Type: single-hop
Interface: gigaethernet1/5/8.10

Raisecom Proprietary and Confidential

331
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Peer Ip Address: 1.1.1.2

Source Ip Address: 1.1.1.1
Ldp Lsp: 0.0.0.0, 0.0.0.0
Tunnelif: --
Pw Id: 0/--
Pw TTL: 0
Pw Type: 1
Session Mode: AsyncWithOutEcho
Bind Application: --
Local Discriminator: 30
Remote Discriminator: 40
Min Send Interval(ms): 10
Min Receive Interval(ms): 10
Detection Multiplier: 3
Session Wtr(s): 0
Role State: Active
Enable State: Enable

 Disconnect the link between Switch E and Switch F to create a fault. Use the show bfd
state command to show BFD status.

iTNA#show bfd state

SessionId State co-Tx-Interval(ms) co-Rx-Interval(ms) co-Detect-
Interval(ms)
---------------------------------------------------------------
1 AdminUP 1000 1000 --

13.9.3 Examples for configuring BFD for PW detection

Network requirements
As shown in Figure 13-3, iTN A and iTN B access user services through their respective GE
1/2/1.10 interfaces. User services are transmitted to the peer through the PW links deployed
on iTN devices. To detect the connectivity of PW links between iTN devices, enable BFD for
PW on iTN A and iTN B to detect the status of the PW link. Once a fault is detected, an alarm
will be reported.

Figure 13-3 Configuring BFD for PW detection

Raisecom Proprietary and Confidential

332
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Configuration principle
 Configure the IP address of the device interface.
 Configure basic MPLS functions, such as LSP and PW.
 Configure BFD for PW detection.

Data preparation
Table 13-1 lists data needed for BFD for PW detection.

Table 13-1 Data needed for BFD for PW detection

Device Route-ID Interface IP address
iTN A 1.1.1.1 gigaethernet 1/1/1.10 10.10.10.1/24
gigaethernet 1/2/1.10 20.10.10.1/24
Loopback 2 1.1.1.1/32
iTN B 2.2.2.2 gigaethernet 1/1/1.10 10.10.10.2/24
gigaethernet 1/2/1.10 30.10.10.1/24
Loopback 2 2.2.2.2/32

Configuration steps
Step 1 Configure the IP address of the device interface. Take iTN A for example. Configuration
steps for iTN B are similar.
iTN A

iTNA#config
iTNA(config)#interface Loopback 2
iTNA(config-Loopback2)#ip address 1.1.1.1 255.255.255.255
iTNA(config-Loopback2)#interface gigaethernet 1/1/1.10
iTNA(config-gigaethernet1/1/1.10)#encapsulation dot1Q 10
iTNA(config-gigaethernet1/1/1.10)#ip address 10.10.10.1 255.255.255.0
iTNA(config-gigaethernet1/1/1.10)#interface gigaethernet 1/2/1.10
iTNA(config-gigaethernet1/2/1.10)#encapsulation dot1Q 10
iTNA(config-gigaethernet1/2/1.10)#ip address 20.10.10.1 255.255.255.0
iTNA(config-gigaethernet1/2/1.10)#exit

Step 2 Configure MPLS basic functions, LSP, and PW.

iTN A

iTNA(config)#mpls lsr-id 1.1.1.1

iTNA(config)#mpls enable
iTNA(config)#interface tunnel 1/1/1

Raisecom Proprietary and Confidential

333
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

iTNA(config-tunnel1/1/1)#destination 2.2.2.2
iTNA(config-tunnel1/1/1)#mpls tunnel-id 1
iTNA(config-tunnel1/1/1)#mpls te commit
iTNA(config-tunnel1/1/1)#exit
iTNA(config)#mpls bidirectional static-lsp ingress lspAB lsr-id 2.2.2.2
tunnel-id 1
iTNA(config-ingress-lsp)#forward 2.2.2.2 255.255.255.255 nexthop
10.10.10.2 gigaethernet 1/1/1.10 out-label 10
iTNA(config-ingress-lsp)#backward in-label 20
iTNA(config-ingress-lsp)#exit
iTNA(config)#interface gigaethernet 1/2/1.10
iTNA(config-gigaethernet1/2/1.10)#encapsulation dot1Q 10
iTNA(config-gigaethernet1/2/1.10)#mode l2
iTNA(config-gigaethernet1/2/1.10)#mpls static-l2vc destination 2.2.2.2
tagged vc-id 1 in-label 101 out-label 101 tunnel 1/1/1 mtu 9600
iTNA(config-gigaethernet1/2/1.10)#exit

iTN B

iTNB(config)#mpls lsr-id 2.2.2.2

iTNB(config)#mpls enable
iTNB(config)#interface tunnel 1/1/1
iTNB(config-tunnel1/1/1)#destination 1.1.1.1
iTNB(config-tunnel1/1/1)#mpls tunnel-id 1
iTNB(config-tunnel1/1/1)#mpls te commit
iTNB(config-tunnel1/1/1)#exit
iTNB(config)#mpls bidirectional static-lsp ingress lspAB lsr-id 1.1.1.1
tunnel-id 1
iTNB(config-ingress-lsp)#forward 1.1.1.1 255.255.255.255 nexthop
10.10.10.1 gigaethernet 1/1/1.10 out-label 20
iTNB(config-ingress-lsp)#backward in-label 10
iTNB(config-ingress-lsp)#exit
iTNB(config)#interface gigaethernet 1/2/1.10
iTNB(config-gigaethernet1/2/1.10)#encapsulation dot1Q 10
iTNB(config-gigaethernet1/2/1.10)#mode l2
iTNB(config-gigaethernet1/2/1.10)#mpls static-l2vc destination 1.1.1.1
tagged vc-id 1 in-label 101 out-label 101 tunnel 1/1/1 mtu 9600
iTNB(config-gigaethernet1/2/1.10)#exit

Step 3 Configure dynamic BFD for PW detection.

iTN A

iTNA(config)#interface gigaethernet 1/2/1.10

iTNA(config-gigaethernet1/2/1.10)#mpls l2vpn pw bfd
iTNA(config-gigaethernet1/2/1.10)#exit

iTN B

Raisecom Proprietary and Confidential

334
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

iTNB(config)#interface gigaethernet 1/2/1.10

iTNB(config-gigaethernet1/2/1.10)#mpls l2vpn pw bfd
iTNB(config-gigaethernet1/2/1.10)#exit

Checking results
After completing configurations, use the show bfd config command to check the
configuration results.

13.9.4 Examples for configuring Y.1564 test

Networking requirements
As shown in Figure 13-4, configure the Y.1564 test type on the iTN A device, create test
services and configure test packet attributes to perform configuration test and performance
test on the target network. Configure loopback on the iTN B to loop the data flow to iTN A for
analysis. The AC-side interface of the iTN A is GE 1/2/1.10, and the AC-side interface of the
iTN B is GE 1/2/1.10, which are used to access user services. Configure Tunnel and PW on
iTN A and iTN B respectively to carry user services for transmission over the IP RAN
network.

Figure 13-4 Y.1564 test

Configuration principle
 Configure basic MPLS functions, such as LSP, tunnel, and PW on iTN A and iTN B.
 Configure the Y.1564 test on iTN A.
 Configure loopback on iTN B.
 Schedule the Y.1564 test.

Data preparation
Table 13-2 lists data needed for Y.1564 test.

Table 13-2 Data needed for Y.1564 test

Device Route-ID Interface IP address
iTN A 1.1.1.1 gigaethernet 1/1/1.10 10.10.10.1/24
loopback 2 1.1.1.1/32

Raisecom Proprietary and Confidential

335
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Device Route-ID Interface IP address

iTN B 2.2.2.2 gigaethernet 1/1/1.10 10.10.10.2/24
loopback 2 2.2.2.2/32

Configuration steps
Step 1 Refer to Table 13-2. Configure the IP addresses of interfaces on iTN A and iTN B.
For details, refer to section 3.1 Basic configurations of interface.
Step 2 Configure OSPF routing.
iTN A

iTNA(config)#router ospf 1 router-id 1.1.1.1

iTNA(config-router-ospf)#network 1.1.1.1 0.0.0.0 area 0
iTNA(config-router-ospf)#network 10.10.10.1 0.0.0.0 area 0

iTN B

iTNB(config)#router ospf 1 router-id 2.2.2.2

iTNB(config-router-ospf)#network 2.2.2.2 0.0.0.0 area 0
iTNB(config-router-ospf)#network 10.10.10.2 0.0.0.0 area 0

Step 3 Configure basic MPLS functions on iTN A and iTN B, such as LSP and PW.
iTN A

iTNA(config)#mpls lsr-id 1.1.1.1

iTNA(config)#mpls enable
iTNA(config)#interface tunnel 1/1/1
iTNA(config-tunnel1/1/1)#destination 2.2.2.2
iTNA(config-tunnel1/1/1)#mpls tunnel-id 1
iTNA(config-tunnel1/1/1)#mpls te commit
iTNA(config-tunnel1/1/1)#exit
iTNA(config)#mpls bidirectional static-lsp ingress lspAB lsr-id 2.2.2.2
tunnel-id 1
iTNA(config-ingress-lsp)#forward 2.2.2.2 255.255.255.255 nexthop
10.10.10.2 out-label 10
iTNA(config-ingress-lsp)#backward in-label 20
iTNA(config-ingress-lsp)#exit
iTNA(config)#interface gigaethernet 1/2/1.10
iTNA(config-gigaethernet1/2/1.10)#encapsulation dot1Q 10
iTNA(config-gigaethernet1/2/1.10)#mode l2
iTNA(config-gigaethernet1/2/1.10)#mpls static-l2vc destination 2.2.2.2
tagged vc-id 1 in-label 101 out-label 101 tunnel 1/1/1 mtu 9600

Raisecom Proprietary and Confidential

336
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

iTNA(config-gigaethernet1/2/1.10)#exit

iTN B

iTNB(config)#mpls lsr-id 2.2.2.2

iTNB(config)#mpls enable
iTNB(config)#interface tunnel 1/1/1
iTNB(config-tunnel1/1/1)#destination 1.1.1.1
iTNB(config-tunnel1/1/1)#mpls tunnel-id 1
iTNB(config-tunnel1/1/1)#mpls te commit
iTNB(config-tunnel1/1/1)#exit
iTNB(config)#mpls bidirectional static-lsp egress lspAB lsr-id 1.1.1.1
tunnel-id 1
iTNB(config-ingress-lsp)#forward out-label 20
iTNB(config-ingress-lsp)#backward 1.1.1.1 255.255.255.255 nexthop
10.10.10.1 in-label 10
iTNB(config-ingress-lsp)#exit
iTNB(config)#interface gigaethernet 1/2/1.10
iTNB(config-gigaethernet1/2/1.10)#encapsulation dot1Q 10
iTNB(config-gigaethernet1/2/1.10)#mode l2
iTNB(config-gigaethernet1/2/1.10)#mpls static-l2vc destination 1.1.1.1
tagged vc-id 1 in-label 101 out-label 101 tunnel 1/1/1 mtu 9600
iTNB(config-gigaethernet1/2/1.10)#exit

Step 4 Configure Y.1564 test on iTN A.

iTNA(config)#sla 1 y1564 performance interface gigaethernet 1/2/1.10 ipv4

dest-ip 2.2.2.2 source-ip 1.1.1.1 pkt-size 1024 bandwidth 500000 tc 0
group-id 1
/*configure a performance test operation which is based on AC-side
interface.*/
iTNA(config)#sla 2 y1564 throughput interface gigaethernet 1/2/1.10 ipv4
dest-ip 2.2.2.2 source-ip 1.1.1.1 pkt-size 1518 mode cir step 1
/*configure a throughput test operation which is based on AC-side
interface.*/

Step 5 Configure internal loopback on the AC-side interface (PW service extraction interface) on
iTNB, looping data flow back to iTN A.

iTNB(config)#interface gigaethernet 1/2/1.10

iTNB(config-gigaethernet1/2/1.10)#loopback internal

Step 6 Schedule Y.1564 test on iTN A.

iTNA(config)#sla schedule group-id 1 life 5 performance

Raisecom Proprietary and Confidential

337
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

iTNA(config)#sla schedule 2 period 60

Checking results
 After step 1, use the show mpls bidirection static-lsp command to show LSP
configuration results.
iTNA(config)#show mpls bidirectional static-lsp
LSP-Index: 1
LSP-Name: lspab
LSR-Role: Ingress
LSP-Flag: Working
Ingress-Lsr-Id: 1.1.1.1
Egress-Lsr-Id: 2.2.2.2
Tunnel-Id: 1
LSP Status: Up
/*LSP is UP.*/
Forward Destination: 2.2.2.2
Forward In-Label: --
Forward Out-Label: 10
Forward In-Interface: --
Forward Out-Interface: gigaethernet1/1/1.10
Forward Next-Hop: 10.10.10.2
Forward Next-Mac: --
Forward Vlan-Id: --
Forward XcIndex: 1
Forward Ds mode: Uniform
Forward PipeServClass: --
Forward Exp2LocalPriMap: Default
Forward LocalPri2ExpMap: Default
Backward Destination: --
Backward In-Label: 20
Backward Out-Label: --
Backward In-Interface: all interfaces
Backward Out-Interface: --
Backward Next-Hop: --
Backward Next-Mac: --
Backward Vlan-Id: --
Backward XcIndex: 2
Backward Ds mode: Uniform
Backward PipeServClass: --
Backward Exp2LocalPriMap: Default
Backward LocalPri2ExpMap: Default

 After step 1, use the show mpls l2vc command to show PW configuration results.

iTNA(config)#show mpls l2vc

Client interface : gigaethernet1/2/1.10
Pw index : 1
Vc id : 1
Encapsulation type : tagged
Ac fault relay action : relay

Raisecom Proprietary and Confidential

338
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Tunnel type : mplsTe

Destination : 2.2.2.2
Tunnel policy : --
Tunnel number : 1/1/1
Local vc label : 101
Remote vc label : 101
Ac status : up(bfd:up, cc:up)
/*AC is UP.*/
Pw state : up(bfd<L0,R0>:up, cc:up, sd:up, cd:up)
/*PW is UP.*/
Vc state : up
/*VC is UP.*/
Vc signal : manual
Local cw : enable
Operational cw : enable
Local vc mtu : 9600
Remote vc mtu : --
Tpid : 0x8100
Svlan : --
Pw role : PrimaryPw
Pw work status : Working
Pw access mode : mesh
Pw QosMode : --
Pw Bandwidth Cir : --
Pw Bandwidth Pir : --
Pw Bandwidth Valid : InValid
Pw Weight : --
Pw Flow Queue : --
Pw DsMode : Uniform
Pw PipeServClass : --
Pw Exp2LocalPriMap : Default
Pw LocalPri2ExpMap : Default
Create time : 1972-06-22,09:02:04
Up time : 0 days, 0 hours, 2 minutes, 41 seconds
Last change time : 1972-06-22,09:02:04
----------------------------------------
Total l2vc : 1 1 up 0 down
/*L2VC is UP, which means that it is normal.*/

 Use the ping mpls vc-id destination command to check whether PW path is well
connected.

iTNA#ping mpls vc-id 1 destination 2.2.2.2

Sending 5, 200-byte MPLS Echoes to 2.2.2.2,VC ID is 1, timeout is 3
seconds,send interval is 1 seconds,
Press CTRL + C to abort:
Reply from 2.2.2.2: bytes=84, Sequence=1, time<1ms.
Reply from 2.2.2.2: bytes=84, Sequence=2, time<1ms.
Reply from 2.2.2.2: bytes=84, Sequence=3, time<1ms.
Reply from 2.2.2.2: bytes=84, Sequence=4, time<1ms.
Reply from 2.2.2.2: bytes=84, Sequence=5, time<1ms.
---- PING Statistics----
5 packets transmitted,5 packets received,

Raisecom Proprietary and Confidential

339
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

Success rate is 100 percent(5/5),

round-trip (ms) min/avg/max = 0/0/0

 After configurations are complete, you can use the show sla group-id configuration
command to check configuration results of performance test.

iTNA#show sla group-id 1 configuration performance

------------------------------------------------------------------------
Operation <1>:
Type: Y1564-PERFORMANCE
Frame type: IPV4
------------------------------------------------------------------------
UNI: gigaethernet1/2/1.10
Destination IP Address: 2.2.2.2
Destination UDP Port : 7
Source IP Address: 1.1.1.1
Source UDP Port : 49184
Service Vlan ID: 0
Nexthop IP Address: 0.0.0.0
TTL Value: 255
Frame Size: 1024
Frame pattern: null
TC: 0
BandWidth(Kbit/s): 500000
Group Id: 1

 After configurations are complete, use the show sla configuration command to show
configuration results of the throughput test.

iTNA#show sla 2 configuration

------------------------------------------------------------------------
Operation <2>:
Type: Y1564-THROUGHPUT
Frame type: IPV4
------------------------------------------------------------------------
UNI: gigaethernet1/2/1.10
Destination IP Address: 2.2.2.2
Destination UDP Port : 7
Source IP Address: 1.1.1.1
Source UDP Port : 49184
TC: 0
Service Vlan ID: 0
Nexthop IP Address: 0.0.0.0
TTL Value: 255
Frame Size: 1518
Frame pattern: null
Mode: Cir
Cir Step: 1
Group Id: 0

Raisecom Proprietary and Confidential

340
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 13 OAM

 Use the show sla group-id result command to show performance test results.

iTNA#show sla group-id 1 result performance

------------------------------------------------------------------------
Group<1>:
Performance-Test:
Id: 1
Status: Completed
Min Mean Max
Flr(0.001%): 0 0 0
Ftd(us): 57 58 60
Fdv(us): 0 0 2
Ir(Mbit/s): 500.000 500.000 500.000
Delay range(us): 3
BER(ES): 0
Available(%): 100
Result: PASS

 Use the show sla result command to show throughput test results.

iTNA#show sla 2 result

------------------------------------------------------------------------
Operation <2>:
Schedule Status: Active
Throughput-Test:
Cir Test:
Step 1(25%):
Min Mean Max
Flr(0.001%): 0 0 0
Ftd(us): 76 77 89
Fdv(us): 0 0 12
Ir(Mbit/s): 250.000 250.000 250.000
Delay range(us): 13
BER(ES): 0
Available(%): 100
Result: PASS

Raisecom Proprietary and Confidential

341
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

14 Security

This chapter describes principles and configuration procedures of security, as well as related
configuration examples, including following sections:
 Configuring storm control
 Configuring CPU protection
 Configuring memory monitoring
 Configuring CPU monitoring
 Configuring RADIUS
 Configuring TACACS+
 Configuring dot.1x
 Configuring interface isolation
 Configuring port mirroring
 Configuring URPF
 Maintenance
 Configuration examples

14.1 Configuring storm control

14.1.1 Preparing for configurations

Scenario
In the Layer 2 network, after storm control is configured, it can inhabit generation of
broadcast storm, when unknown multicast, unknown unicast, and broadcast packets increase,
to ensure forwarding normal packets.

Prerequisite
Configure physical parameters on an interface and make the physical layer Up.

Raisecom Proprietary and Confidential

342
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

14.1.2 Configuring storm control

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#vlan vlan-id Enter VLAN configuration mode.
Raisecom(config)#interface interface- (Optional) enter interface configuration mode.
type interface-number
3 Raisecom(config-vlan)#storm-control Enable storm control.
{ broadcast | unknown-multicast | dlf |
all } enable
By default, storm control of broadcast packets,
Raisecom(config-port)#storm-control
unknown multicast packets, and unknown unicast
{ broadcast | unknown-multicast | dlf |
packets is disabled.
all } enable
4 Raisecom(config-vlan)#ratelimit Configure the rate limiting threshold of storm
{ broadcast | unknown-multicast | dlf } control.
cir cir-value [ cbs cbs-value ]
Raisecom(config-port)#ratelimit
By default:
{ broadcast | unknown-multicast | dlf }  Broadcast traffic: cir-value 0 and cbs-value = 0
cir cir-value [ cbs cbs-value ]  Unknown multicast traffic: cir-value 0 and cbs-
value = 0
 Unknown unicast traffic: cir-value 0 and cbs-

value = 0

When storm control is enabled, you can configure rate limiting. However,
configurations cannot take effect. When storm control is disabled, rate limiting
configurations take effect automatically.

14.1.3 Checking configurations

No. Command Description
1 Raisecom#show storm-control [ vlan vlan-id ] Show storm control configurations.

14.2 Configuring CPU protection

14.2.1 Preparing for configurations

Scenario
When the device receives a great number of attack packets in a short period, the CPU will run
with full load and the CPU utilization rate reaches to 100%. This will cause the normal
functions of the device to fail. CPU CAR helps to efficiently limit the speed of packets, which
enters the CPU.

Raisecom Proprietary and Confidential

343
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

Prerequisite
N/A

14.2.2 Configuring global CPU CAR

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#cpu-protect car Configure the protocol type, rate limiting mode,
{ arp | dhcp | global | icmp | igmp | CIR, and CBS of global CPU packet protection.
tcp } { kbps | pps } cir cir cbs cbs
By default, the CIR and CBS are respectively 500
pps and 500 pkt globally.

14.2.3 Configuring interface CPU CAR

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter Layer 3 physical interface configuration
type interface-number mode.
3 Raisecom(config-port)#cpu-protect car Configure the CIR and CBS of Layer 3 physical
{ arp | dhcp | icmp | igmp | tcp } interface CPU packet protection.
kbps cir cir cbs cbs
By default, CPU CAR default configurations are
adopted.
4 Raisecom(config)#portswitch Enter Layer 2 physical interface configuration
mode.
5 Raisecom(config-port)#cpu-protect car Configure the protocol type, rate limiting mode,
{ arp | dhcp | icmp | igmp | tcp } CIR, and CBS of Layer 2 physical interface CPU
kbps cir cir cbs cbs packet protection.
By default, CPU CAR default configurations are
adopted.

14.2.4 Checking configurations

No. Command Description
1 Raisecom#show cpu-protect car statistics Show CPU CAR statistics on the interface.
interface-type interface-number

Raisecom Proprietary and Confidential

344
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

14.3 Configuring memory monitoring

14.3.1 Preparing for configurations

Scenario
This feature enables you to monitor the memory utilization of the system in real time and
configure memory utilization crossing threshold alarms, thus facilitating fault location and
clearance in time or assist NMS personnel in locating faults.

Prerequisite
To output memory utilization alarms as Trap, you must configure the IP address of the target
server for outputting Trap, namely, the IP address of the NMS server.

14.3.2 Configuring memory monitoring

Step Command Description
1 Raisecom#memory utilization Configure the upper threshold for memory utilization alarms.
threshold threshold-value
By default, it is 70, namely, 70%.
2 Raisecom#memory utilization Enable memory utilization monitoring.
monitor enable
By default, it is enabled.

14.3.3 Checking configurations

No. Command Description
1 Raisecom#show memory[utilization threshold ] Show memory utilization rate.

14.4 Configuring CPU monitoring

14.4.1 Preparing for configurations

Scenario
CPU monitoring is used to monitor task status, CPU utilization rate, and stack usage in real
time. It provides CPU utilization threshold alarm to facilitate discovering and eliminating a
hidden danger, helping the administrator locate the fault quickly.

Prerequisite
To output CPU monitoring alarms in a Trap form. You need to configure the IP address of
Trap target host on the iTN8800, that is, the IP address of the NView NNM system.

Raisecom Proprietary and Confidential

345
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

14.4.2 Viewing CPU monitoring information

Step Command Description
1 Raisecom#show cpu-utilization [ dynamic | history Show CPU utilization rate.
{ 10min | 1min | 2hour | 5sec } ]
2 Raisecom#show process [ dead | sorted { normal- Show task status.
priority | process-name } | taskname ]
3 Raisecom#show process cpu [ sorted [ 10min | 1min Show CPU utilization rate of all
| 5sec | invoked ] ] tasks.

14.4.3 Configuring CPU monitoring alarm

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#cpu (Optional) configure the upper CPU threshold.
rising-threshold
rising-threshold-value The configured upper CPU threshold must be greater than the lower
threshold.
By default, the upper CPU threshold is 100%.
3 Raisecom(config)#cpu (Optional) configure the lower CPU threshold.
falling-threshold
falling-threshold- By default, the lower CPU threshold is set to 1%.
value
4 Raisecom(config)#cpu (Optional) configure the CPU alarm sampling period.
interval interval-
value By default, it is 60s.

14.4.4 Checking configruations

No. Command Description
1 Raisecom#show cpu-utilization Show CPU utilization rate and related configurations.

14.5 Configuring RADIUS

14.5.1 Preparing for configurations

Scenario
To control users accessing devices and network, you can deploy the RADIUS server at the
network to authenticate and account users. The iTN8800 can be used as a Proxy of the
RADIUS server to authenticate users based on results returned by the RADIUS server.

Raisecom Proprietary and Confidential

346
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

Prerequisite
N/A

14.5.2 Configuring RADIUS authentication

Step Command Description
1 Raisecom#radius [ backup ] ip-address Specify the IP address and port ID of the RADIUS
[ auth-port port-id ] [ vpn-instance authentication server.
vpn-instance-name ] [ sourceip source-
ip-address ] The backup parameter is used to specify a backup
RADIUS authentication server.
2 Raisecom#radius-key string Configure the shared key for RADIUS
authentication.
3 Raisecom#user login { local-user | Configure the authentication mode for login when
radius-user | local-radius | radius- RADIUS authentication is applied.
local [ server-no-response ] }
4 Raisecom#enablelogin{ local-user | Configure the authentication mode for entering
radius-user | local-radius | radius- privileged EXEC mode when RADIUS
local [ server-no-response ] } authentication is applied.

14.5.3 Configuring RADIUS accounting

Step Command Description
1 Raisecom#aaa Enable RADIUS accounting.
accounting login
enable
By default, RADIUS accounting is disabled.
2 Raisecom#radius Specify the IP address and port ID of the RADIUS accounting server.
[ backup ]
accounting-server By default, the UDP port ID is 1813.
ip-address The backup parameter is used to specify a backup RADIUS accounting
[ account-port ] server.
3 Raisecom#radius Configure the shared key used for communicating with the RADIUS
accounting-server accounting server. The shared key must be identical to the one configured
key string on the RADIUS accounting server. Otherwise, accounting operation fails.
By default, the shared key is empty.
4 Raisecom#aaa Configure the processing policy for accounting failure.
accounting fail
{ online | offline}
By default, the processing policy is online. In indicates that users are
allowed to log in if accounting operation fails.

Raisecom Proprietary and Confidential

347
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

Step Command Description

5 Raisecom#aaa Configure the interval for sending accounting update packets. If the
accounting update interval is 0, it indicates that no accounting update packet is sent.
period
By default, the interval for sending accounting update packets is 0.

With the accounting begin packet, accounting update packet, and

accounting end packet, the RADIUS server can record the
access time and operations of each user.

14.5.4 Checking configurations

No. Command Description
1 Raisecom#show radius-server Show configurations of the RADIUS server.

14.6 Configuring TACACS+

14.6.1 Preparing for configurations

Scenario
To control users accessing devices and network, you can deploy the RADIUS server on the
network to authenticate and account users. Compared with RADIUS, TACACS+ is more
secure and reliable. The iTN8800 can be used as a Proxy of the TACACS+ server to
authenticate users based on results returned by the TACACS+ server.

Prerequisite
N/A

14.6.2 Configuring TACACS+ authentication

Step Command Description
1 Raisecom#tacacs-server[ backup ] ip- Specify the IP address and port ID of the
address [ vpn-instance vpn-instance- TACACS+ authentication server.
name ] [ sourceip source-ip-address ]
The backup parameter is used to specify a backup
TACACS+ authentication server.
2 Raisecom#tacacs-server key string Configure the shared key for TACACS+
authentication.

Raisecom Proprietary and Confidential

348
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

Step Command Description

3 Raisecom#user login { local-user | Configure the authentication mode for login when
tacacs-user | local-tacacs | tacacs- TACACS+ authentication is applied.
local [ server-no-response ] | local-
radius | radius-local [ server-no-
response ] | radius-user }
4 Raisecom#enable login { local-user | Configure the authentication mode for entering
tacacs-user | local-tacacs | tacacs- privileged EXEC mode when TACACS+
local [ server-no-response ] | local- authentication is applied.
radius | radius-local [ server-no-
response ] | radius-user }

14.6.3 Configuring TACACS+ accounting

Step Command Description
1 Raisecom#aaa accounting login enable Enable TACACS+ accounting.
2 Raisecom#tacacs [ backup ] Configure the IP address of the TACACS+
accounting-server ip-address [ vpn- accounting server. Configure the backup parameter
instance vpn-instance-name ] to configure the IP address of the backup TACACS+
[ sourceip source-ip-address ] accounting server.
3 Raisecom#aaa accounting fail
Configure policy for processing failed accounting.
{ offline | online }
4 Raisecom#aaa accounting update Configure the period for sending accounting update
period packets. If it is configured as 0, the system never
sends accounting update packets.

14.6.4 Checking configurations

No. Command Description
1 Raisecom#show tacacs-server Show configurations of the TACACS+ server.

14.7 Configuring dot.1x

14.7.1 Preparing for configurations

Scenario
The network space of the Wi-Fi LAN features openness and mobility of terminals. It is not
like the wired LAN in which you can determine whether the terminals belong to the network
through physical network space. Therefore, how to prevent illegal access through interface
authentication challenges the Wi-Fi network. However, IEEE 802.1X can solve this problem.

Raisecom Proprietary and Confidential

349
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

14.7.2 Configuring dot.1x

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#dot1x auth-mode Configure dot.1x authentication mode, such as local
{ local | radius | tacacs+ | none } authentication, RADIUS authentication, TACACS+
authentication, and free authentication.
By default, the dot.1x authentication mode is
RADIUS.
3 Raisecom(config)#dot1x auth-method Configure dot.1x authentication mode, such as EAP
{ pap | chap | eap } relay, CHAP termination, and PAP termination.
By default, the dot.1x authentication mode is PAP.
4 Raisecom(config)#dot1x auth-type Configure dot.1x authentication type, such as
{ port | mac } interface-based authentication and MAC address–
based authentication.
By default, the dot.1x authentication mode is
interface-based authentication.
5 Raisecom(config)#dot1x auth timeout Configure the timeout of all dot.1x packets.
timeout-value
By default, the timeout is 20s. The packets will be
retransmitted for 3 times after timeout.
6 Raisecom(config)#dot1x reauth Enable dot.1x re-authentication and configure re-
interval interval-value authentication timer.
By default, the time of the re-authentication timer is
0s.
7 Raisecom(config)#dot1x keepalive Configure the timer which sends KeepAlive packets to
interval interval-value the dot.1x client.
By default, the time of the timers is 60s.
8 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-number
9 Raisecom(config-port)#dot1x Enable dot.1x.
{ enable | disable }

14.7.3 Checking configurations

No. Command Description
1 Raisecom#show dot1x interface-type Show dot.1x configurations of the interface.
interface-number
2 Raisecom#show dot1x interface-type Show dot.1x authentication statistics of the
interface-number statistics interface.

Raisecom Proprietary and Confidential

350
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

14.8 Configuring interface isolation

14.8.1 Preparing for configurations

Scenario
To isolate Layer 2 data of interfaces in a VLAN and provide physical isolation between
interfaces, you need to configure interface isolation.
By adding interfaces that need to be controlled to a VLAN protection group, you can enhance
network security and provide flexible networking scheme for users.
Interface isolation helps isolate interfaces in a VLAN, enhance network security, and provide
flexible networking schemes.

Prerequisite
N/A

14.8.2 Configuring interface isolation

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter Layer 2 physical interface
interface-number configuration mode.
Raisecom(config-port)#portswitch
3 Raisecom(config-port)#switchport protect Enable interface isolation.

14.8.3 Checking configurations

No. Command Description
1 Raisecom#show switchport protect Show configurations of interface isolation.

14.9 Configuring port mirroring

14.9.1 Preparing for configurations

Scenario
Port mirroring refers to mirroring packets of the specified mirroring port to the destination
port or aggregation group without affecting packet forwarding. With port mirroring, users can
monitor transmitting and receiving status of one or more interfaces for analyzing network
status.

Raisecom Proprietary and Confidential

351
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

Prerequisite
N/A

14.9.2 Configuring port mirroring

The same interface/link aggregation group cannot be a monitoring interface and a mirroring
source interface concurrently. Therefore, the interface/link aggregation group in step 3 and
step 4 cannot be the same one.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mirror-group group-id Create a port mirroring group.
3 Raisecom(config)#interface interface-type (Optional) enter interface configuration
interface-number mode. Configure the interface as a
Raisecom(config-port)#mirror-group group-id monitoring interface.
monitor-port
Raisecom(config-port)#exit
Raisecom(config)#interface port-channel (Optional) enter link aggregation
channel-number configuration mode. Configure the link
Raisecom(config-port-channel*)#mirror-group aggregation group as the monitoring
group-id monitor-port interface.
Raisecom(config-port-channel*)#exit
4 Raisecom(config)#interface interface-type (Optional) enter interface configuration
interface-number mode. Configure the interface as a
Raisecom(config-port)#mirror-group group-id mirroring source interface and configure
source-port [ ingress | egress ] mirroring rules to mirror the packets in
the ingress direction, egress direction, or
both directions of the source interface.
Raisecom(config)#interface port-channel (Optional) enter link aggregation
channel-number configuration mode. Configure the link
Raisecom(config-port-channel*)#mirror-group aggregation group as a mirroring source
group-id source-port [ ingress | egress ] interface and configure mirroring rules to
mirror the packets in the ingress
direction, egress direction, or both
directions of the source interface.

14.9.3 Checking configurations

No. Command Description
1 Raisecom#show mirror-group [ group-id ] Show basic information about port mirroring.

Raisecom Proprietary and Confidential

352
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

14.10 Configuring URPF

14.10.1 Preparing for configurations

Scenario
You can enable Unicast Reverse Path Forwarding (URPF) on the routing interface to avoid
network attacks which are based on source address spoofing. After it is enabled, the interface
will legally check the source address of the packet upon receiving the packet. If the packet
passes the legal check, the interface will match it with the forwarding table and then forward
it, otherwise, it will be discarded.

Prerequisite
N/A

14.10.2 Configuring URPF

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number

3 Raisecom(config-port)#ip urpf { loose | Enable URPF on the interface.

strict } [ allow-default-route ]
By default, it is disabled.

14.11 Maintenance
Command Description
Raisecom(config)#clear cpu-protect car statistics Clear global CPU CAR statistics or CPU
[ interface-type interface-number ] CAR statistics of specified interfaces.
Raisecom(config)#clear dot1x interface-type Clear dot.1x statistics of the specified
interface-number statistics interface.

Raisecom Proprietary and Confidential

353
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

14.12 Configuration examples

14.12.1 Examples for configuring storm control

Networking requirements
As shown in Figure 14-1, to control the influence of the broadcast storm on iTN A, you need
to deploy storm control on iTN A to control broadcast and unknown unicast packets. The
storm control threshold is configured to 2000 pps.

Figure 14-1 Configuring storm control

Configuration steps
Configure storm control on iTN A.

Raisecom#config
Raisecom(config)#interface gigaethernet 1/1/1
Raisecom(config-port)#storm-control broadcast enable
Raisecom(config-port)#exit
Raisecom(config)#interface gigaethernet 1/1/2
Raisecom(config-port)#storm-control broadcast enable
Raisecom(config-port)#exit
Raisecom(config)#storm-control pps 2000
Actual Storm control pps: 2000 pps

Checking results
Use the show storm-control interface command to show storm control configurations.

Raisecom#show storm-control interface

Threshold: 2000 pps
Threshold: 2000 pps

Raisecom Proprietary and Confidential

354
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

Interface Broadcast Multicast Unicast

----------------------------------------------------------------
gigaethernet1/1/1 Enable Disable Disable
gigaethernet1/1/2 Enable Disable Disable

gigaethernet1/1/3 Enable Disable Disable

gigaethernet1/2/12 Enable Disable Disable

14.12.2 Examples for configuring RADIUS

Networking requirements
As shown in Figure 14-2, to control users accessing iTN A, you need to deploy RADIUS
authentication and accounting features on iTN A to authenticate users logging in to iTN A and
record their operations.
Configure the interval for sending accounting update packet to 2min. Configure the
processing policy for accounting failure to offline.

Figure 14-2 Configuring RADIUS

Configuration steps
Step 1 Authenticate login users through RADIUS.

Raisecom#radius 192.168.1.1
Raisecom#radius-key raisecom
Raisecom#user login radius-user

Step 2 Account login users through RADIUS.

Raisecom#aaa accounting login enable

Raisecom#radiusaccounting-server 192.168.1.1
Raisecom#radius accounting-server key raisecom
Raisecom#aaa accounting fail offline
Raisecom#aaa accounting update 120

Checking results
Use the show radius-server command to show RADIUS configurations.

Raisecom Proprietary and Confidential

355
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 14 Security

Raisecom#show radius-server
Authentication server IP: 192.168.1.1 port:1812
Backup authentication server IP:0.0.0.0 port:1812
Authentication server key: raisecom
Accounting server IP: 192.168.1.1 port:1813
Backup accounting server IP: 0.0.0.0 port:1813
Accounting server key: raisecom
Accounting login: enable
Update interval(min.): 120
Accounting fail policy: offline

14.12.3 Examples for configuring TACACS+

Networking requirements
As shown in Figure 14-3, to control users accessing iTN A, you need to deploy TACACS+
authentication on iTN A to authenticate users logging in to iTN A.

Figure 14-3 Configuring TACACS+

Configuration steps
Authenticate login users through TACACS+.

Raisecom#tacacs-server 192.168.1.1
Raisecom#tacacs-serverkey raisecom
Raisecom#user login tacacs-user

Checking results
Use the show tacacs-server command to show TACACS+ configurations.

Raisecom#show tacacs-server
Server Address: 192.168.1.1
Backup Server Address: --
Sever Shared Key: raisecom
Accounting server Address: --
Backup Accounting server Address: --
Total Packet Sent: 0
Total Packet Recv: 0
Num of Error Packets: 0

Raisecom Proprietary and Confidential

356
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

15 Reliability

This chapter describes principles and configuration procedures of network reliability, as well
as related configuration examples, including following sections:
 Configuring link aggregation
 Configuring interface backup
 Configuring ELPS
 Configuring ERPS
 Configuring PW redundancy protection
 Configuring MPLS linear protection switching
 Configuring PW dual-homed protection switching
 Configuring VPN FRR
 Configuring HA hot backup
 Configuring VRRP
 Configuring PRBS test
 Maintenance
 Configuration examples

15.1 Configuring link aggregation

15.1.1 Preparing for configurations

Scenario
When greater bandwidth and high reliability are needed for network links, you can configure
manual or static LACP link aggregation.
Link aggregation aggregates multiple physical Ethernet interfaces into a logical link to
provide load sharing of uplink and downlink traffic among member interfaces. This helps
increase the bandwidth. In addition, connection reliability is enhanced when member
interfaces back up for each other dynamically.
mLACP link aggregation is used for the AC-side link in dual-homed PW protection to provide
communication between the DHD and 2 destination modes, as well as selection of active

Raisecom Proprietary and Confidential

357
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

interfaces. It is used to resolve the problem for selecting the path, prevent the loop, and
enhance the network availability.

The GE interface of the iTN8800-RXG8 does not support inter-card link aggregation
but the 10GE interface does.

Prerequisite
Configure physical parameters of the interface and make the physical layer Up.

15.1.2 Configuring manual link aggregation

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface port-channel Enter LAG configuration mode.
port-channel-number
3 Raisecom(config-port-channel*)#mode Configure the manual link aggregation mode.
manual
4 Raisecom(config-port-channel*)#load- Configuring the load-sharing mode of the link
sharing mode { dst-ip | dst-mac | label | aggregation.
src-dst-ip | src-dst-mac | src-ip | src-
mac } By default, load sharing mode is rc-dst-mac,
which means selecting the forwarding interface
according to OR operation result of source
MAC address and destination MAC address.
5 Raisecom(config-port-channel*)#exit Return to global configuration mode.
6 Raisecom(config)#interface interface-type Enter physical interface configuration mode.
interface-number
7 Raisecom(config-port)#portswitch Configure the interface as a switching interface
Raisecom(config-port)#mold l2 or a Layer 3 interface working in Layer 2
mode.
8 Raisecom(config-port)#port-channel group- Add member interfaces to the LAG.
id
9 Raisecom(config-port)#exit Return to global configuration mode.

Ensure not to configure services on interfaces, which are added to the LAG.
In a LAG, member interfaces that share loads must be identically configured.
Otherwise, data cannot be forwarded properly. For example, packets may be lost.
These configurations include STP, QoS, QinQ, VLAN, interface properties, and MAC
address learning.
 STP status on the interface, properties (point-to-point/non point-to-point) of the link
connected to the interface, path cost of the interface, STP priority, packet Tx
speed limit, whether the interface is configured with loopback protection, root
protection, and whether the interface is an edge interface.

Raisecom Proprietary and Confidential

358
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

 QoS: traffic policing, traffic shaping, congestion avoidance, rate limiting, SP queue,
WRR queue scheduling, WFQ queue, interface priority, and interface trust mode.
 QinQ: QinQ status on the interface, added outer VLAN tag, policies for adding
outer VLAN Tags for different inner VLAN IDs.
 VLAN: the allowed VLAN, default VLAN, and the link type (Trunk, Hybrid, and
Access) on the interface, and whether VLAN packets carry Tag.
 Interface properties: speed, duplex mode, and link Up/Down status.
 MAC address learning: MAC address learning status, MAC address limit, and
whether to forward and control data after the MAC address table is full.

15.1.3 Configuring static LACP link aggregation

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#lacp system-priority (Optional) configure the system LACP priority.
priority
The smaller the value is, the higher the system
LACP priority is. The end with a higher system
LACP priority is the active end. LACP selects
the active interface and standby interface based
on configurations on the active end. If the system
LACP priorities are identical, select the one with
a smaller MAC address as the active end.
By default, the system LACP priority is 32768.
3 Raisecom(config)#lacp timeout { fast | (Optional) configure the LACP timeout mode.
slow }
4 Raisecom(config)#interface port-channel Enter LAG configuration mode.
channel-number
5 Raisecom(config-port-channel*)#mode Configure the working mode of the LAG to static
lacp LACP link aggregation.
6 Raisecom(config-port-channel*)#{ max- (Optional) configure the maximum/minimum
active | min-active } links threshold number of active links of the LACP LAG.
7 Raisecom(config-port-channel*)#exit Return to global configuration mode.
8 Raisecom(config)#interface interface- Enter physical interface configuration mode.
type interface-number
9 Raisecom(config-port)#portswitch Configure the interface as a switching interface
Raisecom(config-port)#mold l2 or a Layer 3 interface working in Layer 2 mode.
10 Raisecom(config-port)#port-channel Add the interface to the LAG.
channel-number
11 Raisecom(config-port)#lacp mode (Optional) configure the LACP mode of member
{ active | passive } interfaces.
By default, the LACP mode is active. LACP
connection fails if both ends of a link are in
passive mode.

Raisecom Proprietary and Confidential

359
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Step Command Description

12 Raisecom(config-port)#lacp port- (Optional) configure the interface LACP priority.
priority priority The interface LACP priority affects the selection
of LACP default interface. The smaller the
number is, the higher the priority is.
By default, it is 32768.
13 Raisecom(config-port)#exit Return to global configuration mode.

 In a static LACP LAG, a member interface can be an active/standby one. Both the
active interface and standby interface can receive and send LACPDU. However,
the standby interface cannot forward user packets.
 The system selects a default interface based on following conditions in order:
whether the neighbor is discovered, maximum interface speed, the highest
interface LACP priority, and the smallest interface ID. The default interface is in
active status. Interfaces, which have the same speed, peer device, and operation
key of the operation key with the default interface, are in active status. Other
interfaces are in standby status.
 When the number of member interfaces in the static LAG reaches the maximum
number of active interfaces, the later-added interfaces cannot become member
interfaces even they meet all requirements on member interfaces. This helps
make traffic of current member interfaces continuous.

15.1.4 Configuring mLACP link aggregation

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mlacp-group icg-id Create a chassis group and enter chassis group
configuration mode.
3 Raisecom(config-ic-group)#iccp-channel Bind an ICCP channel to the chassis group.
channel-id
4 Raisecom(config-ic-group)#mlacp Configure the mLACP role of the local device in
{ master | slave } the chassis group.
5 Raisecom(config-ic-group)#port-channel Bind a LAG to the chassis group.
group-id
6 Raisecom(config-ic-group)#restore-mode Configure the fault restoration mode and delay of
{ non-revertive | revertive [ restore- the LAG in the chassis group.
delay second ] }
7 Raisecom(config-ic-group)#mlacp system- Configure the mLACP system priority of the
priority system-priority local device in the chassis group.
By default, it is 32768.
8 Raisecom(config-ic-group)#track pw pw- Configure the PW to be monitored in the chassis
id peer ip-address group.

Raisecom Proprietary and Confidential

360
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

15.1.5 Configuring manual backup link aggregation

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface port-channel Enter aggregation group configuration mode.
channel-number
3 Raisecom(config-port-channel*)#mode Configure the working mode of the LAG to
manual backup manual backup link aggregation.
4 Raisecom(config-port-channel*)#master- Configure the master interface of link
port interface-type interface-number aggregation.
5 Raisecom(config-port-channel*)#restore- Configure the restoration mode and restoration
mode { non-revertive | revertive delay of the LAG.
[ restore-delay second ] }
By default, the restoration mode is non-revertive.
6 Raisecom(config-port-channel*)#exit Return to global configuration mode.
7 Raisecom(config)#interface interface- Enter Layer 2 physical interface configuration
type interface-number mode.
8 Raisecom(config-port)#portswitch Configure the interface as a switching interface
Raisecom(config-port)#mold l2 or a Layer 3 interface working in Layer 2 mode.

9 Raisecom(config-port)#port-channel Add member interfaces to the LAG.

channel-number
10 Raisecom(config-port)#exit Return to global configuration mode.

15.1.6 Configuring static LACP backup link aggregation

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#lacp system- (Optional) configure the system LACP priority.
priority system-priority
The smaller the value is, the higher the system LACP priority
is. The end with a higher system LACP priority is the active
end. LACP selects the active interface and standby interface
based on configurations on the active end. If the system
LACP priorities are identical, select the one with a smaller
MAC address as the active end.
By default, it is configured to 32768.
3 Raisecom(config)#lacp timeout (Optional) configure the LACP timeout mode.
{ fast | slow }
4 Raisecom(config)#interface Enter aggregation group configuration mode.
port-channel channel-number
5 Raisecom(config-port- Configure the working mode of the LAG to static LACP
channelif)#mode lacp backup link aggregation.
[ backup ]

Raisecom Proprietary and Confidential

361
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Step Command Description

6 Raisecom(config-port- Configure the master interface of link aggregation.
channelif)#master-port
interface-type interface-
number
7 Raisecom(config-port- Configure the restoration mode and restoration delay of the
channelif)#restore-mode LAG.
{ non-revertive | revertive
[ restore-delay second ] } By default, the restoration mode is non-revertive.
8 Raisecom(config-port- Return to global configuration mode.
channelif)#exit
9 Raisecom(config)#interface Enter Layer 2 physical interface configuration mode.
interface-type interface-
number
10 Raisecom(config- Configure the interface as a switching interface or a Layer 3
port)#portswitch interface working in Layer 2 mode.
Raisecom(config-port)#mold l2

11 Raisecom(config-port)#port- Add Layer 2 physical interfaces to the LAG.

channel channel-number
12 Raisecom(config-port)#lacp (Optional) configure the LACP mode of member interfaces.
mode { active | passive }
By default, the LACP mode is active. LACP connection fails
if both ends of a link are in passive mode.
13 Raisecom(config-port)#lacp (Optional) configure the interface LACP priority. The
port-priority port-priority interface LACP priority affects the selection of the default
LACP interface. The smaller the number is, the higher the
priority is.
By default, it is 32768.
14 Raisecom(config-port)#exit Return to global configuration mode.

15.1.7 Checking configurations

No. Command Description
1 Raisecom#show Show local system LACP interface status, identifier, interface priority,
lacp internal management key, operation key, and interface status machine.
2 Raisecom#show Show neighbor LACP information, including the identifier, interface priority,
lacp neighbor device ID, Age, operation key ID, interface ID, and interface status machine.
3 Raisecom#show Show interface LACP statistics, including the total number of received
lacp statistics LACP packets, number of received and transmitted Marker packets, number
of received and transmitted Marker Response packets, and number of error
packets.
4 Raisecom#show Show global enabling status of local system LACP, device ID, LACP
lacp sys-id priority, and MAC address.

Raisecom Proprietary and Confidential

362
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

No. Command Description

5 Raisecom#show Show whether the current system is enabled with link aggregation, link
port-channel aggregation load-sharing mode, member interfaces and currently-active
member interfaces in all current LAGs.

Currently active member interfaces refers to interfaces in UP status

in the LAG.

15.2 Configuring interface backup

15.2.1 Preparing for configurations

Scenarios
In a dual-uplink networking scenario, you can realize redundancy backup of the primary/slave
link and fast switching of services through interface backup, thus improving service reliability.

Prerequisite
N/A

15.2.2 Configuring interface backup group

The iTN8800 supports interface backup based on interface or interface+VLAN. Choose one
from Step 3 and Step 4. By configuring optional parameters of the command, you can switch
services of the specified VLAN or all services on the interface when faults occur based on
interface backup.

No. Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)# port (Optional) create a backup interface based on interface
backup port-name port-number for the primary interface. Interface-based interface
[ vlanlist vlanlist primaryvlan backup supports switching or restoring services of the
vlanid ] specified VLAN or all services on the interface.
Raisecom(config-port)#exit
4 Raisecom(config-port)#port backup (Optional) create a backup interface based on
port-name port-number vlanlist interface+VLAN for the primary interface.
vlanlist separate
5 Raisecom(config-port)#port backup Configure the restoration mode and restoration delay of
restore-mode { non-revertive | interface backup.
revertive [ restore-delay delay-
time ] }
6 Raisecom(config-port)#port backup Configure the fault detection mode of interface backup.
fault-detect { cfm | bfd | lldp }

Raisecom Proprietary and Confidential

363
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

15.2.3 Checking configurations

No. Item Description
1 Raisecom#show port backup Show basic information about interface backup.
2 Raisecom#show port backup pb Show information about the interface backup group.
3 Raisecom#show port backup group Show interface status of the interface backup group.

15.3 Configuring ELPS

15.3.1 Preparing for configurations

Scenario
To make the Ethernet reliability up to Telecom-grade (network self-heal time less than 50ms),
you can deploy ELPS at Ethernet. ELPS is used to protect the Ethernet connection. It is an
end-to-end protection technology.
ELPS supports 1+1 and 1:1 protection switching modes. It is divided into unidirectional
protection switching and bidirectional protection switching based on the fact that whether
services of both ends are switched concurrently when the link fails. Unidirectional and
bidirectional protection switching are available in 1+1 protection switching mode only. 1:1
protection switching mode supports bidirectional protection switching only.
ELPS provides 3 modes to detect a fault.
 Detect faults based on physical interface status: learning link fault quickly and switching
services immediately, suitable for detecting the fault between neighbor devices.
 Detect faults based on CC: suitable for unidirectional detection or multi-device crossing
detection.
 Detect faults based on physical interface status and CC.

Prerequisite
 Connect interfaces and configure physical parameters for them. Make the physical layer
Up.
 Create a VLAN.
 Add the interface to the VLAN.
 Configure CFM detection and form a neighbor relationship (preparing for CC mode).

15.3.2 Creating protection pair

Step Command Description
1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

364
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Step Command Description

2 Raisecom(config)#ethernet Create the ELPS protection pair and configure the protection mode.
line-protection line-
number working interface- The protection group is in non-revertive mode if you configure the
type interface-number non-revertive parameter.
vlan-list protection  In revertive mode, when the working line recovers from a fault,
interface-type interface- traffic is switched from the protection line to the working line.
number vlan-list one-to-  In non-revertive mode, when the working line recovers from a

one [ non-revertive ] fault, traffic is not switched from the protection line to the
protocol-vlan vlan-id working line.
By default, there is no ELPS protection pair.
3 Raisecom(config)#ethernet (Optional) configure a name for the ELPS protection pair.
line-protection line-
number name string By default, there is no name for the ELPS protection pair.
4 Raisecom(config)#ethernet (Optional) configure the WTR timer. In revertive mode, when the
line-protection line- working line recovers from a fault, traffic is not switched to the
number wtr-timer wtr- working line unless the WTR timer times out.
timer
By default the WTR time value is 5min.

We recommend that WTR timer configurations on both

ends keep consistent. Otherwise, we cannot ensure 50ms
quick switching.
5 Raisecom(config)#ethernet (Optional) configure the HOLDOFF timer. After the HOLDOFF
line-protection line- timer is configured, when the working line fails, the system will
number hold-off-timer delay to process the fault. It means that services will be delayed to
hold-off-timer be switched to the protection line. This can prevent frequent
switching caused by flapping of the working line.
By default, the HOLDOFF timer value is 0.

If the HOLDOFF timer value is over great, it may influence

50ms switching performance. Therefore, we recommend
configuring the HOLDOFF timer value to 0.

15.3.3 Configuring ELPS fault detection modes

Fault detection modes of the working line and protection line can be different.
However, we recommend that fault detection mode configurations of the working line
and protection line keep consistent.
Step Command Description
1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

365
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Step Command Description

2 Raisecom(config)#ethernet Configure the fault detection mode of the working
line-protection line-number line/protection line to failure-detect physical-link.
{ working | protection }
failure-detect physical-link By default, the fault detection mode is failure-detect physical-
link.
Raisecom(config)#ethernet Configure the fault detection mode of the working
line-protection line-number line/protection line to failure-detect cc.
{ working | protection }
failure-detect cc [ md md- This fault detection mode cannot take effect unless you finish
name ] ma ma-name level level related configurations on CFM.
mep local-mep-id remote-mep-
id
Raisecom(config)#ethernet Configure the fault detection mode of the working
line-protection line-number line/protection line to failure-detect physical-link-or-cc.
{ working | protection }
failure-detect physical-link- In this mode, it believes that the link fails when a fault is
or-cc [ md md-name ] ma ma- detected on the physical link/CC.
name level level mep local- This fault detection mode cannot take effect unless you finish
mep-id remote-mep-id related configurations on CFM.

15.3.4 (Optional) configuring ELPS switching control

By default, traffic is automatically switched to the protection line when the working
line fails. Therefore, you need to configure ELPS switching control in some special
cases.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#e Lock protection switching. After this configuration, the traffic is not
thernet line- switched to the protection line even the working line fails.
protection line-
number lockout By default, the traffic is automatically switched to the protection line when
the working line fails.
3 Raisecom(config)#e Switch the traffic from the working line to the protection line forcedly.
thernet line-
protection line-
By default, the traffic is automatically switched to the protection line when
number force- the working line fails.
switch
4 Raisecom(config)#e Switch the traffic from the working line to the protection line manually. Its
thernet line- priority is lower than the one of forced switch and APS.
protection line-
number manual- By default, the traffic is automatically switched to the protection line when
switch the working line fails.

Raisecom Proprietary and Confidential

366
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Step Command Description

5 Raisecom(config)#e In non-revertive mode, switch the traffic from the protection line to the
thernet line- working line.
protection line-
number manual-
switch-to-work
After you execute a protection group command, if a fault/recovery
event occurs or if other protection group commands, both ends of
the protection group may select different lines. In this case, you
should use the clear ethernet line-protection end-to-end
command to delete the configured protection group command to
make both ends of the protection group select the identical line.

15.3.5 Checking configurations

No. Command Description
1 Raisecom(config)#show ethernet line- Show configurations of the protection pair.
protection [ line-number ]
2 Raisecom(config)#show ethernet line- Show statistics of the protection pair.
protection [ line-number ] statistics
3 Raisecom(config)#show ethernet line- Show APS information about the protection pair.
protection [ line-number ] aps

15.4 Configuring ERPS

15.4.1 Preparing for configurations

Scenario
With development of Ethernet to Telecom-grade network, voice and video multicast services
bring higher requirements on Ethernet redundant protection and fault-recovery time. The
fault-recovery time of current STP system is in second level that cannot meet requirements.
By defining different roles for nodes on a ring, ERPS can block a loopback to avoid broadcast
storm in normal condition. Therefore, the traffic can be quickly switched to the protection line
when working lines or nodes on the ring fail. This helps eliminate the loopback, perform
protection switching, and automatically recover from faults. In addition, the switching time is
shorter than 50ms.
The iTN8800 supports the single ring, intersecting ring, and tangent ring.
ERPS provides 2 modes to detect a fault:
 Detect faults based on physical interface status: learning link fault quickly and switching
services immediately, suitable for detecting the fault between neighbor devices.
 Detect faults based on CFM: suitable for unidirectional detection or multi-device
crossing detection.

Raisecom Proprietary and Confidential

367
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

 Detect faults based on physical interface and CFM.

Prerequisite
 Connect interfaces and configure physical parameters for them. Make the physical layer
Up.
 Create a VLAN.
 Add the interface to the VLAN.
 Create the management VLAN and VLANs of the working and protection interfaces.
 Configure CFM detection between devices and form a neighbor relationship (preparing
for CFM detection mode).

15.4.2 Creating ERPS protection ring

 Only one device on the protection ring can be set to the Ring Protection Link (RPL)
Owner and one device is configured to RPL Neighbor. Other devices are set to
ring forwarding nodes.
 In actual, the tangent ring consists of 2 independent single rings. Configurations
on the tangent ring are identical to the ones on the common single ring. The
intersecting ring consists of a master ring and a sub-ring. Configurations on the
master ring are identical to the ones on the common single ring.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ethernet Create a protection ring and set the node to the RPL Owner.
ring-protection ring-
number east interface-type By default, the protocol VLAN is VLAN 1 and blocked VLANs
interface-number west are VLANs 1–4094.
interface-type interface- If you configure the not-revertive mode, the protection ring is in
number [ node-type rpl- non-revertive mode. In revertive mode, the traffic is switched
owner rpl { east | from the protection line back to the working line when the
west } ] [ not-revertive ] working line recovers from a fault. However, in non-revertive
[ protocol-vlan vlan-id ] mode, the traffic is not switched.
[ block-vlanlist vlan- By default, the protection ring is in revertive mode.
list ]

The east and west interfaces cannot be the same one.

Raisecom(config)#ethernet Create a protection ring and set the node to the RPL Neighbour.
ring-protection ring-
number east interface-type By default, the protocol VLAN is VLAN 1 and blocked VLANs
interface-number west are VLANs 1–4094.
interface-type interface-
number [ node-type rpl-
neighbour rpl { east |
west } ] [ not-revertive ]
[ protocol-vlan vlan-id ]
[ block-vlanlist vlan-
list ]

Raisecom Proprietary and Confidential

368
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Step Command Description

Raisecom(config)#ethernet Create a protection line and set the node to the RPL forwarding
ring-protection ring- node.
number east interface-type
interface-number west By default, the protocol VLAN is VLAN 1 and blocked VLANs
interface-type interface- are VLANs 1–4094.
number [ not-revertive ]
[ protocol-vlan vlan-id ]
[ block-vlanlist vlan-
list ]
3 Raisecom(config)#ethernet (Optional) configure a name for the protection ring.
ring-protection ring-
number name string
4 Raisecom(config)#ethernet (Optional) configure the protocol version. Protocol versions of all
ring-protection ring- nodes on a ring should be consistent. Version 1 distinguishes
number version { 1 | 2 } rings through the protocol VLAN. Therefore, you should
configure different protocol VLANs for these rings. We
recommend configuring different protocol VLANs for these
rings, even you use version 2.
By default, version 1 is used.
5 Raisecom(config)#ethernet (Optional) after the ring Guard timer is configured, the failed
ring-protection ring- node does not process APS packets during a period. In a larger
number guard-time guard- ring network, after the failed node is recovered, the node may be
time in down status again because it receives fault notifications sent
by neighbor nodes. The ring Guard timer can resolve this
problem.
By default, the ring Guard timer is 500ms.
6 Raisecom(config)#ethernet (Optional) configure the ring WTR timer. In revertive mode,
ring-protection ring- when the working line recovers from a fault, traffic is not
number wtr-time wtr-time switched to the working line unless the WTR timer times out.
By default, the ring WTR time value is 5min.
7 Raisecom(config)#ethernet (Optional) configure the HOLDOFF timer. After the HOLDOFF
ring-protection ring- timer is configured, when the working line fails, the system will
number holdoff-time delay to report the fault. It means that services will be delayed to
holdoff-time be switched to the protection line. This can prevent frequent
switching caused by flapping of the working line.
By default, the HOLDOFF timer value is 0ms.

If the HOLDOFF timer value is over great, it may

influence 50ms switching performance. Therefore, we
recommend setting the HOLDOFF timer value to 0ms.

Raisecom Proprietary and Confidential

369
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

15.4.3 (Optional) creating ERPS protection sub-ring

 Only the intersecting ring consists of a master ring and a sub-ring. The master ring
is a complete ring and all its nodes should be configured with double interfaces.
The sub-interface is an incomplete ring and you must configure the single
interface on the intersecting node.
 Configurations on the master ring are identical to the ones on the single
ring/tangent ring.
 Configurations of non-intersecting nodes of the intersecting ring are identical to
the ones on the single ring/tangent ring.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ethernet Create the sub-ring on the intersecting node and set the
ring-protection ring-number intersecting node to the RPL Owner.
east interface-type interface-
number west interface-type If you configure the not-revertive mode, the protection ring
interface-number node-type is in non-revertive mode. In revertive mode, the traffic is
rpl-owner rpl { east | west } switched from the protection line back to the working line
[ not-revertive ] [ protocol- when the working line recovers from a fault. However, in
vlan vlan-id ] [ block- non-revertive mode, the traffic is not switched.
vlanlist vlan-list ] By default, the protection ring is in revertive mode.

The links between 2 intersecting nodes belong to the

master ring. Therefore, when you configure the sub-
ring on the intersecting node, you can only configure
the west or east interface.
By default, the protocol VLAN is VLAN 1 and blocked
VLANs are VLANs 1–4094.
Raisecom(config)#ethernet Create the sub-ring on the intersecting node and set the
ring-protection ring-number intersecting node to the RPL Neighbour.
east interface-type interface-
number west interface-type By default, the protocol VLAN is VLAN 1 and blocked
interface-number node-type VLANs are VLANs 1–4094.
rpl-neighbour rpl { east |
west } [ not-revertive ]
[ protocol-vlan vlan-id ]
[ block-vlanlist vlan-list ]
Raisecom(config)#ethernet Create the sub-ring on the intersecting node and set the
ring-protection ring-number intersecting node to the RPL forwarding node.
east interface-type interface-
number west interface-type By default, the protocol VLAN is VLAN 1 and blocked
interface-number [ not- VLANs are VLANs 1–4094.
revertive ] [ protocol-vlan
vlan-id ] [ block-vlanlist
vlan-list ]

Raisecom Proprietary and Confidential

370
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Step Command Description

3 Raisecom(config)#ethernet (Optional) configure the sub-ring virtual channel mode on
ring-protection ring-number the intersecting node. Because the link between intersecting
raps-vc { with | without } nodes belong to the master ring, the transmission mode of
protocol packets of the sub-ring is different from the one of
the master ring. It is divided into with and without modes.
By default, the sub-ring virtual channel adopts the with
mode.
Transmission modes on 2 intersecting nodes must be
identical.
4 Raisecom(config)#ethernet Enable the ring Propagate switch on the intersecting node.
ring-protection ring-number
propagate enable Because data of the sub-ring need to be forwarded through
the master ring, there is the MAC address table of the sub-
ring on the master ring. When the topology of the sub-ring
changes, the sub-ring should use the Propagate switch to
inform the master ring to refresh the MAC address table to
avoid traffic loss.
By default, the ring Propagate switch is disabled. We
recommend enabling ring Propagate switch.

15.4.4 Configuring ERPS fault detection modes

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ethernet Configure the ERPS fault detection mode to failure-detect physical-
ring-protection ring- link.
number { east | west }
failure-detect physical- By default, the ERPS fault detection mode is failure-detect
link physical-link.
Raisecom(config)#ethernet Configure the ERPS fault detection mode to failure-detect cc.
ring-protection ring-
number { east | west } This ERPL fault detection mode cannot take effect unless you
failure-detect cc [ md finish related configurations on CFM.
md-name ] ma ma-name If you configure the MD, the MA should be below the configured
level level mep local- md-level.
mep-id remote-mep-id
Raisecom(config)#ethernet Configure the ERPS fault detection mode to failure-detect physical-
ring-protection ring- link-or-cc.
number { east| west }
failure-detect physical- In this mode, it believes that the link fails when a fault is detected
link-or-cc [ md md-name ] on the physical link/CC.
ma ma-name level level This ERPL fault detection mode cannot take effect unless you
mep local-mep-id remote- finish related configurations on CFM.
mep-id If you configure the MD, the MA should be below the configured
md-level.

Raisecom Proprietary and Confidential

371
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

15.4.5 (Optional) configuring ERPS switching control

By default, traffic is automatically switched to the protection line when the working
line fails. Therefore, you need to configure ERPS switching control in some special
cases.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ethernet ring- Switch the traffic on the protection ring to the
protection ring-number force-switch west/east interface forcedly.
{ east | west }
3 Raisecom(config)#ethernet ring- Switch the traffic on the protection ring to the
protection ring-number manual-switch west/east interface manually. Its priority is lower
{ east | west } than the one of forced switch and APS.

15.4.6 Checking configurations

No. Command Description
1 Raisecom(config)#show ethernet ring- Show ERPS protection ring configurations.
protection
2 Raisecom(config)#show ethernet ring- Show ERPS protection ring status.
protection status
3 Raisecom(config)#show ethernet ring- Show ERPS protection ring statistics.
protection statistics

15.5 Configuring PW redundancy protection

15.5.1 Preparing for configurations

Scenario
PW redundancy protection is used on the networking scenario of CE connecting to 3 PEs
asymmetrically, multiple CEs connecting to multiple PEs, and CE accessing a networking
with MS-PW, etc.

Prerequisite
 The AC link between the dual-homed CE and PE supports E-Trunk or E-APS link
protection.
 PEs can access each other through IGP routing protocol.
 PW or MS-PW is created.

Raisecom Proprietary and Confidential

372
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

15.5.2 Configuring PW redundancy protection

Both Layer 3 physical interface and sub-interface support PW redundancy. When the Layer 3
physical interface or sub-interface at the AC end fails, it will trigger the PW redundancy
protection switching.

No. Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter Layer 3 physical interface configuration
type interface-number mode.
3 Raisecom(config-port)#mode l2 Configure the VPN mode on Layer 3 physical
interface to L2VPN.
By default, it is L3VPN.
4 Raisecom(config-port)#mpls l2vpn Configure L2VPN to support PW redundancy
redundancy { independent | master protection based on VPWS.
[ switch-mode { non-revertive |
revertive [ wtr-time wtr-time ] } ]
5 Raisecom(config-port)#mpls l2vpn Configure manually switching the service flow
switchover from the master PW to the slave PW.

15.5.3 Configuring service PW to be bound with management PW

The master/slave PW status detection in the PW redundancy protection group is based on
BFD. While conducting BFD for PW detection, each service PW is bound with BFD packets
and sessions, which increases the number of BFD sessions, thus wasting resources. By
configuring the management PW, you can create only one BFD session for PWs with the
same destination address, thus saving network resources.
Ensure that the management PW is created on the corresponding loopback interface before
configuring the service PW to be bound with the management PW.

No. Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter Layer 3 physical interface configuration
type interface-number mode.
3 Raisecom(config-port)#mode l2 Configure the VPN mode on Layer 3 physical
interface to be L2VPN.
By default, it is L3VPN.
4 Raisecom(config-port)#mpls l2vc Configure service PW to be bound with the
[ backup | bypass ] track admin-pw management PW.
loopback loopback-number

Raisecom Proprietary and Confidential

373
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

15.5.4 Checking configurations

No. Command Description
1 Raisecom#show mpls l2vc Show configurations of PW redundancy protection.

15.6 Configuring MPLS linear protection switching

15.6.1 Preparing for configurations

Scenario
MPLS-TP linear protection switching protects the primary link by providing a backup link.
Therefore, it provides end-to-end protection for LSP links between devices.

Prerequisite
Configure MPLS basic functions.

15.6.2 Configuring MPLS linear protection switching

Creating LSP 1:1 linear protection pair

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls line-protection aps-id { lsp Create a MPLS LSP linear
| transit-lsp } working lsp-ingress-name lsp- protection pair and configure the
egress-name protection lsp-ingress-name lsp- working line, protection line, and
egress-name [ ttl ttl ] one-to-one [ non- protection mode.
revertive ]

Creating PW 1:1 linear protection pair

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls line-protection aps-id { pw Create a MPLS PW linear
| ms-pw } working vc-id vc-id destination ip- protection pair and configure the
address protection vc-id vc-id destination ip- working line, protection line, and
address [ ttl ttl ] one-to-one [ non-revertive ] protection mode.

Raisecom Proprietary and Confidential

374
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Configuring basic properties of protection pair

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls line-protection (Optional) configure the name of the MPLS
aps-id name string linear protection pair.
3 Raisecom(config)#mpls line-protection Configure the Hold off timer.
aps-id hold-off-timer hold-off-timer
By default, it is 0.
4 Raisecom(config)#mpls line-protection Configure the WTR timer.
aps-id wtr-timer wtr-timer
By default, it is 5min.
5 Raisecom(config)#mpls line-protection Enable MPLS linear protection Trap.
trap enable
By default, it is enabled.

Configuring switching control commands

Select any step from steps 2–5 as required. Use the clear mpls line-protection command to
clear switching control commands of the protection pair immediately.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls (Optional) switch the traffic to the protection line forcedly.
line-protection aps-id
force-switch By default, the traffic is automatically switched to the protection
line, when the working line fails.
3 Raisecom(config)#mpls (Optional) configure MPLS linear protection switching lockout.
line-protection aps-id
lockout By default, the traffic is automatically switched to the protection
line, when the working line fails.
4 Raisecom(config)#mpls (Optional) switch the traffic to the protection line manually.
line-protection aps-id
manual-switch By default, the traffic is automatically switched to the protection
line, when the working line fails.
5 Raisecom(config)#mpls (Optional) switch the traffic back to the working line manually.
line-protection aps-id
manual-switch-to-work

15.6.3 Checking configurations

No. Command Description
1 Raisecom(config)#show mpls line-protection Show MPLS linear protection pair
[ aps-id ] config configurations.
2 Raisecom(config)#show mpls line-protection Show MPLS linear protection pair statistics.
[ aps-id ] statistic

Raisecom Proprietary and Confidential

375
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

No. Command Description

3 Raisecom(config)#show mpls line-protection Show MPLS linear protection pair status.
[ aps-id ] status

15.7 Configuring PW dual-homed protection switching

15.7.1 Preparing for configurations

Scenario
The PW dual-homed protection switching protects user-side access links and network-side
working PWs by cooperating with the working PW, protection PW, and bypass PW. By
bridging any two nodes among the service PW, DNI-PW, and access link, dual-homed
protection can prevent the problem of access-side faults triggering network-side faults, and
vice versa. For example, when the user-side access interface of the PE node fails, the working
node will bridge the working PW and bypass PW to a multi-section PW and the protection
node will bridge the bypass PW with the access link, transmitting the service flow on the
working PW, bypass PW, and access PW. Figure 15-1 shows the application.

Figure 15-1 PW dual-home protection application scenario

Prerequisite
Configure MPLS basic functions, create a LSP, and associate the Tunnel interface.

15.7.2 Configuration flows

 Figure 15-2 shows the flow for configuring PW dual-homed protection switching.

Raisecom Proprietary and Confidential

376
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Figure 15-2 Flow for configuring PW dual-homed protection switching

15.7.3 Configuring ICCP channel

In the PW dual-homed protection scenario, devices at the user side accesses the network
through two PE devices. The two PE devices should establish a ICCP tunnel between them for
carrying DNI-PW (namely, bypass PW).
Configure the MC-PW working node and the protection node as below.

Step Command Description

1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#iccp local-ip ip- Configure the local IP address of the ICCP device.
address The IP address is usually the one of the physical
interface or the LAG interface.
3 Raisecom(config)#iccp channel channel- Create an ICCP channel and enter ICCP
id configuration mode.
4 Raisecom(config-iccp)#member-ip ip- Configure the IP address of the ICCP peer device.
address

Raisecom Proprietary and Confidential

377
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Step Command Description

5 Raisecom(config-iccp)#iccp enable Enable ICCP tunnel.

15.7.4 Configuring PW
For configuring the working PW, see section 11.1.2 Configuring static L2VC or 11.1.3
Configuring dynamic L2VC.

Configuring working PW
For configuring the working PW, see section 11.1.2 Configuring static L2VC or 11.1.3
Configuring dynamic L2VC.
 Configure the working PW pointing to the PE B on PEA.
 Configure the working PW pointing to the PE A on PE B.

Configuring protection PW
 Configure the protection PW pointing to the PE C on PE A.
 Configure the DNI-PW pointing to the PE C on the PE B.
 Configure the DNI-PW pointing to the PE B on PE C.
 Configure the active PW which is pointing to PE A as the protection PW of the
protection node on PE C.

15.7.5 Configuring PW dual-homed protection group

Configuring PW 1:1 protection group

Configure PW 1:1 protection group on node PE A. For details, see section 15.6.2 Configuring
MPLS linear protection switching.

Configuring the working nodes of MC-PW protection group

When the network is normal, the working node bridges the working PW with the access link.
When the network fails, the working node bridges the working PW with the DNI-PW.
 Configure the PE B as below
Step Command Description
1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

378
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Step Command Description

2 Raisecom(config)#mpls line-protection aps- Create the MC-PW protection pair on the
id mc-pw working vc-id vc-id destination working node and associate it with the PW
ip-address [ ttl ttl ] of this working node.

When enabling MC-PW protection

group on the SPE device, you must
choose the TTL value and should
configure it properly. Otherwise,
switching will fail.
3 Raisecom(config)#mpls line-protection aps- Associate the MC-PW protection group with
id binding-channel channel-id the ICCP tunnel on the working node.

Configuring protection node of MC-PW protection group

When the network fails, the protection node bridges DNI-PW and the access link.
 Configure the PE C as below.
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls line-protection aps- Configure the MC-PW protection group on
id mc-pw working vc-id vc-id destination the working node and associate it with the
ip-address [ ttl ttl ] protection PW of the working node.

When enabling MC-PW protection

group on the SPE device, you must
choose the TTL value and should
configure it properly. Otherwise,
switching will fail.
3 Raisecom(config)#mpls line-protection aps- Associate the MC-PW protection group with
id binding-channel channel-id the ICCP tunnel on the working node.

15.7.6 Configuring PW dual-homed protection switching attributes

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#mpls line- (Optional) forcedly switch services to the protection link.
protection aps-id force-switch
By default, when the working link fails, it will
automatically switch the services to the protection link.

Raisecom Proprietary and Confidential

379
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Step Command Description

3 Raisecom(config)#mpls line- (Optional) lock link protection switching.
protection aps-id lockout
By default, when the working link fails, it will
automatically switch the services to the protection link.
4 Raisecom(config)#mpls line- (Optional) switch services to the protection link manually.
protection aps-id manual-switch
By default, when the working link fails, it will
automatically switch the services to the protection link.
5 Raisecom(config)#mpls line- (Optional) configure the Hold-off timer.
protection aps-id hold-off-timer
hold-off-timer By default, the value is 0.
6 Raisecom(config)#mpls line- (Optional) configure the WTR timer.
protection aps-id wtr-timer wtr-
timer By default, the value is 5 min.
7 Raisecom(config)#mpls line- (Optional) enable MPLS linear protection to report Trap.
protection trap enable
By default, it is enabled.

15.8 Configuring VPN FRR

15.8.1 Preparing for configurations

Scenario
VPN FRR implements fast convergence on the services when the PE fails as shown in Figure
15-3, implementing MPLS L3VPN end-to-end protection.
MPLS-TE-FRR is the most commonly used technique to implement fast switching. Through
it, you can establish a tunnel between two PE devices and preconfigure a backup LSP for the
master LSP. When the device detects that the master LSP is unavailable (node fault or link
fault), it will switch the traffic to the backup LSP, thus implementing fast service switching.
However, MPLS-TE can only solve the problem of node faults and link faults instead of the
faults of the starting PE and the ending PE and it only recovers services through route
convergence and LSP convergence.
VPN FRR implements fast route switching based on the VPN route. You can preconfigure the
forwarding entry which points to the master PE and backup PE on the remote PE and combine
with the PE fault fast detection, to solve the problem of long convergence time in the CE dual-
homed MPLS VPN. Under the condition of PE faults, the end-to-end service recovery time is
no longer than 1s.

Raisecom Proprietary and Confidential

380
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Figure 15-3 CE dual-homed networking

Prerequisite
 PE devices are configured with OSPF and the backbone network is interconnected.
 PE devices are configured with MPLS basic functions, and a Tunnel is created.
 PE devices are configured with the VPN instance and the CE devices are accessed to the
PE devices at both ends respectively.
 PE devices has established EBGP peers with the CE devices and introduced VPN routes.
MP-IBGP peers are established among PE devices.

15.8.2 Configuring VPN FRR

Configuring route policy

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ip prefix-list vpn-frr- Create an IP prefix list or add an end node to
name [ seq seq-number ] { deny | permit } it.
any
Raisecom(config)#ip prefix-list vpn-frr-
If the prefix list ID seq-number is not
name [ seq seq-number ] { deny | permit }
configured, the system will automatically
ip-address/mask [ ge min-length ] [ le
generate one with a step length of 5.
max-length ]
3 Raisecom(config)#route-map vpn-frr-name Create a route mapping table and enter route
{ permit | deny } number mapping configuration mode.
4 Raisecom(config-route-map)#match ip next- Configure the match sentence to match the
hop prefix-list vpn-frr-name next hop based on the IP prefix list.

You can select other types of match

sentences. For details, see section 9.3
Configuring routing policy.

Raisecom Proprietary and Confidential

381
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

15.9 Configuring HA hot backup

15.9.1 Preparing for configurations

Scenario
High Availability (HA), including hot backup, batch backup, and realtime backup, is used to
provide high reliability of the system. Devices, which support HA hot backup should be
equipped with 2 cards. The master card works in Master mode and the slave card works in
Slave mode. Whenever the master card fails, the slave card will be activated and continue to
work to ensure that the system can run properly.

Prerequisite
The iTN8800 is inserted with the active and standby MCCs.

15.9.2 Configuring HA switching

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#ha switchover Switch the active and standby MCCs manually.

15.9.3 Checking configurations

No. Command Description
1 Raisecom(config)#show ha state Show HA hot backup status.

15.10 Configuring VRRP

15.10.1 Preparing for configurations

Scenario
In general, we configure a default route to the breakout gateway for all devices in a LAN.
Therefore, these devices can communicate with the external network. If the gateway fails,
devices in the LAN fail to communicate with the external network.
The VRRP technology combines multiple routers to form a backup group. By configuring a
virtual IP address for the backup group, you can set the default gateway to the virtual IP
address of the backup group to make devices in the LAN communicate with the external
network.
VRRP helps improve network reliability. It facilitates avoiding network interruption caused
by failure of s single link and prevents changing routing configurations because of link failure.
Raisecom Proprietary and Confidential
382
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Prerequisite
N/A

15.10.2 Configuration procedure

Figure 15-4 shows the VRRP configuration procedure.

Figure 15-4 VRRP configuration procedure

15.10.3 Configuring VRRP backup group

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface Enter interface configuration mode.
interface-type interface-number
3 Raisecom(config-port)#vrrp group- Create a VRRP backup group and configure a virtual IP
id ip ip-address address for the VRRP backup group. The virtual IP
address must be at the same network segment with the
interface IP address.
4 Raisecom(config-port)#vrrp group- (Optional) configure descriptions of the VRRP backup
id description description group.

Raisecom Proprietary and Confidential

383
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Step Command Description

5 Raisecom(config-port)#vrrp group- (Optional) enable the preemption mode of the VRRP
id preempt [ delay-time second ] backup group.
By default, the newly-created VRRP backup group is in
preemption mode. The preemption delay is 0s.
6 Raisecom(config-port)#vrrp group- Configure the priority of the device in the VRRP backup
id priority priority group.
By default, the priority of the newly-created VRRP
backup group is 100.
7 Raisecom(config-port)#vrrp group- (Optional) configure the interval for the VRRP backup
id timers advertise-interval group sending the notification packet.
seconds
By default, it is 1s.
8 Raisecom(config-port)#vrrp group- Enable VRRP.
id enable
By default, it is enabled.

15.10.4 (Optional) configuring ping function of VRRP virtual IP

address
Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#vrrp Enable pinging the virtual IP address of the VRRP backup group.
ping
By default, pinging the virtual IP address of the newly-created
VRRP backup group is enabled.

15.10.5 Configuring VRRP monitoring interface

Step Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface-type Enter interface configuration
interface-number mode.
3 Raisecom(config-port)#vrrp group-id track Configure VRRP monitoring
interface-type interface-number [ reduce priority ] interface.

15.10.6 Configuring VRRP fast switching

Step Command Description
1 Raisecom#config Enter global configuration mode.

Raisecom Proprietary and Confidential

384
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Step Command Description

2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#vrrp group-id Configure the VRRP backup group to monitor
track bfd-session session-id [ increased the BFD session to realize fast switching.
priority | reduce priority ]

15.10.7 Checking configurations

No. Command Description
1 Raisecom#show vrrp group-id Show VRRP backup group configurations.
2 Raisecom#show vrrp interface interface-type Show VRRP backup group configurations
interface-number [ group-id ] on the interface.
3 Raisecom#show vrrp interface interface-type Show VRRP backup group statistics on the
interface-number [ group-id ] statistics interface.
4 Raisecom#show vrrp [ group-id ] track Show monitoring information about the
VRRP backup group.

15.11 Configuring PRBS test

15.11.1 Preparing for configurations

Scenario
The Pseudo-Random Bit Sequence (PRBS) test module is for testing whether the end-to-end
CES runs normally. It can also test the transmission error rate of the high-speed serial channel
by sending PRBS codes.

Prerequisite
When testing the network-side service performance, you should configure CES on the
interface.

15.11.2 Configuring PRBS

No. Command Description
1 Raisecom#config Enter global configuration mode.
2 Raisecom(config)#interface interface- Enter interface configuration mode.
type interface-number
3 Raisecom(config-port)#prbs { uni | Enable PRBS.
nni } duration { sec | min | hour }
number

Raisecom Proprietary and Confidential

385
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

15.11.3 Checking configurations

No. Command Description
1 Raisecom(config-port)#show prbs test result Show PRBS test results.

15.12 Maintenance
Command Description
Raisecom(config)#clear lacp statistics Clear LACP statistics.
[ interface-type interface-number ]
Raisecom(config)#clear mlacp mlacp-group Clear statistics of received and transmitted packets
[ icg-id ] statistics of the chassis group.
Raisecom(config)#clear ethernet line- Clear statistics of the protection group.
protection statistics
Raisecom(config)#clear ethernet line- Clear end-to-end switching control commands.
protection aps-id end-to-end command
Raisecom(config)#clear ethernet ring- Clear statistics of the protection ring, including the
protection ring-number statistics number of transmitted APS packets, the number of
received APS packets, the last switching time, and
the fault detection mode.
Raisecom(config)#clear ethernet ring- Clear switching control commands of the
protection ring-number command protection ring, including the force-switch and
manual-switch commands.

Raisecom(config)#clear mpls line-protection Clear switching control commands of the MPLS

aps-id command linear protection pair.

Raisecom(config)#clear mpls line-protection Clear statistics of the MPLS linear protection pair.
[ aps-id ] statistics

Raisecom(config)#clear iccp channel Clear statistics of ICC received and transmitted

[ channel-id ] statistics packets.

Raisecom(config)#clear vrrp statistics Clear packet statistics of all VRRP backup groups.

15.13 Configuration examples

15.13.1 Example for configuring manual link aggregation

Networking requirements
As shown in Figure 15-5, to improve the reliability of the link between iTN A and iTN B, you
can configure manual link aggregation on iTN A and iTN B. Add GE 1/4/1 and GE 1/4/2 to a

Raisecom Proprietary and Confidential

386
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

LAG to form a single logical interface. The LAG performs load-sharing according to the
source MAC address.

Figure 15-5 Configuring manual link aggregation

Configuration steps
Step 1 Create a manual LAG.
 Configure iTN A.

Raisecom#hostname iTNA
iTNA#config
iTNA(config)#interface port-channel 1
iTNA(config-port-channel1)#mode manual
iTNA(config-port-channel1)#exit

 Configure iTN B.

Raisecom#hostname iTNB
iTNB#config
iTNB(config)#interface port-channel 1
iTNB(config-port-channel1)#mode manual
iTNB(config-port-channel1)#exit

Step 2 Add interfaces to the LAG.

 Configure iTN A.

iTNA(config)#interface gigaethernet1/4/1
iTNA(config-gigaethernet1/4/1)#port channel 1
iTNA(config-gigaethernet1/4/1)#exit
iTNA(config)#interface gigaethernet1/4/2
iTNA(config-gigaethernet1/4/2)#port channel 1
iTNA(config-gigaethernet1/4/2)#exit

Raisecom Proprietary and Confidential

387
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

 Configure iTN B.

iTNB(config)#interface gigaethernet1/4/1
iTNB(config-gigaethernet1/4/1)#port channel 1
iTNB(config-gigaethernet1/4/1)#exit
iTNB(config)#interface gigaethernet1/4/2
iTNB(config-gigaethernet1/4/2)#port channel 1
iTNB(config-gigaethernet1/4/2)#exit

Step 3 Configure the load-sharing mode of the LAG.

 Configure iTN A.

iTNA(config)#interface port-channel 1
iTNA(config-port-channel1)#load-sharing mode src-mac

 Configure iTN B.

iTNB(config)#interface port-channel 1
iTNB(config-port-channel1)#load-sharing mode src-mac

Checking results
Use the show lacp internal command to show global configurations on manual link
aggregation.

iTNA#show lacp internal

Flags:
S - Device is requesting Slow LACPDUs F - Device is requesting Fast
LACPDUs
A - Device in Active mode P - Device in Passive mode MP - MLACP Peer
Port
Interface State Flag Port-Priority Admin-key Oper-key Port-State
-------------------------------------------------------------------
gigaethernet1/4/1 Active SA 32768 1 1 0x0
gigaethernet1/4/2 Standby SA 32768 1 1 0x0

Raisecom Proprietary and Confidential

388
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

15.13.2 Example for configuring static LACP link aggregation

Networking requirements
As shown in Figure 15-6, to improve the reliability of the link between iTN A and iTN B, you
can configure static LACP link aggregation on iTN A and iTN B. Add GE 1/4/1 and GE 1/4/2
to a LAG. The GE 1/4/1 works as the primary line and the GE 1/4/2 works as the backup line.

Figure 15-6 Configuring LACP link aggregation

Configuration steps
Step 1 Configure the static LACP LAG on iTN A and configure iTN A as the active end.

Raisecom#hostname iTNA
iTNA#config
iTNA(config)#lacp system-priority 1000
iTNA(config)#interface port-channel 1
iTNA(config-port-channel1)#mode lacp
iTNA(config-port-channel1)#exit
iTNA(config)#interface gigaethernet 1/4/1
iTNA(config-gigaethernet1/4/1)#port-channel 1
iTNA(config-gigaethernet1/4/1)#lacp port-priority 1000
iTNA(config-gigaethernet1/4/1)#exit
iTNA(config)#interface gigaethernet 1/4/2
iTNA(config-gigaethernet1/4/2)#port-channel 1
iTNA(config-gigaethernet1/4/2)#exit

Step 2 Configure the static LACP LAG on iTN B.

Raisecom#hostname iTNB
iTNB#config
iTNB(config)#interface port-channel 1
iTNB(config-port-channel1)#mode lacp
iTNB(config-port-channel1)#exit
iTNB(config)#interface gigaethernet 1/4/1

Raisecom Proprietary and Confidential

389
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

iTNB(config-gigaethernet1/4/1)#port-channel 1
iTNB(config-gigaethernet1/4/1)#exit
iTNB(config)#interface gigaethernet 1/4/2
iTNB(config-gigaethernet1/4/2)#port-channel 1
iTNB(config-gigaethernet1/4/2)#exit

Checking results
Use the show lacp internal command on iTN A to show LACP interface status, identifier,
interface priority, administration key, operation key, and interface state machine of the local
system.

iTNA(config)#show lacp internal

Flags:
S - Device is requesting Slow LACPDUs F - Device is requesting Fast
LACPDUs
A - Device in Active mode P - Device in Passive mode MP - MLACP Peer
Port
Interface State Flag Port-Priority Admin-key Oper-key Port-State
-------------------------------------------------------------------------
gigaethernet1/4/1 Active SA 32768 1 1 0x45
gigaethernet1/4/2 Standby SA 32768 1 1 0x45

Use the show lacp neighbor command on iTN A to show LACP interface status, identifier,
interface priority, administration key, operation key, and interface state machine of the remote
system.

15.13.3 Example for configuring PW dual-homed protection

switching

Networking requirements
As shown in Figure 15-7, PW dual-homing protection is applied to the mobile backhaul
network. There is a working PW between PE A and PE B, a protection PW between PE A and
PE C, and a bridge PW (bypass PW) between PE B and PE C. Service data will be switched
to the protection PW for transmission when the working PW fails to work. When an AC at the
RNC side fails, the bypass is bridged with the working/protection PW to form a MS-PW. The
MS-PW provides PW dual-homed protection switching to protect service data. The
configuration parameters are shown in Table 15-1.

Raisecom Proprietary and Confidential

390
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Figure 15-7 Configuring PW dual-homed protection switching

Table 15-1 Configuration parameters

Device LSR-ID Interface IP address PW ID

PE A 132.0.0.1 gigaethernet 1/1/1 10.0.0.10/8 Working PW: 1

gigaethernet 1/1/2 30.0.0.10/8 Protection PW: 3
loopback 1 132.0.0.1/24 –
PE B 132.0.0.2 gigaethernet 1/1/1 10.0.0.20/8 Working PW: 1
gigaethernet 1/1/2 20.0.0.20/8 DNI-PW: 2
loopback 1 132.0.0.2/24 –
PE C 132.0.0.3 gigaethernet 1/1/1 30.0.0.30/8 Protection PW: 3
gigaethernet 1/1/2 20.0.0.30/8 DNI-PW: 2
loopback 1 132.0.0.3/24 –

Configuration steps
Step 1 Configure the IP address of the Layer 3 physical interface on PE A, PE B, and PE C.
PE A

PEA#config
PEA(config)#interface gigaethernet 1/1/1
PEA(config-gigaethernet1/1/1)#ip address 10.0.0.10 255.0.0.0
PEA(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
PEA(config-gigaethernet1/1/2)#ip address 30.0.0.10 255.0.0.0
PEA(config-gigaethernet1/1/2)#interface loopback 1
PEA(config-loopback1)#ip address 132.0.0.1 255.255.255.0
PEA(config-loopback1)#exit

Raisecom Proprietary and Confidential

391
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

PE B

PEB(config)#interface gigaethernet 1/1/1

PEB(config-gigaethernet1/1/1)#ip address 10.0.0.20 255.0.0.0
PEB(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
PEB(config-gigaethernet1/1/2)#ip address 20.0.0.20 255.0.0.0
PEB(config-gigaethernet1/1/2)#interface loopback 1
PEB(config-loopback1)#ip address 132.0.0.2 255.255.255.0
PEB(config-loopback1)#exit

PE C

PEC(config)#interface gigaethernet 1/1/1

PEC(config-gigaethernet1/1/1)#ip address 30.0.0.30 255.0.0.0
gigaethernet1/1/1PEC(config-gigaethernet1/1/1)#interface gigaethernet
1/1/2
PEC(config-gigaethernet1/1/2)#ip address 20.0.0.30 255.0.0.0
PEc(config-gigaethernet1/1/2)#interface loopback 1
PEc(config-loopback1)#ip address 132.0.0.3 255.255.255.0
PEC(config-loopback1)#exit

Step 2 Configure the MPLS basic attributes of PE A, PE B, and PE C.

PE A

PEA(config)#mpls lsr-id 132.0.0.1

PEA(config)#mpls enable

PE B

PEB(config)#mpls lsr-id 132.0.0.2

PEB(config)#mpls enable

PE C

PEC(config)#mpls lsr-id 132.0.0.3

PEC(config)#mpls enable

Step 3 Configuring ICCP for PE B and PE C.

PE B

Raisecom Proprietary and Confidential

392
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

PEB(config)#iccp local-ip 20.0.0.20

PEB(config)#iccp channel 1
PEB(config-iccp)#member-ip 20.0.0.30
PEB(config-iccp)#iccp enable
PEB(config-iccp)#exit

PE C

PEC(config)#iccp local-ip 20.0.0.30

PEC(config)#iccp channel 1
PEC(config-iccp)#member-ip 20.0.0.20
PEC(config-iccp)#iccp enable
PEC(config-iccp)#exit

Step 4 Configure Tunnel for PE A, PE B, and PE C.

PE A

PEA(config)#interface tunnel 1/1/1

PEA(config-tunnel1/1/1)#destination 10.0.0.20
PEA(config-tunnel1/1/1)#mpls tunnel-id 1
PEA(config-tunnel1/1/1)#mpls te commit
PEA(config-tunnel1/1/1)#interface tunnel 1/1/2
PEA(config-tunnel1/1/2)#destination 30.0.0.30
PEA(config-tunnel1/1/2)#mpls tunnel-id 3
PEA(config-tunnel1/1/2)#mpls te commit
PEA(config-tunnel1/1/2)#exit

PE B

PEB(config)#interface tunnel 1/1/1

PEB(config-tunnel1/1/1)#destination 10.0.0.10
PEB(config-tunnel1/1/1)#mpls tunnel-id 1
PEB(config-tunnel1/1/1)#mpls te commit
PEB(config-tunnel1/1/1)#interface tunnel 1/1/2
PEB(config-tunnel1/1/2)#destination 20.0.0.30
PEB(config-tunnel1/1/2)#mpls tunnel-id 2
PEB(config-tunnel1/1/2)#mpls te commit
PEB(config-tunnel1/1/2)#exit

PE C

PEC(config)#interface tunnel 1/1/1

PEC(config-tunnel1/1/1)#destination 20.0.0.20
PEC(config-tunnel1/1/1)#mpls tunnel-id 1

Raisecom Proprietary and Confidential

393
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

PEC(config-tunnel1/1/1)#mpls te commit
PEC(config-tunnel1/1/1)#interface tunnel 1/1/2
PEC(config-tunnel1/1/2)#destination 30.0.0.10
PEC(config-tunnel1/1/2)#mpls tunnel-id 3
PEC(config-tunnel1/1/2)#mpls te commit
PEC(config-tunnel1/1/2)#exit

Step 5 Configure LSP for PE A, PE B, and PE C.

PE A

PEA(config)#mpls static-lsp ingress lspab 10.0.0.20 255.255.255.0 nexthop

10.0.0.20 out-label 101 lsr-id 132.0.0.2 tunnel-id 1
PEA(config)#mpls static-lsp egress lspba in-label 100 lsr-id 132.0.0.2
tunnel-id 1
PEA(config)#mpls static-lsp ingress lspac 30.0.0.30 255.255.255.0 nexthop
30.0.0.30 out-label 201 lsr-id 132.0.0.3 tunnel-id 3
PEA(config)#mpls static-lsp egress lspca in-label 200 lsr-id 132.0.0.2
tunnel-id 3

PE B

PEB(config)#mpls static-lsp ingress lspba 10.0.0.10 255.255.255.0 nexthop

10.0.0.10 out-label 100 lsr-id 132.0.0.1 tunnel-id 1
PEB(config)#mpls static-lsp egress lspab in-label 101 lsr-id 132.0.0.1
tunnel-id 1
PEB(config)#mpls static-lsp ingress lspbc 20.0.0.30 255.255.255.0 nexthop
20.0.0.30 out-label 301 lsr-id 132.0.0.3 tunnel-id 2
PEB(config)#mpls static-lsp egress lspcb in-label 300 lsr-id 132.0.0.3
tunnel-id 2

PE C
PEC(config)#mpls static-lsp ingress lspca 30.0.0.10 255.255.255.0 nexthop
30.0.0.10 out-label 200 lsr-id 132.0.0.1 tunnel-id 3
PEC(config)#mpls static-lsp egress lspac in-label 201 lsr-id 132.0.0.1
tunnel-id 3
PEC(config)#mpls static-lsp ingress lspcb 20.0.0.20 255.255.255.0 nexthop
20.0.0.20 out-label 300 lsr-id 132.0.0.2 tunnel-id 2
PEC(config)#mpls static-lsp egress lspbc in-label 301 lsr-id 132.0.0.2
tunnel-id 2

Step 6 Configuring PW for PE A, PE B, and PE C.

PE A

PEA(config)#interface gigaethernet 1/2/1

PEA(config-gigaethernet1/2/1)#mode l2

Raisecom Proprietary and Confidential

394
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

PEA(config-gigaethernet1/2/1)#mpls static-l2vc destination 20.0.0.20 raw

vc-id 1 in-label 16 out-label 16 tunnel 1/1/1
PEA(config-gigaethernet1/2/1)#mpls static-l2vc destination 30.0.0.30 vc-
id 3 in-label 18 out-label 18 tunnel 1/1/2 backup

PE B

PEB(config)#interface gigaethernet 1/2/1

PEB(config-gigaethernet1/2/1)#mode l2
PEB(config-gigaethernet1/2/1)#mpls static-l2vc destination 10.0.0.10 raw
vc-id 1 in-label 16 out-label 16 tunnel 1/1/1
PEB(config-gigaethernet1/2/1)#mpls static-l2vc destination 30.0.0.30 vc-
id 2 in-label 17 out-label 17 tunnel 1/1/2 bypass
PEB(config-gigaethernet1/2/1)#exit

PE C

PEC(config)#interface gigaethernet 1/2/1

PEC(config-gigaethernet1/2/1)#mode l2
PEC(config-gigaethernet1/2/1)#mpls static-l2vc destination 10.0.0.10 raw
vc-id 3 in-label 18 out-label 18 tunnel 1/1/2
PEC(config-gigaethernet1/2/1)#mpls static-l2vc destination 20.0.0.20 vc-
id 2 in-label 17 out-label 17 tunnel 1/1/1 bypass
PEC(config-gigaethernet1/2/1)#exit

Step 7 Configure the working node and protection node of PW 1:1 protection group and MC-PW
protection group.

PE A

PEA(config)#mpls line-protection 1 pw working vc-id 1 destination

20.0.0.20 protection vc-id 2 destination 30.0.0.30 ttl 1 one-to-one

PE B

PEB(config)#mpls line-protection 2 mc-pw working vc-id 1 destination

10.0.0.10 ttl 1

PE C

PEC(config)#mpls line-protection 2 mc-pw protection vc-id 3 destination

10.0.0.10 ttl 1

Raisecom Proprietary and Confidential

395
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Step 8 Associate the MC-PW protection pair of PE B and PE C to the ICCP Tunnel respectively.
PE B

PEB(config)#mpls line-protection 2 binding-channel 1

PE C

PEC(config)#mpls line-protection 2 binding-channel 1

Checking results
Use the show iccp channel command to show ICCP configurations of PE B.

Iccp local ip address : 20.0.0.20

inter-chassis communication channel number : 1
member ip address : 20.0.0.30
binding number : 0
state : enable
machine state : iccpBegin

Use the show mpls line-protection config command to show protection switching
configurations of PE A, PE B, and PE C.

PE A

PEA(config)#show mpls line-protection config

Trap State:Enable

Id:1
Name:--
Working Entity Information:
Vc-Id:1 destination:20.0.0.20
State/LCK/M: Active/N/N
Link State:failure
Protection Entity Information:
Vc-Id:2 destination:30.0.0.30
State/F/M: Standby/N/N
Link State:failure
Wtr(m):5
Holdoff(100ms):0

PE B

Raisecom Proprietary and Confidential

396
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

PEB(config)#show mpls line-protection config

Trap State:Enable
Id:1
Name:--
Working Entity Information:
Vc-Id:10 destination:10.0.0.10
State/LCK/M: Active/N/N
Link State:failure
Protection Entity Information:
Vc-Id:-- destination:--
State/F/M: --/N/N
Link State:failure
Wtr(m):5
Holdoff(100ms):0
Icc:0
Icc State:non-operational

PE C

PEC(config)#show mpls line-protection config

Trap State:Enable
Id:1
Name:--
Working Entity Information:
Vc-Id:10 destination:10.0.0.10
State/LCK/M: Active/N/N
Link State:failure
Protection Entity Information:
Vc-Id:-- destination:--
State/F/M: --/N/N
Link State:failure
Wtr(m):5
Holdoff(100ms):0
Icc:0
Icc State:non-operational

15.13.4 Examples for configuring PW redundancy protection

Networking requirements
As shown in Figure 15-8, CE 1 services are transmitted through PE 1 and PE 2 respectively.
PE 1 and PE 2 are connected to the PE 4 which locates at the core layer through the static PW
carried by the static Tunnel. The services of the peer CE 2 are transmitted through PE 3 which
is also connected to the core-layer PE 5 through the static PW. The PE devices at the core
layer are enabled with the dynamic PW which is carried by the LDP LSP dynamically. The
core-layer devices include PE 4, PE 5, PE 6, and PE 7. The devices at the access side are all
configured with two static PWs (master/slave) and enabled with PW redundancy protection.
To implement service transmission and protection at the core layer, you can enable static-to-
dynamic PW conversion on PE 4 and PE 5 and enable dynamic PW conversion on PE 6 and
PE 7.

Raisecom Proprietary and Confidential

397
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Figure 15-8 CE accessing multi-section PWs asymmetrically

Configuration strategy
 Configure MPLS basic functions on the PE devices, configure MPLS LDP, and establish
Tunnels between PE devices.
 Enable OSPF on PE 4, PE 5, PE 6, and PE 7 and ensure that routes are reachable
between PE devices.
 Configure static routes among PE 1, PE 2, and PE 4 and configure static routes between
PE 3 and PE 5.
 Configure the static-to-dynamic PW conversion on PE 4 and configure static-to-dynamic
PW conversion on PE 5.
 Configure static PWs among PE 1, PE 2, and PE 4 and configure static PWs on PE 3 and
PE 5.
 Configure PW redundancy.

Data preparation
Figure 15-9 shows the data preparation.

Figure 15-9 Data preparation

Device LSR-ID Interface IP address VC ID

PE 1 1.1.1.1 gigaethernet 1/2/1.100 – Master: 101
Slave: 201
gigaethernet 1/1/1 20.0.0.1/24 –
loopback 2 1.1.1.1/24 –
PE 2 2.2.2.2 gigaethernet 1/2/1.100 – Master: 301
Slave: 401
gigaethernet 1/1/1 40.0.0.1/24 –

Raisecom Proprietary and Confidential

398
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

Device LSR-ID Interface IP address VC ID

loopback 2 2.2.2.2/24 –
PE 4 4.4.4.4 gigaethernet 1/5/1 20.0.0.2/24 –
gigaethernet 1/5/2 40.0.0.2/24 –
gigaethernet 1/5/3 60.0.0.1/24 –
gigaethernet 1/5/4 70.0.0.1/24 –
loopback 2 4.4.4.4/24 –
PE 6 6.6.6.6 gigaethernet 1/1/1 60.0.0.2/24 –
gigaethernet 1/1/2 30.0.0.1/24 –
loopback 1 6.6.6.6/24 –
PE 7 7.7.7.7 gigaethernet 1/1/1 70.0.0.2/24 –
gigaethernet 1/1/2 50.0.0.1/24 –
loopback 2 7.7.7.7/24 –
PE 5 5.5.5.5 gigaethernet 1/5/1 80.0.0.1/24 –
gigaethernet 1/5/3 30.0.0.2/24 –
gigaethernet 1/5/4 50.0.0.2/24 –
loopback 2 5.5.5.5/24 –
PE 3 3.3.3.3 gigaethernet 1/1/1 80.0.0.2/24 –
gigaethernet 1/1/2 90.0.0.2/24 –
gigaethernet 1/2/1.100 – Master: 501
Slave: 601
gigaethernet 1/2/1.200 – Master: 701
Slave: 801
loopback 2 3.3.3.3/24 –

Configuration steps
Step 1 Enable MPLS and LDP globally.
 Configure PE 1.

PE1(config)#mpls lsr-id 1.1.1.1

PE1(config)#mpls enable
PE1(config)#mpls ldp

Raisecom Proprietary and Confidential

399
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

 Configure PE 2, PE 3, PE 4, PE 5, PE 6, and PE 7. The methods are the same as

configuring PE 1.
Step 2 Configure the IP address of the network-side interfaces and enable LDP.
 Configure PE 1.

PE1(config)#interface gigaethernet 1/1/1

PE1(config-gigaethernet1/1/1)#ip address 20.0.0.1 255.255.255.0
PE1(config-gigaethernet1/1/1)#mpls ldp
PE1(config-gigaethernet1/1/1)#exit

 Configure PE 6.

PE6(config)#interface gigaethernet 1/1/1

PE6(config-gigaethernet1/1/1)#ip address 60.0.0.2 255.255.255.0
PE6(config-gigaethernet1/1/1)#mpls ldp
PE6(config-gigaethernet1/1/1)#interface gigaethernet 1/1/2
PE6(config-gigaethernet1/1/2)#ip address 30.0.0.1 255.255.255.0
PE6(config-gigaethernet1/1/2)#mpls ldp
PE6(config-gigaethernet1/1/2)#exit

 Configure PE 2, PE 3, PE 4, PE 5, and PE 7. The methods are the same as configuring

PE 1 or PE 6.
Step 3 Configure the IP address of the Loopback interface and configure OSPF.
 Configure PE 1.

PE1(config)#interface loopback 2
PE1(config-loopback2)#ip address 1.1.1.1 255.255.255.0
PE1(config-loopback2)#exit

 Configure PE 2.

PE2(config)#interface loopback 2
PE2(config-loopback2)#ip address 2.2.2.2 255.255.255.0
PE2(config-loopback2)#exit

 Configure PE 4.

PE4(config)#interface loopback 2
PE4(config-loopback2)#ip address 4.4.4.4 255.255.255.0
PE4(config-loopback2)#exit
PE4(config)#router id 4.4.4.4

Raisecom Proprietary and Confidential

400
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

PE4(config)#router ospf 1 router-id 4.4.4.4

PE4(config-router-ospf)#network 4.4.4.4 0.0.0.255 area 0
PE4(config-router-ospf)#network 60.0.0.1 0.0.0.255 area 0
PE4(config-router-ospf)#network 70.0.0.1 0.0.0.255 area 0
PE4(config-router-ospf)#exit

 Configure PE 6.

PE6(config)#interface loopback 2
PE6(config-loopback2)#ip address 6.6.6.6 255.255.255.0
PE6(config-loopback2)#exit
PE6(config)#router id 6.6.6.6
PE6(config)#router ospf 1 router-id 6.6.6.6
PE6(config-router-ospf)#network 6.6.6.6 0.0.0.255 area 0
PE6(config-router-ospf)#network 60.0.0.2 0.0.0.255 area 0
PE6(config-router-ospf)#network 30.0.0.1 0.0.0.255 area 0
PE6(config-router-ospf)#exit

 Configure PE 7.

PE7(config)#interface loopback 2
PE7(config-loopback2)#ip address 7.7.7.7 255.255.255.0
PE7(config-loopback2)#exit
PE7(config)#router id 7.7.7.7
PE7(config)#router ospf 1 router-id 7.7.7.7
PE7(config-router-ospf)#network 7.7.7.7 0.0.0.255 area 0
PE7(config-router-ospf)#network 70.0.0.2 0.0.0.255 area 0
PE7(config-router-ospf)#network 50.0.0.1 0.0.0.255 area 0
PE7(config-router-ospf)#exit

 Configure PE 5.

PE5(config)#interface loopback 2
PE5(config-loopback2)#ip address 5.5.5.5 255.255.255.0
PE5(config-loopback2)#exit
PE5(config)#router id 5.5.5.5
PE5(config)#router ospf 1 router-id 5.5.5.5
PE5(config-router-ospf)#network 5.5.5.5 0.0.0.255 area 0
PE5(config-router-ospf)#network 30.0.0.2 0.0.0.255 area 0
PE5(config-router-ospf)#network 50.0.0.2 0.0.0.255 area 0
PE5(config-router-ospf)#exit

 Configure PE 3.

PE3(config)#interface loopback 2

Raisecom Proprietary and Confidential

401
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

PE3(config-loopback2)#ip address 3.3.3.3 255.255.255.0

PE3(config-loopback2)#exit

Step 4 Configure static routes among PE devices.

 Configure PE 1.

PE1(config)#ip route 4.4.4.4 255.255.255.0 20.0.0.2

 Configure PE 2.

PE2(config)#ip route 4.4.4.4 255.255.255.0 40.0.0.2

 Configure PE 3.

PE3(config)#ip route 5.5.5.5 255.255.255.0 80.0.0.1

 Configure PE 4.

PE4(config)#ip route 1.1.1.1 255.255.255.0 20.0.0.1

PE4(config)#ip route 2.2.2.2 255.255.255.0 40.0.0.1

 Configure PE 5.

PE5(config)#ip route 3.3.3.3 255.255.255.0 80.0.0.2

Step 5 Establish LDP sessions among PE devices.

 Configure PE 4.

PE4(config)#mpls ldp targeted neighbor 6.6.6.6

PE4(config)#mpls ldp targeted neighbor 7.7.7.7

 Configure PE 5.

PE5(config)#mpls ldp targeted neighbor 6.6.6.6

PE5(config)#mpls ldp targeted neighbor 7.7.7.7

Raisecom Proprietary and Confidential

402
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

 Configure PE 6.

PE6(config)#mpls ldp targeted neighbor 4.4.4.4

PE6(config)#mpls ldp targeted neighbor 5.5.5.5

 Configure PE 7.

PE7(config)#mpls ldp targeted neighbor 4.4.4.4

PE7(config)#mpls ldp targeted neighbor 5.5.5.5

Step 6 Create a static Tunnel and static LSP.

 Configure PE 1.

PE1(config)#interface tunnel 1/1/1

PE1(config-tunnel1/1/1)#destination 4.4.4.4
PE1(config-tunnel1/1/1)#mpls tunnel-id 1
PE1(config-tunnel1/1/1)#mpls te commit
PE1(config-tunnel1/1/1)#exit
PE1(config)#mpls bidirectional static-lsp ingress lspin1 lsr-id 4.4.4.4
tunnel-id 1
PE1(config-ingress-lsp)#forward 4.4.4.4 255.255.255.255 nexthop 20.0.0.2
out-label 1004
PE1(config-ingress-lsp)#backward in-label 4001
PE1(config-ingress-lsp)#exit

 Configure PE 2.

PE2(config)#interface tunnel 1/1/2

PE2(config-tunnel1/1/2)#destination 4.4.4.4
PE2(config-tunnel1/1/2)#mpls tunnel-id 2
PE2(config-tunnel1/1/2)#mpls te commit
PE2(config-tunnel1/1/2)#exit
PE2(config)#mpls bidirectional static-lsp ingress lspin2 lsr-id 4.4.4.4
tunnel-id 2
PE2(config-ingress-lsp)#forward 4.4.4.4 255.255.255.255 nexthop 40.0.0.2
out-label 2004
PE2(config-ingress-lsp)#backward in-label 4002
PE2(config-ingress-lsp)#exit

 Configure PE 3.

PE3(config)#interface tunnel 1/1/3

PE3(config-tunnel1/1/3)#destination 5.5.5.5
PE3(config-tunnel1/1/3)#mpls tunnel-id 3

Raisecom Proprietary and Confidential

403
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

PE3(config-tunnel1/1/3)#mpls te commit
PE3(config-tunnel1/1/3)#exit
PE3(config)#mpls bidirectional static-lsp ingress lspin3 lsr-id 5.5.5.5
tunnel-id 3
PE3(config-ingress-lsp)#forward 5.5.5.5 255.255.255.255 nexthop 80.0.0.1
out-label 3005
PE3(config-ingress-lsp)#backward in-label 5003
PE3(config-ingress-lsp)#exit

 Configure the Tunnel from PE 4 to PE 1 on PE 4.

PE4(config)#interface tunnel 1/1/1

PE4(config-tunnel1/1/1)#destination 1.1.1.1
PE4(config-tunnel1/1/1)#mpls tunnel-id 1
PE4(config-tunnel1/1/1)#mpls te commit
PE4(config-tunnel1/1/1)#exit
PE4(config)#mpls bidirectional static-lsp ingress lspin1 lsr-id 1.1.1.1
tunnel-id 1
PE4(config-ingress-lsp)#forward 1.1.1.1 255.255.255.255 nexthop 20.0.0.1
out-label 4001
PE4(config-ingress-lsp)#backward in-label 1004
PE4(config-ingress-lsp)#exit

 Configure the Tunnel from PE 4 to PE 2 on PE 4.

PE4(config)#interface tunnel 1/1/2

PE4(config-tunnel1/1/2)#destination 2.2.2.2
PE4(config-tunnel1/1/2)#mpls tunnel-id 2
PE4(config-tunnel1/1/2)#mpls te commit
PE4(config-tunnel1/1/2)#exit
PE4(config)#mpls bidirectional static-lsp ingress lspin2 lsr-id 2.2.2.2
tunnel-id 2
PE4(config-ingress-lsp)#forward 2.2.2.2 255.255.255.255 nexthop 40.0.0.1
out-label 4002
PE4(config-ingress-lsp)#backward in-label 2004
PE4(config-ingress-lsp)#exit

 Configure PE 5.

PE5(config)#interface tunnel 1/1/3

PE5(config-tunnel1/1/3)#destination 3.3.3.3
PE5(config-tunnel1/1/3)#mpls tunnel-id 3
PE5(config-tunnel1/1/3)#mpls te commit
PE5(config-tunnel1/1/3)#exit
PE5(config)#mpls bidirectional static-lsp ingress lspin3 lsr-id 3.3.3.3
tunnel-id 3
PE5(config-ingress-lsp)#forward 3.3.3.3 255.255.255.255 nexthop 80.0.0.2
out-label 5003

Raisecom Proprietary and Confidential

404
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

PE5(config-ingress-lsp)#backward in-label 3005

PE5(config-ingress-lsp)#exit

Step 7 Create a static PW and enable PW redundancy protection.

 Configure PE 1 and activate services based on VLAN 100.

PE1(config)#interface gigaethernet 1/2/1.100

PE1(config-gigaethernet1/2/1.100)#encapsulation dot1q 100
PE1(config-gigaethernet1/2/1.100)#mode l2
PE1(config-gigaethernet1/2/1.100)#mpls static-l2vc destination 4.4.4.4
vc-id 101 in-label 1001 out-label 1001 tunnel 1/1/1
PE1(config-gigaethernet1/2/1.100)#mpls static-l2vc destination 4.4.4.4
vc-id 201 in-label 1101 out-label 1101 tunnel 1/1/1 backup
PE1(config-gigaethernet1/2/1.100)#mpls l2vpn redundancy master
PE1(config-gigaethernet1/2/1.100)#mpls l2vpn pw traffic enable
PE1(config-gigaethernet1/2/1.100)#mpls l2vpn pw bfd
PE1(config-gigaethernet1/2/1.100)#mpls l2vpn pw bfd backup

 Configure PE 2 and activate services based on VLAN 200.

PE2(config)#interface gigaethernet 1/2/1.200

PE2(config-gigaethernet1/2/1.200)#encapsulation dot1q 200
PE2(config-gigaethernet1/2/1.200)#mode l2
PE2(config-gigaethernet1/2/1.200)#mpls static-l2vc destination 4.4.4.4
vc-id 301 in-label 2001 out-label 2001 tunnel 1/1/2
PE2(config-gigaethernet1/2/1.200)#mpls static-l2vc destination 4.4.4.4
vc-id 401 in-label 2101 out-label 2101 tunnel 1/1/2 backup
PE2(config-gigaethernet1/2/1.200)#mpls l2vpn redundancy master
PE2(config-gigaethernet1/2/1.200)#mpls l2vpn pw traffic enable
PE2(config-gigaethernet1/2/1.200)#mpls l2vpn pw bfd
PE2(config-gigaethernet1/2/1.200)#mpls l2vpn pw bfd backup

 Configure PE 3 and activate services based on VLAN 100.

PE3(config)#interface gigaethernet 1/2/1.100

PE3(config-gigaethernet1/2/1.100)#encapsulation dot1q 100
PE3(config-gigaethernet1/2/1.100)#mode l2
PE3(config-gigaethernet1/2/1.100)#mpls static-l2vc destination 5.5.5.5
vc-id 501 in-label 3001 out-label 3001 tunnel 1/1/3
PE3(config-gigaethernet1/2/1.100)#mpls static-l2vc destination 5.5.5.5
vc-id 601 in-label 3101 out-label 3101 tunnel 1/1/3 backup
PE3(config-gigaethernet1/2/1.100)#mpls l2vpn redundancy master
PE3(config-gigaethernet1/2/1.100)#mpls l2vpn pw traffic enable
PE3(config-gigaethernet1/2/1.100)#mpls l2vpn pw bfd
PE3(config-gigaethernet1/2/1.100)#mpls l2vpn pw bfd backup

Raisecom Proprietary and Confidential

405
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

 Configure PE 3 and activate services based on VLAN 200.

PE3(config)#interface gigaethernet 1/2/1.200

PE3(config-gigaethernet1/2/1.200)#encapsulation dot1q 200
PE3(config-gigaethernet1/2/1.200)#mode l2
PE3(config-gigaethernet1/2/1.200)#mpls static-l2vc destination 5.5.5.5
vc-id 701 in-label 4001 out-label 4001 tunnel 1/1/3
PE3(config-gigaethernet1/2/1.200)#mpls static-l2vc destination 5.5.5.5
vc-id 801 in-label 4101 out-label 4101 tunnel 1/1/3 backup
PE3(config-gigaethernet1/2/1.200)#mpls l2vpn redundancy master
PE3(config-gigaethernet1/2/1.200)#mpls l2vpn pw traffic enable
PE3(config-gigaethernet1/2/1.200)#mpls l2vpn pw bfd
PE3(config-gigaethernet1/2/1.200)#mpls l2vpn pw bfd backup

Step 8 Configure switching static PW to dynamic PW.

 Configure PE 4.

PE4(config)#mpls switch-l2vc 1.1.1.1 101 in-label 1001 out-label 1001

tunnel 1/1/1 between 6.6.6.6 1011 tagged
PE4(config)#mpls switch-l2vc 1.1.1.1 201 in-label 1101 out-label 1101
tunnel 1/1/1 between 7.7.7.7 1012 tagged
PE4(config)#mpls switch-l2vc 2.2.2.2 301 in-label 2001 out-label 2001
tunnel 1/1/2 between 6.6.6.6 2011 tagged
PE4(config)#mpls switch-l2vc 2.2.2.2 401 in-label 2101 out-label 2101
tunnel 1/1/2 between 7.7.7.7 2012 tagged

 Configure PE 5.

PE5(config)#mpls switch-l2vc 3.3.3.3 501 in-label 3001 out-label 3001

tunnel 1/1/3 between 6.6.6.6 1011 tagged
PE5(config)#mpls switch-l2vc 3.3.3.3 601 in-label 3101 out-label 3101
tunnel 1/1/3 between 7.7.7.7 1012 tagged
PE5(config)#mpls switch-l2vc 3.3.3.3 701 in-label 4001 out-label 4001
tunnel 1/1/3 between 6.6.6.6 2011 tagged
PE5(config)#mpls switch-l2vc 3.3.3.3 801 in-label 4101 out-label 4101
tunnel 1/1/3 between 7.7.7.7 2012 tagged

 Configure PE 6.

PE6(config)#mpls switch-l2vc 5.5.5.5 1011 between 4.4.4.4 1011 tagged

PE6(config)#mpls switch-l2vc 5.5.5.5 2011 between 4.4.4.4 2011 tagged

 Configure PE 7.

Raisecom Proprietary and Confidential

406
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 15 Reliability

PE7(config)#mpls switch-l2vc 5.5.5.5 1012 between 4.4.4.4 1012 tagged

PE7(config)#mpls switch-l2vc 5.5.5.5 2012 between 4.4.4.4 2012 tagged

Checking configurations
After configurations are complete, use the following commands to check whether LDP LSP is
correctly created and whether the status is Up and check whether the status of PW, VC, and
AC are Up.
 show mpls ldp session
 show mpls ldp targeted neighbour
 show mpls lsp ldp
 show mpls l2vc
 show mpls switch-l2vc

Raisecom Proprietary and Confidential

407
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 16 Appendix

16 Appendix

This chapter lists terms, acronyms, and abbreviations involved in this document, including the
following sections:
 Terms
 Acronyms and abbreviations

16.1 Terms
A
A series of ordered rules composed of permit | deny sentences. These
Access
rules are based on source MAC address, destination MAC address,
Control List
source IP address, destination IP address, interface ID, etc. The device
(ACL)
decides to receive or refuse the packets based on these rules.

C
An electronic module, composed of the chip and other electronic
Card components installed on a flat and hard Printed Circuit Board (PCB). The
PCB has conductive circuits for connecting these components.
A standard defined by IEEE. It defines protocols and practices for OAM
Connectivity
(Operations, Administration, and Maintenance) for paths through 802.1
Fault
bridges and local area networks (LANs). Used to diagnose fault for EVC
Management
(Ethernet Virtual Connection). Cost-effective by fault management
(CFM)
function and improve Ethernet maintenance.

E
Encapsulation A technology used by the layered protocol. When the lower protocol
receives packets from the upper layer, it will map packets to the data of
the lower protocol. The outer layer of the data is encapsulated with the
lower layer overhead to form a lower protocol packet structure. For
example, an IP packet from the IP protocol is mapped to the data of
802.1Q protocol. The outer layer is encapsulated by the 802.1Q frame
header to form a VLAN frame structure.
Raisecom Proprietary and Confidential
408
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 16 Appendix

A
Complying with IEEE 802.3ah protocol, EFM is a link-level Ethernet
Ethernet in OAM technology. It provides the link connectivity detection, link fault
the First Mile monitoring, and remote fault notification, etc. for a link between two
(EFM) directly-connected devices. EFM is mainly used for the Ethernet link on
edges of the network accessed by users.

L
Link A computer networking term which describes using multiple network
Aggregation cables/ports in parallel to increase the link speed beyond the limits of any
one single cable or port, and to increase the redundancy for higher
availability.

P
In data communication field, packet is the data unit for switching and
transmitting information. In transmission, it will be continuously
encapsulated and decapsulated. The header is used to define the
Packet
destination address and source address. The trailer contains information
indicating the end of the packet. The payload data in between is the
actual packet.
In packet switching network, data is partitioned into multiple data
segments. The data segment is encapsulated by control information, such
as, destination address, to form the switching packet. The switching
Packet
packet is transmitted to the destination in the way of storage-forwarding
switching
on the network. Packet switching is developed based on storage-
forwarding method and has merits of both circuit switching and packet
switching.

Q
QinQ QinQ is (also called Stacked VLAN or Double VLAN) extended from
802.1Q, defined by IEEE 802.1ad recommendation. Basic QinQ is a
simple layer-2 VPN tunnel technology, encapsulating outer VLAN Tag
for client private packets at carrier access end; the packets take double
VLAN Tag passing through trunk network (public network). In public
network, packets only transmit according to outer VLAN Tag, the private
VLAN Tag are transmitted as data in packets.

V
Virtual Local VLAN is a protocol proposed to solve broadcast and security issues for
Area Ethernet. It divides devices in a LAN into different segments logically
Network rather than physically, thus implementing multiple virtual work groups
(VLAN) which are based on Layer 2 isolation and do not affect each other.

Raisecom Proprietary and Confidential

409
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 16 Appendix

A
VLAN mapping is mainly used to replace the private VLAN Tag of the
Ethernet service packet with the ISP's VLAN Tag, making the packet
transmitted according to ISP's VLAN forwarding rules. When the packet
VLAN
is sent to the peer private network from the ISP network, the VLAN Tag
mapping
is restored to the original private VLAN Tag according to the same
VLAN forwarding rules. Thus, the packet is sent to the destination
correctly.

16.2 Acronyms and abbreviations

A
ACL Access Control List
APS Automatic Protection Switching

C
CE Customer Edge
CFM Connectivity Fault Management
CoS Class of Service

D
DHD Dual Home Device
DRR Deficit Round Robin
DSCP Differentiated Services Code Point

E
EFM Ethernet in the First Mile

F
FTP File Transfer Protocol

G
GPS Global Positioning System
GSM Global System for Mobile Communications

Raisecom Proprietary and Confidential

410
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 16 Appendix

H
HA High Availability

I
ICCP Inter-Chassis Communication Protocol
IEEE Institute of Electrical and Electronics Engineers
IETF Internet Engineering Task Force
IP Internet Protocol
International Telecommunications Union - Telecommunication
ITU-T
Standardization Sector

L
LACP Link Aggregation Control Protocol
LBM LoopBack Message
LBR LoopBack Reply
LLDP Link Layer Discovery Protocol
LLDPDU Link Layer Discovery Protocol Data Unit
LTM LinkTrace Message
LTR LinkTrace Reply

M
MA Maintenance Association
MAC Medium Access Control
MD Maintenance Domain
MEG Maintenance Entity Group
MEP Maintenance associations End Point
MIB Management Information Base
MIP Maintenance association Intermediate Point
MTU Maximum Transmission Unit

Raisecom Proprietary and Confidential

411
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 16 Appendix

A
NTP Network Time Protocol

O
OAM Operation, Administration and Maintenance

P
PDU Protocol Data Unit
PE Provider Edge
PSN Packet Switched Network
PTN Packet Transport Network
PW Pseudo Wire
PWE3 Pseudo Wire Emulation Edge-to-Edge

Q
QoS Quality of Service

R
RMEP Remote Maintenance association End Point
RMON Remote Network Monitoring

S
SAToP Structure-Agnostic TDM over Packet
SFP Small Form-factor Pluggables
SLA Service Level Agreement
SNMP Simple Network Management Protocol
SNTP Simple Network Time Protocol
SP Strict-Priority
SSH Secure Shell

T
TCI Tag Control Information
TCP Transmission Control Protocol

Raisecom Proprietary and Confidential

412
Copyright © Raisecom Technology Co., Ltd.
Raisecom
iTN8800 (P100R002) Configuration Guide 16 Appendix

A
TFTP Trivial File Transfer Protocol
TLV Type Length Value
ToS Type of Service
TPID Tag Protocol Identifier

V
VPN Virtual Private Network
VLAN Virtual Local Area Network

W
WRR Weight Round Robin

Raisecom Proprietary and Confidential

413
Copyright © Raisecom Technology Co., Ltd.
Address: Raisecom Building, No. 11, East Area, No. 10 Block, East Xibeiwang Road, Haidian
District, Beijing, P.R.China Postal code: 100094 Tel: +86-10-82883305
Fax: 8610-82883056 http://www.raisecom.com Email: export@raisecom.com