NView NNM (V5) Operation Guide (iTN201 Network Element ... Kuwait/NView NNM (V5...NView NNM (V5)...

NView NNM (V5) Operation Guide

(iTN201 Network Element Management)

(Rel_41)

www.raisecom.com

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

Address: Building 2, No. 28, Shangdi 6th Street, Haidian District, Beijing, P.R.China

Postal code: 100085

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

Notice

Copyright © 2013

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

NView NNM (V5) Operation Guide (iTN201 Network

Element Management) Preface

Raisecom Technology Co., Ltd. i

Preface

Objectives This guide introduces features and management methods supported by the iTN201 Element

Management System (EMS), including methods and processes for realizing topology

management, device management, service management, alarm management, and performance

management through the iTN201 EMS. The appendix of this guide provides the alarm list,

performance list, as well as terms and abbreviations involved in this guide.

This guide helps you systematically master the usage and configuration methods of the

iTN201.

Versions The following tables list the product versions related to this document.

Product name Product version Hardware version Software version

iTN201 P200R002 C or later P200R002C00 or later

NNM system name NNM system version

NView NNM V5

EMS name EMS version

iTN200 V5.6

Conventions

Symbol conventions

The symbols that may be found in this document are defined as follows.

Raisecom



Raisecom Technology Co., Ltd. ii

Symbol Description

Indicates a hazard with a medium or low level of risk which, if

not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation that, if not avoided,

could cause equipment damage, data loss, and performance

degradation, or unexpected results.

Provides additional information to emphasize or supplement

important points of the main text.

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

GUI conventions

Convention Description

Boldface Buttons, menus, parameters, tabs, windows, and dialog titles are

in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.

Keyboard operation

Format Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+C

means the two keys should be pressed concurrently.

Raisecom



Raisecom Technology Co., Ltd. iii

Format Description

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the

two keys should be pressed in turn.

Mouse operation

Action Description

Click Select and release the primary mouse button without moving the

pointer.

Double-click Press the primary mouse button twice continuously and quickly

without moving the pointer.

Drag Press and hold the primary mouse button and move the pointer

to a certain position.

Change history Updates between document versions are cumulative. Therefore, the latest document version

contains all updates made to previous versions.

Issue 02 (2013-07-03)

Second commercial release

Revised known format and text bugs.

Deleted default gateway configurations of the routing feature.

Added MPLS-TP configurations and related OAM and linear protection switching

configurations.

Added clock synchronization configurations.

Added TDMoP configurations.

Issue 01 (2013-03-27)

Initial commercial release

Raisecom


Element Management) Contents

Raisecom Technology Co., Ltd. iv

Contents

1 Overview ......................................................................................................................................... 1

1.1 Functions .......................................................................................................................................................... 1

1.2 Features ............................................................................................................................................................ 1

1.2.1 Great topology management ................................................................................................................... 1

1.2.2 Flexible security management................................................................................................................. 2

1.2.3 Complete alarm management .................................................................................................................. 2

1.2.4 Perfect performance management ........................................................................................................... 3

1.2.5 Excellent operation and maintenance feature .......................................................................................... 4

1.3 Device introduction .......................................................................................................................................... 4

1.4 Network management protocols ....................................................................................................................... 5

2 Network management .................................................................................................................. 7

2.1 Overview of network management modes ....................................................................................................... 7

2.1.1 In-band management ............................................................................................................................... 7

2.1.2 Out-of-band management ....................................................................................................................... 8

2.2 Configuring in-band management .................................................................................................................... 8

2.3 Configuring out-of-band management ............................................................................................................. 9

2.4 Configuring SNMP community ....................................................................................................................... 9

2.5 Configuring Trap target address ..................................................................................................................... 10

2.6 Checking configurations ................................................................................................................................ 11

3 NView NNM ................................................................................................................................ 12

3.1 System monitoring ......................................................................................................................................... 12

3.1.1 Service management ............................................................................................................................. 12

3.1.2 Monitoring ............................................................................................................................................ 13

3.1.3 Other management functions ................................................................................................................ 13

3.2 Starting/Stopping NView NNM system ......................................................................................................... 13

3.2.1 Starting NMS Server ............................................................................................................................. 13

3.2.2 Viewing enabling status of platform service ......................................................................................... 14

3.2.3 Starting NView NNM Client ................................................................................................................. 14

3.2.4 Stopping NView NNM Client ............................................................................................................... 16

3.2.5 Stopping all NView NNM services ....................................................................................................... 16

3.2.6 Stopping NMS Server ........................................................................................................................... 17

3.3 Topology management ................................................................................................................................... 17

Raisecom



Raisecom Technology Co., Ltd. v

3.3.1 Topology view ....................................................................................................................................... 18

3.3.2 Topology tree ........................................................................................................................................ 24

3.4 Shortcut menus ............................................................................................................................................... 24

3.5 Synchronizing NE data................................................................................................................................... 25

3.5.1 Initiating resource synchronization in topology .................................................................................... 26

3.6 iTN201 EMS .................................................................................................................................................. 26

3.6.1 Access methods ..................................................................................................................................... 26

3.6.2 View descriptions .................................................................................................................................. 26

3.7 Device properties ........................................................................................................................................... 28

3.7.1 Editting device properties ..................................................................................................................... 28

3.7.2 Viewing device properties ..................................................................................................................... 30

4 Basic configurations ................................................................................................................... 33

4.1 Configuring login users .................................................................................................................................. 33

4.1.1 Adding login users ................................................................................................................................ 33

4.1.2 Modifying passwords of login users ..................................................................................................... 34

4.1.3 Configuring priority rules for users performing commands .................................................................. 34

4.2 Configuring system information .................................................................................................................... 35

4.3 Upgrade/Backup ............................................................................................................................................. 35

4.3.1 Overview ............................................................................................................................................... 35

4.3.2 Upgrading/Backing up system software through FTP/TFTP/SFTP ...................................................... 36

4.4 Configuring time management ....................................................................................................................... 37

4.4.1 Configuring system time ....................................................................................................................... 37

4.4.2 Configuring DST .................................................................................................................................. 38

4.4.3 Configuring NTP/SNTP ........................................................................................................................ 40

4.4.4 Checking configurations ....................................................................................................................... 43

4.5 Configuring interface management ................................................................................................................ 44

4.5.1 Configure basic interface properties ..................................................................................................... 44

4.5.2 Configuring flow control of interfaces .................................................................................................. 44

4.5.3 Enabling/Disabling interfaces ............................................................................................................... 45

4.5.4 Configuring SNMP interface ................................................................................................................ 45


4.6 Saving configurations ..................................................................................................................................... 46

4.7 Rebooting the device ...................................................................................................................................... 46

4.8 Deleting configurations .................................................................................................................................. 47

5 Zero-configuration ...................................................................................................................... 48

5.1 Introduction .................................................................................................................................................... 48

5.2 Configuring local zero-configuration ............................................................................................................. 51

5.2.1 Preparing for configurations ................................................................................................................. 51

5.2.2 Configuring directly-connected zero-configuration server ................................................................... 51

5.2.3 Configuring indirectly-connected zero-configuration server ................................................................ 54


Raisecom



Raisecom Technology Co., Ltd. vi

5.3 Configuration examples ................................................................................................................................. 61

5.3.1 Examples for configuring indirectly-connected local/remote zero-configuration ................................. 61

6 Ethernet ......................................................................................................................................... 64

6.1 Introduction .................................................................................................................................................... 64

6.1.1 MAC address table ................................................................................................................................ 64

6.1.2 VLAN ................................................................................................................................................... 66

6.1.3 QinQ...................................................................................................................................................... 67

6.1.4 VLAN mapping..................................................................................................................................... 67

6.1.5 Loopback detection ............................................................................................................................... 68

6.1.6 Interface protection ............................................................................................................................... 68

6.1.7 Layer 2 protocol transparent transmission ............................................................................................ 68

6.1.8 ARP ....................................................................................................................................................... 69

6.1.9 Port mirroring........................................................................................................................................ 70

6.2 Configuring MAC address table..................................................................................................................... 70


6.2.2 Configuring static MAC addresses ....................................................................................................... 71

6.2.3 Configuring dynamic MAC addresses .................................................................................................. 73

6.2.4 Configuring blackhole MAC addresses ................................................................................................ 74


6.3 Configuring VLAN ........................................................................................................................................ 75


6.3.2 Creating VLANs ................................................................................................................................... 76

6.3.3 Configuring interface modes and interface-based VLANs ................................................................... 76

6.3.4 Configuring Layer 3 interface ............................................................................................................... 78


6.4 Configuring QinQ .......................................................................................................................................... 80


6.4.2 Configuring basic QinQ ........................................................................................................................ 80

6.4.3 Configuring selective QinQ .................................................................................................................. 81

6.4.4 Setting egress interface to Tunk interface ............................................................................................. 82


6.5 Configuring VLAN mapping ......................................................................................................................... 83


6.5.2 Configuring 1:1 VLAN mapping .......................................................................................................... 83


6.6 Configuring loopback detection ..................................................................................................................... 84


6.6.2 Configuring basic functions of loopback detection ............................................................................... 84


6.7 Configuring interface protection .................................................................................................................... 86


Raisecom



Raisecom Technology Co., Ltd. vii

6.7.2 Configuring interface protection ........................................................................................................... 87


6.8 Configuring Layer 2 protocol transparent transmission ................................................................................. 87


6.8.2 Configuring Layer 2 protocol transparent transmission parameters ..................................................... 88


6.9 Configuring ARP ............................................................................................................................................ 89


6.9.2 Configuring static ARP entries .............................................................................................................. 90

6.9.3 Configuring dynamic ARP entries ........................................................................................................ 90


6.10 Configuring port mirroring ........................................................................................................................... 92

6.10.1 Preparing for configurations ............................................................................................................... 92

6.10.2 Configuring port mirroring ................................................................................................................. 92

6.11 Configuration examples ............................................................................................................................... 93

6.11.1 Examples for configuring basic QinQ ................................................................................................. 93

6.11.2 Examples for configuring selective QinQ ........................................................................................... 96

6.11.3 Examples for configuring VLAN mapping ......................................................................................... 99

6.11.4 Examples for configuring loopback detection ................................................................................... 103

7 Clock synchronization ............................................................................................................. 105

7.1 Introduction .................................................................................................................................................. 105

7.1.1 Synchronous Ethernet ......................................................................................................................... 106

7.1.2 IEEE 1588 v2 protocol (PTP) ............................................................................................................. 106

7.2 Configuring clock synchronization based on synchronous Ethernet ............................................................ 107


7.2.2 Configuring basic properties of synchronous Ethernet ....................................................................... 108

7.2.3 Configuring clock sources .................................................................................................................. 109

7.2.4 Checking configurations ..................................................................................................................... 111

7.3 Configuring PTP-based clock synchronization ............................................................................................ 112


7.3.2 Configuring clock modes .................................................................................................................... 112

7.3.3 (Optional) configuring clock properties .............................................................................................. 114

7.3.4 (Optional) configuring transmission properties of PTP packets.......................................................... 116

7.3.5 (Optional) configuring clock interface properties ............................................................................... 119

7.3.6 Configuring input/output clock signals of clock sub-card .................................................................. 120


7.4 Maintenance ................................................................................................................................................. 125


7.5.1 Examples for configuring clock synchronization based on synchronous Ethernet ............................. 126

7.5.2 Examples for configuring PTP-based clock synchronization ............................................................. 127

8 MPLS-TP ..................................................................................................................................... 133

Raisecom



Raisecom Technology Co., Ltd. viii

8.1 Introduction .................................................................................................................................................. 133

8.1.1 Basic concepts ..................................................................................................................................... 134

8.1.2 Static LSP ........................................................................................................................................... 136

8.1.3 MPLS L2VPN ..................................................................................................................................... 137

8.1.4 VPLS ................................................................................................................................................... 138

8.2 Configuring basic functions of MPLS .......................................................................................................... 142


8.2.2 Configuring basic functions of MPLS ................................................................................................ 142


8.3 Configuring static LSP ................................................................................................................................. 144


8.3.2 Configuring static LSP ........................................................................................................................ 144


8.4 Configuring MPLS L2VPN ......................................................................................................................... 149


8.4.2 Configuring MPLS L2VPN ................................................................................................................ 149


8.5 Configuring VPLS........................................................................................................................................ 153


8.5.2 Creating VPLS VSI ............................................................................................................................. 153

8.5.3 Configuring VSI static PW ................................................................................................................. 154

8.5.4 Configuring VSI UNI .......................................................................................................................... 156



8.6.1 Examples for configuring bidirectional static LSP ............................................................................. 157

9 TDMoP ........................................................................................................................................ 160

9.1 Introduction .................................................................................................................................................. 160

9.1.1 Principles of TDMoP technology ........................................................................................................ 161

9.1.2 TDMoP service encapsulation protocol .............................................................................................. 163

9.1.3 TDMoP clock recovery technology .................................................................................................... 169

9.1.4 TDMoP delay jitter buffer technology ................................................................................................ 169

9.2 Configuring TDM interfaces ........................................................................................................................ 169


9.2.2 Configuring link type of TDM interfaces............................................................................................ 170

9.2.3 Configuring loopback of TDM interfaces ........................................................................................... 171

9.2.4 Configuring Tx clock source of TDM interfaces ................................................................................ 171

9.2.5 Configuring codes for TDM idle timeslots ......................................................................................... 172


9.3 Configuring Tunnel ...................................................................................................................................... 173


9.3.2 Creating MEF Tunnel.......................................................................................................................... 173

Raisecom



Raisecom Technology Co., Ltd. ix

9.3.3 Creating IP Tunnel .............................................................................................................................. 173


9.4 Configuring PW ........................................................................................................................................... 175


9.4.2 Configuring IP address of the TDMoP sub-card ................................................................................. 175

9.4.3 Creating PW and configuring PW properties ...................................................................................... 176


9.5.1 Examples for configuring CESoPSN emulation services ................................................................... 177

10 OAM .......................................................................................................................................... 181

10.1 Introduction ................................................................................................................................................ 181

10.1.1 EFM .................................................................................................................................................. 181

10.1.2 CFM .................................................................................................................................................. 181

10.1.3 SLA ................................................................................................................................................... 182

10.1.4 RFC2544 ........................................................................................................................................... 183

10.1.5 MPLS-TP OAM ................................................................................................................................ 184

10.2 Configuring EFM ....................................................................................................................................... 184

10.2.1 Preparing for configurations ............................................................................................................. 184

10.2.2 Configuring basic functions of EFM ................................................................................................. 185

10.2.3 Configuring active functions of EFM ............................................................................................... 186

10.2.4 Configuring passive functions of EFM ............................................................................................. 187

10.2.5 Checking configurations ................................................................................................................... 189

10.3 Configuring CFM ....................................................................................................................................... 190


10.3.2 Enabling CFM ................................................................................................................................... 191

10.3.3 Configuring basic functions of CFM ................................................................................................ 192

10.3.4 Configuring fault detection ............................................................................................................... 194

10.3.5 Configuring fault acknowledgement ................................................................................................. 196

10.3.6 Configuring fault location ................................................................................................................. 197

10.3.7 Configuring AIS ................................................................................................................................ 199


10.4 Configuring MPLS-TP CFM ...................................................................................................................... 200


10.4.2 Enabling MPLS-TP CFM.................................................................................................................. 201

10.4.3 Configuring MPLS-TP CFM ............................................................................................................ 202

10.4.4 Configuring MPLS-TP fault detection .............................................................................................. 208

10.4.5 Configuring MPLS-TP fault acknowledgement ................................................................................ 210

10.4.6 Configuring MPLS-TP fault location ................................................................................................ 211

10.4.7 Configuring MPLS-TP AIS ............................................................................................................... 212

10.4.8 Configuring MPLS-TP LCK ............................................................................................................. 213

10.5 Configuring SLA ........................................................................................................................................ 214


Raisecom



Raisecom Technology Co., Ltd. x

10.5.2 Configuring Ethernet SLA operations (delay/jitter/packet loss ratio) ............................................... 214

10.5.3 Configuring basic information of MPLS-TP SLA operations ........................................................... 218

10.5.4 Configuring SLA scheduling information ......................................................................................... 223


10.6 Configuring RFC2544 ................................................................................................................................ 227


10.6.2 Creating test templates ...................................................................................................................... 228

10.6.3 Configuring test tasks........................................................................................................................ 231

10.6.4 Outputting reports ............................................................................................................................. 232


10.7 Configuration examples ............................................................................................................................. 234

10.7.1 Examples for configuring EFM ........................................................................................................ 234

10.7.2 Examples for configuring CFM ........................................................................................................ 235

10.7.3 Examples for configuring SLA ......................................................................................................... 240

10.7.4 Examples for configuring RFC2544 throughput test ........................................................................ 242

11 Network reliability ................................................................................................................. 245

11.1 Introduction ................................................................................................................................................ 245

11.1.1 Link aggregation ............................................................................................................................... 245

11.1.2 Interface backup ................................................................................................................................ 246

11.1.3 ELPS ................................................................................................................................................. 246

11.1.4 ERPS ................................................................................................................................................. 246

11.1.5 MPLS-TP linear protection switching ............................................................................................... 246

11.1.6 Failover ............................................................................................................................................. 248

11.2 Configuring link aggregation ..................................................................................................................... 249

11.2.1 Preparing for configurations .............................................................................................................. 249

11.2.2 Configuring manual link aggregation ................................................................................................ 249

11.2.3 Configuring static LACP link aggregation ........................................................................................ 252


11.3 Configuring interface backup ..................................................................................................................... 253


11.3.2 Configuring basic functions of interface backup ............................................................................... 254


11.4 Configuring ELPS ...................................................................................................................................... 255


11.4.2 Creating protection lines ................................................................................................................... 256

11.4.3 (Optional) configuring ELPS switching control ................................................................................ 259


11.5 Configuring ERPS ...................................................................................................................................... 260


11.5.2 Creating ERPS protection ring .......................................................................................................... 261

11.5.3 (Optional) creating ERPS protection sub-ring .................................................................................. 263

Raisecom



Raisecom Technology Co., Ltd. xi

11.5.4 Configuring ERPS fault detection modes ......................................................................................... 264

11.5.5 (Optional) configuring ERPS switching control ............................................................................... 265


11.6 Configuring MPLS-TP linear protection switching .................................................................................... 267


11.6.2 Configuring Tunnel protection group ................................................................................................ 267

11.6.3 Configuring protection switching ...................................................................................................... 269


11.7 Configuring failover ................................................................................................................................... 270


11.7.2 Configuring failover .......................................................................................................................... 271


11.8 Maintenance ............................................................................................................................................... 273


11.9.1 Examples for configuring manual link aggregation .......................................................................... 274

11.9.2 Examples for configuring 1:1 ELPS ................................................................................................. 275

11.9.3 Examples for configuring single-ring ERPS ..................................................................................... 277

12 Security...................................................................................................................................... 281

12.1 Introduction ................................................................................................................................................ 281

12.1.1 ACL ................................................................................................................................................... 281

12.1.2 RADIUS ............................................................................................................................................ 281

12.1.3 TACACS+ ......................................................................................................................................... 282

12.1.4 Storm control .................................................................................................................................... 282

12.2 Configuring ACL ....................................................................................................................................... 282


12.2.2 Configuring IP ACL .......................................................................................................................... 283

12.2.3 Configuring MAC ACL .................................................................................................................... 284

12.2.4 Configuring User ACL ...................................................................................................................... 285

12.2.5 Applying ACL ................................................................................................................................... 290


12.3 Configuring RADIUS ................................................................................................................................ 294


12.3.2 Configuring RADIUS authentication ................................................................................................ 294


12.4 Configuring TACACS+ .............................................................................................................................. 296


12.4.2 Configuring TACACS+ authentication ............................................................................................. 296

12.4.3 Clearing TACACS+ statistics ............................................................................................................ 297

12.4.4 Viewing TACACS+ statistics ............................................................................................................ 298


12.5 Configuring storm control .......................................................................................................................... 298

Raisecom



Raisecom Technology Co., Ltd. xii


12.5.2 Configuring storm control ................................................................................................................. 299



12.6.1 Examples for configuring ACL ......................................................................................................... 300

12.6.2 Examples for configuring RADIUS .................................................................................................. 302

12.6.3 Examples for configuring TACACS+ ............................................................................................... 303

12.6.4 Examples for configuring storm control ........................................................................................... 305

13 QoS ............................................................................................................................................. 307

13.1 Introduction ................................................................................................................................................ 307

13.1.1 Priority trust ...................................................................................................................................... 308

13.1.2 Priority mapping ............................................................................................................................... 308

13.1.3 Traffic classification .......................................................................................................................... 308

13.1.4 Traffic policy ..................................................................................................................................... 309

13.1.5 Queue scheduling .............................................................................................................................. 309

13.1.6 Congestion avoidance ....................................................................................................................... 310

13.1.7 Queue shaping ................................................................................................................................... 311

13.1.8 Rate limiting based on interface and VLAN ..................................................................................... 311

13.2 Configuring priority trust and priority mapping ......................................................................................... 311

13.2.1 Preparing for conifgurations ............................................................................................................. 311

13.2.2 Configuring priority trust .................................................................................................................. 312

13.2.3 Configuring DSCP priority re-marking ............................................................................................. 312

13.2.4 Mapping DSCP priority to local priority and color ........................................................................... 313

13.2.5 Mapping CoS priority to local priority and color .............................................................................. 314

13.2.6 Mapping local priority to CoS priority .............................................................................................. 315


13.3 Configuring traffic classification and traffic policy ................................................................................... 317


13.3.2 Creating and configuring traffic classification .................................................................................. 317

13.3.3 Creating and configuring traffic policing profile .............................................................................. 319

13.3.4 Creating and configuring traffic policy ............................................................................................. 321


13.4 Configuring queue scheduling.................................................................................................................... 324


13.4.2 Configuring queue scheduling modes on interfaces .......................................................................... 324

13.4.3 Configuring WRR/DRR queue scheduling ....................................................................................... 325


13.5 Configuring congestion avoidance and queue shaping .............................................................................. 325


13.5.2 Configuring queue-based WRED ...................................................................................................... 326

13.5.3 Configuring queue shaping ............................................................................................................... 327

Raisecom



Raisecom Technology Co., Ltd. xiii


13.6 Configuring rate limiting based on interface and VLAN ........................................................................... 328


13.6.2 Configuring interface-based rate limiting ......................................................................................... 329

13.6.3 Configuring VLAN-based/QinQ-based rate limiting ........................................................................ 329

13.6.4 Configuring rate limiting based on interface and VLAN .................................................................. 330


13.7 Maintenance ............................................................................................................................................... 332


13.8.1 Examples for configuring rate limiting based on traffic policy ......................................................... 332

13.8.2 Examples for configuring queue scheduling and congestion avoidance ........................................... 335

13.8.3 Examples for configuring interface-based rate limiting .................................................................... 339

14 System management and maintenance............................................................................... 342

14.1 Introduction ................................................................................................................................................ 342

14.1.1 SNMP ................................................................................................................................................ 342

14.1.2 Routing .............................................................................................................................................. 343

14.1.3 RMON .............................................................................................................................................. 343

14.1.4 LLDP ................................................................................................................................................ 343

14.1.5 Optical module DDM........................................................................................................................ 343

14.1.6 System log ......................................................................................................................................... 344

14.1.7 Loopback test .................................................................................................................................... 344

14.1.8 Alarm management ........................................................................................................................... 344

14.1.9 CPU protection .................................................................................................................................. 345

14.1.10 CPU monitoring .............................................................................................................................. 345

14.1.11 Hardware environment monitoring ................................................................................................. 345

14.1.12 Remote management ....................................................................................................................... 345

14.2 Configuring SNMP .................................................................................................................................... 346


14.2.2 Configuring SNMPv1/v2c basic functions ....................................................................................... 347

14.2.3 Configuring SNMPv3 basic functions .............................................................................................. 349


14.3 Configuring routing .................................................................................................................................... 354


14.3.2 Configuring static routing ................................................................................................................. 354


14.4 Configuring RMON ................................................................................................................................... 355


14.4.2 Configuring RMON statistics ........................................................................................................... 356

14.4.3 Configuring RMON history group .................................................................................................... 356

14.4.4 Configuring RMON alarm group ...................................................................................................... 356

14.4.5 Configuring RMON event group ...................................................................................................... 358

Raisecom



Raisecom Technology Co., Ltd. xiv


14.5 Configuring LLDP ..................................................................................................................................... 359


14.5.2 Enabling global LLDP and LLDP alarm ........................................................................................... 359

14.5.3 Enabling interface LLDP .................................................................................................................. 360

14.5.4 Configuring basic functions of LLDP ............................................................................................... 361


14.6 Configuring optical module DDM ............................................................................................................. 363


14.6.2 Enabling optical module DDM ......................................................................................................... 364

14.6.3 Enabling optical module DDM and alarm management on interfaces .............................................. 364


14.7 Configuring system log .............................................................................................................................. 365


14.7.2 Configuring basic information about system log .............................................................................. 366

14.8 Configuring loopback test .......................................................................................................................... 369


14.8.2 Configuring parameters of interface loopback rules ......................................................................... 369

14.8.3 Configuring global loopback parameters .......................................................................................... 370


14.9 Configuring alarm management ................................................................................................................. 371


14.9.2 Configuring basic functions of alarm management .......................................................................... 372

14.10 Configuring CPU protection .................................................................................................................... 374

14.10.1 Preparing for configurations ........................................................................................................... 374

14.10.2 Configuring CPU protection ........................................................................................................... 374

14.10.3 Checking configurations ................................................................................................................. 375

14.11 Configuring CPU monitoring ................................................................................................................... 375

14.11.1 Preparing for configurations ............................................................................................................ 375

14.11.2 Viewing CPU monitoring information ............................................................................................ 376

14.11.3 Configuring CPU monitoring Trap.................................................................................................. 376

14.11.4 Checking configurations ................................................................................................................. 376

14.12 Configuring remote management ............................................................................................................. 377

14.12.2 Configuring IP addresses of remote devices ................................................................................... 377

14.12.3 Configuring interface properties of remote devices ........................................................................ 378

14.12.4 Configuring OAM Trap notification of remote devices .................................................................. 378

14.12.5 Configuring power-on notification of remote devices .................................................................... 379

14.12.6 Configuring remote VLAN ............................................................................................................. 379

14.12.7 Configuring related functions of remote QinQ ............................................................................... 381

14.12.8 configuring information about customers attaching to remote devices ........................................... 382

14.12.9 Rebooting remote devices ............................................................................................................... 383

14.12.10 Applying configurations ................................................................................................................ 383

Raisecom



Raisecom Technology Co., Ltd. xv

14.12.11 Viewing information about remote devices ................................................................................... 383

14.12.12 Viewing statistics .......................................................................................................................... 383

14.12.13 Viewing remote SFP information .................................................................................................. 384

14.12.14 Viewing extension information ..................................................................................................... 384

14.12.15 Viewing remote environment information .................................................................................... 384

14.12.16 Checking configurations ............................................................................................................... 384

14.13 Maintenance ............................................................................................................................................. 385

14.14 Configuration examples ........................................................................................................................... 385

14.14.1 Examples for configuring RMON alarm group .............................................................................. 385

14.14.2 Examples for configuring LLDP basic functions ............................................................................ 387

14.14.3 Examples for outputting system logs to log host ............................................................................ 390

14.14.4 Examples for managing the RC552-GE (B) remotely .................................................................... 392

15 Batch configuration and management ................................................................................ 395

15.1 Overview .................................................................................................................................................... 395

15.2 Adding a batch configuration task .............................................................................................................. 395

15.3 Enabling batch configuration tasks ............................................................................................................ 398

15.4 Disabling batch configuration tasks ........................................................................................................... 399

16 Alarm management................................................................................................................. 400

16.1 Overview .................................................................................................................................................... 400

16.1.1 Alarm status ...................................................................................................................................... 400

16.1.2 Operation status ................................................................................................................................ 400

16.2 Viewing alarms ........................................................................................................................................... 401

16.2.1 Current alarms ................................................................................................................................... 401

16.2.2 Historical alarms ............................................................................................................................... 405

16.3 Alarm filtering ............................................................................................................................................ 408

16.3.1 Adding device-based filtering rules................................................................................................... 408

16.3.2 Adding interface-based filtering rules ............................................................................................... 409

17 Performance management ..................................................................................................... 410

17.1 Overview .................................................................................................................................................... 410

17.2 Performance monitoring service ................................................................................................................ 410

17.2.1 Introduction ....................................................................................................................................... 410

17.2.2 Enabling performance monitoring service ........................................................................................ 411

17.3 Monitoring real-time performance ............................................................................................................. 411

17.3.1 Introduction ....................................................................................................................................... 411

17.3.2 Monitoring real-time performance .................................................................................................... 411

17.4 Configuring performance monitoring tasks ................................................................................................ 413

17.4.1 Introduction ....................................................................................................................................... 413

17.4.2 Configuring single task ..................................................................................................................... 413

17.4.3 Starting collection tasks .................................................................................................................... 416

17.4.4 Stopping collection tasks .................................................................................................................. 416

17.5 Historical performance ............................................................................................................................... 416

Raisecom



Raisecom Technology Co., Ltd. xvi

17.5.1 Introduction ....................................................................................................................................... 416

17.5.2 Viewing historical performance graph .............................................................................................. 417

18 Data center ................................................................................................................................ 419

18.1 Introduction ................................................................................................................................................ 419

18.2 Starting data center ..................................................................................................................................... 419

18.3 Device operation management ................................................................................................................... 420

18.3.1 Upgrade ............................................................................................................................................. 420

18.3.2 Periodical upgrade............................................................................................................................. 422

18.3.3 Backup .............................................................................................................................................. 423

18.3.4 Periodically automatic backup .......................................................................................................... 423

19 Appendix .................................................................................................................................. 425

19.1 Terms .......................................................................................................................................................... 425

19.2 Abbreviations ............................................................................................................................................. 432

19.3 Alarm list .................................................................................................................................................... 437

19.4 Performance list ......................................................................................................................................... 442

Raisecom


Element Management) 1 Overview

Raisecom Technology Co., Ltd. 1

1 Overview

This chapter describes functions and features of the iTN201 EMS, including the following

sections:

Functions

Features

Device introduction

Network management protocols

1.1 Functions The iTN201 EMS provides a device-like Graphical User Interface (GUI), reflecting the

topology connections and device status in real time and providing concentrated and

convenient monitoring and maintenance modes.

You can manage the iTN201 just by installing the NView Network Node Management (NNM)

system and configuring parameters, such as Simple Network Management Protocol (SNMP)

information and the Trap target address. Therefore, iTN201 EMS can provide functions such

as configuration management, alarm management, performance management, as well as

operation and maintenance.

1.2 Features

1.2.1 Great topology management

Manual topology layout. You can create all types of topology nodes and links using the

topology components provided by NView NNM to structure a logical topology view

caters for self-management need.

Automatic topology layout. Device detection function of NNM supports detecting

managed device in assigned network segment or IP segment. You can add manageable

device by this function. Structuring network topology and greatly increase system

deployment efficiently.

Real-time device offline detection. NView NNM system monitors the offline status of

devices on different levels and with different grades using the device offline detection

service. The offline status of devices is notified by alarms.

Raisecom




In support of topology tree nodes and topology figure nodes to take real-time linkage

selection

Quick search and localization of node. You can search and locate a node under

management quickly using the name or IP address of it.

Real-time alarm status mapping. The system will highlight alarming node in different

colors to demonstrate the highest alarm level the node is suffering. Detailed information

of the alarm can be examined conveniently and quickly.

Various automatic layout patterns, such as tree layout, star layout, grid layout, and etc.

Network topology browsing navigation function. The system provides you with network

topology browsing navigation function along with graphic operations on network

topology like zoom, recover, pre-view, and etc.

Shortcut operation pattern. The system provides shortcuts for operations like subnet

unfold, nodes move, copy, and etc.

1.2.2 Flexible security management

Multi-Level, Multi-Authority and Multi-Domain Security Control Strategy. The system

supports differentiate administrative authorization based on device. Tailored to practical

need of network management, the strategy grants different level of authority over

different network devices to different customers.

Customized Management Domain. The network management tasks for network

administrators can be proportioned according to device functions. The strategy can be

applied to satisfy the internal management policy of an operation and maintenance

department of several people or several dozens of people.

IP Address-Based "User Access Control List". You cannot log in the system through

hosts with IP addresses which are not in the "User Access Control List". The system can

also configure "Login time" restrict, users out of "Login time" cannot login in.

The "Illegal Login Authentication" function will lock up the customer if log on system

by wrong username and password over system setting times.

Support "Multi-user login mode" and "Single-user login mode". In "Single user login

mode", only the super administrator can login the system so as to manage system in

upgrade and maintenance.

System/Device Operation Log. Detailed system operation log and device operation log

facilitate the monitoring and tracing of the working status of network administrator.

1.2.3 Complete alarm management

In alarm management, the network devices with fault or abnormal operation need to report the

alarm events to the operation and maintenance personnel in a way so as to remove the fault

timely and effectively and ensure overall network operation quality. The NView NNM system

supports to parse the various alarms of the iTN201, provides the detailed information of alarm

events, accurately locates the fault, and assists administrators to remove fault within the

shortest possible time and ensure the unobstructed network operation.

The NView NNM system alarm management supports the following functions:

Alarm state management: supports confirming/cancelling operations, support clearing

alarms, and viewing alarm state and duration.

Level of alarm: the alarm can be divided into five types according to the different order

of severity. In the order of the most serious to the least serious, they are:

Raisecom




− Critical alarm (Critical): The highest alarm level, which causes service interruption.

Marked in red: .

− Major alarm (Major): Service continues while the considerably declined performance

affects service operation. Marked in orange: .

− Minor alarm (Minor): Alarm event occurs but not affect service operation. Marked in

yellow: .

− Warn alarm (Warn): The service is operating in order. Only an ordinary problem

occurred. Marked in blue: .

− Unknown alarm (Unknown): Alarm events that cannot be recognized. Marked in light

grey: .

Alarm group: the system provides real-time groups monitoring function to current alarm,

by which to divide and show the received alarm events into groups according to

specified conditions as well as provide level statistics and location functions.

Alarm filtering: you can define filtering policy to specify the alarm of some type in a

certain position not to be received by the NView NNM system. All filtered alarms can be

specified whether to be stored to the database.

Alarm statistics: support current alarm statistics and historical alarm statistics, used to

calculate the number alarms of all levels on various NEs, easy to grasp the distribution

status of alarms.

Alarm blinking: support blinking the LED for critical alarms.

1.2.4 Perfect performance management

In performance management, you can monitor and analyze the network devices connectivity,

bit error rate, traffic, and other performance data to confirm the stability of service operation,

even except the fault to occur according to the declined service quality found through

performance data.

Combined with the NView NNM performance management components, the iTN201 EMS

provides the iTN201 performance data collection, performance chart/data viewing and other

functions. Support to collect the device operation performance data and view operation

situation in graphical interface so that the operation and maintenance personnel understands

the current and past network load, flow and other operation situation as well as provides the

basis for the network fault warning, troubleshooting and network optimization.

Performance management can be used for all aspects of operation and maintenance work.

In network deployment, performance components can be used to monitor device

performance, help the operation and maintenance personnel understand operation

situation of network devices and find the operating problems in deployment so as to

improve the overall efficiency of the network deployment.

In early network operation, performance management can be used to monitor key device

performance, find the bottlenecks in network operation, so as to take network

optimization at an early stage and ensure the network to restore stable state rapidly after

network deployment.

In the process of network operation and maintenance, real-time performance monitoring

can confirm the device operating state and historical performance monitoring can help

the operation and maintenance personnel take statistics and monitor the network

operating state based on performance threshold alarms.

In the process of increasing network services, operation and maintenance personnel will

pay attention to performance thresholds through performance alarm before fault happens

Raisecom




so as to avoid the service problem caused by performance bottlenecks and facilitate the

timely expansion of network.

When a fault occurs, operation and maintenance personnel have been able to analyze the

possible fault reasons according to historical performance chart and data and speed up

the troubleshooting.

After troubleshooting, operation and maintenance personnel will monitor real-time

performance chart and data to confirm the real-time working state of devices and ensure

that the fault has been completely removed.

1.2.5 Excellent operation and maintenance feature

The NView NNM system uses the data center to provide the operation and maintenance

function. The data center component can perform centralized management on upgrade,

backup, recovery, rollback, activation of devices. In addition, it manages the upgrade file,

backup file, and logs generated by various operations and backup. It ensures more convenient

operation, simpler maintenance, and high security of upgrade and backup.

As a new component of NView NNM system, the data center provides:

NE software management

− Support managing multiple software versions through the NE software repository,

and support automatically recognizing files and versions when software is imported.

− Support querying the version, status, and activated time of the NE software.

− Support uploading, downloading, backupping, and activating the NE software.

− Support software file rollback. Support rolling back the software to the one before

upgrade after the data center downloads the software to the NE and activates it.

− Support collecting operation logs, backup logs, and data center logs of the NE

software.

Configuration data management

− Support querying current configuration data about a NE.

− Support collecting and saving current configuration data about a NE for

synchronizing configuration data.

− Support configuring related NE data. Upload configuration data to a NE for applying

NE configurations.

− Support configuring data rollback. After the data center downloads the configuration

data to a NE and activates the data, the configuration data can be rollbacked to the

previous status.

− Support configuring file comparison. Display the differences between two

configuration files with colors.

− Support comparing the configuration file in the data center with the one on the device.

1.3 Device introduction The iTN201 acts as the access node in Raisecom intelligent transport network product line,

and is mainly applicable for Carrier Packet-based Mobile Backhaul (P-MBH) services and

next-generation multi-service access resolutions of the Carrier-grade Ethernet technology. As

a small leased-line access aggregation device, the iTN201 can be installed in the mobile base

and user client.

Raisecom




The iTN201 family includes 2 models, supporting multiple service interfaces and meeting

differentiated user requirements.

iTN201-4GF: provides 4 uplink 100/1000 Mbit/s optical interfaces and up to 12

downlink 100/1000 Mbit/s optical interfaces. In addition, it supports the Ethernet sub-

card, TDMoP sub-card, and clock sub-card.

iTN201-2XG: provides 2 uplink 10 Gbit/s optical interfaces and up to 12 downlink

100/1000 Mbit/s optical interfaces. In addition, it supports the Ethernet sub-card,

TDMoP sub-card, and clock sub-card.

Figure 1-1, Figure 1-2, and Figure 1-3 show the appearance of the iTN201-4GF and the

iTN201-2XG.

Figure 1-1 Appearance of the iTN201-4GF (front panel)

Figure 1-2 Appearance of the iTN201-2XG (front panel)

Figure 1-3 Appearance of the iTN201 (rear panel)

The iTN201-4GF can be equipped with dual Direct Current (DC), dual Alternating

Current (AC), or 1 DC+1 AC power supply redundancy backup. It supports a single DC/AC power supply module.

The iTN201-2XG can be equipped with dual DC power supply redundancy backup. It supports a single DC/AC power supply module only.

The iTN201 must be installed with the fan. Otherwise, it may cause performance degradation and service interruption.

1.4 Network management protocols The iTN201 EMS supports SNMP V1, SNMP V2c, and SNMP V3 and supports analyzing

Trap information sent by the iTN201.

Raisecom




SNMP structure is divided into two parts: Agent and Network Management System (NMS).

Agent is the party to be managed in SNMP network while NMS is the party to manage SNMP

network. Agent and NMS can communicate with each other by transmitting SNMP packets

through User Datagram Protocol (UDP).

Access control authority is an important part in SNMP. The following is the description on

two access control authorities of the iTN201.

Community-based access control

SNMP Agent puts forward the concept of the community in order to prevent itself and the

managed Management Information Base (MIB) from illegal (unauthorized) access. When

using SNMP V1 and SNMP V2c for community authentication, the SNMP packets that do not

meet device approved community will be discarded.

Communities can have read-only or read-write access authorities. The only-read community

can only query the device information, while the read-write community can query device

information and configure the device.

User-based access control

SNMP V3 adopts the User-based Security Model (USM) and View-based Access Control

Model (VACM).

USM puts forward the concept of access group: one or more users correspond to an access

group. Each access group should set the appropriate read and write views. Users in an access

group have authority in the view. The access group, whose user sends requests, must have the

authority corresponding to their requests. Otherwise, the requests will not be accepted.

By managing the MIB views available for a user, the VCAM is used to decide the MIB object

that can be accesses by the user.

Raisecom


Element Management) 2 Network management


2 Network management

This chapter describes how to connect to the NView NNM system, including the following

sections:

Overview of network management modes

Configuring in-band management

Configuring out-of-band management

Configuring SNMP community

Configuring Trap target address

Checking configurations

2.1 Overview of network management modes

2.1.1 In-band management

In in-band management mode, the network management information and user's service

information are transmitted through the same link.

In-band management has the following advantages:

Flexible networking applications

Less restrictions on locations

Higher channel security (compared with out-of-band management)

However, in in-band management mode, network management information occupies service

channels. If service channels are not connected, the iTN201 EMS cannot manage the iTN201

remotely. Figure 2-1 shows the in-band management networking application.

Raisecom




Figure 2-1 In-band management

2.1.2 Out-of-band management

In out-of-band management mode, the network management information and user's service

information are transmitted through the different logical channels.

In out-of-band management mode, the iTN201 EMS can manage the iTN201 even service

channels fail and the network management information is transmitted more reliably. However,

in out-of-band management, more restrictions are put on locations for establishing the

network management network. The cost for establishing Data Communication Network (DCN)

is higher.

Before managing the iTN201 through the iTN201 EMS, you should configure the IP address

of the SNMP port for the managed device. You must ensure the route between the NView

NNM system and device is reachable. In addition, you need to configure related parameters of

SNMP community and Trap destination address properly. Figure 2-2 shows the out-of-band

management networking application.

Figure 2-2 Out-of-band management

2.2 Configuring in-band management In in-band management mode, the NView NNM system manages the iTN201 through its

uplink interfaces. In this case, you need to assign management VLANs and configure the

management IP address. For example, to configure in-band management, where the IP address

is set to 192.168.1.2/255.255.255.0 and the management VLAN ID is set to 1, follow these

steps:

Step 1 Connect to the iTN201 through the Console interface and then enter global configuration

mode in the Command Line Interface (CLI).

Raisecom>enable

Password:

Raisecom#

Raisecom




Raisecom#config

Raisecom(config)#

Step 2 Configure the management IP address.

Raisecom(config)#interface ip 0

Raisecom(config-ip)#ip address 192.168.1.2 255.255.255.0 1

Raisecom(config-ip)#exit

Raisecom(config)#exit

Raisecom#write

2.3 Configuring out-of-band management In out-of-band management mode, the network management information and user's service

information are transmitted through different logical channels. In this case, you need to

configure out-band management IP address. For example, to configure the out-of-band

management, where the IP address of the SNMP interface is set to 192.168.1.2/255.255.255.0,

follow these steps:

The in-band management IP address and the out-of-band management IP address should be in different network segments.


mode in the CLI.

Raisecom#config

Step 2 Configure the out-of-band management IP address.

Raisecom(config)#management-port ip address 192.168.2.1 255.255.255.0


Raisecom#write

2.4 Configuring SNMP community By default, the system establishes a read-only community and a read-write community. The

read-only community is named as Public while the read-write community is named as Private.

To modify the default names and authorities of communities, follow these steps:

Raisecom





mode in the CLI.

Raisecom>enable

Password:

Raisecom#

Raisecom#config

Raisecom(config)#

Step 2 Configure the SNMP read-only and read-write communities.

Raisecom(config)#snmp-server community public1 ro

Raisecom(config)#snmp-server community private1 rw


Raisecom#write

2.5 Configuring Trap target address To ensure that the NView NNM system receives and processes alarms and events properly,

you should configure the Trap target address.

For example, to configure the Trap target address (192.168.1.100), follow these steps:


mode in the CLI.

Raisecom>enable

Password:

Raisecom#

Raisecom#config

Raisecom(config)#

Step 2 Configure the Trap target address and SNMP version.

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

162


Raisecom#write

Raisecom




2.6 Checking configurations

No. Item Description

1 Raisecom#show snmp community Show SNMP community configurations.

2 Raisecom#show snmp host Show Trap target address configurations.

Raisecom


Element Management) 3 NView NNM


3 NView NNM

This chapter describes common functions of the NView NNM system, including the following

sections:

System monitoring

Starting/Stopping NView NNM system

Topology management

Shortcut menus

Synchronizing NE data

iTN201 EMS

Device properties

For details about how to installing the NView NNM system, please see NView NNM Installation Guide and NView NNM Upgrade Guide.

3.1 System monitoring The NView NNM system provides system monitoring, which is used for monitoring various

services of the NView NNM system. System monitoring supports enabling services in a

proper order and based on service relationship. In addition, it supports rebooting services,

reporting alarms, and saving logs when services are in anomaly.

3.1.1 Service management

The following are some service management functions of system monitoring:

Enabling and disabling all services

Enabling and disabling a single service

Configuring service enabling mode

Configuring the IP address and the port information of the northbound interface

Managing the License information of the NView NNM system

Raisecom




3.1.2 Monitoring

The following are some monitoring functions of system monitoring:

Monitoring service operation status

Viewing the NView NNM database information

Viewing system resource information

Viewing the NView NNM component version information

3.1.3 Other management functions

The following are other management functions of system monitoring:

Recording user login information logs

Recording management operation logs

Recording service anomaly information logs

Supporting alarm sending

3.2 Starting/Stopping NView NNM system To start the NView NNM system, follow these steps:

Step 1 Start the NMS Server.

Step 2 Start the NMS Control (system monitoring client) and verify that the InstanceServer is in

Running status.

Step 3 Start the Client (the NView NNM client).

To stop the NView NNM system, follow these steps:

Step 1 Stop all services and the Client.

Step 2 Stop the NMS Control (system monitoring client).

Step 3 Stop the NMS Server (system monitoring server).

3.2.1 Starting NMS Server

Double-click the NMS Server shortcut on the desktop to enable the NMS Server, as shown in

Figure 3-1.

Raisecom




Figure 3-1 Starting the NMS Server

By default, the enabling mode of the NMSServer is set to auto. The system monitoring service can be manually started after the operation system is started. For the system monitoring provided by the NView NNM, the NView NNM platform service is automatically started by default. If the enabling status of the NView NNM platform service is set to manual, you need to manually start it in the NMS Control after starting the NMS Server. Otherwise, the NView NNM Client cannot be used properly. The enabling status of all NView NNM services can be set to auto. In auto mode, all services are started when the NMS Server is started. To set the enabling status of a NView NNM service to auto, you should log in to the NMS Control, right-click a service, and then choose Set Start Model > Automatic.

3.2.2 Viewing enabling status of platform service

Step 1 Double-click the NMS Control shortcut on the desktop and use the user name and the

password of the super administrator to log in to the NMS Control.

Step 2 View the enabling status of the platform service. If the platform service is stopped, right-click

the service and then choose Start Process to start the platform service.

3.2.3 Starting NView NNM Client

After successfully starting the NView NNM platform service and database service, double-

click the Client shortcut on the desktop to start the NView NNM Client. When the Client

starts to connect the NMS server, the system will provide two modes "Choose server start"

and "Not choose server start".

Raisecom




For the first running, the super administrator user name is set to administrator, and the password is set to raisecom by default. We recommend modifying the password immediately after logging in to the NView NNM Client to ensure system security. For the first time to run the client, it may prompt that "The client is incomplete, immediate repair?" Click OK to perform repair operation automatically. After successful repair, it will prompt that "The client resource files have been created, immediately start the client?" Click Yes to start the client again. For detailes about the two modes for enabling the NView NNM Client provided by the system, see NView NNM Operation Guide.

Starting NView NNM Client with selecting a server

By default, the NView NNM Client runs with selecting a server. After double-click the Client

shortcut on the desktop, a Choose Server window is displayed, as shown in Figure 3-2. Select

a server and then click OK to enter the NView NNM Client login interface.

Figure 3-2 Selecting a server

Starting NView NNM Client without selecting a server

In "Not choose server start" mode, double-click the Client shortcut on the desktop to directly

move to the Login window, as shown in Figure 3-3. In this mode, the NView NNM Client

will use the IP address of the default server for login.

Raisecom




Figure 3-3 NView NNM Client login interface

Enter the user name and the password correctly and then click OK to enter the topology

window of the NView NNM Client.

3.2.4 Stopping NView NNM Client

Before stopping NView NNM services, you should stop the NView NNM Client. To stop the

NView NNM Client, perform one of the following:

Choose System > Exit from the system menu and then click Yes at the displayed dialog

box.

Click at the upper right corner of the main interface of the NView NNM Client and

then click Yes at the displayed dialog box.

3.2.5 Stopping all NView NNM services

To stop NView NNM service, follow these steps:

Step 1 Double-click the NMS Control shortcut on the desktop and log in to the NMS Control with

the user name and the password of the super administrator.

Step 2 Choose System > Stop All NMS Services and a dialog box is displayed, as shown in Figure

3-4.

Step 3 Click Yes.

Raisecom




Figure 3-4 Stopping NView NNM services

3.2.6 Stopping NMS Server

After enabling the NMS Server, you can stop it by stopping NMSServer in the operation

system.

On the Windows desktop, choose Start > Control Panel > Administrative Tools > Services.

Right-click NMS Server and then choose Stop.

3.3 Topology management Topology management supported by the NView NNM system includes topology view

management and topology tree management. Topology is a main view containing all subnets

and NEs, where you can realize topology management on subnets, symbols, NEs, and links.

You can enter the topology by logging in to the NView NNM Client, as shown in Figure 3-5.

Figure 3-5 Topology

1 Topology tree 2 Menu bar and tool bar 3 Topology view

4 Legend and property 5 Current alarm list –

Raisecom




Nodes on the topology view and the topology tree are cascaded. If you select a node at the topology tree, the node is also selected at the topology view.

3.3.1 Topology view

Topology view

Topology view displays nodes and links between nodes in a NE/subnet in a form of graph.

The upper area is the tool bar and the menu bar of the topology view, while the current alarm

list is at the bottom. When you select another node in the topology view, the displays in the

current alarm list are changed. The right side to the topology view lists legends and properties

of the selected node.

The NView NNM V5 provides the legend. The legend describes graphs and states of nodes in the topology view. Choose System > Display > Right > Legend to open the Legend panel, where the related legend of the select node is displayed.

Nodes in topology view

Each node in the topology view consists of the icon, text, color, and widget. The icon is used

to distinguish subnets, NEs, remote cards and chassis. The text is used to display the NE name,

device NAME, and IP address. The color is used to display the current highest alarm level.

Black refers the node is offline.

Icon: the one selected when creating a node.

Text: displayed below the icon. It can be set to the NE name, device NAME, and IP

address.

Color: for subnets and devices, 5 color is used to indicate alarm status. The color is

consistent with the system alarm color.

− For a subnet, the color is consistent with the one of the node which has the highest-

level alarm in the subnet.

− For a NE, the color is consistent with the one of the highest-level alarm in all current

alarms.

− The node is displayed in green when no alarm is generated on it while the node is

displayed in black when it is offline.

Widget: different widgets represent different statuses, such as alarm confirmation, offline

status, and management status.

Table 3-1 Widgets

Widget Name Description

Already binding customers The node is related to the customer information.

Already set the alarm filtering The widget appears when an alarm filtering rule is added to the

iTN201. The widget disappears when an alarm filtering rule is

deleted.

Raisecom




Widget Name Description

Alarm unconfirmed The widget appears if there is an unconfirmed alarm. The widget

disappears when all alarms are confirmed.

Already binding customers The widget appears when the iTN201 is related to a customer.

The widget disappears when all customers related to the iTN201

are deleted.

Alarm LED The color of the alarm LED on the device is identical to the one

of the highest-level alarm.

Communication failure The device cannot Ping through.

In synchronization The node is performing synchronization. The NView NNM is

synchronizing resource information of the device.

Resource synchronizing failed The node fails to synchronize resources. The NView NNM fails

to synchronize resource information of the device.

Deployment performance

collection The node is displayed with a performance collection task.

Creating subnets in topology view

Before deploying NEs in a topology, you should partition the subnet properly. Besides

reflecting the real communication network topology structure, the NView NNM topology

should facilitate performing routine maintenance.

To create a subnet in the topology view, follow these steps:

Step 1 Right-click at the blank area of the NView NNM topology view/customized view/subnet

topology, and then choose Add > Add subnet. The mouse state is changed to "+".

Step 2 Click the place where the subnet icon to be displayed and a dialog box is displayed, as shown

in the following figure. Configure parameters and then click Save.

Step 3 After creation, a dialog box appears, asking, continue to add? Click Yes to create another

subnet. Otherwise, click No.

Raisecom




Parameter Description

Symbol name Name of the subnet. Up to 100 characters are allowed.

Remark Descriptions of the subnet. Up to 100 characters are allowed.

Display name Subnet type selected by clicking the type on the left topology tree

Creating NEs in topology view

A NE can be manually added or be automatically discovered by the NView NNM system.

This guide describes how to create a NE manually only. For details about how to automatically discover a NE, see NView NNM Operation Guide.

To create a NE at the NView NNM topology view, follow these steps:

Step 1 Right-click at the blank area of the NView NNM topology view/customized view/subnet

topology, and then choose Add > Add device. The cursor state is changed to "+".

To add a NE, you can also perform one of the following:

Click at the tool bar of the topology view, and then choose Add device. From the menu bar of the topology view, choose Edit > Add > Add device.

Raisecom




Step 2 Click the place where the NE icon to be displayed and a dialog box is displayed, as shown in

the following figure.

Step 3 Configure parameters and then click Save.

Step 4 After creation, a dialog box appears, asking, continue to add? Click Yes to create another NE.

Otherwise, click No.


Base Info

Net name Select a subnet for the NE by clicking .

By default, the subnet that initiates adding the NE is selected.

Name NE name. Up to 100 characters are allowed.

IP address IP address of the NE in dotted decimal notation

Type Device model selected at the left topology tree

After configuring the IP address, click Check Type to display the

device model of the IP address. Select the device type based on the

check result.

Raisecom





Purpose Purpose of the NE

Unspecified Customer access Key customer access Community convergence Office convergence Repeater transmission

Supplier Information about the NE vendor. Up to 100 characters are allowed.

Remark Remarks of the NE. Up to 100 characters are allowed.

Management Information

Read Community Name of the NE SNMP read community. Up to 32 characters are

allowed.

Write Community Name of the NE SNMP write community. Up to 32 characters are

allowed.

Retry Retry times of the NE offline detection. It ranges from 1 to 5. By

default, it is set to 1.

Timeout(sec.) SNMP timeout of the NE. It ranges from 1s to 30s. By default, it is

set to 3s.

If the time expires, the NView NNM system believes that the SNMP

management operation fails.

SNMP Port SNMP destination port ID. It is an integer ranging from 1 to 65535.

The SNMP destination port ID must be identical to the SNMP Rx

port ID used by the NE. Otherwise, the NView NNM system cannot

manage the device.

By default, the SNMP destination port ID is set to 161. We do not

recommend modifying it.

SNMP Version SNMP version of the NE

SNMP V1 SNMP V2c SNMP V3

By default, it is set to SNMP V2c.

SNMP V3

Parameters

Configure related parameters when the SNMP V3 is selected.

Click the SNMP V3 parameters text box and then click to

configure the following parameters.

Customer Name: SNMP V3 user name of the device Security Level: SNMP security level modes of the device,

including noAuth,noPriv, Auth,noPriv, and Auth,Priv. Authority Protocol: authentication type of the device, including

MD5 and SHA. Authority Password: SNMP authentication password. Privacy Protocol: encryption type of the device, including DES

and AES Privacy Password: SNMP encryption password

Raisecom





Extend Info

GRID_ID Grid ID of the NE

GRID_NAME Grid name of the NE

Offline Detecting

Offline detecting Enable/Disable NE offline detection.

Checked: enabled Unchecked: disabled

By default, offline detection is enabled.

Polling protocol Detection mode used by offline detection

ICMP Ping SNMP Ping

By default, it is set to ICMP Ping.

Polling interval Offline detection period

30 Seconds 60 Seconds 5 Minutes 15 Minutes 30 Minutes 60 Minutes

By default, it is set to 30 minutes.

Project Information

Area Name Information about the area where the NE is. Up to 100 characters

are allowed.

Project Information about the project where the NE is. Up to 100 characters

are allowed.

Room Information about the machine room where the NE is. Up to 100

characters are allowed.

Shelf Information about the rack where the NE is. Up to 100 characters

are allowed.

Integrator Information about the NE contractor. Up to 100 characters are

allowed.

Maintenance Person

Maintenance

Person Select a maintenance person by clicking .

TEL Automatically displayed based on the selected maintenance person

Address Automatically displayed based on the selected maintenance person

Raisecom




3.3.2 Topology tree

Topology tree

The topology tree displays subnets, NEs, and symbols in a tree-like structure. Subnets,

devices, chassis, and cards are displayed in a hierarchical mode. Subnets have a higher level

than NEs. With the topology tree, you can directly view the hierarchical relationship, alarm

status, and offline status of all subnets and devices.

Icons on topology tree

Table 3-2 describes icons on the topology tree.

Table 3-2 Icons on the topology tree

Icon Name Description

Sort Forward/sort

Backward

Sort forward/backward based on digits and letters.

Expand All/Collapse All Expand/Collapse the topology tree.

Quick Search Enter a key word to search the node at the topology tree.

Search the matched node at the topology tree based on the

entered key word.

□+ Expand Expand nodes at the topology tree.

□一 Collapse Collapse nodes at the topology tree.

Offline symbol When the symbol is displayed at the upper right corner of a

node, it indicates the node is in off-line state.

3.4 Shortcut menus

The following table shows right-click shortcut menus supported by the iTN201 EMS.

Function Description

Locknode/Unlock

coordinate Lock/Unlock the coordinate of the NE in the topology view.

Edit Edit NEs.

Edit properties: edit the device properties of the NE. Copy to: copy the NE to another subnet. Move to: move the NE to another subnet.

Raisecom




Function Description

Modify IP Modify the IP address of a NE, which is in dotted decimal

notation.

When modifying the IP address of a NE, ensure that the

NE type are consisitent. Otherwise, the NE information will be lost.

When you modify the IP address of a NE, only the one at the NView NNM system side is modified. However, the one at the device side will not he modified.

Delete Delete the NE.

View Properties View the device properties of the NE.

Add to custom view Add the NE to a custom view.

Resource

synchronization

Synchronize information of the NE.

NE management Manage the device through the iTN201 EMS.

Alarm management Manage the alarm information of the NE.

Alarm view: view alarm information. Alarm filtering: filter alarm information.

Related Resources Display related resources of the NE.

Chassis list List of central office card Remote device list Port list

Performance

Management Execute performance management on the NE.

Performance Graph: display the performance graph of the NE. Performance Configuration: configure performance

management on the same type resources.

Tools Provide related tools.

ICMP Ping Native Ping SNMP Ping Telnet MIB Browser

3.5 Synchronizing NE data After a NE is created, the NView NNM system will automatically perform synchronization.

The NE will synchronize resources of the device and ports. If device configurations are

changed, or you need to manually synchronize NE data, you should synchronize NE data in

advance.

Raisecom




When device configurations are changed, data contained by the NView NNM system are

inconsistent with the ones on the device. Therefore, you can perform synchronization to

collect the latest information and update the topology.

3.5.1 Initiating resource synchronization in topology

Step 1 In the main view or the subnet topology, right-click the NE that needs to perform

synchronization, and then choose Resource synchronization.

Step 2 A dialog box appears, saying, Synchronization command has been sent! And then click OK.

Step 3 A icon appears above the NE, which indicates the NE is performing resource

synchronization.

Step 4 Resource synchronization is finished when the icon disappears.

Resource synchronization can also be initiated through inventory management. For details, see NView NNM Operation Guide.

3.6 iTN201 EMS

3.6.1 Access methods

To enter the EMS, perform one of the following:

In the NView NNM topology view, right-click a node and then choose NE Management,

or directly double-click the node to enter the NE management view.

On the NView NNM topology tree, right-click a node and then choose NE Management,

or directly double-click the node to enter the NE management view.

3.6.2 View descriptions

Figure 3-6 shows the initial iTN201 EMS view.

Raisecom




Figure 3-6 iTN201 EMS view

1 Device list 2 Action list

3 Config panel –

The main interface of the iTN201 EMS consists of 3 parts:

Device list: list the device name of the iTN201. By default, the device name is the IP

address of the device.

Action list: a tree-like list at the left side of the iTN201 EMS, which lists all functions

supported by the iTN201. By double-clicking a feature in the action list, you can

configure it at the right area.

Config panel: when you select a feature from the left action list, related configuration

items are displayed at this area. Therefore, you can configure the iTN201 at this area.

Figure 3-6 shows the interface displayed by choosing Device Management > Device

View from the action list.

− Device View: display the front panel of the iTN201.

− Basic Info: you can view and configure information about the iTN201, such as the

name and purpose.

− Current Alarm: current alarms generated on the iTN201 are displayed after you

clicking Refresh.

Common operations at the Config panel area are shown as:

Addition

Deletion

Modification

View

Reset

This guide just describes how to initiate operations by clicking buttons on the configuration

interface. If there is no button on the configuration interface, you can configure an item

through the right-click menu or configuration menu.

Raisecom




The iTN201 does not support configuring items in batch. When you delete/modify items in batch, configurations may fail. When you enter a parameter at a text box, you should note the following matters: If a parameter is displayed in green after it is typed at a text box, it indicates that

the parameter is legal in terms of range. However, it does not indicate that the parameter is legal in terms of configuration.

If a parameter is displayed in red after it is typed in a text box, it indicates that the parameter is illegal in terms of range. You need to modify it.

3.7 Device properties

3.7.1 Editting device properties

The NView NNM system may fail to manage the iTN201 if the modified SNMP version/community parameters are inconsistent with the ones on the iTN201. Therefore, perform this operation with care.

Step 1 Right-click the NE to be edited at the network topology and then choose Edit > Edit

Properties from the right-click menu.

Step 2 A dialog box appears, as shown below. The following table describes items at the dialog box.

Step 3 After configurations, click Save.

Raisecom





Project Information

Area name Modify the area where the NE is.

Station Modify the station information of the NE.

Project Modify the project information of the NE.

Room Modify the machine room information of the NE.

Shelf Modify the rack information of the NE.

Integrator Modify the integrator information of the NE.

Base Info

NE NAME Modify the name of the NE. By default, the NE name is set to the

IP address of the device.

Purpose Select a device purpose.

Unspecified Customer access Key customer access Community convergence Office convergence Repeater transmission

Remark Modify remarks of the NE.


Read Community Modify the read community of the NE.

Write Community Modify the write community of the NE.

Retry Modify the retry times. It ranges from 1 to 5.

Timeout(sec.) Modify the timeout. It ranges from 1 to 30s.

SNMP Port Modify the SNMP interface ID. It ranges from 1 to 65535. By


SNMP Version Select a SNMP version.

SNMP V1 SNMP V2c SNMP V3

Extend Info

GRID_ID Configure the grid ID of the NE.

GRID_NAME Configure the grid name of the NE.

Offline Detecting

Offline Detecting Enable/Disable NE offline detection.

Checked: enabled Unchecked: disabled

Raisecom





Polling Protocol Select a detection mode.

ICMP Ping SNMP Ping

Polling Interval Select a polling interval.

30 Seconds 60 Seconds 5 Minutes 15 Minutes 30 Minutes 60 Minutes

Maintenance Person

Maintenance Person Modify information about the maintenance personnel.

TEL Modify the telephone number of the maintenance personnel.

Address Modify the address of the maintenance personnel.

3.7.2 Viewing device properties

Step 1 Right-click the NE to be viewed at the network topology and then choose View Properties

from the right-click menu.

Step 2 Device properties are displayed at the right Property dialog box. The following table describes

items at the dialog box.


Index

ID Display the ID of the NE.

Base Info

Net Name Display the subnet where the NE is.

NE NAME Display the NE name.

IP Address Display the IP address of the NE.

Type The NE model is displayed as iTN201-4GF.

MAC Address Display the MAC address of the NE.

Subnet Mask Display the subnet mask of the NE.

Purpose Display the device purpose.

Supplier Display the supplier of the NE.

Up Stream Rate List Display the uplink rate supported by the NE.

Sending KeepAlive Display whether KeepAlive is enabled on the NE.

Raisecom





K.A. Interval (Sec.) Display the interface for sending the KeepAlive message. The

unit is set to second.

Last K.A. Received Display the time when the KeepAlive message is sent.

Software Version Display the software version of the NE.

Hardware Version Display the hardware version of the NE.

Manage Mode Display the management mode of the NE.

Web Managed URL Display the Web management URL of the NE.

Last Sync. Time Display the last synchronization time of the NE.

Cluster Identity Display the identity of the NE in the cluster.

Creator Display the creator of the NE.

Creation Time Display the time when the NE is created.

Update User Display the update person of the NE.

Update Time Display the update time of the NE.

Serial NO. Display the serial number of the NE.

Remark Display remarks of the NE.

Project Information

Area Name Display the area where the NE is.

Station Display the station where the NE is.

Project Display the project information of the NE.

Room Display the machine room information of the NE.

Shelf Display the rack information of the NE.

Integrator Display the integrator information of the NE.


Read Community Display the read community of the NE.

Write Community Display the write community of the NE.

Retry Display the retry times of the NE.

Timeout(sec.) Display the timeout of the NE.

SNMP Port Display the SNMP interface ID.

SNMP Version Display the SNMP version.

Extend Info

GRID_ID Display the grid ID of the NE.

GRID_NAME Display the grid name of the NE.

Raisecom





Manage VLAN Display the management VLAN ID of the NE.

Customer VLAN Display the inner VLAN ID of the NE.

Outer VLAN ID Display the outer VLAN ID of the NE.

Uplink Switch Display the uplink switch.

Uplink Port Display the uplink interface.

Uplink Circuit Display the uplink circuit information.

Offline Detecting

Offline Detecting Display whether the NE is enabled with offline detection.

Polling Protocol Display the mode for performing offline detection.

Polling Interval Display the interface for performing offline detection.

Maintenance Person

Maintenance Person Display the information about the maintenance person.

TEL Display the telephone number of the maintenance person.

Address Display the address of the maintenance person.

Raisecom


Element Management) 4 Basic configurations


4 Basic configurations

This chapter describes basic configurations and configuration procedures of the iTN201,

including the following sections:

Configuring login users

Configuring system information

Upgrade/Backup

Configuring time management

Configuring interface management

Saving configurations

Rebooting the device

Deleting configurations

4.1 Configuring login users You can log in to and configure the iTN201 by connecting it to a PC through the Console

interface and entering the user name and password, after the iTN201 is booted for the first

time.

By default, both the user name and password of the iTN201 are set to raisecom.

If you configure an IP address for the SNMP interface or other service interfaces of the

iTN201, any remote user can log in to the iTN201 through Telnet or access the network by

establishing a Point to Point Protocol (PPP) connection with the iTN201. Obviously, it is

unsecure for both the iTN201 and network. Therefore, you should create users and set the

passwords and authorities for the iTN201 to manage login users.

4.1.1 Adding login users

Step 1 From the Action List of the iTN201 EMS, choose SNMP Management > Advanced MGT >

User Config.

Step 2 Select the User Table tab at the User Config area and then click Add.

Raisecom




Step 3 A dialog box appears, where you can configure login users. The following table describes


Step 4 After configurations, click Apply.


User Name Configure the user name, which is a string of 1 to 16 characters.

New Password Configure the password, which is a string of 8 to 16 characters.

Confirm Password Re-enter the password.

User Priority Configure the user priority, which ranges from 1 to 15.

4.1.2 Modifying passwords of login users


User Config.

Step 2 Select the Change Enable Password tab at the User Config area.

Step 3 A dialog box appears, where you can modify the password. The following table describes




Old Password Enter the original password.

New Password Enter the new password, which ranges from 8 to 18 characters.

Confirm password Re-enter the new password.

4.1.3 Configuring priority rules for users performing commands


User Config.

Step 2 Select the User command config table tab at the User Config area and then click Add.

Step 3 A dialog box appears. The following table describes items at the dialog box.



User Name Configure the user name.

Enter a user name, which ranges from 1 to 16 characters. Click Select and then select a created user name.

UCC Index Configure the User Command Control (UCC) index, which

ranges from 1 to 15 characters.

Raisecom





UCC config type Select a UCC configuration type.

allow: allow the user to execute commands which have higher

priorities. disallow: disallow the user to execute commands which have

lower priorities

UCC first keyword Enter the first keyword of the user command.

UCC second keyword Enter the second keyword of the user command.

4.2 Configuring system information

Step 1 From the Action List of the iTN201 EMS, choose SNMP Management > Base MGT >

RFC1213.

Step 2 Configure the system information at the RFC1213 area. The following table describes items at

the area.



System Contact Configure the contact person information, which ranges from 0 to 255

characters. By default, it is set to [email protected].

System Location Configure the device location, which ranges from 0 to 255 characters.

By default, it is set to World China Raisecom.

System Name Configure the system name, which ranges from 1 to 32 characters. By

default, it is set to Raisecom.

4.3 Upgrade/Backup

4.3.1 Overview

Upgrade

You can upgrade the iTN201 when you need to add new features, optimize original functions,

or resolve BUGs of current software version. The iTN201 EMS supports upgrading the

iTN201 through File Transfer Protocol (FTP), Trivial File Transfer Protocol (TFTP), or SSH

SFTP (SFTP).

Raisecom




Backup

When you need to make the system return to a point, you can back up the configuration file or

system file at the point. This helps avoid losing or damaging the system file when the iTN201

fails.

4.3.2 Upgrading/Backing up system software through FTP/TFTP/SFTP

Before upgrading the system file through FTP/TFTP/SFTP, you should establish a

FTP/TFTP/SFTP environment, where the iTN201 acts as the FTP/TFTP/SFTP client. To

establish the FTP/TFTP/SFTP environment, perform operations as below:

Connect the iTN201 to the FTP/TFTP/SFTP server.

Configure the FTP/TFTP/SFTP server and ensure that the FTP/TFTP/SFTP server is

available and has resources.

Configure the IP address of the FTP/TFTP/SFTP server to ensure that the iTN201 can

access to the FTP/TFTP/SFTP server.

Step 1 From the Action List of the iTN201 EMS, choose SNMP Management > Maintenance >

Upgrade/Backup.

Step 2 Click Add at the Upgrade/Backup area.

Step 3 A dialog box appears. The following table describes items at the dialog box.



Protocol Select the transport protocol used for upgrade/backup.

FTP TFTP SFTP

Operation Type Select an operation.

Upgrade Backup

File Type Select the file to be upgraded/backed up.

system-boot: system software startup-config: configuration file bootstrap: Bootstrap file loggingfile: logging file

IP Version Select the IPv4.

At present, the iTN201 EMS does not support IPv6.

Server Address Configure the IP address of the FTP/TFTP/SFTP server, which is in

dotted decimal notation.

File Name Configure the name of the file to be upgraded/backed up.

User Name Enter the FTP user name. This parameter is available for FTP/SFTP.

Raisecom





Password Enter the FTP password. This parameter is available for FTP/SFTP.

Local File Name Select the local file and enter the file name.

Reserve Device

Config

Select whether to reserve configurations.

True False

By default, it is set to False.

4.4 Configuring time management

4.4.1 Configuring system time

To ensure that the iTN201 can cooperate with other devices, you should configure its system

time and time zone accurately.


Time.

Step 2 Select the System Time tab at the Time area.

Step 3 Configure the system time. The following table describes items at the area.


Parameter Classification Description

Clock

Display Mode

– Select the time display mode.

ClockDisplay_DLFT ClockDisplay_UTC

System Time System time

Year Enter the year, which ranges from 2000 to 2099.

Month Enter the month, which ranges from 1 to 12.

Day Enter the day, which ranges from 1 to 31.

Hour Enter the hour, which ranges from 0 to 23.

Minute Enter the minute, which ranges from 0 to 59.

Second Enter the second, which ranges from 0 to 59.

Time zone

Offset Select the offset direction, which is compared with

Coordinate Universal Time (UTC).

+: offset in east direction -: offset in west direction

Raisecom




Parameter Classification Description

Hour offset Configure the hour offset, which ranges from 0 to 11.

Minute offset Configure the hour offset, which ranges from 0 to 59.

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

After DST is enabled, the time synchronized through Simple Network Time Protocol (SNTP) will be translated to local DST.


Time.

Step 2 Select the Summer Time tab at the Time area.

Step 3 Configure the DST. The following table describes items at the area.


Raisecom





Summer Time

Management

Enable/Disable DST management.

Enable Disable

By default, DST management is disabled.

Only when DST management is enabled and you save the configuration, can you configure the DST offset, start and end time of DST.

Summer Time Offset Configure the DST offset, which is in unit of minute.

Summer Time Start Configure the start time of DST with an accuracy of minute.

Summer Time End Configure the end time of DST with an accuracy of minute.

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

Raisecom




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.

4.4.3 Configuring NTP/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. NTP

transmits data based on UDP, using UDP port 123.

NTP is used to perform time synchronization on all devices with clocks in the network.

Therefore, these devices can provide various applications based on the uniformed time. In

addition, NTP can ensure a very high accuracy with an error about 10ms.

Devices, which support NTP, can both be synchronized by other clock sources and can

synchronize other devices as the clock source.

The iTN201 supports performing time synchronization through multiple NTP working modes:

Server/Client mode

In this mode, the client sends clock synchronization message to different servers. The servers

work in server mode automatically after receiving the synchronization message and send

response messages. The client receives response messages, performs clock filtering and

selection, and is synchronized to the preferred server.

In this mode, the client can be synchronized to the server but the server cannot be

synchronized to the client.

Symmetric peer mode

In this mode, the device working in the symmetric active mode sends clock synchronization

messages to the device working in the symmetric passive mode. The device that receives this

message automatically enters the symmetric passive mode and sends a reply. By exchanging

messages, the symmetric peer mode is established between the two devices. Then, the two

devices can synchronize, or be synchronized by each other.

RFC1361 simplifies NTP and provides Simple Network Time Protocol (SNTP). Compared

with NTP, SNTP supports the server/client mode only.

The iTN201 only supports working as the SNTP client to be synchronized by the server.

(Optional) configuring the IP address of NTP server in server/client mode


Protocol MGT > NTP.

Step 2 Select the Remote NTP server table tab at the NTP area and then click Add.

Step 3 A dialog box appears, where you can configure the IP address of the NTP server. The

following table describes items at the dialog box.


Raisecom





NTP peer associate

identifier

Select the connection identifier of NTP servers.

1 2 3

Up to 3 NTP servers can be configured through the iTN201 EMS.

NTP Peer Address Configure the IP address of the NTP server, which is in dotted

decimal notation.

NTP Version Select a NTP version.

v1 v2 v3

(Optional) configuring the IP address of NTP symmetric peer in symmetric peer mode


Protocol MGT > NTP.

Step 2 Select the Remote NTP server table tab at the NTP area and then click Add.

Step 3 A dialog box appears, where you can configure the IP address of the NTP symmetric peer.

The following table describes items at the dialog box.



NTP peer associate

identifier

Set the connection identifier of the NTP server to 4.

Only one IP address of the NTP peer server can be configured through the iTN201 EMS. If you need to configure a new one, you must delete the old one. However, in CLI, the newly-configured IP address of the NTP peer server always overrides the old one, which means you do not need to delete the old one manually.

NTP Peer Address Configure the IP address of the NTP server, which is in dotted

decimal notation.

NTP Version Select a NTP version.

v1 v2 v3

Raisecom




(Optional) configuring the IP address of SNTP server

SNTP and NTP are mutually exclusive. You cannot configure NTP on the iTN201 if you have configured the SNIP server address on the iTN201, and vice versa.


Protocol MGT > SNTP.

Step 2 Configure the SNTP server address at the SNTP area.


Setting the device clock to the NTP reference clock source

If the iTN201 is set to the NTP reference clock source, you cannot configure the NTP server or NTP symmetric peer, and vice versa.


Protocol MGT > NTP.

Step 2 Select the NTP system variables tab at the NTP area. The following table describes items at

the area.


Raisecom





System mode Set the system mode to MTPMaster.

System stratum Configure the system stratum, which ranges from 2 to 16. By


System clock

reference identifier

Configure the IP address of the system clock server.

127.127.1.0 127.127.1.1 127.127.1.2

4.4.4 Checking configurations

After configurations, perform the following operations on the iTN201 to check configurations.

1. View configurations on the system time and DST.

From the Action List of the iTN201 EMS, choose SNMP Management > Base MGT > Time.

Select the System Time tab and then view configurations on the system time.


Select the Summer Time tab and then view configurations on the DST.

2. View SNTP configurations.

From the Action List of the iTN201 EMS, choose SNMP Management > Advanced MGT >

Protocol MGT > SNTP. And then view SNTP configurations.

3. View NTP configurations.


Protocol MGT > NTP and then select the Remote NTP server table tab. Select a record

where the NTP peer associate identifier is set to 1/2/3 and then click View. A dialog box

appears, where you can view IP address configurations of the NTP server in server/client

mode.


Protocol MGT > NTP and then select the Remote NTP server table tab. Select a record

where the NTP peer associate identifier is set to 4 and then click View. A dialog box appears,

where you can view IP address configurations of the NTP server in symmetric peer mode.


Select the NTP system variables tab and then view IP address configurations of the NTP

system reference clock.

4. View NTP connection information.


Protocol MGT > NTP and then select the Clock filter table tab. Select a record about the

NTP server and then click View. A dialog box appears, where you can view NTP connection

information.

Raisecom




4.5 Configuring interface management Ethernet becomes a significant LAN networking technology because it is highly flexible,

relative simple, and easy to implement. Ethernet interfaces are grouped into the Ethernet

electrical interface and Ethernet optical interface.

The iTN201 supports the previously-mentioned Ethernet interfaces.

4.5.1 Configure basic interface properties

The interconnected devices cannot communicate normally if their interface attributes (such as

duplex mode and speed) are inconsistent, and then you have to adjust the interface attributes

to make the devices at two ends match each other.

Step 1 From the Action List of the iTN201 EMS, choose SNMP Management > Port MGT > Port

List and then select the Port MAU Config table tab at the Port List area.

Step 2 Select a record and then click Modify.

Step 3 A dialog box appears, where you can configure the basic interface properties. The following

table describes items at the dialog box.



Speed

Administrative

Status

Select the speed of the interface.

Auto Negotiate Speed-10M: 10 Mbit/s Speed-100M: 100 Mbit/s Speed-1000M: 1000 Mbit/s Speed-10G: 10 Gbit/s

By default, it is set to Auto Negotiate.

Duplex

Administrative

Status

Select the duplex mode of the interface.

Auto Negotiate: devices on both ends of a link automatically

select the duplex mode by exchanging information. Once

negotiated, they transmit packets in identical duplex mode. Full: receive and send packets simultaneously at any time. Half: receive or send packets at any time

By default, it is set to Auto Negotiate.

4.5.2 Configuring flow control of interfaces

IEEE 802.3x is a flow control method for the full-duplex Ethernet data link layer. After the

client sends a request to the server, the client will send a Pause frame to the server if its

system or the network is congested. The Pause frame can be used to make the server delay

sending data to the client.


List and then select the Port MAU Config table tab at the Port List area.


Raisecom




Step 3 A dialog box appears, where you can configure flow control of the interface. The following




Receiving Flow Control Enable/Disable Rx flow control.

Enable Disable

By default, Rx flow control is disabled.

Sending Flow Control Enable/Disable Tx flow control.

Enable Disable

By default, Tx flow control is disabled.

Force Transmit Enable Enable/Disable force transmission.

Enable Disable

By default, force transmission is disabled.

4.5.3 Enabling/Disabling interfaces


List and then select the Port PHY Config table tab at the Port List area.

Step 2 Select a record and then click Modify. A dialog box appears, where you can enable/disable

the interface.


4.5.4 Configuring SNMP interface

The NView NNM system can manage the iTN201 after you configure the SNMP interface of

the iTN201.

If the NView NNM system has managed the iTN201 through the SNMP interface, the NView NNM system cannot manage the device if you change the IP address of its SNMP interface. The IP address of the SNMP interface must be in different network segment with the in-band management IP address (IP address of the Layer 3 interface).


Management traffic.

Step 2 Select the SNMP Interface tab at the Management traffic area and then click Add.

Step 3 A dialog box appears, where you can configure the SNMP interface. The following table

describes items at the dialog box.


Raisecom





Address type The address type is set to IPv4.

IP Address Configure the IP address of the SNMP interface, which is in dotted

decimal notation.

Address Prefix

length

Configure the prefix length of the IP address, which ranges from 0

to 32 characters.



1. View interface status.

From the Action List of the iTN201 EMS, choose SNMP Management > Port MGT > Port

List and then select the Port PHY Config table tab at the Port List area. Select a record and

then click View. A dialog box appears, where you can view interface status.

2. View flow control configurations.


List and then select the Port MAU Config table tab at the Port List area. Select a record and

then click View. A dialog box appears, where you can view flow control configurations.

3. View configurations on the IP address of the SNMP interface.


Management traffic and then select the SNMP Interface tab at the Management Traffic area.

Select a record and then click View. A dialog box appears, where you can view configurations

on the IP address of the SNMP interface.

4.6 Saving configurations New configurations will be lost when the iTN201 is booted next time, if they are not saved.

Therefore, after configurations, you must save them.


Write.

Step 2 A dialog box appears, asking Now send "Write", continue? Click Yes to save configurations.


4.7 Rebooting the device To reboot the iTN201, perform the following operations:

If new configurations are not saved, they will be lost if you reboot the iTN201. Therefore, perform the operation with care.

Raisecom





Reboot.

Step 2 A dialog box appears, asking Now send "Reboot", continue? Click Yes to reboot the iTN201.


4.8 Deleting configurations To delete configurations of the iTN201, perform the following operations:

All configurations will be deleted if you delete the configuration file. Therefore, perform the operation with care.


Erase.

Step 2 A dialog box appears, asking Now send "Erase", continue? Click Yes to delete configurations.


Raisecom


Element Management) 5 Zero-configuration


5 Zero-configuration

This chapter describes principles and configuration procedures of zero-configuration, as well

as related configuration examples, including following sections:

Introduction

Configuring local zero-configuration

Configuration examples

5.1 Introduction With wide application of the Packet Transport Network (PTN) technology in mobile backhaul

and professional fields, the iTN200 and the iTN100 family will be applied in a large scale.

When a project is to be implemented, the maintenance personnel must configure a great

number of scattered devices. This consumes lots of time and effort. In addition, this may

cause errors and influence the working efficiency.

With zero-configuration, the iTN family can configure parameters, such as the IP address and

default gateway, for remote devices to manage them. In addition, with zero-configuration, you

can activiate some services more quickly.

Working principles of zero-configuration

Figure 5-1 shows the working principles of zero-configuration. At the remote, the iTN can

automatically detect the zero-configuration server once it is powered on and is connected to

the network. Therefore, the iTN can get parameters, such as the management VLAN, IP

address, and gateway, from the zero-configuration and can be automatically discovered by the

NView NNM system. The zero-configuration server at the local responds to the detection

requests of remote devices and configures proper management parameters for them.

As shown in Figure 5-1, the iTN201 supports local zero-configuration and remote zero-

configuration.

Raisecom




Figure 5-1 Principles of local/remote zero-configuration

When working as the zero-configuration server, the iTN201 supports working in directly-

connected and indirectly-connected scenarios. As shown in Figure 5-1, the iTN200 B works

as a directly-connected zero-configuration server while the iTN200 A works as an indirectly-

connected zero-configuration server.

Local zero-configuration

Directly-connected zero-configuration server of the iTN remote device is realized with

extended Operation Administration and Maintenance (OAM) protocol, as shown in Figure 5-2.

Both the local and remote devices support and are enabled with extended OAM protocol. In

addition, the local and remote devices are directly connected. In this case, the local device can

discover the remote device and configure the management IP address and management VLAN

for it.

Raisecom




Figure 5-2 Directly-connected remote zero-configuration

By default, the local device is enabled with extended OAM. After being powered on, the local device will discover remote devices automatically.

Indirectly-connected zero-configuration server of the iTN remote device is realized with

extended Dynamic Host Configuration Protocol (DHCP). As shown in Figure 5-3, the iTN

remote devices work as the DHCP Clients and iTN200 A works as the DHCP server. After

being powered on, the iTN remote devices automatically send DHCP packets, which are

transmitted to iTN200 A through PTN. iTN200 A sends DHCP respond packets to remote

devices. These packets include allocated IP addresses, default gateways, and SNMP Trap.

After receiving these parameters, DHCP Clients update their configurations automatically.

Figure 5-3 Indirectly-connected remote zero-configuration

Raisecom




Remote zero-configuration

Once powered on, remote devices can send packets to detect the zero-configuration server. If

the network management channel or network management server is configured improperly

when a remote device is powered on for the first time, the remote device sends the detection

packet periodically to ensure getting correct network management parameters.

In directly-connected and indirectly-connected local/remote zero-configuration modes, the

remote device enabled with zero-configuration supports getting parameters, such as the

management IP address, through the OAM protocol and DHCP protocol. When using the

DHCP protocol to exchange packets, the remote device works as the DHCP Client.

The iTN201 EMS supports configuring local zero-configuration only.

5.2 Configuring local zero-configuration

5.2.1 Preparing for configurations

Scenario When directly connected to a remote device, the iTN201 uses the extended OAM

protocol to discover the remote device and configure the management IP address and

management VLAN for it. Therefore, the NView NNM system can quickly manage the

remote device through the public IP address and global interface ID of the iTN201

without manually configuring them.

When indirectly connected to a remote device, the iTN201 uses DHCP to discover the

remote device and configure the management IP address and management VLAN for it.

Therefore, the NView NNM system can quickly manage the remote device through the

public IP address and global interface ID of the iTN201 without manually configuring

them.

Prerequisite The local DHCP server is configured with the management IP address and management

VLAN.

The local DHCP server is connected to the NView NNM system properly.

5.2.2 Configuring directly-connected zero-configuration server

The iTN201 supports the extended OAM dual uplink feature, which is realized through alarm management and resource synchronization in the iTN201 EMS without being configured. When one remote device is discovered by 2 local devices simultaneously, 2 management links are established, where one link (Link A) is normal and the other one (Link B) is blocked. When Link A fails, the management link is switched to Link B through the OAM loss alarm. If the operation fails, the management link is switched through resource synchronization of the local/remote device to ensure managing the remote device properly.

Raisecom




Configuring remote management VLAN

Step 1 From the Action List of the iTN201 EMS, choose Device Management > Remote Zero

Config.

Step 2 From the Action list at the Remote Zero Config area, choose Extend OAM > Manage Vlan

Config.

Step 3 Configure the remote management VLAN at the Manage Vlan Config area. The remote

management VLAN ID ranges from 1 to 4094.


Configuring remote management IP address auto overriding

When the iTN201 works as the local zero-configuration server and is directly connected to a

remote device, you can enable remote management IP address auto-allocation. After this

function is enabled, the local can forcibly configure a new management IP address for the

remote device even if the remote device is configured with an IP address.


Config.

Step 2 From the Action list at the Remote Zero Config area, choose Extend OAM > Remote

Manager.

Step 3 Select the Remote IP Cover tab and then configure management IP address auto overriding.

The following table describes parameters at the tab.



Auto Cover Remote

Device Snmp IP

Enable/Disable remote management IP address auto overriding.

Enable Disable

By default, it is enabled.

Configuring remote IP address


Config.


Manager and then select the Remote IP Config tab.


Step 4 A dialog box appears, where you can configure the remote IP address. The following table

describes parameters at the dialog box.


Raisecom





Remote Default

Gateway

Configure the default gateway of the remote device, which is in

dotted decimal notation. By default, it is set to 0.0.0.0, which

indicates that no default gateway is configured.

Remote Ip Address Configure the IP address of the remote device, which is in dotted

decimal notation.

Remote Net Mask Configure the subnet mask of the IP address, which is in dotted

decimal notation.

Remote subnet

Associated vlan

Configure the subnet-associated VLAN of the remote device,

which ranges from 1 to 4094.

Configuring remote community


Config.


Manager and then select the Remote Community Config tab.


Step 4 A dialog box appears, where you can configure the remote community. The following table

describes parameters at the dialog box.



Remote Community

Name

Configure the remote community name, which ranges from 1

to 20 characters.

Remote Community

Permission

Select the access authority of the remote community,

ReadOnly: read-only ReadWrite: read-write

Configuring NAT

Network Address Translation (NAT) is used to translate the private management IP address of

the remote device to the public IP address+interface ID. When the management packet of a

remote device is sent to the local device, by using NAT, the local device translates the IP

address of the management packet to the public IP address+interface ID of the local device

and then uses this public IP address to transmit the management packet to the NView NNM

system. Therefore, you need to configure the public IP address and associated management

VLAN of the local device.


Config.

Raisecom




Step 2 From the Action list at the Remote Zero Config area, choose DHCP Server > Config

Manager > Nat Config Management and then click Add at the Nat Config Management

area.

Step 3 A dialog box appears, where you can configure the public IP address.


Viewing extended OAM statistics


Config.

Step 2 From the Action list at the Remote Zero Config area, choose Extend OAM > Extend OAM

Statistic.

Step 3 Select a record and then click View to view extended OAM statistics.

Step 4 After configurations, click Close.

5.2.3 Configuring indirectly-connected zero-configuration server

Configuring working modes of DHCP Server


Config.


Manager > Config Manager.

Step 3 Configure working modes of the DHCP Server at the Config Manager area. The following

table describes parameters at the area.



Dhcp Server Mode Select a working mode of the DHCP Server.

Zero Config Model Normal Model

Configuring DHCP Relay trusted by DHCP Server


Config.


Manager > Relay Ip Manager and then click Add at the Relay Ip Manager area.

Step 3 A dialog box appears, where you can configure the DHCP Relay trusted by the DHCP Server.

The following table describes parameters at the dialog box.


Raisecom





Index of Relay Address Configure the index of the Relay IP address table.

Relay Address Configure the IP address of the DHCP Relay, which is in


Mask of Relay Address Configure the subnet mask of the IP address, which is in


Enabling global DHCP Server


Config.



Step 3 Enable global DHCP Server at the Config Manager area. The following table describes

parameters at the area.



Global DHCP Server

Management

Enable/Disable global DHCP Server.

Enable Disable

By default, global DHCP Server is disabled.

Enabling DHCP Serve on Layer 3 interface


Config.


Manager > IP Interface Manager.

Step 3 Select the record about the Layer 3 interface and then click Modify.

Step 4 A dialog box appears, where you can enable global DHCP Server. By default DHCP Server is

disabled on the Layer 3 interface.


Configuring DHCP Server Trap


Config.



Raisecom




Step 3 Configure DHCP Server Trap at the Config Manager area. The following table describes

parameters at the area.



Trap Bind Ip Enable Enable/Disable DHCP Server Trap.

Enable Disable

By default, DHCP Server Trap is enabled.

Trap target address Configure the DHCP Server Trap target address.

Configuring global lease time of IP addresses


Config.



Step 3 Configure the global lease time of IP addresses at the Config Manager area. The following

table describes parameters at the area.



Max Lease Configure the maximum lease time, which ranges from 30 to 10080min

and is set to 10800 by default.

Min Lease Configure the minimum lease time, which ranges from 30 to 10080min


Default Lease Configure the default lease time, which ranges from 30 to 10080min and

is set to 30 by default.

Saving lease


Config.

Step 2 From the Action list at the Remote Zero Config area, choose DHCP Server > Lease

Manager > IP Lease Info.

Step 3 Click Save Lease at the IP Lease Info area.

Creating IP address pool


Config.

Raisecom





Manager > IP Pool Manager and then click Add at the IP Pool Manager area.

Step 3 A dialog box appears, where you can create an IP address pool. The following table describes

parameters at the dialog box.



Index of IP Pool Configure the IP address pool index.

IP Pool Name Configure the IP address pool name, which ranges from 1 to 16

characters.

IP Interface Configure the Layer 2 interface ID, which ranges from 0 to 14.

Start IP of IP Pool Configure the start IP address of the IP address pool. It is in dotted

decimal notation and ranges from 172.31.0.1 to 172.31.7.255.

End IP of IP Pool Configure the end IP address of the IP address pool. It is in dotted

decimal notation and ranges from 172.31.0.1 to 172.31.7.255.

Mask of IP Pool Configure the mask of IP addresses in the IP address pool, which

is in dotted decimal notation.

Gateway of IP Pool Configure the gateway of the IP address pool, which is in dotted

decimal notation.

The gateway address is identical to the IP address of the IP

interface.

DNS of IP Pool Configure the primary DNS of the IP address pool, which is in


When the request packets sent by DHCP Clients include the DNS

option, the respond packets sent by the DHCP Server will include

the IP address of the DNS.

Secondary DNS of

IP Pool

Configure the secondary DNS of the IP address pool, which is in


IP address of TFTP

Server

Configure the TFTP server corresponding to the IP address pool,

which is in dotted decimal notation.

When the request packets sent by DHCP Clients include the TFTP

server option, the respond packets sent by the DHCP Server will

include the IP address of the TFTP server.

Boot-file name Configure the Bootrom file name of the IP address pool, which

ranges from 1 to 63 bytes.

When the request packets sent by DHCP Clients include the

Bootfile option, the response packets sent by the DHCP Server

will include the path of the Bootfile file.

Although the DHCP Server can configure the Bootrom file

through this parameter, the DHCP server cannot ensure that the

Bootrom file is available.

Max lease time Configure the maximum lease time of the IP address pool, which

ranges from 30 to 10080min and is set to 10800 by default.

Raisecom





Minimum lease time Configure the minimum lease time of the IP address pool, which


Default lease time Configure the default lease time of the IP address pool, which


Configuring binding relationship between IP address pool and MAC /IP address


Config.


Manager > Static Bind IP Manager and then click Add at the Static Bind IP Manager area.

Step 3 A dialog box appears, where you can configure the binding relationship between the IP

address pool and the MAC/IP address. The following table describes parameters at the dialog

box.



Dhcp Server Static Bind Mac Configure the bound MAC address, which is in colon

hexadecimal notation.

Dhcp Server Static Bind Ip Configure the bound IP address, which is in dotted

decimal notation and ranges from 172.31.0.1 to

172.31.7.255.

Static Bind Refer Pool Name Click Select and then select a created IP address pool

name.

Configuring NAT

NAT is used to translate the private management IP address of the remote device to the public

IP address+interface ID. When the management packet of a remote device is sent to the local

device, by using NAT, the local device translates the IP address of the management packet to

the public IP address+interface ID of the local device and then uses this public IP address to

transmit the management packet to the NView NNM system. Therefore, you need to

configure the public IP address and associated management VLAN of the local device.


Config.


Manager > Nat Config Management and then click Add at the Nat Config Management

area.

Step 3 A dialog box appears, where you can configure the public IP address.


Raisecom




Releasing IP addresses


Config.


Manager > IP Lease Info.

Step 3 Click Release Address at the IP Lease Info area.

(Optional) uploading/downloading lease file

When you need to change the device that supports local zero-configuration, you can upload

the IP addresses allocated by the zero-configuration server to the FTP/TFTP/SFTP server in a

lease file form and then download the backed lease file to the changed local device. This

avoids losing assigned IP addresses.


Config.


Manager > Lease upload/download and then click Add at the Lease upload/download area.

Step 3 A dialog box appears, where you can upload/download the lease file.



Protocol Select a protocol used to upload/download the lease file.

FTP SFTP TFTP

By default, it is set to FTP.

Operation Type Select an operation.

Upgrade: upload the lease file to the storage device, such as a PC. Backup: download the file form the storage device, such as a PC.

By default, it is set to Upgrade.

File type Configure the type of file to be uploaded/downloaded.

dhcplease: lease file

IP Version Configure the IP version used to upload/download the lease file.

ipv4: IPv4 version.

Server Address Configure the IP address of the FTP server.

File Name Configure the name of file to be uploaded/downloaded.

User Name Configure the user name of the FTP server.

Password Configure the password of the FTP server.

Raisecom




Viewing packet statistics


Config.

Step 2 From the Action list at the Remote Zero Config area, choose DHCP Server > Stats Bootps to

view packet statistics.



1. View configurations on remote management VLANs.

From the Action List of the iTN201 EMS, choose Device Management > Remote Zero

Config. From the Action list at the Remote Zero Config area, choose Extend OAM >

Manage Vlan Config. Select a record and then click View to view configurations on remote

management VLANs.

2. View configurations on remote management IP address auto overriding.



Remote Manager. Select the Remote IP Cover tab to view configurations on remote

management IP address auto overriding.

3. View configurations on remote IP addresses.



Remote Manager and then select the Remote IP Config tab. Select a record and then click

View to view configurations on remote IP addresses.

4. View configurations on the remote community.



Remote Manager and then select the Remote Community Config tab. Select a record and

then click View to view configurations on the remote community.

5. View configurations on the DHCP Server.


Config. From the Action list at the Remote Zero Config area, choose DHCP Server > Config

Manager > Config Manager to view configurations on the DHCP Server.

6. View configurations on the IP address pool.



Manager > IP Pool Manager. Select a record and then click View to view configurations on

the IP address pool.

7. View configurations on the binding relationship between the IP address pool and

MAC/IP addresses.



Manager > Static Bind IP Manager. Select a record and then click View to view

configurations on the binding relationship between the IP address pool and MAC/IP addresses.

Raisecom




5.3 Configuration examples

5.3.1 Examples for configuring indirectly-connected local/remote zero-configuration

Networking requirements

As shown in Figure 5-4, iTN200 A, as the local zero-configuration server, is enabled with the

DHCP Server feature while iTN200 B is enabled with remote zero-configuration. iTN200 B

applies the IP address, default gateway, and management VLAN for iTN200 A through the IP

interface 1 (173.31.1.150). In addition, the route between iTN200 A and the NView NNM

system is reachable. Before configuring indirectly-connected local/remote zero-configuration,

you need to configure the following parameters:

Lease time of iTN200 A IP address pool: infinite

Name of the iTN200 A IP address pool: pool1

IP address range: 172.31.1.100–172.31.1.149

Subnet mask: 255.255.0.0

IP interface of PTN connected with iTN200 A: IP 0

IP address of IP 0: 128.10.10.1

IP address of the NView NNM system: 172.30.10.2

Enable local zero-configuration on iTN200 A and remote zero-configuration on iTN200 B to

ensure that iTN200 B can automatically obtain management parameters and can be managed.

Figure 5-4 Configuring indirectly-connected remote zero-configuration

Raisecom




Configuration steps

In this guide, steps for setting the IP address of IP interface 1 to 172.31.1.150 and setting the associated VLAN ID to 100 are not described.

Configure local zero-configuration on iTN200 A.

Step 1 Configure the DHCP Server.

1. From the Action List of the iTN201 EMS, choose Device Management > Remote Zero

Config.

2. From the Action list at the Remote Zero Config area, choose DHCP Server > Config


3. Configure the DHCP Server at the Config Manager area. The following table lists values

of parameters.

4. After configurations, click Save.

Parameter Value

Global DHCP Server Management Enable

Max Lease 10080

Min Lease 30

Default Lease 30

Step 2 Create and configure the IP address pool.


Config.


Manager > IP Pool Manager and then click Add at the IP Pool Manager area.

3. A dialog box appears, where you can create an IP address pool. The following table lists

values of parameters.

4. After configurations, click Apply.

Parameter Value

Index of IP Pool 1

IP Pool Name pool1

IP Interface 1

Start IP of IP Pool 172.31.0.100

End IP of IP Pool 172.31.0.149

Mask of IP Pool 255.255.0.0

Gateway of IP Pool 172.31.0.149

Raisecom




Step 3 Enable DHCP Server on the IP interface.


Config.


Manager > IP Interface Manager.

3. Select the record about IP interface 1 and then click Modify.

4. A dialog box appears, where you can enable DHCP Server.


Step 4 Configure NAT. This step is available in CLI only.

Raisecom(config)#interface ip 0

Raisecom(config-ip)#ip address 128.10.10.1

Raisecom(config-ip)#ip vlan 100

Raisecom(config-ip)#exit

Raisecom(config)#nat global ip address 128.10.10.1

Raisecom(config)#ip routing

Checking results

1. View configurations on the IP address pool.



Manager > IP Pool Manager. Select a record and then click View to view configurations on

the IP address pool.

2. View configurations on the binding relationship between the IP address pool and

MAC/IP addresses.



Manager > Static Bind IP Manager. Select a record and then click View to view

configurations on the binding relationship between the IP address pool and MAC/IP addresses.

3. View configurations on remote NEs.

From the main menu of the NView NNM system, choose Inventory > Physical. A dialog box

appears and then choose Device > NE from the left tree topology.

Raisecom


Element Management) 6 Ethernet


6 Ethernet

This chapter describes principles and configuration procedures of Ethernet, as well as related

configuration examples, including following sections:

Introduction

Configuring MAC address table

Configuring VLAN

Configuring QinQ

Configuring VLAN mapping

Configuring loopback detection

Configuring interface protection

Configuring Layer 2 protocol transparent transmission

Configuring ARP

Configuring port mirroring


6.1 Introduction

6.1.1 MAC address table

MAC address table

With the MAC address forwarding rules, Ethernet devices can quickly forward Ethernet

packets. All packets on the ingress interface are forwarded based on the MAC address table.

The MAC address table is the basis for Ethernet devices to quickly forward Layer 2 packets.

The MAC address table is saved in the buffer of a device. The capacity of the buffer decides

the numbers for MAC addresses.

The iTN201 supports MAC address auto-aging. The aging time ranges from 10s to 1000000s.

Forwarding modes of MAC address

When forwarding packets, based on the information about MAC address entries, Ethernet

devices adopt following modes:

Raisecom




Unicast: when a MAC address entry, which is related to the destination MAC address of

a packet, is listed in the MAC address table, the Ethernet device will directly forward the

packet to the received interface through the egress interface of the MAC address entry.

Multicast: when receiving a packet whose destination address is a multicast MAC

address, if the related destination address is listed in the MAC address table, the Ethernet

device will forward the packet through the egress interface of the MAC address entry.

Otherwise, the packet will be discarded.

Broadcast: when an Ethernet device receives an all-F packet, or when the Ethernet

device receives a packet whose MAC address is not listed in the MAC address table, it

will flood the packet to all interfaces in the same VLAN except for the interface that

receives this packet.

MAC address learning

When a packet is sent to a device, the device will look up the MAC address table for the

interface ID that is related to the destination MAC address of the packet. If find, the device

will forward the packets to the received interface. Meanwhile, the device will add the relevant

source MAC address, interface ID, as well as VLAN ID to the MAC address table.

When a packet is sent to the learned MAC address through other interfaces, the packet will be

directly forwarded to the received interface according to the MAC address table. If the

destination MAC address is not listed in the MAC address, the device floods the packets to all

interfaces except for the interface that receives this packet. In addition, the source MAC

address of the packet will be added to the MAC address table on the device.

MAC address limit

MAC address limit is used to restrict the number of MAC address entries on an interface or in

a VLAN. If the MAC address table is over great, the device will cost more time to look up the

MAC address table. Therefore, it reduces the forwarding performance. MAC address limit is

an effective method for managing the MAC address table.

Interface-based MAC address limit: learn source MAC addresses of packets in all

VLANs received the interface. If the number of learned MAC addresses reaches the

threshold, the device will not learn any MAC address. At this time, if the source MAC

address of the packet received by the interface is unknown (the source MAC address is

not listed in the learned MAC address table), the packet will be discarded.

VLAN-based MAC address limit: learn source MAC addresses of packets in specified

VLANs. If the number of learned MAC addresses reaches the threshold, the device will

not learn any MAC address.

The iTN201 supports interface-based and VLAN-based MAC address limit.

Blackhole MAC address

The blackhole MAC address is a special MAC address. The iTN201 will directly discard the

packet when it receives a packet whose source MAC address/destination MAC address is a

blackhole MAC address. The blackhole MAC address is manually added and is not aged.

The iTN201 supports 32K MAC addresses, of which includes 200 static MAC addresses.

Raisecom




6.1.2 VLAN

Overview of VLAN

Virtual Local Area Network (VLAN) is a protocol that is proposed for addressing the Ethernet

broadcast problem and for enhancing the security. VLAN is a Layer 2 isolation technology

that is used to partition devices in a LAN logically instead of physically to a network segment.

Therefore, multiple distinct virtual broadcast domains are created.

VLANs supported by the iTN201 meet the IEEE 802.1Q standard. The iTN201 supports 4094

concurrent VLANs.

Interface modes and packet forwarding modes

The iTN201 interface modes are divided into Access mode and Trunk mode. Table 6-1 lists

comparison on interface modes and packet forwarding modes.

Table 6-1 Interfaces modes and packet forwarding modes

Interface type

Forwarding modes for ingress packet Forwarding modes for egress packet

Untag packet Tag packet

Access Add the Native VLAN to

packets.

If the VLAN ID is

identical to the native

VLAN ID or is in the

VLAN ID list available

for the interface,

receive the packet. If the VLAN ID is not

identical to the native

VLAN ID or is not in

the VLAN ID list

available for the

interface, discard the

packet.

If the VLAN ID of a packet is

identical to the Access VLAN, the

packet is sent by removing the

Tag. If the VLAN ID of a packet is in

the VLAN ID list on a port, the

packet is sent by removing the

Tag. If the VLAN ID of a packet is not

in the VLAN ID list on a port, the

packet is discarded.

Trunk Add the Tag of the Native

VLAN to packets.

If the VLAN ID of a

packet is in the VLAN

ID list available for the

interface, receive the

packet. If the VLAN ID of a

packet is not in the

VLAN ID list available

for the interface,

discard the packet.

If the VLAN ID of a packet is

identical to the Native VLAN ID

and the interface allows the packet

to pass, the packet is sent by

removing the Tag. If the VLAN ID of a packet is not


and the interface allows the packet

to pass, the packet is sent with

keeping the Tag. If the VLAN ID of a packet is not


and the interface disallows the

packet to pass, the packet is

discarded.

Raisecom




Layer 3 interface

The Layer 3 interface of the iTN201 is a VLAN-based virtual interface, which is mainly used

to perform network management on the device or perform route connection between multiple

devices. You can relate a Layer 3 interface to the VLAN which needs to be configured with an

IP address. Each Layer 3 interface corresponds to an IP address and is related to a VLAN.

6.1.3 QinQ

QinQ (also called Stacked VLAN or Double VLAN) technology is an extension of 802.1Q,

which is defined in the 802.1ad standard by the IEEE.

Basic QinQ

Basic QinQ is a simple Layer 2 VPN tunnel technology. At the Carrier's access end, QinQ

encapsulates an outer VLAN Tag for a private packet, so that the packet traverses the

backbone network of the Internet service provider (ISP) carrying double VLAN tags.

In the ISP, the packet is transmitted according to the outer VLAN Tag (public VLAN Tag).

And the private VLAN Tag is transmitted as the data in the packet.

Selective QinQ

Selective QinQ is an enhanced application for basic QinQ. Based on some features, selective

QinQ can perform traffic classification on users' data. By adopting the interface, VLAN, or

both of them, selective QinQ encapsulates different data traffics with different VLAN Tags. In

addition to all functions realized by basic QinQ, according to different VLAN IDs, selective

QinQ can also perform different operations on packets received by the same interface, adding

different outer VLAN Tag for packets with different inner VLAN ID. With selective QinQ,

you can configure the mapping rules for inner and outer VLANs, so that you can adopt these

mapping rules to encapsulate different outer VLAN Tag for different inner VLAN Tags.

Selective QinQ makes the Carrier's network architecture flexible. With selective QinQ,

devices can classify customer devices on the interface that is connected to the access layer,

encapsulating different outer Tag for various customer devices. In addition, selective QinQ

adopts the outer Tag to configure the QoS policy in the public network, flexibly configure the

data transmission priority, and provide related services for users.

6.1.4 VLAN mapping

VLAN mapping is mainly used to replace the private VLAN Tag of Ethernet packets with

Carrier's VLAN Tag, making packets transmitted according to Carrier's VLAN forwarding

rules. During packets are sent to the peer private network from the Carrier network, the

VLAN Tag returns to the original private VLAN Tag, according to the same VLAN

forwarding rules. Therefore packets are sent to the destination properly.

When the iTN201 receives packets with private VLAN Tag, the device will match the private

VLAN Tag according to configured VLAN mapping rules. If successful, the private VLAN

Tag is replaced according to configured VLAN mapping rules. The iTN201 supports 1:1

VLAN mapping. 1:1 VLAN mapping refers to replacing VLAN Tag of packets from a

specified VLAN with new VLAN Tag.

Different from QinQ, VLAN mapping does not need to encapsulate multi-layer VALN Tags

for packets. It just modifies the VLAN Tag. Therefore, packets can be transmitted based on

Carrier's VLAN forwarding rules.

Raisecom




6.1.5 Loopback detection

The loopback detection can address the influence on network caused by a loopback, providing

the self-detection, fault-tolerance and robustness.

Procedures for the loopback detection are shown as follows:

All interfaces on the iTN201 send the Hello packet periodically. (The interval can be

configured. By default, the interval is 4 seconds.)

The iTN201 checks the source MAC field of the received packet. If the MAC address of

the iTN201 is saved in the source MAC field, it is believed that a loopback is detected on

some interface of the iTN201. If MAC addresses are different, the iTN201 will compare

the 2 MAC addresses and then greater one will be blocked.

If the Tx interface ID and Rx interface ID of a packet are identical, the interface will be

shut down.

If the Tx interface ID and Rx interface ID of a packet are different, the interface with a

bigger interface ID will be shut down and the interface with a smaller interface ID is in

UP status.

6.1.6 Interface protection

With interface protection, you can add an interface, which needs to be controlled, to an

interface protection group, isolating Layer 2/Layer 3 data in the interface protection group.

This can provide physical isolation between interfaces, enhance network security, and provide

flexible networking scheme for users.

After being configured with interface protection, interfaces in an interface protection group

cannot transmit packets to each other. Interfaces in and out of the interface protection group

can communicate with each other. So do interfaces out of the interface protection group.

6.1.7 Layer 2 protocol transparent transmission

In the real network environment, Layer 2 protocol packets of some user networks must

implement calculation by traversing the Carrier network. In this case, the device should be

enabled with Layer 2 protocol transparent transmission.

The transparent transmission function is a main function for Ethernet devices. In general, the

Carrier's edge device charges for transparently transmission of Layer 2 protocol packets. The

transparent transmission function is enabled on the interface where the Carrier's edge device is

connected to the user network. This interface works in Access mode and the interface on the

connected user device works in Trunk mode. A Layer 2 protocol packet is transmitted through

the ingress interface and is encapsulated on the edge device (the ingress interface) of the

Internet Service Provider (ISP). And then the Layer 2 protocol packet is transmitted to the

Carrier network. The Layer 2 protocol packet traverses the ISP to the other edge device (the

egress interface). Then this edge device decapsulates the Layer 2 protocol packet and

transmits it to the user network through the egress interface, as shown in Figure 6-1.

Raisecom




Figure 6-1 Layer 2 protocol packets being transparently transmitted through Carrier network

The transparent transmission function consists of encapsulation and decapsulation processes.

And basic principles are shown as follows:

Encapsulation: on the ingress interface of the ISP, the device changes the destination

MAC address of the Layer 2 protocol packet to a special multicast address (by default, it

is 010E.5E00.0003). In the Carrier network, the modified packet is taken as a data packet

to be forwarded in the VLAN where the user belongs.

Medium processing: Layer 2 protocol transparent transmission can either run with QinQ

simultaneously or run independently. However, in the real networking application, after

the MAC address of a Layer 2 protocol packet is modified, the device decides whether to

encapsulate the outer VLAN Tag of the packet based on the configured transparent

transmission mode to make the packet traverse the Carrier network smoothly.

Decapsulation: on the egress interface of the ISP, the device recognizes the specified

multicast address (010E.5E00.0003 by default) and restores it to the original destination

MAC address of the Layer 2 protocol packet. In addition, the device decides whether to

remove the outer VLAN Tag of the packet based on the configured transparent

transmission mode to transmit the packet to the specified user network.

The iTN201 supports transparently transmitting DOT1X packets, LACP packets, and some

specified protocol packets.

6.1.8 ARP

In the TCP/IP network, each host is assigned with a 32-bit IP address, which is called a logical

address used to identify the host in the network. To transmit packets through physical links,

you must learn the physical address of the destination host. This needs to establish a mapping

relationship between the IP address and the physical address.

In the Ethernet, a physical address is a 48-bit MAC address. To transmit packets to the target

host properly, you should translate the 32-bit IP address in to a 48-bit MAC address. That is

why the Address Resolution Protocol (ARP) is generated. ARP is mainly used to translate IP

addresses into MAC addresses, establishing a mapping relationship between IP addresses and

MAC addresses.

Entries in the ARP address table are classified into the following types:

Static ARP entry: static entry is used to perform static binding on an IP address and a

MAC address. It is used to prevent ARP dynamic learning fraud. Static ARP entries

should be manually added and deleted and are not aged.

Dynamic ARP entry: entries that are automatically established through ARP. Dynamic

ARP entries are automatically generated by the iTN201. You can adjust some parameters

Raisecom




as required. There is no need to manually add or delete dynamic ARP entries. To avoid

wasting ARP entries, you need to configure the aging time to release ARP entries in time.

6.1.9 Port mirroring

Port mirroring refers to mirroring packets of the source ports to the monitor port without

affecting packets forwarding. You can use this function to monitor the receiving and sending

status of some port and analyze the network situation.

Figure 6-2 Principles of port mirroring

Basic principles for the port mirroring are displayed in Figure 6-2. PC 1 accesses to the

network through Client 1 of the iTN201. PC 2 is the monitor PC and is connected to Client 2

of the iTN201.

When needing to monitor packets sent by PC 1, you need to configure Client 1 as the

mirroring port and enable port mirroring for packets on the ingress port. Configure Client 2 as

the monitor port, that is, the mirroring destination port.

When forwarding a packet sent by PC 1, the iTN201 mirrors one to Client 2. Monitor devices

connected to Client 2 receive and analyze this mirrored packet.

The iTN201 supports port mirroring based on ingress and egress ports.

6.2 Configuring MAC address table


Scenario

Static MAC addresses need be set for fixed servers, fixed and important hosts for special

persons (managers, financial staffs, etc.), to ensure all data traffic to these MAC addresses are

correctly forwarded from the interface that is related to these static MAC addresses.

Raisecom




To avoid the explosive growth of MAC address table entries, you need to configure the aging

time for the MAC address table.

Prerequisite

N/A

6.2.2 Configuring static MAC addresses

Creating static MAC addresses


Static MAC.

Step 2 Select the Static Unicast MAC tab at the Static MAC area and then click Add.

Step 3 A dialog box appears, where you can create a static MAC address. The following table




VLAN ID Configure the VLAN ID, which ranges from 1 to 4094.

Static MAC address Configure the static MAC address, which is in colon hexadecimal

notation.

Port Number Click Select and then select an interface ID.

Configuring MAC address statistics


Static MAC.

Step 2 Select the MAC Count Group tab at the Static MAC area.

Step 3 Configure the MAC address statistics at the area. The following table describes items at the

area.



The Port that MAC Address is

from

Configure the interface ID corresponding to the MAC

address.

Enter an interface ID, which ranges from 1 to 24 for

the iTN201-4GF and ranges from 1 to 22 for the

iTN201-2XG. Click Select and then select an interface ID. Select the All Ports radio button.

By default, the All Ports radio button is selected.

Raisecom





The VLAN that MAC Address

is from

Configure the VLAN ID corresponding to the MAC

address.

Enter an interface ID, which ranges from 1 to 4094. Select the All radio button.

By default, the All radio button is selected.

Count of MAC Address Display the number of MAC addresses that match with

the parameters of The Port that MAC Address is from

and The VLAN that MAC Address is from.

MAC Table Count Display the number of MAC addresses in the MAC

address table.

Deleting MAC addresses


Static MAC.

Step 2 Select the MAC Table Clear tab at the Static MAC area.

Step 3 Configure the MAC address to be deleted. The following table describes items at the area.



MAC-clear Flay Select the criterion based to delete MAC addresses.

type: clear MAC addresses based on their types. vlan_type: clear MAC addresses based on the VLAN ID and

MAC address types. vlan_port_type: clear MAC addresses based on the VLAN ID,

interface ID, and MAC address type. mac_type: clear MAC addresses based on the deleted MAC

address and MAC address type. mac_vlan: clear MAC addresses based on the deleted MAC

address and VLAN ID. port_type: clear MAC addresses based on the interface ID and

MAC address type.

The MAC Address

Type

Select the type of deleted MAC addresses based on the MAC-

clear Flay.

All: all MAC addresses Static: static MAC addresses Dynamic: dynamic MAC addresses BlackHole: blackhole MAC addresses

Port ID Based on the MAC-clear Flay, configure the interface ID

corresponding to the deleted MAC address.

iTN201-4GF: interfaces 1–24 iTN201-2XG: interfaces 1–22

Raisecom





The Deleted MAC

Address

Based on the MAC-clear Flay, configure the deleted MAC

address, which is in colon hexadecimal notation.

The VLAN ID Based on the MAC-clear Flay, configure the VLAN ID

corresponding to the deleted MAC address, which ranges from 1

to 4094.

6.2.3 Configuring dynamic MAC addresses

Configuring dynamic MAC address learning on interfaces


MAC Learning Config and then select the Port MAC Learning tab at the MAC Learning

Config area.


Step 3 A dialog box appears, where you can configure dynamic MAC addresses. The following table




MAC Learning Enable Enable/Disable MAC address learning.

Enable Disable

By default, MAC address learning is enabled.

Configuring interface-based MAC address limit

When the newly-configured MAC address threshold is smaller than the existing one, the system will delete the learned MAC addresses from the MAC address table. When the newly-configured MAC address limit threshold is greater than the existing one, learned MAC addresses in the MAC address table are not changed.



Config area.


Step 3 A dialog box appears, where you can configure the interface-based MAC address limit

threshold. The following table describes items at the dialog box.


Raisecom





Port MAC

Threshold

Configure the interface-based MAC address limit threshold.

Enter the MAC address limit threshold, which ranges from 1 to 8192. Select the UnLimited radio box. Therefore, no MAC address limit

threshold is configured.

Configuring VLAN-based MAC address limit


MAC Learning Config and then select the Vlan MAC Learning tab at the MAC Learning

Config area.


Step 3 A dialog box appears, where you can configure the VLAN-based MAC address limit

threshold. The following table describes items at the dialog box.



The Threshold Of MAC Configure the VLAN-based MAC address limit threshold,

which ranges from 1 to 8192. By default, it is set to 0. It

indicates that no MAC address limit threshold is configured.

Configuring aging time of dynamic MAC addresses


System Config.

Step 2 Configure the aging time of MAC addresses. The following table describes items at the area.



MAC Aging

Time

Configure the aging time of MAC addresses.

Enter the aging time, which ranges from 10 to 1000000s. By

default, it is set to 300s. Select the Deny Aging radio box. It indicates that learned MAC

addresses are always valid.

6.2.4 Configuring blackhole MAC addresses


Static MAC.

Step 2 Select the Blackhole MAC Address tab at the Static MAC area and then click Add.

Raisecom




Step 3 A dialog box appears, where you can create a blackhole MAC address. The following table





Static MAC address Configure the static MAC address, which in colon hexadecimal

notation.



1. View static MAC address configurations.


Static MAC and then select the Static Unicast MAC tab at the Static MAC area. Select a

record and then click View. A dialog box appears, where you can view static MAC address

configurations.

2. View dynamic MAC address configurations.



Config area. Select a record and then click View. A dialog box appears, where you can view

dynamic MAC address configurations.

3. View blackhole MAC address configurations.


Static MAC and then select the Blackhole MAC Address tab at the Static MAC area. Select a

record and then click View. A dialog box appears, where you can view blackhole MAC

address configurations.

6.3 Configuring VLAN


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

Raisecom




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 to each other, so you has to carve up

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

When you need to configure an IP address for a VLAN, you can relate a Layer 3 interface to

the VLAN. Each Layer 3 interface corresponds to an IP address and is related to a VLAN.

Prerequisite

N/A

6.3.2 Creating VLANs

The NView NNM system does not support creating VLANs in batch.

Step 1 From the Action List of the iTN201 EMS, choose SNMP Management > VLAN MGT >

VLAN Config.

Step 2 Select the VLAN Static Table tab at the VLAN Config area and then click Add.

Step 3 A dialog box appears, where you can create a VLAN. The following table describes items at

the dialog box.



VLAN ID Configure a VLAN ID, which ranges from 2 to 4094.

By default, there is the VLAN 1 which is named Default. You cannot modify or delete it.

VLAN Name Enter the VLAN name, which ranges from 0 to 32 characters.

6.3.3 Configuring interface modes and interface-based VLANs


VLAN Config and then select the Port VLAN Table tab at the VLAN Config area.

Raisecom





Step 3 A dialog box appears, where you can configure the interface mode and interface-based VLAN.




Port Display the interface ID.

Port Mode Select an interface mode.

Access: allow only one VLAN to pass. In addition, the

VLAN ID is identical to the native VLAN ID of the

interface. The Access interface can receive untagged

frames (frames without VLAN Tag) and send untagged

frames only. Trunk: allow multiple VLANs to pass. If the VLAN

Tag of a frame sent by the Trunk interface is identical to

the native VLAN ID of the Trunk interface, the frame is

transmitted by being removed the VLAN Tag. If the

VLAN Tag of a frame sent by the Trunk interface is not

identical to the native VLAN ID of the Trunk interface

but the Trunk interface allows the VLAN to pass, the

frame is forwarded as original.

By default, all physical interfaces are Access interfaces.

Port Access Vlan Id When the Port Mode is set to Access, configure the

default VLAN ID of the interface. It ranges from 1 to

4094. By default, it is set to 1.

Port Access Egress Vlan List When the Port Mode is set to Access, configure the

VLAN list available for the interface. It is in a format of

2,5–16,18 or 2 5–16 18. By default, it is set to 1.

Port Trunk Native Vlan ID When the Port Mode is set to Trunk, configure the default

VLAN ID of the interface. It ranges from 1 to 4094. By


Port Trunk Allow Vlan List When the Port Mode is set to Trunk, configure the VLAN

list available for the interface. It is in a format of 2,5–

16,18 or 2 5–16 18. By default, it is set to 1.

Port Trunk Untag Vlan List When the Port Mode is set to Trunk, configure the

VLAN/VLAN where Tags are allowed to be deleted on

the interface. It is in a format of 2,5–16,18 or 2 5–16 18.

By default, it is set to 1.

Port Reject Frame Type Select the frame to be discarded by the interface.

none tagged: tagged frames untagged: untagged frames

Raisecom




6.3.4 Configuring Layer 3 interface

Configuring the IP address of Layer 3 interface


Management traffic.

Step 2 Select the Ip Address tab at the Management traffic area and then click Add.

Step 3 A dialog box appears, where you can create an IP address for the Layer 3 interface. The




Port Index Configure the Layer 3 interface index, which ranges from 0 to 14.

Address type The address type is set to IPv4.

IP Address Configure the IP address of the Layer 3 interface, which is in


Address Prefix

length

Configure the prefix length of the IP address.

IP Address Source

Type

The IP address source type is set to AssignedIP, which means

assigning an IP address manually.

IP Address

Catagory

Select an IP category.

primary: primary IP address sub: subordinate IP address

Configuring VLANs related to Layer 3 interface


Management traffic.

Step 2 Select the VLAN LIST tab at the Management traffic area and then click Add.

Step 3 A dialog box appears, where you can configure the VLAN related to the Layer 3 interface.





IP Interface Configure the IP interface ID, which ranges from 0 to 14.

Raisecom




Configuring basic information of Layer 3 interface


Management traffic and then select the management traffic tab.


Step 3 A dialog box appears, where you can configure basic information of the Layer 3 interface.




VLAN

Mode

Select a VLAN mode.

Single-tagging: single VLAN Tag Double-tagging: double VLAN Tags

By default is set to Single-tagging.

Cos Configure the CoS value of the Layer 3 interface, which ranges from 0 to 7


Vlan TPID Configure the TPID (in hexadecimal notation) of the VLAN where the

Layer 3 interface is. It ranges from 0 to FFFF and is set to 8100 by default.



1. View VLAN configurations.

From the Action List of the iTN201 EMS, choose SNMP Management > VLAN MGT >

VLAN Config. Select the VLAN Current Table tab and all VLAN configurations are

displayed.

2. View interface-based VLAN configurations.


VLAN Config and then select the Port VLAN Table tab. Select a record and then click View

to view VLAN configurations on the interface.

3. View IP address configurations of the Layer 3 interface.


Management traffic and then select the Ip Address tab. Select a record and then click View

to view IP address configurations of the Layer 3 interface, including the IP address, type, and

prefix length.

4. View the binding relationship between the Layer 3 interface and VLAN.


Management traffic and then select the VLAN LIST tab. Select a record and then click View

to view the binding relationship between the Layer 3 interface and VLAN.

5. View basic information of the Layer 3 interface.

Raisecom





Management traffic and then select the management traffic tab. Select a record and then

click View to view the basic information of the Layer 3 interface.

6.4 Configuring QinQ


Scenario

You can configure basic QinQ or selective QinQ on the iTN201 as required.

Basic QinQ

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 ISP can be transparently transmitted,

without conflicting with the VLAN ID in ISP.

Selective QinQ

Differentiated from basic QinQ, the outer VLAN Tag for selective QinQ can be selected

according to service types. Set different VLAN IDs for services in the user network.

Differentiate voice, video and data services in the ISP by adding different outer VLAN Tags to

classify services when forwarding them, realizing the VLAN mapping between inner and

outer VLAN tags.

Prerequisite

Before configuring QinQ, you must finish following operations:

Connect interfaces and configure physical parameters of interfaces. Make the physical

layer Up.

Create a VLAN.

6.4.2 Configuring basic QinQ

Configuring Basic QinQ


VLAN Mapping and then select the QinQ Port Table tab.


Step 3 A dialog box appears, where you can enable basic QinQ. The following table describes items

at the dialog box.



Port qinq status Select Dotlq-tunnel.

Raisecom




(Optional) configuring global inner Tag TPID value


VLAN Mapping and then select the Double tag outer TPID tab.

Step 2 Configure the inner TAG VLAN value at the tab. The following table describes items at the

tab.



Double tag inner

TPID

Configure the inner Tag TPID value. It is in hexadecimal notation,

ranges from 0000 to FFFF and is set to 8100 by default.

Configuring interface modes and allowed VLAN IDs


VLAN Config and then select the Port VLAN List tab.


Step 3 A dialog box appears, where you can configure interface modes and allowed VLAN IDs. The





Port Mode Set the interface mode to Access.

Port Access Vlan Id When the Port Mode is set to Access, configure the default

VLAN ID of the interface. It ranges from 1 to 4094. By default,

it is set to 1.

6.4.3 Configuring selective QinQ

(Optional) configuring global outer Tag TPID value



Step 2 Configure the outer Tag VLAN value at the tab. The following table describes items at the tab.



Double tag inner

TPID

Configure the outer Tag TPID value. It is in hexadecimal notation,

ranges from 0000 to FFFF and is set to 8100 by default.

Raisecom




Configuring selective QinQ rules on interfaces


VLAN Mapping.

Step 2 Select the Port Vlan Mapping Table tab at the VLAN Mapping area and then click Add.

Step 3 A dialog box appears, where you can configure selective QinQ. The following table describes




Port Configure the interface.

Enter an interface ID, which ranges from 1 to 24 for the

iTN201-4GF and ranges from 1 to 22 for the iTN201-2XG. Click Select and then select an interface ID.

Provider vlan list Configure the inner VLAN list, which ranges from 1 to 4094

and is in a format of 2–4 6 or 2–4,6.

Translated outer vlan id Configure the added outer VLAN Tag ID, which ranges from

1 to 4094.

Vlan mapping mode Set the VLAN mapping mode to CVLAN.

6.4.4 Setting egress interface to Tunk interface




Step 3 A dialog box appears, where you can set the Port Mode to Trunk.




1. View basic QinQ configurations.


VLAN Mapping and then select the QinQ Port Table tab. Select a record and then click View

to view basic QinQ status and outer TPID values of the interface.

2. View selective QinQ configurations.


VLAN Mapping and then select the QinQ Port Table tab. Click View to view basic QinQ

status and outer TPID values of interfaces.


VLAN Mapping and then select the Port Vlan Mapping Table tab. Select a record and then

click View to view the inner VLAN ID and added outer VLAN ID of the interface.

Raisecom




6.5 Configuring VLAN mapping


Scenario

Differentiated from QinQ, VLAN mapping only changes VLAN tag but does not encapsulate

additional multilayer VLAN Tag. You just need to change VLAN Tag to make packets

transmitted according to Carrier VLAN mapping rules, without increasing frame length of the

original packet. VLAN mapping is used in following situations:

Map user services into one carrier VLAN ID.

Map multi-user services into one carrier VLAN ID.

Prerequisite

Before configuring VLAN mapping, you must finish following operations:

Connect interfaces and configure physical parameters of interfaces. Make the physical

layer Up.

Create a VLAN.

6.5.2 Configuring 1:1 VLAN mapping


VLAN Mapping.

Step 2 Select the Port Vlan Mapping Table tab at the VLAN Mapping area and then click Add.

Step 3 A dialog box appears, where you can configure VLAN mapping. The following table




Port Configure the interface. Click Select and then select

an interface ID.

Customer vlan list Configure the inner VLAN list to be translated,

which is in a format of 2–4 6 or 2–4,6.

Provider vlan list Configure the outer VLAN list to be translated,

which is in a format of 2–4 6 or 2–4,6.

Translated inner vlan id Configure the translated inner VLAN ID, which

ranges from 1 to 4094.

Translated outer vlan id Configure the translated outer VLAN ID, which


Vlan mapping mode Select a VLAN mapping mode.

Egress: in inbound direction Ingress: in outbound direction

Raisecom







VLAN Mapping and then select the Port Vlan Mapping Table tab. Select a record and then

click View to view the VLAN mapping rule of the interface.

6.6 Configuring loopback detection


Scenario

In the network, hosts or Layer 2 devices connected to access devices may form a loopback

intentionally or involuntary. Enable loopback detection on downlink interfaces of all access

devices to avoid the network congestion generated by unlimited copies of data traffic. Once a

loopback is detected on a port, the interface will be blocked.

Prerequisite

Before configuring loopback detection, you need to configure physical parameters on an

interface and make the physical layer Up.

6.6.2 Configuring basic functions of loopback detection

Do not enable loopback detection on 2 directly connected devices simultaneously. Otherwise, interfaces on the device with a greater MAC address will be blocked.

Configuring loopback detection on interfaces and actions when receiving detection packet


Loopback Detection and then select the Loopback Detection Port Table tab.


Step 3 A dialog box appears, where you can configure loopback detection and actions when the

interface receives the detection packet.



Port Display the interface index.

Raisecom





Loopback

Detection

Management

Enable/Disable loopback detection.

Enable Disable

By default, loopback detection is disabled.

Loop Action Configure the action to be taken when an interface receives the

loopback detection packet.

trap-only: send the Trap only when an interface receives the

loopback detection packet and the MAC address of the packet is

greater than the one of Rx device. discarding: send the Trap and block the interface when an interface

receives the loopback detection packet and the MAC address of the

packet is greater than the one of Rx device. shutdown: shut down the interface when an interface receives the

loopback detection packet and the MAC address of the packet is

greater than the one of Rx device.

By default, it is set to trap-only.

Configuring global properties of loopback detection


Loopback Detection.

Step 2 Select the Global Config tab at the Loopback Detection area and then configure global

properties of loopback detection. The following table describes items at the tab.



Loopback

Detection Period

Configure the period for sending the loopback detection packet. It

ranges from 1 to 65535s and is set to 4s by default.

Restore Time Configure the auto-restore time after an interface is blocked because

of loopback.

Enter the auto-restore time, which ranges from 1 to 65535s. Select the Always Close radio button.

By default, the Always Close radio button is selected.

Loopback

Detection Mode

Select a loopback detection mode.

Port: when a loopback is detected, the related interface will be

blocked. The interface will be automatically restored when the

loopback disappears. Vlan: when a loopback is detected, the related VLAN will be

blocked. The VLAN will be released when the loopback

disappears.

Raisecom




Releasing blocked interfaces

When an interface is blocked due to a detected loopback, it can be restored automatically or

manually. After a bloacked interface is manually released, the interface will perform loopback

detection again. If the loopback is detected, the interface will be blocked. If the loopback is

removed, the interface works in forwarding status.



Step 2 Select a record and then click Unblock Port.



1. View interface loopback detection configurations.

From the Action List of the iTN201 EMS, choose SNMP Management > Maintenance >

Loopback Detection and then select the Loopback Detection Port Table tab. Select a record

and then click View to view loopback detection configurations of the interface.

2. View global configurations of loopback detection.


Loopback Detection and then select the Global Config tab to view global configurations of

loopback detection.

3. View devices where a loopback is detected.


Loopback Detection and then select the Error Devices Record Table tab. Select a record and

then click View to view devices where a loopback is detected.

4. View VLANs where a loopback is detected.


Loopback Detection and then select the VLAN Record Table tab. Select a record and then

click View to view VLANs where a loopback is detected.

6.7 Configuring interface protection


Scenario

To isolate Layer 2/Layer 3 data in an interface protection group and provide physical isolation

between interfaces, you need to configure interface protection.

By adding interfaces that need to be controlled to an interface protection group, you can

enhance network security and provide flexible networking scheme for users.

Prerequisite

N/A

Raisecom




6.7.2 Configuring interface protection


List and then select the Port Protected Config tab.


Step 3 A dialog box appears, where you can configure interface protection. The following table




Protect Port Enable/Disable interface protection.

Enable Disable

By default, interface protection is enabled.



View interface protection configurations.


List and then select the Port Protected Config tab. Select a record and then click View to view

interface protection configurations.

6.8 Configuring Layer 2 protocol transparent transmission


Scenario

In the ISP, destination multicast addresses for some Layer 2 protocol packets cannot be

forwarded. The Layer 2 protocol transparent transmission is configured to make the Layer 2

protocol packet of the user network traverse the ISP network and to realize the Layer 2

protocol run in the same user network at different locations. With the Layer 2 protocol

transparent transmission, you can modify the multicast addresses for Layer 2 protocol packets,

forwarding them across the ISP. In addition, you can decapsulate the modified multicast

address to the original one on the egress interface. Therefore, the same user network at

different locations can run the same Layer 2 protocol.

Prerequisite

Before configuring the Layer 2 protocol f transparent transmission, you need to configure

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

Raisecom




6.8.2 Configuring Layer 2 protocol transparent transmission parameters

Configuring global information


Relay Config.

Step 2 Select the Global Config tab at the Relay Config area and then configure global information

of Layer 2 protocol transparent transmission. The following table describes items at the tab.



Relay Destination MAC

Address

Configure the destination MAC address of the Layer 2

protocol packet, which is in colon hexadecimal notation.

Relay CoS Configure the CoS value of the Layer 2 protocol packet,

which ranges from 0 to 7. By default, it is set to --, which

indicates no CoS value is configured.

Configuring Relay protocol information


Relay Config and then select the Relay Protocol Table tab.


Step 3 A dialog box appears, where you can configure the Relay protocol information. The following




Protocol Type Select Layer 2 protocol packets.

STP: transmit STP packets transparently. dot1x: transmit Dot1x packets transparently. lacp: transmit LACP packets transparently. cdp: transmit CDP packets transparently. vtp: transmit VPT packets transparently. pvst: transmit PVST packets transparently. lldp: transmit LLDP packets transparently.

Protocol VLAN Configure the protocol VLAN, which ranges from 2 to 4094. It

is set to 0, which indicates no protocol VLAN is specified.

Protocol Egress Port Select the specified egress interface for Layer 2 protocol packets.

Raisecom





Relay Tunnel Type Configure the channel for Layer 2 protocol packets.

none: no channel is configured. mac: MAC channel mpls: mpls channel

By default, no channel is configured.

Viewing Relay statistics


Relay Config and then select the Relay Statistics Table tab.

Step 2 Select a record and then click View.

Step 3 A dialog box appears, where you can view Relay statistics.



1. View global configurations of Layer 2 protocol transparent transmission.


Relay Config and then select the Global Config tab to view global configurations of Layer 2

protocol transparent transmission.

2. View Relay protocol information configurations.


Relay Config and then select the Relay Protocol Table tab. Select a record and then click

View to view Relay protocol information configurations.

6.9 Configuring ARP


Scenario

Entries in the ARP address table are classified into the following types:

Static ARP entry: static entry is used to perform static binding on an IP address and a

MAC address. It is used to prevent ARP dynamic learning fraud. Static ARP entries

should be manually added and deleted and are not aged.

Dynamic ARP entry: entries that are automatically established through ARP. Dynamic

ARP entries are automatically generated by the iTN201. You can adjust some parameters

as required. You should not manually add or delete dynamic ARP entries. To avoid

wasting ARP entries, you can set the aging time for them to release them as required.

In general, ARP entries are dynamically maintained by the device. The device automatically

finds the mapping relationship between IP addresses and MAC addresses based on ARP. You

Raisecom




can manually configure the device just for preventing ARP dynamic learning fraud and for

adding static ARP entries.

Prerequisite

N/A

6.9.2 Configuring static ARP entries

When you configure static ARP entries, IP addresses of these static ARP entries must be at the IP network of Layer 3 interfaces on the iTN201.


Protocol MGT > ARP.

Step 2 Select the ARP tab at the ARP area and then click Add.

Step 3 A dialog box appears, where you can configure ARP static entries. The following table




Index Configure the ARP entry index.

Enter the ARP entry index, which ranges from 0 to 14. Select the Snmp Interface radio box

IP Address Configure the IP address, which is in dotted decimal notation.

MAC Address Configure the MAC address, which is in hexadecimal notation.

6.9.3 Configuring dynamic ARP entries

Configuring ARP learning and learning threshold


Protocol MGT > ARP and then select the ARP Interface Config Table tab.


Step 3 A dialog box appears, where you can configure ARP learning and learning threshold. The




Arp Max Learn Num Configure the number of learned dynamic ARP entries. It

ranges from 1 to 1024 and is set to 512 by default.

Raisecom





The Status of Arp Learning Enable/Disable ARP learning.

Enable Disable

By default, ARP learning id enabled.

Configuring ARP learning modes


Protocol MGT > ARP.

Step 2 Select the ARP Learn Mode Config tab at the ARP area and then configure ARP learning

modes. The following table describes items at the tab.



ARP Learn

Mode

Select an ARP learning mode.

learn-all: learn request and respond packets of ARP entries. Learn-reply-only: learn ARP entries that get a respond packet after

sending a request packet.

By default, it is set to learn-reply-only.

Configuring aging time of dynamic ARP entries


System Config.

Step 2 Configure the aging time of dynamic ARP entries at the System Config tab. The following

table describes items at the tab.



ARP Aging

Time

Configure the aging time of dynamic ARP entries.

Enter the aging time. It ranges from 30 to 2147483s and is set to 1200.



1. View static ARP entry configurations.


Protocol MGT > ARP and then select the ARP tab. Select a record and then click View to

view static ARP entry configurations.

Raisecom




2. View ARP learning and learning threshold configurations.


Protocol MGT > ARP and then select the ARP Interface Config Table tab. Select a record

and then click View to view ARP learning and learning threshold configurations.

3. View ARP learning mode configurations.


Protocol MGT > ARP and then select the ARP Learn Mode Config tab to view ARP learning

mode configurations.

4. View aging time configurations of dynamic ARP entries.

From the Action List of the iTN201 EMS, choose SNMP Management > Base MGT >

System Config to view aging time configurations of dynamic ARP entries.

6.10 Configuring port mirroring


Scenario

Port mirroring is used for the administrator to monitor data traffic in a network. By mirroring

traffic on a mirroring port to a monitor port, the administrator can get traffics that have fault

and anomaly. The port mirroring is used to locate, analyze and resolve faults.

Prerequisite

N/A

6.10.2 Configuring port mirroring

There can be multiple mirroring ports. However, there is only one monitor port. After port mirroring takes effect, packets on both ingress and egress ports will be

copied to the monitor port. The mirroring port and the monitor port should not be the same one.


Mirror.

Step 2 Configure port mirroring at the Port Mirror area. The following table describes items at the

area.



Monitor Port Click Select and the select the monitor port.

Raisecom





Monitor Set Enable/Disable port mirroring.

Enable Disable

By default, port mirroring is disabled.

Ingress Port List Configure the ingress port list. Click Select and then select ingress

ports.

Out Port List Configure the egress port list. Click Select and then select ingress

ports.


6.11.1 Examples for configuring basic QinQ


As shown in Figure 6-3, iTN A and iTN B are connected to VLAN 100 and VLAN 200

respectively. To communicate through the ISP, Department A and Department C, Department

B and Department D should set the outer Tag to VLAN 1000. Configure Client 2 and Client 3

on iTN A and iTN B working in dot1q-tunnel mode and being connected to VLAN 100 and

VLAN 200. Client 1 is used to connect the ISP network, which works in Trunk mode and

allows packets with double tag to pass. The TPID is set to 9100.

Raisecom




Figure 6-3 Configuring basic QinQ

Configuration steps

Step 1 Create VLANs 100, 200, and 1000.

Configure iTN A.

1. From the Action List of iTN A EMS, choose SNMP Management > VLAN MGT >

VLAN Config.

2. Select the VLAN Static Table tab at the VLAN Config area and then click Add.

3. A dialog box appears, where you can create VLAN 100. The following table lists values

of parameters.


Parameter Value

VLAN ID 100

VLAN Name VLAN100

5. Configure VLANs 200 and 1000. Configuration steps are identical to the ones of VLAN

100.

Configure iTN B.

Configuration steps are identical to the ones of iTN A.

Raisecom




Step 2 Configure the interface mode of interfaces Client 2 and Client 2, as well as VLANs available

for these 2 interfaces.

Configure iTN A.



2. Select a record and then click Modify.

3. A dialog box appears, where you can configure the interface mode and VLANs available

for the 2 interfaces. The following table lists values of parameters.


Parameter Value of Client 2 Value of Client 3

Port Client 2 Client 3

Port Mode Access Trunk

Port Access Vlan Id 1000 –

Port Trunk Native Vlan ID – 1000

Configure iTN B.


Step 3 Configure interfaces Client 1, Client 2, and Client 3 working in dot1q mode.

Configure iTN A.


VLAN Mapping and then select the QinQ Port Table tab.

2. Select a record and then click Modify.

3. A dialog box appears, where you can configure the interface mode. The following table

lists values of parameters.


Parameter Value of Client 1 Value of Client 2 Value of Client 3

Port Client 1 Client 2 Client 3

Port qinq status Dotlq-tunnel Dotlq-tunnel Dotlq-tunnel

Configure iTN B.


Step 4 Configure the outer Tag TPID.



2. Set the outer TAG VLAN value to 9100. After configurations, click Save.

Configure iTN B.


Raisecom




Step 5 Configure interface Client 1 allowing double Tag packets to pass.

Configure iTN A.



2. Select the record about interface Client 1 and then click Modify.

3. A dialog box appears, where you can configure the interface mode and allowed VLAN

IDs of Client 1. The following table lists values of parameters.


Parameter Value

Port Mode Trunk

Port Trunk Allow Vlan List 1000

Configure iTN B.


Checking results

View QinQ configurations, taking iTN A for an example.

From the Action List of iTN A EMS, choose SNMP Management > VLAN MGT > VLAN

Mapping and then select the QinQ Port Table tab.

Select the record about interface Client 2 and then click View to view QinQ mode

configurations of interface Client 2.

Configuration steps for viewing Client 3 are identical to the ones of Client 2.

6.11.2 Examples for configuring selective QinQ


As shown in Figure 6-4, services in the ISP are divided in to PC service and IP service.

Therefore, configure the PC service with VLAN 1000 and configure the IP service with

VLAN 2000. Perform following configurations on iTN A and iTN B.

Add outer Tag VLAN 1000 to VLANs 100–150 that are assigned to PC service. Add outer

Tag VLAN 2000 to VLANs 300–400 that are assigned to IP service. Make users properly

communicate with the server through the ISP. The TPID is set to 9100.

Raisecom




Figure 6-4 Configuring selective QinQ

Configuration steps

Step 1 Create VLANs 100–150, 300–400, 1000, and 2000.

Configure iTN A.


VLAN Config.



of parameters.


Parameter Value

VLAN ID 100

VLAN Name VLAN100

5. Configure other VLANs. Configuration steps are identical to the ones of VLAN 100.

Configure iTN B.


Step 2 Configure the outer Tag TPID.

Raisecom






2. Set the outer TAG VLAN value to 9100. After configurations, click Save.

Configure iTN B.


Step 3 Configure interfaces Client 2 and Client 3 working in dot1q mode.

Configure iTN A.


VLAN Config and then select the Port VLAN Table tab.

2. Select the records about interfaces Client 2 and Client 3 and then click Modify.

3. A dialog box appears, where you can configure the interface mode and allowed Untag

label. The following table lists values of parameters.



Port Mode Trunk Trunk

Port Trunk Untag Vlan List 1000 2000 1000 2000


VLAN Mapping.

6. Select the Port Vlan Mapping Table tab at the VLAN Mapping area and then click Add.

7. A dialog box appears, where you can configure the double Tag labels of interfaces Client

2 and Client 3. The following table lists values of parameters.




Provider vlan list 100-150 300-400

Translated outer vlan id 1000 2000

VLAN mapping mode CVLAN CVLAN

Configure iTN B.


Step 4 Configure interface Client 1 allowing double Tag packets to pass.

Configure iTN A.




3. A dialog box appears, where you can configure the interface mode and allowed VLAN

IDs of Client 1. The following table lists values of parameters.

Raisecom





Parameter Value

Port Mode Trunk

Port Trunk Untag Vlan List 1000 2000

Configure iTN B.


Checking results

View QinQ configurations, taking iTN A for an example.


Mapping and then select the Port Vlan Mapping Table tab.

Select the record about interface Client 2 and then click View to view the user VLAN list and

Carrier VLAN list configurations.


6.11.3 Examples for configuring VLAN mapping


As shown in Figure 6-5, Client 2 and Client 3 of iTN A are connected to Department A and

Department B. Department A is in VLAN 100 and Department B is in VLAN 200.

Client 2 and Client 3 of iTN B are connected to Department C and Department D. Department

C is in VLAN 100 and Department D is in VLAN 200.

In the ISP, VLAN 1000 is assigned to Department A and Department C for transmitting data.

VLAN 2008 is assigned to Department B and Department D for transmitting data. By

configuring 1:1 VLAN mapping on the iTN A and iTN B, PC and terminal users can properly

communicate with the server.

Raisecom




Figure 6-5 Configuring VLAN mapping

Configuration steps

Configurations on iTNA and iTN B are identical. In this guide, only configurations on iTNA

are described.

Step 1 Create VLAN 100.


VLAN Config.



of parameters.


Parameter Value

VLAN ID 100

VLAN Name VLAN100

5. Configure VLANs 200, 1000, and 2008. Configuration steps are identical to the ones of

VLAN 100.

Step 2 Configure interface Client 1 working in Trunk mode and allowing VLANs 1000 and 2008 to

pass.

Raisecom








for interface Client 1. The following table lists values of parameters.


Parameter Value

Port Mode Trunk

Port Trunk Allow Vlan List 1000 2008

Step 3 Configure interface Client 2 working in Access mode, allowing VLAN 100 to pass, and being

enabled with VLAN mapping.







Parameter Value

Port Mode Access

Port Trunk Allow Vlan List 100


VLAN Mapping.


7. A dialog box appears, where you can configure VLAN mapping. The following table



Parameter Value

Port Client 2

Provider vlan list 100

Translated outer vlan id 1000

VLAN mapping mode Ingress


VLAN Mapping.


Raisecom







Parameter Value

Port Client 2

Provider vlan list 1000

Translated outer vlan id 100

VLAN mapping mode Egress

Step 4 Configure interface Client 3 working in Trunk mode, allowing VLAN 200 to pass, and being

enabled with VLAN mapping.







Parameter Value

Port Mode Trunk

Port Trunk Native Vlan ID 200


VLAN Mapping.





Parameter Value Value


Provider vlan list 200 2008

Translated outer vlan id 2008 200

VLAN mapping mode Ingress Egress

Checking results

View 1:1 VLAN mapping configurations.

Raisecom





Mapping and then select the Port Vlan Mapping Table tab.

Select the record about interface Client 2 and then click View to view configurations on the

Carrier VLAN list, translated outer VLAN IDs, and VLAN mapping modes.


6.11.4 Examples for configuring loopback detection


As shown in Figure 6-6, Line 1 of iTN A is connected to the core network. Client 1 and Client

2 of iTN A are connected to the user network. Enable loopback detection on iTN A to detect

the loop generated in the user network immediately and block the related interface.

Figure 6-6 Configuring loopback detection

Configuration steps

Step 1 Create VLAN 3 and add interfaces Client 1 and Client 2 to VLAN 3.


VLAN Config.


3. A dialog box appears, where you can create VLAN 3. The following table lists values of

parameters.


Parameter Value

VLAN ID 100

VLAN Name VLAN100

Raisecom






6. Select records about interfaces Client 1 and Client 2 and then click Modify.

7. A dialog box appears, where you can configure the VLANs available for the 2 interfaces.

The following table lists values of parameters.



Port Mode Access Access

Port Access Vlan Id 3 3

Step 2 Enable loopback detection on a specified interface and configure the detection period.

1. From the Action List of iTN A EMS, choose SNMP Management > Maintenance >


2. Select records about interfaces Client 1 and Client 2 and then click Modify.

3. A dialog box appears, where you can enable loopback detection. The following table lists




Loopback Detection Management Enable Enable

5. From the Action List of iTN A EMS, choose SNMP Management > Maintenance >

Loopback Detection.

6. Select the Global Config tab at the Loopback Detection area and then configure the

loopback detection period. The following table lists values of parameters.


Parameter Value

Loopback Detection Period 3

Checking results

View loopback detection status on interfaces.

From the Action List of iTN A EMS, choose SNMP Management > Maintenance >

Loopback Detection and then select the Global Config tab to view configurations on

loopback detection period.

From the Action List of iTN A EMS, choose SNMP Management > Maintenance >

Loopback Detection and then select the Loopback Detection Port Table tab. Select the record

about Interface Client 2 and then click View to view loopback detection configurations of the

interface.


Raisecom


Element Management) 7 Clock synchronization


7 Clock synchronization

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

well as related configuration examples, including following sections:

Introduction

Configuring clock synchronization based on synchronous Ethernet

Configuring PTP-based clock synchronization

Maintenance


7.1 Introduction Clock synchronization is divided into 2 modes:

Frequency synchronization: has identical time interval.

Phase synchronization: has identical time interval and begin time.

The harshest requirement on clock synchronization introduced by the communication network

is the application of clock synchronization in the wireless scenarios. Frequencies of signals in

various base stations must be in a certain precision. Otherwise, base stations fail when signals

are being switched. Some wireless mechanisms adopt synchronous base station technologies,

such as Time Division-Synchronous Code Division Multiple Access (TD-SCDMA) or Code

Division Multiple Access 2000 (CDMA2000). These wireless mechanisms have higher

requirements on phase synchronization.

Previously, Global Positioning System (GPS) is used to resolve the clock synchronization

problem. GPS can troubleshoot both frequency synchronization and phase synchronization.

However, it costs lots of money and has a higher military risk. Therefore, GPS cannot be

applied widely.

At present, synchronous Ethernet is used to synchronize frequency of devices at the physical

layer. Synchronous Ethernet synchronize phases of devices in the network through the clock

synchronization technology based on Institute of Electrical and Electronics Engineers (IEEE)

1588v2 protocol.

Raisecom




7.1.1 Synchronous Ethernet

Physical-layer synchronization technologies are widely used in the traditional TDM network.

Each node can extract clock signals from the physical link or the exterior synchronization

interface. It selects the clock source with best quality from multiple clock sources, takes it as

the local clock, and transmits it to the downstream devices. Therefore, it synchronizes clocks

of all devices to the master reference clock by locking the host.

The synchronous Ethernet technology adopted by the PTN has the similar principle, as shown

in Figure 7-1.

Step 1 iTN B outputs the clock with high precision to the physical-layer chip.

Step 2 The physical-layer chip uses the clock to transmit the data.

Step 3 Based on the clock data recovery technology integrated in the physical-layer chip, iTN A

recovers the clock signals from the serial data flow and then transmits the clock signals to the

clock sub-card.

Step 4 After being processed by the clock sub-card, these clock signals are sent to other clocks

through interfaces. Therefore, upstream clocks and downstream clocks are concatenated and

clock synchronization is realized in PTN.

Figure 7-1 Principles of synchronous Ethernet

7.1.2 IEEE 1588 v2 protocol (PTP)

The synchronous Ethernet technology supports frequency synchronization only. However, the

IEEE 1588v2 protocol supports both frequency synchronization and phase synchronization.

Therefore, the IEEE 1588v2 protocol is widely used in the PTN and it is a development trend

of clock synchronization technology.

The IEEE 1588v2 protocol, also known as Precision Time Protocol (PTP), is used to

synchronize clocks of all nodes throughout the precision synchronous distributed network.

With the hardware and software, the IEEE 1588v2 protocol can synchronize system clocks of

network devices to the master clock of the network. It achieves clock accuracy in the

nanosecond range. Compared with 10ms delay of PTN without being enabled with PTP, the

one enabled with PTP improves the timing synchronization metric greatly.

PTP helps meet requirements on clocks brought by Node B and Radio Network Controller

(RNC) in the 3G network.

Clock synchronization technology of PTP adopts the master-slave clock mode to code clock

signals. It uses network symmetry and delay measurement technology to synchronize master

Raisecom




and slave clocks by transmitting packets bidirectionaly. The iTN201 supports OneStep mode

and TwoStep mode.

The IEEE 1588v2 clock architecture supported by the iTN201 has 4 modes:

Ordinary Clock (OC): in this mode, only one interface of the iTN201 supports PTP. The

iTN201 can act as the slave clock device to be synchronized through the PTP-supported

interface. In addition, the iTN201 can act as the master clock device to output high-

precision clock through the exterior clock interface and then transmit the clock to

downstream devices through the PTP-supported interface.

Boundary Clock (BC): in this mode, multiple interfaces support PTP. Similar to the OC

mode, in BC mode, the iTN201 can acts as the master clock device or slave clock device.

In this mode, the iTN201 is connected to the upstream device through an interface to

extract clock signals. And then the iTN201 transmits the clock signals to downstream

devices through multiple interfaces. In OC mode, the iTN201 transmits the clock signals

to downstream devices through an interface only.

Transparent Clock (TC): in this mode, the iTN201 records the dwell time of received

PTP event packets and then sends the dwell time to the slave clock device. In TC mode,

the iTN201 transmits clock signals transparently. End-to-end (E2E) TC is one TC where

the master and slave clocks use end-to-end delay measurement mechanism. In E2E TC,

devices on the path add inbound and outband time to the packet. This can resolve the

delay problem caused by the dwell time on devices.

TC+OC: realize modification and transparent transmission of timestamp of IEEE 1518v2

packets, as well as clock synchronization. In this mode, the iTN201 selects the clock

source based on the configured priorities and then transmits the selected clock source to

the system clock module. If necessary, the iTN201 can set the clock to the system clock.

7.2 Configuring clock synchronization based on synchronous Ethernet


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 technology can perform clock synchronization in the PTN.

Because it does not support phase synchronization, synchronous Ethernet technology is

applied for the data base station, fixed network TDM relay, leased clock network relay, and

wireless base stations which have no requirement on phase synchronization, such as Global

System for Mobile Communications (GSM) and Wideband Code Division Multiple Access

(WCDMA).

The iTN201 supports selecting the optimum clock source automatically or selecting the

specified clock source manually.

Prerequisite

N/A

Raisecom




7.2.2 Configuring basic properties of synchronous Ethernet

Step 1 From the Action List of the iTN201 EMS, choose SNMP Management > Sync Ethernet

MGT > Clock Sync.

Step 2 Select the Clock Sync Config tab at the Clock Sync area.

Step 3 Configure basic properties of synchronous Ethernet at the area. The following table describes

items at the area.



Synce enable Enable/Disable synchronous Ethernet.

Enable Disable

By default, synchronous Ethernet is disabled.

Quality Level Mode Select a quality level mode.

Active Standard SSM: use the standard SSM quality level

to select the clock source. Deactive SSM: do not use the standard SSM quality level to

select the clock source. Active Extend SSM: use the extended SSM quality level to

select the clock source.

By default, it is set to Active Standard SSM.

Raisecom





Revertive Mode Select the auto reverse mode of the clock source.

Enable: the system will automatically switch to the better

clock source when a better clock source appears. Disable: the system will not automatically switch to the

better clock source when a better clock source appears

unless the current clock source is unavailable.


Trap Enable Enable Trap of synchronous Ethernet.

Enable: the system automatically sends Trap to the NView

NNM system when the clock source status of synchronous

Ethernet changes. Disable: the system does not send Trap to the NView NNM

system when the clock source status of synchronous

Ethernet changes.


Operation mode Select a mode for selecting the synchronous Ethernet clock

source.

Auto Select Mode: the iTN201 selects the clock source

based on the quality level or priority. Freerun Mode: the iTN201 selects the local crystal

oscillator as the clock source. Holdover Mode: the iTN201 uses the current selected clock

source.

By default, it is set to Freerun Mode.

Quality level transmit

threshold

Configure the quality level threshold of the synchronous

Ethernet packet. It ranges from 0 to 15 and is set to 0 by

default.

Quality Level

Degraadation Process

Mode

Select a quality level degradation processing mode.

Lock Current Source Holdover Previous Source

By default, it is set to Lock Current Source.

7.2.3 Configuring clock sources

The following table lists clock sources supported by the iTN201.

Clock source Description

Local crystal oscillator Local clock source, using the local crystal oscillator to

synchronize the clock

Slot 0-Ethernet interface 1 Use the lock clock source, extracting clock information

from Line 1.


from Line 2.

Raisecom




Clock source Description


from Line 3.


from Line 4.

Slot 0-PDH interface 1 PDH link clock source 1, extracting the recovery clock

from data of PDH interface 1

Slot 0-PDH interface 2 PDH link clock source 2, extracting the recovery clock

from data of PDH interface 2

Slot 0-exterior clock interface

1 (2 Mbit/s)

Use the input signal of 2 Mbit/s clock interface on clock

sub-card in slot 1 as the clock source.

Slot 0-exterior clock interface

2 (2 Mbit/s)

Use the input signal of 2 Mbit/s clock interface on clock

sub-card in slot 2 as the clock source.

PTP PTP clock source on the clock sub-card

Configuring priorities of clock sources


MGT > Clock Source.

Step 2 Select a record and then click or to set the priority of the clock source.


Configuring quality levels of clock sources


MGT > Clock Source.

Step 2 Select a record and then double-click the text box at the Admin quality level area to set the

quality level of the clock source.

Step 3 Press Enter or clock other places.


Switching clock sources forcibly

The forced clock source is not bound by the SSM quality level and clock priority. It can be

switched to any clock source, even to the one with invalid signals.

The clock source to be forcibly switched should meet the following requirements. Otherwise, switching fails. The clock source must not be locked. The clock source must be configured with priority.

Raisecom





MGT > Clock Source.

Step 2 Select a record and then click Forced Switch.

Switching clock sources manually

When the auto-recovery feature and SSM quality level are forbidden to select the clock source,

the iTN201 will not switch the clock source automatically. In this case, you can manually

switch the clock source. In addition, when SSM quality level is used to select the clock source

and a clock source with a higher quality level appears, you can manually switch the clock

source.

The clock source to be manually switched should meet the following requirements. Otherwise, switching fails. The clock source must not be locked. The clock source must be configured with priority. Signals of the clock source must be valid. The SSM quality level of the clock source must be available. The clock source must be the one with a higher SSM quality level.


MGT > Clock Source.

Step 2 Select a record and then click Manual Switch.

Clearing switching


MGT > Clock Source.

Step 2 Select a record and then click Clear Switch.

Locking clock sources


MGT > Clock Source.

Step 2 Select a record and then click Lock.

Unlocking clock sources


MGT > Clock Source.

Step 2 Select a record and then click Clear Lock.



1. View configurations on clock synchronization based on synchronous Ethernet.

Raisecom




From the Action List of the iTN201 EMS, choose SNMP Management > Sync Ethernet

MGT > Clock Sync. Select the Clock Sync Config tab to view configurations on clock

synchronization based on synchronous Ethernet.


MGT > Clock Sync. Select the Current Source Info tab to view information about the current

clock source.


MGT > Clock Sync. Select the Previous Source Info tab to view information about the

previous clock source.

2. View synchronization status information based on synchronous Ethernet.


MGT > Clock Source to view synchronization status information based on synchronous

Ethernet.

3. View configurations on clock signals of the clock sub-card.

From the Action List of the iTN201 EMS, choose SNMP Management > Clock Card MGT >

Clock Card Port. Select a record and then click View to view configurations on clock signals

of clock sub-card.

4. View synchronous Ethernet clock source statistics.


MGT > ESMC Stat to view synchronous Ethernet clock source statistics.

7.3 Configuring PTP-based clock synchronization


Scenario

The synchronous Ethernet technology supports frequency synchronization only. PTP supports

both frequency synchronization and phase synchronization. Therefore, PTP is suitable for

scenarios which have requirements on frequency synchronization and phase synchronization,

such as clock synchronization of TD-SCDMA/CDMA200 base stations.

Prerequisite

The clock sub-card is available.

7.3.2 Configuring clock modes

Enabling global PTP

Step 1 From the Action List of the iTN201 EMS, choose SNMP Management > PTP MGT > PTP

Clock Sync.

Step 2 Enable PTP at the PTP NE Properties area.


Raisecom




Configuring clock synchronization modes


Clock Sync.

Step 2 Configure the PTP-based clock synchronization mode at the PTP NE Properties area. The

following table describes items at the area.



Device clock mode Select a clock synchronization mode.

OC: ordinary clock on a signal physical interface used for

clock synchronization. The interface synchronizes time with

the upstream device or applies time to the downstream device. BC: boundary clock on two or more physical interfaces used

for clock synchronization. One interface synchronizes time

with the upstream device while the other interfaces apply time

to downstream devices. TC (E2E): end-to-end transparent clock. It is used to forward

1588v2 packets directly, does not synchronize time with other

device, but participate in calculating delay of the whole link. OC+TC (E2E): end-to-end ordinary transparent clock

Configuring the Slave mode of the device working in OC clock mode


Clock Sync.

Step 2 Configure the Slave mode of the iTN201 that works in OC clock mode at the PTP NE

Properties area. The following table describes items at the area.



Device clock mode Set the clock mode to OC.

PTP clock slave only Select a clock salve mode.

Slave-Only: the iTN201 gets clock synchronization

information from the upstream device only and cannot

synchronize downstream device. Not Slave-Only: as an ordinary clock, the iTN201 can be in

slave clock mode or be in master clock mode.

By default, it is set to Not Slave-Only.

Enabling PTP on interfaces


Port Config.

Raisecom




Step 2 The PTP Port Create area is displayed at the PTP Port Config area, as shown below.

Step 3 Select an interface from the Optional port list text box and then click to move the

interface to PTP port list text box.


7.3.3 (Optional) configuring clock properties

Configuring Step properties of the clock

When the iTN201 works in non-transparent mode, this configuration takes effect immediately. When the iTN201 works in transparent mode, this configuration will be saved and take effect when the iTN201 works in non-transparent mode.


Clock Sync.

Step 2 Configure the clock Step mode at the PTP NE Properties area. The following table describes

items at the area.



Clock step flag Select a clock Step mode.

One-step: the transmitted packet (Sync or PDelay_Resp

packet) carries the timestamp when the packet is transmitted. Two-step: the transmitted packet (Sync or PDelay_Resp

packet) does not carry the timestamp when the packet is

transmitted. The timestamp is carried by the later-transmitted

packet (Follow_Up or PDelay_Resp_Follwo_up packet).

By default, it is set to One-step mode.

(Optional) configuring clock domain of device

If the clock works in the boundary clock mode, the clock domain value of the master interface must be different from the one of the slave interface.

Raisecom





Clock Sync.

Step 2 Select the Out Clock tab at the PTP Clock Reference area and then configure the clock

domain of the iTN201. The clock domain value ranges from 0 to 255 and is set to 0 by default.


Configuring clock priorities

The configured priority takes effect immediately only when the clock is a master clock, slave clock, or boundary clock. Otherwise, configurations are saved without taking effect.


Clock Sync.

Step 2 Select the Out Clock tab at the PTP Clock Reference area and then configure the clock

priority. The following table describes items at the area.



Clock priority 1 Configure the clock priority 1. It ranges from 0 to 255 and is set

to 128 by default.

The smaller the value is, the higher the priority is and the more

possible the clock is a master one. If the master clock cannot be

selected just based on clock priority 1, you can refer to clock

priority 2.

Clock priority 2 Configure the clock priority 1. It ranges from 0 to 255 and is set

to 128 by default.

The smaller the value is, the higher the priority is and the more

possible the clock is a master one.

Configuring PTP-based clock sources


Clock Sync.

Step 2 Select the Out Clock tab at the PTP Clock Reference area and then configure the clock source

of the iTN201. The following table describes items at the area.


Raisecom





Device Time Source Select a clock source.

Atomic Clock: atomic clock GPS: GPS clock Terrestrial Radio: wireless clock PTP: PTP clock NTP: NTP clock HandSet: manually configured clock Internal Oscillartor: internal crystal oscillator clock

By default, it is set to Internal Oscillartor.

Enabling frequency adjustment of PTP clock


Clock Sync.

Step 2 Enable PTP frequency adjustment at the PTP NE Properties area. By default, PTP frequency

adjustment is enabled.


7.3.4 (Optional) configuring transmission properties of PTP packets

Configuring transmission modes of PTP packets


Clock Sync.

Step 2 Configure the transmission mode PTP packets at the PTP NE Properties area. The following

table describes items at the area.



Unicast flag Select a transmission mode of PTP packets.

Multicast Unicast PTP_Appropriate: self-adaptive mode

By default, it is set to multicast.

Configuring transmission protocols of PTP packets


Port Config.

Step 2 Select a record and then clock Modify at the PTP Port Config area.

Raisecom




Step 3 A dialog box appears, where you can configure the transmission protocol of PTP packets. The




Transmit

Protocol

Select a transmission protocol of PTP packets.

UDP: transmit PTP packets based on Layer 3 UDP. In this mode, IEEE

1588 v2 packets can be transmitted across the network. Ethernet: transmit PTP packets based on Layer 2 Ethernet protocol. In

this mode, IEEE 1588 v2 packets are transmitted only in a LAN.

By default, it is set to UDP.

(Optional) adding addresses to the master clock address pool


Address Pool Config.

Step 2 Select the Unicast Mater Pool tab at the PTP Address Pool Config area and then click Add.

Step 3 A dialog box appears, where you can add addresses to the master address pool. The following


Step 4 After configurations, click Ok.


Port Configure the interface ID of the slave clock.

iTN201-4GF: 1–24 iTN201-2XG: 1–22

Raisecom





Pool Index Configure the IP address index.

iTN201-4GF: 1–24 iTN201-2XG: 1–22

Du-Layout work

Mac Address Configure the MAC address of the master clock, which is in

dotted hexadecimal notation. This parameter is available for the

Du-Layout work parameter only.

VLAN Configure the VLAN of the master clock, which ranges from 1 to

4094. This parameter is available for the Du-Layout work

parameter only.

Three-Layout work

IP Address Configure the IP address of the master clock, which is in dotted

decimal notation. This parameter is available for the Three-

Layout work parameter.

(Optional) adding addresses to the symmetric peer address pool


Address Pool Config.

Step 2 Select the Unicast Peer Pool tab at the PTP Address Pool Config area and then click Add.

Step 3 A dialog box appears, where you can add addresses to the symmetric peer address pool. The




Port Configure the interface ID of the slave clock.

iTN201-4GF: 1–24 iTN201-2XG: 1–22

Pool Index Configure the IP address index.

iTN201-4GF: 1–24 iTN201-2XG: 1–22

Mac Address Configure the MAC address of the master clock, which is in

dotted hexadecimal notation. This parameter is available for the

Du-Layout work parameter only.

VLAN Configure the VLAN of the master clock, which ranges from 1 to

4094. This parameter is available for the Du-Layout work

parameter only.

IP Address Configure the IP address of the master clock, which is in dotted

decimal notation. This parameter is available for the Three-

Layout work parameter.

Raisecom




(Optional) configuring timers of clock interface


Port Config.


Step 3 A dialog box appears, where you can configure the timers of the clock interface. The




Sending sync message interval Configure the interval for the clock interface sending

the synchronization message. It ranges from -7 to 2s.

Sending Announce message

interval

Configure the interval for the clock interface sending

the announcement message. It ranges from -4 to 2s.

Mean time interval between

successive delay_Req messages

sent over a link

Configure the minimum interval for the clock interface

sending the delay request message. It ranges from -7 to

2s.

Reception Announce message

timeout

Configure the timeout for the clock interface receiving

the announcement message. It ranges from 3 to 16s

and is set to 3.

(Optional) configuring VLANs encapsulated in PTP packets


Port Config.


Step 3 A dialog box appears, where you can configure the VLAN of the clock interface. By default,

no VLAN is configured.


7.3.5 (Optional) configuring clock interface properties


Port Config.


Step 3 A dialog box appears, where you can configure properties of the clock interface. The



Raisecom





Asymmetry path delay Configure the asymmetric path delay compensation value,

which ranges from -100000 to 100000ns. By default, it is set

to 0, which indicates no asymmetric delay adjustment.

Force Status Select a working mode of the PTP clock interface.

Noforce: no forced interface status. The clock interface

status depends on the BMC algorithm. Master: master interface status. The clock interface is used

to apply time to downstream devices. Slave: slave interface status. The clock interface is used to

synchronize the absolute time of upstream devices. Passive: passive interface status. The clock interface

performs no operation.

By default, it is set to Noforce.

Delay mechanism Select a delay measurement mechanism supported by the

clock interface.

End-to-End: the clock interface has nothing with the delay

measurement mechanism. The clock interface supports E2E

and P2P delay request packets. Peer-to-Peer: the clock interface supports P2P delay

measurement mechanism only and does not respond to the

E2E delay request packet. In addition, the interface

connected to the clock interface must be in P2P mode

By default, it is set to End-to-End.

7.3.6 Configuring input/output clock signals of clock sub-card

When the PTP module uses the BMC algorithm to select the master clock, you need to configure the clock priority. The clock with a higher priority is more possible to be the master clock. If the PTP module cannot select the master clock based on the value of clock priority 1, it will compare the levels of clock sources. If the PTP module still cannot select the master clock, it will refer to the value of clock priority 2. Table 7-1 lists priority and precision of clock sources. If values of clock priority 1 are identical, the clock source with a higher quality level and precision is more likely to be selected as the clock source. In general, the smaller the value is, the higher the quality level is. The shorter the delay is, the higher the precision is.

Table 7-1 Priority and precision of clock sources

Clock source Meaning Quality level Precision

atomic Atomic clock 6 0x20 (< 25ns)

gps GPS clock 6 0x20 (< 25ns)

radio Wireless clock 52 0x22 (< 250ns)

Raisecom




Clock source Meaning Quality level Precision

ntp NTP clock 187 0x30 (< 10s)

oscillator Internal crystal oscillator clock 187 0xFE (unknown)

ptp PTP clocks of other devices 187 0x30 (< 10s)

handset Manually-configured clock 187 0x30 (< 10s)

Configuring basic function parameters of clock sub-card

Step 1 From the Action List of the iTN201 EMS, choose SNMP Management > Clock Card MGT >

Clock Card.

Step 2 Select a record and then clock Modify at the Clock Card area.

Step 3 A dialog box appears, where you can configure basic function parameters of clock sub-card.




Ip address Configure the IP address of the clock sub-card. It is in

dotted decimal notation and is set to 10.10.70.100 by

default.

Mask address Configure the subnet mask of the clock sub-card. It is in

dotted decimal notation, and is set to 255.0.0.0 by default.

Gateway Configure the gateway of the clock sub-card. It is in

dotted decimal notation and is set to 10.10.70.1 by

default.

input cable delay

compensate (ns)

Configure the cable delay compensation time of the input

signal. It ranges from -10000 to 10000ns. 4.5ns equals to

1 meter. The positive or negative value indicates the

offset of the original delay.

output cable delay

compensate (ns)

Configure the cable delay compensation time of the

output signal. It ranges from -10000 to 10000ns. 4.5ns

equals to 1 meter. The positive or negative value indicates

the offset of the original delay.

input cable delay

compensate (meter)

Configure the cable delay compensation length of the

input signal. It ranges from -2222 to 2222 m. 1 meter

equals to 4.5ns. The positive or negative value indicates

the offset of the original cable length.

output cable delay

compensate (meter)

Configure the cable delay compensation length of the

output signal. It ranges from -2222 to 2222 m. 1 meter

equals to 4.5ns. The positive or negative value indicates

the offset of the original cable length.

Raisecom




Configuring input clock sources


Clock Card.

Step 2 Select a record and then clock Modify at the Clock Card area.

Step 3 A dialog box appears, where you can configure the input clock source, exterior clock interface

reference source, and exterior clock interface priority. The following table describes items at

the dialog box.



Input Source Select an input clock source.

1PPS Plus TOD-Port 1 1PPS-Port 1 2M-Port 1 1PPS Plus TOD-Port 2 SystemClock

By default, it is set to 1PPS Plus TOD-Port 1

Tod signal transmit

format

Select a transmission format of TOD clock signals.

CMCC-time-info: meet the time information format specified

in Chine Mobile Precision Time Synchronization General

Technology Specification for TD Wireless system. NMEA-0183-GPRMC: meet GPS data format (GPRMC)

defined by NMEA0183. CMCC-time-status: meet the time status format specified in

Chine Mobile Precision Time Synchronization General

Technology Specification for TD Wireless system.

External time port

time source

Select a clock source used by the PTP clock.

Atomic Clock: atomic clock GPS: GPS clock Terrestrial Radio: wireless clock NTP: NTP clock HandSet: manually configured clock Internal Oscillartor: internal crystal oscillator clock

By default, it is set to GPS.

External time port

priority_1

Configure the BMC parameter priority 1 of the exterior clock

interface. It ranges from 0 to 255 and is set to 128 by default.

External time port

priority_2

Configure the BMC parameter priority 2 of the exterior clock

interface. It ranges from 0 to 255 and is set to 128 by default.

Configuring output clock sources


Clock Card Port.

Step 2 Select a record and then clock Modify at the Clock Card Port area.

Raisecom




Step 3 A dialog box appears, where you can configure the output clock signals. The following table




Output source Select an output clock signal source.

Not-Support: the clock sub-card does not output clock sigbals. PTP: the output clock signals are from the PTP clock. System-clock: the output clock signals are from the local system clock.

Configuring quality level threshold of output clock signals


Clock Card Port.

Step 2 Select a record and then clock Modify at the Clock Card Port area.

Step 3 A dialog box appears, where you can configure the quality level threshold of output clock

signals. The following table describes items at the dialog box.



Signal output quality level

shutdown threshold

Enter the quality level threshold of output clock signals,

which ranges from 0 to 15. By default, no threshold is

configured. It means clock signals can be output.

(Optional) configuring 1PPS+TOD clock input/output


Clock Card Port.

Step 2 Select the record about the 1PPS+TOD signals and then clock Modify at the Clock Card Port

area.

Step 3 A dialog box appears, where you can configure the cable delay compensation value of

the1PPS+TOD clock input/output signals. The following table describes items at the dialog

box.



Signal input/output

enable

Select the usage mode of signals.

Input: input signals Output: output signals

Raisecom




(Optional) configuring 1PPS clock signal input/output


Clock Card Port.

Step 2 Select the record about the 1PPS signals and then clock Modify at the Clock Card Port area.

Step 3 A dialog box appears, where you can enable 1PPS clock signal input/output. The following




Signal input/output

enable

Select the usage mode of signals.

Input: input signals Output: output signals

(Optional) configuring 2M clock signal input/output


Clock Card Port.

Step 2 Select the record about the E1 signals and then clock Modify at the Clock Card Port area.

Step 3 A dialog box appears, where you can enable E1 clock signal input/output. The following table




Port Mode Select the interface mode of E1 signals.

2MHz: clock signals of 2 Mbit/s clock interface are 2 MHz signals

only. E1: clock signals of 2 Mbit/s clock interface are 2 Mbit/s signals

without CRC only. E1-CRC: clock signals of 2 Mbit/s clock interface are 2 Mbit/s

signals with CRC only.

Port E1 Sa bit When the Port Mode is set to E1/E1-CRC, enter the bit occupied by

the E1 SA bit. The value is set to 4 or ranges from 4 to 8. When the

value is set to 0, it indicates that no SA bit is configured.



1. View configurations on clock signals of the clock sub-card.


Clock Card. Select a record and then click View to view configurations on clock signals of

the clock sub-card.

Raisecom




2. View configurations on the clock and interface.

From the Action List of the iTN201 EMS, choose SNMP Management > PTP MGT > PTP

Port Config. Select a record at the PTP Port Config area and then click View to view

configurations on the clock and interface.

3. View properties of the clock.


Clock Sync. Select the Out Clock tab at the PTP Clock Reference area to view information

about the exterior clock interface of the iTN201. Select the Current Clock Tab at the PTP

Clock Reference area to view information about the current clock. Select the Parent Clock tab

at the PTP Clock Reference area to view information about the parent clock. Select the Clock

Time at the PTP Clock Reference area tab to view time information of the clock.

4. View records of the master and slave address pools.


Address Pool Config and then select the Unicast Master Pool tab. Select a record and then

click View to view configurations on the master address pool. Select a record at the Unicast

Peer Pool tab and then click View to view configurations on the slave address pool.

5. View PTP packet statistics on a specified interface.


Port Stat. Select a record and then click View to view PTP packet statistics on the specified

interface.

6. View configurations on PTP-based clock synchronization.


Clock Sync to view configurations on PTP-based clock synchronization at the PTP NE

Properties area.

7.4 Maintenance 1. Clear synchronization status statistics of synchronous Ethernet.


MGT > EMSC Stat. Select a record and then click Clear Emsc Stat.

2. Clear PTP statistics of all interfaces.


Port Stat and then click Clear all ports statistics.


Raisecom




7.5.1 Examples for configuring clock synchronization based on synchronous Ethernet


As shown in Figure 7-2, the RNC device transmits clock information to the iTN A through the

synchronous Ethernet. iTN A is connected to Carrier's Node B base stations. Clock signals are

transmitted to Node B stations through client interfaces.

The clock sub-card of the iTN B is in slot 1. The input clock signals are 2 Mbit/s signals.

Figure 7-2 Configuring clock synchronization based on synchronous Ethernet

Configuration steps

Step 1 Configure iTN A.

1. From the Action List of iTN A EMS, choose SNMP Management > Sync Ethernet

MGT > Clock Sync.

2. Select the Clock Sync Config tab at the Clock Sync area.

3. Enable synchronous Ethernet and configure the SSM quality level mode at the area. The

following table lists values of parameters.


Parameter Value

Synce enable Enable

Quality Level Mode Active Standard SSM

5. From the Action List of the iTN A EMS, choose SNMP Management > Sync Ethernet

MGT > Clock Source.

6. Select the record about Ethernet interface 1 and then click continuously until

the priority is changed to 1; double-click the text box at the Admin quality level area to

set quality level to 0.


Step 2 Configure iTN B.

Raisecom




1. From the Action List of iTN B EMS, choose SNMP Management > Sync Ethernet

MGT > Clock Sync.

2. Select the Clock Sync Config tab at the Clock Sync area.

3. Enable synchronous Ethernet and configure the SSM quality level mode at the area. The



Parameter Value

Synce enable Enable

Quality Level Mode Active Standard SSM

5. From the Action List of the iTN B EMS, choose SNMP Management > Sync Ethernet

MGT > Clock Source.

6. Select the record about exterior interface 1 (2M) and then click continuously

until the priority is changed to 1; double-click the text box at the Admin quality level

area to set quality level to 0.


Checking results

1. View configurations on clock synchronization based on synchronous Ethernet, taking

iTN A for an example.

From the Action List of the iTN A EMS, choose SNMP Management > Sync Ethernet

MGT > Clock Sync. Select the Clock Sync Config tab to view configurations on clock

synchronization based on synchronous Ethernet.

2. View synchronization status information based on synchronous Ethernet, taking iTN A

for an example.


MGT > Clock Source to view synchronization status information based on synchronous

Ethernet.

7.5.2 Examples for configuring PTP-based clock synchronization


As shown in Figure 7-3, the BITS device transmits clock information to BC. The BC sends

the clock information in PTP packet to downstream devices through the PTP-based PTN.

The TC acts as a relay to transparently transmit the clock information to OCs and save the

dwell time of PTP packets.

OCs are connected to Carrier's Node B base stations. OCs obtains the upstream clock packets

from the interface that supports PTP packets. OCs sends clock signals to Node B base stations

through client interfaces to synchronize clocks throughout the whole network.

The clock sub-card is in slot 1.

The input clock signals are 2 Mbit/s signals.

Raisecom




Figure 7-3 Configuring PTP-based clock synchronization

Configuration steps

Step 1 Configure the clock mode.

Configure the clock mode of the BC.

1. From the Action List of the iTN BC EMS, choose SNMP Management > PTP MGT >

PTP Clock Sync.

2. Configure the clock mode of the BC at the PTP NE Properties area. The following table



Parameter Value

PTP enable state Enable

Device Clock Mode BC


PTP Port Config.

5. Select interface 3 from the Optional port list text box and then click to move the

interface to PTP port list text box at the PTP Port Create area.


Configure the clock mode of the TC.

1. From the Action List of the iTN TC EMS, choose SNMP Management > PTP MGT >

PTP Clock Sync.

2. Configure the clock mode of the TC at the PTP NE Properties area. The following table



Raisecom




Parameter Value


Device Clock Mode TC (E2E)


PTP Port Config.

5. Select interfaces 3 and 1 from the Optional port list text box and then click to

move the interfaces to PTP port list text box at the PTP Port Create area.


Configure the clock mode of the OC.

1. From the Action List of the iTN OC EMS, choose SNMP Management > PTP MGT >

PTP Clock Sync.

2. Configure the clock mode of the OC at the PTP NE Properties area. The following table



Parameter Value


Device Clock Mode OC


PTP Port Config.

5. Select interfaces 1 and 3 from the Optional port list text box and then click to

move the interfaces to PTP port list text box at the PTP Port Create area.


Step 2 Configure clock properties.

Configure clock properties of the BC.


PTP Clock Sync.

2. Select the Out Clock tab at the PTP Clock Reference area and then configure clock

properties of the BC. The following table lists values of parameters.


Parameter Value

Clock priority 1 100

Device Time Source Atomic Clock

Configure clock properties of the OC.


PTP Clock Sync.

Raisecom




2. Select the Out Clock tab at the PTP Clock Reference area and then configure clock

properties of the OC. The following table lists values of parameters.


Parameter Value

Clock priority 1 200

Step 3 Configure transmission properties of PTP packets.

Configure PTP packet transmission properties of the BC.


PTP Clock Sync.

5. Configure the transmission properties of PTP packets at the PTP NE Properties area. The



Parameter Value

Unicast flag Unicast


PTP Port Config.

8. Select the record about interface 3 and then clock Modify at the PTP Port Config area.

9. A dialog box appears, where you can configure the transmission protocol of PTP packets.



Parameter Value

Transmit Protocol Ethernet

Configure PTP packet transmission properties of the TC.


PTP Clock Sync.




Parameter Value



PTP Port Config.

5. Select the records about interfaces 1 and 3 and then clock Modify at the PTP Port Config

area.

Raisecom







Parameter Value of interface 1 Value of interface 3

Transmit Protocol Ethernet Ethernet

Configure PTP packet transmission properties of the OC.


PTP Clock Sync.




Parameter Value



PTP Port Config.

5. Select the records about interfaces 1 and 3 and then clock Modify at the PTP Port Config

area.




Parameter Value of interface 1 Value of interface 3

Transmit Protocol Ethernet Ethernet


PTP Address Pool Config.

9. Select the Unicast Mater Pool tab at the PTP Address Pool Config area and then click

Add.

10. A dialog box appears, where you can configure the MAC address of the master address

pool. The following table lists values of parameters.

11. After configurations, click Ok.

Parameter Value

MAC Address 00:01:00:01:00:01

Step 4 Configure input clock signals of the BC.

1. From the Action List of the iTN BC EMS, choose SNMP Management > Clock Card

MGT > Clock Card.

Raisecom




2. Select a record and then clock Modify at the Clock Card area.

3. A dialog box appears, where you can configure the IP address of clock sub-card. The



Parameter Value

Ip address 192.168.1.100

Mask address 255.255.255.0

Gateway 192.168.1.1

5. From the Action List of the iTN BC EMS, choose SNMP Management > Clock Card

MGT > Clock Card Port.

6. Select the record about the E1 interface and then clock Modify at the Clock Card Port

area.

7. A dialog box appears, where you can modify E1 interface configurations. The following

table lists values of parameters.


Parameter Value

Port Mode E1-CRC

Port E1 SA bit 6

Checking results

1. View configurations on the clock and interface.


Clock Sync to view global configurations on the clock.


Port Config. Select a record at the PTP Port Config area and then click View to view clock

configurations on the interface.

2. View configurations on the clock signal of the clock sub-card.


Clock Card. Select a record and then click View to view configurations on clock signals of

the clock sub-card.


Clock Card Port. Select a record and then click View to view configurations on clock signals

of clock sub-card.

Raisecom


Element Management) 8 MPLS-TP


8 MPLS-TP

This chapter describes principles and configuration procedures of MPLS-TP, as well as related


Introduction

Configuring basic functions of MPLS

Configuring static LSP

Configuring MPLS L2VPN

Configuring VPLS


8.1 Introduction Multiprotocol Label Switching (MPLS) is an emerging IP backbone network technology. It

introduces connection-oriented label switching concept in connectionless-oriented IP network.

Compared with the traditional IP routing mode, MPLS only analyzes IP packet header at the

network edge instead of at each hop when forwarding data. This helps save the time.

The MPLS technology has a good expandability because it supports multi-layer labels and

provides connection-oriented forwarding service. Therefore, it is widely used in Virtual

Private Network (VPN), traffic engineering, and Quality of Service (QoS).

Cooperating with the Pseudo-Wire Emulation Edge to Edge (PWE3) technology, the MPLS

network can carry Time Division Multiplex (TDM) service, ATM service, and Ethernet

service. With development of Telecom-grade network, higher requirements are introduces on

the Operation, Administration and Management (OAM) capability and end-to-end quick

protection capability of the MPLS network.

In 2008, ITU-T and Internet Engineering Task Force (IETF) establish a working team JWT.

This working team extends the existing MPLS technology to MPLS-TP in aspects of packet

forwarding, network protection, network management, control plane, and OAM.

Table 8-1 lists comparisons on MPLS and MPLS-TP.

Raisecom




Table 8-1 Comparisons on MPLS and MPLS-TP

MPLS MPLS-TP

Unidirectional Label Switched Path (LSP) Bidirectional LSP

Support Penultimate Hop Popping (PHP). Optional PHP

Support dynamic label space only. Support static and dynamic label space.

Support LSP aggregation. Do not support LSP aggregation.

Have no OAM mechanism suitable for

transmission.

Have complete OAM mechanism and

support multi-layer connectivity.

Have no complete protection mechanism

and support the local protection technology

Fast ReRoute (FRR) only.

Support end-to-end protection switching,

linear protection switching, and ring

protection switching.

8.1.1 Basic concepts

FEC

Forwarding Equivalence Class (FEC) is a term used to describe a set of packets with similar

and/or identical characteristics (destination IP address, forwarding path, and Class of Service).

Packets in the same FEC may be forwarded the same way in the MPLS network.

Label

The label is a short fixed length physically contiguous identifier which is used to identify a

FEC, usually of local significance. In some case, such as performing load sharing, a FEC may

have multiple labels simultaneously. However, a label belongs to a FEC only.

LSR

The LSR is a network device for switching and forwarding MPLS labels. It is also called a

MPLS node. LSR is the basic element of the MPLS network. All LSRs support the MPLS.

LER

The LSR locating at the edge of the MPLS domain is called a LER. If a LSR has one or more

neighbouring nodes that do not operate MPLS, this LSR is a LER.

LER is responsible for assigning FECs for packets entering the MPLS domain and pushing

labels for these FECs to forward packets. When packets leave from the MPLS domain, the

labels are popped out and then packets are forwarded.

LSP

The path along which the same FEC traverses the MPLS network is called the LSP.

In terms of function, LSP acts as the virtual circuit of the ATM and Frame Relay (FR). It is a

unidirectional path from the ingress interface to the egress interface.

Raisecom




Ingress node, Transit node, and Egress node

The LSP is a unidirectional path. LSRs on the LSP can be divided into the following types:

Ingress node: the begin mode of the LSP. One LSP has an Ingress node only. The Ingress

node is responsible for pushing labels for packets to encapsulate them into MPLS

packets for forwarding.

Transit node: middle node of the LSP. One LSP may have multiple Transit Nodes. The

Transit node is responsible for looking up the label forwarding table to forward MPLS

packets by switching labels.

Egress node: the end node of the LSP. One LSP has an Egress node only. The Egress

node is responsible for popping out the label and recovering the packets to the original

ones for forwarding.

Label space

The label space is the mode used to specify the label distribution and assignment. It is divided

into the following 2 types:

Per-Platform Label Space: the whole LSR can only generate a unique label for the

specified FEC.

Per-Interface Label Space: each interface of the LSR can generate a label for a specified

FEC.

Label stack

The label stack is an ordered set of labels. MPLS packets support carrying multiple labels

simultaneously. The label closer to the Layer 2 header is called a top label or an outer label.

The label closer to the IP header is called a bottom label or an inner label. Theoretically, the

MPLS label can be embedded infinitely.

Figure 8-1 Structure of the label stack

The label stack organizes labels in a Last In First Out form. It processes labels from the top of

the stack.

Operations of label

Operations of a label include push, swap, and pop. They are basic actions for label forwarding

and components of the label forwarding table.

Push: when an IP packet enters the MPLS domain, the MPLS edge device inserts a new

label between the Layer 2 header and the IP header of the IP packet.

Swap: when the MPLS packet is forwarded across the MPLS domain, based on the label

forwarding table, the top label of the MPLS packet is deleted and a label assigned by the

next-hop device is added.

Pop: when the MPLS packet leaves form the MPLS domain, the label is removed or

remove the stack top label from the last second node of MPLS to reduce the number of

labels in the label stack.

Raisecom




Figure 8-2 Operation process of a label

PHP

The Egress node only performs IP forwarding on received MPLS packets. Therefore, the label

is meaningless on the Egress node. In this case, you can use the Penultimate Hop Popping

(PHP) feature to remove the label from the last second node to reduce the burden of the last

hop. The last-hop node can perform IP forwarding or next-layer label forwarding directly.

On the Egress node, PHP selects a label distribution mode based on PHP configurations on the

last second node.

8.1.2 Static LSP

MPLS needs to assign labels for packets in advance and establish a LSP. And then it can

forward packets.

LSPs are divided into static LSP and dynamic LSP.

Static LSP: manually configured by the administrator

Dynamic LSP: dynamically established by using the routing protocol and the label

distribution protocol

At present, the iTN201 supports the static LSP only.

The static LSP is established by the administrator by manually assigning labels for all FECs.

To manually assign labels, the egress label value of the last node is the ingress label value of

the next mode.

For the static LSP, all LSRs cannot sense each other and then learn status of the whole LSP.

Therefore, the static LSP is of local significance.

The static LSP does not use the label distribution protocol and does not exchange the control

packet. Therefore, it consumes fewer resources. It is suitable for simple and stable small-size

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

Raisecom




8.1.3 MPLS L2VPN

Overview

MPLS L2VPN provides Layer 2 VPN services based on the MPLS network. Therefore, the

Carrier can provide Layer 2 VPN service based on different data link layer protocol on a

uniform MPLS network, including ATM, FR, VLAN, Ethernet, and PPP.

Simply, MPLS L2VPN transmits Layer 2 data transparently across the MPLS network. In

terms of user, the MPLS network is a Layer 2 switching network where you can establish

Layer 2 connection between different nodes.

As shown in Figure 8-3, taking Ethernet for an example, each Customer Edge (EC) device is

configured with an Ethernet Attachment Circuit (AC) and is connected to the remote CE

device through the MPLS network. This is similar to the connection realized through the

Ethernet.

Figure 8-3 CE accessing the network through Ethernet AC

Network model

Figure 8-4 shows the MPLS L2VPN model, which composed by 6 parts.

Figure 8-4 MPLS L2VPN model

CE device: it has an interface to directly connect to the Internet Service Provider (ISP)

network. The CE device can be a router, switch, or a PC. The CE device does not sense

the VPN and does not need to support MPLS.

Raisecom




Provider Edge (PE) device: the edge device of the ISP network. It is connected to the

user's CE device. In the MPLS network, packets entering or leaving from the VPN are

processed on the PE device.

Provider (P) device: the backbone router in the ISP network. It is not directly connected

to the CE device. The P device just needs to provide basic MPLS forwarding capability.

AC: it is an independent link or circuit used to connect the CE device and the PE device.

The AC properties include the encapsulation type, Maximum Transmission Unit (MTU)

and interface parameters of specified links.

Virtual Circuit (VC): it is a logical connection between 2 PE nodes identified by the VC

label.

Tunnel: it is used to carry the VC and transmit user data transparently.

MPLS L2VPN transparently transmits user packets in the MPLS network through the label

stack.

Outer label (Tunnel label): transmits packets from one PE device to another PE device.

Inner label (VC label): differentiate connections in different VPNs. The Rx PE device

decides the CE device to which packets are forwarded.

Figure 8-5 shows the changes of the label stack during the MPLS L2VPN forwarding process.

Figure 8-5 MPLS L2VPN label stack processing process

Layer2 Protocol Data Unit (L2PDU): the link-layer packet

T: Tunnel label

V: VC label

T': the outer label is replaced during the forwarding process.

As shown in Figure 8-5, the packet sent by CE 1 is added with 2 labels by PE 1 and then is

transmitted to PE 2. PE 2 removes the labels and then forwards the packet to CE 2.

8.1.4 VPLS

Overview

The Ethernet technology is not only widely used on the enterprise network but increasingly

used in the Carrier network, especially the Metro Area Network (MAN). The speed ranges

from 100 Mbit/s to 1000 Mbit/s and the deployment cost is less and less. Owning to high

bandwidth and low cost, the Ethernet has a powerful competitiveness. In general, the MAN

Ethernet provides point-to-point service and cannot provide services by crossing the Wide

Area Network (WAN). The development of MPLS makes MPLS-based L2VPN is widely

used. To provide Ethernet-like multipoint services in MAN/WAN, VPLS is introduced.

VPLS is a MPLS-and Ethernet-based Layer 2 VPN technology. VPLS can achieve multipoint-

to-multipoint VPN networking. VPLS provides a much complete resolution for the Carrier

who uses point-to-point L2VPN services. In addition, differentiated from L3VPN, it does not

need to manage user's internal routing information.

Raisecom




VPLS is also called Transparent LAN Service (TLS) or Virtual Private Switched Network

Service (VPSNS). Different from the common L2VPN point-to-point service, VPLS

technology can help the service provider to provide Ethernet-based multipoint services for

users through the MPLS backbone network. IETF describes the VPLS resolution in a series of

draft where MPLS virtual links are used as Ethernet bridge links to transparently transmit

LAN services through the MPLS network.

VPLS is mainly used to connect multiple Ethernet LAN network segments through the PSN

to make them work like a whole LAN.

As shown in Figure 8-6, in VPLS, the MPLS backbone network emulates the bridge device to

forward packets based on the MAC address, or MAC address+VLAN Tag.

Figure 8-6 VPLS structure

Forwarding model

The PE device uses the Virtual Switch Instance (VSI) to perform VPLS forwarding. With VSI,

the PE device can map physical attachment links of the VPLS to virtual links. PE devices

forward Ethernet frames through fully-connected Ethernet emulation circuit of PW.

Figure 8-7 shows the forwarding model of the VPLS.

Raisecom




Figure 8-7 VPLS forwarding model

PE devices in the same VPLS must be fully connected. In addition, PWs must be in any 2 PE

devices. Packets can be directly transmitted from the ingress PE device to the egress PE

device without being forwarded by the middle PE device. Therefore, no loopback is formed

between 2 PE devices and PE devices do not need to run the Spanning Tree Protocol (STP).

Basic architectures of VPLS

VPLS-related drafts provide 2 VPLS network architectures:

Common VPLS network architecture

Raisecom




Figure 8-8 Common VPLS network architecture

As shown in Figure 8-8, PE devices (PE 1, PE 2, PE 3, and PE 4) related to sites of the VPLS

are fully connected in logical and can provide point-to-point connection services. PE devices

can learn MAC address and switch packets on each VPN site among multiple points. The

MPLS network provides the Tunnel for transparently transmitting VPN packets. The core

device in the MPLS network does not learn the MAC address and switch packets. It just

provides common MPLS packet forwarding. In addition, the forwarding tables of all VPNs on

the PE device are independent. This can achieve MAC address overlap among VPNs.

Hierarchical VPLS network architecture

Figure 8-9 Hierarchical VPLS network architecture

As shown in Figure 8-9, in the hierarchical VPLS network architecture, core devices (NPE)

are fully connected in logical while user devices (UPE) and the nearest NPE establish the

virtual connection only. The NPE exchanges packets with the peer site to layer the network

technology and extend the access range.

Raisecom




NPEs in the core network have good performance and VPN service traffic is integrated. UPEs

have low performance and are mainly used to access VPN services. In addition, backup links

can be established between UPEs and NPEs to enhance the network robustness.

The access network between UPEs and NPEs can be a MPLS edge network (connected

through VPLS/VLL) or a simple Ethernet switching network (connected through QinQ). In

addition, access modes of all UPEs in the hierarchical VPLS network architecture can be used

hybrid. VPN sites can freely select the access type between UPEs and NPEs based on the real

access network type.

8.2 Configuring basic functions of MPLS


Scenario

Basic functions of MPLS are the basis for other MPLS functions taking effect. Basic

functions of MPLS include enabling MPLS globally and on an interface. Configuring the LSR

ID is the basis for enabling global MPLS.

Prerequisite

N/A

8.2.2 Configuring basic functions of MPLS

Some IP interface address needs to be used as the LSR ID of the device. From the topology view the iTN201 EMS, you must configure the LSR ID and then

click Save and then enable MPLS and click Save. Otherwise, configurations fail. MPLS on an interface cannot take effect unless global MPLS is enabled and the

IP interface is configured with an IP address and is related to a VLAN.


System Config.

Step 2 Select the MPLS Global Config tab and then configure basic functions at the tab. The

following table describes items at the tab.



MPLS LSR ID Enter the LSR ID of the local device, which is in dotted decimal

notation.

By default, it is set to 0.0.0.0, which means that no local LSR ID is

configured.

Raisecom





MPLS Enable Enable/Disable global MPLS.

Enable Disable

By default, global MPLS is disabled.

Public TTL Enable/Disable public TTL duplication after global MPLS is

enabled.

Enable Disable

By default, public TTL duplication is enabled.

Lable.pth.VPNPro

pagate

Enable/Disable private TTL duplication after global MPLS is

enabled.

Enable Disable

By default, private TTL duplication is disabled.

Tunnel Trap

Enable

Enable/Disable Tunnel Trap after global MPLS is enabled.

Enable Disable

By default, Tunnel Trap is enabled.

PW Trap Enable Enable/Disable PW Trap.

Enable Disable

By default, PW Trap is enabled.

Aps Mpls Trap

Enable

Enable/Disable Tunnel protection group Trap.

Enable Disable

By default, Tunnel protection group Trap is enabled.



View global MPLS configurations.


System Config. Select the MPLS Global Config tab and then view global MPLS

configurations.

Raisecom




8.3 Configuring static LSP


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 egress

label value of the last node is the ingress 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

Before configuring the static LSP, you need to configure basic functions of MPLS.

8.3.2 Configuring static LSP

During configuration, ensure that the in-label values of the Ingress node, Transit node, and Egress node are different.

Configuring static LSP of Ingress node

Step 1 From the Action List of the iTN201 EMS, choose SNMP Management > Packet Service >

Tunnel Management > MPLS Tunnel Management.

Step 2 Click from the tool bar of the iTN201 EMS and a dialog box appears. The following


Step 3 After configurations, select the Deploy radio box and then click Save.


Tunnel ID Configure the Tunnel ID, which ranges from 1 to 1024.

Friendly Name Configure the Tunnel name, which ranges from 1 to 200 characters.

LSP Name Configure the LSP name, which ranges from 1 to 32 characters.

Direction Configure the LSP type.

One-way Two-way

By default, it is set to Two-way.

Node Type Configure the node type.

Ingress: Ingress node

Raisecom





Forward the next

hop address type

Configure the forward next hop address type.

MAC

The forward next-hop address must be a MAC address on colon


Forward next hop Configure the forward next hop address.

Reverse into label Configure the backward in-label, which ranges from 16 to 1048319.

This parameter is available only when the Direction parameter is set

to Two-way.

Out Port Click and then select a LSP egress interface.

Forward out label Configure the forward out-label, which ranges from 16 to 1048575.

Destination node

address

Configure the IP address of the destination node, which is in dotted

decimal notation.

Tunnel Interface The Tunnel is the working channel of a Tunnel protection group if

you configure the Tunnel interface. Otherwise, the Tunnel is the

protection channel of the Tunnel protection group. The Tunnel

interface ID ranges from 1 to 1024.

Remark Configure the LSP remark on the Ingress node, which ranges from 0

to 512 characters.

Signaling Type Set the label distribution mode to static, which means distributing

labels manually.

Forward Vlan ID Configure the forward VLAN ID, which ranges from 1 to 4094.

Configuring static LSP of Transit node








Friendly Name Configure the Tunnel name, which ranges from 1 to 200 characters.

LSP Name Configure the LSP name, which ranges from 1 to 32 characters.


One-way Two-way

Raisecom






Transit: Transit node

Reverse out label Configure the backward in-label, which ranges from 16 to 1048575.


to Two-way.

Forward into label Configure the forward out-label, which ranges from 16 to 16 to

1048319.

In Port Click and then select a LSP ingress interface.

Forward the next

hop address type

Configure the forward next hop address type.

MAC

The forward next-hop address must be a MAC address on colon


Forward next hop Configure the forward next hop address.


Forward out label Configure the forward out-label, which ranges from 16 to 1048575.

Reverse into label Configure the backward in-label, which ranges from 16 to 1048319.


to Two-way.

Reverse next hop

address type

Configure the backward next hop address type.

MAC

The backward next-hop address must be a MAC address on colon

hexadecimal notation. This parameter is available only when the

Direction parameter is set to Two-way.

Reverse next hop Configure the backward next hop address. This parameter is

available only when the Direction parameter is set to Two-way.

Source node

address

Configure the IP address of the source node, which is in dotted

decimal notation.

Destination node

address

Configure the IP address of the destination node, which is in dotted

decimal notation.

Remark Configure the LSP remark on the Transit node, which ranges from 0

to 512 characters.

Signaling Type Set the label distribution mode to static, which means distributing

labels manually.

SNC Protection

Mode

Configure the SNC protection mode.

working standby


to Two-way. This parameter is used to distinguish the working

Tunnel from the protection Tunnel.

Raisecom





Reverse Vlan ID Configure the backward VLAN ID, which ranges from 1 to 4094.


to Two-way.

Forward Vlan ID Configure the forward VLAN ID, which ranges from 1 to 4094.


to Two-way.

Configuring static LSP of Egress node








Friendly Name Configure the Tunnel name, which ranges from 1 to 200

characters.

LSP Name Configure the LSP name, which ranges from 1 to 32

characters.


One-way Two-way



Egress: Egress node

Reverse out label Configure the backward in-label, which ranges from 16

to 1048575. This parameter is available only when the


Forward into label Configure the forward out-label, which ranges from 16

to 16 to 1048319.


Reverse next hop address type Configure the backward next hop address type.

MAC

The backward next-hop address must be a MAC address

on colon hexadecimal notation. This parameter is

available only when the Direction parameter is set to

Two-way.

Raisecom





Reverse next hop Configure the backward next hop address. This

parameter is available only when the Direction

parameter is set to Two-way.

Source node address Configure the IP address of the source node, which is in


Tunnel Interface The Tunnel is the working channel of a Tunnel

protection group if you configure the Tunnel interface.

Otherwise, the Tunnel is the protection channel of the

Tunnel protection group. The Tunnel interface ID ranges

from 1 to 1024. This parameter is available only when

the Direction parameter is set to Two-way.

Remark Configure the LSP remark on the Egress node, which

ranges from 0 to 512 characters.

Signaling Type Set the label distribution mode to static, which means

distributing labels manually.

Reverse Vlan ID Configure the backward VLAN ID, which ranges from 1



Forward Vlan ID Configure the forward VLAN ID, which ranges from 1





1. View LSP configurations on the Ingress node.

From the Action List of the iTN201 EMS, choose SNMP Management > Packet Service >

Tunnel Management > MPLS Tunnel Management to view LSP configurations on the

Ingress node.

2. View LSP configurations on the Transit node.


Tunnel Management > MPLS Tunnel Management. Select the Transit LSP tab to view LSP

configurations on the Transit node.

3. View LSP configurations on the Egress node.


Tunnel Management > MPLS Tunnel Management. Select the Egress LSP tab to view LSP

configurations on the Egress node.

Raisecom




8.4 Configuring MPLS L2VPN


Scenario

With MPLS L2VPN, the Carrier can provide Layer 2 VPN service based on different media

on a uniform MPLS network. The iTN201 supports MPLS L2VPN technology that supports

carrying Ethernet.

MPLS L2VPN technology, which supports carrying Ethernet, distinguishes services through

interface+VLAN.

VPWS services provide point-to-point L2VPN.

VPLS services provide multipoint-to-multipoint.

Prerequisite

Before configuring VPLS, you need to configure the basic functions of MPLS and MPLS

L2VPN.

8.4.2 Configuring MPLS L2VPN

Enabling global MPLS L2VPN


System Config.

Step 2 Select the MPLS Global Config tab and then enable L2VPN at the tab.


(Optional) configuring static L2VC

This parameter is available when you set the SVC mode to MPLS L2VPN.


ELine Management.




Service ID Configure the service ID, which ranges from 1 to 2147483647.

Service Name Configure the service name.

Associated

Customer Click and then select the customer associated to the service.

NE Name Display the NE name.

Raisecom





Access Type Configure the service interface type.

Physical Interface: correspond to the switching interface. VLAN: correspond to the switching interface+VLAN.

Port Click and then select a service interface.

VLAN Configure the VLAN associated to the service interface when the

Access Type is set to VLAN. It ranges from 1 to 4094.

Service Priority Configure the service priority, which ranges from 0 to 7.

Remark Configure the service remark, which ranges from 0 to 512 characters.

Step 3 After configurations, click Config PW and a dialog box appears. The following table



PW ID Configure the PW ID, which is identical to the created service ID. It


PW Identity Configure the PW identifier, which ranges from 1 to 32 characters.

PW Name Configure the PW name, which ranges from 1 to 200 characters.

PW Type Configure the mode for PW processing packets.

Ethernet: in in-PW direction, the PE removes VLAN Tags of

received packets and then encapsulates them into the PW. In out-

PW direction, the PW forwards packets after decapsulating them

and add VLAN Tags to them. Ethernet-tag: in in-PW direction, the PE encapsulates received

packets into the PW. In out-PW direction, the PW transmit

packets to the AC packets after decapsulating them.

By default, it is set to Ethernet.

In Label Configure the PW in-label, which ranges from 16 to 1048319.

Out Label Configure the PW out-label, which ranges from 16 to 1048575.

Tunnel Type Display the Tunnel type.

Tunnel Specified Configure the binding type between the PW and Tunnel.

Automatic select Manual binding

By default, it is set to Automatic select.

Tunnel Name When the Tunnel Specified is set to Manual binding, click

and then select a Tunnel ID to be bound. It ranges from 1 to 1024.

Peer Address When the Tunnel Specified is set to Automatic select, configure the

IP address of the peer device, which is in dotted decimal notation.

Raisecom





Is Send Control

Word

Configure whether to send the control word.

Yes No

The control word is an encapsulation packet header composed by 4

bytes. It is used to identify the packet order or act as the padding bit.

By default, the control word is sent.

EXP Configure the EXP priority.

0–7 Mapping: dynamic mapping

By default, it is set to Mapping.

Local Priority Configure the local priority.

0–7 Mapping: dynamic mapping Not-Change: use the fixed priority.


Request VLAN ID When the PW Type is set to Ethernet-tag, configure the CVLAN ID.

The CVLAN ID is used for the receiver PE (referring to Figure 8-4)

to locate the CE to which the packet is forwarded. It ranges from 0

to 4094.

TPID Configure the TPID of the VLAN, which is in hexadecimal notation

and is set to 0x8100, 0x9100, or 0x88A8.

MTU (byte) Configure the MTU of the PW, which ranges from 46 to 16383

bytes.

By default, it is set to 9600 bytes.

Remark Configure the remark, which ranges from 0 to 512 characters.


Step 5 After configurations, select the Deploy radio box and then click Ok.

Configuring static PW switching


Transit PW Management.





Base Info


Raisecom










packets into the PW. In out-PW direction, the PW transmit packets

to the AC packets after decapsulating them.

Is Send Control

Word


Yes No





Front-end PW

PW ID Configure the PW ID, which ranges from 1 to 2147483647.

Peer Address Configure the destination IP address, which is in dotted decimal

notation.






Back-end PW


Peer Address Configure the destination IP address, which is in dotted decimal

notation.








Raisecom




1. View configurations on global MPLS L2VPN.


System Config. Select the MPLS Global Config tab to view configurations on global MPLS

L2VPN.

2. View configurations on static L2VC.


ELine Management. Click Query Result (All) at the ELine Management area to view

configurations on static L2VC.

3. View configurations on Transit PW management.


Transit PW Management. Click Query Result (All) at the Transit PW Management area to

view configurations on Transit PW management.

4. View configurations on PW management.


PW Management. Click Query Result (All) at the PW Management area to view

configurations on PW management.

8.5 Configuring VPLS


Scenario

VPLS is a MPLS-based Layer 2 VPN technology. It allows users in multiple physical

locations to access to the network simultaneously and to communicate with each other. It

seems that these physical locations directly access to the LAN.

Prerequisite

Before configuring VPLS, you need to configure basic functions of MPLS, static LSP and

MPLS L2VPN.

8.5.2 Creating VPLS VSI

You can configure the VSI ID to identify the VSI ID. The VSI ID cannot be modified once is

successfully configured. The iTN201 provides independent VPLS service for each VSI.


VPLS Management.

Step 2 Right-click the blank area at the VPLS Management area and then choose Add from the right-

click menu.

Step 3 A dialog box appears and then select the VSI tab, where you can configure the VSI. The

following table describes parameters at the tab.


Raisecom





Service ID Configure the VSI ID, which ranges from 1 to 2147483647.

Service Identity Configure the VSI name, which ranges from 1 to 32 characters.

Associated Customer Configure the customers associated this service.

MAC Learn Count Configure the MAC address limit of the VSI. It ranges from 1

to 255 and is set to 0 by default.

Unicast Storm Control

Enable

Enable/Disable unknown unicast storm control of the VSI.

Enable Disable

By default, it is disabled.

Multicast Storm

Control Enable

Enable/Disable multicast storm control of the VSI.

Enable Disable


Broadcast Storm

Control Enable

Enable/Disable broadcast storm control of the VSI.

Enable Disable


MAC Address Study Enable/Disable MAC address learning.

Enable Disable


Broadcast Rate (pps) Configure the rate threshold of VSI broadcast packets. It

ranges from 1 to 262143 packets/s. By default, it is set to 1024

packets/s.

The broadcast rate threshold of the VSI can be used to prevent

wasting broadcast and resources and reducing system

performance.

MTU (byte) Configure the MTU of the VSI, which ranges from 46 to 16383

bytes.

By default, it is set to 9600 bytes.


8.5.3 Configuring VSI static PW


VPLS Management.


click menu.

Raisecom




Step 3 A dialog box appears and then select the PW tab. Click Add and then a dialog box appears,

where you can configure the PW. The following table describes parameters at the dialog box.










packets into the PW. In out-PW direction, the PW transmit

packets to the AC packets after decapsulating them.

By default, it is set to Ethernet.



Tunnel Type The Tunnel type is displayed as MPLS.




Peer Address When the Tunnel Specified is set to Automatic select, configure the

IP address of the peer device, which is in dotted decimal notation.

Is Send Control

Word


Yes No




EXP Configure the EXP priority.

0–7 Mapping: dynamic mapping


Local Priority Configure the local priority.

0–7 Mapping: dynamic mapping Not-Change: use the fixed priority.


Raisecom





ISOLATE Enable/Disable the isolation feature of the PW associated with the

VPLS service.

Enable Disable



8.5.4 Configuring VSI UNI


VPLS Management.


click menu.

Step 3 A dialog box appears and then select the UNI tab. Click Add and then a dialog box appears,

where you can configure the interface bound to the VSI. The following table describes

parameters at the dialog box.



Access Type Configure the service interface type.

Physical Interface: correspond to the switching interface. VLAN: correspond to the switching interface+VLAN.

By default, it is set to VLAN.

Port Name Click and then select the interface bound to the VSI.

VLAN Configure the VLAN of the interface. It ranges from 1 to 4094.

Service Priority Configure the service priority, which ranges from 0 to 7.

ISOLATE Enable/Disable the isolation feature of user VPLS service.

Enable Disable



1. View configurations on the VSI.


VPLS Management. Select a record and then click from the tool bar of the iTN201 EMS.

A dialog box appears, where you can view configurations on the VSI at the Base Info area.

Raisecom





VPLS Management. Select a record and then select the VSI Config tab to view

configurations on the VSI.

2. View configurations on the VSI static PW.


VPLS Management. Select a record and then select the PW Config tab to view

configurations on the VSI static PW VSI.

3. View configurations on the VSI UNI.


VPLS Management. Select a record and then select the UNI Config tab to view

configurations on the VSI UNI.


8.6.1 Examples for configuring bidirectional static LSP


As shown in Figure 8-10, User A has branches at 2 locations. You need to establish VPN

between the 2 locations. Therefore, devices at these 2 locations can communicate with each

other.

Because the network is small and stable, you can configure the bidirectional static LSP

between iTN A and iTN B and take it as the private Tunnel of the L2VPN.

Figure 8-10 Configuring the bidirectional static LSP

Configuration steps

Step 1 Configure basic functions of MPLS.

1. From the Action List of the iTN201 EMS, choose SNMP Management > Base MGT >

System Config.

2. Select the MPLS Global Config tab and then configure the LSR ID and enable MPLS at

the tab. The following table lists values of parameters.


Raisecom




Parameter Value of iTN A Value of iTN B Value of iTN C

MPLS LSR ID 192.168.1.1 192.168.4.2 192.168.1.2

MPLS Enable Enable Enable Enable

Step 2 Configure the bidirectional static LSP between iTN A and iTN B.

1. From the Action List of the iTN201 EMS, choose SNMP Management > Packet

Service > Tunnel Management > MPLS Tunnel Management.

2. Click from the tool bar of the iTN201 EMS and a dialog box appears, where you

can configure the static LSP. The following table lists values of parameters.

3. After configurations, select the Deploy radio box and then click Save.

Parameter Value of iTN A Value of iTN C Value of iTN B

Tunnel ID 1 1 1

Friendly Name Tunnel1 Tunnel1 Tunnel1

LSP Name lspAB lspAB lspAB

Direction Two-way Two-way Two-way

Node Type Ingress Transit Egress

Into Port – line 1 line 1

Forward into label – 1001 1002

Reverse out label – 2001 2002

Forward the next hop

address type

MAC MAC –

Forward next hop 00:0e:5e:11:11:13 00:0e:5e:11:11:12 –

Out Port line 1 line 2 –

Forward out label 1001 1002 –

Reverse into label 2001 2002 –

Reverse next hop

address type

– MAC MAC

Reverse next hop – 00:0e:5e:11:11:11 00:0e:5e:11:11:13

Source node address – 192.168.1.1 192.168.1.1

Destination node

address

192.168.4.2 192.168.4.2 –

Signaling Type Static Static Static

Forward Vlan ID 1 1 –

Reverse Vlan ID – 1 1

Raisecom




Checking results

1. View configurations on basic functions of MPLS.


System Config. Select the MPLS Global Config tab and then view configurations on basic

functions of MPLS.

2. View configurations on static LSP.


Tunnel Management > MPLS Tunnel Management. Select a record and then click

from the tool bar of the iTN201 EMS to view configurations on static LSP.

Raisecom


Element Management) 9 TDMoP


9 TDMoP

This chapter describes principles and configuration procedures of TDMoP, as well as related


Introduction

Configuring TDM interfaces

Configuring Tunnel

Configuring PW


9.1 Introduction As the 3G era comes, data services grow fast. However, traditional Time Division Multiplex

(TDM), based on Circuit Switched (CS) network, becomes a bottleneck due to the following

disadvantages:

Inadequate bandwidth

Low channel utilization rate

Poor expansibility

On the contrary, the Packet Switched Network (PSN), based on statistics and multiplexing,

becomes the trend of future networks with the following advantages:

Flexible networking

Adequate bandwidth

Low cost

However, PSN is not constructed within a short period. The TDM network is still predominant

and will coexist with the PSN for a long time. As a result, TDMoP is generated.

With TDMoP, TDM CS service can be transparently transmitted on a PSN. TDMoP is the

combination of traditional CS network and PSN and can share resources and support network

expansion.

The TDMoP services supported by the TDMoP sub-card of the iTN201 are PWE3-based

circuit emulation.

Raisecom




9.1.1 Principles of TDMoP technology

Overview of PWE3

PWE3 is a protocol structure for end-to-end tunnel transmission Layer 2 emulation services.

Figure 9-1 shows the principle of PWE3.

Step 1 Customer Edge 1 (CE 1) transmits TDM service data to Provider Edge 1 (PE) 1 through

Attachment Circuit (AC).

Step 2 PE1 encapsulates TDM service data to PW messages through related protocols to form one or

multiple PWs.

Step 3 PW messages are carried through the Tunnel defined by a PSN protocol, such as MPLS,

Metro Ethernet Forum (MEF), or UDP/IP, traverse the PSN, and reach PE 2.

Step 4 PE 2 removes headers of PW messages at the egress interface, decapsulates and transmits

TDM service data to CE 2 through AC.

Figure 9-1 Principle of PWE3

CE: connected to the ISP network through the TDM interface. A CE is a TDM device.

The CE cannot sense the PSN.

AC: an independent link/circuit that connects a CE and a PE. Ac properties include the

encapsulation type, MTU, interface parameters of specified links.

PE: a device at the edge of ISP network, connected to a CE. A PE is a TDMoP device. At

the PSN side, the PE encapsulates received TDM service data into emulation messages

and then transmits emulation messages to the PTN through the uplink interface. At the

E1/T1 side, the PE decapsulates received emulation messages to TDM service data, and

transmits TDM service data to the CE.

Tunnel: a tunnel transparently transmitting TDM emulation messages across the PSN

TDM interface

At present, TDMoP is used to emulate low-speed PDH services and transparently transmit

E1/T1 services on a PSN. E1/T1/E3/T3, early used in voice communication, is widely used in

data communication now.

The E1/T1 interface, a physical layer interface, can connect Public Switched Telephone

Network (PSTN) devices, private network devices, and user access network devices. It carries

Layer 2 services, such as TDM, frame relay, and ATM services.

E1

− Be used in European and China, etc.

Raisecom




− The E1 interface speed is 2.048 Mbit/s. An E1 frame is composed of 32 timeslots,

numbering TS0 through TS31. The speed of each timeslot is 64 Kbit/s.

− An E1 frame is 256 bits long, and takes 125 μs to be transmitted. Each timeslot is 8

bits long.

− E1 data is in three modes: framed, multiframed, and unframed.

− In a multiframed E1, TS0 carries Frame Alignment Signal (FAS), CRC-4, and peer

alarm indicator, and TS16 carries Channel Associated Signaling (CAS), multi-FAS,

and multiframe peer alarm indicator.

− In a framed E1, TS0 carries FAS and uses out-of-band Common Channel Signaling

(CCS), and TS16 carries service data. Namely, TS1 through TS31 carry service data.

− All 32 timeslots of the unframed E1 are used to transmit service data.

T1

− Be used in USA and Japan, etc.

− The T1 interface speed is 1.544 Mbit/s. A T1 frame is composed of 24 timeslots. The

speed of each timeslot is 64 Kbit/s.

− A T1 frame is 193 bits long, and takes 125μs to be transmitted. Each timeslot is 8 bits

long. A bit of frame alignment or error indicator is added to each frame.

− T1 data is in two modes: super frame, Extended Super Frame (ESF).

Tunnel

Tunnel is a tunnel that carries TDM service to traverse the PSN. It is a path used to

transparently transmit data between the local PE and peer PE. TDM service data is

encapsulated in PW emulation messages, and thus is invisible to the Tunnel. A Tunnel can

carry one or multiple PWs.

Tunnel is defined based on protocols in the PSN.

Tunnel of MPLS protocol is defined by MPLS outer label.

Tunnel of UDP/IP protocol is defined by the IP layer.

Tunnel of MEF 8.0 protocol is defined by the Ethernet layer.

PW

PW is a mechanism that encapsulates TDM service data into PW emulation messages and

then uses the Tunnel to carry these PW emulation messages to traverse the PSN. PW supports

the following functions:

Encapsulate TDM service data into PW emulation messages.

Provide a Tunnel that can carry a PW emulation message to traverse the PSN.

Establish PW connection, distribute and exchange PW labels at the Tunnel ends.

Sort PW messages and extract clock signals.

Manage data status and alarms of TDMoP circuit emulation services.

With distribution and exchange of PW labels, TDMoP circuit emulation services can be

forwarded among different nodes in the PSN. The PW label is used to identify PW emulation

message flows in the same channel, so same PW labels cannot coexist in a Tunnel. The PW

label is defined by the related PSN.

MPLS: the PW label is defined by the innermost label of the MPLS protocol.

Raisecom




UDP/IP: the PW label is defined by the UDP port. You need to manually bind the ingress

port ID and egress port ID for a PW at the ends of the PW.

9.1.2 TDMoP service encapsulation protocol

TDM services are encapsulated into emulation messages by using the adaption protocol.

Based on encapsulation mode, protocols are grouped into structured and unstructured

protocols. The following sections describe 2 encapsulation protocols supported by the iTN201.

Structure-Agnostic TDM over Packet (SAToP)

Structure-Aware TDM Circuit Emulation Service over Packet-Switched Network

(CESoPSN)

SAToP

SAToP provides emulation for low-speed PDH circuit services, such as E1, T1, E3, and T3

services. It encapsulates unstructured services only. It takes TDM services as a serial data flow,

fragments and encapsulates it into PW packets for transmission. SAToP is defined by the

RFC4553.

SAToP encapsulation principles of MPLS-based TDM data are shown in Figure 9-2. E1/T1

data flow is taken as binary codes to be fragmented into data packets with a fixed length and

then be encapsulated into TDM payload. The outer lay is encapsulated by the Real-time

Transport Protocol (RTP) header, SAToP control word, and MPLS label. Therefore, a PW

emulation message is composed.

Figure 9-2 SAToP encapsulation principle

SAToP control word

An emulation message encapsulated by the SAToP protocol contains a 4-byte control word, as

shown in Figure 9-3.

Figure 9-3 Structure of the SAToP control word

Table 9-1 describes fields of the SAToP control word.

Raisecom




Table 9-1 Fields of the SAToP control word

Field Length (bit) Description

0000 4 Provide the necessary MPLS payload discrimination.

It is used to identify the begin of ACH when you need

to use Virtual Circuit Connectivity (VCC) to monitor

SAToP-based PW status.

By default, the value is set to 0.

L 1 If the value is set to 1, it indicates the TDM link fails.

That is, the TDM data encapsulated by SAToP is

incorrect. It also indicates ignoring the TDM data in

the packet to save bandwidth resources.

R 1 If the value is set to 1, it indicates the PSN-side packet

loss ratio exceeds the preconfigured threshold,

notifying the peer that the local is in the packet loss

status.

Identify whether the connection feature at the local CE

side is in packet status. It the value is set to 0, it

indicates the device receives continuous packet and the

packet is not lost.

Reserved 2 By default, the value is set to 0.

Fragmentation 2 Indicate the packet is encapsulated in fragment.

00: the packet encapsulates the whole TDM data. 01: the packet encapsulates the first fragment of the

TDM data. 10: the packet encapsulates the last fragment of the

TDM data. 11: the packet encapsulates the middle fragment of

the TDM data.


Length 6 Indicate the size of SAToP packet (defined as SAToP

overhead size + TDM payload size). The value must

be set to 0 if the length is more than 64 bytes.

Sequence

number

16 Indicate the serial number for the SAToP encapsulated

packet, used for detecting packet loss ratio. The initial

value is generated randomly. The sequence number is

added by one when a packet is sent.

RTP

RTP supports end-to-end transmission of real-time data across a network, such as unicast-

based and multicast-based voice, video, and emulation services.

Varying on protocols adopted by the PSN, positions of the RTP field in emulation messages

are different. The RTP field precedes the SAToP control word for UDP/IP PSN, while the RTP

field follows the SAToP control word in other PSN networks. The RTP field is an optional 12-

byte filed in an encapsulation protocol header.

Raisecom




RTP provides a sequence number for identifying the emulation packet, whose function is

similar to the sequence number of the SAToP control word. However, the RTP sequence

number does not coexist with the sequence number of the SAToP control word. The RTP

structure is shown in Figure 9-4.

Figure 9-4 Structure of RTP packet header

Table 9-2 describes fields of the RTP packet header.

Table 9-2 Fields of RTP packet header


V 2 RTP protocol version

P 1 Padding flag

If the value is set to 1, it indicates that one or more extra 8-

bit are padded at the end of the message. The padding is not

valid payload.

X 1 Extended flag

If the value is set to 1, it indicates that an extended packet

header is padded after the RTP packet header.

CC 4 Contributing Sources (CSRC) counter

It indicates the number of CSRC identifiers.

M 1 Marker

Different payloads have different markers.

PT 7 Valid information carried in the payload

Sequence

number

16 Sequence number of a RTP packet

It grows by 1 when a packet is sent.

With it, the receiver detects packet loss ratio and resorts

packets.

Timestamp 32 Time index for the first sample of the RTP packet

It has two modes: absolute mode and differentiated mode.

With it, the receiver calculates delay and jitter.

SSRC 32 Synchronization Source (SSRC) Identifier, used to detect

error connection

Raisecom





CSRC 32 Contributing Source (CSRC) Identifier, used to identify all

contributing sources contained in the valid payload of the

RTP packet

TDM payload

In SAToP encapsulation mode, TDM frame structure is not identified. Instead, TDM service

data is fragmented and encapsulated, and then transparently transmitted.

After a PW connection is established, the length of SAToP encapsulation packets

is fixed accordingly. For a PW, the length in both two directions must be identical and keeps fixed in the whole working period.

The length of SAToP encapsulation packets cannot exceed the MTU between 2 PEs.

CESoPSN

CESoPSN, defined by the RFC5086, emulates low-speed PDH circuit services, such as E1

services. It is a structured TDM service emulation protocol and can identify and process E1

frame structure and internal frame signaling. CESoPSN discards idle timeslots and

encapsulates timeslots in use, thus improving bandwidth utilization.

Figure 9-5 shows CESoPSN encapsulation principle for MPLS-based TDM data. Frame

structure of E1/T1 specified timeslot is encapsulated into the TDM payload. The outer lay is

encapsulated by the RTP header, CESoPSN control word, and MPLS label. Therefore, a PW

emulation message is composed. The length of the TDM payload in the packet is a multiple of

the length of E1/T1 frame structure (125 μs).

Figure 9-5 CESoPSN encapsulation principle

CESoPSN control word

The CESoPSN encapsulation protocol contains a 4-byte control word, whose format is shown

in Figure 9-6.

Raisecom




Figure 9-6 Structure of the CESoPSN control word

Table 9-3 describes fields of the CESoPSN control word.

Table 9-3 Fields of the CESoPSN control word


0000 4 Provide the necessary MPLS payload discrimination.


L 1 If the value is set to 1, it indicates the TDM link fails.

That is, the TDM data encapsulated by CESoPSN is

incorrect.

R 1 If the value is set to 0, it indicates the PSN-side packet

loss ratio exceeds the preconfigured threshold,

notifying the peer that the local is in the packet loss

status.

M 2 It indicates signaling detection at the AC side.

Combination of M and L indicates that packet received

from the PSN side is a signaling packet or a service

packet.

Fragmentation 2 Indicate the packet is encapsulated in fragment.

00: the packet encapsulates the whole TDM data. 01: the packet encapsulates the first fragment of the

TDM data. 10: the packet encapsulates the last fragment of the

TDM data. 11: the packet encapsulates the middle fragment of

the TDM data.


Length 6 Indicate the size of CESoPSN packet (defined as

CESoPSN overhead size + TDM payload size). The

value must be set to 0 if the length is more than 64

bytes.

Sequence

number

16 Indicate the serial number for the SAToP encapsulated

packet, used for detecting packet loss ratio.

RTP

The RTP field precedes the CESoPSN control word for UDP/IP PSN, while the RTP field

follows the CESoPSN control word in other PSN networks. The RTP field is an optional 12-

byte filed in an encapsulation protocol header, whose structure and function are identical to

ones of SAToP protocol.

Raisecom




TDM payload

The payload of a CESoPSN encapsulation packet is a basic NxDS0 data queue with or

without signaling. Signaling and basic NxDS0 data can be encapsulated independently or

together. There are three encapsulation modes: encapsulation of basic NxDS0 data,

encapsulation of NxDS0 signaling, and encapsulation of NxDS0 data and signaling.

After a PW connection is established, the length of a CESoPSN encapsulation

packet is fixed accordingly. The encapsulation payload time granularity is set to 125 μs.

The length of PW encapsulation packets in all directions must be identical. CESoPSN encapsulation packet discards invalid TDM service data and then the L

field of the CESoPSN control word is set to 1.

Encapsulation of basic NxDS0 data

As shown in Figure 9-7, the payload of a CESoPSN encapsulation packet consists of M

frames (Frame 1 to Frame M). A frame has N timeslots in use (that is, NxDS0 carrying data).

When the CESoPSN encapsulation packet is forwarded through the PW, Frame 1 of the

payload will be forwarded first. The length of the CESoPSN encapsulation packet is a

multiple of a frame, and is related to the delay.

Figure 9-7 Format for CESoPSN encapsulation of basic NxDS0 data

Encapsulation of basic NxDS0 signaling

As shown in Figure 9-8, the payload of the CESoPSN packet consists of N signaling codes of

DS0 channel, which means the payload of the CESoPSN packet only contains DS0 signaling.

This encapsulation mode is a supplement of basic NxDS0 encapsulation mode.

Figure 9-8 Format for CESoPSN encapsulation of basic NxDS0 signaling

A signaling encapsulation packet uses an independent sequence number. Values of some bits in the control word of the signaling encapsulation packet are

set as follows: L = 0, M = 11, and R = 0. If the RTP header exists in the signaling encapsulation packet, a PT mark is

assigned specially to the packet with independent SSRC.

Encapsulation of basic NxDS0 and signaling

As shown in Figure 9-9, a CESoPSN encapsulation packet consists of M frames (Frame 1 to

Frame M). A frame contains N NxDS0 with data. The signalling also contains signalling

codes corresponding to NxDS0. Each signaling code occupies 4 bits. A byte is composed of 2

DS0 signaling codes or a DS0 signaling code and padding bits (if not adequate for a byte).

Raisecom




Figure 9-9 Format for CESoPSN encapsulation of basic NxDS0 and signaling

9.1.3 TDMoP clock recovery technology

TDMoP technology requires TDM services to be transmitted across the PSN. The

combination of PSN and TDM network may damage code stream and affect clock

synchronization between the sender and the receiver, going against real-time transmission.

To eliminate influence on the clock signals brought by the PSN, the TDMoP technology

adopts the clock synchronization mechanism to ensure clock synchronization information to

be transparently transmitted across the PSN. This helps achieve synchronization between the

sender and receiver.

At present, the main clock synchronization mechanisms used by TDMoP technology are as

below:

Self-adaptive clock recovery

Differential clock recovery

External clock input

Link loopback clock

System clock

9.1.4 TDMoP delay jitter buffer technology

Delay jitter is the delay change of frames in a network. That is, after transmission, the delay

for each frame in the network is variable. This changeable delay is called jitter. The cause to

delay jitter is that the bearing network (PSN) of TDM services is asynchronous and frames are

transmitted in different paths. Frame Packet jitter has great impact on performance of

emulation services. Therefore, compensation must be taken to emulation services.

The jitter buffer on the destination can reduce the impact caused by frame delay changes. It

buffers early or late packets. Its capacity can be dynamically configured as required.

9.2 Configuring TDM interfaces


Scenario

The iTN201 accesses TDM services through 8 E1/T1 interfaces of the TDMoP sub-card. Each

interface can be configured independently. When providing 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, code of TDM idle timeslots, and signaling codes

of idle and occupied timeslots.

Raisecom




When a TDM interface is in unframed mode, the TDM frame structure is not recognized.

When a TDM interface is in framed/multiframed mode, TDM frame structure can be

recognized.

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 TDMoP sub-card is available.

9.2.2 Configuring link type of TDM interfaces

If a TDM interface is related to a PW, you cannot change its link type unless deleting the related PW.

Step 1 From the Action List of the iTN201 EMS, choose SNMP Management > Port MGT >

TDM Config.

Step 2 Select a record and then click from the tool bar of the iTN201 EMS.

Step 3 A dialog box appears, where you can configure the link type of the TDM interface. The




Line Type Select a link type of the TDM interface.

E1 Framed: E1 framed mode E1 Unframed: E1 unframed mode T1 D4: T1 super frame mode T1 EST: T1 ESF mode T1 Unframed: T1 unframed mode

By default, it is set to E1 Unframed.

Circuit Identifier Configure the link identifier of the TDM interface, which ranges from

1 to 255 characters. By default, it is set to slot ID-TDM interface ID,

such as slot 1-TDM 2.

Signal Mode Configure whether the TDM interface carrying CAS.

None: the TDM interface carries CAS. CAS: the TDM interface does not carry CAS.

By default, it is set to None.

This parameter is available when the Line Type is set to E1 Framed,

T1 D4, or T1 ESF.

Raisecom





CRC Checker Configure whether the TDM interface performing CRC.

enable: the TDM interface performs CRC. disable the TDM interface does not perform CRC.

By default, the TDM interface does not perform CRC.

This parameter is available when the Line Type is set to E1 Framed.

9.2.3 Configuring loopback of TDM interfaces


TDM Config.


Step 3 A dialog box appears, where you can configure the loopback type of the TDM interface. The




Loopback Config Select a loopback type of the TDM interface.

dsx1 NoLoop (1) dsx1 LineLoop (3) dsx1 InwardLoop (5) bi-directional

by default, it is set to dsx1 NoLoop (1).

9.2.4 Configuring Tx clock source of TDM interfaces

The TDM interface adopts the TDMoP clock recovery technology based on the Tx clock

source.


TDM Config.


Step 3 A dialog box appears, where you can configure the Tx clock source of the TDM interface.



Raisecom





Transmit Clock

Source

Select the Tx clock source of the TDM interface.

system: system clock loopback: link loopback clock adaptive: self-adaptive clock differential: differential clock external: external clock

By default, it is set to system.

When the Tx clock source of a TDM interface is set to self-

adaptive/differential clock, you need to configure a PW as a recovery

clock source in advance and then extract the recovery clock from the

PW.

9.2.5 Configuring codes for TDM idle timeslots

When TDM services are in framed/multiframed mode, idle timeslots do not carry any service.

To save bandwidth resources, idle timeslots are not encapsulated in structured encapsulation

mode. When encapsulated TDM services is transmitted to the peer device through the Tunnel

and TDM frame structure is re-created at E1/T1 side, idle timeslots are padded with codes.


TDM Config.


Step 3 A dialog box appears, where you can configure codes for TDM idle timeslots. The following




Port Display the TDM interface ID.

Ts Idle Code Configure codes for idle timeslots, which ranges from 0 to 255.




View status of the current TDM interface.

From the Action List of the iTN201 EMS, choose SNMP Management > Port MGT > TDM

Config. Select a record and then click from the tool bar of the iTN201 EMS to view

status of the current TDM interface.

Raisecom




9.3 Configuring Tunnel


Scenario

The Tunnel is a tunnel carrying TDM emulation services. Before configuring PW, you must

configure Tunnel properties, including the destination MAC address and MPLS properties.

Prerequisite

N/A

9.3.2 Creating MEF Tunnel


Tunnel Management > MEF Tunnel Management.





Friendly Name Configure the friendly name of the Tunnel, which ranges from 1 to

200 characters.

Tunnel Name Configure the Tunnel name, which ranges from 1 to 32 characters.

Destination node

address

Configure the MAC address of the destination TDMoP device,

which is in dotted hexadecimal notation.

Vlan Mode Select a VLAN Tag mode.

tag: the packet carries a single VLAN Tag. double tag: the packet carries double VLAN Tags. untag: the packet does not carry the VLAN Tag.

Inner Vlan ID Configure the inner VLAN ID, which ranges from 1 to 4094.

Inner Vlan Priority Configure the inner VLAN priority, which ranges from 0 to 7.

Remark Configure the remark on the Tunnel, which ranges from 0 to 512

characters.

9.3.3 Creating IP Tunnel

Before configuring IP Tunnel, you need to configure the IP address and mask of the TDMoP sub-card. Otherwise, configurations fail. To configure the IP address and mask of the TDMoP sub-card, choose SNMP Management > Base MGT > System

Raisecom




Config from the ITN201 EMS and then select the SubCard Config tab. For details, see section 9.4.2 Configuring IP address of the TDMoP sub-card.


Tunnel Management > IP Tunnel Management.





Friendly Name Configure the friendly name of the Tunnel, which ranges from 1 to

200 characters.

Tunnel Name Configure the Tunnel name, which ranges from 1 to 32 characters.

SLOT Select the slot where the TDMoP sub-card is inserted.

1 2

Destination node

address

Configure the IP address of the destination TDMoP device, which


Next hop address

type

Select the next-hop address type.

None MAC IP

By default, it is set to None, which means that no next-hop address

is selected.

Next hop mac/ip

address

Configure the next-hop address.

Enter the next-hop MAC address that is in dotted hexadecimal

notation, when the Next hop address type is set to MAC. Enter the next-hop IP address that is in dotted hexadecimal

notation, when the Next hop address type is set to IP.

Vlan Mode Select a VLAN Tag mode.

tag: the packet carries a single VLAN Tag. double tag: the packet carries double VLAN Tags. untag: the packet does not carry the VLAN Tag.

Inner Vlan ID Configure the inner VLAN ID, which ranges from 1 to 4094.

Inner Vlan Priority Configure the inner VLAN priority, which ranges from 0 to 7.

IP TTL Configure the TTL value, which ranges from 1 to 255.

IP TOS Configure the ToS value, which ranges from 0 to 7.

Remark Configure the remark of the Tunnel, which ranges from 0 to 512

characters.



Raisecom




1. View configurations on MEF Tunnel.


Tunnel Management > MEF Tunnel Management. Select a record and then click from

the tool bar of the iTN201 EMS to view configurations on MEF Tunnel.

2. View configurations on IP Tunnel.


Tunnel Management > IP Tunnel Management. Select a record and then click from the

tool bar of the iTN201 EMS to view configurations on IP Tunnel.

9.4 Configuring PW


Scenario

The PW packet carries TDM service payloads. One PQ is a service flow.

The TDMoP sub-card of the iTN210 can be configured with up to 64 PWs.

Prerequisite

You have configured and deployed the Tunnel.

9.4.2 Configuring IP address of the TDMoP sub-card

The IP address of the TDMoP sub-card and the management IP address of the iTN201 should be in different network segments.


System Config and then select the SubCard Config tab.

Step 2 Select a record and then click Modify. A dialog appears, where you can configure the IP

address of the TDMoP sub-card. The following table describes items at the dialog box.



SubCard IP

Address

Configure the IP address of the TDMoP sub-card, which is in dotted

decimal notation.

SubCard IP Mask Configure the mask of the IP address, which is in dotted decimal

notation.

Raisecom




9.4.3 Creating PW and configuring PW properties

The PW label value corresponds to the innermost label value of MPLS. The PW Jitter Buffer size must be equal to or greater than the PW packet

encapsulation time. When you enable PW connection, the iTN201 EMS will check current

configurations of the PW. If configurations are conflicted, incorrect, or incomplete, the operation will fail.


CES Config.





Service ID Configure the service ID.

Service Name Configure the service name, which ranges from 1 to 200 characters.

Associated Customer Click and then select the customer associated to the service.

Encapsulate Type Configure the encapsulation type of services

SAToP: unstructured encapsulation CESoPSN: structured encapsulation

Port Select a TDM interface ID

TDM Time SLot Click and select the timeslot to be used, which ranges from 1

to 31. This parameter is available for structured encapsulation.

Encapsulate RTP

Head

Enable/Disable emulation packet header RTP.

Enable Disable

By default, emulation packet header RTP is disabled.

Jitter Buffer Time

(µs)

Configure the delay jitter buffer size, which ranges from 375 to

160000µs and is set to 3750 by default.

Message Loading

Time (µs)

Configure the loading time of encapsulated packets, which ranges

from 125 to 5000us and the unit is set to 125µs.

By default, it is set to 1000µs.

Missing pkts (%) Configure the packet loss ratio, which ranges from 1% to 100%.

Out Synch Threshold Configure the sequential frame loss threshold, which ranges from 1

to 15 and is set to 15 by default.

The iTN201 will record a log or send a Trap when the sequential

frame loss threshold is reached.

Remark Configure the remark of the PW, which ranges from 0 to 512

characters.

Raisecom





9.5.1 Examples for configuring CESoPSN emulation services


As shown in Figure 9-10, the user has offices in sites A and B. Telephones of sites A and B

access to the PTN through iTN A and iTN B respectively. Telephones of sites A and B need to

communicate with each other through the PTN. Configurations are shown as below:

Site A:

– Occupied timeslots: TS6–TS10 and TS17–TS31

– Idle timeslots: TS1–TS5 and TS11–TS15

Site B:

– Occupied timeslots: TS6–TS10 and TS17–TS31

– Idle timeslots: TS1–TS5 and TS11–TS15

IP address of iTN B: 192.168.10.1 (configured on the iTN A)

Encapsulation protocol: CESoPSN protocol

LSR ID of iTN A: 10.1.1.1

Figure 9-10 Configuring CESoPSN emulation services

Configuration steps

Configuration steps of iTN A are identical to the ones of iTN B. In this guide, only

configurations on iTN A are described.

Step 1 Configure the TDM interface.

1. From the Action List of iTN A EMS, choose SNMP Management > Port MGT >

TDM Config.

2. Select the record about TDM interface 2 in slot 1 and then click from the tool bar of

iTN A EMS.

Raisecom




3. A dialog box appears, where you can configure parameters of the TDM interface. The



Parameter Value

Line Type E1 Framed

Signal Mode CAS

CRC Checker Enable

Ts Idle Code 20

Step 2 Configure basic functions of MPLS.

1. From the Action List of the iTN A EMS, choose SNMP Management > Base MGT >

System Config.

2. Select the MPLS Global Config tab and then configure basic functions of MPLS at the

tab. The following table lists values of parameters.


Parameter Value

MPLS LSR ID 10.1.1.1

MPLS Enable Enable

Step 3 Configure the Tunnel and LSP.

1. From the Action List of the iTN A EMS, choose SNMP Management > Packet

Service > Tunnel Management > MPLS Tunnel Management.

2. Click from the tool bar of the iTN A EMS and a dialog box appears, where you can

configure the Ingress LSP. The following table lists values of parameters.


Parameter Value

Tunnel ID 1

LSP Name a2b

Direction One-way

Node Type Ingress

Forward the next hop address type MAC

Forward next hop 00:0e:5e:11:11:13

Out Port Line 1

Forward out label 102

Destination node address 192.168.10.1

Raisecom




Parameter Value

Signaling Type Static

Forward Vlan ID 1

Step 4 Configure the PW.

1. From the Action List of the iTN A EMS, choose SNMP Management > Packet

Service > CES Config.

2. Click from the tool bar of the iTN A EMS and a dialog box appears, where you can

configure the CES service. The following table lists values of parameters.

Parameter Value

Service ID 100

Service Name CES

Encapsulate Type CESoP

Port TDM 1/2

TDM Time SLot TDM2/TS6–TS10 and TS17–TS31

Encapsulate RTP Head Enable

Jitter Buffer Time (µs) 8000

Message Loading Time (µs) 1000

Missing pkts (%) 35

Out Synch Threshold 10

3. Click Config PW and a dialog box appears, where you can configure the PW. The


Parameter Value

In Label 100

Out Label 200

Tunnel Specified Automatic select

Peer Address 192.168.10.1


Step 5 Configure the TDMoP clock.

1. From the Action List of the iTN A EMS, choose SNMP Management > Port MGT >

TDM Config.

2. Select a record and then click from the tool bar of the iTN A EMS.

Raisecom




3. A dialog box appears, where you can configure the Tx clock source of the TDM

interface. The following table lists values of parameters.


Parameter Value

Transmit Clock Source differential

Associated PW Name 100

Checking results

1. View configurations on the TDM interface and TDMoP clock.

From the Action List of the iTN201 EMS, choose SNMP Management > Port MGT > TDM

Config. Select a record and then click from the tool bar of the iTN201 EMS to view

status of the current TDM interface.

2. View configurations on basic functions of MPLS.


System Config. Select the MPLS Global Config tab and then view configurations on basic

functions of MPLS.

3. View configurations on the Tunnel and LSP.


Tunnel Management > MEF Tunnel Management. Select a record and then click

from the tool bar of the iTN201 EMS to view configurations on the Tunnel and LSP.

4. View configurations on the PW.


CES Config. Select a record and then click from the tool bar of the iTN201 EMS to

view configurations on the PW.

Raisecom


Element Management) 10 OAM


10 OAM

This chapter describes principles and configuration procedures of OAM, as well as related


Introduction

Configuring EFM

Configuring CFM

Configuring MPLS-TP CFM

Configuring SLA

Configuring RFC2544


10.1 Introduction Initially, Ethernet is designed for LAN. Operation, Administration and Maintenance (OAM) is

weak because of its small size and a NE-level administrative system. With continuous

development of Ethernet technology, the application scale of Ethernet in Telecom network

becomes wider and wider. Compared with LAN, the link length and network size of Telecom

network is bigger and bigger. The lack of effective management and maintenance mechanism

has seriously obstructed Ethernet technology applying to the Telecom network.

To confirm connectivity of Ethernet virtual connection, effectively detect, confirm, and locate

faults on Ethernet layer, balance network utilization, measure network performance, and

provide service according Service Level Agreement (SLA), implementing OAM on Ethernet

has becoming an inevitable developing trend.

10.1.1 EFM

Complying with IEEE 802.3ah protocol, Ethernet in the First Mile (EFM) is a link-level

Ethernet OAM technology. It provides link connectivity detection, link fault monitoring, and

remote fault notification, etc. for a link between two directly connected devices. EFM is

mainly used for Ethernet links on edges of the network accessed by users.

10.1.2 CFM

Connectivity Fault Management (CFM) is a network-level Ethernet OAM technology,

providing end-to-end connectivity fault detection, fault notification, fault judgement, and fault

Raisecom




location. It is used to diagnose fault actively for Ethernet Virtual Connection (EVC), provide

cost-effective network maintenance solution, and improve network maintenance via the fault

management function.

The iTN201 provides CFM that is compatible with both ITU-Y.1731 and IEEE802.1ag

standards.

CFM consists of following components:

MD

Maintenance Domain (MD), also called Maintenance Entity Group (MEG), is a network that

runs CFM. It defines network range of OAM management. MD has a level property, with 8

levels (level 0 to level 7). The bigger the number is, the higher the level is and the larger the

MD range is. Protocol packets in a lower-level MD will be discarded after entering a higher-

level MD. If no Maintenance association End Point (MEP) but a Maintenance association

Intermediate Point (MIP) is in a high-level MD, the protocol can traverse the higher-level MD.

However, packets in a higher-level MD can traverse lower-level MDs. In the same VLAN

range, different MDs can be adjacent, embedded, but not crossed.

Service instance

The service instance is also called a Maintenance Association (MA). It is a part of a MD. One

MD can be divided into one or multiple service instances. One service instance corresponds to

one service and is mapped to a group of VLANs. VLANs of different service instances cannot

cross. Though a service instance can be mapped to multiple VLANs, one instance can only

use a VLAN for sending or receiving OAM packets. This VLAN is the master VLAN of the

service instance.

MEP

The MEP is an edge node of a service instance. MEPs can be used to send and process CFM

packets. The service instance and the MD where the MEP locates decide VLANs and levels of

packets received and sent by the MEP.

For any device that runs CFM in the network, the MEP is called local MEP. For MEPs on

other devices of the same service instance, they are called Remote Maintenance association

End Points (RMEP).

Multiple MEPs can be configured in a service instance. Packets sent by MEPs in one instance

take identical S-VLAN TAG, priority, and C-VLAN TAG. A MEP can receive OAM packets

sent by other MEPs in the instance, intercept packets which at the same or lower level, and

forward packets of higher level.

The MIP is the internal node of a service instance, which is automatically created by the

device. MIP cannot actively send CFM packets but can process and response to LinkTrace

Message (LTM) and LoopBack Message (LBM) packets.

MP

MEP and MIP are called Maintenance Point (MP).

10.1.3 SLA

SLA is an agreement between users and a service provider about the service quality, priority,

and responsibility. It is a telecommunication service evaluating standard negotiated by the

service provider and users.

In technology, SLA is a real-time network performance detection and statistic technology,

which can collect statistics on responding time, network jitter, delay, and packet loss ratio, etc.

Raisecom




SLA can be used to monitor related metrics by selecting different tasks for different

applications.

Ethernet throughput test (ETH-Test involved in this guide) is used for diagnostic test on

continuous services. It is a part of ETH-Test technology defined by Y.1731. You can test the

Layer 2 network throughput by configuring the test operation and enabling scheduling.

Basic concepts involved in SLA are shown as follows:

Operation

It is a static concept. It is a point-to-point SLA network performance test task, including Layer

2 network delay/jitter test (y1731-echo/y1731-jitter), throughput, and packet loss test, as well

as Layer 3 network delay/jitter test (icmp-echo/icmp-jitter).

Test

It is a dynamic concept. It is used to describe an execution of one operation.

Detection

It is a dynamic concept. It is used to describe a procedure for sending-receiving detection

packets in a test. According to the definition of operation, one test can contain multiple

detections (For an Echo operation, one test contains one detection only).

Scheduling

It is a dynamic concept. It is used to describe a scheduling of one operation. One scheduling

contains multiple periodical tests.

10.1.4 RFC2544

With widely application of Ethernet, more and more users perform data communicate through

Ethernet services. Ethernet services are configured and established based on SLA signed by

the Carrier and users. Users care whether the Carrier can provide trusted service type and QoS.

Three network metrics are used to define quality of services provided by the Carrier:

Ethernet throughput (network bandwidth)

Ethernet delay

Ethernet packet loss rate

The Carrier tests the quality of service based on these 3 metrics to meet users' requirements.

RFC2544 is a network benchmarking test process and test method defined by Request For

Comments (RFC) recommendations. It is used to test, evaluate, and analyze Ethernet

performance. Therefore, the Carrier and users can reach an agreement on execution and result

of network quality measurement at the same benchmarking level. In addition, it helps enhance

network operating quality further.

The following phases of Ethernet operation is involved in RFC2544 Ethernet service

benchmarking test:

Ethernet design and construction phase

Ethernet test and acceptance phase

Ethernet service debugging and connection

Ethernet routine maintenance and fault diagnostics

As shown in Figure 10-1, iTN A supports RFC2544 test feature and is taken as a tester. The

test packet sent by iTN A passes through the Device Under Test (DUT) and is forwarded to

Raisecom




iTN B which is enabled with interface loopback. The test packet returns to iTN A to finish the

test. A test result is obtained through RFC2544.

Figure 10-1 RFC2544 benchmarking test

RFC2544 benchmarking test needs to establish an independent test environment while ETH-

Test can be used in a test scenario where Ethernet services are not interrupted.

10.1.5 MPLS-TP OAM

MPLS-TP OAM can effectively detect, recognize, and locate faults generated at the MPLS

layer. In addition, it can perform protection switching quickly when the link/node fails.

OAM is an effective method to reduce network maintenance cost. The MPLS-TP OAM

mechanism is used for maintenance and management at the MPLS layer.

MPLS-TP OAM is an independent mechanism, providing the following functions:

Detect, recognize, and locate faults generated at the MPLS layer effectively.

Measure network utilization rate and network performance effectively.

Perform protection switching quickly when the link/node fails to reduce shutdown time

and improve network reliability.

On the iTN201, MPLS-TP OAM is realized by combining the Generic Associated Channel

(GACH) technology defined in RFC5586 ad OAM technology defined in Y.1731.

10.2 Configuring EFM


Scenario

Deploying EFM between directly-connected devices can effectively improve the management

and maintenance capability of Ethernet links and ensure network running smoothly.

Prerequisite

Before configuring EFM, you need to connect interfaces and configure physical parameters of

interfaces. Make the physical layer Up.

Raisecom




10.2.2 Configuring basic functions of EFM

Enabling OAM and configuring EFM working modes on interfaces


OAM MGT (802.ah) > OAM Table and then select the OAM Table tab.


Step 3 A dialog box appears, where you can enable OAM and configure EFM working modes. The




OAM Administration

State

Enable/Disable OAM.

Enable Disable

By default, OAM is enabled.

OAM Operation

Mode

Select an OAM working mode.

active: the interface send OAM Protocol Data Unit (PDU)

actively to initiate peer discovery or remote loopback. passive: the interface waits for the OAM PDU sent by the peer

passively.

By default, it is set to passive.

(Optional) configuring the period for sending OAM PDU and link timeout


OAM MGT (802.ah) > OAM Table.

Step 2 Select the OAM Global Config tab, where you can configure the period for sending OAM

PDU and link timeout. The following table describes parameters at the tab.


Send period Configure the period for sending OAM PDU. It ranges from 1 to 100 and

is set to 10 by default. The unit is set to 100ms.

Link time out Configure the link timeout, which ranges from 1 to 10s and is set to 5s by

default.

Configuring remote loopback information


OAM MGT (802.ah) > OAM Table and then select the OAM Loopback Timeout tab.


Raisecom




Step 3 A dialog box appears, where you can configure the remote loopback information. The




Loopback

Timeout (second)

Configure the timeout, which ranges from 1 to 10s and is set to 3s

by default.

Loopback Retry

Times

Configure the retry times, which ranges from 0 to 10 and is set to 2

by default.

10.2.3 Configuring active functions of EFM

Active functions of EFM must be configured when the iTN201 is in active mode.

Configuring the interface initiating EFM remote loopback

Initiating EFM remote loopback cannot succeed unless the following operations are performed. Establish the EFM connection. Configure EFM at device in active mode. Enable loopback response.


OAM MGT (802.ah) > OAM Loopback Table.

Step 2 Select a record and then click Init LoopBack.

(Optional) configuring peer OAM event Trap


OAM MGT (802.ah) > OAM Trap Table.


Step 3 A dialog box appears, where you can enable peer OAM event Trap. The following table




OAM Peer Event Trap Enable Enable/Disable peer OAM event Trap.

True False

By default, peer OAM event Trap is disabled.

Raisecom




(Optional) viewing current variable values of peer device

Peer variable cannot be obtained unless EFM connection is established.


OAM MGT (802.ah) > OAM Peer Table.

Step 2 Select a record and then click View to view current variable values of the peer device.

10.2.4 Configuring passive functions of EFM

The passive functions of EFM can be configured regardless of the iTN201 is in active or passive mode.

(Optional) configuring the iTN201 responding to EFM remote loopback

The peer EFM remote loopback will not take effect until the following operations are performed. Remote loopback response is configured on the local device. The peer works in active mode. Loopback is enabled.


OAM MGT (802.ah) > OAM Loopback Table.


Step 3 A dialog box appears, where you can configure the iTN201 responding to/ignoring the EFM

remote loopback. The following table describes items at the dialog box.



Ignore Received OAM Loopback Select a mode for processing the OAM loopback

command.

Ignore: the iTN201 ignores the OAM loopback

command sent by the peer. Process: the iTN201 responds to the OAM

loopback command sent by the peer

By default, the iTN201 ignores the OAM loopback

command sent by the peer.

Raisecom




(Optional) configuring OAM link monitoring and enabling OAM fault indication

OAM link monitoring is used to detect and report link errors in different conditions. When detecting a fault on a link, the iTN201 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 via SNMP Trap. Besides, the local device can directly report events to the NView NNM system via SNMP Trap.


OAM MGT (802.ah) > OAM Event Config Table.


Step 3 A dialog box appears, where you can configure OAM link monitoring and enable OAM fault

indication. The following table describes items at the dialog box.



Lower Error Symbols

Period Window

Configure the monitor window for an error symbol period

event, which ranges from 1 to 60s and is set to 10s by default.

Lower Error Symbols

Period Threshold

Configure the monitor threshold for an error symbol period

event, which ranges from 1 to 65535 and is set to 1 by

default.

Error Symbols Period

Notification Enable

Enable/Disable error symbol period event notification.

True False

By default, error symbol period event notification is enabled.

Error Frames Period

Window

Configure the monitor window for an error frame period

event, which ranges from 1 to 600 and is set to 10 by default.

The unit is set to 100ms.

Error Frames Period

Threshold

Configure the monitor threshold for an error frame period


default.

Error Frames Period

Notify Enable

Enable/Disable error frame period event notification.

True False

By default, error frame period event notification is enabled.

Error Frame Window Configure the monitor window for an error frame event,

which ranges from 1 to 60s and is set to 1s by default.

Error Frame Threshold Configure the monitor threshold for an error frame event,

which ranges from 1 to 65535 and is set to 1 by default.

Raisecom





Error Frame Notify

Enable

Enable/Disable error frame event notification.

True False

By default error frame event notification is enabled.

Error Frame Seconds

Summary Window

Configure the monitor window for an error frame seconds

event, which ranges from 10 to 900s and is set to 60s by

default.

Error Frame Seconds

Summary Threshold

Configure the monitor threshold for an error frame seconds


default.

Error Frame Seconds

Summary Notify Enable

Enable/Disable error frame seconds event notification.

True False

By default, error frame seconds event notification is enabled.

Dying Gasp Enable Enable/Disable Dying Gasp.

True False

By default, Dying Gasp is enabled.

Critical Event Enable Enable/Disable Critical Event.

True False

By default, Critical Event is enabled.

(Optional) configuring local OAM event Trap




Step 3 A dialog box appears, where you can enable local OAM event Trap. The following table




OAM Event Trap Enable Enable/Disable local OAM event Trap.

True False



Raisecom




1. View basic configurations of EFM.


OAM MGT (802.ah) > OAM Table and then select the OAM Table tab. Select a record and

then click View to view basic configurations of EFM on the interface.

2. View configurations on OAM link monitoring and OAM fault indication.


OAM MGT (802.ah) > OAM Event Config Table. Select a record and then click View to

view configurations on OAM link monitoring and OAM fault indication.

3. View OAM statistics.


OAM MGT (802.ah) > OAM Stat. Table. Select a record and then click View to view OAM

statistics or click Chart to view the trend chart of OAM statistics.

4. View configurations on OAM event Trap.


OAM MGT (802.ah) > OAM Trap Table. Select a record and then click View to view

configurations on OAM event Trap.

10.3 Configuring CFM


Scenario

To expand application of Ethernet technologies at a Telecom network, the Ethernet must

ensure the same QoS as the Telecom transport network. CFM solves this problem by

providing overall OAM tools for the Telecom Carrier Ethernet.

CFM can provide following OAM functions:

Fault detection (Continuity Check, CC)

The function is realized by periodically sending Continuity Check Messages (CCMs). One

MEP sends CCM and other MEPs in the same service instance can verify the RMEP status

when receiving this packet.

Fault acknowledgement (LoopBack, LB)

This function is used to verify the connectivity between two MPs through the source MEP

sending LoopBack Message (LBM) and the destination MP sending LoopBack Reply (LBR).

The source MEP sends a LBM to a MP who needs to acknowledge a fault. When receiving the

LBM, the MP sends a LBR to the source MEP. If the source MEP receives this LBR, it is

believed that the route is reachable. Otherwise, a connectivity fault occurs.

Fault location (LinkTrace, LT)

The source MEP sends LinkTrace Message (LTM) to the destination MP and all MPs on the

LTM transmission route will send a LinkTrace Reply (LTR) to the source MEP. By recording

valid LTR and LTM, this function can be used to locate faults.

Alarm Indication Signal (AIS)

Raisecom




This function is used to inhibit alarms when a fault is detected at the server layer. When

detecting a fault, the MEP (including the server MEP) sends an AIS frame to the client MD.

By transmitting ETH-AIS frames, the device can inhibit or stop an alarm on MEP (or server

MEP).

When receiving an AIS frame, the MEP must inhibit alarms for all peer MEPs regardless of

connectivity, because this frame does not include information about MEPs that are at the same

level with the failed MEP. With AIS, the device can inhibit the alarm information at client

level when the server layer (sub-layer) fails. Therefore, the network is easy for maintenance

and management.

In general, CFM is an end-to-end OAM technology at the server layer. It helps reduce

operation and maintenance cost. In addition, it improves the competitiveness of service

providers.

Prerequisite

Before configuring CFM, you should finish following operations:

Connect interfaces and configure physical parameters of the interfaces. Make the

physical layer Up.

Create a VLAN.

Add interfaces to the VLAN.

10.3.2 Enabling CFM

CFM fault detection and CFM fault location functions cannot take effect until the CFM is enabled.

Enabling CFM globally

Step 1 From the Action List of the iTN201 EMS, choose SNMP Management > CFM

Management > Global Config.

Step 2 Select the Ethernet Global Info tab, where you can enable CFM. By default, CFM is disabled.


Enabling CFM on interfaces


Management > Global Config and then select the Y.1731 Port CFM Config tab.

Step 2 Select a record and then click Modify. A dialog box appears, where you can enable CFM on

the interface. By default, CFM is disabled on the interface.


Raisecom




10.3.3 Configuring basic functions of CFM

Creating MDs

Levels of different MDs must be different. Otherwise the MD is not successfully configured.


Management > Ethernet CFM.

Step 2 Click from the tool bar of the iTN201 EMS. A dialog box appears, where you can

configure a MD. The following table describes items at the dialog box.

Step 3 After configurations, click OK.


Protocol Type Select a protocol.

Y.1731: a Y.1731-style MD and all MAs and CCMs in the MD

are in Y.1731 style. 802.1ag: an 802.1ag -style MD and all MAs and CCMs in the MD

are in 802.1ag style.

MD Level Select a MD level, which ranges from 0 to 7.

MD Name Configure the ME name. Up to 16 characters are available.

This parameter is available only when the Protocol Type is set to

802.1ag.

The MD name must be unique in global. Otherwise the MD is configured unsuccessfully.

Creating service instances and VLAN mapping



Step 2 Select a created MD, right-click the blank area at the Ethernet CFM area, and then choose

Add from the right-click menu.

Step 3 A dialog box appears, where you can create a service instance and VLAN mapping. The




MA Name Configure the name of the service instance. Up to 13 characters are

available.

Raisecom





S-VLAN Configure the VLAN to which the service instance is mapped. It

ranges from 1 to 4094. All MEPs in the service instance receive and

send packets through this VLAN.

The iTN201 EMS supports mapping the service instance to a single VLAN (primary VLAN) only.

Creating MEPs based on service instances

When configuring a MEP based on a service instance, you must ensure that the service instance is mapped to a VLAN.



Step 2 Select a created MA, select the MEP tab, right-click the blank area at the MEP tab, and then

choose Add from the right-click menu.

Step 3 A dialog box appears, where you can create a MEP based on the service instance. The




MEP ID Configure the MEP ID, which ranges from 1 to 8191.

Port Click and select an interface.

MEP Direction Select a direction of the MEP.

Up: the MEP detects the fault in uplink direction. Down: the MEP detects the fault in downlink direction.

Creating static RMEPs



Raisecom




Step 2 Select a created MA, select the Static Remote MEP tab, right-click the blank area at the Static

Remote MEP tab, and then choose Add from the right-click menu.

Step 3 A dialog box appears, where you can create a static RMEP. The following table describes




Remote MEP ID Configure the RMEP ID, which ranges from 1 to 8191.


10.3.4 Configuring fault detection

Configuring aging time of RMEP and hold time of error CCMs



Step 2 Select the Ethernet Global Info tab, where you can configure the aging time of RMEP and

hold time of error CCMs. The following table describes items at the tab.



CCM Database

Archive Holdtime

Configure the hold time of CCMs. It ranges from 1 to 65535min and

is set to 100min by default.

Rmep Age Time Configure the aging time of RMEP. It ranges from 1 to 65535min

and is set to 100min by default.

Configuring interval for service instance sending CCMs, CVLAN, and OAM priority



Step 2 Right-click a record and then choose Modify from the right-click menu.

Step 3 A dialog box appears, where you can configure the interface for the service instance sending

CCMs, CVLAN, and OAM priority.


Raisecom





CCM Send

Period

Select an interval for the service instance sending CCMs.

3.3ms 10ms 100ms 1s 10s 1min 10min

By default, it is set to 1s. In section 10.3.3 Configuring basic

functions of CFM, if the MEP Direction is set to UP, you cannot set

the CCM Send Period to 3.3ms, 10ms, or 100ms.

PDU Priority Select an OAM priority, which ranges from 0 to 7.

After you configure the OAM priority, CCMs, LBMs, LTMs, and

DDMs sent by all MEPs in the service instance will use the priority.

By default, the OAM priority is set to 7.

CE-VLAN Configure the CE-VLAN, which ranges from 1 to 4097. It is an

optional parameter.

By default, the CFM OAM PDU does not carry the C-TAG. After you

configure the CE-VLAN, CCMs, LBMs, LTMs, and DDMs sent by

all MEPs in the service instance will carry double TAGs, where the C-

TAG is configured through this operation.

Enabling MEPs to send CCMs



Step 2 Right-click a record about the local MEP and then choose CCM Enable from the right-click

menu.

Configuring static RMEPs



Step 2 Select a created MA, select the Static Remote MEP tab, right-click the blank area at the Static

Remote MEP tab, and then choose Add from the right-click menu.

Step 3 A dialog box appears, where you can create a static RMEP. The following table describes





Remote MAC Address Configure the static remote MAC address, which is in colon


Raisecom






Configuring REMP learning dynamic import

Before configuring RMEP learning dynamic import, there should be a dynamically-

discovered MEP. After REMP learning dynamic import is enabled, when receiving a CCM,

the service instance will automatically translate the dynamically-learned REMP into the

statically-configured RMEP. By default, REMP learning dynamic import is disabled.



Step 2 Right-click a record and then choose Import Dynamic Remote MEP from the right-click

menu.

Configuring CC Check of REMP

After CC Check is enabled, when receiving a CCM, the service instance will check whether

the ID value of the dynamically-learned REMP is identical to the one of statically configured

RMEP. If it is inconsistent, the CCM is taken as an error one. By default, CC Check is

disabled.



Step 2 Right-click a record and then choose from CCM Check Enable the right-click menu.

10.3.5 Configuring fault acknowledgement

Before performing this operation, 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 the specified destination MEP ID and the MAC address of destination is not found based on the MEP ID;

Ping operation will fail if other users are using the specified source MEP to perform Ping operation.



Step 2 Right-click a record about the local MEP and then choose LB from the right-click menu.

Step 3 A dialog box appears, where you can configure the fault acknowledgement information. The


Raisecom




Step 4 After configurations, click Save and Start and then you can view results at the Operation

Result area.


LB Type Select a fault acknowledgement type.

MEP Unicast MAC Multicast MAC


This parameter is available when the LB Type is set to

MEP.

Remote MAC Address Configure the remote MAC address, which is in colon


This parameter is available when the LB Type is set to

MAC.

TLV Type Select the TLV carried by the packet.

Data TLV Test TLV: prbs Test TLV: prbs_crc Test TLV: null Test TLV: null_crc

Wherein, the PRBS refers to Pseudo Random Binary

Sequence (PRBS).

TLV Length (Byte) Configure the size of request packet to be sent. It ranges

from 1 to 1484 bytes.

Message Nums Configure the number of packets, which ranges from 1 to

1024.

Timeout(s) Configure the timeout. It ranges from 1 to 60s and is set to

5s by default.

10.3.6 Configuring fault location


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 the specified destination MEP ID and the MAC address of destination is not found based on the 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.

Raisecom




Traceroute operation will fail if other users are using the specified source MEP to perform Traceroute operation.

Configuring Traceroute database



Step 2 Select the Link Trace DataBase Config tab, where you can configure the Traceroute database.

The following table describes items at the tab.



Database Enable Enable/Disable Traceroute database.

True False

By default Traceroute database is disabled.

Holdtime Configure the hold time of data in the Traceroute database. It

ranges from 1 to 65535min and is set to 100min by default.

This parameter is available only when the Traceroute database is enabled.

Storage Entry Count Configure the Traceroute database size. It ranges from 1 to 512


This parameter is available only when the Traceroute database is enabled.

Configuring fault location



Step 2 Right-click a record about the local MEP and then choose LT from the right-click menu.

Step 3 A dialog box appears, where you can configure fault location. The following table describes



Result area.


LT Type Select a fault location type.

MEP MAC

Raisecom






This parameter is available when the LT Type is set to MEP.

Remote MAC

Address

Configure the remote MAC address, which is in colon hexadecimal

notation.

This parameter is available when the LT Type is set to MAC.

TTL Configure the TTL value, which ranges from 1 to 255 and is set to 64

by default.

10.3.7 Configuring AIS

Configuring AIS on server-layer devices



Step 2 Right-click a record about a service instance and then choose Modify from the right-click

menu.

Step 3 A dialog box appears, where you can configure AIS. The following table describes items at

the dialog box.



AIS Enable Enable/Disable AIS.

Enable Disable

By default, AIS is disabled.

AIS Send Period Select an AIS delivery period.

1s 60s

By default, the AIS delivery period is set to 1s.

AIS Admin Level Configure the level of customer-level MD to which AIS is sent.

It ranges from 0 to 7.

Configuring AIS on customer-layer devices



Step 2 Right-click a record about a local MEP and then choose Alarm Suppression Enable from the

right-click menu to enable alarm inhibition. By default, alarm inhibition is enabled.

Raisecom






1. View CFM global configurations.

From the Action List of the iTN201 EMS, choose SNMP Management > CFM

Management > Global Config and then select the Ethernet Global Info tab to view CFM

global configurations.

2. View MD configurations.


Management > Ethernet CFM to view MD configurations at the Ethernet CFM area.

3. View configurations on service instances.


Management > Ethernet CFM. Right-click a record about a service instance and then

choose Config from the right-click menu to view configurations on the service instance.

4. View configurations on local MEPs.


Management > Ethernet CFM and then select the MEP tab to view configurations on local

MEPs.

5. View configurations on static RMEPs.


Management > Ethernet CFM and then select the Static Remote MEP tab to view

configurations on static RMEPs.

10.4 Configuring MPLS-TP CFM


Scenario

To expand application of MPLS-TP technologies at a Telecom network, the MPLS-TP

network must ensure the same QoS as the Telecom transport network. CFM solves this

problem by providing overall OAM tools for the MPLS-TP network.

CFM can provide following OAM functions based on the MPLS-TP network:

Fault detection (Continuity Check, CC)

Fault acknowledgement (LoopBack, LB)

Fault location (LinkTrace, LT)

Alarm Indication Signal (AIS)

Client Signal Failure (Client Signal Fail, CSF)

Ethernet lock signal (Lock, LCK)

Delay and jitter detection (Packet Delay and Packet Delay Variation Measurements, DM)

Frame loss detection (Frame Loss Measurements, LM)

Raisecom




Principles of MPLS-TP OAM are similar to the ones of Ethernet OAM. They are different in

aspects of the way to carry packets.

To provide users with qualified network services, the SP signs a SLA with users. To carry out

SLA effectively, the SP 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 iTN devices), SLA configures and

schedules SLA operations on a detection point. Therefore, network performance between this

2 detection points can be detected.

SLA makes a statistics on round-trip packet loss ratio, round-trip/unidirectional (SD/DS)

delay, jitter, jitter variance, jitter distribution, throughput, and LM packet loss 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.

Configurations and configuration methods for Section CFM, Tunnel CFM, PW CFM, multi-section CFM, and Transit LSP CFM are similar. In this guide, only differences when creating MA are described. The others are described by taking creating Section CFM for an example. To create Section CFM, choose SNMP Management > CFM Management > Section CFM from the Action List of the iTN201 EMS.

Prerequisite

Before configuring MPLS-TP CFM, you should finish following operations:

Connect interfaces and configure physical parameters of the interfaces. Make the

physical layer Up.

Configure basic functions of MPLS.

Deploy CFM between devices that need to be detected.

10.4.2 Enabling MPLS-TP CFM

CFM fault detection and CFM fault location functions cannot take effect until the CFM is enabled.

Enabling MPLS-TP CFM



Step 2 Select the MPLS-TP CFM Global Info tab, where you can enable MPLS-TP CFM. By default,

MPLS-TP CFM is disabled.


Raisecom




Configuring ICC



Step 2 Select the ICC Config tab, where you can configure the ICC. The following table describes

items at the tab.



ICC Code Configure the ITU-T Carrier Code (ICC) carried in the LBR packet.

Each ICC corresponds to a network vendor/ISP. It ranges from 0 to 6

characters.

By default, no ICC is configured.

ICC ID Configure the ICC ID. It ranges from 1 to 4294967295.

By default, no ICC is configured.

10.4.3 Configuring MPLS-TP CFM

Before enabling CFM packet delivery, you need to configure the relationship between the service instance and L2VC.

Creating MDs

Maintenance Domain (MD), also called Maintenance Entity Group (MEG), is a network that

runs CFM. It defines network range of OAM management. MD has a level property, with 8

levels (level 0 to level 7). The bigger the number is, the higher the level is and the larger the

MD range is. Protocol packets in a lower-level MD will be discarded after entering a higher-

level MD. If no Maintenance association End Point (MEP) but a Maintenance association

Intermediate Point (MIP) is in a high-level MD, the protocol can traverse the higher-level MD.

However, packets in a higher-level MD can traverse lower-level MDs. In the same VLAN

range, different MDs can be adjacent, embedded, but not crossed.


Management > Section CFM.

Step 2 Click and a dialog box appears, where you can configure a MD. The following table




Protocol Type Select a protocol. At present, only Y.1731 protocol is available.

In a Y.1731-style MD, all MAs and CCMs in the MD are in Y.1731

style.

Raisecom





MD Level Select a MD level, which ranges from 0 to 7.

Configuring Section MAs

MA narrows the CFM detection scale to a much smaller one. In addition, fault detections on

multiple service instances in a MD are independent.

One MD can be divided into one or multiple MAs (service instances). One MA corresponds to

one service and is mapped to a group of VLANs. VLANs of different MAs cannot cross.

Though a MA can be mapped to multiple VLANs, one MA can only use a VLAN for sending

or receiving OAM packets. This VLAN is the master VLAN of the MA. The VLAN with the

smallest ID is used as the master VLAN.

In the QinQ networking environment, you need to configure the CE-VLAN (CVLAN) of the

MA. In this case, CCM, LTM, and LBM sent by all MEPs in the MA carry double Tags,

where the CE-VLAN Tag is configured through this operation.



Step 2 Select a created MD level, right-click the blank area at the Section CFM area, and then choose


Step 3 A dialog box appears, where you can configure the MA parameters. The following table



Raisecom





MA Name Configure the MA name, which ranges from 1 to 12 characters.

Dest NE Click and then select a destination NE.

Dest NE

MAC

Configure the MAC address of the destination NE, which is in colon


Remark Configure the remark of the MA, which ranges from 0 to 512 characters.

Configuring Tunnel MAs


Management > Tunnel CFM.

Step 2 Select a created MD level, right-click the blank area at the Tunnel CFM area, and then choose







Tunnel Direction Configure the Tunnel direction.

One-way Two-way


Associated

Ingress Tunnel Click to select a bidirectional/unidirectional associated LSP.

Associated

Egress Tunnel

Click to select a unidirectional associated LSP.

This parameter is available only when the Tunnel Direction is set to

One-way.

Remark Configure the remark of the MA, which ranges from 0 to 512

characters.

Configuring PW MAs


Management > PW CFM.

Step 2 Select a created MD level, right-click the blank area at the PW CFM area, and then choose




Raisecom







Associated PW Configure the associated PW. Click and then select a created

PW.

PW ID Configure the PW ID.

Peer Address Type Display the peer address type.

Peer Address Configure the peer address.


characters.

Configuring multi-section PW MAs


Management > MSPW CFM.

Step 2 Select a created MD level, right-click the blank area at the MSPW CFM area, and then choose






MA Name Configure the MA name, which ranges from 1 to 12

characters.

Associate MS PW Click and then select the associated multi-section

PW.

Forward PW ID Configure the forward PW ID.

Forward Dest Address Type Display the forward destination address type.

Forward Dest Address Configure the forward destination address.

Backward PW ID Configure the backward PW ID.

Backward Dest Address

Type

Display the backward destination address type.

Backward Dest Address Configure the backward destination address.

Remark Configure the remark of the MA, which ranges from 0 to

512 characters.

Raisecom




Click at the Associate MS PW text box and then select a created multi-section PW. The parameters of the multi-section PW automatically keep consistent with the selected one.

If you do not select the created multi-section PW, you can ignore the Associate MS PW and configure other parameters.

Configuring Tunnel Transit MAs


Management > Transit LSP CFM.

Step 2 Select a created MD level, right-click the blank area at the Transit LSP CFM area, and then







Tunnel Direction Configure the Tunnel direction.

One-way Two-way


Associated Forward

Tunnel Click and then select an associated forward Tunnel.

Associated Backward

Tunnel Click and then select an associated backward Tunnel.

This parameter is available only when the Tunnel Direction is

set to One-way.

Dest Address Type Configure the destination address type. This parameter is

available only when the Tunnel Direction is set to Two-way.

Dest Address Configure the destination address. This parameter is available

only when the Tunnel Direction is set to Two-way.

TTL Configure the TTL, which ranges from 1 to 255.



characters.

Configuring local MEPs


Management > Transit LSP CFM.

Raisecom






Step 3 A dialog box appears, where you can configure a local MEP. The following table describes




MEP ID Configure the local MEP ID, which ranges from 1 to 8191.

CCM Send Enable Enable/Disable CCM delivery.

Enable: the interface can receive and send CCMs directly. Disable: the interface cannot receive or send CCM directly.

By default, CCM delivery is disabled.

Adding RMEPs manually



Step 2 Select a created MD, right-click the blank area at the Section CFM area, and then choose Add


Step 3 A dialog box appears, where you can create a RMEP. The following table describes items at

the dialog box.




Learning RMEPs dynamically

RMEPs dynamically learned by the iTN201 can be aged. During the aging time, if a RMEP is

not learned again, it will be deleted.

The iTN201 can learn RMEPs automatically. After dynamic learning REMP is enabled, the

iTN201 automatically import the dynamically learned RMEP to the MA based on the CFM

packet received by the RMEP and then translate the dynamic RMEP to static RMEP.

Step 1 Configure the aging time of dynamically-learned RMEPs.

1. From the Action List of the iTN201 EMS, choose SNMP Management > CFM


2. Select the MPLS-TP CFM Global Info tab, where you can configure the aging time of

dynamically-learned RMEPs.


Raisecom





Rmep Age Time Configure the aging time of dynamically-learned RMEPs. It ranges

from 1 to 65535min and is set to 100min by default.

Step 2 View dynamically-learned RMEPs.

1. From the Action List of the iTN201 EMS, choose SNMP Management > CFM


2. Select a created MD. Select a record about a created MA and then choose Import

Dynamic Remote MEP from the right-click menu to translate dynamically-learned

RMEPs to static RMEPs automatically.

10.4.4 Configuring MPLS-TP fault detection

CFM fault detection is used to perform periodical fault detection on MEPs in MAs based on

CCM. If no CCM is received by a MEP during 3.5 CCM intervals, it is believed that the link

fails. Then a fault Trap will be sent according to configured alarm priority and a record about

the CFM error is saved.

For MAs, you need to configure the CCM delivery period, CCM priority, and hold time

of error information in the CCM database. If you need to use CCMs to verify whether

dynamically-learned MEP IDs are consistent with static MEP IDs, you should configure

CCM check.

For local MEPs, after configuring CCM delivery and CFM fault detection, you can

configure alarms to be reported to the NView NNM system through Trap.



Step 2 Select the MPLS-TP CFM Global Info tab, where you can configure the hold time of error

information in the CCM database.



CCM Database Archive

Holdtime

Configure the hold time of error information in the CCM

database. The error information will be deleted once the hold

time expires. It ranges from 1 to 65535min and is set to

100min by default.

Configuring MA fault detection parameters





Step 3 A dialog box appears, where you can configure the MA fault detection parameters. The


Raisecom







CCM Send Period Select an interval for the MA sending CCMs.

3.3ms 10ms 100ms 1s 10s 1min 10min

This parameter is read-only when CCM delivery is enabled.

By default, it is set to 1s.

PDU Priority Select an OAM priority, which ranges from 0 to 7.

After you configure the OAM priority, CCMs, LBMs, LTMs,

and DDMs sent by all MEPs in the service instance will use the

priority.

By default, the OAM priority is set to 7.

Enabling remote CCM check

After remote CCM check is enabled, when receiving a CCM, the iTN201 will check whether

the dynamically-learned RMEP ID is consistent with the static RMEP ID. If they are

inconsistent, the CCM is regarded as an error one.



Step 2 Select a created MD level. Right-click a created MA at the Section CFM area, and then

choose CCM Check Enable from the right-click menu to enable CCM check.

Step 3 (Optional) select a created MD level. Right-click a created MA at the Section CFM area, and

then choose CCM Check Disable from the right-click menu to disable CCM check.

Configuring fault detection of local MEPs



Step 2 Select a created MD level; right-click a created MA at the Section CFM area; select the MEP

tab; right-click the blank area at the tab and then choose Add from the right-click menu.



MEP ID Configure the local MEP ID, which ranges from 1 to 8191.

Raisecom





CCM Send Enable Enable/Disable CCM delivery.

Enable Disable

By default, CCM delivery is disabled.

10.4.5 Configuring MPLS-TP fault acknowledgement


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 other users are using the specified source MEP to perform Ping operation.

CFM fault acknowledgement is used to verity connectivity between 2 MEPs in a MA. This

feature is similar to Ping. In actual, it is Layer 2 Ping. Layer 2 Ping (also called as 802.1ag

MAC Ping) is similar to Layer 3 Ping. It detects the route between source and destination

ends by sending request packets and receiving respond packets. It can be used for end-to-end

connectivity fault acknowledgement.



Step 2 Right-click a record about the local MEP and then choose LB from the right-click menu.

Step 3 A dialog box appears, where you can configure the fault acknowledgement information. The



Result area.


LB Type Select a LB type.

MEP MIP Direction

By default, it is set to MEP.


This parameter is available when the LB Type is set to MEP.

TTL Configure the TTL value, which ranges from 1 to 255 and is set

to 64 by default.

Raisecom





Message Nums Configure the number of packets, which ranges from 1 to 1024.


TLV Type Select the TLV carried by the packet.

Data TLV Test TLV: prbs Test TLV: prbs_crc Test TLV: null Test TLV: null_crc

TLV Length (Byte) Configure the size of request packet to be sent. It ranges from 1

to 1484 bytes. By default, it is set to 1 byte.

Timeout(s) Configure the timeout. It ranges from 1 to 60s and is set to 5s by

default.

10.4.6 Configuring MPLS-TP fault location


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 other users are using the specified source MEP to perform Traceroute operation.

Configuring Traceroute database



Step 2 Select the Link Trace DataBase Config tab, where you can configure the Traceroute database.




Database Enable Enable/Disable Traceroute database.

True False

By default Traceroute database is disabled.

Holdtime Configure the hold time of data in the Traceroute database. It

ranges from 1 to 65535min and is set to 100min by default.

Raisecom





Storage Entry Count Configure the Traceroute database size. It ranges from 1 to 512


Configuring fault location



Step 2 Right-click a record about the local MEP and then choose LT from the right-click menu.

Step 3 A dialog box appears, where you can configure fault location. The following table describes



Result area.


LT Type Select a LT type.

MEP MIP TTL

By default, it is set to MEP.

LT Mode Select a LET mode.

Node Interface

By default, no LT mode is configured.


This parameter is available when the LT Type is set to MEP.

Node ID Configure the node ID, which ranges from 1 to 4294967295.

This parameter is available when the LT Type is set to MIP.

ICC Code Configure the ICC, which ranges from 1 to 6.

This parameter is available when the LT Type is set to MIP.

TTL Configure the TTL value, which ranges from 1 to 255 and is set to 64

by default.

Timeout(s) Configure the timeout. It ranges from 1 to 60s and is set to 5s by

default.

10.4.7 Configuring MPLS-TP AIS



Raisecom




Step 2 Select a created ME level. Right-click the blank area at the Section CFM area and then choose


Step 3 A dialog box appears and then click Advanced Config.

Step 4 A dialog box appears, where you can configure MPLS-TP AIS. The following table describes


Step 5 After configurations, click OK to return to the Add MA tab



AIS Enable Enable/Disable AIS.

Enable Disable

By default, AIS is disabled.

AIS Send Period Select an AIS delivery period.

1s 60s

By default, the AIS delivery period is set to 1s.

AIS Admin Level Configure the level of customer-level MD to which AIS is sent.

It ranges from 0 to 7.

10.4.8 Configuring MPLS-TP LCK



Step 2 Select a created ME level. Right-click the blank area at the PW CFM area and then choose


Step 3 A dialog box appears and then click Advanced Config.

Step 4 A dialog box appears. Select the CSF tab, where you can configure MPLS-TP LCK. The


Step 5 After configurations, click OK to return to the Add MA tab



Receive CSF Trap Enable Enable/Disable Trap of the CSF module.

Enable Disable

By default, Trap of CSF module is disabled.

Raisecom





CSF Send Period Select a CSF delivery period.

1s 60s

By default, the CSF delivery period is set to 1s.

10.5 Configuring SLA


Scenario

To provide users with qualified network services, the SP signs a SLA with users. To carry out

SLA effectively, the SP 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 iTN devices), SLA configures and

schedules SLA operations on a detection point. Therefore, network performance between this

2 detection points can be detected.

SLA makes a statistics on round-trip packet loss ratio, round-trip/unidirectional (SD/DS)

delay, jitter, jitter variance, jitter distribution, throughput, and LM packet loss 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.

Prerequisite When you configure Layer 2 test operations, 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 test operations (icmp-echo and icmp-jitter), Layer 3 Ping

operation succeeds between local and remote devices.

Enable PerfMonitor at the NView NNM Control.

Deploy CFM between devices that need to be detected.

10.5.2 Configuring Ethernet SLA operations (delay/jitter/packet loss ratio)

Creating threshold templates


SLA Config > Ethernet SLA.

Step 2 Choose Edit > Add from the menu bar of the iTN201 EMS.

Raisecom




Step 3 A dialog box appears. Select the metric group (delay/jitter/packet loss rate) and then click

Threshold configuration.

Step 4 Click Add and a dialog box appears, where you can configure the threshold template. The


Step 5 After configurations, click Confirm.

Table 10-1 Parameters of metric groups


Base Information

Template Name Configure the threshold template name.

Template

Description

Configure descriptions about the threshold template.

Delay (µs)

SD Configure the source-to destination delay threshold. It ranges from 0

to 999999999.

DS Configure the destination-to source delay threshold. It ranges from 0

to 999999999.

Two-way Configure the bidirectional delay threshold. It ranges from 0 to

999999999.

Jitter (µs)

SD Configure the source-to destination jitter threshold. It ranges from 0

to 999999999.

DS Configure the destination-to source jitter threshold. It ranges from 0

to 999999999.

Two-way Configure the bidirectional jitter threshold. It ranges from 0 to

999999999.

Packet loss rate (thousandth)

SD Configure the source-to destination packet loss ratio threshold. It


DS Configure the destination-to source packet loss ratio threshold. It


Configuring properties of metric groups




Step 3 A dialog box appears. Select the metric group (delay/jitter/packet loss rate) and then click

Modify.

Raisecom




Step 4 A dialog box appears, where you can configure properties of metric groups. The following



Table 10-2 Parameters of threshold templates


Delay

Type of test

packets

Select a detection packet.

DM: Delay measurement packet LB: Loopback measurement packet

Jitter

Type of test

packets

Select a detection packet.

DM: Delay measurement packet

Probe Interval

(ms)

Configure the interval for sending DM detection packet. It ranges

from 20 to 60000ms. By default, it is set to 1000ms.

Number of

probes packets

Configure the number of Tx DM detection packets. It ranges from 1

to 20. By default, it is set to 5.

Detection period = Detection times × detection interval + 5s (timeout).

Packet loss rate

Type of test

packets

LM: Loss measurement packet

Probe Interval

(ms)

Configure the interval for sending LM detection packet. It ranges

from 20 to 60000ms. By default, it is set to 1000ms.

Number of

probes packets

Configure the number of Tx LM detection packets. It ranges from 1 to


Detection period = Detection times × detection interval + 5s (timeout).

Creating SLA operations




Step 3 A dialog box appears, where you can configure a SLA operation. The following table



Raisecom





Base Info

Operation name Configure the SLA operation name.

MD level Select a MD level, which ranges from 0 to 7.

Schedule

survival time

Select the survival time of the scheduling.

1 day 7 day 30 day Custom

Custom survival

time (day)

Customize the scheduling survival time which ranges from 1 to 100

days.

This parameter is available only when the Schedule survival time is set to Custom.

Schedule cycle Select a scheduling period.

5 minutes 10 minutes 15 minutes 30 minutes 60 minutes


CFM VLAN ID The server VLAN ID is displayed after you click and selecting

a MA.

CUSTOMER

VLAN ID

Configure the CVALN ID, which ranges from 1 to 4094.


Cfm Operation

COS

Configure the CoS value of the CFM operation, which ranges from 0

to 7.

MAC

ADDRESS

Configure the destination MAC address, which is in colon


Metric

Delay After selecting the Delay metric, click Threshold configuration to

select a threshold template or clock Modify to configure the

properties.

Jitter After selecting the Jitter metric, click Threshold configuration to

select a threshold template or clock Modify to configure the

properties.

Packet loss rate After selecting the packet loss rate metric, click Threshold

configuration to select a threshold template or clock Modify to

configure the properties.

Raisecom





Dispatch Configure whether scheduling the operation once it is created.

Checked: schedule the operation once it is created. Unchecked: manually schedule the operation after it is created.

10.5.3 Configuring basic information of MPLS-TP SLA operations

Before clicking Threshold configuration, you need to enable the PerfMonitor. For details, see section 17.2 Performance monitoring service. Before configuring a SLA operation, you need to configure related CFM functions. For example, before configuring Section SLA, you need to configure Section CFM.

Configuring Section SLA


SLA Config > SECTION SLA.

Step 2 Click from the tool bar of the iTN201 EMS.

Step 3 A dialog box appears. Select one or multiple metrics (delay/jitter/packet loss rate) and then

click Modify.

Table 10-3 Parameters of metric groups (2)


Delay

Type of test packets Select a detection packet.


Jitter



Probe interval (ms) Configure the interval for sending DM detection packet. It

ranges from 20 to 60000ms. By default, it is set to 1000ms.

Number of probes

packets

Configure the number of Tx DM detection packets. It ranges

from 1 to 20. By default, it is set to 5.

Packet loss rate


LM: Loss measurement packet

Probe interval (ms) Configure the interval for sending LM detection packet. It

ranges from 20 to 60000ms. By default, it is set to 1000ms.

Number of probes

packets

Configure the number of Tx LM detection packets. It ranges


Raisecom




Step 4 After configurations, click Confirm to return to the Add dialog box.

Step 5 Click Threshold configuration and a dialog box appears.

Step 6 Click Add to add a new threshold template.

Table 10-4 Parameters of the threshold template


Base Information

Template Name Configure the threshold template name.

Template

Description

Configure descriptions about the threshold template.

Delay (µs)

SD Configure the source-to destination delay threshold. It ranges from 0

to 999999999.

DS Configure the destination-to source delay threshold. It ranges from 0

to 999999999.

Two-way Configure the bidirectional delay threshold. It ranges from 0 to

999999999.

Jitter (µs)

SD Configure the source-to destination jitter threshold. It ranges from 0

to 999999999.

DS Configure the destination-to source jitter threshold. It ranges from 0

to 999999999.

Two-way Configure the bidirectional jitter threshold. It ranges from 0 to

999999999.

Packet loss rate (thousandth)

SD Configure the source-to destination packet loss ratio threshold. It


DS Configure the destination-to source packet loss ratio threshold. It


Step 7 After configurations, click Confirm to return to the Select threshold template dialog box.

Step 8 Select a threshold template and then click Confirm to return to the Add dialog box, where

you can configure Section SLA parameters. The following table describes items at the dialog

box.



Base Info

Raisecom






MD level Select a MD level, which ranges from 0 to 7. By default, it is set to

0.

Schedule survival

time



By default, it is set to 1 day.




Section Port Name Click and then select a section-layer interface.

TC of Label Configure the label Traffic Class (TC), which ranges from 0 to 7.

Compare the configured TC and service priority and then perform

SLA network performance test operation if they are identical.

Configuring Tunnel SLA


SLA Config > TUNNEL SLA.



click Modify. A dialog box appears. The following table describes items at the dialog box.



Step 6 Click Add to add a new threshold template. Table 10-4 lists items at the dialog box.



you can configure Tunnel SLA parameters.



Base Info

Raisecom







0.

Schedule survival

time







Select Tunnel Click and select an associated Tunnel.




INGRESS LSP Configure the ingress LSP name.

EGRESS LSP Configure the egress LSP name.

Configuring PW SLA


SLA Config > PW SLA.



click Modify. A dialog box appears. The following table describes items at the dialog box.



Step 6 Click Add to add a new threshold template. Table 10-2 lists items at the dialog box.



you can configure PW SLA parameters.


Raisecom





Base Info



0.

Schedule survival

time




Custom survival

time (day)

Customize the scheduling survival time which ranges from 1 to 100

days.

This parameter is available only when the Schedule survival time is

set to Custom.




PW Friendly

Name Click and select a PW name.




Static VC ID Configure the static VC ID.

REMOTE IP

TYPE IPV4

Configure the IP address type of the remote device.

Unknown IP v4 IP v6 IP v4Z IP v6Z DNS

PEER IP

ADDRESS

Configure the IP address of the remote device, which is in dotted

decimal notation.

INGRESS LSP Configure the ingress LSP name.

EGRESS LSP Configure the egress LSP name.

Raisecom




10.5.4 Configuring SLA scheduling information

Steps for configuring Ethernet SLA, Section SLA, Tunnel SLA, and PW SLA are similar. In this guide, configuration steps for Ethernet SLA are described for an example.

Configuring Section SLA scheduling information



Step 2 Select a record and then click to enable SLA scheduling.

Step 3 (Optional) select a record where SLA scheduling is enabled and then click to disable

SLA scheduling.

Generating SLA report



Step 2 Right-click a record and then choose Report from the right-click menu.

Step 3 Click Query Result to query SLA report information. The following table describes items at

the dialog box.

Step 4 After configurations, click Save As PDF.


Basic Information

Report Name Configure the report name.

Customer Name Configure the customer name.

Business Name Configure the service name.

Operators Configure the Carrier information.

Maintainers Configure the information about the maintenance person.

Telephone Configure the phone number of the maintenance person.

Remark Configure remarks.

Measurement Index

Delay Configure whether the report includes the delay metric.

Jitter Configure whether the report includes the jitter metric.

Packet loss rate Configure whether the report includes the packet loss rate metric.

Raisecom





Start time Configure the time to begin generating the report. Select the begin

time and then click OK.

End time Configure the time to finish generating the report. Select the end

time and then click OK.

Measurement

period

Display the metric measurement period. By default, it is set to 5min.

Contain chart Configure whether the PDF file includes the chart about the delay,

jitter, and packet loss rate metrics.

Measurement Index

Data Click Results to display the query results of measurement metrics in

a data form.

Chart Click Results to display the query results of measurement metrics in

a chart form.

By default, the SLA report is saved in the client file. If the NView NNM system is installed in Disk C, the SLA report will be saved in C:\NMS\PLATFORM\NNM5\client.

Viewing SLA performance statistics



Step 2 Right-click a record and then choose Statistics from the right-click menu.

Step 3 Select performance metrics to be viewed and then click Query.

Icon Description

Metric group: includes one or more

metrics. All metrics in it can be

checked/unchecked when you

check/uncheck the metric group.

Collection metric

Save the current performance graph

to the local in a format of .png/.gif.

By default, it is saved in a .png

format.

Print the current performance graph.

Display the collection estimation

results in a line chart.

Raisecom




Icon Description


results in an area chart.


results in a bar chart.

Configure the time ranges of real-

time performance.



Steps for viewing Ethernet CFM, Section CFM, Tunnel CFM, PW CFM, multi-section PW

CFM, and Transit LSP CFM are similar. In this guide, only steps for viewing Section CFM

are described.

Viewing SLA operation configurations


SLA Config > Ethernet SLA to view configurations on SLA operations.

Viewing Section CFM configurations

1. View global MPLS-TP OAM configurations.


Management > Global Config. Select the MPLS-TP CFM Global Info tab to view global

MPLS-TP OAM configurations.

2. View ICC configurations.


Management > Global Config. Select the ICC Config tab to view ICC configurations.

3. View MA configurations.


SLA Config > SECTION SLA. From the Action List of the iTN201 EMS, choose SNMP

Management > CFM Management > Section CFM. Select a created MD level to view MA

configurations.

4. View local MEP configurations.



Management > CFM Management > Section CFM. Select a created MD level. Select a MA

and then select the MEP tab to view configurations on local MEPs.

5. View static RMEP configurations.



Management > CFM Management > Section CFM. Select a created MD level. Select a MA

and then select the Static Remote MEP tab to view configurations on static RMEPs.

Raisecom




6. View CCM fault, AIS, LCK, AIS source, LCK source, and CSF packet statistics.



Management > CFM Management > Section CFM. Select a created MD level. Right-click

a MA and then choose Statistics from the right-click menu to view CCM fault, AIS, LCK,

AIS source, LCK source, and CSF packet statistics.

7. View dynamic RMEP configurations.



Management > CFM Management > Section CFM. Select a created MD level. Right-click

a MA and then choose View Dynamic Remote MEP from the right-click menu to view

configurations on dynamic RMEPs.

8. View LB detection information.



Management > CFM Management > Section CFM. Right-click a record about local MEP

and then choose LB from the right-click menu to view LB detection information.

9. View LT detection information.



Management > CFM Management > Section CFM. Right-click a record about local MEP

and then choose LT from the right-click menu to view LB detection information.

Viewing MIP information

This parameter is available for the multi-section PW CFM and Transit LSP CFM.

1. View multi-section PW MIP configurations.


Management > MSPW CFM. Select a created MD level. Select a MA to view

configurations on multi-section PW MIP.

2. View Transit MIP configurations.


Management > Transit LSP CFM. Select a MD level. Right-click a MA and then choose

View MIP from the right-click menu to view Transit MIP configurations.

Viewing Ethernet SLA configurations

Steps for viewing Ethernet SLA, Section SLA, Tunnel SLA, and PW SLA are similar. In this

guide, only steps for viewing Ethernet SLA are described.

1. View Ethernet SLA configurations.


SLA Config > Ethernet SLA to view Ethernet SLA configurations.

2. View and export SLA performance reports.

Raisecom





SLA Config > Ethernet SLA. Right-click a record and then choose Report from the right-

click menu to view and export the SLA performance report.

3. View Ethernet SLA statistics.


SLA Config > Ethernet SLA. Right-click a record and then choose Statistics from the right-

click menu to view Ethernet SLA statistics.

10.6 Configuring RFC2544


Scenario

At the Ethernet design phase, RFC2544 benchmarking test can help the Carrier get the

network operating quality data to optimize the design and construction scheme and reduce the

future Ethernet operation and maintenance cost.

At the Ethernet acceptance phase, with RFC2544 benchmarking test process and test method,

the Carrier and the network construction party can reach an agreement on execution and result

of network quality measurement at the same benchmarking level. In addition, it helps

implement network acceptance work.

To implement the test process, schedule and perform the test operation by configuring and

scheduling the RFC2544 test operation, follow these rules:

After a test operation is successfully scheduled, you cannot re-schedule it before the test

process is finished.

A scheduling command can be used to schedule multiple test operations with same type.

These operations are scheduled based on the creation time.

Schedule multiple different test operations based on the scheduling time.

The deletion operation fails when a test operation is scheduled and is being performed.

The result of a performed test operation is saved in the related result table. When Trap is

enabled, the NView NNM system can manage the test operation.

If a performed throughput test operation is re-scheduled, the original test result table will

be cleared.

Prerequisite The remote device, participating in RFC2544 test, is enabled with interface loopback.

We recommend that the MTU size of devices, participating in RFC2544 test, is greater

than 1540 bytes.

VLANs are created on the iTN201. In addition, the interfaces are in Trunk mode.

OAM remote loopback, MPLS-TP OAM, interface loopback, and ETH-Test are disabled

on the iTN201.

Raisecom




10.6.2 Creating test templates

By default, there are templates on the iTN201. The following table lists default values of these

parameters.

Parameter Default value Default value Default value

Template Name Default Template

Metric Type Throughput Latency Frame loss

Frame Size (byte) 64, 128, 256, 512, 1024, 1280, 1518, 1536

INIT SPEED (Mbit/s) – 1000 –

MIN SPEED (Mbit/s) 1 – –

MAX SPEED (Mbit/s) 1000 1000 –

STEP SIZE 10 10 –

PACKET LOSS RATIO

(0.01%)

0.01% – –

FRAME LOSS TEST SPEED

(Mbit/s)

– – 100

DICHOTOMY RESOLUTION

(Mbit/s)

1 – –

Pad Pattern Static Static Static

Static Value (0x) 12345678 12345678 12345678

OP Code (0x) 7 7 7

Test Duration (s) 60 60 60

Trial Times 20 20 20


Performance Test > RFC2544 > Template MGT.

Step 2 Right-click the left blank area at the Template MGT area and then choose


Step 3 A dialog box appears, where you can create a test template. The following table describes




Template Name Configure the template name.

Template

Description

Configure descriptions about the template.

Raisecom





Please select the

metric type

Select the metric type of the template to be created.

Throughput Latency Loss Rate

Throughput (This metric is available when the metric type is set to Throughput.)

Frame Size Click and select the size of test frame. The unit is set to byte.

You can select multiple options.

64 128 256 512 1024 1280 1518 1536

MIN SPEED

(Mbit/s)

Configure the minimum speed for sending the test packet. It ranges

from 1 to 1000 Mbit/s.

MAX SPEED

(Mbit/s)

Configure the maximum speed for sending the test packet. It ranges


STEP SIZE

(Mbit/s)

Configure the change granularity of speed for sending the test

packet. It ranges from 1 to 100 Mbit/s.

FRAME LOSS

RATIO (0.01%)

Configure the tolerable packet loss ratio. It ranges from 0% to

100%.

DICHOTOMY

RESOLUTION

(Mbit/s)

Configure the precision of dichotomy test. It ranges from 1 to 20

Mbit/s.

Pad Pattern Select a packet padding mode.

Static Increment

By default, it is set to Static.

Static Value (0x) Configure the static padding value. It is in hexadecimal notation and

ranges from 0x00000000 to 0xFFFFFFFF. By default, it is set to

0x12345678.

This parameter is available when the Pad Pattern is set to Static.

OP Code (0x) Display the operation code.

Test Duration (s) Configure the time for performing one test. It ranges from 1 to 600s.

Trial Times Configure the retry times of the test. It ranges from 1 to 20.

Latency (This metric is available when the metric type is set to Latency.)

Raisecom







64 128 256 512 1024 1280 1518 1536

INIT SPEED

(Mbit/s)

Configure the initial test speed. It ranges from 1 to 1000 Mbit/s. by

default, it is set to 1000 Mbit/s.

MAX SPEED

(Mbit/s)

Configure the maximum speed for sending the test packet. It ranges


STEP SIZE

(Mbit/s)

Configure the change granularity of speed for sending the test

packet. It ranges from 1 to 100 Mbit/s.

DICHOTOMY

RESOLUTION

(Mbit/s)


Mbit/s.


Static Increment




0x12345678.





Frame Loss (This metric is available when the metric type is set to Loss Rate.)



64 128 256 512 1024 1280 1518 1536

Raisecom





FRAME LOSS

TEST SPEED

(Mbit/s)

Configure the packet loss test speed. It ranges from 1 to 1000

Mbit/s.

DICHOTOMY

RESOLUTION

(Mbit/s)


Mbit/s.


Static Increment




0x12345678.





10.6.3 Configuring test tasks


Performance Test > RFC2544 > Test Task List.

Step 2 Right-click the blank area at the Test Task List area and then choose from the right-

click menu.

Step 3 A dialog box appears, where you can create a test task. The following table describes items at

the dialog box.

Step 4 Click at the Template Name area to select a created template.

Step 5 (Optional) you can enter parameters and create a test template. For details, see section 10.6.2

Creating test templates. After configurations, click Save to template.

Step 6 Select the Dispatch radio button to perform the test task.


Base Info

Dest NE MAC Configure the loopback MAC address of the remote device,

which is in colon hexadecimal notation.

MD Level Configure the Y.1731 MEG level of the test packet, which

ranges from 0 to 7.

Raisecom





Inner VLAN Enable Enable/Disable the inner VLAN of the test packet.

Enable Disable

Inner VLAN Configure the inner VLAN of the test packet, which ranges

from 1 to 4094.

This parameter is available only when the inner VLAN is

enabled.

Inner VLAN TPID (0x) Configure the TPID of inner VLAN Tag of the test packet,

which ranges from 0x0000 to 0xFFFF. By default, it is set to

0x8100.


enabled.

Inner VLAN Cos Configure the inner VLAN CoS value of the test packet, which

ranges from 0 to 7. By default, it is set to 0.


enabled.

Outer VLAN Enable Enable/Disable the outer VLAN of the test packet.

Enable Disable

Outer VLAN Configure the outer VLAN of the test packet, which ranges

from 1 to 4094.

This parameter is available only when the outer VLAN is

enabled.

Outer VLAN TPID

(0x)

Configure the TPID of outer VLAN Tag of the test packet,

which ranges from 0x0000 to 0xFFFF. By default, it is set to

0x8100.


enabled.

Outer VLAN Cos Configure the outer VLAN CoS value of the test packet, which

ranges from 0 to 7. By default, it is set to 0.


enabled.

10.6.4 Outputting reports

The iTN201 supports outputting test results in a PDF report from, facilitating users to view

them.



Step 2 Right-click a record and then choose Report from the right-click menu.

Step 3 A dialog box appears, where you can configure information about the report to be output. The


Raisecom




Step 4 After configurations, click Save As PDF.


Basic Information

Report Name Configure the report name.

Customer Configure the name of customer to whom the test task belongs.

Business Name Configure the test task name.

Vendor Configure the vendor name.

Maintenance Person Configure the information about the maintenance person.

Telephone Configure the telephone number of the maintenance person.

Remark Configure the remarks.

Test Category

Throughput Configure whether outputting the throughput test result to the

report.

Checked: output the throughput test result to the report. Unchecked: do not output the throughput test result to the report.

Loss Rate Configure whether outputting the packet loss ratio test result to the

report.

Checked: output the packet loss ratio test result to the report. Unchecked: do not output the packet loss ratio test result to the

report.

Latency Configure whether outputting the delay test result to the report.

Checked: output the delay test result to the report. Unchecked: do not output the delay test result to the report.

Contain Chart Configure whether including the chart information in the report.

Checked: include the chart information in the report. Unchecked: do not include the chart information in the report.

Test Category

Graph Click Query Result to display the test result of selected metrics in

a form of graph.

Data Select the Data tab to display the test result of selected metrics in a

form of data.


1. View configurations on RFC2544 test templates.


Performance Test > RFC2544 > Template MGT. Select a test template name from the left

RFC2544 Template tree topology and then view configurations on the RFC2544 test template.

2. View basic information about the RFC2544 test.

Raisecom





Performance Test > RFC2544 > Test Task List to view basic information about the

RFC2544 test.

3. View RFC2544 test results.


Performance Test > RFC2544 > Test Task List. Select a record at the related metric tab and

then choose Show Result from the right-click menu. A dialog box appears, select the frame

size and related test curve chart is displayed.


10.7.1 Examples for configuring EFM


As shown in Figure 10-2, to enhance the management and maintenance capability of the

Ethernet link between iTN A and iTN B, you need to deploy EFM on iTN A and iTN B. The

iTN A is the active end and the iTN B is the passive end. In addition, you need to deploy

OAM event Trap on iTN A.

Figure 10-2 Configuring EFM

Configuration steps

Step 1 Configure iTN A.

1. From the Action List of iTN A EMS, choose SNMP Management > Advanced MGT >


2. Select the record about Line 1 and then click Modify.

3. A dialog box appears, where you can enable OAM and configure EFM working modes.

The following table describes lists values of parameters.


Parameter Value

OAM Administration State Enable

OAM Operation Mode active




Raisecom




7. A dialog box appears, where you can enable local and peer OAM event Trap. The



Parameter Value

OAM Event Trap Enable True

OAM Peer Event Trap Enable True

Step 2 Configure iTN B.

1. From the Action List of iTN B EMS, choose SNMP Management > Advanced MGT >



3. A dialog box appears, where you can enable OAM and configure EFM working modes.

The following table describes lists values of parameters.


Parameter Value


Checking results

1. View EFM configurations.

From the Action List of iTN A EMS, choose SNMP Management > Advanced MGT >

OAM MGT (802.ah) > OAM Table and then select the OAM Table tab. Select the record

about Line 1 and then click View to view EFM configurations.

2. View configurations on OAM event Trap.


OAM MGT (802.ah) > OAM Trap Table. Select the record about Line 1 and then click

View to view configurations on OAM event Trap.

10.7.2 Examples for configuring CFM


As shown in Figure 10-3, Node B communicates with the RNC through iTN A, iTN B, and

iTN C at the ring network, as well as the iTN2100.

To make the Ethernet link between RNC and Node B provide Telecom-grade services, you

need to deploy CFM on iTN devices to achieve detecting, acknowledging, and locating faults

actively. iTN A and iTN C are MEPs and iTN B is the MIP.

Detect Ethernet faults on the link between iTN A Client 1 and iTN C Client 1. The MD level

is set to 3.

Raisecom




Figure 10-3 Configuring CFM

Configuration steps

Step 1 Adding interfaces to VLANs.

Configure iTN A.


VLAN Config.

2. Select the VLAN Static Table tab and then click Add. A dialog box appears, where you

can create VLAN 100. The following table lists values of parameters.


Parameter Value

VLAN ID 100



5. Select the record about Client 1 and then click Modify. A dialog box appears, where you

can configure allowed VLANs of the interface. The following table lists values of

parameters.


Parameter Value

Port Mode Access

Port Access Vlan Id 100

Raisecom






8. Select the record about Line 1 and then click Modify. A dialog box appears, where you


parameters.


Parameter Value

Port Mode Trunk

Configure iTN B.

1. From the Action List of iTN B EMS, choose SNMP Management > VLAN MGT >


2. Select the records about Line 1 and Line 2 and then click Modify. A dialog box appears,

where you can configure allowed VLANs of the interface. The following table lists



Parameter Value of Line 1 Value of Line 2


Port Trunk Allow Vlan List 1–4094 1–4094

Configure iTN C.


VLAN Config.

2. Select the VLAN Static Table tab and then click Add. A dialog box appears, where you

can create VLAN 100. The following table lists values of parameters.


Parameter Value

VLAN ID 100

4. From the Action List of iTN C EMS, choose SNMP Management > VLAN MGT >


5. Select the record about Client 1 and then click Modify. A dialog box appears, where you


parameters.


Parameter Value

Port Mode Access


Raisecom




7. From the Action List of iTN C EMS, choose SNMP Management > VLAN MGT >


8. Select the record about Line 1 and then click Modify. A dialog box appears, where you


parameters.


Parameter Value

Port Mode Trunk

Port Trunk Allow Vlan List 1–4094

Step 2 Enable CFM.

Configure iTN A.

1. From the Action List of iTN A EMS, choose SNMP Management > CFM


2. Select the Ethernet Global Info tab, where you can enable CFM.


Configuration steps for iTN B iTN C are identical to the ones for iTN A. Therefore, in this

guide, no details are described.

Step 3 Configure basic functions of CFM.

Configure iTN A.



2. Click from the tool bar of the iTN A EMS. A dialog box appears, where you can

create a MD. The following table lists values of parameters.

3. After configurations, click OK.

Parameter Value

Protocol Type Y.1731

MD Level 3

4. Select the created MD, right-click the blank area at the Ethernet CFM area, and then


5. A dialog box appears, where you can create a MA. The following table lists values of

parameters.


Parameter Value

MA Name ma1

S-VLAN 100

Raisecom




7. Select the created MA, select the MEP tab, right-click the blank area at the MEP tab, and

then choose Add from the right-click menu.

8. A dialog box appears, where you can create a MEP. The following table lists values of

parameters.


Parameter Value

MEP ID 301

Port 5

MEP Direction UP

Configuration steps for iTN B and iTN C are identical to the ones for iTN A. Configure iTN B

and iTN C with the following values.

The following table lists values of the MD.

Parameter Value of iTN B Value of iTN C

Protocol Type Y.1731 Y.1731

MD Level 3 3

The following table lists values of the MA.

Parameter Value of iTN B Value of iTN C

MA Name ma1 ma1

S-VLAN 100 100

The following table lists values of the local MEPs.

Parameter Value of iTN C

MEP ID 302

Port 5

MEP Direction UP

The following table lists the value of the RMEP.

Parameter Value of iTN C

Remote MEP ID 301

Raisecom




Step 4 Configure CFM fault detection.

Configure iTN A.



2. Right-click the record about local MEP 301 and then choose CCM Enable from the

right-click menu.

Configure iTN C.

1. From the Action List of iTN C EMS, choose SNMP Management > CFM


2. Right-click the record about local MEP 302 and then choose CCM Enable from the

right-click menu.

Checking results

View CFM configurations, taking iTN A for an example.

From the Action List of iTN A EMS, choose SNMP Management > CFM Management >

Global Config. Select the Ethernet Global Info tab to view EFM configurations.

10.7.3 Examples for configuring SLA


As shown in Figure 10-4, Node B communicates with the RNC through iTN A, iTN B, and

iTN C at the ring network, as well as the iTN2100.

To make the Ethernet link between RNC and Node B provide Telecom-grade services, you

need to deploy CFM on iTN devices. To effectively fulfil the SLA signed with users, the

Carrier deploys SLA on iTN A and schedules it periodically. SLA is used to detect the

network performance between iTN A and iTN C in time.

Perform Layer 2 delay test from iTN A to iTN C. Configure the y1731-echo operation on iTN

A as below:

Operation ID: 2

RMEP ID: 3

MD level: 3

VLAN ID: 100

CoS priority: 0

Scheduling lifetime: 20s

Test period: 10s

Raisecom




Figure 10-4 Configuring SLA

Configuration steps

Step 1 Configure CFM on iTN devices.

For details, see section 10.7.2 Examples for configuring CFM.

Step 2 Configure the Y.1731-echo operation on iTN A and enable operation scheduling.



2. Choose Edit > Add from the menu bar of iTN A EMS.

3. A dialog box appears, where you can configure the SLA operation. The following table


4. After configurations, click Confirm.

Parameter Value

Operation name 2

MD level 3

Schedule survival time Custom

Custom survival time (day) 20

Schedule cycle 10

CFM VLAN ID 100

Remote MEP ID 302

CFM Operation COS 0

CUSTOMER VALN ID 0

Raisecom




Parameter Value

Dispatch Selected


View SLA configurations, taking iTN A for an example.

From the Action List of iTN A EMS, choose SNMP Management > Advanced MGT > SLA

Config > Ethernet SLA to view SLA configurations.

10.7.4 Examples for configuring RFC2544 throughput test


As shown in Figure 10-5, iTN A is the RFC2544 test device and iTN Z is the DUT. iTN B is

the RFC2544 remote device and is enabled with interface loopback. The MAC address of iTN

B is set to 00:0e:5e:12:34:56. Both SVLAN and CVLAN of iTN A are enabled. Other

RFC2544 parameters use default values. Perform configurations on iTN A to test throughput

of iTN Z.

Figure 10-5 Configuring RFC2544 throughput test

Configuration steps

Step 1 Create a test template on iTN A.


Performance Test > RFC2544 > Template MGT.

2. Right-click the left blank area at the Template MGT area and then choose


3. A dialog box appears, where you can create a test template. The following table lists


4. After configurations, click Ok.

Parameter Value

Template Name 1

Frame Size 128

Please select the metric type Throughput

MIN SPEED (Mbit/s) 1000

Raisecom




Parameter Value

MAX SPEED (Mbit/s) 10

STEP SIZE (Mbit/s) 2

FRAME LOSS RATIO (0.01%) 50

DICHOTOMY RESOLUTION (Mbit/s) 10

Test Duration (s) 100

Trial Times 10

Step 2 Configure a test task and enable task scheduling.



2. Right-click the blank area at the Test Task List area and then choose from the

right-click menu.

3. A dialog box appears, where you can create a test task. The following table lists values

of parameters.

4. Click at the Template Name area to select the created template 1.

5. Select the Dispatch radio button to perform the test task.

Parameter Value

Dest NE MAC 00:0e:5e:12:34:56

Inner VLAN Enable Enable

Inner VLAN 1

Outer VLAN Enable Enable

Outer VLAN 1

Checking results

1. View configurations on the RFC2544 test template.


Performance Test > RFC2544 > Template MGT. select Template 1 from the left RFC2544

Template tree topology to view configurations on the RFC2544 test template.

2. View basic information about the RFC2544 test.


Performance Test > RFC2544 > Test Task List to view basic information about the

RFC2544 test.

3. View RFC2544 test results.


Performance Test > RFC2544 > Test Task List. Select the Throughput tab and then choose

Raisecom




Show Result from the right-click menu. A dialog box appears, select the frame size (128) and

related test curve chart is displayed.

Raisecom


Element Management) 11 Network reliability


11 Network reliability

This chapter describes principles and configuration procedures of network reliability, as well

as related configuration examples, including following sections:

Introduction

Configuring link aggregation

Configuring interface backup

Configuring ELPS

Configuring ERPS

Configuring MPLS-TP linear protection switching

Configuring failover

Maintenance


11.1 Introduction Ethernet is widely used because of its simplicity, high-efficiency and low-cost features. For a

long time, the reliability is one major factor that restricts the development of traditional

Ethernet in Telecom network. The poor reliability is related to the packet feature of born

services and the mechanism of Ethernet.

To enhance the reliability of Ethernet and to meet the requirements on the Telecom network,

you can deploy specified reliability technology in the Ethernet.

11.1.1 Link aggregation

Link Aggregation Control Protocol (LACP) is a protocol based on IEEE 802.3ad. With link

aggregation, multiple physical Ethernet interfaces are combined to form a logical aggregation

group. Multiple physical links in one aggregation group are taken as a logical link. Link

aggregation helps share traffics among member interfaces in an aggregation group. In addition

to effectively improving the reliability on links between devices, link aggregation can help

gain greater bandwidth without upgrading hardware.

Raisecom




11.1.2 Interface backup

At present, the dual uplink networking application is a commonly-used one. In dual uplink

networking, Spanning Tree Protocol (STP) is used to block the redundancy link and

implement backup. Though STP can meet users' backup requirements, it fails to meet

switching requirements. Though Rapid Spanning Tree Protocol (RSTP) is used, the

convergence is second level only. It is not a satisfied performance parameter for advanced

Ethernet devices applied to the Telecom-grade network.

Interface backup, targeted for dual uplink networking, implements backup and fast

convergence. It is designed for the dual uplink networking application to ensure the

performance and simplify configurations.

Interface backup is another resolution of STP. You can achieve link redundancy by manually

configuring interface backup when STP is disabled. If the device is enabled with STP, you

need to disable interface backup. STP provides functions similar to the ones realized by

interface backup.

Interface backup is realized by configuring the interface backup group. An interface backup

group contains a pair of interfaces, where an interface is the primary interface and the other

interface is a backup interface. The link, where the primary interface is, is called a primary

link. The link, where the backup interface is, is called a backup link.

Member interfaces in the interface backup group supports physical interfaces and Link

Aggregation Group (LAG) but do not support Layer 3 interfaces.

In the interface backup group, when an interface is in Up status, the other interface is in

standby status. Only one interface can be in Up status. When the interface in Up status fails,

the standby interface can be switched to Up status to sustain a normal link.

11.1.3 ELPS

Ethernet Linear Protection Switching (ELPS) is an Automatic Protection Switching (APS)

protocol based on the ITU-TG.8031 recommendation. It is an end-to-end protection

technology used to protect an Ethernet connection.

ELPS deploys protection resources for working resources, such as path and bandwidth, etc.

ELPS technology takes a simple, fast, and predictable mode to realize network resource

switching, easier for Carrier to plan network more efficiently and learn network active status.

11.1.4 ERPS

Ethernet Ring Protection Switching (ERPS) is an APS protocol based on the ITU-TG.8032

recommendation. It is a link-layer protocol specially used in Ethernet rings. Generally, ERPS

can avoid broadcast storm caused by data loopback in Ethernet rings. When a link/device on

the Ethernet ring fails, traffic can be quickly switched to the backup link to ensure restoring

services quickly.

ERPS uses the control VLAN in the ring network to transmit ring network control

information. Meanwhile, combining with the topology feature of the ring network, it

discovers network fault quickly and enable the backup link to restore service fast.

11.1.5 MPLS-TP linear protection switching

MPLS-TP linear protection switching previously-establishes a related protection LSP

(secondary LSP) for the working LSP (primary LSP) and assigns bandwidth for it. The

working LSP and protection LSP makes a protection group. When the working LSP fails, data

Raisecom




flow is switched quickly to the protection LSP to reduce packet loss/delay problems caused by

working LSP failure. This helps improve network reliability. MPLS-TP linear protection

switching is an end-to-end protection architecture, developed based on G.8031.

MPLS-TP linear protection switching is divided into 1+1 protection switching and 1:1

protection switching. 1+1 protection switching can either be unidirectional or bidirectional

while 1:1 protection switching is bidirectional.

At present, the iTN201 supports 1:1 protection switching only.

1+1 protection switching

1+1 protection switching can either be unidirectional or bidirectional. In 1+1 protection

switching, data flow can be switched from the working LSP to the protection LSP in failed

direction or be switched from the working LSP to the protection LSP in failed and unfailed

directions. Bidirectional protection switching coordinates the connection of ends through

Automatic Protection Switching (APS). Figure 11-1 shows 1+1 protection switching.

Figure 11-1 1+1 protection switching

The sender sends service packets through 2 LSPs and the receiver receives these packets

through the configured working LSP and uses CFM to detect LSPs between them. When the

receiver discovers that the working LSP fails and the protection LSP works fail, it switches

services to the protection LSP.

1:1 protection switching

1:1 protections witching is bidirectional. Data flow is switched from the working LSP to the

protection LSP in failed and unfailed directions. Bidirectional protection switching

coordinates the connection of ends through APS. Figure 11-2 shows 1:1 protection switching.

Raisecom




Figure 11-2 1:1 protection switching

The sender sends service packets through the configured working LSP through which the

receiver will receive these packets. When the working LSP fails, the receiver will detect the

fault and trigger APS to switch data to the protection LSP. The whole process is shown as

below:

Step 2 The receiver detects a fault.

Step 3 The receiver communicates with the sender through the working LSP and protection LSP and

sends APS command to the sender through the protection LSP to ask for protection switching.

Step 4 The sender sends the APS command to confirm the protection switching request. In addition,

the sender sends service packets to the receiver through the working LSP and protection LSP.

Step 5 The sender and receiver switch data to the protection LSP for transportation.

11.1.6 Failover

Failover provide an interface linkage scheme to expand the range of link backup. By

monitoring the uplinks and synchronizing downlinks, the fault generated on the uplink device

can be transmitted to downlink devices to trigger switching. This helps avoid traffic loss when

downlink devices cannot sense faults of uplinks.

As shown in Figure 11-3, interface Line 1 is the primary interface and interface Line 2 is the

secondary interface. Add uplink interfaces (interfaces Line 1 and Line 2) and the downlink

interface (interface Client 1) to a failover group. Once uplink interfaces fail, the downlink

interface is in Down status. The downlink interface returns to Up status once one or both

uplink interfaces recover. Therefore, the uplink link status is notified to the downstream

devices immediately. Uplink interfaces work properly when the downlink interface fails.

Figure 11-3 Interface-to-interface failover

Raisecom




11.2 Configuring link aggregation


Scenario

When needing to provide greater bandwidth and reliability for a link between two devices,

you can configure link aggregation.

The iTN201 supports the following 2 link aggregation modes:

Manual link aggregation mode

Static LACP link aggregation mode

Prerequisite Before configuring link aggregation, you need to configure physical parameters of the

interface and make the physical layer Up.

If the iTN201 uses the default community, you cannot configure the LACP module.

Therefore, perform the following operations:

− Configuring the view: Raisecom(config)#snmp-server view tv 1.2 included

– Configuring the community: Raisecom(config)#snmp-server community abcd

view tv ro(rw)

– Setting the read-only community name to abcd: right-click the iTN201 node at the

NView NNM topology view and then choose Edit > Edit Properties from the right-

click menu.

11.2.2 Configuring manual link aggregation

Configuring manual link aggregation modes


LACP and then select the Trunk Group Table tab.


Step 3 A dialog box appears, where you can configure the link aggregation modes and related

information. The following table describes items at the dialog box.



Aggregation Group

Mode

Set the link aggregation mode to Manual.

Aggregation Group

Min Links

Configure the minimum number of links for a LAG. It ranges

from 1 to 8 and is set to 1 by default.

Raisecom





Aggregation Group

Max Links

Configure the maximum number of links for a LAG. It ranges


For a LAG, the maximum number of links should be equal to or greater than the minimum number of links.

Configuring basic information about link aggregation


LACP.

Step 2 Select the Trunk Config tab, where you can configure basic information about link

aggregation. The following table describes items at the tab.



Link Aggregation Status Enable/Disable link aggregation.

Enable Disable

By default, link aggregation is enabled.

Link Aggregation Load

Sharing Mode

Select a load-sharing mode of link aggregation.

SourceMAC: select the forwarding interface based on the

source MAC address and ensure that packets from the same

source MAC address are forwarded through this interface. DestinationMAC: select the forwarding interface based on

the destination MAC address and ensure that packets sent to

the same source MAC address are forwarded through this

interface. SourceXORDestinationMAC: select the forwarding

interface based on the OR result of the source and

destination MAC addresses and ensure that packets with the

same source result are forwarded through this interface. SourceIP: select the forwarding interface based on the

source MAC address and ensure that packets from the same

source IP address are forwarded through this interface. DestinationIP: select the forwarding interface based on the

destination IP address and ensure that packets from the

same source MAC address are forwarded through this

interface. SourceXORDestinationIP: select the forwarding interface

based on the OR result of the source and destination IP

addresses and ensure that packets with the same source

result are forwarded through this interface.

By default, it is set to SourceXORDestinationMAC.

Raisecom





Actor System Priority Configure the LACP priority of the local system, which


The end with a higher priority is the active end. LACP selects

the active interface and backup interface based on

configurations on the active end.

The smaller the value is, the higher the priority is. If the

LACP priorities are identical, the one with a smaller MAC

address is taken as the active end.

In a LAG, member interfaces that share loads must be identically configured. Otherwise, data cannot be forwarded properly. These configurations include QoS, QinQ, VLAN, interface properties, and MAC address learning. 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 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

configuration, and whether continue to forwarding packets after the MAC address entries exceed the threshold.

Configuring LAGs of interfaces


LACP and then select the Aggregation Port Table tab.


Step 3 A dialog box appears, where you can configure the LAG of the interface. The following table




Agg Port Index Display the interface ID.

Actor Admin Key Configure the IP of the LAG to which the interface is added.

Actor Port Priority Configure the priority of the local interface, which ranges from 0

to 65535. The smaller the value is, the higher the priority is and

the more possible the interface is an active one.

Raisecom




11.2.3 Configuring static LACP link aggregation

Configuring static LAG and maximum/minimum number of active links




Step 3 A dialog box appears, where you can configure the mode of the LAG and

maximum/minimum number of active links of the interface. The following table describes




Aggregation Group

Mode

Set the link aggregation mode to Lacp-Static.

Aggregation Group

Min Links

Configure the minimum number of links for a LAG. It ranges


Aggregation Group

Max Links

Configure the maximum number of links for a LAG. It ranges


Configuring LACP priority on interfaces




Step 3 A dialog box appears, where you can configure the LACP priority of the interface. The




Actor Port Priority Configure the priority of the local interface, which ranges from 0 to

65535 and is set to 32768 by default.

The LACP priority is used to select the default interface of LACP.

The smaller the value is, the higher the priority.

Enabling link aggregation


LACP.

Step 2 Select the Trunk Config tab, where you can enable link aggregation. The following table

describes items at the tab.

Raisecom







1. View the interface status, flag, interface priority, administration key, operation key,

LACP priority, system MAC address, and interface state machine status of the local and

remote LACP.


LACP and then select the Aggregation Table tab. Select a record and then click View to view

the interface status, flag, interface priority, administration key, operation key, LACP priority,

system MAC address, and interface state machine status of the local and remote LACP.

2. View LACP statistics on an interface, including total number of Tx/Rx LACP packets,

Tx/Rx Marker packets, Marker Response packets, and error packets.


LACP and then select the Port Stats Table tab. Select a record and then click View to view

LACP statistics on the interface, including total number of Tx/Rx LACP packets, Tx/Rx

Marker packets, Marker Response packets, and error packets.

3. View configurations on local LACP status and load-sharing mode of the LAG.


LACP and then select the Trunk Config tab. Select a record and then click View to view

configurations on local LACP status and load-sharing mode of the LAG.

4. View member interfaces and currently-effective interfaces of all LAGs.


LACP and then select the Trunk Group Table tab. Select a record and then click View to view

member interfaces and currently-effective interfaces of all LAGs.

11.3 Configuring interface backup


Scenario

Interface backup can realize redundancy backup and fast switching of primary and backup

links, VLAN-based interface backup can realize load-sharing among different interfaces.

Interface backup ensures millisecond level switching and simplifies configurations.

Prerequisite

Before configuring interface backup, perform the following operations:

Create a VLAN.


Raisecom




11.3.2 Configuring basic functions of interface backup

In an interface backup group, an interface is a primary interface or a backup

interface. In a VLAN, an interface/LAG is a member of only one interface backup group.

Configuring interface backup


Backup.

Step 2 Select the Port Backup Management Table and then click Add.

Step 3 A dialog box appears, where you can configure the interface backup group. The following




Primary Port Click Select and then select a primary interface.

Standby Port Click Select and then select a secondary interface.

Vlanlist Configure the specified VLAN list for the interface backup group.

Enter the specified VLAN list. Select the default radio box: VLAN IDs 1–4094.

Configuring interface backup parameters


Backup.

Step 2 Select the Port Backup Config tab, where you can configure interface backup parameters. The




Restoration Mode Select an interface restoration mode.

Port-Up: interface connection mode. In this mode, the link returns

to the proper status when the interface is Up. Neighbor-Discover: neighbor discovery mode. In this mode, the

link returns to the proper status when the interface discovers the

neighbor through Raisecom Neighbor Discover Protocol (PNDP). Disable: disable interface backup.

By default, it is set to Port-Up.

Restoration Delay Configure the interface restoration delay, which ranges from 0 to

300s. By default, it is set to 15s.

Raisecom






1. View configurations on the interface backup group.


Backup and then select the Port Backup Management Table. Select a record and then click

View to view configurations on the interface backup group.

2. View interface backup parameters.


Backup. Select the Port Backup Config tab to view interface backup parameters.

11.4 Configuring ELPS


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 protection switching and 1:1 protection switching architectures:

1+1 protection switching: each working line is assigned with a protection line. When the

working line fails, both ends negotiate through the APS protocol. In the protection

domain, the source end sends traffic through the working and protection lines while the

destination end receives the traffic from one line.

1:1 protection switching: each working line is assigned with a protection line. The source

end sends traffic through the working/protection line. In general, the source sends traffic

through the working line. The protection line is a backup line. When the working line

fails, the source end and destination end communicate through APS protocol to switch

traffic to the protection line simultaneously.

Based on whether the source end and destination end switch traffic simultaneously, ELPS is

divided into unidirectional switching and bidirectional switching:

Unidirectional switching: when one direction of a line fails, one end can receive the

traffic while the other end fails to receive the traffic. The end failing to receive the traffic

detects a fault and switches the traffic. And the other end does not detect the fault and

switch traffic. Therefore, both ends may receive the traffic through different lines.

Bidirectional switching: when a line fails, even in one direction, both ends communicate

through APS protocol to switch traffic to the protection line. Therefore, both ends receive

and send the traffic through the same line.

1+1 protection switching is divided into unidirectional switching and bidirectional switching.

1:1 protection switching supports bidirectional switching only.

The iTN201 supports bidirectional 1:1 protection switching only.

ELPS provides 3 modes to detect a fault:

Raisecom




Detect faults based on the 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.

Detect faults based on the physical interface status or CFM.

ELPS provides 2 timers:

HOLDOFF timer: After the HOLDOFF timer is configured, when the working line fails,

the system will delay processing the fault. It means that traffic is delayed to be switched

to the protection line. This helps prevent frequent switching caused by working line

vibration.

WTR timer: In revertive mode, traffic is automatically switched from the protection line

to the working line when the working line recovers from a fault. After the WTR timer is

configured, traffic is not switched to the working line immediately. Instead, traffic is not

switched to the working line unless the WTR timer times out. This helps prevent

frequent switching caused by working line vibration.

Prerequisite

Before configuring ELPS, perform the following operations:

Connect interfaces and configure physical parameters for them. Make the physical layer

Up.

Create a VLAN.


Configure CFM detection between devices and these devices forms a neighbor

relationship (preparing for CFM detection mode).

11.4.2 Creating protection lines

Creating ELPS protection lines

Step 1 From the Action List of the iTN201 EMS, choose SNMP Management > APS Protection >

APS Line Protected > G.8031 > Config.

Step 2 Select the Linear Protection Configuration Table and then click Add.

Step 3 A dialog box appears, where you can create an ELPS protection line. The following table



Table 11-1 Creating protection lines


Index Configure the ELPS protection line ID, which ranges from 1

to 32.

Type Set the ELPS protection line type to ether-aps.

Working Entity Port Click Select and then select a working interface.

Raisecom





Working Block Vlanlist Configure the service VLAN list of the working line, which


Protection Port Click Select and then select a protection interface.

Protection Block Vlanlist Configure the service VLAN list of the protection line, which


Configured Protection

Group

Select a protection switching mode.

ONE_TO_ONE_NO_REVERT ONE_TO_ONE

Protocol Vlan Configure the protocol VLAN, which ranges from 1 to 4094.

Configuring WTR timer


APS Line Protected > G.8031 > Config and then select the Linear Protection Configuration

Table tab.


Step 3 A dialog box appears, where you can configure the WTR timer. The following table describes




Name Configure the linear protection switching name, which ranges

from 0 to 32 characters.

WTR Timer (min) Configure the WTR timer of the ELPS protection line. It

ranges from 1 to 12 minutes and is set to 5 minutes.

We recommend that WTR timer configurations on both ends keep consistent. Otherwise, we cannot ensure 50ms quick switching.

Setting fault detection mode to physical-link-based detection


APS Line Protected > G.8031 > Fault Detection.


Step 3 A dialog box appears, where you can set the fault detection mode to physical-link-based

detection.


Raisecom




Setting fault detection mode to CC-based detection




Step 3 A dialog box appears, where you can set the fault detection mode to CC-based detection. The




Failure Detect Type Set the fault detection mode to CC-based detection.

MD Name Configure the MD name, which ranges from 1 to 16 characters.


Local MEP Id Configure the local MEP ID, which ranges from 1 to 8191.

Remote MEP Id Configure the RMEP ID, which ranges from 1 to 8191.

MD Level Configure the MD level, which ranges from 1 to 7.

Setting fault detection mode to physical-link-/CC-based detection




Step 3 A dialog box appears, where you can set the fault detection mode to physical-link-/CC-based

detection. The following table describes items at the dialog box.



Failure Detect Type Set the fault detection mode to physical-link-/CC-based detection.

MD Name Configure the MD name, which ranges from 1 to 16 characters.


Local MEP Id Configure the local MEP ID, which ranges from 1 to 8191.

Remote MEP Id Configure the RMEP ID, which ranges from 1 to 8191.

MD Level Configure the MD level, which ranges from 1 to 7.

Raisecom




11.4.3 (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.

You cannot configure ELPS switching control through the NView NNM system unless you configure ELPS on both ends. Otherwise, configurations fail.

Locking protection switching

After the configuration, the traffic is not switched to the protection line even the working line

fails.



Table tab.

Step 2 Select a record and then click Lock Out.

Step 3 A dialog box appears and then click OK.

Configuring forced switch

After the configuration, the traffic is forcibly switched from the working line to the protection

line.



Table tab.

Step 2 Select a record and then click Force Switch.


Switching traffic to the working line manually

After traffic is switched from the protection line to the working line, configurations may be inconsistent if the working line fails/recovers or other commands are executed. In this case, you need to click Clear Out to clear protection line statistics to ensure configurations on both ends are consistent.

In non-revertive mode, switch the traffic from the protection line to the working line manually.



Table tab.

Step 2 Select a record and then click Manual Switch To Work.


Raisecom




Switching traffic to the protection line manually

Switch the traffic from the working line to the protection line manually



Table tab.

Step 2 Select a record and then click Manual Switch.


Clearing protection switching



Table tab.

Step 2 Select a record and then click Clear Out.




1. View configurations on the protection line.

From the Action List of the iTN201 EMS, choose SNMP Management > APS Protection >


Table tab. Select a record and then click View to view configurations on the protection line.

2. View protection line statistics.


APS Line Protected > G.8031 > Config and then select the Statistics Table of Ethernet

Linear Protection switching tab to view protection line statistics.

11.5 Configuring ERPS


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 iTN201 supports the single ring, intersecting ring, and tangent ring.

Raisecom




ERPS provides 3 modes to detect a fault:

Detect faults based on the 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.

Detect faults based on the physical interface status or CFM.

Prerequisite

Before configuring ERPS, perform the following operations:

Connect interfaces and configure physical parameters for them. Make the physical layer

Up.

Create a VLAN.


Configure CFM detection between devices and these devices forms a neighbor

relationship (preparing for CFM detection mode).

11.5.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 set to RPL Neighbour. 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. Non-intersecting node of the master ring should be in a protection ring and the non-intersecting node of the sub-ring should be in another protection ring. The intersecting node of the master ring and sub-ring should be in these 2 protection rings simultaneously.

Configurations on the non-intersecting mode of the master ring and sub-ring are identical to the ones on the common single ring.

Creating ERPS protection ring

Only one device on the protection ring can be set to the RPL Owner and one device is set to

RPL Neighbour. Other devices are set to ring forwarding nodes.


APS Ring Protected > G.8032 > Config.

Step 2 Select the EthRngPrt_Mng_Cfg and then click Add.

Step 3 A dialog box appears, where you can create an ERPS protection ring. The following table




Ring Id Configure the ERPS protection ring ID, which ranges from 1 to 255.

Raisecom





East Port Click Select and then select an east interface.

West Port Click Select and then select a west interface.

Node Type Select a node type.

Transfer: forwarding node owner: at one end of the RPL. In normal status, it is blocked and

is activated when the link fails. neighbour: at one end of the RPL. In normal status, it is blocked

and is activated when the link fails. It corresponds to the RPL

Owner.

Rpl Link Select a RPL type.

East: fault detection mode of the east interface west: fault detection mode of the west interface

Revert Mode Select a link mode.

Revertive: in this mode, traffic is switched from the protection

line to the working line when the working line recovers. Non-revertive: in this mode, traffic is not switched from the

protection line to the working line when the working line

recovers.

Traffic VLAN List Configure the service VLAN list, which ranges from 1 to 4094.

Protocol VLAN Configure the protocol VLAN, which is used to transport ERPS

protocol packets. It ranges from 1 to 4094 and is set to 1 by default.

Configuring timers


APS Ring Protected > G.8032 > Config and then select the EthRngPrt_Mng_Cfg tab.


Step 3 A dialog box appears, where you can configure the timers. The following table describes




Guard Timer (ms) Configure the Guard timer, which ranges from 20 to 2000ms. By

default, it is set to 500ms.

After the ring Guard timer is configured, the failed node does not

process APS packets during a period. In a bigger ring network, if

the failed node recovers from a fault immediately, it may receive the

fault notification sent by the neighbor node on the protection ring.

Therefore, the node is in Down status again. You can configure the

ring Guard timer to resolve this problem.

Raisecom





Wtr Timer (m) Configure the WTR timer, which ranges from 1 to 12min. By

default, it is set to 5min.

In revertive mode, when the working line recovers from a fault,

traffic is not switched to the working line unless the WTR timer

times out.

HoldOff Timer

(100ms)

Configure the HOLDOFF timer, which ranges from 0 to 100. By


After the HOLDOFF timer is configured, when the working line

fails, the system will delay processing the fault. It means that traffic

is delayed to be switched to the protection line. This helps prevent


11.5.3 (Optional) creating ERPS protection sub-ring

Creating sub-ring on intersecting nodes



Step 2 Select the EthRngPrt_Mng_Cfg and then click Add.

Step 3 A dialog box appears, where you can create a sub-ring on the intersecting node. The following




Ring Id Configure the ERPS protection ring ID, which ranges from 1 to 255.

East Port Click Select and then select an east interface.

West Port Click Select and then select a west interface.

Node Type Select a node type.

Transfer: forwarding node owner: at one end of the RPL. In normal status, it is blocked and

is activated when the link fails. neighbour: at one end of the RPL. In normal status, it is blocked.

Rpl Link Select a RPL type.

East: fault detection mode of the east interface west: fault detection mode of the west interface

Revert Mode Select a link mode.

Revertive: in this mode, traffic is switched from the protection

line to the working line when the working line recovers. Non-revertive: in this mode, traffic is not switched from the

protection line to the working line when the working line

recovers.

Raisecom





Protocol VLAN Configure the protocol VLAN, which is used to transport ERPS

protocol packets. It ranges from 1 to 4094 and is set to 1 by default.

Configuring the sub-ring virtual circuit mode, ring Propagate switch, and protocol version




Step 3 A dialog box appears, where you can configure the sub-ring virtual circuit mode, ring

Propagate switch, and protocol version. The following table describes items at the dialog box.



Propagate Switch Enable/Disable the Propagate switch.

Enable Disable

Because data of the sub-ring needs to be transmitted through

the master ring, there are MAC address table of the sub-ring

on the master ring. When the sub-ring fails, it needs to use the

Propagate switch to inform the master ring of refreshing the

MAC address table to avoid traffic loss.

Sub-ring Virtual Channel Select a sub-ring virtual circuit mode.

with: protocol packets of the sub-ring are transmitted

through the master ring. without: protocol packets of the sub-ring are transmitted

through the sub-ring protocol VLAN. Therefore, the

blocked VLAN list does not contain the protocol VLAN.

Protocol Version Select a protocol version.

v1 v2

11.5.4 Configuring ERPS fault detection modes


APS Ring Protected > G.8032 > Fault Detection.


Step 3 A dialog box appears, where you can configure the ERPS fault detection modes. The



Raisecom





Failure detection Type Select a fault detection type.

Physical Link Check: detect faults based on the physical

interface status: learning link fault quickly and switching

services immediately, suitable for detecting the fault between

neighbor devices. Continuity Check: detect faults based on CFM: suitable for

unidirectional detection or multi-device crossing detection. Physical Link or Continuity Check: detect faults based on the

physical interface status or CFM.

By default, it is set to Physical Link Check.

Md Name Configure the MD name, which ranges from 1 to 16 characters.

This parameter is available when the Failure detection Type is

set to Continuity Check/Physical Link or Continuity Check.

Ma Name Configure the MA name, which ranges from 1 to 13 characters.



Local Mep Configure the local MEP ID, which ranges from 1 to 8191.



Remote Mep Configure the RMEP ID, which ranges from 1 to 8191.



Md Level Configure the MD level, which ranges from 1 to 7.



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

Switching traffic to east interface forcibly



Step 2 Select a record and then click Force West.


Raisecom




Switching traffic to west interface forcibly



Step 2 Select a record and then click Force East.


Switching traffic to east interface manually

Configure this function in non-revertive mode.



Step 2 Select a record and then click Manual West.


Switching traffic to west interface manually



Step 2 Select a record and then click Manual East.


Clearing protection switching



Step 2 Select a record and then click Clear Out.




1. View configurations on the ERPS ring.


APS Ring Protected > G.8032 > Config and then select the EthRngPrt_Mng_Cfg tab. Select

a record and then click View to view configurations on the ERPS ring.

2. View ERPS ring status.


APS Ring Protected > G.8032 > Config. Select the EthRngPrt_Mng_Sta tab to view ERPS

ring status.

3. View ERPS ring statistics.


APS Ring Protected > G.8032 > Config. Select the EthRngPrt_Mng_Lnk tab to view ERPS

ring statistics.

Raisecom




11.6 Configuring MPLS-TP linear protection switching


Scenario

MPLS-TP linear protection switching provides a secondary link to protect the primary link,

providing end-to-end protection for the LSP between 2 devices.

Prerequisite

Before configuring MPLS-TP linear protection switching, you need to configure basic

functions of MPLS and MPLS-TP OAM.

11.6.2 Configuring Tunnel protection group

By creating MPLS-TP linear protection group, you can assign related protection resources for

working resources and switch network resources in a predictable mode. The MPLS-TP linear

protection group can be used to plan network and learn network status effectively, realizing

Carrier-class operation.


Tunnel Protection Group > Tunnel Protection Group.

Step 2 Click at the tool bar of the iTN201 EMS. A dialog box appears, where you can configure

the Tunnel protection group. The following table describes items at the dialog box.

Table 11-2 Parameters of Tunnel protection group


Name Configure the Tunnel protection group identifier, which ranges from

1 to 200 characters.

Protection Group

Name

Configure the Tunnel protection group name, which ranges from 1

to 200 characters.

Protection Group

Number

Configure the Tunnel protection group ID, which ranges from 1 to

32.

The Tunnel protection group ID should differ from the index listed in Table 11-1 Creating protection lines.

Raisecom





Protection Type Configure the Tunnel protection group type.

SNC: 1:1 bidirectional protection switching. Assign a protection

transport entity for each working transport entity. The source and

destination select the same transport entity by negotiating through

the APS protocol.

1:1: 1:1 bidirectional protection switching. Assign a protection

line for each working line. The traffic is transmitted through the

working/protection line. The he source and destination select the

same transport entity by negotiating through the APS protocol.

By default, it is set to 1:1.

Recovery Mode Configure revertive modes of the Tunnel protection group.

Recovery: after protection switching is enabled, traffic is switched

back to the working line when it recovers from a fault. Non-recovery: after protection switching is enabled, traffic is not

automatically switched back to the working line even when it

recovers from a fault.

By default, it is set to Recovery.

Reversion Time

(min)

Configure the WTR timer of the Tunnel protection group. It ranges

from 1 to 12min and is set to 5min by default.

In revertive mode, traffic is automatically switched from the

protection line to the working line when the working line recovers

from a fault. After the WTR timer is configured, traffic is not

switched to the working line immediately. Instead, traffic is not

switched to the working line unless the WTR timer times out. This

helps prevent frequent switching caused by working line vibration.

HoldOff time

(100ms)

Configure the HOLDOFF timer of the Tunnel protection group,

which ranges from 0 to 100. By default, it is set to 0.

After the HOLDOFF timer is configured, when the working line

fails, the system will delay processing the fault. It means that traffic

is delayed to be switched to the protection line. This helps prevent


Work Path Fault

Detect Type

Configure fault detection modes of the working line.

SD: signal degradation fault detection CC: CFM CC fault detection Link: physical link detection: SD CC: SD+CC fault detection SD Link: SD+physical link fault detection CC Link: CC+physical link fault detection SD CC Link: CC+SD+physical link fault detection

By default, it is set to CC Link.

Raisecom





Protect Path Fault

Detect Type

Configure fault detection modes of the protection line.

SD: signal degradation fault detection CC: CFM CC fault detection Link: physical link detection: SD CC: SD+CC fault detection SD Link: SD+physical link fault detection CC Link: CC+physical link fault detection SD CC Link: CC+SD+physical link fault detection

By default, it is set to CC Link.

Remark Configure the remark of the Tunnel protection group, which ranges

from 0 to 512 characters.

Step 3 Click Choose and then select the working Tunnel and protection channel. You can select the

work two-way/Protection of two-way radio buttons.

Step 4 After configurations, select the Deploy radio button and then click Save.

11.6.3 Configuring protection switching

By default, the protection switching mode of a created Tunnel protection group is set to auto-switching.

Locking protection switching



Step 2 Select a record and then choose Switch > Lock from the tool bar of the iTN201 EMS.

Therefore, traffic is not switched to the protection line automatically even the working line

fails.

Configuring forced switch



Step 2 Select a record and then choose Switch > FS from the tool bar of the iTN201 EMS to switch

the traffic from the working line to the protection line forcibly.

Configuring manual switch

After traffic is switched from the protection line to the working line, configurations may be inconsistent if the working line fails/recovers or other commands are executed. In this case, you need to choose Switch > Clear from the tool bar of the iTN201 EMS to clear protection line statistics to ensure configurations on both ends are consistent.

Raisecom






Step 2 Select a record and then choose Switch > MS from the tool bar of the iTN201 EMS to switch

the traffic from the working line to the protection line manually.

Step 3 (Optional) select a record and then choose Switch > MSW from the tool bar of the iTN201

EMS to switch traffic from the protection line to the working line manually.

Clearing protection switching commands



Step 2 Select a record and then choose Switch > Clear from the tool bar of the iTN201 EMS to clear

MPLS-TP linear protection switching commands.



1. View Tunnel protection group information.


Tunnel Protection Group > Tunnel Protection Group to view statistics about linear

protection switching.

2. View information about the working and protection Tunnels of the Tunnel protection

group.


Tunnel Protection Group > Tunnel Protection Group. Select a record and then click the

Tunnel information tab to view information about the working and protection Tunnels.

3. View Tunnel OAM information.


Tunnel Protection Group > Tunnel Protection Group. Select a record and then click the

OAM tab to view Tunnel OAM information.

11.7 Configuring failover


Scenario

When the uplink of the middle device fails and the middle device fails to inform the

downstream devices of the fault, the traffic cannot be switched to the backup line. This may

cause traffic break.

The failover feature is used to add the upstream interfaces and downstream interfaces of the

middle device to a failover group. In addition, it is used to monitor the upstream interfaces.

When all upstream interfaces fail, downstream interfaces are in Down status. When one failed

upstream interface recovers from the fault, all downstream interfaces are in Up status.

Raisecom




Therefore, faults of the uplinks can be notified to the downstream devices in time. If

downstream interfaces fail, upstream interfaces still work properly.

Prerequisite

Before configuring failover, you need to connect interfaces, configure physical parameters of

the interfaces and make the physical layer Up.

11.7.2 Configuring failover

A failover group may have multiple upstream interfaces. Failover is not performed when at least one upstream interface is in Up status. Failover is performed only when all upstream interfaces are in Down status. When you delete a failover group, if there are member interfaces in the failover group, configurations fail. Otherwise, the failover group is deleted successfully.

Creating and enabling failover group


Link State Track.

Step 2 Select the Fault Track Group Config Table tab and then click Add.

Step 3 A dialog box appears, where you can create a failover group. The following table describes




Fault track group

index

Enter the failover group ID, which is an integer and ranges from 1

to 32.

Fault upstream type Select a fault source for the failover group.

Port: interface-based failover group Lacp: LACP-based failover group

By default, it is set to Port.

Raisecom





Fault pstream

portlist

Select interfaces to be added to the failover group. Click Select

and then choose interfaces. After configurations, click Confirm.

This parameter is available when then Fault upstream type is set to

Port.

iTN201-4GF: Line 1–Line 4, Client 1–Client 12, ETH 1/1–ETH

1/4, ETH 2/1–ETH 2/4, Port-channel 1–Port-channel 8, with

interface ID ranging from 1 to 32 iTN201-2XG: Line 1–Line 2, Client 1–Client 12, ETH 1/1–ETH

1/4, ETH 2/1–ETH 2/4, Port-channel 1–Port-channel 8, with

interface ID ranging from 1 to 30

Fault upstream lacp

group id

Enter the LAG ID, which is an integer and ranges from 1 to 8.

This parameter is available when then Fault upstream type is set to

Lacp.

Enabling Trap of failover group


Link State Track and then select the Fault Track Group Config Table tab.

Step 2 Select a record and then click Modify. A dialog box appears, where you can enable/disable

Trap of the failover group.

Enable: the failover group sends Trap to the NView NNM system.

Disable: the failover group does not send Trap to the NView NNM system.


Configuring actions of failover group


Link State Track and then select the Fault Track Port Config Table tab.

Step 2 Select a record and then click Modify. A dialog box appears, where you can configure actions

of the failover group. The following table describes items at the dialog box.



Fault track group index Read-only failover group ID

Raisecom





Fault action mode The iTN201 can perform the following actions when a fault

occurs:

NoAction: perform no action. Shutdown: shut down the interface. At the Fault action

portlist text box, click Select to select interfaces to be

shut down. Modify-Pvid: modify the PVID. At the Fault action port

pvid text box, enter the PVID of the interface, which is an

integer and ranges from 1 to 4094. At the Fault action set

pvid portlist text box, click Select to select interfaces

whose PVIDs need to be modified. Delete-Vlan: delete the VLAN. At the Fault action delete

vlan text box, enter the VLAN ID to be deleted, which is

an integer and ranges from 1 to 4094. Suspend-Vlan: suspend the VLAN. At the Fault action

suspend vlan text box, enter the VLAN ID to be

suspended, which is an integer and ranges from 1 to 4094.



View failover group configurations.


Link State Track and then select the Fault Track Group Config Table tab. Select a record and

then click View to view failover group configurations.

11.8 Maintenance Perform the following operations on the iTN201 to maintain network reliability.

1. Clear statistics about the protection line.


APS Line Protected > G.8031 > Config and then select the Statistics Table of Ethernet

Linear Protection Switching. Select a record and then click Clear Statistic.

2. Clear statistics about the protection ring.


APS Ring Protected > G.8032 > Config and then select the EthRngPrt_Mng_Lnk. Select a

record and then click Clear Statistic.

3. Clear MPLS-TP linear protection switching statistics


Tunnel Protection Group > Tunnel Protection Group. Choose Switch > Clear from the

tool bar of the iTN201 EMS. A tab appears, where you can select a record and then click

Clear Statistic.

Raisecom





11.9.1 Examples for configuring manual link aggregation


As shown in Figure 11-4, 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 Line 1 and Line 2 to a LAG

to form a single logical interface. The LAG performs load-sharing to the source MAC address.

Figure 11-4 Configuring manual link aggregation

Configuration steps

Step 1 Create the manual LAG.

Configure iTN A.



2. Select the record about LAG 1 and then click Modify. A dialog box appears, where you

can configure the mode of the LAG. The following table lists the value of the parameter.


Parameter Value

Aggregation Group Mode Manual



5. Select a record and then click Modify. A dialog box appears, where you can configure

the LAG of the interface. The following table lists values of parameters.


Parameter Value Value

Agg Port Index 1 2

Actor Admin Key 1 1

Raisecom




Configure iTN B.

Configuration steps for iTN B are identical to the ones for iTN A. In this guide, no details are

described.

Step 2 Enable link aggregation and configure the load-sharing mode.

Configure iTN A.


LACP.

2. Select the Trunk Config tab, where you can enable LAG and configure the load-sharing

mode of links. The following table lists values of parameters.


Parameter Value

Link Aggregation Status Enable

Link Aggregation Load Sharing Mode SourceMAC

Configure iTN B.


described.


View global configurations on manual link aggregation, taking iTN A for an example.


LACP. Select the Trunk Config tab to view global configurations on manual link aggregation.

11.9.2 Examples for configuring 1:1 ELPS


As shown in Figure 11-5, to enhance reliability of the link between iTN A and iTN B, you

need to configure 1:1 ELPS on iTN A and iTN B and detect the fault based on the physical

interface status. Line 1 and Line 2 are in VLANs 100–200.

Figure 11-5 Configuring 1:1 ELPS

Configuration steps

Step 1 Creates VLANs 100–200 and add line 1 and line 2 to VLANs 100–200.

Configure iTN A.

Raisecom





VLAN Config.

2. Select the VLAN Static Table tab at the VLAN Config area and then click Add. A dialog

box appears, where you can create VLAN 100. The following table lists the value of the

parameter.


Parameter Value

VLAN ID 100




where you can configure the interface mode and allowed VLANs. The following table





Port Trunk Native Vlan ID 100 100

Configure iTN B.


described.

Step 2 Create 1:1 ELPS working and protection lines.

Configure iTN A.

1. From the Action List of iTN A EMS, choose SNMP Management > APS Protection >

APS Line Protected > G.8031 > Config.

2. Select the Linear Protection Configuration Table and then click Add. A dialog box

appears, where you can create 1:1 ELPS working and protection lines. The following



Parameter Value

Index 1

Working Entity Port 1

Working Block Vlanlist 100

Protection Port 2

Protection Block Vlanlist 100

Configured Protection Group ONE_TO_ONE

Raisecom




Configure iTN B.


described.

Step 3 Configure the fault detection mode.

Configure iTN A.



2. Select the record about the working line and then click Modify. A dialog box appears,

where you can configure the fault detection mode of the working line. The following

table lists the value of the parameter.


Parameter Value

Failure Detect Type Physical Link Check

4. Select the record about the protection line and then click Modify. A dialog box appears,

where you can configure the fault detection mode of the protection line. The following

table lists the value of the parameter.


Parameter Value

Failure Detect Type Physical Link Check

Configure iTN B.


described.

Checking results

View 1:1 ELPS configurations, taking iTN A for an example.

From the Action List of iTN A EMS, choose SNMP Management > APS Protection > APS

Line Protected > G.8031 > Config and then select the Linear Protection Configuration Table

tab. Select a record and then click View to view 1:1 ELPS configurations. Select the Elps

information of the far end tab to view ELPS configurations of the peer.

11.9.3 Examples for configuring single-ring ERPS


As shown in Figure 11-6, to enhance Ethernet reliability, iTN A, iTN B, iTN C, and iTN D

form an ERPS single ring.

iTN A is the RPL Owner and iTN B is the RPL neighbour. The link between iTN A and iTN B

are blocked.

The fault detection mode on all links is set to Physical-Link.

Raisecom




The default value of protocol VLAN is set to 1. Blocked VLAN IDs ranges from 1 to 4094.

Figure 11-6 Configuring single-ring ERPS

Configuration steps

Step 1 Add interfaces to VLANs 1–4094.

Configure iTN A.




where you can configure the interface mode. The following table lists values of

parameters.




Port Trunk Allow Vlan List 1–4094 1–4094

Configure iTN B, iTN C, and iTN D.

Configuration steps for iTN B, iTN C, and iTN D are identical to the ones for iTN A. In this

guide, no details are described.

Step 2 Create the ERPS protection ring.

Configure iTN A.



2. Select the EthRngPrt_Mng_Cfg and then click Add. A dialog box appears, where you

can create the ERPS protection ring. The following table lists values of parameters.

Raisecom





Parameter Value

Ring Id 1

East Port 1

West Port 2

Node Type owner

Rpl Link east

Configure iTN B.

1. From the Action List of iTN B EMS, choose SNMP Management > APS Protection >





Parameter Value

Ring Id 1

East Port 1

West Port 2

Node Type neighbour

Rpl Link west

Configure iTN C.

1. From the Action List of iTN C EMS, choose SNMP Management > APS Protection >





Parameter Value

Ring Id 1

East Port 1

West Port 2

Configure iTN D.

Configuration steps for iTN D are identical to the ones for iTN C. In this guide, no details are

described.

Raisecom




Step 3 Configure the fault detection mode.

Because the iTN201 adopts the default fault detection mode, no configurations are described

in this guide.

Checking results

View ERPS protection ring configurations, taking iTN A for an example.

From the Action List of iTN A EMS, choose SNMP Management > APS Protection > APS

Ring Protected > G.8032 > Config and then select the EthRngPrt_Mng_Cfg tab. Select a

record and then click View to view ERPS protection ring configurations. Select the

EthRngPrt_Mng_Sta tab to view ERPS ring status.

Raisecom


Element Management) 12 Security


12 Security

This chapter describes principles and configuration procedures of security, as well as related


Introduction

Configuring ACL

Configuring RADIUS

Configuring TACACS+

Configuring storm control


12.1 Introduction With continuous development of Internet technology, network is increasingly applied. More

and more enterprises make development with network. How to ensure the data and resource

security becomes a significant problem. In addition, the device performance is reduced or the

device operates improperly in case users access to the network in an unconscious but

aggressive way.

Security technologies, such as Access Control List (ACL) and user authentication, can

improve network and device security effectively.

12.1.1 ACL

To control influence of illegal packets on the network, you need to configure a series of rules

on network devices to decide which packets can be transmitted. There rules are defined

through ACL.

ACL is a series of sequential rules composed by permit | deny sentences. These rules describe

packets based on based on source MAC addresses, destination MAC addresses, source IP

addresses, destination IP addresses, and interface IDs. The device decides packets to be

received or refused based on these rules.

12.1.2 RADIUS

Remote Authentication Dial In User Service (RADIUS) is a standard communication protocol

that provides centralized Authentication, Authorization, and Accounting (AAA) management

for remote users. RADIUS uses the User Datagram Protocol (UDP) as the transport protocol

Raisecom




(port 1812/1813) and has good instantaneity. In addition, RADIUS supports re-transmission

mechanism and backup server mechanism. Therefore, it provides good reliability.

RADIUS works in client/server mode. Network devices are clients of the RADIUS server.

RADIUS server is responsible for receiving users' connection requests, authenticating uses,

and replying configurations required by all clients to provide services for users. This mode

can control users accessing devices and network to improve network security.

Clients and the RADIUS server communicate with each other through the shared key. The

shared key is not transmitted through the network. In addition, any user password needs to be

encapsulated when it is transmitted through clients and RADIUS. This helps prevent getting

the user password by sniffing unsecure network.

12.1.3 TACACS+

Terminal Access Controller Access Control System (TACACS+) is a network access

authentication protocol, similar to RADIUS. Compared with RADIUS, TACACS+ has the

following features:

Use TCP port 49, providing the higher transmission reliability. RADIUS uses a UDP port.

Encapsulate the whole standard TACACS+ packet but for the TACACS+ header,

providing the higher security. RADIUS encapsulates the user password only.

Separate TACACS+ authentication from TACACS+ authorization and TACACS+

accounting, providing a more flexible deployment mode.

Therefore, compared with RADIUS, TACACS+ is more secure and reliable. However, as an

open protocol, RADIUS is more widely-used.

12.1.4 Storm control

In most Layer 2 network scenarios, the unicast traffic should be much greater than the

broadcast traffic. If speed of broadcast and multicast traffic is not limited, when a broadcast

storm is generated, a number of bandwidth will be occupied. Therefore, network performance

is reduced and unicast packets cannot be forwarded. In addition, the communication between

devices may be interrupted.

Configuring storm control on Layer 2 devices can prevent broadcast storm from occurring

when broadcast packets increase sharply in the network. Therefore, this helps ensure that the

unicast packets can be properly forwarded.

Broadcast traffic may exist in following forms, so you need to limit the bandwidth for them

on Layer 2 devices.

Unknown unicast traffic: the unicast traffic whose destination MAC address is not in

MAC address table. It is broadcasted by Layer 2 devices.

Multicast traffic: the traffic whose destination MAC address is a multicast MAC address.

Generally, it is broadcasted by Layer 2 devices.

Broadcast traffic: the traffic whose destination MAC address is a broadcast MAC

address. It is broadcasted by Layer 2 devices.

12.2 Configuring ACL

Raisecom





Scenario

To filter packets, device needs to be configured with ACL to identify packets to be filtered.

Devices cannot allow/disallow related packets to pass based on pre-configured policies unless

they identify specified packets.

ACLs are grouped in to the following types:

IP ACL: make classification rules based on properties of data packets, such as

source/destination IP address carried by the IP header of data packets or used TCP/UDP

port ID.

MAC ACL: make classification rules based on Layer 2 information, such as source MAC

address, destination MAC address, or Layer 2 protocol type carried by the Layer 2 frame

header of data packets.

User ACL: compared with IP ACL and MAC ACL, MAP ACL can define more protocols

and more detailed protocol fields. In addition, it can be used to match any byte in first 64

packets of a Layer 2 data frame based on user's definition.

Based on real scenarios, ACL can be applied based on the whole device, interface, flow from

the ingress interface to the egress interface, or VLAN.

Prerequisite

N/A

12.2.2 Configuring IP ACL


ACL MGT > IP ACL.

Step 2 Click Add. A dialog box appears, where you can configure IP ACL. The following table




Index Configure the index value, which ranges from 0 to 999.

Access Type Select an access type.

Permit: forward packets that match rules. Deny: discard packets that match rules.

Protocol Type Configure the protocol type.

Enter the protocol ID in the IP packet header, which means

filtering packets with specified protocol ID. It ranges from 0 to

255. Select the IP/ICMP/IGMP/TCP/UDP radio button.

Source IP Address Configure the source IP address.

Enter the source IP address, which is in dotted decimal notation. Select the ANY radio button.

Raisecom





Source Address

Mask

Configure the mask of the source IP address, which is in dotted


Source Protocol

Port

Configure the source port ID of TCP/UDP, which ranges from 0 to

65535.

Destination IP

Address

Configure the destination IP address.

Enter the destination IP address, which is in dotted decimal

notation. Select the ANY radio button.

Destination Address

Mask

Configure the mask of the destination IP address, which is in

dotted hexadecimal notation.

Destination Protocol

Port

Configure the destination port ID of TCP/UDP, which ranges from

0 to 65535.

12.2.3 Configuring MAC ACL


ACL MGT > MAC ACL.

Step 2 Click Add. A dialog box appears, where you can configure MAC ACL. The following table







Protocol Type Configure the protocol type.

Enter the protocol identifier of the Ethernet packet, which is in

a format of HHHH. H refers to a hexadecimal digit. Select the ANY/ARP/IP/RARP radio button.

Source Address Configure the source MAC address of the Ethernet packet.

Enter the source MAC address, which is in colon hexadecimal

notation. Select the ANY radio button.

Source Mac Mask Configure the mask of the source MAC address, which is in

colon hexadecimal notation.

Destination Mac

Address

Configure the destination MAC address of the Ethernet packet.

Enter the destination MAC address, which is in colon

hexadecimal notation. Select the ANY radio button.

Raisecom





Destination Mac

Mask

Configure the mask of the destination MAC address, which is in


12.2.4 Configuring User ACL

Configuring matching rules based on source/destination MAC address


ACL MGT > User ACL.

Step 2 Click Add and then select the Level 2 ACL Config tab, where you can configure matching

rules based on the source/destination MAC address. The following table describes items at the

dialog box.






Source Mac Address Configure the source MAC address, which is in colon


Source Mac Mask Configure the mask of the source MAC address, which is in


Destination Mac

Address

Configure the destination MAC address, which is in colon


Destination Mac

Mask

Configure the mask of the destination MAC address, which is in


Configuring CoS-based matching rules


ACL MGT > User ACL.

Step 2 Click Add and then select the Level 2 ACL Config tab, where you can configure CoS-based

matching rules. The following table describes items at the dialog box.




Raisecom







CoS Value Configure the CoS value, which ranges from 0 to 7.

Configuring matching rules based on VLAN IDs of packets


ACL MGT > User ACL.


rules based on VLAN IDs of packets. The following table describes items at the dialog box.






CVLAN ID Configure the CVLAN ID, which ranges from 1 to 4094.

SVLAN ID Configure the SVLAN ID, which ranges from 1 to 4094.

Configuring customized matching rules


ACL MGT > User ACL.

Step 2 Click Add and then select the Level 2 ACL Config tab, where you can configure customized

matching rules. The following table describes items at the dialog box.






Raisecom





Rule String Configure the customized rule character string, which is in hexadecimal

notation. Up to 64 characters are available. This character string is used

as the matching standard.

The rule must even number of hexadecimal digits. The offset includes the 802.1q VALN Tag field, even the received packet is an Untag one.

Rule Mask Configure the customized matching mask.

Use this mask to perform AND operation with the packet and then match

the result with the rule-string. If they are identical, operation succeeds.

Otherwise, operation fails.

Off Set Configure the offset. Based on the packet header, specify the byte where

the AND operation is performed with the rule-string. It ranges from 22 to

63.

The offset includes the 802.1q VALN Tag field, even the received packet is an Untag one.

Configuring matching rules based on TCP port ID


ACL MGT > User ACL.


rules based on the TCP port ID. The following table describes items at the dialog box.






Ether Type Set the Ethernet type to IP.

IP Protocol Type Set the IP type to TCP.

Source Protocol Port Configure the TCP source port ID, which ranges from 0 to

65535.


Port

Configure the TCP destination port ID, which ranges from 0 to

65535.

Raisecom




Configuring matching rules based on TCP flag


ACL MGT > User ACL.


rules based on the TCP flag. The following table describes items at the dialog box.







IP Protocol Type Set the IP type to TCP.

TCP Protocol Flag Select a TCP flag.

ack fin psh rst syn urg

Configuring matching rules based on UDP port ID


ACL MGT > User ACL.


rules based on the UDP port ID. The following table describes items at the dialog box.







IP Protocol Type Set the IP type to UDP.

Source Protocol Port Configure the UDP source port ID, which ranges from 0 to

65535.


Port

Configure the UDP destination port ID, which ranges from 0 to

65535.

Raisecom




Configuring matching rules based on DSCP values of IP packets


ACL MGT > User ACL.

Step 2 Click Add and then select the ACL Config Based on IP tab, where you can configure

matching rules based on DSCP values of IP packets. The following table describes items at

the dialog box.






IP Based Select IP DSCP.

IP DSCP Configure the DSCP value, which ranges from 0 to 63.

Configuring matching rules based on ToS values of IP packets


ACL MGT > User ACL.


matching rules based on ToS values of IP packets. The following table describes items at the

dialog box.






IP Based Select IP ToS.

IP ToS Configure the ToS value, which ranges from 0 to 15 or you can select a

ToS type of IP Packets from the drop-down list.

normal: normal ToS value min-monetary-cost: minimum cost ToS value max-reliability: highest reliability ToS value max-throughput: maximum throughput ToS value min-delay: minimum delay ToS value

Raisecom




Configuring matching rules based on IP precedence


ACL MGT > User ACL.


matching rules based on the IP precedence. The following table describes items at the dialog

box.






IP Based Select IP Precedence.

IP Precedence Select an IP precedence.

routine: be related to priority 0. priority: be related to priority 1. Immediate: be related to priority 2. flash: be related to priority 3. flash-override: be related to priority 4. Critical: be related to priority 5. internet: be related to priority 6. network: be related to priority 7.

12.2.5 Applying ACL

ACL cannot take effect on the iTN201 unless it is added to the filter. Multiple ACL matching rules can be added to the filter to form multiple filtering rules. When you configure a flow-based filter, the sequence to add ACL rules decides their priorities. The later an ACL rule is added, the higher the priority is. If ACL rules are exclusive, the ACL rule with the highest priority takes effect. Therefore, you must arrange their sequence reasonably to filter packets properly.

Applying ACL based on device


ACL MGT > Filter and then select the Filter Action tab, where you can enable the filter.


Step 3 Select the Filter Rule Table tab and then click Add.

Step 4 A dialog box appears, where you can configure applying ACL rules based on the whole

device, as shown below. The following table describes items at the dialog box.


Raisecom





ACL Type Select a matched ACL type.

IP_ACL MAC_ACL User_ACL

ACL Number Click Select to select a matched ACL ID or enter the ACL ID directly.

Applying ACL based on interface





Step 4 A dialog box appears, where you can configure applying ACL rules based on the interface, as

shown below. The following table describes items at the dialog box.


Raisecom








Ingress Port Configure interface list for receiving packets in receiving direction.


The number 0 indicates all interfaces.

Egress Port Configure interface list for receiving packets in forwarding direction.


The number 0 indicates all interfaces.

Applying ACL based on VLAN





Step 4 A dialog box appears, where you can configure applying ACL rules based on the VLAN, as



Raisecom








VLAN Configure the VLAN ID, which is an integer and ranges from 1 to 4094.

Filter packets in this VLAN.

VLAN Type Select the VLAN type.

Inner VLAN Outer VLAN

Filter QinQ packets whole inner VLAN Tag or outer VLAN Tag is set to

this VLAN.

Applying ACL based on Layer 3 interface




Step 3 Select the Layer 3 Filter Table tab and then click Add.

Step 4 A dialog box appears, where you can configure applying ACL rules based on the Layer 3

interface. The following table describes items at the dialog box.



IP Subnet Index Click Select to select an IP subnet.

IP ACL Index Click Select to select the matched IP ACL index, which ranges from

1 to 14.

Filter Port List Configure the filtered interface information.

Configure the interface to be filtered: interfaces 1–24 for the

iTN201-4GF and interfaces 1–22 for the iTN201-2XG. Select the All Ports radio button.



1. View IP ACL configurations.


ACL MGT > IP ACL. Select a record and then click View to view IP ACL configurations.

Raisecom




2. View MAC ACL configurations.


ACL MGT > MAC ACL. Select a record and then click View to view MAC ACL

configurations.

3. View User ACL configurations.


ACL MGT > User ACL. Select a record and then click View to view User ACL

configurations.

4. View configurations on the filter.


ACL MGT > Filter and then select the Filter Rule Table tab. Select a record and then click

View to view configurations on the filter.


ACL MGT > Filter and then select the Layer 3 Filter Table tab. Select a record and then click

View to view configurations on the filter based on Layer 3 interface.

12.3 Configuring RADIUS


Scenario

To control users accessing devices and network, you can deploy the RADIUS server at the

network to authenticate users. The iTN201 can be used as a Proxy of the RADIUS server to

authenticate users based on results returned by the RADIUS server.

Prerequisite

N/A

12.3.2 Configuring RADIUS authentication


User Config.

Step 2 Select the User Config tab, as shown below. The following table describes items at the tab.


Raisecom





Logon Method Select a login mode for users.

Local: user local authentication. Radius: use RADIUS authentication. Try Radius after the Failure of Local: use local

authentication first if both local authentication and RADIUS

authentication co-exist. Try Local after the Failure of Radius: use RADIUS

authentication first if both local authentication and RADIUS

authentication co-exist. Try Local with no response of Radius Server: use local

authentication when the RADIUS server fails to response.

IP Address of RADIUS

Server

Configure the IP address of the RADIUS server, which is in

dotted decimal notation, such as 10.0.0.1.

Radius Authentication

Key

Configure the authentication key of the RADIUS server. Up to

255 characters are available.

Port of Radius Server Configure the interface ID of the RADIUS server. By default,

it is set to 1812.

Backup IP Address of

RADIUS Server

Configure the IP address of the backup RADIUS server, which


Backup Port of Radius

Server

Configure the interface ID of the backup RADIUS server.

Enable Method Select an Enable mode. Values are identical to the ones of

Logon Method.

Raisecom






View RADIUS configurations.


User Config and then select the User Config tab to view RADIUS configurations.

12.4 Configuring TACACS+


Scenario

To control users accessing devices and network, you can deploy the RADIUS server at the

network to authenticate users. Compared with RADIUS, TACACS+ is more secure and

reliable. The iTN201 can be used as a Proxy of the TACACS+ server to authenticate users

based on results returned by the TACACS+ server.

Prerequisite

N/A

12.4.2 Configuring TACACS+ authentication


User Config.

Step 2 Select the User Config tab, as shown below. The following table describes items at the tab.


Raisecom





Logon Method Select a login mode for users.

Local: user local authentication. Tacacs: use TACACS+ authentication. Try Tacacs after the Failure of Local: use TACACS+

authentication if local authentication fails. Try Local after the Failure of Tacacs: use local

authentication if TACACS+ authentication fails. Try Local with no response of Tacacs Server: use local

authentication when the TACACS+ server fails to response.

IP Address of Tacacs

Server

Configure the IP address of the TACACS+ server, which is in


Backup IP Address of

Tacacs Server

Configure the IP address of the backup TACACS+ server,


Tacacs Authentication

Key

Configure the authentication key of the TACACS+ server. Up

to 255 characters are available.

Enable Method Select an Enable mode. Values are identical to the ones of

Logon Method.

12.4.3 Clearing TACACS+ statistics


User Config.

Step 2 Select the Tacacs Statistic tab, where you can clear TACACS+ statistics. The following table


Raisecom






Tacacs Statistic Clear Enable/Disable clearing TACACS+ statistics.

True False

By default, it is set to False.

12.4.4 Viewing TACACS+ statistics


User Config.

Step 2 Select the Tacacs Statistic tab, where you can view TACACS+ statistics. The following table



Tacacs Send Packets Display the number of packets sent by the TACACS+ server.

Tacacs Receive Packets Display the number of packets received by the TACACS+

server.

Tacacs Error Packets Display the number of error packets of the TACACS+ server.



View TACACS+ configurations.


User Config and then select the User Config tab to view TACACS+ configurations.

12.5 Configuring storm control


Scenario

Configuring storm control on Layer 2 devices can prevent broadcast storm from occurring

when broadcast packets increase sharply in the network. Therefore, this helps ensure that the

unicast packets can be properly forwarded.

Broadcast traffic may exist in following forms, so you need to limit the bandwidth for them

on Layer 2 devices.

Unknown unicast traffic: the unicast traffic whose destination MAC address is not in

MAC address table. It is broadcasted by Layer 2 devices.

Raisecom




Multicast traffic: the traffic whose destination MAC address is a multicast MAC address.

Generally, it is broadcasted by Layer 2 devices.

Broadcast traffic: the traffic whose destination MAC address is a broadcast MAC

address. It is broadcasted by Layer 2 devices.

Prerequisite

Before configuring storm control, you need to connect interfaces and configure physical

parameters of interfaces. Make the physical layer Up.

12.5.2 Configuring storm control

Configuring storm control scale


Storm Control.

Step 2 Select the GLOBAL CONFIGURATION tab, where you can configure the storm control

scale. The following table describes items at the tab.



Storm Control

Scale

Configure the storm control scale, which ranges from 2 to 262143 pps.

By default, it is set to 1024 pps.

Configuring storm control on interfaces


Storm Control and then select the PORT CONFIGURATION tab.

Step 2 Select a record and then click Modify. A dialog box appears, where you can enable storm

control on broadcast traffic, multicast traffic, and unknown unicast traffic. The following table




Broadcast Storm Control

Management

Enable/Disable broadcast storm control.

Enable Disable.


Multicast Storm Control

Management

Enable/Disable multicast storm control.

Enable Disable.


Raisecom





DLF Storm Control

Management

Enable/Disable unknown unicast storm control.

Enable Disable.




1. View global configurations of storm control.


Storm Control and then select the GLOBAL CONFIGURATION tab to view storm control

scale configurations.

2. View storm control configurations on an interface.


Storm Control and then select the PORT CONFIGURATION tab. Select a record and then

click View to view storm control configurations on the interface.


12.6.1 Examples for configuring ACL


As shown in Figure 12-1, to control users accessing the server, you can deploy ACL on iTN A

to disallow 192.168.1.1 to access 192.168.1.100.

Figure 12-1 Configuring ACL

Configuration steps

Step 1 Configure IP ACL.


ACL MGT > IP ACL.

2. Click Add. A dialog box appears, where you can configure IP ACL 2. The following


Raisecom





Parameter Value

Index 2

Access Type Deny

Source IP Address 192.168.1.1

Source Address Mask 255.255.255.255

Destination IP Address 192.168.1.100

Destination Address Mask 255.255.255.255

Configuration steps for IP ACL 1 are identical to the ones for IP ACL 2. No details are

described in this guide. The following table lists values of parameters.

Parameter Value

Index 1

Access Type Permit

Source IP Address 0.0.0.0

Source Address Mask 0.0.0.0

Destination IP Address 0.0.0.0

Destination Address Mask 0.0.0.0

Step 2 Apply ACL on interface Client 1 of iTN A.


ACL MGT > Filter.

2. Select the Filter Rule Table tab and then click Add. A dialog box appears, where you can

apply ACL rule 1 on the interface. The following table lists values of parameters.


Parameter Value

ACL Type IP_ACL

ACL Number 1

Ingress Port 5

Configuration steps for ACL rule 2 are identical to the ones for ACL rule 1. No details are

described in this guide. The following table lists values of parameters.

Raisecom




Parameter Value

ACL Type IP_ACL

ACL Number 2

Ingress Port 5


ACL MGT > Filter and then select the Filter Action tab, where you can enable the filter

of iTN A.


Checking results

1. View IP ACL configurations.

From the Action List of iTN A EMS, choose SNMP Management > Advanced MGT > ACL

MGT > IP ACL. Select a record and then click View to view IP ACL configurations.

2. View configurations on the filter.

From the Action List of iTN A EMS, choose SNMP Management > Advanced MGT > ACL

MGT > Filter and then select the Filter Rule Table tab. Select a record and then click View to

view configurations on the filter.

12.6.2 Examples for configuring RADIUS


As shown in Figure 12-2, to control users accessing iTN A, you need to deploy RADIUS

authentication on iTN A to authenticate users logging in to iTN A and record their operations.

Raisecom




Figure 12-2 Configuring RADIUS

Configuration steps

Step 1 From the Action List of iTN A EMS, choose SNMP Management > Advanced MGT >

User Config.

Step 2 Select the User Config tab, where you can configure RADIUS authentication. The following



Parameter Value

Logon Method Radius

IP Address of RADIUS Server 192.168.1.1

Radius Authentication Key raisecom

Checking results

View RADIUS configurations.

From the Action List of iTN A EMS, choose SNMP Management > Advanced MGT > User

Config and then select the User Config tab to view RADIUS configurations.

12.6.3 Examples for configuring TACACS+


As shown in Figure 12-3, to control users accessing iTN A, you need to deploy TACACS+

authentication on iTN A to authenticate users logging in to iTN A.

Raisecom




Figure 12-3 Configuring TACACS+

Configuration steps

Step 1 From the Action List of iTN A EMS, choose SNMP Management > Advanced MGT >

User Config.

Step 2 Select the User Config tab, where you can configure TACACS+ authentication. The



Parameter Value

Logon Method TACACS

IP Address of Tacacs Server 192.168.1.1

Tacacs Authentication Key raisecom

Enable Method TACACS

Checking results

View TACACS+ configurations.

From the Action List of iTN A EMS, choose SNMP Management > Advanced MGT > User

Config and then select the User Config tab to view TACACS+ configurations.

Raisecom




12.6.4 Examples for configuring storm control


As shown in Figure 12-4, 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 set to 2000 pps.

Figure 12-4 Configuring storm control

Configuration steps

Step 1 Enable storm control.


Storm Control and then select the PORT CONFIGURATION tab.

2. Select the record about interface 1 and then click Modify. A dialog box appears, where

you can enable broadcast and unicast storm control. The following table lists values of

parameters.


Parameter Value

Broadcast Storm Control Management Enable

DLF Storm Control Management Enable

Configuration steps for interface 2 are identical to the ones for interface 1. No details are

described in this guide.

Step 2 Configure the storm control scale.


Storm Control.

2. Select the GLOBAL CONFIGURATION tab, where you can configure the storm control

scale. The following table lists the value of the parameter.


Raisecom




Parameter Value

Storm Control Scale 2000

Checking results

View storm control configurations.

From the Action List of iTN AEMS, choose SNMP Management > Advanced MGT >

Storm Control and then select the PORT CONFIGURATION tab. Select a record and then

click View to view storm control configurations on the interface.

Raisecom


Element Management) 13 QoS


13 QoS

This chapter describes principles and configuration procedures of QoS, as well as related


Introduction

Configuring priority trust and priority mapping

Configuring traffic classification and traffic policy

Configuring queue scheduling

Configuring congestion avoidance and queue shaping

Configuring rate limiting based on interface and VLAN

Maintenance


13.1 Introduction Generally, Internet (IPv4), which bases on the storage-and-forward mechanism, only provides

"best-effort" service for users. When the network is overloaded or congested, this service

mechanism cannot ensure to transmit packets timely and completely.

With the ever-growing of network application, users bring different service quality

requirements on network application. Then network should distribute and schedule resources

for different network applications according to users' demands.

Quality of Service (QoS) can ensure real-time and integrated service when network is

overloaded or congested and guarantee that the whole network runs high-efficiently.

QoS consists of a number of traffic management technologies:

Priority trust

Priority mapping

Traffic classification

Traffic policy

Queue scheduling

Congestion avoidance

Queue shaping

Rate limiting based on interface and VLAN

Raisecom




13.1.1 Priority trust

Priority trust refers that a packet adopts its own priority as the classification standard to

perform follow-up QoS management on the packet. In general, the bigger the value is, the

higher the priority is.

The iTN201 supports interface-based priority trust. Priorities are divided into priorities based

on Differentiated Services Code Point (DSCP) of IP packets and priorities based on Class of

Service (CoS) of VLAN packets.

For packets that do not trust their DSCP priorities, the iTN201 supports performing re-

marking on packets based on the interface.

13.1.2 Priority mapping

Priority mapping refers to sending packets to different queues with different local priorities

according to pre-configured mapping relationship between external priority and local priority.

Therefore, packets in different queues can be scheduled on the egress interface.

The local priority refers to an internal priority that is assigned to packets. It is related to the queue number on the egress interface. The bigger the value is, the more quickly the packet is processed.

The iTN201 supports performing priority mapping based on the DSCP priority of IP packets

or the CoS priority of VLAN packets.

By default, the mapping relationship between the iTN201 local priority and DSCP, CoS

priorities is listed in Table 13-1 and Table 13-2.

Table 13-1 Mapping relationship between local priority and DSCP priority

Local 0 1 2 3 4 5 6 7

DSCP 0–7 8–15 16–23 24–31 32–39 40–47 48–55 56–63

Table 13-2 Mapping relationship between local priority and CoS priority

Local 0 1 2 3 4 5 6 7

CoS 0 1 2 3 4 5 6 7

13.1.3 Traffic classification

Traffic classification is a process that recognizes specified packets according to some certain

rule. All resulting packets can be treated differently to differentiate the service implied to

users.

The iTN201 supports classifying traffics based on ToS and DSCP priority of IP packets and

CoS priority of VLAN packets. In addition, it supports classifying traffics based on ACL rules

and VLAN IDs.

Raisecom




ToS priority and DSCP priority

The IP packet header has an 8-bit ToS field. In RFC1349, the first 3 bits of the ToS field

represent the ToS priority, ranging from 0 to 7. In RFC2474, the ToS field is re-defined. The

first 6 bits (0–5 bits) represent the priority of IP packets, which is called DSCP priority,

ranging from 0 to 63. The last 2 bits (6 and 7 bits) are reserved bits.

CoS priority

IEEE802.1Q-based VLAN packets are a modification of Ethernet packets. A 4-byte 802.1Q

header is added between the source MAC address and protocol type. The 802.1Q header

consists a 2-byte Tag Protocol Identifier (TPID, valuing 0x8100) filed and a 2-byte Tag

Control Information (TCI) field.

The first 3 bits of the TCI field represent the CoS priority, which ranges from 0 to 7. CoS

priority is used to ensure service quality in Layer 2 network.

13.1.4 Traffic policy

After performing traffic classification on packets, you need to perform different operations on

packets of different categories. A traffic policy is formed when traffic classifiers are bound to

traffic behaviours.

Rate limiting based on traffic policy

Rate limiting refers to limiting network traffics. Rate limiting is used to control the speed of

traffic in the network. By dropping the traffic that exceeds the speed, you can control the

traffic within a reasonable range. Therefore, network resources and Carrier's benefits are

protected.

The iTN201 supports rate limiting based on traffic policy on the ingress interface.

Re-marking

Re-marking refers to re-configuring some priority fields for some packets, so that devices can

re-classify packets based on their own standards. In addition, downstream nodes can provide

differentiated QoS services depending on re-marking information.

The iTN201 supports performing re-remarking on the following priority fields of packets:

ToS priority of IP packets

DSCP priority of IP packets

CoS priority of VLAN packets

13.1.5 Queue scheduling

Devices need to perform queue scheduling when delay-sensitive services need better QoS

services than non-delay-sensitive services and when the network is congested once in a while.

Queue scheduling adopts different scheduling algorithms to send packets in a queue.

Scheduling algorithms supported by the iTN201 include Strict-Priority (SP), Weight Round

Robin (WRR), Deficit Round Robin (DRR), SP+WRR, and SP+DRR. All scheduling

algorithms are designed for addressing specified traffic problems. And they have different

effects on bandwidth distribution, delay, and jitter.

Raisecom




SP: the device strictly schedules packets in a descending order of priority. Packets with

lower priority cannot be scheduled until packets with higher priority are scheduled.

WRR: on the basis of scheduling packets in a polling manner according to the priority,

the device schedules packets according to the weight of the queue. The queue with

higher priority gets more bandwidth. This ensures the fairness among services with same

priority and indicates weights of services with different priorities.

DRR: on the basis of scheduling packets in a polling manner according to the priority,

the device schedules packets according to the weight of the queue. In addition, during the

scheduling, if one queue has redundant bandwidth, the device will temporarily assign

this bandwidth to another queue. During next scheduling, the assigned schedule will

return equal bandwidth to the original queue.

SP+WRR: a scheduling mode combining the SP scheduling and WRR scheduling. In this

mode, queues on an interface are divided into 2 groups. You can specify the queues

where SP scheduling/WRR scheduling is performed.

SP+DRR: a scheduling mode combining the SP scheduling and DRR scheduling. In this

mode, queues on an interface are divided into 2 groups. You can specify the queues

where SP scheduling/DRR scheduling is performed.

13.1.6 Congestion avoidance

By monitoring utilization of network resources (queues/memory buffer), congestion

avoidance can discard packets actively when congestion occurs or when network traffic

increases. It is a traffic control mechanism that is used to resolve network overload by

adjusting network traffic.

The traditional packet loss policy uses the Tail-Drop mode to process all packets equally

without differentiating class of services. When congestion occurs, packets at the end of a

queue are discarded until congestion is resolved.

This Tail-Drop policy may cause TCP global synchronization. In TCP global synchronization,

packets of multiple TCP connections are discarded, these TCP connections enter congestion

avoidance and slow startup status simultaneously to reduce and adjust traffic. And later these

TCP connections co-occur at some time to result in traffic peak. Therefore, network traffic is

not stable, which influences the link utilization rate.

RED

The Random Early Detection (RED) technology discards packets randomly and makes

multiple TCP connection not reduce transport speed simultaneously to avoid TCP global

synchronization.

The RED algorithm set a minimum threshold and maximum threshold for length of each

queue. In addition:

Packets are not discarded when the queue length is smaller than the minimum threshold.

All received packets are discarded when the queue length is greater than the maximum

threshold.

Packets to be received are discarded randomly when the queue length is between the

minimum and maximum thresholds. Add a random number to the packet to be received

and compare the random number with the drop ratio of the current queue. If the random

number is greater than the drop ration, the packet is discarded. The greater the queue size

is, the higher the packet drop probability is.

Raisecom




WRED

The Weighted Random Early Detection (WRED) technology also discards packets randomly

to avoid TCP global synchronization. However, the random drop parameter generated by

WRED technology is based on the priority. WRED differentiates drop policies through the

color of packets. This helps ensure that high-priority packets have a smaller packet drop

probability.

The iTN201 performs congestion avoidance based on WRED.

13.1.7 Queue shaping

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 traffic shaping on the egress interface of upstream devices to shape upstream traffic.

This helps resolve congestion problem occurs on downstream devices.

Queue shaping is a traffic control technology applied to the interface queues. It can be used to

control speed of all packets in a specified interface queue, buffer packets whose speed

exceeds the threshold, and then forward them when enough bandwidth is available. If the

packet size exceeds the buffer queue size, the packet is discarded.

13.1.8 Rate limiting based on interface and VLAN

Besides rate limiting based on the traffic policy, the iTN201 also supports rate limiting based

on interfaces and VLAN IDs. Similar to rate limiting based on the traffic policy, the iTN201

discards traffic whose speed exceeds the threshold in this 2 modes.

13.2 Configuring priority trust and priority mapping

13.2.1 Preparing for conifgurations

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 re-marking. After configuring priority trust, the iTN201 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 relationship between DSCP

priority and local priority. For VLAN packets, you need to configure the mapping relationship

between CoS priority and local priority.

Prerequisite

Ensure the related interfaces Up.

Raisecom




13.2.2 Configuring priority trust

Enabling QoS globally

Step 1 From the Action List of the iTN201 EMS, choose SNMP Management > QoS MGT > QoS

Base Config.

Step 2 Select the Global QoS Configuration tab, where you can enable QoS globally. By default,

QoS is enabled.


Configuring priorities trusted by an interface


Base Config and then select the Basic QoS Config In Port tab.

Step 2 Select a record and click Modify. A dialog box appears, where you can configure the priority

trusted by the interface. The following table describes items at the dialog box.



The Trust Mode Based On Port Select a trust mode.

Trust_CoS Trust_DSCP

By default, it is set to Trust_CoS.

13.2.3 Configuring DSCP priority re-marking

Creating DSCP re-marking profile


Template Config.

Step 2 From the left side of the QoS Template Config area, choose QoS Template Config > DSCP

ReMark Mapping Template.

Step 3 Choose Edit > Add Qos Template from the menu bar at the right side of the QoS Template

Config area. A dialog box appears, where you can configure the DSCP remarking profile. The




Qos Template Name Configure the name of the DSCP re-marking profile.

Qos Template Desc Configure descriptions of the DSCP re-marking profile.

Right-click a record and then choose Modify from the right-click menu.

Raisecom





NEW DSCP Configure the DSCP priority after re-marking, which ranges

from 0 to 63.

Applying DSCP re-marking profile to an interface



Step 2 Select a record and click Modify. A dialog box appears, where you can apply the DSCP re-

marking profile to the interface. The following table describes items at the dialog box.



Index of Qos Configure

Table On Port

Display the interface ID to which the DSCP re-marking

profile is to be applied.

DSCP Mutation Profile Click Select to select a created DSCP re-marking profile.

13.2.4 Mapping DSCP priority to local priority and color

Creating DSCP-to-local priority (color) mapping profile


Template Config.

Step 2 From the left side of the QoS Template Config area, choose QoS Template Config > DSCP

Mapping Template.


Config area. A dialog box appears, where you can configure the DSCP-to-local priority (color)

mapping profile. The following table describes items at the dialog box.



Qos Template

Name

Configure the name of the DSCP-to-local priority (color) mapping

profile.

Qos Template

Desc

Configure descriptions about the DSCP-to-local priority (color)

mapping profile.


LOCAL

PRIORITY

Configure the local priority to which DSCP priority is mapped. It

ranges from 0 to 7.

Raisecom





COLOR Select the color to which DSCP priority is mapped.

green yellow red

Applying DSCP-to-local priority (color) mapping profile to an interface



Step 2 Select a record and click Modify. A dialog box appears, where you can apply the DSCP-to-

local priority (color) mapping profile to the interface. The following table describes items at

the dialog box.




Table On Port

Display the interface ID to which the DSCP-to-local

priority (color) mapping profile is to be applied.

DSCP Local Priority Profile Click Select to select a created DSCP-to-local priority

(color) mapping profile.

13.2.5 Mapping CoS priority to local priority and color

Creating CoS-to-local priority (color) mapping profile


Template Config.

Step 2 From the left side of the QoS Template Config area, choose QoS Template Config > CoS

Mapping Template.


Config area. A dialog box appears, where you can configure the CoS-to-local priority (color)




Qos Template

Name

Configure the name of the CoS-to-local priority (color) mapping

profile.

Qos Template

Desc

Configure descriptions about the CoS-to-local priority (color)

mapping profile.


Raisecom





LOCAL

PRIORITY

Configure the local priority to which CoS priority is mapped. It

ranges from 0 to 7.

COLOR Select the color to which CoS priority is mapped.

green yellow red

Applying CoS-to-local priority (color) mapping profile to an interface



Step 2 Select a record and click Modify. A dialog box appears, where you can apply the CoS-to-

local priority (color) mapping profile to the interface. The following table describes items at

the dialog box.




Table On Port

Display the interface ID to which the CoS-to-local priority

(color) mapping profile is to be applied.

CoS Local Priority Profile Click Select to select a created CoS-to-local priority


13.2.6 Mapping local priority to CoS priority

Creating local-to-CoS priority (color) mapping profile


Template Config.

Step 2 From the left side of the QoS Template Config area, choose QoS Template Config > CoS

ReMark Mapping Template.


Config area. A dialog box appears, where you can configure the local-to-CoS priority (color)




Qos Template

Name

Configure the name of the local-to-CoS priority (color) mapping

profile.

Qos Template

Desc

Configure descriptions about the local-to-CoS priority (color) mapping

profile.

Raisecom






NEW COS Configure the COS priority after re-marking, which ranges from 0 to 7.

Applying local-to-CoS priority (color) mapping profile to an interface



Step 2 Select a record and click Modify. A dialog box appears, where you can apply the local-to-

CoS priority (color) mapping profile to the interface. The following table describes items at

the dialog box.




Table On Port

Display the interface ID to which the local-to-CoS priority

(color) mapping profile is to be applied.

CoS Remark Profile Click Select to select a created local-to-CoS priority




1. View priority trust configurations on an interface.

From the Action List of the iTN201 EMS, choose SNMP Management > QoS MGT > QoS

Base Config and then select the Basic QoS Config In Port tab. Select a record and then click

View to view priority trust configurations on the interface.

2. View information about the DSCP re-marking profile.


Template Config. From the left side of the QoS Template Config area, choose QoS Template

Config > DSCP ReMark Mapping Template to view information about the DSCP re-

marking profile.

3. View information abou the DSCP-to-local priority (color) mapping profile.



Config > DSCP Mapping Template to view information about the DSCP-to-local priority


4. View information abou the CoS-to-local priority (color) mapping profile.



Config > CoS Mapping Template to view information about the CoS-to-local priority (color)

mapping profile.

Raisecom




5. View information abou the local-to-CoS priority (color) mapping profile.



Config > CoS ReMark Mapping Template to view information about the local-to-CoS

priority (color) mapping profile.

6. View the mapping profile applied to an interface.


Base Config and then select the Basic QoS Config In Port tab. Select a record and then click

View to view the mapping profile applied to the interface.

13.3 Configuring traffic classification and traffic policy


Scenario

Traffic classification is the basis of QoS. For packets from upstream devices, you can classify

them according to their priorities or 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 re-mark the packet according to the service feature.

Prerequisite

To perform traffic classification based on the priority of packets, you need to configure

priority trust.

13.3.2 Creating and configuring traffic classification

Creating traffic classification


Policy Config and then select the QoS Class Map Configuration Table tab.

Step 2 Click Add and a dialog box appears, where you can create traffic classification, as shown

below. The following table describes items at the dialog box.


Raisecom





Class Map Name Configure the traffic classification name, which ranges from 1 to 16

characters.

Class Map

Description

Configure the traffic classification description, which ranges from 1 to

255 characters.

Class Map Type Select a traffic classification type.

MatchAll: match all defined classification rules. MatchAny: match one or more defined classification rules.

(Optional) configuring traffic classification rules


Policy Config and then select the QoS Match Statement Table tab.

Step 2 Click Add and a dialog box appears, where you can configure traffic classification rules. The




Class Map Name Click Select to select a created traffic classification name.

Match Statement

Type

Select a traffic classification matching rule.

IP ACL: use the created IP ACL to classify packets. MAC ACL: use the created MAC ACL to classify packets. Access List Map: use the created MAP ACL to classify packets. IP DSCP: use the DSCP priority to classify packets. IP Precedence: use the IP precedence to classify packets. Class-map: use traffic classification to classify packets. Vlan: use the VLAN ID to classify packets. Vlan-inner: use the inner VLAN ID to classify packets. CoS: use the CoS priority to classify packets. Inner Outer Vlan: use the inner/outer VLAN ID to classify

packets. Label: use the label to classify packets. EXP: use the EXP priority to classify packets. Second Label: use the second label to classify packets. VC-EXP: use the VC-EXP priority to classify packets.

Raisecom





Match Value Select the traffic classification matching rule ID based on the

selected Match Statement Type.

IP ACL: select a created IP ACL ID. MAC ACL: select a created MAC ACL ID. Access List Map: select a created MAP ACL ID. IP DSCP: enter a DSCP value, which ranges from 0 to 63. IP Precedence: enter an IP precedence, which ranges from 0 to 7. Class-map: select a created traffic classification ID. Vlan: enter a VLAN ID. Vlan-inner: enter an inner VLAN ID. CoS: enter a CoS value, which ranges from 0 to 7. Inner Outer Vlan: enter an inner/outer VLAN ID. Label: enter a label value, which ranges from 16 to 1048575. EXP: enter an EXP priority, which ranges from 0 to 7. Second Label: enter a second label value, which ranges from 16 to

1048575. VC-EXP: enter a VC-EXP priority, which ranges from 0 to 7.

13.3.3 Creating and configuring traffic policing profile

To perform traffic policing on packets, you need to configure traffic policing profile and refer

to this profile in traffic classification bound to traffic policy.

On the traffic policing profile, you can configure rate limiting rules or perform relate

operations on specified packets based on the color.


Template Config.

Step 2 From the left side of the QoS Template Config area, choose QoS Template Config > FLOW

Template.


Config area. A dialog box appears, where you can configure the traffic policing profile. The




Base Info

TEMPLATE NAME Configure the traffic policing profile name.

POLICER NAME Configure the traffic policy name.

POLICER TYPE Select a traffic policy.

single flow: set the token bucket mode to single traffic

policing. class flow: set the token bucket mode to class traffic policing. aggregate flow: set the token bucket mode to aggregation

traffic policing.

Raisecom





POLICER MODE Select a token bucket.

flow: the token bucket is a single one, supporting red and

yellow packet actions. rfc2697: the token bucket is a double one. rfc2698: the token bucket is a double one. rfc4115: the token bucket is a double one. mef: the token bucket is a double one.

POLICER CIR

(Kbps)

Configure the CIR, which is an integer and ranges from 0 to

1048576 Kbit/s.

POLICER EIR/PIR

(Kbps)

Configure the Extended Information Rate (EIR), which is an

integer and ranges from 0 to 1048576 Kbit/s.

POLICER CBS

(Kbytes)

Configure the Committed Burst Size (CBS), which is an integer

and ranges from 0 to 16384 KB.

POLICER EBS/PBS

(Kbytes)

Configure the Extended Burst Size (EBS), which is an integer

and ranges from 0 to 16384 KB.

POLICER COLOR

MODE

Select a color-mode of the token bucket.

color blind color aware

If the token bucket is referred to, you cannot set its color-mode.

TEMPLATE DESC Configure the description about the traffic policing profile.

Red

Action Type Select an action to be performed on red packets.

drop other

Remark DSCP Select a marked DSCP priority, which ranges from 0 to 63.

This parameter is available when the Action Type is set to other.

Remark COS Select a marked CoS priority, which ranges from 0 to 7.


Remark Local Priority Select a marked local priority, which ranges from 0 to 7.


Remark Color Select the marked color.

yellow green


yellow

Raisecom





Action Type Select an action to be performed on yellow packets.

drop other








red green


green

Action Type Select an action to be performed on green packets.

drop other








yellow red


13.3.4 Creating and configuring traffic policy

Enabling traffic policy


Base Config.

Step 2 Select the Global QoS Configuration tab, where you can enable traffic policy. By default,

traffic policy is disabled.


Raisecom




Creating traffic policy


Policy Config and then select the QoS Policy Map Configuration Table tab.

Step 2 Click Add and a dialog box appears, where you can create a traffic policy. The following




Policy Map Name Configure the traffic policy name, which ranges from 1 to 16

characters.

Policy Map

Description

Configure the traffic policy description, which ranges from 1 to 255

characters.

Policy Map Type Set the Policy Map Type to policy-map.

Configuring traffic policy


Policy Config and then select the QoS Action Configuration Table tab.

Step 2 Click Add and a dialog box appears, where you can configure the traffic policy. The




Policy Map Name Click Select to select a created Policy Map.

Class Map Name Click Select to select a created Class Map.

Policer Name Click Select to select a created traffic policing profile.

Statistics Enable Enable/Disable the statistics feature.

Enable Disable

Rewrited VLAN ID Rewrite the VLAN ID, which ranges from 1 to 4094.

Inner VLAN

Rewrite

Rewrite the inner VLAN ID, which ranges from 1 to 4094.

Outer VLAN to

Add

Rewrite the outer VLAN ID, which ranges from 1 to 4094.

Copy to the Mirror-

to Port

Select whether to copy traffic to the mirroring port.

Enable Disable

Raisecom





Redirect Port Click Select to select a re-direction interface.

This parameter is available only when the Copy to the Mirror-to Port is set to Disable.

Rewrite Local

Priority

Rewrite the local priority, which ranges from 0 to 7.

Hierarchy Police

Name

Click Select to select a created hierarchical traffic policing profile.

Rewrite IP

Precedence

Rewrite the IP precedence, which ranges from 0 to 7.

Rewrite DSCP Rewrite the DSCP priority, which ranges from 0 to 63.

Rewrite COS Rewrite the CoS priority, which ranges from 0 to 7.

Binding configured traffic policy to egress interface


Policy Config and then select the QoS Service Egress Policy Table tab.

Step 2 Click Add and a dialog box appears, where you can bind a configured traffic policy to the

egress interface. The following table describes items at the dialog box.



QoS Service Egress Policy Table Index Click Select to select an egress interface ID.

Policy Map Name Click Select to select a Policy Map.

Binding configured traffic policy to ingress interface


Policy Config and then select the QoS Service Policy Table tab.

Step 2 Click Add and a dialog box appears, where you can bind a configured traffic policy to the

ingress interface. The following table describes items at the dialog box.



Ingress Port Click Select to select an ingress interface ID.

Policy Map Name Click Select to select a Policy Map.

Raisecom






1. View traffic classification information.


Policy Config and then select the QoS Class Map Configuration Table tab. Select a record

and then click View to view traffic classification information.

2. View traffic policy information.


Policy Config and then select the QoS Policy Map Configuration Table tab. Select a record

and then click View to view traffic policy information.

3. View information about traffic classification in traffic policy.


Policy Config and then select the QoS Action Configuration Table tab. Select a record and

then click View to view information about traffic classification in traffic policy.

13.4 Configuring queue scheduling


Scenario

When congestion occurs, you need to balance delay and jitter of packets, making packets of

core services, such as video and voice services, processed first while packets of non-core

services of the same priority, such as email, processed in a fair manner. Therefore, services of

different priorities are processed according to the weights. This can be realized by configuring

queue scheduling. The selection of scheduling algorithm depends on service types and users'

requirements.

After queue scheduling, you can configure the mapping relationship between local priority

and CoS priority of packets. Therefore, packets enter downstream devices by carrying the

specified CoS priority.

Prerequisite

To configure local priority and queue scheduling, you need to configure priority trust.

13.4.2 Configuring queue scheduling modes on interfaces



Step 2 Select a record and click Modify. A dialog box appears, where you can configure queue

scheduling modes for the interface. The following table describes items at the dialog box.


Raisecom





The Scheduler Mode Based On Port Select a queue scheduling mode.

SP WRR DRR

13.4.3 Configuring WRR/DRR queue scheduling


Base Config and then select the Scheduler Table on Port tab.

Step 2 Select a record and click Modify. A dialog box appears, where you can WRR/DRR queue

scheduling. The following table describes items at the dialog box.



Physical ports Display the interface ID.

Index of Scheduler

Table On Port

Display the queue ID.

WRR Configure the WRR weight value, which ranges from 0 to 127. The

number 0 indicates SP queue scheduling.

DRR Configure the DRR weight value, which ranges from 0 to 127. The

number 0 indicates SP queue scheduling.



View queue weight values on an interface.


Base Config and then select the Scheduler Table on Port tab. Select a record and then click

View to view queue weight values on the interface.

13.5 Configuring congestion avoidance and queue shaping


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 iTN201 supports WRED-based congestion avoidance.

Raisecom




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 traffic shaping on the egress interface of upstream devices to shape upstream traffic.

Prerequisite

N/A

13.5.2 Configuring queue-based WRED

Enabling global WRED


Base Config.

Step 2 Select the Global QoS Configuration tab, where you can enable WRED globally. By default,

WRED is disabled.


Creating WRED profile

Generally, the drop probability, begin-drop threshold, and fully-drop threshold are configured as below: Drop probability: green packets < yellow packets < red packets Begin-drop threshold and fully-drop threshold: green packets > yellow packets >

red packets.


Template Config.

Step 2 From the left side of the QoS Template Config area, choose QoS Template Config > WRED

Template.


Config area. A dialog box appears, where you can configure the WRED profile. The




Qos Template Name Configure the name of the WRED profile.

Qos Template Desc Configure descriptions of the WRED profile.

green

START DISCARD

THRESHOLD

Configure the begin-drop threshold of green packets, which


MAX DISCARD

THRESHOLD

Configure the fully-drop threshold of green packets, which


Raisecom





MAX DISCARD

PROBABILITY

Configure the maximum drop probability of green packets,


yellow

START DISCARD

THRESHOLD

Configure the begin-drop threshold of yellow packets,


MAX DISCARD

THRESHOLD

Configure the fully-drop threshold of yellow packets, which


MAX DISCARD

PROBABILITY

Configure the maximum drop probability of yellow packets,


Red

START DISCARD

THRESHOLD

Configure the begin-drop threshold of red packets, which


MAX DISCARD

THRESHOLD

Configure the fully-drop threshold of red packets, which


MAX DISCARD

PROBABILITY

Configure the maximum drop probability of red packets,


Applying WRED profile to an interface


Base Config and then select the Wred Profile Applied on Port tab.

Step 2 Click Add and a dialog box appears, where you can apply the WRED profile to an interface.




Port Click Select to select an interface ID.

Queue Id Enter the queue ID, which ranges from 1 to 8.

Profile Index Click Select to select a created WRED profile.

13.5.3 Configuring queue shaping


Base Config and then select the Basic QoS Queue Bandwidth Config In Port tab.

Step 2 Select a record and click Modify. A dialog appears, where you can configure queue shaping.



Raisecom





CIR Configure the CIR, which ranges from 0 to 1048576 Kbit/s.

CBS Configure the CBS, which ranges from 0 to 16384 KB.

EIR Configure the EIR, which ranges from 0 to 1048576 Kbit/s.

EBS Configure the EBS, which ranges from 0 to 16384 KB.

BandWidth Limit Enable/Disable rate limiting.

Enable Disable




1. View WRED profile configurations.



Config > WRED Template to view WRED profile configurations.

2. View queue shaping configurations.


Base Config and then select the Basic QoS Queue Bandwidth Config In Port tab. Select a

record and then click View to view queue shaping configurations.

13.6 Configuring rate limiting based on interface and VLAN


Scenario

To avoid/remit network congestion, you can configure interface-based, VLAN-based rate

limiting, or rate limiting based on interface and VLAN. Rate limiting is used to make packets

transmitted at a relative average speed by control the burst traffic on an interface or in a

VLAN.

Prerequisite To configure VLAN-/QinQ-based rate limiting, you need to create related VLANs.

To configure rate limiting based on interface and VLAN, you need to enable PerfMonitor

at the NView NNM Control

Raisecom




13.6.2 Configuring interface-based rate limiting


List and then select the Rate Limit Port Table tab.

Step 2 Select a record and click Modify. A dialog box appears, where you can configure interface-

based rate limiting. The following table describes items at the dialog box.



Ingress Rate Configure the uplink bandwidth, which ranges from 64 to 1000000

Kbit/s. By default, it is set to 1000000 Kbit/s.

Ingress Burst Configure the uplink burst value, which ranges from 1 to 16384 KB. By

default, it is set to 512 KB.

Egress Rate Configure the downlink bandwidth, which ranges from 64 to 1000000

Kbit/s. By default, it is set to 1000000 Kbit/s.

Egress Burst Configure the downlink burst value, which ranges from 1 to 16384 KB.

By default, it is set to 512 KB.

13.6.3 Configuring VLAN-based/QinQ-based rate limiting


List and then select the Rate Limit VLAN Table tab.

Step 2 Click Add and a dialog box appears, where you can configure VLAN-based/QinQ-based rate

limiting. The following table describes items at the dialog box.



VLAN Type Select a VLAN type for rate limiting.

single double

Customer

VLAN ID

Configure the customer VLAN ID.

Enter a CVALN ID, which ranges from 1 to 4094. Select the ANY radio button.

Service

Provider

VLAN ID

Configure the SVLAN ID.

Enter a SVALN ID, which ranges from 1 to 4094. Select the ANY radio button.

This parameter is available when the VLAN Type is set to double.

Rate Configure the bandwidth, which ranges from 64 to 1000000 Kbit/s.

Burst Configure the burst value, which ranges from 1 to 16384 KB.

Statistic Switch Enable/Disable the VLAN bandwidth statistics switch.

Enable Disable

Raisecom




13.6.4 Configuring rate limiting based on interface and VLAN

Configuring rate limiting test task based on interface and VLAN


Performance Test > Rate Limit.

Step 2 Right-click the blank area and then choose Add from the right-click menu.

Step 3 A dialog box appears, where you can configure a rate limiting test task based on interface and

VLAN. The following table describes items at the dialog box.



Base Info

Friendly Name Configure the service name, which ranges from 0 to 100 characters.

Port Click to select an interface.

VLAN Configure the VLAN ID, which ranges from 1 to 4094.

Rate Limit

Enable

Enable/Disable rate statistics.

Enable Disable

Ingress Traffic Limit

Ingress Rate

Limit

Enable/Disable rate limiting on the ingress interface.

Enable Disable

Parameters of Ingress cir, Ingress cbs, and Ingress ebs are unavailable unless rate limiting on ingress interface is enabled.

Ingress cir (kbps) Configure the CIR on the ingress interface, which ranges from 8 to

1048576 Kbit/s.

Ingress cbs (kB) Configure the CBS on the ingress interface, which ranges from 1 to

16384 KB.

Ingress eir (kbps) Configure the EIR on the ingress interface, which ranges from 8 to

1048576 Kbit/s.

Ingress ebs (kB) Configure the EBS on the ingress interface, which ranges from 1 to

16384 KB.

Egress Traffic Limit

Raisecom





Egress Rate

Limit

Enable/Disable rate limiting on the egress interface.

Enable Disable

Parameters of Egress cir, Egress cbs, and Egress ebs are unavailable unless rate limiting on egress interface is enabled.

Egress cir (kbps) Configure the CIR on the egress interface, which ranges from 8 to

1048576 Kbit/s.

Egress cbs (kB) Configure the CBS on the egress interface, which ranges from 1 to

16384 KB.

Egress eir (kbps) Configure the EIR on the egress interface, which ranges from 8 to

1048576 Kbit/s.

Egress ebs (kB) Configure the EBS on the egress interface, which ranges from 1 to

16384 KB.

Enabling performance detection



Step 2 Right-click a record and then choose Performance > Start Check. A dialog box appears,

where you can configure a single task.


For details about how to configure a single task, see section 17.4.2 Configuring single task.

Viewing performance statistics



Step 2 Right-click a record and then choose Performance > Show Performance. A dialog box

appears, where you can select resources to be collected. And then click the History PM

Chart/Real Time PM Chart tab.

Step 3 Select a metric group and related performance statistics chart is displayed at the right side.



1. View configurations on interface-based rate limiting.

Raisecom





List and then select the Rate Limit Port Table tab. Select a record and then click View to view

configurations on interface-based rate limiting.

2. View configurations on VLAN-/QinQ-based rate limiting.


List and then select the Rate Limit VLAN Table tab. Select a record and then click View to

view configurations on VLAN-/QinQ-based rate limiting.

3. View configurations on rate limiting based on interface and VLAN.


Performance Test > Rate Limit. Right-click a record and then choose Property from the

right-click menu to view configurations on rate limiting based on interface and VLAN.

13.7 Maintenance Perform the following operations on the iTN201 to maintain QoS.

Clear QoS packet statistics.


Statistics. Select a record and then click Clear Statistics to clear QoS packet statistics of the

interface.


13.8.1 Examples for configuring rate limiting based on traffic policy


As shown in Figure 13-1, User A, User B, and User C are respectively within VLAN 1,

VLAN 2, and VLAN 3. And they are respectively connected to the iTN201 through Switch A,

Switch B, and Switch C.

User A transmits voice and video services; User B transmits voice, video, and data services;

User C transmits video and data services.

According to users' requirements, make following rules:

For User A, provide 25 Mbit/s bandwidth; set the burst traffic to 100 Kbit/s and discard

the redundant traffic.

For User B, provide 35 Mbit/s bandwidth; set the burst traffic to 100 Kbit/s and discard


For User C, provide 30 Mbit/s bandwidth; set the burst traffic to 100 Kbit/s and discard


Raisecom




Figure 13-1 Configuring rate limiting based on traffic policy

Configuration steps

Step 1 Enable QoS globally.

1. From the Action List of the iTN EMS, choose SNMP Management > QoS MGT > QoS

Base Config.

2. Select the Global QoS Configuration tab, where you can enable QoS globally.


Step 2 Create traffic classification.


Policy Config and then select the QoS Class Map Configuration Table tab.

2. Click Add and a dialog box appears, where you can create traffic classification. The



Parameter Value Value Value

Class Map Name usera userb userc

Class Map Type MatchAny MatchAny MatchAny

Step 3 Classify users based on the VLAN ID.


Policy Config and then select the QoS Match Statement Table tab.

2. Click Add and a dialog box appears, where you can configure the traffic classification

rule. The following table lists values of parameters.


Raisecom





Class Map Name usera userb userc

Match Statement Type Vlan Vlan Vlan

Match Value 1 2 3

Step 4 Create the traffic policing profile and configure rate limiting rules.


Template Config.

2. From the left side of the QoS Template Config area, choose QoS Template Config >

FLOW Template.

3. Choose Edit > Add Qos Template from the menu bar at the right side of the QoS

Template Config area. A dialog box appears, where you can configure the traffic

policing profile. The following table lists values of parameters.



POLICER NAME usera userb userc

POLICER TYPE single flow single flow single flow

POLICER CIR (Kbps) 25000 35000 30000

POLICER CBS (Kbytes) 100 100 100

Step 5 Create the traffic policy.


Policy Config and then select the QoS Policy Map Configuration Table tab.

2. Click Add and a dialog box appears, where you can create a traffic policy. The following




Policy Map Name usera userb userc

Policy Map Description usera userb userc

Policy Map Type policy-map policy-map policy-map

Step 6 Configure the traffic policy.


Policy Config and then select the QoS Action Configuration Table tab.

2. Click Add and a dialog box appears, where you can configure a traffic policy. The



Raisecom






Policy Map Description usera userb userc

Policy Map Type policy-map policy-map policy-map

Step 7 Apply the traffic policy to interfaces.


Policy Config and then select the QoS Service Policy Table tab.

2. Click Add and a dialog box appears, where you can apply a configured traffic policy to

the ingress interface. The following table lists values of parameters.


Ingress Port Client1 Client2 Client3


Checking results

1. View traffic classification configurations.

From the Action List of the iTN EMS, choose SNMP Management > QoS MGT > QoS

Policy Config and then select the QoS Class Map Configuration Table tab. Select a record

and then click View to view traffic classification configurations.

2. View configurations on rate limiting rules.



Config > FLOW Template to view configurations on rate limiting rules.

3. View traffic policy configurations.


Policy Config and then select the QoS Policy Map Configuration Table tab. Select a record

and then click View to view traffic policy configurations.

13.8.2 Examples for configuring queue scheduling and congestion avoidance


As shown in Figure 13-2, User A transmits voice and video services; User B transmits voice,

video, and data services; User C transmits video and data services.

CoS priorities for voice, video and data services are configured with 5, 4, and 2 respectively.

And these three CoS priorities are mapped to local priorities 6, 5, and 2 respectively.

Make following rules based on service types.

Raisecom




Perform SP scheduling on voice service to ensure that the traffic is first transmitted.

Perform WRR scheduling on video service and set the weight to 50.

Perform WRR scheduling on data service and set the weight to 20. In addition, you need

to set the drop threshold to 50 to avoid network congestion caused by too large burst

traffic.

Figure 13-2 Configuring queue scheduling

Configuration steps

Step 1 Enable WRED globally.


Base Config.

2. Select the Global QoS Configuration tab, where you can enable WRED globally.


Step 2 Create and configure the WRED profile.


Template Config.


WRED Template.


Template Config area. A dialog box appears, where you can configure the WRED profile.



Parameter Value

Qos Template Name 1

Qos Template Desc Profile1

Raisecom




Parameter Value

green

START DISCARD THRESHOLD 50

MAX DISCARD THRESHOLD 90

MAX DISCARD PROBABILITY 60

yellow




Red




Step 3 Enable QoS globally.


Base Config.

2. Select the Global QoS Configuration tab, where you can enable QoS globally.


Step 4 Configure priority trust.



2. Select a record and click Modify. A dialog box appears, where you can configure the

priority trusted by the interface. The following table lists values of parameters.



Index of Qos Configure Table On Port Client1 Client2 Client3

The Trust Mode Based On Port Trust-CoS Trust-CoS Trust-CoS

Step 5 Configure congestion avoidance.


Base Config and then select the Wred Profile Applied on Port tab.

2. Click Add and a dialog box appears, where you can apply the WRED profile to an



Raisecom





Port Client1 Client2 Client3

Queue Id 6 5 2 6 5 2 6 5 2

Profile Index 1 1 1

Step 6 Create a CoS-to-local priority mapping profile.


Template Config.


CoS Mapping Template.


Template Config area. A dialog box appears, where you can configure the CoS-to-local

priority (color) mapping profile. The following table lists values of parameters.



Qos Template Name 1

Qos Template Desc cos-to-local-priority1

CoS 5 4 2

LOCAL PRIORITY 6 5 2

Step 7 Apply the CoS-to-local priority mapping profile to an interface.



2. Select a record and click Modify. A dialog box appears, where you can apply the CoS-

to-local priority (color) mapping profile to the interface. The following table lists values

of parameters.




CoS Local Priority Profile 1 1 1

Step 8 Configure SP+WRR queue scheduling.



2. Select a record and click Modify. A dialog box appears, where you can configure queue

scheduling modes for the interface. The following table lists values of parameters.


Raisecom






The Scheduler Mode Based On Port WRR WRR WRR

Step 9 Configure the queue scheduling weight.


Base Config and then select the Scheduler Table on Port tab.

2. Select a record and click Modify. A dialog box appears, where you can WRR/DRR

queue scheduling. The following table lists values of parameters.


Parameter Value Value Value Value Value Value

Value

Value

Physical ports Client1/Client2/Client3

Index of

Scheduler

Table On Port

1 2 3 4 5 6 7 8

WRR 1 1 20 1 1 50 0 0

Checking results

1. View mapping relationship configurations of a specified priority.



Config > CoS Mapping Template to view mapping relationship configurations of a specified

priority.

2. View queue scheduling configurations.


Base Config and then select the Scheduler Table on Port tab. Select a record and then click

View to view queue scheduling configurations.

3. View WRED profile configurations.



Config > WRED Template to view WRED profile configurations.

13.8.3 Examples for configuring interface-based rate limiting


As shown in Figure 13-3, User A, User B, and User C are connected to the iTN201 through

Switch A, Switch B, and Switch C.

Raisecom




User A transmits voice and video services; User B transmits voice, video, and data services;

User C transmits video and data services.

According to users' requirements, make following rules:

For User A, provide 25 Mbit/s bandwidth; set the burst traffic to 100 Kbit/s and discard


For User B, provide 35 Mbit/s bandwidth; set the burst traffic to 100 Kbit/s and discard


For User C, provide 30 Mbit/s bandwidth; set the burst traffic to 100 Kbit/s and discard


Figure 13-3 Configuring interface-based rate limiting

Configuration steps

Step 1 From the Action List of the iTN EMS, choose SNMP Management > Port MGT > Port

List and then select the Rate Limit Port Table tab.

Step 2 Select a record and click Modify. A dialog box appears, where you can configure interface-

based rate limiting. The following table lists values of parameters.



Port Client1 Client2 Client3

Ingress Rate 25000 35000 30000

Ingress Burst 100 100 100

Checking results

View configurations on interface-based rate limiting.

Raisecom




From the Action List of the iTN EMS, choose SNMP Management > Port MGT > Port List

and then select the Rate Limit Port Table tab. Select a record and then click View to view

configurations on interface-based rate limiting.

Raisecom


Element Management) 14 System management and maintenance


14 System management and maintenance

This chapter describes principles and configuration procedures of system management and

maintenance, as well as related configuration examples, including following sections:

Introduction

Configuring SNMP

Configuring routing

Configuring RMON

Configuring LLDP

Configuring optical module DDM

Configuring system log

Configuring loopback test

Configuring alarm management

Configuring CPU protection

Configuring CPU monitoring

Configuring remote management

Maintenance


14.1 Introduction

14.1.1 SNMP

Simple Network Management Protocol (SNMP) is designed by the Internet Engineering Task

Force (IETF) to resolve problems in managing network devices connected to the Internet.

Through SNMP, a network management system 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.

Raisecom




14.1.2 Routing

To communicate with devices in indirectly-connected network segment, the device should use

the routing feature.

The routing is used to select a path and forward packets. The routing is realized through

routing protocols. Routing protocols are rules to main the routing table between devices. It is

used to discover routes, generate the routing table, and instruct packet forwarding.

The routing feature is performed in the following 3 modes:

Default route

Static routing

Dynamic routing

At present, the iTN201 supports default route and static routing only.

Static routing refers to a type of routing that is manually configured. It has fewer requirements

on the system. The static routing is mainly applied to small-and medium network. However,

the static routing cannot automatically adapt to the network topology changes.

14.1.3 RMON

Remote Network Monitoring (RMON) is a standard developed by the Internet Engineering

Task Force (IETF). RMON is used to monitor network data through different Agents and

NMS. RMON is an extension of SNMP. However, compared with SNMP, ROMN is more

active and efficient for monitoring remote devices. The administrator can quickly trace faults

generated on the network, network segments or devices.

At present, RMON realizes 4 function groups:

Statistics group: collect statistic information on each interface, including number of

received packets and packet size distribution statistics.

History group: similar with the statistics group, but it only collect statistic information in

an assigned detection period.

Alarm group: monitor an assigned MIB object, set 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, etc.

14.1.4 LLDP

Link Layer Discovery Protocol (LLDP) is based on IEEE 802.1ab standard. Network

management system can fast grip the Layer 2 network topology and changes.

LLDP organizes the local device information in different Type Length Value (TLV) and

encapsulates in Link Layer Discovery Protocol Data Unit (LLDPDU) to transmit to straight-

connected neighbour. It also saves the information from neighbour as standard Management

Information Base (MIB) for network management system querying and judging link

communication.

14.1.5 Optical module DDM

Small Form-factor Pluggables (SFP) is an optical module in optical module transceivers. The

SFP Digital Diagnostic Monitoring (DDM) provides a method for monitoring performance.

Raisecom




By analyzing monitored data provided by the SFP module, the administrator can predict the

lifetime of the SFP module, isolate system faults, as well as verify the compatibility of the

SFP module.

The SFP module offers 5 performance parameters:

Temperature for the transceiver

Internal Power Feeding Voltage (PFV)

Launched bias current

Launched optical power

Received optical power

14.1.6 System log

The system log refers that the device records the system information and debugging

information in a log and sends the log to the specified destination. When the device fails to

work, you can check and locate the fault easily.

The system information and some scheduling output will be sent to the system log to deal

with. According to the configuration, the system will send the log to various destinations. The

destinations that receive the system log are divided into:

Console: send the log message to the local console through Console interface.

Host: send the log message to the host.

Monitor: send the log message to the monitor.

Flash: send the log file to the Flash of the device.

14.1.7 Loopback test

As shown in Figure 14-1, interface loopback test is a common method for checking interface

and network problems. Return the packets, which meet rules and related parameters defined

by users, to the iTN B through Client 1 of iTN A. By counting packets transmitted and

received by an interface, iTN B can detect the network connectivity.

Figure 14-1 Interface loopback

14.1.8 Alarm management

An alarm refers to information generated by the system based on module failures when a fault

is generated on the iTN201 or some working condition changes.

Raisecom




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. Meanwhile, the alarm is generated to log information.

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.

14.1.9 CPU protection

The iTN201 supports CPU protection. In a certain interval, when the number of some packet

received by an interface exceeds the upper threshold, the iTN201 will discard the packet

without reporting it to the CPU. This helps protect the CPU.

14.1.10 CPU monitoring

The iTN201supports CPU monitoring, which is used to monitor task status, CPU utilization

rate, and stack usage in real time, helping the administrator locate the fault quickly.

CPU monitoring can provide the following functions:

Viewing CPU utilization

– View CPU hold time and utilization rate of all tasks in each period (5 seconds, 1

minute, 10 minutes, or 2 hours). The total CPU utilization rate within each period can

be displayed statically or dynamically.

– View the operating status of all tasks and the detailed operating status information of

specified tasks.

– View historical CPU utilization rate within each period.

– View the dying gasp task information.

CPU utilization rate threshold alarm

Within a specified sampling period, the system will generate an alarm and send Trap if CPU

utilization rate is over the configured rising threshold or below the declining threshold. The

Trap provides 5 task IDs and their CPU utilization rates of tasks which have the highest CPU

utilization rate in the latest period (5 seconds, 1 minute, or 10 minutes).

14.1.11 Hardware environment monitoring

The Nview NNM system supports monitoring the hardware information of the iTN201,

including the following information:

Temperature information

Voltage information

Fan information

Power supply information

14.1.12 Remote management

The iTN201 perform remote management on the RC552 series through the extended OAM

protocol. Remote management involves configuring the name, IP address, interface properties

of the remote device. In addition, it consists of monitoring interface status of the remote

device and notifying the NView NNM system when the interface status changes.

Raisecom




Extended OAM is based on IEEE 802.3ah OAM link. By using the expandability, it enhances

OAM management further and realizes management on remote devices.

As shown in Figure 14-2, the OAM link is established between the iTN201 and the RC552-

FE (A). The iTN201 is directly connected to the NView NNM system. Therefore, the iTN201

can configure and monitor the RC552-FE (A)

Figure 14-2 Extended OAM

As the local device, the iTN200 can manage the RC552-FE (A) through extended OAM,

including the following aspects:

Querying remote properties: query properties, configurations, and statistics of the remote

device.

Configuring remote basic functions: configure some functions of the remote device,

including the host name, interface status, speed and duplex mode, VLAN, QinQ,

bandwidth, and failover.

Configuring remote network management: configure related network management

parameters for remote devices that support SNMP, such as the IP address, gateway,

management IP address, and read-write community. Therefore, the iTN201 can manage

these remote devices through SNMP.

Sending remote Trap: when an interface Link Up/Down alarm is generated, the remote

device sends an extended OAM notification frame to the iTN201. And then the iTN201

sends Trap to the NView NNM system.

Rebooting the remote device: the iTN201 can send the command to reboot the remote

device.

At present, the iTN201 supports managing the RC552-FE(A), RC552-FE(B), RC552-GE(B), and RC552-GE(D) remotely. For above-mentioned transceivers, the capabilities for supporting extended OAM are different. Therefore, remote management configurations on the iTN201 are different.

14.2 Configuring SNMP

Raisecom





Scenario

When you need to log in to the iTN201 through the NView NNM system, you should

configure basic SNMP functions on the iTN201.

Prerequisite

Before configuring SNMP, you should perform the following operations:

Configure the IP address of the SNMP interface.

Configure a routing protocol, making the route between the iTN201 and the NView

NNM system reachable.

14.2.2 Configuring SNMPv1/v2c basic functions

Creating community name and configuring related view and access authority

Indexes 1 and 2 are communities created by the system and cannot be modified or deleted.


SNMP MGT > SNMP Community.

Step 2 Select a record and then click Modify. A dialog box appears, as shown below. The following




Index Display the index.

Community

Name

Configure the community name, which ranges from 1 to 20 characters.

View Name Click Select to select a view name.

Raisecom





Access Control Select an access authority.

ReadOnly: read the data from Agent only. ReadWrite: read the data from Agent and write data to it.

(Optional) configuring the mapping relationship between users and access group


SNMP MGT > VACM Security to Group.

Step 2 Click Add and a dialog box appears, as shown below. The following table describes items at

the dialog box.



VACM Security Model Select a VACM security model.

v1SM v2cSM USM

VACM Security Name Click Select to select a VACM security name (i.e. SNMP

community name).

VACM Group Name Click Select to select a VACM access group name.

Configuring SNMP target host address


SNMP MGT > SNMP Target Addr..


the dialog box.


Raisecom





SNMP Transport IP

Address

Configure the SNMP transport IP address (i.e. the IP address of

SNMP Trap target host).

SNMP Transport Port Configure the SNMP transport port ID, which is set to 162 by

default.

SNMP Tag List Read-only SNMP Tag list

SNMP Message

Processing Model

Select a SNMP message processing mode (i.e. SNMP version).

v1 v2c v3

SNMP Security Model Select a SNMP security model.

V1SM V2cSM USM

SNMP Security Name Select a SNMP security name (i.e. community name).

public private

SNMP Security Level Select a SNMP security level.

noauthnopriv: have no authentication or authority. authnopriv: have authentication but no authority. authPriv: have authentication and authority.

14.2.3 Configuring SNMPv3 basic functions

Creating and configuring SNMP access group


SNMP MGT > VACM Access.

Raisecom





the dialog box.



VACM Group Name Enter a VACM access group name. Up to 32 characters

are available.

VACM Context Prefix Configure the VACM context prefix.

VACM Security Model Select a VACM security model.

USM v1SM v2cSM

VACM Security Level Select a VACM security level.

authNoPriv noauthNoPriv authPriv

VACM Context Match Select a VACM context matching rule.

exact: match all characters. prefix: match the first several characters.

VACM ReadView Name Click Select to select a VACM read-view name.

VACM WriteView Name Click Select to select a VACM write-view name.

VACM NotifyView Name Click Select to select a VACM notification-view name.

Creating users and configuring authentication modes


SNMP MGT > USM User.

Raisecom





the dialog box.



User Name Enter a user name. Up to 32 characters are available.

User Clone From Click Select to select configurations to be cloned by the user.

After a user is created, it cannot be activated unless you set the Authentication Protocol to usmNoAuth Protocol.





User Engine ID Display the user engine ID.

User Name Display the user name.

Raisecom





Authentication

Protocol

Display the authentication protocol used by the user.

Authentication Key

Change

Configure the changes authentication key. You can modify any

user.

Privacy Protocol Display the encapsulation mode used by the user.

Privacy Key Change Configure the changed encapsulation key. You can modify any

user.

Configuring SNMP view


SNMP MGT > VACM View Tree Family.


the dialog box.



VACM View Name Enter a VACM view name.

VACM Subtree Click Select to select a VACM sub-tree.

VACM View Tree

Type

Select a VACM sub-tree type.

included: MIB variables of the view are included in the sub-tree. excluded: MIB variables of the view are excluded from the sub-

tree.

Raisecom





VACM Mask Configure the VACM mask, which ranges from 0 to 32 and is in


The VACM mask displayed through the NView NNM system differs from the one displayed through CLI. When the length of the VACM mask is a one with odd digits, a F is added to the last bit. For example, when the length of a VACM mask is set to 1, it is displayed as 1F on the NView NNM system. When the length of the VACM mask is a one with even digits, it is displayed as original on the NView NNM system. For example, when the length of a VACM mask is set to 12, it is displayed as 12 on the NView NNM system.



1. View configurations on the SNMP access group.


SNMP MGT > VACM Access. Select a record and then click View to view configurations on

the SNMP access group.

2. View configurations on the SNMP community.


SNMP MGT > SNMP Community. Select a record and then click View to view

configurations on the SNMP community.

3. View basic configurations of SNMP.


RFC1213 to view basic configurations of SNMP, including the contact method of the

administrator and physical position of the iTN201.

4. View the mapping relationship between SNMP users and access group.


SNMP MGT > VACM Security to Group. Select a record and then click View to view the

mapping relationship between SNMP users and access group.

5. View configurations on the SNMP Trap target host.


SNMP MGT > SNMP Target Addr.. Select a record and then click View to view

configurations on the SNMP Trap target host.

6. View SNMP statistics.


SNMP MGT > USM Stat.. Select items and click Chart to view SNMP statistics in a form

of chart.

Raisecom




7. View SNMP user information.


SNMP MGT > USM User. Select a record and then click View to view SNMP user

information.

8. View SNMP view information.


SNMP MGT > VACM View Tree Family. Select a record and then click View to view

SNMP view information.

14.3 Configuring routing


Scenario

Configure static routing for simple topology network. You need to configure static routing

manually to create an intercommunication network.

Prerequisite

Configure the IP address of the Layer 3 interface properly.

14.3.2 Configuring static routing

Configuring static routing information


ROUTER > Static Config and then select the IP Static Config Table tab.

Step 2 Click Add and a dialog box appears, where you can configure static routing information. The




Route Destination

Address

Configure the destination IP address of the routing, which is

in dotted decimal notation.

Mask Of Destination

Address

Configure the subnet mask of the destination IP address,


Next Hop IP Address Configure the next-hop IP address, which is in dotted decimal

notation.

Raisecom




Configuring default administrative distance


ROUTER > Static Config.

Step 2 Select the IP Static Set tab, where you can configure the default administrative distance. The




Default Admin Distance Configure the default administrative distance, which ranges




1. View configurations on the static routing.


ROUTER > Static Config and then select the P Static Config Table tab. Select a record and

then click View to view configurations on the static routing.

2. View information about the static routing table.


ROUTER > Static Config and then select the IP Static Set tab to view information about the

static routing table.

14.4 Configuring RMON


Scenario

RMON helps monitor and count network traffics.

Compared with SNMP, RMON is a more high-efficient monitoring method. After you

specifying the alarm threshold, the iTN201 actively sends alarms when the threshold is

exceeded without gaining the variable information. This helps reduce the traffic of

management and managed devices and facilitates managing the network.

Prerequisite

The route between the iTN201 and the Nview NNM system is reachable.

Raisecom




14.4.2 Configuring RMON statistics

By default, RMON statistics is enabled and cannot be configured. You can view RMON statistics only.

14.4.3 Configuring RMON history group


Protocol MGT > RMON MGT > RMON HISTORY and then select the RMON History

Statistics Group Control tab.

Step 2 Click Add and a dialog box appears, where you can configure the RMON history group. The




Entry index Configure the OAM history group table index, which ranges from

1 to 65535.

Requested data

buckets number

Configure the number of requested data storage blocks, which


Sample interval Configure the sampling interval, which ranges from 1 to 3600s.


Control data owner Configure the owner of the control parameter, which ranges from

0 to 255 characters.

14.4.4 Configuring RMON alarm group


Protocol MGT > RMON MGT > RMON ALARM.

Step 2 Click Add and a dialog box appears, where you can configure the RMON alarm group, as



Raisecom





Table index Configure the OAM alarm group table index, which ranges from

1 to 512.

Sample interval Configure the sampling interval of MIB variables, which ranges

from 2 to 3600s.

MIB variable Enter a MIB variable.

Sample type Select a sampling type.

AbsoluteValue: check the absolute value of the MIB variable

and take it as a mode to generate alarm. Compare the absolute

value with the pre-configured thresholds. An alarm is

generated if the absolute value is smaller than the minimum

threshold or greater than the maximum threshold. DeltaValue: check the relative value of the MIB variable and

take it as a mode to generate alarm. Compare the relative value

with the pre-configured thresholds. An alarm is generated if

the absolute value is smaller than the minimum threshold or

greater than the maximum threshold.

Alarm to be sent Select the alarm to be send.

RisingAlarm: rising alarm FallingAlarm: falling alarm Rising or FallingAlarm: rising/falling alarm

Rising threshold Configure the maximum threshold, which ranges from 2 to

2147483647.

The maximum threshold must be greater than the minimum threshold.

Raisecom





Falling threshold Configure the minimum threshold, which ranges from 2 to

2147483647.

Rising Event Index Configure the index of the rising event.

Falling Event Index Configure the index of the falling event.

Entry owner Configure descriptions about the alarm record.

14.4.5 Configuring RMON event group


Protocol MGT > RMON MGT > RMON EVENT.

Step 2 Click Add and a dialog box appears, where you can configure the RMON event group, as




Table index Configure the OAM event group table index, which ranges from

1 to 32.

Event description Configure descriptions about the RMON event.

Notification type Select how to notify the RMON event.

none: perform no operation. Log: record the RMON event to a log. SNMP-Trap: send a Trap to the NView NNM system. Log&Trap: record the RMON event to a log and send a Trap

to the NView NNM system.

SNMP community Display the SNMP community name.

Event owner Configure descriptions about the RMON event owner.

Raisecom






1. View RMON alarm group information.


Protocol MGT > RMON MGT > RMON ALARM. Select a record and then click View to

view RMON alarm group information.

2. View RMON event group information.


Protocol MGT > RMON MGT > RMON EVENT. Select a record and then click View to

view RMON event group information.

3. View RMON statistics group information.


Protocol MGT > RMON MGT > RMON STATIS. Select a record and then click View to

view RMON statistics group information.

14.5 Configuring LLDP


Scenario

When you obtain connection information between devices through the NView NNM system

for topology discovery, you need to enable LLDP on the iTN201. Therefore, the iTN201 can

notify its information to the neighbours mutually, and store neighbour information to facilitate

the NView NNM system querying information.

Prerequisite

N/A

14.5.2 Enabling global LLDP and LLDP alarm

After global LLDP is disabled, you cannot re-enable it immediately. Global LLDP cannot be enabled unless the restart timer times out.


Protocol MGT > LLDP > LLDP Config Info.

Step 2 Select the LLDP group config tab, as shown below. The following table describes items at the

tab.


Raisecom





LLDP enable Enable/Disable global LLDP.

True False

By default, global LLDP is disabled.

Lldp Notification Enable Enable/Disable LLDP alarm notification.

True False

By default, LLDP alarm notification is enabled.

14.5.3 Enabling interface LLDP


Protocol MGT > LLDP > LLDP Config Info and then select the LLDP Port Config Table

tab.

Raisecom




Step 2 Select a record and then click Modify. A dialog box appears. The following table describes




LLDP port enable Enable/Disable interface LLDP.

True False

By default, interface LLDP is enabled.

Lldp Port Dest Address Configure the LLDP interface destination address, which is in


14.5.4 Configuring basic functions of LLDP

When configuring the delay timer and period timer, the value of the delay timer

should be smaller than or equal to a quarter of the period timer value. The value of the delay timer should be smaller than the aging time.



Step 2 Select the LLDP Configuration tab, as shown below. The following table describes items at

the tab.


Raisecom





LLDP message

transfer interval

Configure the period for sending LLDP packets, which ranges

from 5 to 32768s. By default, it is set to 30s.

LLDP hold

multiplier

Enter the aging coefficient of LLDP packets, which ranges from 2

to 20. By default, it is set to 4.

Aging time = aging coefficient × period

LLDP reinit delay

timer

Configure the restart timer. After global LLDP is disabled, it

cannot be enabled unless the restart timer times out.

It ranges from 1 to 10s. By default, it is set to 2s.

LLDP delay transfer

timer

Configure the delay timer of the LLDP packet.

It ranges from 1 to 8192s. By default, it is set to 2s.

Raisecom





LLDP trap

notification timer

Configure the LLDP Trap period timer. It ranges from 5 to 3600s.

By default, it is set to 5s.



1. View LLDP local configurations.


Protocol MGT > LLDP > LLDP Config Info and then select the LLDP group config tab to

view LLDP local configurations.


Protocol MGT > LLDP > LLDP Config Info and then select the LLDP Configuration tab to

view configurations on LLDP timers.

2. View LLDP local system information.


Protocol MGT > LLDP > LLDP Local Info to view LLDP local system information.

3. View LLDP neighbor information.


Protocol MGT > LLDP > LLDP Neighbor Info to view LLDP neighbor information.

4. View LLDP packet statistics.


Protocol MGT > LLDP > LLDP Statistics Info and then select the LLDP Statistics tab to

view LLDP packet statistics of the iTN201.


Protocol MGT > LLDP > LLDP Statistics Info and then select the LLDP Statistics Port

Table tab. Select a record and then click View to view LLDP packet statistics on the interface.

14.6 Configuring optical module DDM


Scenario

Optical module DDM provides a method for monitoring SFP performance parameters. By

analyzing monitored data provided by the optical module, the administrator can predict the

SFP module lifetime, isolate system faults, as well as verify the compatibility of the optical

module.

Prerequisite

N/A

Raisecom




14.6.2 Enabling optical module DDM


Optical Monitor.

Step 2 Select the Global Config tab, where you can enable optical module DDM and transceiver

Trap. The following table describes items at the tab.



Transceiver Trap

Management of Device

Enable/Disable transceiver Trap.

Enable Disable


Digitaldiagnotic enable of

the device

Enable/Disable DDM.

Enable Disable


14.6.3 Enabling optical module DDM and alarm management on interfaces


Optical Monitor and then select the optical module current status table tab.





transceiver trap management of

port

Enable/Disable alarm management on interfaces.

Enable Disable

Raisecom





Digitaldiagnotic enable of the port Enable/Disable DDM on interfaces.

Enable Disable



1. View the global status of optical module DDM.

From the Action List of the iTN201 EMS, choose SNMP Management > Port MGT >

Optical Monitor and then select the Global Config tab to view the global status of optical

module DDM.

2. View information about optical module DDM performance parameters and the ones the

when they exceed the configured thresholds last time.


Optical Monitor and then select the optical module digital diagnostic tab to view information

about optical module DDM performance parameters and the ones the when they exceed the

configured thresholds last time.

3. View historical information about optical module DDM.


Optical Monitor and then select the period history monitor information tab. Select a record

and then click View to view historical information about optical module DDM.

4. View basic information about the optical module.


Optical Monitor and then select the transceiver information tab. Select a record and then

click View to view basic information about the optical module.

14.7 Configuring system log


Scenario

The iTN201 generates critical information, debugging information, or error information of the

system to system logs and outputs the system logs to log files or transmits them to the host,

Console interface, or monitor for viewing and locating faults.

Prerequisite

N/A

Raisecom




14.7.2 Configuring basic information about system log

Enabling system log management and configuring related parameters


Protocol MGT > SysLog.

Step 2 Select the SysLog Service tab, where you can enable system log management and configure

related parameters. The following table describes items at the tab.



Syslog Management Enable/Disable system log management.

Enable Disable

Rate Limit Configure the number of logs processed every second. It ranges

from 1 to 10000. By default, it is set to 0, which indicates no

configurations on the rate.

Time Stamp Select a timestamp for the system log.

no-timestamp: no timestamp data-timestamp: absolute time, a time point (i.e. system time) up-timestamp: relative time, a time period (i.e. time since the

system is enabled.)

History Table Status Enable/Disable output logs to the log history table.

Enable Disable

History Table Size Configure the history table size, which ranges from 1 to 500.

Buffer Size Configure the buffer size, which ranges from 4 to 256 KB.

Sequence Number

Status

Enable/Disable displaying the sequence number.

Enable Disable

Outputting system logs to log host


Protocol MGT > SysLog and then select the SysLog Server Table tab.


the dialog box.


Raisecom





Server IP Address Configure the IP address of the log server, which is in dotted

decimal notation.

Up to 10 log hosts are available.

Facility Configure the facility filed of the log sent to the log host.

kern: log generated by kernel user: information generated by user process mail: log generated by the mail system daemon: log of the system daemon process auth: log generated when being authenticated syslog: log generated by the system log lpr: log generated by the line print system news: log of USENET network news system uucp: UUCP system information cron: cron/at tool information security: information generated when being authorized FTP: information of FTP process ntp: information of network time sub-system audit: information generated when being audited Alert: information generated when an alarm occurs clock: information of clock management process Local 0–7: local logs

Max Severity Select a severity level for a log.

Emergency: level 0, most serious. The system cannot run. You

need to reboot the device. Alert: level 1, very serious. You need to take actions immediately. Critical: level 2, critical. You need to take actions or analyze

reasons. error: level 3, error. It has no effect on services but needs

attention. Warning: level 4, warning. It may cause service failure and needs

attention. Notice: level 5, normal, key operating information when the

device is running Info: level 6, notification, general operating information when the

device is running Debug: level 7, debugging information, general operating

information when the device is running, and needing no attention

Raisecom




Enabling/Disabling system log Trap


ALARM SWITCH.

Step 2 Select the Alarm Switch tab, where you can enable/disable system log Trap. The following




Alarm information syslog status Enable/Disable system log Trap.

Enable Disable


Clear all alarm information Select whether to clear all alarm information.

True False

By default, do not clear all alarm information.

Enabling/Disabling dying-gasp system log output


ALARM SWITCH.

Step 2 Select the Power Switch tab, where you can enable/disable dying-gasp system output. By

default, it is enabled.


Enabling/Disabling temperature alarm system log output


ALARM SWITCH.

Step 2 Select the Temperature Switch tab, where you can enable/disable temperature alarm system

log output. By default, it is enabled.


Enabling/Disabling voltage alarm system log output


ALARM SWITCH.

Step 2 Select the Voltage Switch tab, where you can enable/disable voltage alarm system log output.



Raisecom




14.8 Configuring loopback test


Scenario

The network maintenance engineers can detect and analyze interface and network faults

through interface loopback.

Ingress packets and egress packets are defined as below:

Ingress packets: test packets received by an interface

Egress packets: test packets return to the peer device through an interface

Prerequisite

When the current interface is in Forwarding status, packets entering the interface can be

properly forwarded or transmitted to the CPU.

14.8.2 Configuring parameters of interface loopback rules


Loopback Test and then select the Loopback Function Table tab.

Step 2 Select a record and then click Modify. A dialog box appears, where you can configure

interface loopback parameters. The following table describes items at the dialog box.



DMAC

Parameter

Configure the loopback rule parameter based on the destination MAC

address. It is in colon hexadecimal notation. By default, it is set to

00:00:00:00:00:00, which indicates that there is no such a parameter.

SMAC

Parameter

Configure the loopback rule parameter based on the source MAC

address. It is in colon hexadecimal notation. By default, it is set to

00:00:00:00:00:00, which indicates that there is no such a parameter.

SVLAN

Parameter

Configure the SVLAN-based loopback rule parameter. It ranges from 0

to 4094. By default, it is set to 0, which indicates that there is no such a

parameter.

CVLAN

Parameter

Configure the CVLAN-based loopback rule parameter. It ranges from 0

to 4094. By default, it is set to 0, which indicates that there is no such a

parameter.

Destination

IP

Configure the loopback rule parameter based on the destination IP

address. It is in dotted decimal notation. By default, it is set to 0.0.0.0,

which indicates that there is no such a parameter.

Source IP Configure the loopback rule parameter based on the source IP address. It

is in dotted decimal notation. By default, it is set to 0.0.0.0, which

indicates that there is no such a parameter.

Raisecom





Loop Back

Lasting Time

Configure the interface loopback interval. It ranges from 0 to 30 min.

Loopback

Mode

Select an interface loopback rule.

Abort Loopback Function: disable loopback. Loopback Based Port: perform loopback on packets received by the

interface. Loopback Based Source MAC: perform loopback on packets with the

specified destination MAC address received by the interface. Loopback Based Destination MAC: perform loopback on packets with

the specified source MAC address received by the interface. Loopback Based Customer VLAN: perform loopback on packets with

the specified CVLAN ID received by the interface. Loopback Based Service VLAN: perform loopback on packets with the

specified SVLAN ID received by the interface. Loopback Based SVLAN&CVLAN: perform loopback on packets

with the specified CVLAN ID and SVLAN ID received by the

interface. Loopback based on sip: perform loopback on packets with the

specified source IP address received by the interface. Loopback based on dip: perform loopback on packets with the

specified destination IP address received by the interface. Loopback based on sip and dip: perform loopback on packets with the

specified source and destination IP addresses received by the interface.

By default, it is set to Abort Loopback Function.

14.8.3 Configuring global loopback parameters


Loopback Test.

Step 2 Select the Global Config tab, where you can configure global loopback parameters. The




Broadcast And

Multicast MAC

Address Transform

Enable/Disable destination MAC address translation of multicast

and broadcast loopback packets.

Enable Disable


Multicast Dip

Transform Mode

Enable/Disable destination IP address translation of multicast

loopback packets.

Enable Disable


Raisecom





Local IP Configure the IP address of the iTN201, which is in dotted

decimal notation. By default, it is set to 127.0.0.1.

Unicast SMAC

Transform Mode

Configure the valuing rule for the source MAC address of unicast

loopback packets.

local MAC: the source MAC address of the unicast loopback

packet is the local MAC address. Swap: the source MAC address of the unicast loopback packet is

translated to the destination MAC address of the packet.

By default, it is set to local MAC.

Local MAC Configure the local MAC address of the iTN201, which is in colon

hexadecimal notation. By default, it is set to the MAC address of

the current device.



1. View configurations on interface loopback rule parameters.


Loopback Test and then select the Loopback Function Table tab. Select a record and then

click View to view configurations on the interface loopback rule parameter.

2. View configurations on global loopback parameters.


Loopback Test and then select the Global Config tab to view configurations on global

loopback parameters.

14.9 Configuring alarm management


Scenario

When the iTN201 fails, the alarm management module will collect the fault information and

output the alarm in a log. The alarm information includes the time when the alarm is

generated, the name and descriptions of the alarm. It helps you quickly locate the fault.

If the NView NNM system is configured on the iTN201, when the operating environment of

the device is abnormal, the iTN201 supports saving to the hardware monitoring alarm table,

sending Trap to the NView NNM system, and outputting to the system log. It notifies users to

process the fault and prevent the fault from occurring.

With alarm management, you can directly perform following operations on the iTN201: alarm

inhibition, alarm auto-report, alarm monitoring, alarm inverse, alarm delay, alarm storage

mode, alarm clearing, and alarm viewing.

Raisecom




Prerequisite

After hardware monitoring is configured on the iTN201,

When alarms are output in Syslog form, alarms are generated to the system log. When

needing to send alarms to the log host, you need to configure the IP address of the log

host on the iTN201.

When needing to send alarms to the NView NNM system in a Trap form, you need to

configure the IP address of the NView NNM system on the iTN201.

14.9.2 Configuring basic functions of alarm management

Configuring related functions of alarm management


Alarm MGT > ALARM MGMT.

Step 2 Select the Alarm Config tab, where you can configure related functions of alarm management.




Alarm Raise Delay Configure alarm report delay time, which ranges from 0 to 600s.

Alarm Clear Delay Configure alarm clear delay time, which ranges from 0 to 600s.

Active Alarm Store

Mode

Configure the storage mode of the current alarm table.

Stop: the newly-generated alarm will be discarded when the

alarm buffer is full. Loop: the newly-generated alarm will replace the oldest one

when the alarm buffer is full.

Alarm Inhibit Enable Enable/Disable alarm inhibition.

Enable Disable

Alarm Syslog Enable Enable/Disable alarm system log.

Enable Disable

Configuring alarm notification


Alarm MGT > Alarm MGT to enable alarm notification.


Enabling alarm reporting and alarm shielding (alarm monitoring)


Alarm MGT > ALARM MGMT and then select the Report/Monitor Config tab.

Raisecom








Alarm Report Enable Enable/Disable alarm reporting.

Enable Disable

Alarm Monitor Enable Enable/Disable alarm shielding.

Enable Disable

Configuring alarm inverse


Alarm MGT > ALARM MGMT and then select the Alarm Inverse tab.

Step 2 Select a record and then click Modify. A dialog box appears, where you can configure alarm

inverse. The following table describes items at the dialog box.



Inverse Mode Select an alarm inverse mode.

None: device alarm is reported normally. Auto: no matter what the current alarm state is, the reported alarm

state of the interface will be changed opposite to the actual alarm state

immediately, that is to say, not report when there are alarms, report

when there are not alarms actually. The interface will maintain the

opposite alarm state regardless of the alarm state changes before the

alarm reverse state being restored to non-reverse mode. Manual: If the interface has not actual reverse alarm currently, the

setting will return fail; if the interface has actual reverse alarm, the

setting is success and enter reverse mode, i.e. the interface reported

alarm status is changed opposite to the actual alarm status

immediately. After the alarm is finished, the enabling state of

interface alarm reverse will ends automatically and changes to non-

reverse alarm mode so that the alarm state can be reported normally

in next alarm.

Raisecom




Clearing current alarms


Alarm MGT > ALARM MGMT and then select the Alarm Delete tab.

Step 2 Select a record and then click Save.

14.10 Configuring CPU protection


Scenario

In a certain interval, when the number of some packet received by an interface exceeds the

upper threshold, the iTN201 will discard the packet without reporting it to the CPU. This

helps protect the CPU.

Prerequisite

N/A

14.10.2 Configuring CPU protection

Enabling CPU protection


CPU Protect > CPU Protect and then select the CPU Protect Port Info tab.

Step 2 Select a record and then click Modify. A dialog box appears, where you can enable CPU

protection. By default, it is disabled.


Configuring basic information about CPU protection


CPU Protect > CPU Protect and then select the CPU Protect Packet Info tab.

Step 2 Select a record and then click Modify. A dialog box appears, where you can configure basic

information about CPU protection. The following table describes items at the dialog box.



Sample Interval Enter the sampling interface of packets. It ranges from 0 to 65535s.

By default, the sampling interval for ARP and ICMP packets is set

to 5s and is set to 1s for BPDU packets.

Raisecom





Threshold Of

Denying Packet

Configure the threshold for discarding packets. It means that

packets will be discarded when the number of the received packets

exceeds the threshold during the interval. It ranges from 1 to 65535.

By default, the threshold is set to 200 for ARP and BPDU packets

and is set to 300 for ICMP packets.

Threshold Of

Receiving Packet

Configure the threshold for receiving packets. It means that packets

will not be discarded when the number of received packets is

smaller than the threshold during the interval. It ranges from 1 to

65535.

By default, the threshold is set to 40 for ARP, BPDU, and ICMP

packets.



1. View CPU protection status.


CPU Protect > CPU Protect and then select the CPU Protect Port Info tab. Select a record

and then click View to view CPU protection status.

2. View basic information about CPU protection.


CPU Protect > CPU Protect and then select the CPU Protect Packet Info tab. elect a record

and then click View to view basic information about CPU protection.

14.11 Configuring CPU monitoring


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 iTN201, that is, the IP address of the NView NNM system.

Raisecom




14.11.2 Viewing CPU monitoring information

Viewing CPU utilization rate


CPU Monitor Config > CPU Monitor Info and then select the CPU Utilization Entry tab to

view CPU utilization rate in each time period (1s, 5s, 1min, 10min, or 2 hours).

Viewing status of all tasks


CPU Monitor Config > CPU Monitor Info and then select the Process Statistics In The

Period tab.

Step 2 Select a record and then click View to view status of all tasks.

Viewing CPU utilization rate history table


CPU Monitor Config > CPU Monitor Info and then select the CPU Utilization History

Entry tab.

Step 2 Select a record and then click View to view the CPU utilization rate history table.

14.11.3 Configuring CPU monitoring Trap


CPU Monitor Config > CPU Monitor Config to configure CPU monitoring Trap. The




CPU Utilization

Threshold Trap Status

Enable/Disable CPU threshold Trap.

Enable Disable


CPU Utilization Rising

Threshold

Configure the maximum threshold, which ranges from 1% to

100%.

CPU Utilization Falling

Threshold

Configure the minimum threshold, which ranges from 1% to

100%.

CPU Utilization

Threshold Interval

Configure the sampling interval, which ranges from 5 to

36000s. By default, it is set to 60s.



View CPU monitoring configurations.

Raisecom





CPU Monitor Config > CPU Monitor Config to view CPU monitoring configurations.

14.12 Configuring remote management

Scenario

The iTN201 establishes connections with remote transceivers and manage them through

extended OAM protocol.

Prerequisite

Before managing a remote device, you need to perform the following operations in order.

Enable OAM on the iTN201.

Configuring the iTN201 working in active mode.

Configure the remote device working in passive mode through CLI or other mode.

Right-click the iTN201 icon at the NView NNM topology view and then choose

Resource Synchronization from the right-click menu to synchronize the remote device

to the NView NNM topology view.

14.12.2 Configuring IP addresses of remote devices

For the RC552-FE (A) and RC552-GE (B), you cannot configure their IP addresses and default gateways on the iTN201.

Step 1 Double-click the remote device icon at the NView NNM topology view.

Step 2 Select the IP Address tab.

Step 3 Configure the IP address of the remote device. The following table describes items at the tab.

Step 4 After configurations, click apply.


IP Address Configure the IP address of the remote device, which is in dotted

decimal notation.

Subnet Mask Configure the subnet mask of the IP address, which is in dotted

decimal notation.

Default Gateway Configure the default gateway of the remote device, which is in


The default gateway and the IP address of the remote device should be in the same network segment.

Raisecom




14.12.3 Configuring interface properties of remote devices


Step 2 Select the Port Table tab.

Step 3 Select a record and then click Modify. A dialog box appears, where you can configure

interface properties of the remote device. The following table describes items at the dialog

box.



Port Administrative State Select the interface management status.

Up: the interface is open. Down: the interface is shut down.

Port Speed/Duplex Set Select the speed and duplex mode of the interface

Auto: negotiate the speed and duplex mode automatically. 10M/Full Duplex: 10 Mbit/s and full duplex 10M/Half Duplex: 10 Mbit/s and half duplex 100M/Full Duplex: 100 Mbit/s and full duplex 100M/ Half Duplex: 100 Mbit/s and half duplex 1000M/Full Duplex: 1000 Mbit/s and full duplex 1000M/ Half Duplex: 1000 Mbit/s and half duplex

Port Ingress Rate Configure the uplink bandwidth of the interface, which ranges

from 1 to 1000000 bit/s.

Port Fault Pass Enable/Disable failover on the interface.

Enable Disable

14.12.4 Configuring OAM Trap notification of remote devices


OAM MGT (802.3ah) > Extend OAM Config.

Step 2 Enable/Disable OAM Trap notification. The following table describes items at the dialog box.



Extend-OAM

Notification Enable Enable/Disable OAM Trap notification.

Enable Disable


Raisecom




14.12.5 Configuring power-on notification of remote devices


OAM MGT (802.3ah) > Extend OAM Config.

Step 2 Enable/Disable power-on notification of remote devices. The following table describes items

at the dialog box.



Config Request Enable Enable/Disable power-on notification of remote devices.

Enable Disable


14.12.6 Configuring remote VLAN

For the RC552-FE (A) and RC552-GE (B), you cannot configure their VLANs on the iTN201.

After you configure the remote VLAN on the iTN201, the remote device can process packets

based on the configured VLAN properties. Available remote VLAN features include VLAN

status, VLAN CoS status, VLAN Tag properties, and VLAN group.

VLAN status of remote devices includes:

Enable

Disable

After VLAN CoS is enabled, the remote device can process received packets based on their

VLAN priorities. The one with higher priority will be processed first.

Configuring remote VLAN properties


Step 2 Select the Vlan Config Table tab.

Step 3 Configure the remote VLAN properties. The following table describes items at the tab.

Step 4 After configurations, click apply.

Raisecom





Vlan Status Select a VLAN status of the interface.

vlan-forbid: forward received packets transparently. vlan-dot1q: forward received packets based on the dot1q mode. vlan-port: the remote VLAN is in Port mode. vlan-forbid:

By default, it is set to VLAN-Forbid.

CoS Status Enable/Disable remote VLAN CoS.

True: enable remote VLAN CoS. False: disable remote VLAN CoS.


Fiber Port Tag

Type

Select a Tag type of the optical interface.

Untag: do not carry Tag. Tag: carry Tag.

By default, it is set to Untag.

Fiber Port CoS

Value

Configure the priority of the optical interface. It ranges from 0 to 7.


Fiber Port Pvid Configure the PVID of the optical interface. It ranges from 1 to


Cable Port Tag

Type Select a Tag type of the electrical interface.



Cable Port CoS

Value

Configure the priority of the electrical interface. It ranges from 0 to


Cable Port Pvid Configure the PVID of the electrical interface. It ranges from 1 to


Cpu Port Tag Type Select a Tag type of the CPU interface.



Cpu Port CoS

Value

Configure the priority of the CPU interface. It ranges from 0 to 7.


Cpu Port Pvid Configure the PVID of the CPU interface. It ranges from 1 to 4094.


Configuring remote VLAN groups

After configuring the remote VLAN group, you can relate the VLAN to interfaces.


Raisecom




Step 2 Select the Vlan Group Table tab.

Step 3 Select a record and then click Modify. A dialog box appears, where you can configure the

remote VLAN group. The following table describes items at the dialog box.




Index Display the VLAN group ID, which ranges from 1 to 16.

Vlan ID Configure the VLAN ID, which ranges from 0 to 4094. The

number 0 indicates configuring no VLAN.

Vlan Member Select a member interface for the VLAN group.

Fiber Port Cable Port Cpu Port

14.12.7 Configuring related functions of remote QinQ

For the RC552-FE (A), you cannot configure related functions of remote QinQ on the iTN201.


Step 2 Select the Q-in-Q tab.

Step 3 Configure related functions of remote QinQ. The following table describes items at the tab.



Switch Mode Select a switching mode.

Transparent: do not process the packet. 802.1Q: add the native VLAN ID (PVID) to received Untag

packets/do not process Tag packets. Q-in-Q: add the specified TPID and outer Tag of the native

VLAN ID (PVID) to received packets.

Outer Tag TPID Configure the outer Tag TPID, which is in hexadecimal

notation. It ranges from 0000 to FFFF. By default, it is set to

9100.

This parameter is available when the Switch Mode is set to Q-in-Q.

Raisecom





Native VLAN ID Configure the native VLAN ID, which ranges from 1 to 4094.

This parameter is available when the Switch Mode is set to 802.1Q/Q-in-Q.

VLAN Access Port Select an ingress interface.

line client

This parameter is available when the Switch Mode is set to 802.1Q/Q-in-Q.

14.12.8 configuring information about customers attaching to remote devices

Adding and attaching customers


Step 2 Select the Customer Info tab and then click Add&Attach Customer. A dialog box appears,

where you can configure information about the customer. The following table describes items

at the dialog box.

Step 3 After configurations, click Add&Attach Customer.


Base Info.

Customer Name Configure the customer name (required).

Customer Category Select a customer category.

General Customer Key Customer

Customer Type Select a customer type.

Customer Level Select a customer level (Level 1–Level 5)

Circuit ID Configure the circuit ID.

Description Configure descriptions about the customer.

Contact Info.

Contact Phone Configure the telephone number of the customer.

Contact Person Configure the contact person.

Contact Address Configure the address of the customer.

Raisecom




In addition, you can attach the iTN201 to a created customer by clicking Attach Customer.

14.12.9 Rebooting remote devices

When the remote device is being reset or rebooted, OAM links will be broken. Therefore, the iTN201 cannot connect to the remote device.


Step 2 Click Reboot.

Step 3 Click OK.

14.12.10 Applying configurations


Step 2 Select the Send Config tab.

Step 3 Click send at the Send vlan allocation area to apply VLAN configurations.

Step 4 Click send at the Send global allocation area to apply global configurations.

14.12.11 Viewing information about remote devices


Step 2 Select the Base Info tab to view information about the remote device.

14.12.12 Viewing statistics

Viewing statistics of remote interfaces


Step 2 Select the Port Stats tab.

Step 3 Select a record and then click View to view statistics of remote interfaces.

Step 4 (Optional) select a record and then click Chart to view statistics of remote interfaces in a

form of chart.

Viewing statistics of local interfaces


OAM MGT (802.3ah) > Extend OAM Statistics.

Step 2 Select a record and then click View to view statistics of the interface.

Step 3 (Optional) select a record and then click Chart to view statistics of the interface in a form of

chart.

Raisecom




14.12.13 Viewing remote SFP information


Step 2 Select the SFP Info tab to view remote SFP information.

14.12.14 Viewing extension information

Viewing remote extension information


Step 2 Select the Extend Info tab to view remote extension information.

Viewing extended OAM information on local interfaces


OAM MGT (802.3ah) > Extend OAM Status.

Step 2 Select a record and then click View to view statistics of the interface.

Step 3 (Optional) select a record and then click Chart to view extended OAM information on the

local interface.

14.12.15 Viewing remote environment information


Step 2 Select the Environment Info tab to view remote environment information.



1. View configurations on the IP address of the remote device.

Double-click the remote device icon at the NView NNM topology view and then select the IP

Address tab to view configurations on the IP address of the remote device.

2. View configurations on interfaces of the remote device.

Double-click the remote device icon at the NView NNM topology view and then select the

Port Table tab. Select a record and then click View to view configurations on interfaces of the

remote device.

3. View QinQ configurations of the remote device.

Double-click the remote device icon at the NView NNM topology view and then select the Q-

in-Q tab to view QinQ configurations of the remote device.

4. View configurations on remote VLAN properties.


Vlan Config Table tab to view configurations on remote VLAN properties.

5. View configurations on remote VLAN groups.

Raisecom





Vlan Group Table tab. Select a record and then click View to view configurations on

interfaces of the remote device.

14.13 Maintenance Perform the following operations on the iTN201 to maintain system features.

1. Clear LLDP interface statistics.


Protocol MGT > LLDP > LLDP Statistics Info and then select the LLDP Statistics Port

Table tab. Select a record and then click LLDP port clear statistics.

2. Clear LLDP interface neighbor information.


Protocol MGT > LLDP > LLDP Neighbor Info. Select a record and then click LLDP port

clear remote.

3. Clear remote interface statistics.


Port Stats tab. Select a record and then click Clear.

4. Clear local interface statistics.


OAM MGT (802.3ah) > Extend OAM Statistics. Select a record and then click Clear.


14.14.1 Examples for configuring RMON alarm group


As shown in Figure 14-3, the iTN201 is the Agent, which is connected to the terminal through

the Console interface and is connected to the NView NNM system through the Internet.

Enable RMON statistics on the iTN201 to execute performance statistics on Client 1. During

a period, when the number of packets received by the interface exceeds the configured

threshold, the iTN201 records a log and sends a Trap to the NView NNM system.

Raisecom




Figure 14-3 Configuring RMON alarm group

Configuration steps

Step 1 Create RMON event group 1, which is used to record and send logs whose description string

is set to High-ifOutErrors. The owner of the log is set to system.

1. From the Action List of the iTN EMS, choose SNMP Management > Advanced MGT >

Protocol MGT > RMON MGT > RMON EVENT.

2. Click Add and a dialog box appears, where you can configure RMON event group 1.



Parameter Value

Table index 1

Event description High-ifOutErrors

Notification type Log

Event owner system

Step 2 Create alarm group 10. Alarm group 10 is used to monitor the MIB variable

(1.3.6.1.2.1.2.2.1.20.1) every 20 seconds. If the value of the variable is added by 15 or greater,

a Trap is triggered. The owner of the Trap is also set to system.

1. From the Action List of the iTN EMS, choose SNMP Management > Advanced MGT >

Protocol MGT > RMON MGT > RMON ALARM.

2. Click Add and a dialog box appears, where you can configure RMON alarm group 10.



Parameter Value

Table index 10

Sample interval 20

MIB variable 1.3.6.1.2.1.2.2.1.20.1

Sample type DeltaValue

Raisecom




Parameter Value

Alarm to be sent RisingAlarm

Rising threshold 15

Falling threshold 0

Rising event index 1

Entity owner system

Checking results

1. View configurations on RMON event group 1.

From the Action List of the iTN EMS, choose SNMP Management > Advanced MGT >

Protocol MGT > RMON MGT > RMON EVENT. Select the record about RMON event

group 1 and then click View to view configurations on RMON event group 1.

2. View configurations on RMON alarm group 10.

From the Action List of the iTN EMS, choose SNMP Management > Advanced MGT >

Protocol MGT > RMON MGT > RMON ALARM. Select the record about RMON alarm

group 10 and then click View to view configurations on RMON alarm group 10.

14.14.2 Examples for configuring LLDP basic functions


As shown in Figure 14-4, iTN A and iTN B are connected to the NView NNM system. Enable

LLDP on links between iTN A and iTN B. And then you can query the Layer 2 link changes

through the NView NNM system. If the neighbour is aged, added, or changed, iTN A and iTN

B send LLDP alarm to the NView NNM system.

Figure 14-4 Configuring LLDP basic functions

Raisecom




Configuration steps

Step 1 Enable global LLDP and enable LLDP alarm.

Configure iTN A.



2. Select the LLDP group config tab, where you can enable global LLDP and enable LLDP

alarm. The following table lists values of parameters.


Parameter Value

LLDP enable True

Lldp Notification Enable True

Configure iTN B.


described.

Step 2 Configure the management IP address.

Configure iTN A.


VLAN Config and then select the VLAN Static Table tab.

2. Click Add and a dialog box appears, where you can create VLAN 1024. The following



Parameter Value

VLAN ID 1024



2. Select the record about interface 3 and then click Modify. A dialog box appears, where

you can configure allowed VLAN IDs of this interface. The following table lists values

of parameters.


Parameter Value

Port Mode Access



Management traffic and then select the Ip Address tab.

Raisecom




2. Click Add and a dialog box appears, where you can create a Layer 3 address. The



Parameter Value

Port Index 1

IP Address 10.10.10.1


Management traffic and then select the VLAN LIST tab.

2. Click Add and a dialog box appears, where you can configure the VLAN of the Layer 3



Parameter Value

VLAN ID 1024

IP Interface 1

Configure iTN B.


described.

Step 3 Configure LLDP properties.

Configure iTN A.



2. Select the LLDP Configuration tab. The following table lists values of parameters.


Parameter Value

LLDP message transfer interval 60

LLDP delay transfer timer 9

LLDP trap notification timer 10

Configure iTN B.


described.

Checking results

1. View iTN A local configurations.

Raisecom





Protocol MGT > LLDP > LLDP Config Info and then select the LLDP group config tab to

view LLDP status.


Protocol MGT > LLDP > LLDP Config Info and then select the LLDP Configuration tab to

view LLDP properties.

2. View iTN B local configurations.

Steps for viewing iTN B local configurations are identical to the ones for viewing iTN A local

configurations. In this guide, no details are described.

3. View neighbor information.


Protocol MGT > LLDP > LLDP Neighbor Info. Select the record about interface 1 and then

click View to view LLDP neighbor information.

14.14.3 Examples for outputting system logs to log host


As shown in Figure 14-5, configure system log to output system logs of the iTN201 to the log

host, facilitating view them at any time.

Figure 14-5 Outputting system logs to log host

Configuration steps

Step 1 Configure the IP address of the iTN201.

1. From the Action List of iTN EMS, choose SNMP Management > Advanced MGT >

Management traffic and then select the Ip Address tab.

2. Click Add and a dialog box appears, where you can configure the IP address of the

Layer 3 interface. The following table lists values of parameters.


Parameter Value

Port Index 0

Address Type IPv4

IP Address 20.0.0.6

Address Prefix length 8

Raisecom





Management traffic and then select the VLAN LIST tab.

2. Click Add and a dialog box appears, where you can configure the VLAN of the Layer 3



Parameter Value

VLAN ID 1

IP Interface 0

Step 2 Output system logs to the log host.


Protocol MGT > SysLog.

2. Select the SysLog Service tab, where you can configure information about the system

log server. The following table lists values of parameters.


Parameter Value

Syslog Management Enable

Rate Limit 2

Time Stamp date-timestamp

4. Select the SysLog Server Table tab and then click Add. A dialog box appears. The



Parameter Value

Server IP Address 20.0.0.168

Max Severity Warning

Checking results

View system log configurations.

From the Action List of iTN EMS, choose SNMP Management > Advanced MGT >

Protocol MGT > SysLog and then select the SysLog Service tab to view system log

configuration. Select the SysLog Server Table tab. Select a record and then click View to view

configurations on the IP address of the system log server.

View the log information displayed on the PC terminal emulation program interface.

Raisecom




14.14.4 Examples for managing the RC552-GE (B) remotely


As shown in Figure 14-6, the RC552-GE (B) is the remote device and the iTN200 is the local

device. An extended OAM link is established between local and remote devices to perform

remote management of the RC552-GE (B) on the iTN201, including configuring the IP

address, default gateway, interface properties, network management, and QinQ. By default,

the RC552-GE (B) is enabled with extended OAM and works in OAM passive mode.

Configure the RC552-GE (B) as below:

IP address: 192.168.10.8

Subnet mask: 255.255.255.0

VLAN ID: VLAN 1

Default gateway: 192.168.10.1

Speed and duplex mode of Client 1: 100 Mbit/s and full duplex

Bandwidth of Ingress interface Client 1: 8 Mbit/s

Failover status: enabled

Working mode: transparent mode

Other parameters: default values

Figure 14-6 Managing the RC552-GE (B) remotely

Configuration steps

Configure related functions of the RC552-GE (B) on the iTN201.

Step 1 Configure OAM on iTN201 interface Client 1.

1. From the Action List of the iTN201 EMS, choose SNMP Management > Advanced

MGT > OAM MGT (802.3ah) > OAM Table and then select the OAM Table tab.


3. A dialog box appears, where you can configure OAM on the interface. The following



Raisecom




Parameter Value


OAM Operation Mode active

Step 2 Configure the IP address of the RC552-GE (B).

1. Double-click the RC552-GE (B) icon at the NView NNM topology view and then select

the IP Address tab.

2. Configure the IP address of the RC552-GE (B). The following table lists values of

parameters.


Parameter Value

IP Address 192.168.10.8

Subnet Mask 255.255.255.0

Default Gateway 192.168.10.1

Step 3 Configure the properties and bandwidth of the RC552-GE (B) interface Client 1 and enable

failover.

1. Double-click the RC552-GE (B) icon at the NView NNM topology view and then select

the Port Table tab.

2. Select a record and then click Modify. A dialog box appears, where you can configure

the interface properties. The following table lists values of parameters.


Parameter Value

Port Index 2

Port Administrative State Up

Port Speed/Duplex Set 100M/Full Duplex

Port Ingress Rate 8000

Port Fault Pass Enable

Step 4 Configure QinQ of the RC552-GE (B).

1. Double-click the RC552-GE (B) icon at the NView NNM topology view.

2. Select the Q-in-Q tab, where you can configure QinQ of the RC552-GE(B). The



Raisecom




Parameter Value

Switch Mode Transparent

Step 5 Configure remote alarm reporting.

1. From the Action List of the iTN201 EMS, choose SNMP Management > Advanced

MGT > OAM MGT (802.3ah) > Extend OAM Config.

2. Enable OAM notification and then click Save.

Checking results

1. View configurations on the IP address of the RC552-GE (B).

Double-click the RC552-GE (B) icon at the NView NNM topology view and then select the

IP Address tab to view configurations on the IP address of the RC552-GE (B).

2. View configurations on interfaces of the RC552-GE (B).


Port Table tab. Select a record and then click View to view configurations on interfaces of the

RC552-GE (B).

3. View QinQ configurations of the RC552-GE (B).


Q-in-Q tab to view QinQ configurations of the RC552-GE (B).

Raisecom


Element Management) 15 Batch configuration and management


15 Batch configuration and management

This chapter describes how to use the batch configuration and management feature of the

NView NNM system, including the following sections

Overview

Adding a batch configuration task

Enabling batch configuration tasks

Disabling batch configuration tasks

15.1 Overview Because there are a great number of devices in the network, it is complex to configure an

operation form them. The NView NNM system provides the batch configuration and

management feature to help the administrator configure an operation for devices periodically,

improving working efficiency greatly.

Steps for configure all tasks are similarly identical. In this guide, take steps for configuring the NE time for an example.

15.2 Adding a batch configuration task After adding a batch configuration task, you can schedule it manually/periodically to perform

batch configuration on NEs.

Step 1 Choose EMS Config > Batch Task Center from the menu bar of the NView NNM system.

Step 2 Choose Batch Tasks > Common Commands > Set NE Time (0) from the left topology tree.

Step 3 Click from the tool bar at the Task List area, a dialog box appears, as shown below.


Raisecom





Task Type Display the selected batch configuration task.

Task Name Define a name for identifying the task.

Task Status Select the task status in initial status.

Enable Disable

Execute

Mode

Select a mode for performing the task.

Manual Only Once Daily Weekly Monthly

Related labels and text boxes change based on the select Execute Mode.

If a task to be manually performed is added, it is performed once being enabled. The task cannot be performed periodically. To re-perform the task, modify its properties or re-enable it. The task to be performed once cannot be performed periodically. Compared with the task to be manually performed, it can be configured with the time to perform the task. Other tasks can be performed periodically.

Raisecom




Step 4 After configurations, click Next. A dialog box appears, as shown below.

Click Add to add a device.

To delete a device, select it and then click Delete.

In addition, you can copy the devices of an existing task to the device list by selecting

the Select devices of existing task radio button and then click the drop-down list or

Search… to select a created task.

Step 5 Click Add and a dialog box appears, as shown below.

Step 6 (Optional) query the device. Set conditions and then click Query. The system will display

devices that meet conditions. Select the device and click OK to add the device to the device

list.

Raisecom




Step 7 After configurations, click OK. The system will record the task to the database and schedule

it based on the configured execution mode.

15.3 Enabling batch configuration tasks

To enable a disabled task or re-perform a manual task, perform one of the following

operations:

Right-click a task record at the Task List area and then choose Enable from the right-

click menu.

Select a task record at the Task List area and then choose Enable from the tool bar at the

Task List area.

Modify the task properties (any parameter but for the task type) and then set the Task

Status to Enable.

Right-click a device at the Task Detail List area and then choose Restart from the right-

click menu or select a device at the Task Detail List area and then choose Restart from

the tool bar at the Task Detail List area. This operation is available for the selected

device.

Raisecom




15.4 Disabling batch configuration tasks To disable a task, perform one of the following operations:

Right-click a task record at the Task List area and then choose Disable from the right-

click menu.

Select a task record at the Task List area and then choose Disable from the tool bar at the

Task List area.

Modify the properties of a task and then set the Task Status to Disable.

Raisecom


Element Management) 16 Alarm management


16 Alarm management

This chapter introduces how to use the alarm management feature of the NView NNM system,


Overview

Viewing alarms

Alarm filtering

16.1 Overview After receiving an alarm, the NView NNM system will notify the administrator in a striking

way, provide detailed information of the alarm event, and locate the alibi of the fault. The

NView NNM system may even provide a resolution to assist the administrator remove the

fault in time and guarantee the smooth operation of the network.

16.1.1 Alarm status

In the NView NNM system, every alarm event may be in one of the following two statuses:

Newly generated: Received alarm event from network device

Recovered: If the fault occurred on network device disappears or some performance

indexes get back to normal automatically, the Agent will send "Alarm Recovery

Information" via Trap to the system. System will modify the alarm status of the

corresponding alarm event to "Recovered" after receiving the recovery information. By

this time, the fault on the device should have been removed. The recovered alarm

displays in green in the alarm list.

16.1.2 Operation status

For every alarm event, network administrator may execute some operation on it. There are 4

types of operations can be executed on an alarm event, leading to 4 types of operation status:

Unacknowledged: The network administrator has not executed any operation on the

alarm event.

Acknowledged: As to newly generated alarms, you can execute an "acknowledge"

operation on a current alarm to modify the status of the alarm to "Acknowledged" if

he/she is aware of the content of the alarm. Please note that the alarm status is

Raisecom




"Acknowledged" does not mean that the corresponding fault has been removed from the

network.

Cleared: All current alarms can be changed to historical alarms by executing the "clear"

operation on them. The operation status of the alarm will become "Cleared" after the

operation. And "Cleared" alarms will be removed from the current alarm list and listed

on the historical alarm list.

Filtered: The system provides an alarm filtering scheme, which filters some received

alarms from being displayed on the current alarm list. The operation status of these

alarms is "Filtered". All filtered alarms will not be displayed in the current alarm list, but

be saved as historical alarm directly.

16.2 Viewing alarms You can view current alarms and historical alarms, which are described in following sections.

16.2.1 Current alarms

Current alarms are defined based on the operation status of alarm events. Therefore, alarms

that are not deleted or filtered are current alarms. You must learn that the "current" is not a

specified time. It is identified according to operation status. In the network management,

current alarms are at higher level.

Right-click the iTN201 NE at the topology view and then choose Alarm management >

Alarm view from the right-click menu. Select the Current Alarm tab and current alarms on

the iTN201 are displayed, as shown below.

You can perform following configurations on current alarms:

Acknowledging alarms

Clearing alarms

Viewing alarm properties

Querying troubleshooting

Raisecom




Locating device in topology view

Acknowledging alarms

Acknowledge selected current alarms. You can select multiple current alarms. This operation

cannot be performed until all selected alarms are in "new entry" status. It indicates the

administrator has acknowledged the alarm and delivered a fault sheet or sent the personnel to

address this fault.

To acknowledge an alarm, follow these steps:

Step 1 In the current alarm list, right-click one or multiple newly-generated alarms and choose

Acknowledge from the right-click menu and a dialog box appears.

Step 2 Enter the acknowledgement information, such as the fault sheet information and personnel

and click OK.

Step 3 If successful, for the selected alarms will be in "acknowledged" status.

The acknowledged alarms are still displayed in the current alarm list. After an alarm is

acknowledged, if the highest alarm is changed, the warning tone will also be changed. If all

alarms in the current alarm list are acknowledged, the warning tone will disappear.

Clearing alarms

If an alarm is cleared, it indicated the fault is troubleshot or the administrator confirms that the

alarm cannot reduce the current network service quality. You can clear current alarms based

on some specified conditions. Sub-menus for clearing one or more alarms are shown as

follows:

Clear selected: clear one or more selected alarms.

Clear same type: clear one or more alarms that are same with the selected alarm in the

current alarm list.

Clear same location: clear one or more alarms that are at the same location with the

selected alarm in the current alarm list.

Clear acknowledged: clear all acknowledged alarms in the current alarm list.

To clear alarms, follow these steps:

Step 1 Right-click one or more alarms that need to be cleared in the current alarm list and choose

Clear Alarm from the right-click menu. Select a sub-menu as required and a dialog box

appears.

Step 2 When clearing an alarm, you need to enter some information, such as clearing log, fault

reason, fault description, and resolution. The information will be saved to the trouble-shooting

database. If a similar fault is generated, you can query related information, improving the

trouble-shooting efficiency, as shown below.

Raisecom




The alarm clearing information includes:

Clear user: automatically add a user for clearing current alarms.

Clearing log: it is optional. Descriptions about the trouble-shooting operations.

Fault reason. It is a required option. Click and a dialog box appears. And then

enter the fault reason.

Step 3 After entering a fault reason, click Add. You can edit the fault reason. However, you cannot

delete a used fault reason.

Step 4 Click OK and the system will clear selected alarms. After operation, all selected alarms will

be deleted from the current alarm list and are saved to the historical alarm list.

Similar to alarm acknowledgement, if the highest alarm changed, the warning tone will also

be changed. If all alarms in the current alarm list are cleared, the warning tone will disappear.

The alarm status for the NE will also be changed.


When checking properties about an alarm, besides detailed basic information about the alarm,

you can also check related device information and customer information. It facilitates you

checking related information about this alarm.

To view properties of an alarm, follow these steps:

Step 1 Double-click a record or right-click a record and then choose Properties from the right-click

menu.

Step 2 A dialog box appears. Click different buttons on the left side to view related properties.

Raisecom




Querying troubleshooting

The system provides a trouble-shooting repository for saving and managing the trouble-

processing policies used in routine work. It helps provide trouble-shooting policies in shortest

time if a fault is generated, improving trouble-shooting efficiency. When the system is initially

installed, nothing is saved in the repository. All trouble-shooting experience is accumulated

during routine operations.

Right-click a record in the current alarm list and then choose Query Troubleshooting from

the right-click menu. A dialog box is displayed. All default recommends and historical

trouble-shooting records will be displayed in this dialog box.

Raisecom





This function can be used to quickly find the failed device in the network according to the

alarm.

Right-click a record in the current alarm list and then choose Locate in Topo from the right-

click menu. The location of the device, where the alarm is generated, is displayed at the

topology view.

16.2.2 Historical alarms

Except for current alarms, other alarms are called historical alarms. Historical alarms refer to

alarm events that are cleared or filtered. You must learn that the "historical" is not a specified

time. It is identified according to operation status.

Right-click the iTN201 NE at the topology view and then choose Alarm management >

Alarm view from the right-click menu. Select the Historical Alarm tab and current alarms on

the iTN201 are displayed, as shown below.

Raisecom




Deleting historical alarms

In the historical alarm list, two methods are supported for deleting alarms.

Delete Selection: delete selected alarms.

Delete Query Result: delete all historical alarms under current query condition.

Right-click records that need to be cleared in the historical alarm list and then choose Delete >

Delete Selection/Delete Query Result from the right-click menu. A dialog box is displayed.

Click Yes to delete historical alarms.


Right-click records that need to be viewed in the historical alarm list and click Properties. A

dialog box is displayed. And then you can view historical alarm properties.

Raisecom




Querying trouble-shooting Adding trouble-shooting

All cleared alarms are saved in the historical alarm database. You can add the trouble-shooting

for a historical alarm. Select one or more records in the historical alarm list, and then choose

Query Troubleshooting > Add Troubleshooting from the right-click menu. Enter fault

reasons and trouble-shooting modes in the dialog box and click OK to generate a trouble-

shooting record.

With Same Alarm Type

When an alarm is generated on the iTN201, the system will provide some troubleshooting

experience of this alarm type. This troubleshooting experience is accumulated. Right-click

multiple records and then choose Query Troubleshooting > With Same Alarm Type from

the right-click menu. A dialog box is displayed, where you can view historical troubleshooting

experience.

Raisecom





Right-click a record in the historical alarm list and then choose Locate in Topo from the

right-click menu. The location of the device, where the alarm is generated, is displayed at the

topology view.

16.3 Alarm filtering The NView NNM system provides the alarm filtering mechanism. You can specify the NView

NNM system not receiving some alarms by defining the filtering rule. In addition, you can

specify whether to save filtered alarms to the database. If yes, these alarms are historical ones

and their operation status is set to Filtered.

The iTN201 supports the following 4 filtering rules:

Device-based filtering rule

Interface-based filtering rule

Chassis-based filtering rule

Card-based filtering rule

The alarm type and alarm level filtering rules are based on the alarm management feature of

the NView NNM system. For detailed configuration steps, see NView NNM Operation Guide.

16.3.1 Adding device-based filtering rules

To add a device-based filtering rule, follow these steps:

Step 1 Right-click the iTN201 NE at the NView NNM topology view and then choose Alarm

management > Alarm filtering from the right-click menu and then click the Add Filter Rule

for Device tab.

Step 2 Select one or more devices to be filtered and then select alarms to be filtered, as shown below.

If All Alarm Types are selected, it indicates filtering all alarms of the device.

If not, alarms of the device are displayed and then select alarms that need to be filtered.

Raisecom





16.3.2 Adding interface-based filtering rules

To add an interface-based filtering rule, follow these steps:

Step 1 Right-click the iTN201 NE at the NView NNM topology view and then choose Alarm

management > Alarm filtering from the right-click menu and then click the Add Filter Rule

for Port tab.

Step 2 Select one or more ports to be selected and then select alarms to be filtered.

If All Alarm Types are selected, it indicates filtering all alarms of the device.

If not, alarms of the device are displayed and then select alarms that need to be filtered.


Raisecom


Element Management) 17 Performance management


17 Performance management

This chapter introduces how to use the performance management feature of the NView NNM

system, including the following sections:

Overview

Performance monitoring service

Monitoring real-time performance

Configuring performance monitoring tasks

Historical performance

17.1 Overview The performance management module of the NView NNM system provides the iTN201

performance data-based and network-oriented performance data detection function, helps the

network administrator learn operation status (such as the load and the traffic) during the

current and the past period, as well as provides evidences for troubleshooting problems and

optimizing network.

To operate performance management on the iTN201, you need to use NView NNM performance monitoring service. This service is restricted by the License. It cannot be used unless authenticated by the License. For details about how to use NView NNM performance monitoring service, see NView NNM User Manual (Performance Monitoring Service).

17.2 Performance monitoring service

17.2.1 Introduction

The NView NNM V5 system provides system monitoring function, which can start

performance monitoring service through system monitoring client. The performance

monitoring service supports being started through system monitoring and through EXE

executable file. After manual start of performance monitoring service, system monitoring can

manage performance monitoring service.

Raisecom




17.2.2 Enabling performance monitoring service

The performance monitoring service can be enabled manually/automatically.

This guide describes how to enable performance monitoring service manually. For other details, see NView NNM User Manual (Performance Monitoring Service).

To manually enable/disable performance monitoring service, follow these steps:

Step 1 Double-click the "NMS Server" shortcut on the desktop to start the NView NNM software.

Step 2 Double-click the "NMS Control" shortcut on the desktop to start the system monitoring client.

Step 3 (Optional) at the Process Monitor tab, right-click the PerfMonitor record and then choose

Start Process when it is disabled.

Step 4 (Optional) at the Process Monitor tab, right-click the PerfMonitor record and then choose

Stop Process when it is enabled.

17.3 Monitoring real-time performance

17.3.1 Introduction

The real-time performance graph function provided by performance monitoring service can

make performance data graphical, draw performance graph automatically based on real-time

performance data, and display the real-time status of device performance data clearly and

intuitively. Moreover, you can select to view different network element device easily in real-

time performance graph monitoring.

After NView NNM platform service and performance monitoring service are started, you can

take real-time performance monitoring through NView NNM client.

17.3.2 Monitoring real-time performance

To initiate performance monitoring service, follow these steps:

Step 1 Choose Performance > Graph from the menu bar of the NView NNM system.

Step 2 Query the device whose real-time performance to be monitored. The following table describes

related items.


Device Name Query network element device name.

Device name refers to network element name, right-click network

element, and choose View Properties from the right-click menu to

view network element name.

Raisecom





Subnet Name Query network element located subnet.

Click to pop up "Select subnet" dialog box. Select the subnet

to query, and then click OK. "Select subnet" dialog box can provide

search function, input subnet name and then click to search

subnet meeting the query conditions.

Device Ip Query network element IP address.

Format: dotted decimal IP address.

Purpose Query network element device purpose.

The default device purpose is "Unspecified", including the

following options:

Blank, not query device purpose. Unspecified Common user access Key account access Community aggregation Bureau station aggregation Relay transmission

Right-click a NE and then choose View Properties from the right-

click menu.

Step 3 Click Search.

Step 4 Select the NE and performance collection resources are displayed. This step is availbel for the

performance graph initiated from the system menu.

Step 5 Select resources according to resource type and slot. You can only select resource in the same

resource type, the same type of resource support to select 5 resources at most. Select resource

type and slot classification, and all resources in this classification will be selected.

Step 6 Select the Real Time PM Chart tab in the right after selecting resource to show performance

metrics and real-time performance graph interface.

Step 7 Select performance metrics accordance to metrics group, supporting to select multiple

performance metrics; each performance metric shows one performance graph. Multiple

resources will be distinguished in different colors in the same performance graph.

Step 8 (Optional) click drop-down list to configure real-time collection interval.

Step 9 Click Running to draw real-time performance graph for monitoring.

Click , , in real-time chart toolbar to switch real-time performance graph display type to line chart, area chart, or bar chart.

You can initiate monitoring real-time performance in the following 3 modes:

Raisecom




Initiating from the topology view/topology tree Initiating from the collection task management interface Initiating from the inventory management

17.4 Configuring performance monitoring tasks

17.4.1 Introduction

Performance monitoring collection task supports to select performance collection resources,

performance metrics, alarm thresholds, and supports to configure collection frequency as well

as task execution cycle, etc. Performance monitoring service takes scheduling to perform

collection task and performance monitoring to network element device based on user

configuration, and then records the collected performance data to the database for you to view

historical performance data and historical performance graph.

Performance collection task is divided into the following two types:

Batch deployment tasks: to take performance monitoring to network element device, you

can use performance monitoring service batch deployment collection tasks function to

configure performance collection to multiple device resources with the same type.

Single-point task: single-point configuration is to configure a single device. The main

function of single-point configuration is to configure and issue collection task with single

device as collection object.

This guide describes how to configure a single task only.

17.4.2 Configuring single task

Configuration steps

Step 1 Right-click the iTN201 NE at the topology view or topology tree and then choose

Performance > Single Node Config from the right-click menu.

Step 2 Select a collection resource at the left side and basic information, collection plan, metric

template, and threshold template about the single task are described at the right side. The

following tablde describes related parameters.

Do not select resources with icons and . These two icons indicate that the collection resources have already configured performance collection task and cannot be configured again.

Figure 17-1 Basic parameters of a single task

Parameter Value Description

Task name – Configure batch deployment task names.

The task names cannot be the repeated.

Raisecom




Parameter Value Description

Period 5 minutes 15 minutes 24 hours

Configure collection task execution frequency

cycle, i.e. the time interval to perform one time

performance collection.

Status Stopped Running Yield

Configure the initial status of collection task.

Stop by default. Only "Start" collection task

performs performance collection. After collection

task is created, you can modify collection status in

collection task management interface.

In a single task, the selected resources belong to the same resource category. For example, you can select Ethernet interfaces of multiple cards on one NE.

Step 3 (Optional) select the "Collect Plan" tab to configure collection plan. By default, performance

task performs continuous collection only then collection task is started, you can configure

collection plan to collect performance data periodically. The configuration parameters of

collection plan are shown below.

Continuous collection and user-defined collection can perform collection only then collection task is started.

Table 17-1 Parameters for collection plan of a single task


Continue Collect Collect performance data continuously after starting collection task.

By default, select continuous collection.

Custom Collect Collect performance data according to collection plan configuration

periodicity after starting collection task.

Configure follow-up parameters after selecting user-defined

collection.

Task Start/End

Time Configure customized collection data range.

Start/Stop Collect

Period

Configure user-defined collection time slot, supporting multiple time

slots collection.

By default, "00:00:00–23:59:59" to collect, i.e. all day collection.

To modify time slot, select default time record at first, and then click

to remove default record.

Add collection time slot records

Select time slot record, and then click to remove collection

time slot record.

Raisecom





Collect Dyas of

Week

Collect based on weekly collection days.

Click Select to configure weekly collection days.

All Select: collect from Monday to Sunday, which is default. Custom Define: configure days to collect from Monday to Sunday

and collect in the selected days. Select Work Days: collect from Monday to Friday.

Collect Days of

Month

Collect based on monthly collection days.

Click Select to configure monthly collection days.

All Select collect all the month, which is default. Custom Define: configure days to collect from the first day to the

end day in this month and collect in the selected days.

Step 4 (Optional) click Advance and a dialog box is displayed, where you can configure the

performance metric template and the threshold template, as shown below. Select a

performance metric template at the Metric Template Setting area and then choose a threshold

template for the performance metric template at the Tca Template Name drop-down list. After

configurations, click Confirm.

Table 17-2 Parameters for performance metric template and threshold template of a single task


Metric Template

Setting

Select the metric template to record configuration collection task.

Use system default template by default, also supporting to select

user-defined metric template. Only when user-defined metric

template contains resources supporting performance metric, the

user-defined template record can be shown.

Tca Template

Name

Configure to select threshold template of metric template.

Click to select metric template record, click drop-down list box to

select threshold template. The interface will show the detailed

information of selected threshold template.


Icons at the interface

Table 17-3 describes icons at the interface.

Table 17-3 Icons at the collection object

Icon Description

Resource type. Each resource type contains one or multiple resources. All

resources are checked/unchecked when you check/uncheck the resource

type.

Online resource deployed with the collection task

Raisecom




Icon Description

Offline resource without being deployed with the collection task

Online resource deployed with the collection task

Offline resource without being deployed with the collection task

17.4.3 Starting collection tasks

After starting a collection task, the performance monitoring service begins to collect

performance data.

In the basic information of the collection task, the status is set to Stopped by default. If you do not change the collection status when creating a task, the performance monitoring services cannot collect the performance data unless you start the collection task.

Step 1 Choose Performance > Collect Task Management from the system menu of the NView

NNM system.

Step 2 Select a Stopped record or select multiple Stopped record by selecting one, pressing and

dragging the left button of the mouse. And then choose Running from the right-click menu.

Step 3 After the collection task is started, the collection task status is displayed as .

17.4.4 Stopping collection tasks

After stopping a collection task, the performance monitoring service does not collect the

performance data. Stopping a collection task does not influence the collected performance

data or viewing the historical performance graph.

Step 1 Choose Performance > Collect Task Management from the system menu of the NView

NNM system.

Step 2 Select a Running record or select multiple Running record by selecting one, pressing and

dragging the left button of the mouse. And then choose Stopped from the right-click menu.

Step 3 After the collection task is started, the collection task status is displayed as .

17.5 Historical performance

17.5.1 Introduction

The historical performance graph function provided by performance monitoring service can

make performance data graphical, draw performance graph automatically based on historical

performance data, and display the working status of device performance data clearly and

intuitively.

Raisecom




When collection task is configured, performance monitoring service will perform

performance data collection and save them to database. You can browse historical

performance graph and data to view whether the network device and service are running

normally so that the operation and maintenance personnel can check.

The historical performance graph is divided into the following six categories:

Original: collected original performance data, including all performance data collected

after the performance task is started.

Hour: hourly performance data, taking statistics based on original performance data, one

piece of record per hour.

Day: daily performance data, taking statistics based on original performance data, one

piece of record per day.

Week: weekly performance data, taking statistics based on original performance data,

one piece of record per week.

Month: monthly performance data, taking statistics based on original performance data,

one piece of record per month.

Year: annual performance data, taking statistics based on original performance data, one

piece of record per year.

17.5.2 Viewing historical performance graph

The function entrance to browse historical performance graph and data and monitor real-time

performance graph and data is the same, which is shown in "History PM Chart"

Step 1 (Optional) query a NE, which only applies to launching performance graph from system menu.

Enter query information in the above of network element list, click Search to filter network

element list. The following table describes parameters.


Device Name Query network element device name.

Device name refers to network element name, right-click network

element, and choose View Properties from the right-click menu to

view network element name.

Subnet Name Query network element located subnet.

Click to pop up "Select subnet" dialog box. Select the subnet

to query, and then click OK. "Select subnet" dialog box can provide

search function, input subnet name and then click to search

subnet meeting the query conditions.

Device Ip Query network element IP address.

Format: dotted decimal IP address.

Raisecom





Purpose Query network element device purpose.

The default device purpose is "Unspecified", including the

following options:

Blank, not query device purpose. Unspecified Common user access Key account access Community aggregation Bureau station aggregation Relay transmission

Right-click a NE and then choose View Properties from the right-

click menu.

Step 2 Select the NE and performance collection resources are displayed. This step is availbel for the

performance graph initiated from the system menu.

Step 3 Select resources according to resource type and slot. You can only select resource in the same

resource type, the same type of resource support to select 5 resources at most. Select resource

type and slot classification, and all resources in this classification will be selected.

Step 4 Select the History PM Chart tab in the right after selecting resource to show performance

metrics and real-time performance graph interface.

Step 5 (Optional) configure a historical collection interval. By default, the last 24 hours are

configured.

Step 6 Select a historical performance graph type.

In hourly, daily, weekly, monthly and annual performance graphs, each point data in performance curve is calculated based on original data. According to different performance metrics, there are different calculation methods. The typical calculation methods are as follows: Calculate total sum of the data: accumulate performance data in one time slot, for

example calculate data flow by accumulating total sum of the data. Calculate average value of the data: average performance data in one time slot,

for example use CPU utilization rate to calculate the average value.

Step 7 Click Query to show the historical performance graph.

Raisecom


Element Management) 18 Data center


18 Data center

This chapter introduces how to use the data center feature of the NView NNM system,


Introduction

Starting data center

Device operation management

18.1 Introduction The NView NNM system has a data center component which is used to manage the NE

software and configuration data. The data center provides Carrier with a high-efficient

management method on software management and data configuration management.

The data center component can perform centralized management on upgrade, backup,

recovery, rollback, activation of devices. In addition, it manages the upgrade file, backup file,

and logs generated by various operations and backup. It ensures more convenient operation,

simpler maintenance, and high security of upgrade and backup.

This chapter describes the most commonly-used upgrade and backup operation only. For detailed usage of the data center, see NView NNM User Guide (Data Center). At present, the data center supports upgrading and backing up the iTN201 system software and configuration file.

18.2 Starting data center The data center is installed together with the NView NNM system.

Through system monitoring provided by the NView NNM system, you can start/stop data

center manually/automatically. In addition, you can manually start the data center.

The data center is a service of the NView NNM system. You can launch various operations by

choose Data Center and its related sub-menus from the system menu of the Nview NNM

system or from the right-click menu.

Raisecom




To ensure that the data center works properly, be sure port 20 and port 21 are not

blocked by the firewall or other monitoring programs. Because operations of the data center may influence the device, we do not

recommend operating the data center when services are busy. In addition, we do not recommend performing operations on the same device frequently.

Step 1 Double-click the NMS Server at the desktop to start the NView NNM system.

Step 2 After the NMS server is successfully enabled, a dialog box is displayed, saying, NMS Server

has been started successfully! And then click OK.

Step 3 Double-click the NMS Control at the desktop to start the NMS system monitoring client.

Step 4 Enter the user name and password and then click OK to enter the NMS system monitoring

client.

Step 5 View the operating status of the Instance Server and confirm the operating status of the

Instance Server is set to Running in the Process Monitor tab.

Step 6 At the Process Monitor tab, right-click the Dc EMS and Dc Server respectively and then

choose Set Start Model > Automatic from the right-click menu to configure the data center

being started automatically when the NView NNM system is started.

The data center contains "Dc server" and "Dc EMS" services. To use the data center, you must enable these 2 services. When the start mode is set to Automatic, it indicates that related services are automatically enabled after the NView NNM system is started. When the start mode is set to Manual, it indicates that related services are not automatically after the NView NNM system is started. However, you can manually enable them at the system monitoring client.

Step 7 (Optional) when the operating status of the Dc Server/Dc EMS is set to Stopped, right-click it

and then choose Start Process from the right-click menu to manually enable the service.

Step 8 (Optional) when the operating status of the Dc Server/Dc EMS is set to Running, right-click it

and then choose Stop Process from the right-click menu to manually enable the service.

18.3 Device operation management It is very significant to ensure the stability of the device in complex environment of the

operation and maintenance network. To ensure services work properly, you should well plan

the time and efficiently and reliably deploy services when you upgrade/back up device

software or configuration data files. The NView NNM data center transmits device operations

to tasks and relates network resources to these tasks. It meets requirements on time, high-

efficiency, and reliability of operation and maintenance tasks.

18.3.1 Upgrade

Use files in the software base to upgrade the NEs. After the upgrade task is finished, the

system will prompt you whether to reboot the device for activation. By default, do not reboot

the device.

Raisecom




Upgrading NE files

To upgrade NE files, follow these steps:

Step 1 Choose Data Center > Device Operation from the system menu of the NView NNM system.

Step 2 Right-click the blank area and then choose Create NE Upgrade Task from the right-click

menu.

Step 3 Enter the task name.

Step 4 Select the NE to be upgraded and relate it to the upgrade task. The NView NNM system

support selecting a NE based on its type, IP address, and NE version.

Step 5 Select the file to be upgraded and the related target upgrade file. By selecting different version,

you can realize upgrade.

Step 6 If there is no file needed for the upgrade in the software repository. Click Import to import

the upgrade file to the software repository. And then select the file to be upgraded and the

related target upgrade file.

Step 7 Set the start time. If you do not set the start time, the upgrade task is performed as soon as the

task is created.

Step 8 Click Next Step to configure whether to activate the upgrade file. If you select activating the

upgrade file, the device is rebooted after the task is finished. Otherwise, the device is not

rebooted.


Acknowledging upgrade

To acknowledge the upgrade operation, follow these steps:


Step 2 View information displayed at the Status field.

Downloading files

When the data center upgrades or recovers device files, it automatically downloads files. The

data center downloads the NE software, patches, and configuration data to NEs in a related

form and activates them to finish upgrade and switch versions. The status of downloaded files

is displayed at the Description filed.

Activating tasks

After executing upgrade tasks, you can activate tasks that are not activated.

The activation operation may lead to rebooting the device and then interrupting services. Be careful to perform the operation. After activation, the device uses the upgraded system software when being started.

To activate tasks, follow these steps:

Raisecom




Step 1 From the NView NNM system menu, choose Data Center > Task Management. A window

is displayed.

Step 2 Select a task from the Waiting for Activation area of the left upgrade task classification tree.

Step 3 Confirm the detailed information of the task and the device related to the upgrade task.

Step 4 Choose Activate from the right-click menu.

Step 5 View the task status after performing activation.

You can upgrade the iTN201 periodically. For details, see NView NNM User Guide (Data Center).

18.3.2 Periodical upgrade

Periodical upgrade is mainly used for the administrator to perform upgrade through the data

center at some time. To perform periodical upgrade, follow these steps:


Step 2 Right-click the blank area and then choose Create NE Upgrade Task from the right-click

menu.

Step 3 Enter the task name.

Step 4 Select the NE to be upgraded and relate it to the upgrade task. The NView NNM system

support selecting a NE based on its type, IP address, NE version, card classification, card type,

and card version.

Step 5 Select the file to be upgraded and the related target upgrade file. By selecting different version,

you can realize upgrade.

Step 6 If there is no file needed for the upgrade in the software repository. Click Import to import

the upgrade file to the software repository. And then select the file to be upgraded and the

related target upgrade file.

Step 7 Set the start time at the Start Time drop-down list. And then click OK.

Step 8 Click Next Step.


During a task is being created, you set the time and period. The system will

automatically perform the task at the specified time or in a specified period. You can manually start/stop a task by choosing Data Center > Task Management from the system menu of the NView NNM system.

You can perform rollback and recovery operation on the software version. Rollback refers to rolling the software back to the one before upgrade. Recovery refers to return the current software to a specified version. The rollback operation cannot select a software version manually while the recovery operation can manually select the software version.

Raisecom




18.3.3 Backup

Backup is an important part of the operation and maintenance operation. The backup

operation supports backing up the system software and the configuration data file of the

device or cards.

Backing up device files

To back up a device file, follow these steps:


Step 2 Select a device from the left device tree.

Step 3 Select the Device View tab.

Step 4 Select the device that needs to be backed up based on the query fields.

Step 5 Right-click the device and then choose Backup from the right-click menu.

Step 6 Select the file that needs to be backed up and confirm the backup information.

Step 7 Click OK.

Acknowledging backup

To acknowledge the backup operation, follow these steps:

Step 1 The status of the device is displayed at the Operation Status field of the window.

Step 2 During backup, several dialog boxed are displayed to prompt the current device status.

Step 3 The backed up file will be added to the backup base.

You can back up device file periodically. For details, see NView NNM User Guide (Data Center).

18.3.4 Periodically automatic backup

The periodically automatic backup is a commonly-performed task. With the periodically

automatic backup function, the data center can dramatically reduce repetitive tasks. When a

backup policy is configured and enabled, and the backup policy is related to a specified

device, the device can use the backup policy to perform the periodically automatic backup

function.

To perform periodically automatic backup, follow these steps:

Step 1 Choose Data Center > Backup Policy from the system menu of the NView NNM system.

Step 2 Right-click a node at the left backup policy tree and then choose Add from the right-click

menu.

Step 3 Enter the policy name and select a file.

Step 4 Select the backup policy period, backup policy time, and backup policy date.

Step 5 Enable/Disable the policy.

Raisecom




Step 6 Click OK.

Step 7 Select the No Backup node at the left backup policy tree.

Step 8 Select the Device View Tab.

Step 9 Select a record about a NE that needs to use the backup policy.

Step 10 Click Alter Backup Policy.

Step 11 Click OK.

Raisecom


Element Management) 19 Appendix


19 Appendix

This chapter describes terms and abbreviations involved in this guide and provides the alarm

list and performance list supported by the iTN201, including the following sections:

Terms

Abbreviations

Alarm list

Performance list

19.1 Terms

A

Access Control

List (ACL)

A series of orderable rules composed by permit | deny sentences. The

device decides the packets to be received/refused based on these rules.

Alarm The reported information when device or network management system

detects failure.

Alarm auto-

Report

The device sends alarms that meet report rules to the NView NNM

system automatically.

Alarm filtering The NView NNM system cannot receive alarms that meet filtering

rules.

Alarm inverse For interfaces that do not transmit service, alarm inverse is used to

avoid generating related alarms.

Alarm shielding On the host, an alarm management method through which you can set

conditions for the system to discard (not to save, display, or query for)

the alarm information meeting the conditions.

Automatic

Protection

Switching (APS)

When a device fails, services are automatically switched to the backup

device to ensure proper communication.

B

Raisecom




Board An electronic module, composed by the chip and other electronic

components installed on a flat and hard Printed Circuit Board (PCB).

The PCB has conductive circuits for connecting these components.

C

Collision A state that 2 packets are co-transmitted through a medium. These 2

packets cannpt be identified because of interference.

Connectivity Fault

Management

(CFM)

A standard defined by IEEE. It defines protocols and practices for

OAM (Operations, Administration, and Maintenance) for paths through

802.1 bridges and local area networks (LANs). Used to diagnose fault

for EVC (Ethernet Virtual Connection). Cost-effective by fault

management function and improve Ethernet maintenance.

Control Word The control word is a 4-byte TDM service data encapsulation packet

header, used for circuit emulation services. The control word is mainly

used to indicate a packet sequence number, link faults, shorter

encapsulation packet, and encapsulation packet type.

Current alarm Alarms that are in unclear, unclear but acknowledged, cleared but not

acknowledged modes are called current alarms

Customer Customer uses device provided service; the customer information can

associate with NE, alarm and can only be stored in network

management system.

D

Data Center

It is a program provifing auxiliary function. It can back up, upgrade the

system software and configuration file, as well as maintain their

versions.

Device Scan The device can scan devices whose IP addresses in the IP address range

and add them to the NView NNM system automatically.

Domain The domain takes the NE as the minimum granularity, where you can

perform resource collection.

Dynamic Host

Configuration

Protocol (DHCP)

A technology used for assigning IP address dynamically. It can

automatically assign IP addresses for all clients in the network ro

resuce workload of the administrator. In addition, it can realize

centralized management of IP addresses.

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




Ethernet Ethernet is created by the Xerox company initially. Xerox convinced

Digital Equipment Corporation (DEC), Intel, and Xerox to work

together to promote Ethernet as a standard. It is the most widely-used

Local Area Network (LAN). The speed of Ethernet includes 10 Mbit/s,

100 Mbit/s, 1000 Mbit/s, and 10 Gbit/s. Ethernet adopts the CSMA/CD

access control mode and complies with the IEEE802.3 standard.

Ethernet in the

First Mile (EFM)

Complied with IEEE 802.3ah protocol, Ethernet in the First Mile

(EFM) is a link-level Ethernet OAM technology. It provides the link

connectivity detection function, link fault monitor function, and remote

fault notification function, etc for a link between two directly

connected devices. EFM is mainly used for Ethernet link on edges of

the network accessed by users.

Ethernet Linear

Protection

Switching (ELPS)

An APS (Automatic Protection Switching) protocol based on ITU-T

G.801 Recommendation to provide backup link protection and

recovery switching for Ethernet traffic in a ring topology and at the

same time ensuring that there are no loops formed at the Ethernet layer.

Ethernet Ring

Protection

Switching (ERPS)

A protocol based on ITU-T G.8032 APS (Automatic Protection

Switching) to protect an Ethernet connection. It is a kind of end-to-end

protection technology. Including two linear protection modes: linear

1:1 protection switching and linear 1+1 protection switching.

F

Failover Provide a port association solution, extending link backup range.

Transport fault of upper layer device quickly to downstream device by

monitoring upstream link and synchronize downstream link, then

trigger switching between master and standby device and avoid traffic

loss.

Forced Switch In forced switch mode, services are forced to be switched from the

working channel to the protection channel. The force switching cannot

be automatically recovered until the protection card or channel is

satisfying higher-level protection switch requests, regardless whether

the protection channel or card is normal.

Frame A unit of data transmission

Full duplex Also called duplex. Refers to two-way electronic communication that

takes place in both directions at the same time.

H

Half duplex Refers to two-way electronic communication that takes place

unidirectionally at a time. Communication between people is half-

duplex when one person listens while the other speaks.

History Alarm All cleared/filtered alarms

I

Raisecom




In-band Network

Management

It refers that the NView NNM system and the device transmit data

through the service channel.

Internet

Engineering Task

Force (IETF)

It is estanlished in 1985. It is the most authoritative technology and

standard organization, which develops and formulate specifications

related to the Internet.

Inventory Various resources in network management system.

J

Jitter Buffer When packets are transmitted in the PSN, delay will be generated,

which influence the performance of emulation services. The Jitter

Buffer can be used to reduce the influence caused by delay. Jitter

Buffer is used to contain earlier or later-received packets.

Requirements are introduced to the distribution of Jitter Buffer

capacity. If the capacity is too larger, the buffer overflow can be

prevented. However, longer delay will be generated. If the capacity is

too small, it will cause buffer overflow. Therefore, you should set an

appropriate value for the Jitter Buffer capacity.

L

License The authorization file of the NView NNM system, which specify

network management functions available for a user.

Link Aggregation A computer networking term which describes using multiple network

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.

Local Area

Network

A small telecommunication network where multiple devices are

connected to share resources and tansmit data.

Loopback A process that a signal is sent back to the original place. It is used to

detect and analyze faults that may exist in the network.

M

MA

The service instance is also called a Maintenance Association (MA). It

is a part of a MD. One MD can be divided into one or multiple service

instances. One service instance corresponds to one service and is

mapped to a group of VLANs. VLANs of different service instances

cannot cross.

Manual Switch A protection switch mode. If the protection is normal and there is no

higher-level protection switching requirement, in the manual switching

mode, services are manually switched from the working channel to the

protection channel (vice versa) to test whether the network protection

ability.

Mapping SDH mapping refers mapping tributary signals to the VC at the edge of

the SDH network.

http://en.wikipedia.org/wiki/Computer_networking

http://en.wikipedia.org/wiki/Redundancy_(engineering)

Raisecom




MD

Maintenance Domain (MD), also called Maintenance Entity Group

(MEG), is a network that runs CFM. It defines network range of OAM

management. MD has a level property, with 8 levels (level 0 to level

7). The bigger the number is, the higher the level is and the larger the

MD range is. Protocol packets in a lower-level MD will be discarded

after entering a higher-level MD. If no Maintenance association End

Point (MEP) but a Maintenance association Intermediate Point (MIP) is

in a high-level MD, the protocol can traverse the higher-level MD.

However, packets in a higher-level MD can traverse lower-level MDs.

In the same VLAN range, different MDs can be adjacent, embedded,

but not crossed.

MEP

The MEP is an edge node of a service instance. MEPs can be used to

send and process CFM packets. The service instance and the MD

where the MEP locates decide VLANs and levels of packets received

and sent by the MEP.

Message

In the data communication filed, the message has a fixed structure. The

destination address is defined in the header. The text is the real

message, which contains information that can stop the operation.

MIP

The MIP is the internal node of a service instance, which is

automatically created by the device. MIP cannot actively send CFM

packets but can process and response to LinkTrace Message (LTM)

and LoopBack Message (LBM) packets.

Mobile Backhaul Solve communication problem from BTS to BSC for 2G, NodeB to

RNC for 3G.

Mobile backhaul for 2G focuses on voice service, not request high

bandwidth, implemented by TDM microwave or SDH/PDH device.

In 3G times, lots of data service as HSPA, HSPA+, etc concerning to

IP service, voice is changing to IP as well, namely IP RAN, to solve

problem of IP RAN mobile backhaul is solving whole network

backhaul, satisfying both data backhaul and voice transportation over

IP (clock synchronization).

MP MEP and MIP are called MP.

N

Network Element Network device takes management in network management system as

network element

Network

Management

System

A PC program used to manage network devices

Network Time

Protocol (NTP)

A time synchronization protocol defined by RFC1305. It is used to

synchronize time between distributed timer server and clients. NTP is

used to perform clock synchronization on all devices in the network

that support clock. Therefore, devices can provide different

applications based on some time. In addition, NTP can ensure very

high accuracy (about 10ms).

Raisecom




NMS Monitor Auxiliary program of network management system, which can manage

various service programs in network management system and monitor

network management system operating status.

Node General terms of subnet, NE and symbols in network management

system.

Northbound

Interface

The interface between the NView NNM system and the upper layer.

The upper layer can manage all devices throught he Northbound

Interface.

O

Operate Privilege The authority used to operate and manage the NView NNM system and

its resources.

Out-of-band

Network

Management

It refers that the NView NNM system and the device transmit data

through an independent channel.

P

Packet Loss Ratio The percentage of packets that are not forwarded because of bandwidth

lack.

Performance

Monitor

Network management system collects and shows device flow, packet

loss and other performance data.

Polling It can be used to periodically detect whether the device is off line.

Precision Time

Protocol (PTP)

IEEE 1588 v2 protocol is also called PTP (Precision Time Protocol), a

high-precision time protocol for synchronization used in measurement

and control systems residing on a local area network. Accuracy in the

sub-microsecond range may be achieved with low-cost

implementations.

Q

Quality of Service

(QoS)

A commonly-used performance indicator of a telecommunication

system or channel. Depending on the specific system and service, it

may relate to jitter, delay, packet loss ratio, bit error ratio, and signal-

to-noise ratio. It functions to measure the quality of the transmission

system and the effectiveness of the services, as well as the capability of

a service provider to meet the demands of users.

R

RADIUS A protocol used to authenticate and account users in the network

Rapid Spanning

Tree Protocol

(RSTP)

RSTP is an extension of Spanning Tree Protocol, which realizes quick

convergency of network topology.

Raisecom




Resource Management objects in network management system, including device,

chassis, card, port and etc.

S

Self-adaption Refer that an interface automatically selects the speed and duplex mode

based on the negotiation results.

SNMP (Simple

Network

Management

Protocol)

A network management protocol defined by Internet Engineering Task

Force (IETF) used to manage devices in the Internet. SNMP can make

the network management system to remotely manage all network

devices that support SNMP, including monitoring network status,

modifying network device configurations, and receiving network event

alarms. At present, SNMP is the most widely-used network

management protocol in the TCP/IP network.

SNTP (Simple

Network Time

Protocol)

SNTP is mainly used for synchronizing time of devices in the network.

Spanning Tree

Protocol (STP)

STP can be used to emiliate network loops and back up link data. It

blocks loops in logic to prevent broadcast storms. When the unblocked

link fails, the blocked link is re-activated to act as the protection link.

Subnet Subnet refers to the logical division of network topology structure in

network management system, which can help show NE topology

structure clearly in network management system. The subnet interior

can contain subnet, NE, symbol, and link etc topology nodes.

Symbol Symbol is schematic topology node, which cannot take network

management, but give better display to network structure.

Synchronization Network management system updates device resource or alarm

information in database by synchronization function to make network

management system correspondence with device.

Syslog Device logs that meet Syslog protocol format defined in RFC3164.

T

Throughput The maximum speed supported by a device without losing packets.

Timeslot Divide time into periodic frames and each frame is further divided into

multiple time slots. Each time slot is a communication channel

assigned to users.

Topology Graphical network structure in network management system, which

can show networking situation, subnet/NE alarm and online status

intuitionally.

Topology

Discovery

A technology used to identify network topology accurately. It is

realized through several network architecture assumption and simple

tools.

Trap A mode for the device sending alarms to the NView NNM system. It is

sent to the NView NNM system through the SNMP packet.

Raisecom




Trap Inhibit The device reports the root source alarm. The attached alarms are not

reported to the NView NNM system.

Trunk Group Bind multiple member interfaces to a logical link. It is used to enlarge

the bandwidth for sharing load balancedly.

U

User Network management system client user; the collection of user and

user group management domain and operation permission confirms

network management function used by user.

V

Virtual Local

Area Network

(VLAN)

Partition network resources and users in logically. A physical LAN can

be partitioned into multiple VLANs in logical.

19.2 Abbreviations

A

AC Alternating Current

AC Attachment Circuit

ACL Access Control List

AES Advanced Encryption Standard

AIS Alarm Indication Signal

APS Automatic Protection Switching

ARP Address Resolution Protocol

ATM Asynchronous Transfer Mode

B

BC Boundary Clock

BGP Border Gateway Protocol

BITS Building Integrated Timing Supply System

BPDU Bridge Protocol Data Unit

BSC Base Station Controller

BTS Base Transceiver Station

C

Raisecom




CC Continuity Check

CCC Circuit Cross Connect

CCM Continuity Check Message

CE Conformite Europeenne

CE Customer Edge

CFM Connectivity Fault Management

CIST Common Internal Spanning Tree

CLI Command Line Interface

CoS Class of Service

CPU Central Processing Unit

CRC Cyclic Redundancy Check

D

DC Direct Current

DES Data Encryption Standard

DHCP Dynamic Host Configuration Protocol

DNS Domain Name System

DRR Deficit Round Robin

DS Differentiated Services

DSCP Differentiated Services Code Point

E

EFM Ethernet in the First Mile

ELPS Ethernet Linear Protection Switching

ERPS Ethernet Ring Protection Switching

EVC Ethernet Virtual Connection

F

FEC Forwarding Equivalence Class

FM Fault Management

FPGA Field-Programmable Gate Array

FTP File Transfer Protocol

G

GARP Generic Attribute Registration Protocol

Raisecom




GUI Graphical User Interface

GVRP Generic VLAN Registration Protocol

I

IANA Internet Assigned Numbers Authority

ICMP Internet Control Message Protocol

IEEE Institute of Electrical and Electronics Engineers

IETF Internet Engineering Task Force

IGMP Internet Group Management Protocol

IP Internet Protocol

ISP Internet Service Provider

iTN intelligent Transport Network

ITU-T International Telecommunications Union - Telecommunication

Standardization Sector

L

LACP Link Aggregation Control Protocol

LB Loop Back

LBM LoopBack Message

LBR LoopBack Reply

LDP Label Distribution Protocol

LER Label Edge Router

LLDP Link Layer Discovery Protocol

LLDPDU Link Layer Discovery Protocol Data Unit

LT Link Trace

LTM LinkTrace Message

LTR Link Trace Reply

M

MA Maintenance Association

MAC Medium Access Control

MD Maintenance Domain

MD5 Message-Digest Algorithm 5

MDI Medium Dependent Interface

Raisecom




MEF Metro Ethernet Forum

MEG Maintenance Entity Group

MEP Maintenance associations End Point

MIB Management Information Base

MIP Maintenance association Intermediate Point

MP Maintenance Point

MTU Maximum Transmission Unit

N

NCIA North CORBA Interface Agent

NMS Network Management System

NNM Network Node Management

NSIA North Socket Interface Agent

NTP Network Time Protocol

NView NNM NView Network Node Management

O

OAM Operation, Administration and Management

OID Object Identifiers

OOS Out of Service

P

P2P Point-to-Point

PC Personal Computer

PCM Pulse Code Modulation

PDH Plesiochronous Digital Hierarchy

PDU Protocol Data Unit

PE Provider Edge

PHP Penultimate Hop Popping

PM Performance Monitoring

P-MBH Packet-based Mobile Backhaul

PPP Point to Point Protocol

PSN Packet Switched Network

Raisecom




Q

QoS Quality of Service

R

RADIUS Remote Authentication Dial In User Service

RARP Reverse Address Resolution Protocol

RED Random Early Detection

RMEP Remote Maintenance association End Point

RMON Remote Network Monitoring

RNC Radio Network Controller

RNDP Raisecom Neighbour Discover Protocol

ROS Raisecom Operating System

RPL Ring Protection Link

RSTP Rapid Spanning Tree Protocol

S

SD Signal Detect

SDH Synchronous Digital Hierarchy

SES Severely Errored Second

SFP Small Form-factor Pluggable

SHA Secure Hash Algorithm

SLA Service Level Agreement

SMTP Simple Mail Transfer Protocol

SNTP Simple Network Time Protocol

SP Strict-Priority

SSHv2 Secure Shell version 2

SVC Switching Virtual Circuit

T

TACACS Terminal Access Controller Access Control System

TACACS+ Terminal Access Controller Access Control System

TC Transparent Clock

TCI Tag Control Information

TCP Transmission Control Protocol

Raisecom




TD-SCDMA Time Division-Synchronous Code Division Multiple Access

TFTP Trivial File Transfer Protocol

TLV Type Length Value

ToS Type of Service

TP Tunneling Protocol

TPID Tag Protocol Identifier

TTL Time To Live

U

UDP User Datagram Protocol

UNI User Network Interface

URL Uniform Resource Locator

USM User-Based Security Model

V

VC Virtual Container

VLAN Virtual Local Area Network

VoIP Voice over IP

VPN Virtual Private Network

W

WCDMA Wideband Code Division Multiple Access

WRED Weighted Random Early Detection

WRR Weight Round Robin

X

XML Extensible Mark-up Language

19.3 Alarm list

No. Alarm name

1 Cold boot

2 SNMP authentication failure

Raisecom




No. Alarm name

3 Online upgrade/backup failure

4 Online upgrade/backup success

5 SFP module pulled out

6 SFP module plugged in

7 Interface Link Down

8 Interface Link Up

9 Optical interface SD alarm

10 Optical interface SD alarm recovered

11 Power supply Down

12 Power supply Up

13 Power supply Deleted

14 Failover

15 Fault return

16 Far End Fault Indication (FEFI)

17 Far End Fault Indication (FEFI) recovered

18 Configuration operation

19 RMON falling

20 RMON rising

21 KeepAlive

22 Loop interface DOWN

23 Loop interface UP

24 OAM discovery alarm

25 OAM peer device loss

26 Extended OAM upgrade/backup finished

27 OAM remote loopback timeout

28 LinkFault

29 LinkFault recovered

30 DyingGasp event

31 DyingGasp event recovered

32 CriticalLink event

33 CriticalLink event recovered

Raisecom




No. Alarm name

34 Backup port valid

35 Primary port valid

36 Ethernet port status: blocked

37 Ethernet port status: Forwarding

38 Intra-connection failure

39 CCM error

40 Port failure

41 Remote MEP failure

42 Remote Defect Indication (RDI)

43 Remote Defect Indication (RDI) recovered

44 Port failure recovered

45 LOF rate alarm rising threshold

46 LOF rate alarm falling threshold

47 Frame delay rising threshold

48 Frame delay falling threshold

49 Frame delay jitter rising threshold

50 Frame delay jitter falling threshold

51 Remote MEP failure recovered

52 Loopback generated

53 Loopback cleared

54 CFM failure recovered

55 CCM error recovered

56 Intra-connection failure recovered

57 SFP module pulled out

58 SFP module plugged in

59 SFP operation abnormal

60 SFP operation normal

61 SFP Rx signal loss

62 SFP Rx signal normal

63 SFP password check failure

64 SFP password check success

Raisecom




No. Alarm name

65 SFP performance parameter high

66 SFP performance parameter low

67 LLDP neighbor change

68 Card plugged in

69 Card pulled out

70 Fan rotational speed normal

71 Fan rotational speed abnormal

72 Fan sub-card plugged in

73 Fan sub-card pulled out

74 Online upgrade

75 Alarm information

76 dFOP Trap generated

77 dFOP Trap cleared

78 Working status no apply

79 Protection status no apply

80 Lock protection

81 Linear protection switching FS

82 Working entity signal invalid

83 Protection entity signal invalid

84 Linear protection switching MS

85 Wait to recover

86 No recover

87 Service blocked

88 Service forwarded

89 Loopback protection idle

90 Loopback protection on-going

91 Loopback protection FS

92 Loopback protection MS

93 Clear MS

94 Protocol mismatch error

95 MS to working line

Raisecom




No. Alarm name

96 Loopback protection suspend

97 Alarm Indication Signal (AIS)

98 Alarm Indication Signal (AIS) recovered

99 LCK

100 LCK recovered

101 Customer signal loss

102 Customer forwarding failure

103 Customer switching failure

104 Customer failure cleared

105 Unexpected MA ID(MMG)

106 Unexpected MA level(UNL)

107 Unexpected MEP ID(UNM)

108 Unexpected period(UNP)

109 Detected unexpected failure

110 Loss of Connectivity (LOC)

111 FEFI detected

112 External clock signal LOS cleared

113 External clock signal LOF cleared

114 External clock signal AIS cleared

115 Unexpected MA ID(MMG) recovered

116 Unexpected MA level(UNL) recovered

117 Unexpected MEP ID(UNM) recovered

118 Unexpected period(UNP) recovered

119 Loss of Connectivity (LOC) recovered

120 FEFI recovered

121 Local error symbol event

122 Local error symbol event recovered

123 Local error frame period event

124 Local error frame period event recovered

125 Local error frame event

126 Local error frame event recovered

Raisecom




No. Alarm name

127 Local error frame second event

128 Local error frame second recovered

129 Local error symbol event

130 Local error symbol event recovered

131 Local error frame period event

132 Local error frame period recovered

133 Local error frame event

134 Local error frame event recovered

135 Local error frame second event

136 Local error frame second recovered

19.4 Performance list

Collection resource Metric clafficiation name Metric name

Ethernet interface Ethernet interface

performance

Packet loss ratio

Number of unicast packets

Bandwidth utilization

Number of broadcast packets

Rate

Number of multicast packets

Error packet rate

Address: Building 2, No. 28, Shangdi 6th Street, Haidian District, Beijing, P.R.China.

Postal code: 100085 Tel: +86-10-82883305

Fax: 8610-82883056 http://www.raisecom.com Email: [email protected]

Date post:	20-Aug-2020
Category:	Documents
Upload:	others
View:	45 times
Download:	8 times

NView NNM (V5) Operation Guide (iTN201 Network Element ... Kuwait/NView NNM (V5...NView NNM (V5)...

Documents