En Quidview Adoc Device Manager UM I V3.11(20060809)

Quidview Device Manager

User Manual Volume I

Hangzhou Huawei-3Com Technology Co., Ltd.

http://www.huawei-3com.com

Manual Version: T2-08016J-20060804-C-3.11

Product Version: V3.10

Copyright © 2006, Hangzhou Huawei-3Com Technology Co., Ltd. and its licensors

All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Hangzhou Huawei-3Com Technology Co., Ltd.

Trademarks

H3C, Aolynk, , IRF, H3Care,

, Neocean, , TOP G, SecEngine, SecPath, COMWARE, VVG, V2G, VnG, PSPT, NetPilot, and XGbus are trademarks of Hangzhou Huawei-3Com Technology Co., Ltd.

All other trademarks that may be mentioned in this manual are the property of their respective owners.

Notice

The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.

To obtain the latest information, please access:


Technical Support

[email protected]


mailto:[email protected]

http://www.huawei-3com.com/

About This Manual

Related Documentation

Manual Description

Quidview Device Manager User Manual Volume II

The manual provides the introduction to the management function of Quidview Device Manager on Ethernet switches.

Organization

Quidview Device Manager User Manual Volume I is organized as follows:

Chapter Contents

1 Overview Introduces briefly Quidview Network Management System and profiles the features and applicable scope of Quidview Device Manager.

2 General Functionalities Focuses on the startup methods and main menu functions of Quidview Device Manager.

3 Device Management Details the configuration management functions of Quidview Device Manager specific to devices.

4 Port Management Describes in detail how to browse and configure port in Quidview Device Manager.

5 Performance Monitoring Describes in detail how to monitor the performances of different objects in Quidview Device Manager.

6 RMON Management Introduces the RMON management of Quidview Device Manager on devices.

7 VLAN Management Describes in detail how to query, create, delete and configure core routers, S8016 VLAN and VLAN Trunk in Quidview Device Manager.

8 RSTP Management Describes in detail how to configure the RSTP on core routers, S8016 device and ports in Quidview Device Manager.

9 Routing Protocol Management

Describes in detail how to browse routing protocols (RIP, OSPF and BGP) in Quidview Device Manager.

Chapter Contents

10 S8016 NAT Management Elaborates on the management over the NAT function of S8016 switch in Quidview Device Manager.

11 Ethernet Interface Configuration

Describes in detail the configuration, querying and statistics making of Ethernet interface in Quidview Device Manager.

12 Ethernet Trunk Management

Describes in detail how to add, delete, configure and query Ethernet Trunk in Quidview Device Manager.

13 IP Trunk Management Describes in detail how to add, delete, configure and query IP Trunk in Quidview Device Manager.

14 POS Interface Management

Describes in detail how to configure and query POS interface in Quidview Device Manager.

15 RPR Interface Management

Describes in detail the configuration, querying and statistics making of RPR interface in Quidview Device Manager.

16 CPOS Port Management Details about the configuration, query, and statistics collection of CPOS interface in Quidview Device Manager.

17 ATM Interface Management

Details about the configuration, query, and statistics collection of ATM interface in Quidview Device Manager.

18 Portal Configuration Concentrates on the configuration of Portal service for the high end router in Quidview Device Manager.

19 Voice Management Describes in detail the configuration, querying and statistics making of voice services in Quidview Device Manager.

20 POS Access Management

Describes in detail the POS access management of Quidview Device Manager.

21 NDEC Management Tells about the management over the encryption cards in Quidview Device Manager.

22 Terminal Server Management

Describes the management over the terminal application in Quidview Device Manager.

23 DLSW Service Management

Goes into particulars of the management of DLSW service in Quidview Device Manager.

24 DHCP Management Introduces the configuration of the DHCP function of the core router and S8016 switch in Quidview Device Manager.

25 Frame Relay Management

Introduces the configuration of the frame relay in Quidview Device Manager.

Conventions

The manual uses the following conventions:

I. GUI conventions

Convention Description

< > Button names are inside angle brackets. For example, click <OK>.

[ ] Window names, menu items, data table and field names are inside square brackets. For example, pop up the [New User] window.

/ Multi-level menus are separated by forward slashes. For example, [File/Create/Folder].

II. Symbols

Convention Description

Caution Means reader be careful. Improper operation may cause data loss or damage to equipment.

Note Means a complementary description.

User Manual Volume I Quidview Device Manager Table of Contents

i

Table of Contents

Chapter 1 Overview....................................................................................................................... 1-1 1.1 Introduction of Quidview Network Management System................................................... 1-1 1.2 Overview of Quidview Device Manager............................................................................. 1-1

Chapter 2 General Functionalities ............................................................................................... 2-1 2.1 Starting Quidview Device Manager ................................................................................... 2-1

2.1.1 Starting Quidview Independently ............................................................................ 2-1 2.1.2 Starting Quidview on Quidview NMF Topology Platform........................................ 2-4 2.1.3 Starting Quidview on SNMPc Topology Platform ................................................... 2-4 2.1.4 Starting Quidview on HP OpenView ....................................................................... 2-4 2.1.5 Starting on N2000 EMF Platform ............................................................................ 2-4

2.2 Introduction to Menu Functions ......................................................................................... 2-5 2.2.1 System .................................................................................................................... 2-5 2.2.2 Device ................................................................................................................... 2-11 2.2.3 View....................................................................................................................... 2-12 2.2.4 Tools...................................................................................................................... 2-13 2.2.5 Help ....................................................................................................................... 2-14 2.2.6 Pop-up Menu......................................................................................................... 2-15

2.3 Introduction to Toolbar..................................................................................................... 2-15 2.4 Device Pane and Function Pane ..................................................................................... 2-17

2.4.1 Device Pane.......................................................................................................... 2-17 2.4.2 Function Pane ....................................................................................................... 2-17

2.5 Information Display Area ................................................................................................. 2-17 2.6 Message Window............................................................................................................. 2-18 2.7 Status Bar ........................................................................................................................ 2-18

Chapter 3 Device Management .................................................................................................... 3-1 3.1 Panel Monitoring................................................................................................................ 3-1 3.2 System Information............................................................................................................ 3-1 3.3 Board Browsing.................................................................................................................. 3-5

3.3.1 Board Browsing for Routers .................................................................................... 3-5 3.3.2 Module Information Browsing of Switches .............................................................. 3-7

3.4 SubCard Browsing of Routers ........................................................................................... 3-9 3.5 Clock Source Browsing.................................................................................................... 3-10 3.6 Fan Browsing................................................................................................................... 3-10 3.7 Power Browsing............................................................................................................... 3-12 3.8 Active/Standby Switching ................................................................................................ 3-13 3.9 Attribute Config ................................................................................................................ 3-14 3.10 Card Reset..................................................................................................................... 3-14


ii

3.11 L2 Forwarding Table Management................................................................................ 3-14 3.11.1 Querying L2 Forwarding Table Information ........................................................ 3-14 3.11.2 Creating L2 Forwarding Entry ............................................................................. 3-15 3.11.3 Deleting L2 Forwarding Entry.............................................................................. 3-16 3.11.4 Configuring L2 Forwarding Entry ........................................................................ 3-16 3.11.5 Querying and Configuring L2 Forwarding Table Aging Time.............................. 3-16

3.12 Environment Monitor...................................................................................................... 3-17 3.13 Saving Configuration ..................................................................................................... 3-17 3.14 Resetting Device............................................................................................................ 3-17

Chapter 4 Port Management......................................................................................................... 4-1 4.1 Port Browsing..................................................................................................................... 4-1 4.2 Subport Browsing............................................................................................................... 4-3 4.3 Port Time Slot .................................................................................................................... 4-3 4.4 Port Up/Down Configuration .............................................................................................. 4-4 4.5 Port Mirror Management.................................................................................................... 4-4

4.5.1 Monitoring Port Management.................................................................................. 4-5 4.5.2 Port Mirror Management ......................................................................................... 4-6

4.6 Port L2/L3 Configuration.................................................................................................... 4-7 4.7 Link-aggregation Management .......................................................................................... 4-8

4.7.1 Querying Link-aggregation Information................................................................... 4-8 4.7.2 Add Link-aggregation .............................................................................................. 4-9 4.7.3 Delete Link-aggregation ........................................................................................ 4-10 4.7.4 Config Link-aggregation ........................................................................................ 4-11

Chapter 5 Performance Monitoring ............................................................................................. 5-1 5.1 Operation Description ........................................................................................................ 5-1 5.2 Device Monitoring .............................................................................................................. 5-2 5.3 Port Monitoring................................................................................................................... 5-2 5.4 System Monitoring ............................................................................................................. 5-3 5.5 Card Monitoring ................................................................................................................. 5-3

Chapter 6 RMON Management..................................................................................................... 6-1 6.1 Configuration and Real-time Monitoring of Statistics Group ............................................. 6-1

6.1.1 Add a Statistics Item ............................................................................................... 6-2 6.1.2 Delete a Statistics Item ........................................................................................... 6-3 6.1.3 Real-time Monitoring ............................................................................................... 6-3

6.2 Configuration and Data Browsing of History Group........................................................... 6-6 6.2.1 Configuration of History Group................................................................................ 6-6 6.2.2 Data Browsing of History Group.............................................................................. 6-8

6.3 Configuration and Data Browsing of Alarm Group ............................................................ 6-9 6.3.1 Adding an Alarm Item............................................................................................ 6-10 6.3.2 Configuring an Alarm Item .................................................................................... 6-12 6.3.3 Deleting Alarm Items............................................................................................. 6-12


iii

6.3.4 Displaying Invalid Alarm Items .............................................................................. 6-12 6.4 Configuration and Log Browsing of Event Group ............................................................ 6-13

6.4.1 Adding an Event Item............................................................................................ 6-13 6.4.2 Deleting Event Items ............................................................................................. 6-15 6.4.3 Displaying Invalid Event Items .............................................................................. 6-15 6.4.4 Browsing Log Information Related to the Specified Event.................................... 6-16

6.5 Configuration and Data Browsing of Alarm Extended Group .......................................... 6-16 6.5.1 Adding an Alarm Extended Item ........................................................................... 6-18 6.5.2 Configuring an Alarm Extended Item .................................................................... 6-20 6.5.3 Deleting Alarm Extended Items............................................................................. 6-20 6.5.4 Displaying Invalid Alarm Extended Items.............................................................. 6-20

6.6 Browsing of Log Information ............................................................................................ 6-21

Chapter 7 VLAN Management ...................................................................................................... 7-1 7.1 VLAN Management ........................................................................................................... 7-1

7.1.1 Querying VLAN Information .................................................................................... 7-1 7.1.2 Creating Common VLAN......................................................................................... 7-2 7.1.3 Deleting VLAN......................................................................................................... 7-3 7.1.4 Configuring Common VLAN.................................................................................... 7-3 7.1.5 Configuring Aggregate VLAN.................................................................................. 7-3 7.1.6 Setting Common VLAN as Aggregate VLAN.......................................................... 7-4

7.2 VLAN Interface Management ............................................................................................ 7-4 7.2.1 Querying VLAN Interface Information ..................................................................... 7-4 7.2.2 Creating VLAN Interface ......................................................................................... 7-5 7.2.3 Deleting VLAN Interface.......................................................................................... 7-6 7.2.4 Configuring VLAN Interface .................................................................................... 7-6

7.3 VLAN Trunk Management ................................................................................................. 7-7 7.3.1 Querying Trunk Port Information............................................................................. 7-7 7.3.2 Creating Trunk Port................................................................................................. 7-8 7.3.3 Deleting Trunk Port ................................................................................................. 7-9 7.3.4 Configuring Trunk Port ............................................................................................ 7-9

Chapter 8 RSTP Management ...................................................................................................... 8-1 8.1 Device RSTP Configuration............................................................................................... 8-1 8.2 Port RSTP Management.................................................................................................... 8-3

Chapter 9 Routing Protocol Management .................................................................................. 9-1 9.1 Overview ............................................................................................................................ 9-1 9.2 Browsing of RIP Information .............................................................................................. 9-3

9.2.1 Interface Configuration............................................................................................ 9-4 9.2.2 Interface Statistics................................................................................................... 9-5 9.2.3 Peer Information...................................................................................................... 9-6

9.3 Browsing of OSPF Information .......................................................................................... 9-6 9.3.1 OSPF Attribute ........................................................................................................ 9-7


iv

9.3.2 OSPF Area Information........................................................................................... 9-8 9.3.3 LSDB Information.................................................................................................. 9-10 9.3.4 OSPF Interface...................................................................................................... 9-11 9.3.5 Peer Information.................................................................................................... 9-13 9.3.6 Virtual Link Information ......................................................................................... 9-14

9.4 Browsing of BGP Information .......................................................................................... 9-16 9.4.1 BGP Attribute ........................................................................................................ 9-17 9.4.2 Peer Information.................................................................................................... 9-18 9.4.3 BGP4 Path Information ......................................................................................... 9-20

9.5 Routing Protocol Enable Configuration ........................................................................... 9-22 9.6 Browsing of Routing Table............................................................................................... 9-22

9.6.1 Static Routing Information..................................................................................... 9-23 9.6.2 Dynamic Routing Information................................................................................ 9-24

Chapter 10 S8016 NAT Management......................................................................................... 10-1 10.1 NAT Board Attribute and Monitor................................................................................... 10-2

10.1.1 Querying NAT Board Attribute ............................................................................ 10-2 10.1.2 Configuring NAT Board Attribute......................................................................... 10-3 10.1.3 NAT Board Flow Monitor..................................................................................... 10-4 10.1.4 Clearing Dynamic Entries on a NAT Board......................................................... 10-5

10.2 Address Group and ACL Management ......................................................................... 10-5 10.2.1 Querying NAT Address Group Information ......................................................... 10-5 10.2.2 Creating a NAT Address Group .......................................................................... 10-6 10.2.3 Deleting a NAT Address Group........................................................................... 10-7 10.2.4 Querying NAT ACL Information .......................................................................... 10-7 10.2.5 Creating a NAT ACL ........................................................................................... 10-7 10.2.6 Deleting a NAT ACL............................................................................................ 10-8 10.2.7 Querying NAT Bind Information .......................................................................... 10-8 10.2.8 Creating a NAT Bind ........................................................................................... 10-9 10.2.9 Deleting a NAT Bind.......................................................................................... 10-10

10.3 Server Management .................................................................................................... 10-10 10.3.1 Querying NAT Server Information..................................................................... 10-10 10.3.2 Creating a NAT Server...................................................................................... 10-11 10.3.3 Deleting a NAT Server ...................................................................................... 10-12

10.4 Aging Time Management............................................................................................. 10-13 10.5 NAT Enable Attribute Management............................................................................. 10-13

10.5.1 Querying the NAT Enable Attribute of an Interface........................................... 10-13 10.5.2 Changing the NAT Enable Status of an Interface............................................. 10-14 10.5.3 Creating a NAT-enabled Destination Segment................................................. 10-14 10.5.4 Deleting a NAT-enabled Destination Segment ................................................. 10-15

10.6 Blacklist Management.................................................................................................. 10-15 10.6.1 Querying Blacklist Information .......................................................................... 10-15 10.6.2 Deleting Blacklist Information............................................................................ 10-16


v

10.6.3 Querying and Configuring Blacklist Connection Limitation Parameters ........... 10-16 10.6.4 Querying Blacklist Connection Limitation Parameters on Special IPs.............. 10-18 10.6.5 Creating Blacklist Connection Limitation Parameters on Special IPs............... 10-19 10.6.6 Deleting Blacklist Connection Limitation Parameters on Special IPs ............... 10-20 10.6.7 Configuring Blacklist Connection Limitation Parameters on Special IPs.......... 10-20

Chapter 11 Ethernet Interface Configuration ........................................................................... 11-1 11.1 Overview........................................................................................................................ 11-1 11.2 Ethernet Interface Configuration.................................................................................... 11-3

11.2.1 Ethernet Port Status Configuration ..................................................................... 11-4 11.2.2 Interface Parameter Configuration...................................................................... 11-4 11.2.3 Reset Counter ..................................................................................................... 11-7

11.3 Ethernet Interface Information Query ............................................................................ 11-8 11.3.1 Browse Basic Information ................................................................................... 11-8 11.3.2 Browse Received Information ............................................................................. 11-9 11.3.3 Browse Sent Information................................................................................... 11-11 11.3.4 Browse Invalid VLAN ID.................................................................................... 11-13 11.3.5 Browse E4GC Information ................................................................................ 11-14

11.4 Real-time Statistics of Ethernet Interface .................................................................... 11-16 11.4.1 Real-Time Flow Statistics.................................................................................. 11-16 11.4.2 Real-Time Collision Statistics............................................................................ 11-17 11.4.3 Real-Time Error Statistics ................................................................................. 11-18

11.5 Subinterface Management........................................................................................... 11-19 11.5.1 Subinterface Management ................................................................................ 11-20 11.5.2 Subinterface MultiCast Query ........................................................................... 11-22 11.5.3 Subinterface Flow Query................................................................................... 11-23

Chapter 12 Ethernet Trunk Management .................................................................................. 12-1 12.1 Overview........................................................................................................................ 12-1 12.2 Adding an Eth Trunk ...................................................................................................... 12-2 12.3 Deleting an Eth Trunk .................................................................................................... 12-4 12.4 Eth Trunk Configuration................................................................................................. 12-4

12.4.1 Eth Trunk Status Configuration........................................................................... 12-4 12.4.2 Eth Trunk Parameter Configuration .................................................................... 12-6 12.4.3 Eth Trunk Counter Reset .................................................................................... 12-7 12.4.4 Port Configuration ............................................................................................... 12-7

12.5 Eth Trunk Information Query ......................................................................................... 12-9 12.5.1 Trunk Information ................................................................................................ 12-9 12.5.2 Trunk Port Information ...................................................................................... 12-10

12.6 Eth Trunk Statistic Information Query.......................................................................... 12-11 12.7 Eth Trunk Subinterface Management.......................................................................... 12-13

12.7.1 Eth Trunk Subinterface Management ............................................................... 12-13 12.7.2 Trunk Subinterface MultiCast Query................................................................. 12-16 12.7.3 Trunk Subinterface Flow Query ........................................................................ 12-17


vi

Chapter 13 IP Trunk Management ............................................................................................. 13-1 13.1 Brief Introduction to the IP Trunk................................................................................... 13-1 13.2 Adding an IP Trunk ........................................................................................................ 13-2 13.3 Deleting an IP Trunk Interface ....................................................................................... 13-4 13.4 Configuring the IP Trunk................................................................................................ 13-4

13.4.1 IP Trunk Status Configuration ............................................................................. 13-4 13.4.2 IP Trunk Parameter Configuration ...................................................................... 13-5 13.4.3 Add/Delete IP Trunk Member Port ...................................................................... 13-6

13.5 IP Trunk View................................................................................................................. 13-7 13.5.1 IP Trunk Member Port Information...................................................................... 13-7 13.5.2 IP Trunk Flow Statistics Query............................................................................ 13-8

Chapter 14 POS Interface Management .................................................................................... 14-1 14.1 Overview........................................................................................................................ 14-1 14.2 POS Interface Configuration.......................................................................................... 14-2 14.3 Path Configuration ......................................................................................................... 14-4 14.4 SDH Interface Query ..................................................................................................... 14-8 14.5 SDH Path Query .......................................................................................................... 14-12

Chapter 15 RPR Interface Management .................................................................................... 15-1 15.1 Logical and Physical Interfaces of RPR ........................................................................ 15-2 15.2 Interface Management................................................................................................... 15-3

15.2.1 MAC Parameter................................................................................................... 15-4 15.2.2 Interface Status ................................................................................................... 15-5 15.2.3 Interface Parameter ............................................................................................ 15-6

15.3 Counter Configuration.................................................................................................... 15-7 15.3.1 Source Counter Configuration............................................................................. 15-8 15.3.2 Destination Counter Configuration.................................................................... 15-11 15.3.3 Source Reject Counter Configuration ............................................................... 15-12

15.4 Topology Management ................................................................................................ 15-13 15.4.1 Static Ring Selection ......................................................................................... 15-14 15.4.2 Querying the Topology Information................................................................... 15-16

15.5 Querying the SDH Interface......................................................................................... 15-17 15.6 SDH Path Query .......................................................................................................... 15-18 15.7 Ring Monitoring............................................................................................................ 15-18 15.8 Host Monitoring............................................................................................................ 15-21 15.9 Error Monitoring ........................................................................................................... 15-22 15.10 Display Topology Ring............................................................................................... 15-24

Chapter 16 CPOS Port Management ......................................................................................... 16-1 16.1 Overview........................................................................................................................ 16-1 16.2 CPOS Interface Configuration ....................................................................................... 16-2 16.3 Higher-Order Path Management ................................................................................... 16-4

16.3.1 Higher-Order Path Configuration ........................................................................ 16-5


vii

16.3.2 Higher-Order Path Current View......................................................................... 16-5 16.3.3 Higher-Order Path History View.......................................................................... 16-7

16.4 Lower-Order Path Management .................................................................................... 16-9 16.4.1 Adding a Lower-Order Path ................................................................................ 16-9 16.4.2 Deleting a Lower-Order Path ............................................................................ 16-11 16.4.3 Lower-Order Path Configuration ....................................................................... 16-11 16.4.4 Lower-Order Path Traffic Monitor...................................................................... 16-15 16.4.5 Lower-Order Path Current View........................................................................ 16-17 16.4.6 Lower-Order Path History View......................................................................... 16-19

16.5 Multilink Management.................................................................................................. 16-20 16.5.1 Adding a Multilink .............................................................................................. 16-21 16.5.2 Deleting a Multilink ............................................................................................ 16-22 16.5.3 Configuring a Multilink....................................................................................... 16-22 16.5.4 Multilink Statistics.............................................................................................. 16-26

16.6 SDH Interface Query ................................................................................................... 16-26

Chapter 17 ATM Interface Management.................................................................................... 17-1 17.1 Overview........................................................................................................................ 17-1 17.2 Interface Configuration .................................................................................................. 17-2

17.2.1 Interface Maintenance......................................................................................... 17-3 17.2.2 SDH Parameter Configuration ............................................................................ 17-5

17.3 PVC Management ......................................................................................................... 17-7 17.3.1 PVC Configuration .............................................................................................. 17-7 17.3.2 OAM Test Configuration.................................................................................... 17-12

17.4 SDH Interface Query ................................................................................................... 17-13 17.5 SDH Path Query .......................................................................................................... 17-13

Chapter 18 Portal Configuration ................................................................................................ 18-1 18.1 Portal Protocol Overview ............................................................................................... 18-1 18.2 Portal Configuration ....................................................................................................... 18-2

18.2.1 Portal Function List ............................................................................................. 18-2 18.2.2 Enabling Portal .................................................................................................... 18-2 18.2.3 Configuring Portal ID........................................................................................... 18-4 18.2.4 Address Pool Configuration ................................................................................ 18-6 18.2.5 NAS Configuration .............................................................................................. 18-7 18.2.6 iTELLIN Key Configuration.................................................................................. 18-8 18.2.7 Browsing Portal User Information ..................................................................... 18-10 18.2.8 Browsing Portal Status Information................................................................... 18-10

Chapter 19 Voice Management .................................................................................................. 19-1 19.1 Voice Common Information ........................................................................................... 19-2 19.2 Voice Port Information ................................................................................................... 19-3

19.2.1 Analog Port Configuration ................................................................................... 19-3 19.2.2 Digital Port Configuration .................................................................................. 19-11


viii

19.3 Voice Entity Information............................................................................................... 19-17 19.3.1 POTS Voice Entity Configuration...................................................................... 19-18 19.3.2 VOIP Voice Entity Configuration ....................................................................... 19-21

19.4 Voice AAA Information................................................................................................. 19-24 19.4.1 AAA Attribute Configuration .............................................................................. 19-24 19.4.2 Local User Configuration................................................................................... 19-25 19.4.3 Access Number Configuration .......................................................................... 19-26

19.5 GK Client Information .................................................................................................. 19-28 19.6 Voice Call Information.................................................................................................. 19-30 19.7 H.323 Call Statistics..................................................................................................... 19-34

Chapter 20 POS Access Management....................................................................................... 20-1 20.1 POS Access Common Information................................................................................ 20-1 20.2 POS Access Port Management ..................................................................................... 20-3

20.2.1 Browse POS Access Port ................................................................................... 20-3 20.2.2 Add POS Access Port ......................................................................................... 20-4 20.2.3 Delete POS Access Port ..................................................................................... 20-5 20.2.4 Config POS Access Port ..................................................................................... 20-5 20.2.5 Monitoring Statistical Information of POS Access Port ....................................... 20-6

20.3 POS App Port Management .......................................................................................... 20-7 20.4 POS Application Management....................................................................................... 20-8

20.4.1 Browse POS Applications ................................................................................... 20-8 20.4.2 Add POS Application......................................................................................... 20-10 20.4.3 Delete POS Application..................................................................................... 20-12 20.4.4 Config POS Application..................................................................................... 20-12 20.4.5 Monitoring Statistical Information of POS Application....................................... 20-12

20.5 POS Map Management ............................................................................................... 20-13 20.5.1 Browsing POS Map........................................................................................... 20-14 20.5.2 Add POS Map ................................................................................................... 20-15 20.5.3 Delete POS Map ............................................................................................... 20-15 20.5.4 Config POS Map ............................................................................................... 20-16

20.6 FCM Port Management ............................................................................................... 20-16

Chapter 21 NDEC Management.................................................................................................. 21-1 21.1 NDEC Management....................................................................................................... 21-1 21.2 NDEC Information.......................................................................................................... 21-2

21.2.1 Clearing Statistics ............................................................................................... 21-3 21.2.2 Resetting NDEC.................................................................................................. 21-4 21.2.3 Synchronizing Clock............................................................................................ 21-4 21.2.4 NDEC Logging .................................................................................................... 21-4

21.3 Router SA Information ................................................................................................... 21-4 21.4 NDEC IKE SA Information ............................................................................................. 21-6 21.5 Router IKE Policy Information........................................................................................ 21-7 21.6 Router Security Policy Information ................................................................................ 21-7


ix

21.7 Transform Mode Security Information ........................................................................... 21-9

Chapter 22 Terminal Server Management................................................................................. 22-1 22.1 Terminal Access Server Management .......................................................................... 22-1 22.2 Terminal Access Application Management ................................................................... 22-2 22.3 Physical Terminal and Virtual Terminal Management................................................... 22-5 22.4 Physical Terminal Information ....................................................................................... 22-8 22.5 Management Path Information .................................................................................... 22-11

Chapter 23 DLSW Service Management ................................................................................... 23-1 23.1 DLSW Configuration ...................................................................................................... 23-1 23.2 Local Peer...................................................................................................................... 23-2 23.3 Remote Peer.................................................................................................................. 23-4 23.4 Bridge Group.................................................................................................................. 23-6 23.5 SDLC Interface .............................................................................................................. 23-8

23.5.1 SDLC Interface Configuration ............................................................................. 23-9 23.5.2 SDLC Prot Remote Peer Configuration .............................................................. 23-9

23.6 LLC2 Parameter Configuration .................................................................................... 23-11 23.7 DLSW View.................................................................................................................. 23-13

Chapter 24 DHCP Management.................................................................................................. 24-1 24.1 DHCP Server Group Management ................................................................................ 24-1

24.1.1 Browsing DHCP Server Group Information ........................................................ 24-1 24.1.2 Configuring DHCP Server Group........................................................................ 24-2

24.2 DHCP Relay Management ............................................................................................ 24-3 24.2.1 Querying VLAN and DHCP Server Group Association....................................... 24-3 24.2.2 Creating VLAN and DHCP Server Group Association........................................ 24-4 24.2.3 Deleting VLAN and DHCP Server Group Association ........................................ 24-5 24.2.4 Configuring VLAN and DHCP Server Group Association................................... 24-5

24.3 VLAN Address Pool Management ................................................................................. 24-6 24.3.1 Querying VLAN Address Pool Information.......................................................... 24-6 24.3.2 Changing VLAN Address Allocation Mode ......................................................... 24-7 24.3.3 Configuring VLAN Address Pool ......................................................................... 24-7 24.3.4 Querying Statistics Information ........................................................................... 24-7 24.3.5 Appending Disabled IP Segment ........................................................................ 24-8 24.3.6 Canceling Disabled IP Segment ......................................................................... 24-9

24.4 Global Address Pool Management.............................................................................. 24-10 24.4.1 Querying Global Address Pool Information....................................................... 24-10 24.4.2 Creating Global Address Pool........................................................................... 24-11 24.4.3 Deleting Global Address Pool ........................................................................... 24-13 24.4.4 Configuring Global Address Pool ...................................................................... 24-13 24.4.5 Querying Statistics Information ......................................................................... 24-13 24.4.6 Appending Disabled IP Segment ...................................................................... 24-14 24.4.7 Canceling Disabled IP Segment ....................................................................... 24-15


x

24.5 DHCP Traffic Monitoring.............................................................................................. 24-16

Chapter 25 Frame Relay Management ...................................................................................... 25-1 25.1 Overview........................................................................................................................ 25-1 25.2 Frame Relay DTE Management .................................................................................... 25-1

25.2.1 DLCM Management ............................................................................................ 25-1 25.2.2 Circuit Management ............................................................................................ 25-4 25.2.3 Error Information ................................................................................................. 25-4 25.2.4 Trap State Management ..................................................................................... 25-5

25.3 Frame Relay Service Management ............................................................................... 25-6 25.3.1 Logical Port Management ................................................................................... 25-6 25.3.2 LMI Parameter Management .............................................................................. 25-8 25.3.3 PVC End-points Management........................................................................... 25-10 25.3.4 PVC Connection Management.......................................................................... 25-12

User Manual Volume I Quidview Device Manager Chapter 1 Overview

1-1

Chapter 1 Overview

1.1 Introduction of Quidview Network Management System

Quidview is a device management product, which is independently developed by Huawei-3Com Technology Co., Ltd. (hereinafter referred to as Huawei-3Com), and is intended for integrated management and maintenance of such data communication products as routers and Ethernet switches. Quidview is used at the management layer of network solutions and implements management for multi-device network element and network. In combination with Huawei-3Com data communication products, Quidview provides overall network solutions, not only supporting maintenance and network management of data communication devices but also providing support and interface for Operating Support System (OSS) of telecom network.

The system uses the universal standard network management protocol SNMP and supports SNMP V1, V2c and V3.

Quidview network management system (NMS) can help users to reach the following goals:

Improving reliability of networks Ensuring QoS of network operation Outlining and allocating network resources reasonably Forecasting and detecting network faults Centralized management of widely distributed network nodes Statistics and analysis of device performance

1.2 Overview of Quidview Device Manager

Quidview Device Manager is the network management software of device level, which is independently designed by Huawei-3Com, and is applied to various operating systems including Windows platform (NT/2000) and UNIX platform (SUN Solaris /HP UX). Quidview Device Manager is one of the Quidview series NM products and is mainly used to manage Huawei-3Com devices.


1-2

As a compact device management tool making sufficient use of the management information base of the device, Quidview Device Manager fulfils such fundamental network management functions as browsing configuration information of the device and monitoring running status of the device etc. Moreover, it can also be integrated with some universal device management platforms such as SNMPc, HP OpenView NNM, and N2000 EMF, implementing all-round device management from device level to network level. Quidview Device Manager endeavors to meet requirements of more abundant functions while helping users reduce product cost.

Note:

Device Manager is included in Quidview NMF. With Quidview NMF installed, it is unnecessary to install Device Manager.

Quidview Device Manager has the following features:

I. Powerful functions

Quidview Device Manager provides visual operations on the whole device. That is, it provides users with complete device views, in which users can directly select objects such as the overall device, object panels and interfaces etc, and select corresponding functions to fulfill corresponding function operations including browsing and configuring the information about the device, and monitoring the system status etc.

Quidview Device Manager, a standalone subsystem of Network Management, provides corresponding service functions according to different devices, including RMON management, VLAN management, RSTP management, protocol management, S8016 NAT management, Ethernet interface management, Ethernet Trunk management, IP Trunk management, POS interface management, RPR interface management, CPOS Port management, ATM interface management, Portal Management, VoIP service management, POS access management, NDEC management, Terminal Server management, DLSW Service management, DHCP management, VDSL management, cluster management, stack management, QoS management and performance monitoring, etc.

II. Irrelevance between operating environment and platform

Developed in Java which is independent of platform, the system can run on multiple platforms. It is included in Quidview NMF, and can also be integrated with other NM platforms such as SNMPc, OpenView and N2000 EMF. At present, the NMS supports two operating systems, namely, Windows (NT/2000) and UNIX (SUN Solaris/HP UX). In addition, the system also provides various graphic operating interfaces that display data obviously, thus easing the use of various management functions.


1-3

III. Visual display

The system provides graphic user interface (GUI) for users to select desired operations. Users can access the device managed by specifying the IP address of the device and obtain a fully emulated and complete device panel view. Changes of the interface colors obviously indicate the running status of all the interfaces of the device.

IV. Easy to use and universal

On the GUI of the system, users just click on the menu items to complete a series of functional operations. The operation style is consistent with that of Windows. Users who have experience in Windows can easily master the use of this software.

V. Cost effective and investment protection

The system is simple and practical. It provides to users with the most reasonable functions at minimum investment. Users can use the powerful functions provided in the MIB to monitor the device and browse configuration information, thus implementing real-time monitoring on the running status of the device and network management.

With low requirement for hardware environment of the running platform, the system can be installed normally on both workstation and PC, thereby saving costs greatly and protecting investment of users to a maximum extent.

Note:

Quidview Device Manager User Manual has two volumes. This volume mainly describes the general functions of Device Manager and the functions of managing devices such as routers and voice devices. As for the functions of managing the switching feature supported by routers, refer to the related sections in Quidview Device Manager User Manual Volume II.

User Manual Volume I Quidview Device Manager Chapter 2 General Functionalities

2-1

Chapter 2 General Functionalities

2.1 Starting Quidview Device Manager

Quidview Device Manager can run as a standalone application or be integrated into a network topology platform. The startup of Quidview Device Manager varies with different platforms.

2.1.1 Starting Quidview Independently

I. Startup on Windows OS

Restart the computer as prompted at the completion of independent installation, and then select [Start/Program/Quidview/DeviceManager/DeviceManager] under Windows environment, a user login window will pop up. After the user correctly enters user name and password, Quidview Device Manager will be started.

Figure 2-1 User login

II. Startup on UNIX OS

After installing Quidview Device Manager in UNIX OS, run the DeviceManager file under same directory of the installation directory to access the login dialog box. Enter the proper user name and password in the dialog box and you will start the Quidview Device Manager.


2-2

Note:

Quidview Device Manager can be installed and run under both Windows and UNIX series OSs to implement exactly same functions. This manual details the use and operation of Quidview Device Manager by taking Windows system as an example. For the installation of Quidview Device Manager, refer to the related installation manual;

The default username and password in Quidview Device Manager is admin and quidview, which enables user to add and delete different types of users through the function of user management.

After login, the following main interface of Quidview Device Manager will appear, as shown in Figure 2-2.

Figure 2-2 Main interface of Quidview Device Manager

The main interface of Quidview Device Manager is divided into seven parts: menu bar, toolbar, device pane, function pane, panel view, information prompt area and status bar.

Menu bar: provides the menu options for the general functions of the system. Toolbar: provides the pop-up operations for the commonly used menu items. Panel view: displays the panel information of the opened devices, including the

position and status of all boards and ports. If none of the devices is opened, the area is empty.

Device pane: provides the list of the devices that have been opened. Users may double-click on the item listed in the window to open the panel of the corresponding device.


2-3

Function pane: provides the function list corresponding to the opened devices. The contents shown in the window vary according to different devices.

Information prompt area: displays the information prompted during the operation of the system.

Status bar: displays the running status of the system, such as running time.

Click on the toolbar or select [Device/Open Device…] to display the [Open Device]

dialog box, as shown in Figure 2-3.

Figure 2-3 Open Device

Input the IP address of the device to be opened in the dialog box and click <OK>, then the main interface after opening the device will appear, as shown in Figure 2-4.

Figure 2-4 Main interface of Quidview Device Manager (after opening the device)


2-4

2.1.2 Starting Quidview on Quidview NMF Topology Platform

Quidview Device Manager is installed as an add-on to the Quidview NMF platform, just double-click on a device to launch it and display the related device panel.

Note:

There may be a slight difference in the interface and menu functions between the add-on and the standalone Quidview Device Manager. The Device Manager does not repeat the general functionalities deployed in Quidview NMF, such as the device list on the interface, user management, password modifying, authentication options and log viewing in the System menu, device menu, and device list in the View menu.

2.1.3 Starting Quidview on SNMPc Topology Platform

After Quidview Device Manager has been installed on the SNMPc NMS platform, the H3C series network devices will be automatically discovered when SNMPc is started, and their icons will be displayed in the SNMPc topology view. Double-click a device icon, and you will start Quidview Device Manager and open the corresponding device panel.

2.1.4 Starting Quidview on HP OpenView

After installing Quidview Device Manager on the HP OpenView NNM platform, run HP OpenView NNM and you will view the icons of H3C series devices in the topology view. Meanwhile, the H3C icon and a menu item [Quidview] (containing pull-down menu [DeviceManager...]) are added to the toolbar and the menu bar respectively. Select a device icon, and click the H3C icon on the toolbar or select [DeviceManager...] from the menu bar, and you will start Quidview Device Manager, and access the corresponding device panel.

2.1.5 Starting on N2000 EMF Platform

Integrate Quidview to the N2000 EMF platform, and start N2000 EMF to open an existent topology view or create a topology view. Add a H3C router device to the topology view, when the device icon is displayed in the interface. Double-clicking on the icon will start Quidview Device Manager and display the related device panel.


2-5

2.2 Introduction to Menu Functions

The main interface of Quidview Device Manager provides five menu items, System, Device, View, Tools and Help. The functions of each menu item are briefly introduced below.

2.2.1 System

The system menu is mainly used to manage system users, set authentication parameters and system parameters, and view logs. The System menu contains the following items:

I. User Management

As shown in Figure 2-5, it is used to browse the existent users of the system and to add or delete a user.

Figure 2-5 User Management

Click <Add...>, and the [Add a User] dialog box will pop up, as shown in Figure 2-6. Input a new user name and password and select a user type, then click <OK> to add a new user.


2-6

Figure 2-6 Add User

Note:

Only administrators have the user management function. “admin” is the default administrator, and it cannot be deleted. For sake of security, you need to change its password in time after login.

Select a user and click <Modify…> to open the [Modify User] dialog box, which allows you to change the user’s password and the user type.

Select a user and click <Delete>, and the system will display a dialog box for the user to confirm the deleting of the user. Click <OK>, and then the user will be deleted.

II. Change Password

This function is used to modify the password of the current user. All users are capable of this function.

III. Auth. Options

It is used to set the SNMP parameter of device, as well as the Telnet parameter of the router.

1) SNMPv1 and SNMPv2c


2-7

Figure 2-7 Auth. Options-SNMPv1&SNMPv2c

SNMPv1 and SNMPv2c adopt community name for authentication, and the SNMP packet whose community name is different from that configured on the device will be dropped. The community name with read-only right can only query the device information, while the community name with read and write rights can configure the device.

In Figure 2-7, the user needs to set the Read Community, Write Community, Timeout(s) and Retries. Here, Timeout(s) represents the maximum time it takes for the system to wait for the response from the managed device during the communication. The timeout value should be at least two times greater than the average response time for communication between the system and the managed device. If with low speed network connection, the value should be set high; if the system and managed device are within the same LAN, the value should be set low.

Retries means the maximum number of retires in the case that fault occurs during the communication between the system and the managed device. SNMP packets may be dropped when the network gets busy. In case there is no response due to packet dropping, Quidview sends a SNMP request again after a response timeout period until the managed device responses with a SNMP packet or the maximum number of attempts is reached.

2) SNMPv3


2-8

Figure 2-8 Auth. Options-SNMPv3

As shown in Figure 2-8, SNMPv3 adopts user name and password for authentication. The setting of authentication passwords and encryption passwords is decided by different security levels. The contents used in the setting of SNMPv3 protocol parameters are listed in Table 2-1.

Table 2-1 Description on main SNMPv3 parameters

Content Description

User Name SNMPv3 user name

Security Level Includes: No Auth No Encrypt, Auth No Encrypt, Auth with Encrypt

Auth Type Includes: NONE, MD5, SHA

Encryption Type Includes: NONE, DES

Auth Password For the security that has both authentication and encryption or only has authentication but no encryption, the user needs to input correct authentication password.

Encryption Password

For the security that has both authentication and encryption, the user needs to input correct encryption password.

3) Telnet parameter

It is used to set the interface IP address and routing protocol of the router. The configuration interface is shown in Figure 2-9.


2-9

Figure 2-9 Auth. Options-Telnet Options

Device configuration is not available unless the Telnet parameters are correctly configured.

Caution:

Select [System/Auth. Options…], and you can set the Telnet parameters to the default values, that is, the values used for opening a device. To modify the Telnet parameters of a specific device, you must select [Device Properties…] from the shortcut menu of the device node in the device list for configuration.

IV. System Options

As shown in Figure 2-10, this menu item is used to set panel refreshing interval and real-time monitoring refreshing interval. According to the settings, the system will refresh device panels and real-time monitoring interfaces periodically.


2-10

Figure 2-10 System Options

V. View Logs

As shown in Figure 2-11 and Figure 2-12, this menu is used to browse the operation and running logs of the system.

Figure 2-11 Operation log

Operation log records the operations of various users in the system. Each record includes such fields as time, user, device, function, result and description. Click a column title, and you can sort the table by the column entries.


2-11

Figure 2-12 Running log

Running log records the information generated during the running of the system. Each record includes such fields as time, user, level, function and description. Click a column title, and you can sort the table by the column entries.

VI. Exit

It is used to exit the Quidview Device Manager.

2.2.2 Device

It is mainly used to open/close the device panel, create cluster/stack, etc. It includes the following menu items:

I. Open Device

As shown in Figure 2-13, this menu item asks the user to input the IP address and label (optional) of the device to be opened. Click <OK>, the designated device will be opened and the device panel view will be displayed.


2-12

Figure 2-13 Open Device

Note:

Make related configurations on the device before opening the device, such IP address and authentication parameters.

II. Close Device

It is used to disconnect the current device and close the related panel view.

2.2.3 View

I. Refresh

It is used to refresh the device panel.

II. Search

It searches, by the IP address or the label, for the specified devices from the device pane, and highlights it. This function only supports backward fuzzy matching, and is case sensitive.

III. Device List

It sets whether to display the device pane.

IV. Function Pane

It sets whether to display the function pane.

V. Message Window

It sets whether to display the message window.


2-13

VI. Select Layout

It allows you to select different layout.

VII. Zoom

It is used to zoom in or zoom out the panel view, and mainly includes the following functions:

Actual size

If the panel size is changed, you can use this function to restore the original size.

Zoom in

Use it to zoom in the current panel.

Zoom out

Use it to zoom out the current panel.

Fit Window

Use it to display the whole panel to occupy the area exactly. The panel size may be increased or reduced.

Fit Width

Use it to display the whole panel to occupy the area horizontally. The panel size may be increased or reduced.

Fit Height

Use it to display the whole panel to occupy the area vertically. The panel size may be increased or reduced.

2.2.4 Tools

I. Telnet

It is used to Telnet to the specified device.

II. PortBinding

It provides the batch configuration function on the ports of the switch. Refer to online help for details.

III. Ping

It tests the connectivity to the specified device.

IV. Proxy Ping

It performs a ping between the Proxy Ping-enabled device selected by the user and the target device.


2-14

V. TraceRoute

It displays the route from current host to the specified device.

2.2.5 Help

I. Legend

Note:

The tab pages in the [Legend] window vary with different devices. For routes and voice devices: device legend, interface color, device status and

board status, etc; For switches: device legend, mode, board status, V1 cluster and V2 cluster, etc.

1) Device Legend

Display the icons and their corresponding devices supported by Quidview Device Manager.

2) Mode

The available modes include default mode, duplex mode, mirror mode, speed mode, PoE mode, stack mode, Vlan Trunk mode, Vlan mode, Vlan hybrid mode, and aggregation mode. The legends indicate the correspondence between port status and colors in various modes respectively.

3) Board Status

Table 2-2 Corresponding relations between board colors and status

Board color Meaning of status

Green The board operating normally is represented by green screws in device panel.

Blue The backup board operating normally is represented by blue screws in device panel.

Red The board (including backup board) operating abnormally is represented by red screws in device panel.

Note:

Before CT1/PRI port is set as serial, the port status is unavailable and the port is dimmed. The port will be highlighted after the time slot is set.


2-15

4) V1 Cluster and V2 Cluster

The [V1 Cluster] and [V2 Cluster] tabs show the icons of various roles and connections in V1 and V2 cluster topology views respectively.

II. Help Topics

When using the Quidview Device Manager, you can click <Help Topics…> on the toolbar at any time to enable the online help to get related information.

III. About

It displays the version, copyright and Liscence information of Quidview Device Manager.

2.2.6 Pop-up Menu

The pop-up menu includes that for device, for panel and for port, which are described below respectively.

I. Pop-up menu for the device pane

Right click on the device pane area, and the corresponding pop-up menu will appear. It provides such functions as opening/closing a device panel, deleting a device from the device pane, setting SNMP properties for the device, and sorting devices by IP address or label. Besides, the [Tool] menu includes some simple tools such as ping and telnet for operation without opening a device.

II. Pop-up menu for panel

Right click on the device panel area, and the corresponding pop-up menu will appear. It provides all of device management functions such as device management, port management, performance monitoring, routing protocol management, and VLAN management etc. The available functions vary with the type of devices. For details, refer to the subsequent chapters of this volume and the Volume II.

III. Pop-up menu for port

Right click a certain port on the device panel, and the corresponding pop-up menu will appear. It provides all of port management functions such as port browsing, port configuring, port MAC mapping and port monitoring etc. The available functions vary with the port of the device. For more detail, refer to the subsequent chapters of this volume and Volume II.

2.3 Introduction to Toolbar

The following figure shows the toolbar of Quidview Device Manager, and the functions of all the tools on the toolbar (from left to right) are described in Table 2-3.


2-16

Figure 2-14 The toolbar of Quidview Device Manager

Table 2-3 Toolbar functions

Description Function

Open Device Function the same as [Device/Open Device…] menu

Close Device Function the same as [Device/Close Device] menu

Refresh Function the same as [View/Refresh] menu

Search Function the same as [View/Search…] menu

Show/Hide Device List Function the same as [View/Device List] menu

Show/Hide Function Window Function the same as [View/Function Window] menu

Show/Hide Message Window Function the same as [View/Message Window] menu

Auth. Options… Function the same as [System/Auth. Options…]

System Options… Function the same as [System/System Options…] menu

Telnet… Function the same as [Tools/Telnet…] menu

PortBinding… Function the same as [Tools/PortBinding…] menu

Ping… Function the same as [Tools/Ping…] menu

Proxy Ping… Function the same as [Tools/Proxy Ping…] menu

TraceRoute… Function the same as [Tools/TraceRoute…] menu

Actual Size Function the same as [Zoom/Undo Zoom] menu

Zoom in Function the same as [Zoom/Zoom in] menu

Zoom out Function the same as [Zoom/Zoom out] menu

Fit Window Function the same as [Zoom/Fit Window] menu

Fit Width Function the same as [Zoom/Fit Width] menu

Fit Height Function the same as [Zoom/Fit Height] menu

Help Topics… Function the same as [Help/Help Topics…] menu


2-17

2.4 Device Pane and Function Pane

2.4.1 Device Pane

The device pane displays the list of the devices that have been opened or are being opened. You may double-click on the IP addresses of different devices to switch between different device panels.

2.4.2 Function Pane

As shown in Figure 2-15, the function pane of the Device Manager displays the available management functions for the current device, which implement browsing, configuration and maintenance. For detailed description, refer to the related sections later in this manual.

Figure 2-15 Function Pane

Note:

The function menus in the function pane are loaded when you open a device. If the device model or the board changes, you need to re-open the device to load the function menus again.

2.5 Information Display Area

This area displays the panel view and corresponding information about the managed device. The colors of the interfaces and boards in the device panel represent their current working status. For the convenience of browsing the panel view and device information simultaneously, you can select suitable layout of various windows in the information area.


2-18

2.6 Message Window

The prompt information generated during the operation is displayed in the message window.

2.7 Status Bar

Status bar lies on the bottom of the Quidview DM interface, and is broken into four parts from left to right, that is, user prompt area, active device process area, reservation area and system running duration and Huawei-3Com icon area.

The reservation area displays the status of the active panel, and the time area shows the duration since the startup of the system.

User Manual Volume I Quidview Device Manager Chapter 3 Device Management

3-1

Chapter 3 Device Management

3.1 Panel Monitoring

The Panel Monitoring enables users to take an overall intuitive sight at the system, namely provides a fully emulated view on device panel. In the view, users can select the desired object such as the whole of device, subcard and interface, with function options in relation to corresponding operation including browse, configuring the related information on device and monitoring interface status.

3.2 System Information

The System Information offers the system information of a device, including system information, address translation table, interface table, IP address table, IP routing table, and TCP connection table.

Select [Device Management/System Information] on the navigation tree in the function pane, and the [System Information] window appears on the information display area.

Note:

The displayed system information varies with different devices.

I. System

The system information, available for every device, describes the basic and indispensable information about them. The related parameters are described in Table 3-1.

Table 3-1 Description on the parameters of the system information

Name Description

System Description

ASCII text describing the device name and versions of software and hardware.

System OID A group of unique ID of manufacturer and device used online.

Elapsed Time Continuous operation time of the system after being started.

Location Describes the geographical location of the device.


3-2

Name Description

Device Name Mnemonic symbol of the device defined at the device side.

Contact Contact information about the responsible company or person.

II. Address Translation Table

The address resolution protocol (ARP) provides a dynamic mapping between IP addresses and corresponding hardware addresses. Usually, each device has an ARP cache, which stores the latest mapping entries between IP addresses and hardware addresses. The Address Translation Table shows the contents of the ARP cache of the device in a table. The related parameters are described in Table 3-2.

This interface also supports static ARP adding, configuration and deletion.

Table 3-2 Description on the parameters of the Address Translation Table

Name Description

Interface Description Identifier of the interface name of the router or of the VLAN interface that the switch belongs to currently

Network Address IP address of the interface

Physical Address Media-specific physical address, for example, MAC address

III. Interfaces Table

The Interface Table records some important data about the current operation of the interface, which helps an administrator quickly locate and analyze the fault whenever the interface operates abnormally. The related parameters are described in Table 3-3.

Table 3-3 Description on the parameters of Interfaces Table

Name Description

Description Identifier of the interface name of the router or of the VLAN interface that the switch belongs to currently

Alias The alias of the interface.

Type Interface type, mainly decided by the physical and link layer protocols.

MTU (byte) Maximum transmission unit of an interface

Speed (bps) Bits passing through an interface per second

PhyAddress Interface MAC address mapped on the link layer


3-3

Name Description

AdminStatus

The interface administration status specifies the expected operation status of the interface and can be configured. UP means an interface can transmit and receive data packets, while DOWN means it cannot transmit or receive any data packets.

OperStatus

The interface operation status indicates the actual operation status of an interface and cannot be configured. UP means an interface can transmit and receive data packets, while DOWN means it cannot transmit or receive any data packets.

LastChange Records when the interface changed into the current status.

InOctets All octets received by the interface.

InUcastPkts Number of unicast packets received via the interface.

InNUcastPkts Number of broadcast and multicast packets received via the interface.

InDiscards Number of discarded incoming packets due to packet errors or lack of buffer space.

InErrors Number of packets with error received via the interface. Such packets will be discarded.

InUnknowProtos Number of packets with illegal unknown protocols received via the interface. Such packets will be discarded.

OutOctets All octets transmitted from the interface.

OutUcastPkts Number of unicast packets transmitted from the interface.

OutNUcastPkts Number of broadcast and multicast packets transmitted from the interface.

OutDiscards Number of discarded outgoing packets due to packet errors or lack of buffer space.

OutErrors Number of packets with error transmitted from the interface. Such packets will be discarded.

OutQLen Length of the outgoing packet queue of an interface

Specific Media to offer the interface.

IV. IP Address Table

The IP Address Table offers IP address information related to the device interface, which helps the administrator learn such information. The related parameters are described in Table 3-4.

The [Address Translation Table] tab allows you to browse the relationship between IP addresses and media-specific physical addresses, and also supports static ARP adding, configuration and deletion.


3-4

Table 3-4 Description on the parameters of IP Address Table

Name Description


Address IP address of an interface

NetMask Mask of the IP address of an interface

The Least-significant Bit of Broadcast Address

Lowest bit in an IP broadcast address. If an interface has a broadcast address with all the digits being 1s, the value is 1.

Max Size of IP Packet The Maximum IP packet that can be reassembled with the maximum value as 65535.

V. IP Routing Table

The IP Routing Table offers the routing table information of a device, which is the basis for forwarding packets. The related parameters are described in Table 3-5.

Table 3-5 Description on the parameters of IP Routing Table

Name Description


Destination Address IP address of a destination host or network segment

Mask Mask of the destination host or network segment

Metric Cost of the route. If it is –1, it means the route is not enabled.

Next Hop Address IP address of the next hop on the route.

Routing Protocol Specifies the routing protocol (For example, other; RIP; OSPF; BGP).

Route Type Specifies the route type (For example, other; invalid; direct; indirect).

Route Age How many seconds elapsed since the route has been refreshed or decided as correct.

VI. TCP Connection Table

The TCP Connection Table lists the TCP connections of a device and includes the IP address and port number of the connection initiator and the connection status. The related parameters are described in Table 3-6.


3-5

Table 3-6 Description on the parameters of TCP Connection Table

Name Description

Local Address Local IP address for TCP connection.

Local Port Local port of the TCP connection.

Remote Address IP address of the remote device of the TCP connection.

Remote Port Remote port of the TCP connection.

Status

Specifies the status of TCP connection: CLOSED; LISTEN; SYN_SENT; SYN_RCVD; ESTABLISHED; FIN_WAIT1; FIN_WAIT2; CLOSE_WAIT; LAST_ACK; CLOSING; TIME_WAIT; or Deleted.

3.3 Board Browsing

3.3.1 Board Browsing for Routers

I. Board browsing for core routers

In the function pane, select [Device Management/Board Browsing] on the navigation tree and see the board information of a device in the information display area on the right side.

Table 3-7, Table 3-8, Table 3-9 and Table 3-10 list the parameters contained in each kind of board:

Table 3-7 Description on the parameters of the main board

Name Description

Status Shows the status of the main board as Master or Standby.

Running Status Shows the running status of the main board as normal or abnormal. A normally running main board can receive the heart beat of the standby board.

Alarm LED Shows the status of the alarm light on a main board as LightOn or LightOff.

Table 3-8 Description on the parameters of the clock board

Name Description

Status Shows the clock board status as Master or Standby.

Phase Lock Method

Shows the phase lock method of a clock board as free; free-verdict; snatch; track; retain; retain-verdict.


3-6

Name Description

Warm-up Oscillator Shows if it is in the warm-up oscillator status as normal or preheat.

Running Status Shows the running status of a clock board as normal or abnormal.

Trace Active Clock

Shows the current active clock being traced. 0: Free oscillation of a clock board; 1: BITS1; 2: BITS2; or 3 through 18 are reference clock of the circuit board.

Current Active Clock

Shows the current active clock, which can be 0: Free oscillation of a clock board; 1: BITS1; 2: BITS2; or 3 through 18 are reference clock of the circuit board.

Traction Status Shows the traction status of a clock board as normal or outrange.

Export SSM Severity

Shows the SSM severity, which can be 1: Unknown synchronous quality; 2: G8.11 clock signal; 3: G.812 transit node clock signal; 4: G.812 local node clock signal; 5: SDH device clock source signal; or 6: No synchronization.

Table 3-9 Description on the parameters of the line and NAT board

Name Description

Slot/SlotNum Slot number of a card

Number of Subcards Number of subcards of a card.

FSU Version FSU Version of a card.

EFU Version EFU Version of a card.

Registration Info Registration information of a card.

Up Date Shows the date on which the card was started last time.

Up Time Shows the time when the card was started last time.

Network Port Status Shows the network port status of a card as normal or abnormal.

Syn Status The synchronous status of LPU and NET board. The synchronous status of NAT board and NM.

Number of Subslots Number or subslots of a card.

Table 3-10 Description on the parameters of the NET board

Name Description

Self-Check Result Self-check of the NET board.

Port Status The status of the port on a NET board. The port is the DASL channel between the interface LPU and NET board.


3-7

Name Description

Status NET board status, which can be Master or Standby.

Running Status Running status of the NET board.

II. Board browsing for high-end routers

In the function pane, select [Device Management/Board Browsing] on the navigation tree of high-end routers and see the board information of a device in the information display area on the right side. The information of all the boards contained in the device is displayed in tables. The parameters are described in Table 3-11.

Table 3-11 Description on the parameters of high-end routers

Name Description

Module Index Index of the board

Card Number Slot number of the board

Type Type of the board

Description Description of the board

Serial No. Serial number of the board

Number of Cards Number of subcards of the board

Hardware Ver Hardware version of the board

Software Ver Software version of the board

Last Card Change Last time when the board changes

Admin Status Administration status of the board

Oper Status Operation status of the board

Note:

S8016 and the mid-range and low-end routers do not support board browsing function.

3.3.2 Module Information Browsing of Switches

In the function pane, select [Device Management/Hardware Information] on the navigation tree of switches to open the [Hardware Information] dialog box, which includes the module information of switches and contains two tables from the top down.


3-8

The upper table lists the status of all cards on current device, including slot No., type, description, CPU usage, hardware version, software version, sub slots number, administrative status and operation status.

The lower table lists the sub cards on the selected card. If no card selected, all the sub cards of current device will be listed. Sub card information includes slot No. (consistent with that of the card it is located), sub slot No., sub card type, ports number and sub card status. The value range of several key parameters is described in Table 3-12.

Table 3-12 Description on parameters of cards/sub cards

Parameter Description

Slot No./Sub Card Slot No.

The slot number where current card/sub card is located, sequenced from 0. Note that the first sub card of a card is the card itself.

Type

The type of the card identified by a character string in English, of which the meaning is same as the silk-screen characters on the card. In some special cases, the silk-screen characters of the same type of cards on different devices are a little different so as to differentiate some internal information. The type of the main control card of the 6506 series switches is "Main".

Sub Slot No. The number of the sub cards that can be plugged to the card

Administrative status

The administrative status of the card, including "Normal", "Fault" and "Forbidden".

Operation status

The operation status of the card that can be set to any of the following: "enable" (enable current card), "disable" (disable current card when the administrative status turns to "Forbidden"), "reset" (reset current card) and "test" (set to test status). Improper setting of this value may lead to service stop when only the reset operation is supported.

Sub Card Type

The type of the sub card identified by a character string in English, of which the meaning is same as the silk-screen characters on the sub card. In some special cases, the silk-screen characters of the same type of sub cards on different devices are a little different so as to differentiate some internal information. As the first sub card of a card is the card itself, the type is same as the card.

Ports Number The number of physical ports on the sub card

Sub Card Status The administrative status of the sub card, including "Normal", "Fault" and "Forbidden". The status except "Fault" of the sub card is consistent with that of the card.

The system supports card configuration and reset operations, where the configuration operation allows modifying the card description and the reset operation restarts the card.


3-9

Caution:

Resetting the selected main control card will cause the whole device to be rebooted.

3.4 SubCard Browsing of Routers

In the function pane, select [Device Management/SubCard Browsing] on the navigation tree and see the sub card information of a device on the right side. The related parameters are described in Table 3-13, Table 3-14, and Table 3-15.

Table 3-13 Description on the parameters of high-end routers and S8016 subcard browsing table

Name Description

Card Number Card number of the subcard.

SubCard Number Subcard number

SubCard Type Subcard type

Number of Ports Number of port on a subcard.

Hard Version Hardware Version of a subcard

Logic Version Logic Version of a subcard

Table 3-14 Description on the parameters of NE16 and NE08 device subcard browsing

Name Description

Card Number Card number of the subcard.

SubCard Number Subcard number

Type Subcard type

Description Subcard description.

Serial NO Unique hardware serial No. of a subcard. For example, 0 means the card is not in use.

Number of Ports Number of ports on a subcard

Hardware Ver Hardware Version of a subcard

Software Ver Software Version of a subcard

Admin Status Administration status of a subcard

Operation Status Operation status of a subcard


3-10

Table 3-15 Description on the parameters of middle-range and low-end routers subcard browsing

Name Description

Slot No. Slot number of a subcard

Type Subcard type

Number of Ports Number of ports on a subcard.

Software Version Subcard software version.

Hardware Version Subcard hardware version.

3.5 Clock Source Browsing

You can browse the information about the clock source of the high-end routers and S8016. In the function pane, select [Device Management/ClockSrc Browsing] on the navigation tree and see the information about clock source on the right side. The Clock Source Browsing Table has some parameters described in the following table.

Table 3-16 Description on the parameters of the Clock Source Browsing Table

Name Description

Index Reference source index.

Description Description on the clock

SSM Level

Shows the SSM level, which can be 1: Unknown synchronous quality; 2: G8.11 clock signal; 3: G.812 transit node clock signal; 4: G.812 local node clock signal; 5: SDH device clock source signal; or 6: No synchronization

Priority Priority of the clock reference source, ranging from 1 to 19. 19 means no clock source is set.

Time-slot

Set the timeslots to extract ssm level for 2Mbps bits clock source. sa4: Set the timeslot of the clock reference source sa as sa4; sa5: Set the timeslot of the clock reference source sa as sa5; sa6: Set the timeslot of the clock reference source sa as sa6; sa7: Set the timeslot of the clock reference source sa as sa7; and sa8: Set the timeslot of the clock reference source sa as sa8.

ForceSSM Shows if the clock board extracts SSM level from the input signals by force. 1: Not extract; 2: Extract.

3.6 Fan Browsing

This function makes it possible to monitor the fans of the devices. The monitored information varies with different devices. The related parameters are described in Table 3-17, Table 3-18, and Table 3-19.


3-11

Table 3-17 Description on the parameters of core routers and S8016 fan browsing table

Name Description

Slot No. Slot number of a fan of NE80, which can be 25 (upper FANA) or 26 (lower FANB).

Online Status Shows if a fan is online or offline.

Sub-Fans Number of sub-fans. FANA has 4 sub-fans, while FANB has 3 sub-fans.

Self-Test Result Self-test result of a fan

Software Version Software Version of a fan

Hardware Version Hardware Version of a fan

Temperature The temperature of a fan, which ranges from 20 to 50 normally.

Running Status Running status of a fan, which can be normal or abnormal.

Control Mode Time control mode of a fan, which can be 1 (manual), 2 (automatic), or 3 (none).

Speed Adjustment Information

Shows the speed adjustment information of a fan as Series or noseries.

Speed Type Shows the speed type of a fan as LowSpeed or HighSpeed.

Table 3-18 Description on the parameters of NE40 Series Routers’ fan browsing table

Name Description

Fan index Hardware serial number of a fan

Online status Shows if the fan is online or offline.

Running status Shows the running status of a fan as normal or abnormal.

Table 3-19 Description on the parameters of switches’ fan browsing table

Name Description

Device name Identifier of the device that the fan belongs to

Fan slot No. Slot No. of the fan in the switch

Fan status Running status of the fan: active-normal; deactive-stopped; not_install-fan is not available in the slot


3-12

Caution:

3680E-RPS, 2631E-RPS, 2610-RPS, and 2611-RPS only allow fan status monitoring.

3.7 Power Browsing

This function shows the running status of a specific power. The following information will be displayed: Power Index, Slot, Serial Number, Power Type, Duration, Working Status, Dissipation Status, Description, Has Power, Has Fan, Fan Operation Status, and so on. The parameters are described in the following tables.

Table 3-20 Description on the parameter of NE08/16 Series Router power browsing table

Name Description

Slot Slot number of power.

Serial Number Specifies the hardware serial number of the power.

Power Type Power type, which can be unknown, DC, and AC.

Duration Time passed since the power working status changed last time.

Working Status Working status of the power, which can be unknown, ON, or OFF.

Dissipation Status

Dissipation status of the fan, which can be unknown, good, alarm, or bad.

Description Name or description of the slot where the power is located.

Has Power Shows if the power is in position with unknown, exist, and inexistence.

Has Fan Shows if the fan is in position with unknown, exist, inexistence.

Fan Operation Status

The operation status of the fan, which can be unknown, highspeed, lowspeed, or stop.

Table 3-21 Description on the parameter of core router and S8016 power browsing table

Name Description

Index Specifies the hardware serial number of the power.

Power Type Power type, which can be Power and Dpower (Distributed power).

Status Working status of the power, which can be normal or abnormal.

Description Description on the power.


3-13

Name Description

Slot Number Inside slot number of the power, which can be PowerModule1, PowerModule2, PowerModule3, PowerModule4, PowerModule5 or Dpower (Distributed power).

Table 3-22 Description on the parameter of NE40 Series Router power browsing table

Name Description

Power index Specifies the hardware serial number of the power.

Online status Shows if the power is in position with online or offline.

Running status Running status of the power, which can be normal or abnormal.

Table 3-23 Description on the parameter of switches’ power browsing table

Name Description

Device name Identifier of the device that the power belongs to

Power slot No. Slot No. of the power in the switch

Power status Running status of the power: active-normal; deactive-stopped; not_install-the power is not available in the slot

Caution:

3680E-RPS, 2631E-RPS, 2610-RPS, and 2611-RPS only allow the power status monitoring.

3.8 Active/Standby Switching

High-speed and stability are the two important features for core router and S8016 device. To implement stability, the user should configure 1+1 backup work mode for main control board, network board and clock board when the device is configured fully. When the active board works abnormally and the service is affected, the system will switch to standby board automatically. The active/standby switching can implement the data backup and data smoothness. The function is especially important for the system.

Quidview NMS provides active/standby switching function for core router and S8016 device to implement such switching as main control board, clock board and network board. Select [Device Management/Card Standby Switch] on the navigation tree and the [Card Standby Switch] dialog box pops up. This dialog box displays the switching


3-14

date and time of main control board. According to the demand, the user can select <Switch MPU>, <Switch CLK>, and <Switch NET> in this dialog box to perform the switchover of main control board, clock board and network board.

Click <Refresh> in the dialog box, and the system will re-read latest data from the device and display the data on the dialog box through refreshing.

3.9 Attribute Config

Quidview NMS can query the aging time of current ARP table of core router and S8016 device and can configure the aging time. Select [Device Management/Attribute Config] on the navigation tree, and the [Attribute Config] dialog box pops up. The aging time of ARP table can be queried and configured in this dialog box.

3.10 Card Reset

Only the core router has this function.

In the [Panel Monitoring] dialog box, select the card to be reset and select [Device Management/Card Reset] on the navigation tree, and the [Card Reset] dialog box will pop up.

Click <Config> in this dialog box, the user can re-upgrade the data to the device to complete card reset function.

To reset many cards at one time, the user can select many cards in the [Panel Monitoring] dialog box after opening the [Card Reset] dialog box. The list in the [Card Reset] dialog box will display many entries and the user can select multiple entries according to demand, and then click <Config> to complete the reset function of many boards.

Click <Refresh> to re-read data from the device. Click <Clear> and <Clear All> to delete the selected entries or all entries in board reset list and the user does not need to perform reset operation for those cards.

3.11 L2 Forwarding Table Management

3.11.1 Querying L2 Forwarding Table Information

This function is to query the L2 forwarding table information on Core routers and S8016 Core switch. Select [Device Management/L2 Forwarding Table Management] on the navigation tree to open the [L2 Forwarding Table Management] dialog box, as shown in Figure 3-1.


3-15

Figure 3-1 L2 Forwarding Table Management

Descriptions of the parameters in the dialog box are listed in Table 3-24.

Table 3-24 Description on the parameters of L2 Forwarding Table Management

Name Description

MAC Address Source MAC address in the data packet

VLAN ID VLAN ID

Forwarding Port Name of the forwarding port, option differs as selected VLAN ID changes

Packet Filter Type Type of packets to be filtered. For S8016, three types are available: static, permanent and blackhole; for Core routers, only two types available: static and blackhole

Click <Refresh> in the [L2 Forwarding Table Management] window and system will read the L2 forwarding table data to refresh the displayed information.

3.11.2 Creating L2 Forwarding Entry

Click <Add> in the L2 Forwarding Table Management] window and [L2 Forwarding Entry Creation] dialog box will pop up, as shown in Figure 3-2.


3-16

Figure 3-2 L2 Forwarding Entry Creation

Input MAC address in the dialog box and select VLAN ID. All the ports involved in the specified VLAN and all TRUNK ports will be automatically displayed in the [Forwarding Port] list. Please select necessary ports for forwarding. Select packet filter type and click <OK> to create a new L2 forwarding entry.

3.11.3 Deleting L2 Forwarding Entry

Select one or more lines in the [L2 Forwarding Table Management] window and click <Delete> to delete selected entries. If only some of the selected entries are deleted, the system will give prompt to notice that deletion was not executed successfully.

3.11.4 Configuring L2 Forwarding Entry

Configuring L2 forwarding entry is similar to creating one. The only difference is, MAC address and VLAN ID cannot be modified here. See section 3.11.2 “Creating L2 Forwarding Entry” for details.

3.11.5 Querying and Configuring L2 Forwarding Table Aging Time

Modification of L2 forwarding table aging time is available here. When an entry keeps un-refreshed within the aging time, it will be deleted by system.

Click <Aging Time…> in the [L2 Forwarding Table Management] window and the [L2 Forwarding Table Aging Time Management] dialog box will pop up, as show in Figure 3-3.


3-17

Figure 3-3 L2 Forwarding Table Aging Time Management

If Yes is selected, the aging time can be modified in the range of 10s to 1000000s. If No is selected, the [Aging Time] field will be disabled and no modification is available.

3.12 Environment Monitor

Select [Device Management/Environment Monitor] on the function pane, and the [Environment Monitor] dialog box will pop up. The dialog box displays the status of each card, temperature, and the upper limit and lower limit of temperature alarm.

To refresh the data of all cards, click <Refresh>.

To close the dialog box, click <Close>.

3.13 Saving Configuration

Select [Device Management/Save Configuration] in the function pane to open the [Configuration Saving] dialog box. Click <OK>, the system deploys command and the device will write the configuration in the memory to FLASH. The latest configuration will be valid until the device is restarted. This operation is equal to the "write" or "save" command and is irretrievable.

Click <Cancel>, and the system does nothing.

3.14 Resetting Device

Select [Device Management/Reset Device] node in the function pane to open the [Device Resetting] dialog box. Click <OK>, and the system will prompt whether to save the configuration. Generally, the configuration should be saved before device reset. Otherwise, the new configuration made after last saving will be lost. The reset operation will continue no matter you save the configuration or not. The reset operation will last for several minutes during which the device may lose connection with the system. During this period you can switch to manage other devices.


3-18

Click <Cancel>, and the system does nothing.

User Manual Volume I Quidview Device Manager Chapter 4 Port Management

4-1

Chapter 4 Port Management

4.1 Port Browsing

The port browsing function can display port related configuration information that will be automatically refreshed at certain interval. The user can browse the configuration information of various ports through modifying the value of port index.

Double-click [Port Management/Port Information] on function tree and the device port information displayed in right information display area is shown as Figure 4-1.

Figure 4-1 Port basic information management-port basic information

There are two tabs in the port information interface, and the description of various parameters in the interface is shown in Table 4-1.

Table 4-1 Parameter description of port basic information interface

Name Description

Interface Index Index number of current interface

Interface Description Characteristic description of interface

Interface Alias The alias of the interface that is easier to memorize.

Interface Type Network type of interface

MTU Maximum transmission unit allowed by current interface

Interface Speed Maximum transmission speed allowed by current interface, unit: bit/s


4-2

Name Description

Physical Address Interface physical address. The interface without physical address is represented with all 0.

Administration Status Current administration status of interface: UP; DOWN.

Operation Status Current operation status of interface: UP; DOWN.

Last Status Change Time Time of last change of interface status

When switching to the IP address information tab, the interface is shown in Figure 4-2.

Figure 4-2 Port basic information management-IP Address Information

I. Adding an IP address

Click <Add…> in Figure 4-2 to open the [Add Port IP Address] dialog box. Here select Chief Address or Sub Address, type an IP address and the mask, and click <OK> to add an IP address. Usually, a port needs only one IP address. When a router port needs connecting with several subnets, it can also be configured with several IP addresses with one as the chief IP address and the others as sub IP addresses.

II. Deleting all IP addresses

Click <Delete All> in Figure 4-2 to open the confirmation dialog box, where confirm to delete all the IP addresses configured for the port.


4-3

Note:

Port IP address configuration is not available unless the Telnet parameters of the device is configured properly in authentication options.

4.2 Subport Browsing

The user can browse the related information of various sub-ports for the physical port including subports.

Double-click [Port Management/Subport Browsing] on function tree and the device subport configuration information will be displayed in right information display area. The description of various parameters in subport information browsing table is shown in Table 4-2.

Table 4-2 Description on the parameters in the subport information browsing table

Name Description

Interface Index Index number of current subport

Interface Description Characteristic description of current subport

Administration Status Current administration status of port: UP; DOWN

Operation Status Current operation status of port: UP; DOWN

4.3 Port Time Slot

If the device has E1, T1, E3 and T3 ports, the user can view the encapsulation of various time slot interfaces of these ports. The encapsulation of E1/cE1 is described as an example.

E1/cE1 port refers to the channelizable E1, i.e., Channelized E1. It has two work modes: E1 and cE1 work mode.

When working in E1 mode, E1/cE1 port equals to an interface whose data bandwidth is 2.048M and that has no time slot division. Its logical feature is same as synchronous serial port. E1/cE1 port supports such link layer protocol as PPP and frame relay, and supports such network protocols as IP.

When working in cE1 mode, E1/cE1 port is divided into 32 time slots physically and the time slots are numbered 0 to 31 correspondingly. 31 time slots of them can be divided into some groups at will (time slot 0 is used to transmit frame synchronization signal and cannot be bundled). Each group of time slots are bundled as one serial port (channel-group) whose logical feature is same as the


4-4

synchronous serial port. It supports such link layer protocols as PPP, HDLC, FR, LAPB and X.25, and supports such network protocols as IP.

Double-click [Port Management/Channel Group] on function tree and the interface time slot information will be displayed in right information display area. The description of various parameters in interface time slot browsing is shown in Table 4-3.

Table 4-3 Parameters description of interface time slot table

Name Description

Interface Description Each group time slots are bundled as a serial port (channel-group). Here, the interface description refers to the description of channel-group.

Channel Group No. Channel group number, ranging from 0 to 30.

Binding Timeslot Number

Total amount of time slots bundled on channel group successfully.

Administration Status Current administration status of port: UP; DOWN

Operation Status Current operation status of port: UP; DOWN

4.4 Port Up/Down Configuration

This function can configure the administration status of interface. Double-click [Port Management/Port UP/Down Configuration] on function tree to open the port configuration dialog box. Here select the administration status of the interface from the drop-down list box to complete the interface UP/Down configuration.

4.5 Port Mirror Management

Port mirror functions mapping special traffic to a monitoring port for network debugging. It falls into the following types according to the selected traffic types:

Physical port based mirror: copies the traffic of a specified port fully to a monitoring port.

VLAN based mirror: copies the traffic of a specified VLAN fully to a monitoring port. Virtual port based mirror: copies the traffic of a specified VLAN on a specified port

fully to a monitoring port.

S8016 supports physical port based mirror.

In the function pane, double-click on [Port Management/Port Mirror Management] node on the function tree to open the [Port Mirror Management] dialog box, as shown in Figure 4-3.


4-5

Figure 4-3 Port mirror management - Monitoring port

This dialog box includes two tabbed pages, Monitoring Port and Port Mirror. Their functions are detailed as follows:

4.5.1 Monitoring Port Management

I. Adding a monitoring port

In Figure 4-3, click <Add…> to enter the [Monitoring Port Creation] dialog box, as shown in Figure 4-4.

Figure 4-4 Monitoring port creation

Select the description of the port to be created and specify whether to permit data flow on the port, then click <OK> to create a monitoring port.

II. Deleting a monitoring port

Select one or more monitoring ports from the monitoring port list and click <Delete> to delete them.


4-6

III. Changing status

Select a monitoring port from the monitoring port list and click <Change Status>. After confirmation, you can change the data flow status of the port.

4.5.2 Port Mirror Management

The [Port Mirror Management] dialog box is shown in the following figure:

Figure 4-5 Port mirror management - Port mirror

I. Adding a mirroring port

In Figure 4-5, click <Add…> to open the [Port Mirror Creation] dialog box, as shown in Figure 4-6.

Figure 4-6 Port mirror creation


4-7

Various parameters in the dialog box are described in Table 4-4.

Table 4-4 Port mirror parameters

Name Description

Mirroring Port Index of the mirroring port

Ingress Monitoring Index of the ingress monitoring port

Egress Monitoring Index of the egress monitoring port

Select the parameters and click <OK> to create a mirroring port.

II. Deleting a mirroring port

Select one or more mirroring ports from the mirroring port list and click <Delete> to delete them.

4.6 Port L2/L3 Configuration

This function is available only on Core routers. Double-click [Port Management/Port L2&L3 Configuration] node on function tree to open the [Port L2/L3 Configuration] dialog box, as shown in Figure 4-7.

Figure 4-7 Port L2/L3 Configuration

Parameter descriptions are shown in Table 4-5.


4-8

Table 4-5 Parameters description of Port L2/L3 Configuration

Name Description

Interface Index Index of the interface.

Interface Description Text description of the interface.

Type Type of the interface, l2port refers to layer 2 port, l3port refers to layer 3 interface.

Select the interfaces to be configured from the dialog box (multiple selection available here) and click <Change Type> to switch the layer attribute of the interface. By doing so, layer 2 interface changes to layer 3 interface and vice versa.

4.7 Link-aggregation Management

This function is available on Core routers and S8016 Core switch. These devices support aggregating multiple ports into one logical port which is called link-aggregation. The aggregated link supports automatic port traffic balancing protection by adopting traffic arranging algorithm, which ensures balanced traffic among the physical links. Packets to be sent via this aggregated link will be forwarded through any one (and the only one) physical link among all the aggregated links. The service quality and packets order are guaranteed by the dispatching policy on the physical link. If one or more physical links break, traffic though these links will be automatically directed to other good links. And after the recovery of the links, traffic will be automatically distributed again among all the good links.

The link type will be Point to Point after the link-aggregation. It demands that the peer (e.g. ethernetswitch) side supports link aggregation also. However, the traffic arranging algorithm can be different between the link aggregations on the two peers.

4.7.1 Querying Link-aggregation Information

Double-click [Port Management/Link-aggregation Management] node on function tree to open the [Link-aggregation Management] dialog box, as shown in Figure 4-8.


4-9

Figure 4-8 Link-aggregation Management

Descriptions of the parameters in the dialog box are listed in Table 4-6.

Table 4-6 Parameters description of Link-aggregation Management

Name Description

Link-aggregation List Text description of the main port of the aggregation

Slave Port List Text description of the slave ports of the aggregation

Information of all the link-aggregations can be queried here. The main ports of the link-aggregations are shown in the left dialog box. Click one of them and all the slave ports involved in the link-aggregation will be displayed in the [Slave Port List] dialog box to the right.

4.7.2 Add Link-aggregation

Click <Add…> in the [Link-aggregation Management] and [Link-aggregation Creation] dialog boxes will pop out as shown in Figure 4-9.


4-10

Figure 4-9 Link-aggregation Creation

Select the main port of the aggregation in the [Master Port] list. Then select one or more slave ports to be added into the aggregation in the [Available Slave Ports] list and click <>>> to add them into the Selected Slave Ports list. Click <OK> to finish creating the link-aggregation.

Note:

Observing port and ports already involved in other link-aggregations are not available for new aggregations. So they will not appear in the [Master Port] list. What’s more, auto-negotiating port cannot be used in aggregations;

After selecting the master port, contents in the Available Port List will change respectively. All the slave ports involved in a link-aggregation cannot exceed the number of 7.

4.7.3 Delete Link-aggregation

Select one or more lines in [Link-aggregation List] in the [Link-aggregation Management] dialog box. Then click <Delete> to delete the corresponding aggregations.


4-11

4.7.4 Config Link-aggregation

Select one line in [Link-aggregation List] in the [Link-aggregation Management] dialog box. Then Click <Config…> and the [Link-aggregation Configuration] dialog box will be displayed as shown in Figure 4-10.

Figure 4-10 Link-aggregation Configuration

Click <>>> or <<<> to add or remove slave ports to the link-aggregation in the dialog box. Click <OK> to finish the configuration.

User Manual Volume I Quidview Device Manager Chapter 5 Performance Monitoring

5-1

Chapter 5 Performance Monitoring

5.1 Operation Description

Performance monitoring is primarily used to display the statistical information of the specified performance monitoring items in the format of a bar graph or a fold-line graph, and to refresh the display at the preset interval. This makes it convenient for the network administrator to learn about the operation status of the device and to conduct troubleshooting in urgent situations.

The performance monitoring function mainly includes device monitoring, system monitoring, board monitoring, RMON, and SMON specific to S5516 switches.

This chapter elaborates on the first several monitoring functions. RMON will be introduced in Chapter 6 “RMON Management”, and SMON will be introduced in Quidview Device Manager User Manual Volume II.

The following details the use of the monitoring dialog box by taking device monitoring as an example.

Double-click on [Performance Monitoring/Device Monitoring] node on the function tree, and the [Device Monitoring] dialog box appears on the right information display area.

This dialog box is separated into two parts, as follows:

1) Functional buttons

On the left of the dialog box are functional buttons that are, from the top down, <Select Items>, <Bar>, <Plot>, <Exporting Data>, <Importing Data> and <Properties>. If you position the cursor over the buttons for a few seconds, the corresponding tips will be displayed.

2) Display area of monitoring results

It lies in the middle of the dialog box, showing the monitoring results in the format of a bar graph or a fold-line graph.

I. Usage example

1) Select the proper polling interval and maximum number samples to be displayed.

In the [Device Monitoring] dialog box, click <Properties> to open the [Properties] dialog box. Here specify the proper values for Interval(s) and Max Samples items, and click <OK> to close the dialog box.

By default, the polling interval is 60s and the maximum number of samples is 500.

2) Select new items

In the [Device Monitoring] dialog box, click <Select Items> to open the [Select Monitor Item] dialog box. You are required to select a group first, and then the monitoring items


5-2

from the list. You may select several items by holding down <Shift> (<Ctrl>) on while clicking several items. The monitoring results of these items will be displayed in the result display area in different colors. After selection, click <OK> to start polling monitoring immediately.

You can also customize default settings as follows: Select the items to be monitored, and click <Default>. When you open the [Device Monitor] window next time, the system will monitor these selected monitor items by default.

Caution:

After new monitoring items are selected, the information displayed in the result area will be cleared and new polling monitoring will be started.

3) Browse monitoring results

You may select to browse the monitoring results in a bar graph or a fold-line graph on demand, where different items are displayed in different colors. The system reads the values of the items from the device at certain interval and refreshes the graph accordingly. After the number of the displayed records reaches the value of "Max Samples", the whole graph will move leftward horizontally, having the new record replace the earliest record one by one.

Finally, you may export or import monitored data on demand to facilitate data access.

5.2 Device Monitoring

This function is mainly used to monitor device traffic on a real-time basis so as to show the operation trend of the device within certain interval. This will provide reference for the network administrator in troubleshooting.

The system categorizes device monitoring into the following groups: IP traffic, TCP traffic, UDP traffic, ICMP traffic, SNMP traffic, SNMP operation, and SNMP error. The items to be monitored vary with different groups. For the specific monitored items, refer to online helps.

5.3 Port Monitoring

This function is mainly used to monitor some important statistical data of the port on a real-time basis, so as to show the operation trend of the port within certain interval. This will provide reference for the network administrator in network troubleshooting.

The system categorizes port monitoring into the following groups: low speed port traffic, high speed port traffic, and bandwidth utilization of port. The items to be monitored vary with different groups. For the specific monitored items, refer to online helps.


5-3

In the [Port Monitoring] window, you can also select one or more ports to be monitored as needed.

Tip:

After the [Port Monitoring] window is opened, you can click multiple ports on the panel view one by one, so their related information can be monitored together.

5.4 System Monitoring

This function is mainly used to monitor system loading and status of low-end and mid-range routers on a real-time basis, so as to show the operation trend of the systems within a certain interval. This will provide reference for the network administrators in network troubleshooting.

The system classifies port monitoring into two groups: system loading and system status. Each group includes different items to be monitored. For details, refer to online helps.

5.5 Card Monitoring

This function monitors the status of device cards on a real-time basis. For the specific items to be monitored, refer to online helps.

User Manual Volume I Quidview Device Manager Chapter 6 RMON Management

6-1

Chapter 6 RMON Management

RMON (Remote Monitoring) is the most important improvement to the SNMP. It is used to reduce the requirements for network bandwidth in an efficient manner, to realize value-added analysis of network data and to facilitate network management and decrease network loading.

RMON management is primarily used for remote monitoring and management on host devices based on the monitoring and configuration functions of statistics, history, alarm and event groups defined in RMON-MIB of RFC1757 and extended alarm MIB defined by Huawei-3Com. In addition, it also provides graphical monitoring, browsing and configuration interfaces.

The RMON management function provided in Quidview Device Manager includes:

Configuration of real-time monitoring of statistics group Configuration and data browsing of history group Configuration and browsing of alarm group Configuration and browsing of event group Configuration and browsing of alarm extended group Browsing of log information corresponding to event group

6.1 Configuration and Real-time Monitoring of Statistics Group

The statistics group provides related information about the loading and overall robustness of the subnet. This information can be obtained by configuring the network management host to monitor different interfaces and to poll the statistical information periodically.

The real-time monitoring function of statistical data performs real-time monitoring on the statistical variables of the specified interface on the device. Users can select the interface and statistical variables and perform real-time monitoring on the statistical data in a plot graph.

Enable Quidview Device Manager. Select [Device/Open Device…] or click to

open the panel view of a certain device. In the function pane, select [Performance Monitor/RMON] to enter the [RMON] dialog box, as shown in Figure 6-1:


6-2

Figure 6-1 RMON

The main interface of RMON management comprises six property tabs, namely statistics group, history group, alarm group, event group, alarm extended group and log. By default, the [Statistics Group] tab is displayed.

Note:

The tab pages shown in Figure 6-1 vary with different devices.

Meaning of various fields in statistics group is described in Table 6-1.

Table 6-1 Statistics Group

Field name Description

Index Index of the configuration item of the statistics group

Port Description Port name

Received Bytes The number of bytes received on the port

Received Packets The number of packets received on the port

Owner Owner of the configuration item of the statistics group

Status Status of the port, including Activate and Inactivate.

In this dialog box, you may implement such functions as adding a statistics item, deleting a statistics item, refreshing the statistics items, real-time monitoring, etc. Various functions are detailed below.

6.1.1 Add a Statistics Item

In Figure 6-1, click <Add…> to open the [Add a Statistics Item] dialog box as shown in Figure 6-2.


6-3

Figure 6-2 Add a Statistics Item

In this dialog box, enter the information of Ethernet port and owner, where the [Port] label refers to the source port of the data and the [Owner] label refers to by whom the configuration item of the statistics group is created (by default, it is monitor, and you may also specify another name).

6.1.2 Delete a Statistics Item

In Figure 6-1, select a statistics item or several consecutive (or separate) statistics items by holding down <Shift> (or <Ctrl>) while clicking several statistics items. Then click <Delete> and click <OK> in the popup [Prompt] dialog box to delete the selected statistics items.

6.1.3 Real-time Monitoring

The real-time monitoring function of the statistics group displays the statistical information of the specified configuration items in statistics group in the format of a table, histogram or plot graph and refreshes the information display periodically according to the specified interval.

In Figure 6-1, click <Real-time Monitor…> to enter the [Statistics Group Real-time Monitoring] dialog box, as shown in Figure 6-3.


6-4

Figure 6-3 Statistics Group Real-time Monitoring

This dialog box is broken into two parts as follows:

Functional buttons

On the left of the dialog box are the functional buttons that are, from the top down: <Select Items>, <Bar>, <Realtime Grid>, <Plot>, <Export Data>, <Import Data> and <Properties>.

Display area of monitoring results

It lies in the middle of the dialog box, displaying the results of monitoring in the format of Chart & Grid, Bar or Plot.

I. Select items

In Figure 6-3, click to open the [Select Items to be Monitored] dialog box, as shown

in Figure 6-4.


6-5

Figure 6-4 Select Items to be Monitored

This dialog box consists of such two tabs as [Same Port] and [Same Variable], which monitor the values of several statistical variables of the same port and the same statistical variable of different ports respectively.

II. Bar, realtime grid, plot

The system provides several information display modes such as Bar, Realtime Grid, and Plot, etc. You may click the corresponding buttons to display the statistical information in different modes.

III. Importing data/Exporting data

You may select the functional buttons <Export Data> and <Import Data> in the [Statistics Group Real-time Monitoring] dialog box to export the monitoring results to a file or import the corresponding monitoring results from a file.

IV. Properties

This function is used to adjust the system polling interval and the maximum number of values that can be displayed in result-displaying graph.


6-6

6.2 Configuration and Data Browsing of History Group

The history group is used to define the collection function for several interfaces, including setting history data collection task for a given device, collecting data on the specified interface and displaying collection results in the specified mode.

6.2.1 Configuration of History Group

1) Adding a history item

In the [RMON] window, click the [History Group] tab to open the data browsing and configuration interface of history group, as shown in Figure 6-5. The list on the left displays all history items defined for the device and the meaning of various fields is described in Table 6-2. Various functional buttons on the right provide configuration and browsing functions for history items.

Figure 6-5 RMON - Configuration and Data Browsing of History Group

Table 6-2 History Group

Content Description

Index Index of the configuration item in the history group.


Configured Maximum Samples

The number of discrete sampling intervals required. By, default it is 50.

Actual Maximum Samples The actual number of discrete sapling intervals.

Sampling Interval Data sampling interval in seconds. It is a value in the range of 1 to 3600 and the default value is 1800.

Owner Owner of the configuration item of the history group.

Status The status of the port, including Active and Inactive.

Click <Add…>, and the [Add a History Item] dialog box pops up, as shown in Figure 6-6.


6-7

Figure 6-6 Add a History Item

Information to be inputted in this dialog box is described in Table 6-3.

Table 6-3 Information to be inputted in adding a history item

Content Description

Port The source data port of the collection task must be specified. Here a drop-down list box is provided for you to select the Ethernet port for data collection.

Sampling Interval

Data collection interval on the specified device port in the units of second. It is a value in the range of 10 to 3600 and the default value is 1800.

Configured Maximum Samples

The maximum number of samples that can be reserved for the collection task by the device. It is a value in the range of 1 to 50 and the default value is 50. A device reserves the last N (the maximum sampling amount allowed) samples, which is decided by the storage capacity of the device and should set properly (not too large) to save system resources.

Owner By whom the collection task is created and the default value is monitor. You may also input another name.

Caution:

When adding a history item, the newly entered port and sampling interval cannot be same with those of an existent item simultaneously. Otherwise, the operation will fail and a prompt dialog box will pop up, showing "The combination of port and sampling interval cannot be repeated".


6-8

2) Deleting history items

In Figure 6-5, select one or more history items and click <Delete>. Then click <OK> in the popup [Prompt] dialog box to delete the selected history items.

6.2.2 Data Browsing of History Group

The history table contains the history statistics information collected by the host according to the monitoring items set in history control table. Data browsing of history group means to display the history table information of the specified configuration items in history group in the format of a table, histogram or plot graph.

In Figure 6-5, click <Browse…> to open the [Browse History] dialog box, as shown in Figure 6-7.

Figure 6-7 Browse History

The use of the first button in this dialog box is described below and the other functions are the same as those of statistics group and will be omitted here.

In Figure 6-7, click to open the [Select Items to be Monitored] dialog box, which

consists of such parts as [Data Item] and [Control Item]. The [Data Item] list contains the data items that can be browsed by users and the [Control Item] list contains history items for users to select from. After selection, click <OK> to browse the data in history group in various modes (Realtime Grid, Bar or Plot).


6-9

Caution:

If you click <Browse…> during the sampling interval of the selected history item, a prompt dialog box will pop up, indicating that reading device data failed. That is because history data is to be generated.

The data in the [Browse History] dialog box is static. Only when you re-open the dialog box can you view the new data.

6.3 Configuration and Data Browsing of Alarm Group

The alarm group management is used to monitor the statistics information of the specified port. When the value of the monitored data crosses the corresponding threshold, an alarm event will be created. Usually, alarm event is recorded into device log and a Trap is sent to the network management station simultaneously. The alarm events are defined in event management. Alarm group is composed of independent alarm configuration items, each of which specifies a special monitoring variable, a sampling interval and the related thresholds.

The functions of alarm group management includes: browsing/adding/deleting alarm items, related event definition and log browsing.

In the [RMON] window, click the [Alarm Group] tab to open the data browsing and configuration dialog box of alarm group, as shown in Figure 6-8. The list on the left displays all alarm items defined for the device and meaning of various fields is described in Table 6-4. The functional buttons on the right provide configuration and browsing functions of the alarm items.

Figure 6-8 RMON – Configuration and Data Browsing of Alarm Group


6-10

Table 6-4 Displayed information of alarm group

Content Description

Index The unique identification of the alarm item.

Interval Sampling interval of the alarm data in the range of 1 second to 3600 seconds.

Statistics Item MIB variable to be monitored, including such two sections as statistical variable and port name.

Sampling Type Include absolute sampling and relative sampling.

Current Sampling Value Statistical data collected during the last sampling interval.

Startup Type Include rising and falling alarm allowed, rising alarm allowed, and falling alarm allowed.

Rising Threshold Threshold of rising alarms. If the monitored data crosses this value, a rising alarm will be generated.

Falling Threshold Threshold of falling alarms. If the monitored data crosses this value, a falling alarm will be generated.

Rising Event Index Index of rising event

Falling Event Index Index of falling event

Owner By whom the alarm configuration item is created

Status Include Active and Inactive.

6.3.1 Adding an Alarm Item

Click <Add…> in above dialog box to open the [Add an Alarm Item] dialog box, as shown in Figure 6-9.


6-11

Figure 6-9 Add an Alarm Item

This dialog box is broken into such three parts as [Alarm Variable], [Sampling Properties] and [Alarm Threshold and Related Events]. The meanings of various configuration items are described in Table 6-5.

Table 6-5 Meanings of various configuration items in adding an alarm item

Content Description

Statistics Item The variable to be monitored

Port Description of the port that is monitored by the configuration item of the statistics group.

Interval (second) Sampling interval in the units of second and in the range of 1 to 3600. By default, it is 10.

Type

Include absolute sampling and relative sampling. Absolute sampling refers to the accumulated value from the startup of the system to present and relative sampling refers to current absolute sampling value minus last absolute sampling value. Relative sampling is commonly adopted, whose value is related to sampling interval.

Owner By whom the alarm item is created. The default value is monitor. Users can also input other names.


6-12

Content Description

Alarm Threshold and Related Events

Threshold of the creation of alarms and events to be generated. It includes such two sections as alarm type control and thresholds and events input. If the Create Default Event check box is not selected, you need to input values in the [Rising Threshold], [Falling Threshold], [Rising Event Index] and [Falling Event Index] fields respectively. If the check box is selected, you do not need to input the indices, and an event definition is generated automatically according to the selected variables.

Rising Threshold When the monitored alarm item crosses (larger than) this value, an alarm will be created.

Rising Event Index Index of the rising event

Falling Threshold

When the monitored alarm item crosses (larger than) this value, an alarm will be created.

Falling Event Index Index of the falling event

Caution:

When adding an alarm item, make sure that the statistics item, port and sampling interval of the newly inputted item are not the same as those of any existent item simultaneously. Otherwise, the operation will fail.

6.3.2 Configuring an Alarm Item

In Figure 6-8, select an alarm item and click <Configure…>, and then all the configuration items in the [Add an Alarm Item] dialog box except [Alarm Variable] are available for modifying.

6.3.3 Deleting Alarm Items

In Figure 6-8, select one or more alarm items and click <Delete>. Then click <OK> in the popup [Prompt] dialog box to delete the selected alarm items.

6.3.4 Displaying Invalid Alarm Items

The event definitions invoked by alarm configuration items may be deleted by other users, which will invalidate the corresponding alarm configuration items. In the meantime, some alarm configuration items may not be activated. Therefore, this


6-13

function is provided for users to view and clear the invalidated alarm configuration items or revalidate them through modification.

On the [Alarm Group] tab (as shown in Figure 6-8), click <Invalid Items> to display the invalid alarm items, as shown in Figure 6-10.

Figure 6-10 Displaying invalid alarm items

The contents of this interface are basically the same as those of Figure 6-8 except the [Reason for Null] field, which is new on this interface and is used to describe the alarm item failure reason.

On this interface, clicking <All Items> will switch to the interface shown in Figure 6-8.

6.4 Configuration and Log Browsing of Event Group

The event group supports definitions of events. An event can either be triggered by other conditions defined in the MIB or trigger other actions defined in the MIB. In addition, the creation of an event can have the information be recorded in the event group and have the monitor of the host send SNMP Trap message.

The events defined in the event group are primarily used to define configuration items of the alarm group and extended alarm group, when the alarm thresholds and events to be created should be inputted in the [Alarm Threshold and Related Events] frame.

6.4.1 Adding an Event Item

In the [RMON] window, click the [Event Group] tab to open the data browsing and configuration dialog box of event group, as shown in Figure 6-11. The list on the left of the dialog box displays all event items defined for the device and meanings of various fields is described in Table 6-6. The functional buttons on the right provides configuration and browsing functions of various event items.


6-14

Figure 6-11 RMON – Configuration and Data Browsing of Event Group

Table 6-6 Event Group

Content Description

Index The unique identification of the event.

Event Description

Descriptive information of the event, which provides the clear meaning of the event.

Event Type

Include the following types: Log: the event will be recorded into RMON log after creation. SNMP Trap: SNMP Trap message will be sent after the creation of the event. Log and Trap: the event will be recorded into RMON log and SNMP Trap message will be sent by the host after creation of the event.

Trap Community

Community name used to send SNMP Trap message upon the creation of the event. It is effective only when the event type is SNMP Trap.

Event Last Trigger Time

Time when the event occurred the last time, which is maintained by the system.

Owner By whom the event is created. By default, it is monitor.


Click <Add…> to open the [Add an Event Item] dialog box. The meanings of the information to be inputted in this dialog box are described in Table 6-7.


6-15

Table 6-7 Contents to be configured in adding a configuration item of event group

Content Description

Description Descriptive information of the event, which provides the clear meaning of the event.

Type

Include the following types: Null: the alarm event is invalidated. Log: the event will be recorded into RMON log after creation. SNMP Trap: SNMP Trap message will be sent after the creation of the event. Log and Trap: the event will be recorded into RMON log and SNMP Trap message will be sent by the host after creation of the event.

Community Community name used to send SNMP Trap message upon the creation of the event. It is effective only when the event type is SNMP Trap.

Owner By whom the event is created. By default, it is monitor.

6.4.2 Deleting Event Items

In the data browsing and configuration dialog box of event group (Figure 6-11), select one or more event items and click <Delete>. Then click <OK> in the popup [Prompt] dialog box to delete the selected event items.

6.4.3 Displaying Invalid Event Items

Frequent adding, deleting and modifying operations on alarm configuration items may invalidate the definitions of some events. This function is used to display the invalidated events so as to facilitate the management (e.g. deleting) over them.

In Figure 6-11, click <Invalid Items> to display the invalid event list, as shown in Figure 6-12.

Figure 6-12 Displaying invalid event list


6-16

The information displayed in this interface is basically the same as that in Figure 6-11 except the [Reason for Null] field, which is new on this interface and is used to describe the failure reason for the event item.

6.4.4 Browsing Log Information Related to the Specified Event

In Figure 6-11, select one or more event items and click <View Log> to view the related log information of the specified events. For example, you can select the events of index 1 and index 2 respectively. Then, click <View Log>, and the logs related to the events of index 1 and index 2 will be displayed, because all these logs are triggered by the two events.

For descriptions on the fields in the log list, refer to Table 6-8.

Table 6-8 Log information

Field Description

Event Index Index of the event that triggers event or log

Log Index A unique integer that identifies the log. It is maintained by the system.

Log Time Time when the log occurs

Log Description Description on the log

Note:

Click <View Log> without selecting any event in Figure 6-11, and the system will display the information of all logs.

6.5 Configuration and Data Browsing of Alarm Extended Group

RMON alarm extension is used to manage RMON alarm extended group that is the extension of RMON alarm group. The alarm group can only set one object in MIB, whereas the alarm extended group, as indicated by the name, supports alarm configuration for both single object and object expressions, and supports settings of both interfaces and all valid instance values.

The NMS provides configuration of alarm extended group for the device that will generate alarms according to the set conditions. Because this type of alarm is caused by threshold-crossing of the monitored performance data on the device, it is also called "performance alarm".


6-17

In the [RMON] window, click the [Alarm Extended Group] tab to open the data browsing and configuration dialog box of alarm extended group, as shown in Figure 6-13. The list on the left of the dialog box displays all alarm extended items defined for the device and meanings of various fields are described in Table 6-9. The functional buttons on the right provides configuration and browsing functions of various event items.

Figure 6-13 RMON – Configuration and Data Browsing of Alarm Extended Group

Table 6-9 Alarm extended group

Content Description

Index The unique identification of the alarm item.

Interval Sampling interval of the alarm data in the range of 1 second to 3600 seconds.

Sampling Object Expression

The formula composed of OIDs and arithmetic operation expressions, whose result generates an alarm.

Object Expression Description Meanings of sampling object expression

Alarm Sampling Type

Include absolute sampling, relative sampling and rate sampling.

Alarm Value Statistical data collected during the last sampling interval.

Alarm Startup Type

Include rising and falling alarm allowed, rising alarm allowed and falling alarm allowed.

Rising Threshold Threshold of rising alarms. If the monitored data crosses this value, a rising alarm will be created.

Falling Threshold Threshold of falling alarms. If the monitored data crosses this value, a falling alarm will be created.

Rising Event Index Index of rising event

Falling Event Index Index of falling event

Stat. Period It is effective only when the sampling type is specified to periodical sampling. It specifies the duration from the creation of an alarm to expiration in the units of hour.


6-18

Content Description

Stat. Type

Include periodical sampling and permanent sampling. If periodical sampling is specified, the period must be specified in above edit box. If permanent sampling is specified, the sampling period edit box becomes ineffective.

Owner By whom the alarm configuration item is created


6.5.1 Adding an Alarm Extended Item

Click <Add…> in above dialog box to open the [Add an Alarm Extended Item] dialog box, as shown in Figure 6-14.

Figure 6-14 Add an Alarm Extended Item

This dialog box is broken into such three parts as Object Expression, Sampling Properties, and Alarm Threshold and Related Events. The meanings of various configuration items are described in Table 6-10.


6-19

Table 6-10 Meanings of various configuration items in the [Add an Alarm Extended Item] dialog box

Content Description

Expression Name Meanings of sampling object expression

Expression Formula

The formula composed of OIDs and arithmetic operation expressions, whose result generates an alarm.

Instance Value

It may correspond to any of the following logical entities: whole device, port number and other valid OID indexes. For different expression formulas, the available instance values are different. Therefore, it is recommended that the instance value be selected from the drop-down list to ensure its validity. For users familiar with the expression formula, this value can be input directly to accelerate the configuration, as it takes time to get data from the device if there are many instance values.

Interval (second) Sampling interval in the units of second and in the range of 1 to 3600s. By default it is 10.

Type

Include absolute sampling and relative sampling. Absolute sampling refers to the accumulated value from the startup of the system to present and relative sampling refers to current absolute sampling value minus last absolute sampling value. Relative sampling is commonly adopted, whose value is related to sampling interval.

Period Type

Include periodical sampling and permanent sampling. If periodical sampling is specified, the period must be specified in above edit box. If permanent sampling is specified, the sampling period edit box becomes ineffective.

Sampling Period It is effective only when the sampling type is specified to periodical sampling. It specifies the duration from the creation of an alarm to expiration in the units of hour.

Owner By whom the alarm extended item is created. The default value is monitor. You may also input another name.

Alarm Threshold and Related Events

Thresholds of the creation of alarms and events to be generated. It includes such two sections as alarm type control and thresholds and events input. If the [Create Default Event] check box is not selected, you need to input values in the [Rising Threshold], [Falling Threshold], [Rising Event Index] and [Falling Event Index] fields respectively. If the check box is selected, you do not need to input the indices, and an event definition is generated automatically according to the selected variables.

Rising Threshold When the monitored alarm item is larger than this value, rising alarm will be created.

Rising Event Index Index of the rising event


6-20

Content Description

Falling Threshold

When the monitored alarm item crosses (larger than) this value, an alarm will be created.

Falling Event Index Index of the falling event

Caution:

When adding an alarm extended configuration item, make sure that the expression, instance value and sampling interval of the newly inputted item are not the same as those of any existent item simultaneously. Otherwise, the operation will fail.

6.5.2 Configuring an Alarm Extended Item

In Figure 6-13, select an alarm extended item and click <Configure…>, and then all the configuration items in the [Add an Alarm Extended Item] dialog box except object expression are available for modifying.

6.5.3 Deleting Alarm Extended Items

In Figure 6-13, select one or more alarm extended items and click <Delete>. Then click <OK> in the popup [Prompt] dialog box to delete the selected alarm extended items.

6.5.4 Displaying Invalid Alarm Extended Items

The event definitions invoked by alarm extended configuration items may be deleted by other users, which will invalidate the corresponding alarm extended configuration items. In the meantime, some alarm extended configuration items may not be activated. Therefore, this function is provided to view and clear the invalidated alarm extended configuration items or revalidate them through modification.

In Figure 6-13, click <Invalid Items> to display the invalidated alarm items. The contents of this interface are basically the same as those of Figure 6-13 except the [Reason for Null] field, which is new on this interface and is used to describe the failure reason for the alarm configuration item.

On this interface, clicking <Restore Normal Display> will switch to Figure 6-8.


6-21

6.6 Browsing of Log Information

In the [RMON] window, click the [Log] tab to open the log information interface, where all the current log information of the system is displayed. The description on the fields is shown in Table 6-8.

User Manual Volume I Quidview Device Manager Chapter 7 VLAN Management

7-1

Chapter 7 VLAN Management

Virtual local area network (VLAN) is a protocol brought forward to resolve the Ethernet broadcast and security. It adds a four-byte 802.1Q frame header after the source address of Ethernet. VLAN ID divides the user into less work group and each work group is just a virtual LAN. The virtual LAN can limit the broadcast range and form virtual work group to manage network dynamically.

Before VLAN appeared, the administrator improved Ethernet performance or limit the inter-access right of the computers over the Internet network through dividing network segments. At that time, every network segment must own one set of network hardware independently and the same set of network device cannot be shared between various network segments. When a computer transfers from one network segment to another network segment, the administrator should perform more alteration relatively to the network. After VLAN appears, the administrator divides network into segments through VLAN. Every network segment can share one set of network device, which saves the overhead of network hardware. At the same time, the work done in computer transfer is reduced greatly and the internetworking cost is also reduced.

This chapter provides VLAN management of core routers and S8016.

7.1 VLAN Management

7.1.1 Querying VLAN Information

Double-click [VLAN Management/VLAN Management] on function tree to open the [VLAN Management] dialog box, shown as Figure 7-1.

Figure 7-1 VLAN Management


7-2

The queried information includes all VLAN list of device, VLAN ID, VLAN type, contained access VLAN information, information of aggregate VLAN where the VLAN belongs to, whether to broadcast unknown packet, whether there is layer-3 interface, whether to permit MAC to be learned. The port list contained in this VLAN can be queried by clicking a VLAN in the list.

7.1.2 Creating Common VLAN

In the [VLAN Management] dialog box, click <Add…> and the [VLAN Creation] dialog box pops up, shown as Figure 7-2.

Figure 7-2 VLAN Creation

Input related parameters and select related ports in the dialog box, click <OK>, one new VLAN can be created. The parameters and meanings involved in VLAN creation go as follows:

VLAN ID: an integer identifying VLAN uniquely, ranging from 2 to 4094. McastUnknown: select whether to broadcast unknown packet. MAC Learn: select whether to permit MAC to be learned.


7-3

The VLAN's Ports: when VLAN is created, the user can specify port list contained in VLAN. The method goes as follows: select ports to be contained in the VLAN from the [Available Ports] list box at the left, and then click <>>>.

Caution:

The ports listed in selectable port list do not include aggregation-branch port, observing port and port belonging to other VLAN.

The selectable port list supports Shift and Ctrl multi-option operation.

7.1.3 Deleting VLAN

Select one or more VLANs to be deleted from VLAN list in the [VLAN Management] dialog box, and click <Delete> to delete the corresponding VLANs. After a VLAN is deleted, the port contained in it will change to a default VLAN automatically, i.e., VLAN 1. If the deleted VLAN is an aggregate VLAN, the access VLAN contained in it will automatically become a common VLAN.

Caution:

VLAN1 cannot be deleted. The VLAN configured with layer-3 interface cannot be deleted.

7.1.4 Configuring Common VLAN

The operation of configuring VLAN is similar to that of creating VLAN. Refer to section 7.1.2 “Creating Common VLAN”.

7.1.5 Configuring Aggregate VLAN

Select one line in VLAN list in the [VLAN Management] dialog box and then click <Config…>. If the selected VLAN is aggregate VLAN, the [Aggregate VLAN Configuration] dialog box pops up. Set VLAN parameter and access VLAN contained in this aggregate VLAN in the dialog box, and then click <OK>, the configuration can be just completed.


7-4

Caution:

The existing aggregate VLAN, existing access VLAN and VLAN configured with layer-3 interface or VLAN1 cannot be set as the access VLAN of other aggregate VLAN.

7.1.6 Setting Common VLAN as Aggregate VLAN

Select one VLAN from the VLAN list in the [VLAN Management] dialog box, click <Change Type> and then you can set common VLAN as aggregate VLAN. If the selected VLAN contains physical port, the VLAN cannot be set as aggregate VLAN.

Note:

"Change Type" function can both set common VLAN as aggregate VLAN and set aggregate VLAN as common VLAN, which depends on the type of current selected VLAN.

7.2 VLAN Interface Management

To implement network layer function on VLAN interface, the user can specify interface for VLAN, i.e., configure IP address and mask for VLAN.

7.2.1 Querying VLAN Interface Information

Double-click [VLAN Management/VLAN Interface Management] on function tree to open the [VLAN Interface Management] dialog box, as shown in Figure 7-3.


7-5

Figure 7-3 VLAN Interface Management

The following information can be queried: all VLAN interfaces on this device, including VLAN ID, layer-3 interface IP address, mask of VLAN interface, Route Property, Administration Status, Operation Status, etc.

Caution:

Figure 7-3 shows the case of single-port VLAN. When the device supports multi-port VLAN, there is not routing property bar in the dialog box. The single-port VLAN refers to that the routing attribute of a VLAN layer-3 interface must be configured as routing when the VLAN layer-3 interface is connected to the layer-3 interface of other router. Here, the VLAN can only contain one port. In the figure, the routing attribute of VLANs whose ID are 2, 4 and 80 are routing and they can only contains one port. At present, core router only supports single-port VLAN.

7.2.2 Creating VLAN Interface

Click <Add…> in the [VLAN Interface Management] and [Layer-3 VLAN Interface Creation] dialog box pop up, shown as Figure 7-4.


7-6

Figure 7-4 Layer-3 VLAN Interface Creation

In this dialog box, select VLAN ID, input IP address and Mask, click <OK>, one new VLAN interface can be created.

7.2.3 Deleting VLAN Interface

Select one or more VLAN to be deleted from VLAN list in the [VLAN Interface Management] dialog box, and then click <Delete>, the corresponding VLAN interface will be deleted.

Caution:

If the layer-3 interface used currently is deleted, the management device will not be connected.

7.2.4 Configuring VLAN Interface

Select a line of data in the [VLAN Interface Management] dialog box, click <Config…> and the [Layer-3 VLAN Interface Configuration] dialog box pops up, shown as Figure 7-5,Figure 7-6,Figure 7-7,Figure 7-8.


7-7

Figure 7-5 Layer-3 VLAN Interface Configuration

Caution:

Figure 7-5 shows the case of single-port VLAN. When the device supports multi-port VLAN, there is not routing property in the dialog box.

Select or modify related attribute in this dialog box. Click <OK> to complete configuration operation.

7.3 VLAN Trunk Management

After a port is set as Trunk port and the VLAN that is allowed to pass is specified for this port, this port will permit the packets of one or more different VLANs to pass so as to implement the interconnection between the VLAN on local device and the VLAN on opposite device.

7.3.1 Querying Trunk Port Information

Double-click [VLAN Management/VLAN Trunk Management] on function tree to open the [VLAN Trunk Management] dialog box, shown as Figure 7-6.


7-8

Figure 7-6 VLAN Trunk Management

The following information is available: VLAN Trunk port description, VLAN Passed and VLAN Allowed to Pass on the port.

VLAN Allowed to Pass refers to the VLAN IDs, configured through the NMS that can pass the device port. They may be the existent VLAN IDs (those actually pass through the device port) configured on the device or new ones.

7.3.2 Creating Trunk Port

Click <Add…> in the [VLAN Trunk Management] and [VLAN Trunk Creation] dialog box pop up, shows as Figure 7-7.

Figure 7-7 VLAN Trunk Creation


7-9

The list at the left of the dialog box lists all device interfaces that can act as Trunk port but this list does not include aggregation branch port and observing port.

Select one or more ports from optional ports and click <>>> to add the port into the list of port to be set as Trunk. Just click <OK>. If the creation does not succeed, the "Prompt" on main interface will prompt the failure reason to the user.

7.3.3 Deleting Trunk Port

Select one or more lines from port list in the [VLAN Trunk Management] dialog box. Click <Delete> and the selected Trunk port can be deleted.

7.3.4 Configuring Trunk Port

Select one Trunk port in the [VLAN Trunk Management] dialog box, click <Config…> and the [VLAN Trunk Port Configuration] dialog box pops up, shows as Figure 7-8.

Figure 7-8 VLAN Trunk Port Configuration

In this dialog box, the input example is given and the user can set VLAN for this Trunk port according to the example.

After input, click <OK>, <Add> or <Delete> to execute corresponding operation. Click <OK>, the VLAN list input by the user this time will completely overwrite the VLAN list that is allowed to pass formerly on this Trunk port. Click <Add>, the VLAN input by the user this time will add to the list of former VLAN that is allowed to pass. Click <Delete>, the VLAN input by the user this time will be deleted from the list of VLAN that is allowed to pass formerly. On matter which case is selected from <OK>, <Add> or <Delete>, the system will open the confirm dialog box to ask the user to confirm this if the user inputs more VLAN than 1000 at one time.

User Manual Volume I Quidview Device Manager Chapter 8 RSTP Management

8-1

Chapter 8 RSTP Management

Spanning tree protocol (STP) is applied to loopback networks. It blocks some redundant paths through some specific algorithms and tailors the loopback network into the tree-shape loopless network, consequently avoiding the packet flooding and infinite cycling.

The basic principle of STP is that it determines the topology structure of the network by transmitting the specific protocol packet between switches (IEEE 802.1D protocol calls such packet as “Configuration Message”). The configuration message contains sufficient information to guarantee the switch to complete the calculation of the spanning tree.

Rapid Spanning Tree Protocol implemented by core router and S8016 device is the optimized version of STP. The “Rapidness” is incarnated in the shortened delay in a certain condition when entering the Forwarding state from the root port and the specified port, and it also shortens the required time to stabilize of the network topology. The device applying the RSTP is also compatible with the device applying STP. STP and RSTP protocol packets can both be identified and applied in the STP calculation.

RSTP management functions implemented by Quidview NMS mainly include device RSTP configuration and port RSTP management. The following details the two sections by taking S8016 as an example.

8.1 Device RSTP Configuration

The function can be used to browse and partially configure RSTP and STP information of S8016 device.

Double-click [RSTP Management/Device RSTP Configuration] in the function tree of the function pane as shown in Figure 8-1.


8-2

Figure 8-1 Device RSTP Configuration dialog box

The meaning of each parameter is shown below:

RSTP Status: enable and disable RSTP. Some network resources will be occupied after RSTP is enabled on the device.

RSTP Operation Mode: Two kinds of operation modes are available for RSTP: RSTP Mode and STP Mode. RSTP can operate in STP Mode, and it is interconnected to STP. If there is the network bridge operating STP in the switching network, the current RSTP can be configured to operate in STP Mode.

RSTP Diameter: Network diameter refers to the maximum number of switches between any two terminal devices in the switching network. The parameter can be configured as required, ranging 1 to 7 while 7 by default.

RSTP Priority: the size of the network bridge determines whether the network bridge can be selected as the root of the whole spanning tree. Specifying smaller priority sets a certain network bridge as the root of the spanning tree, ranging 0 to 61440.

RSTP ForwardDelay: The ForwardDelay feature of the network bridge refers to the delay entering the port from Discarding state to Forwarding state, and its parameter is related to the network diameter of the switching network. If FowardDelay is configured too short, the temporary redundant path may be redistributed; if ForwardDelay is configured too long, the network topology cannot restore the connection in a long time after it is changed. The user is recommended to use the default value for the configuration, 15 seconds by default.

RSTP Bridge Hello Time: Bridge HelloTime refers to the duration for RSTP to periodically send the configuration message. Proper Hello Time can not only guarantee


8-3

the bridge to discover the link fault in the network in time, but also occupy less network resources. Longer HelloTime may cause the bridge to wrongly assume the protocol packet loss to be link fault and recalculate the tree, while shorter HelloTime may cause the bridge to repeatedly send the configuration message-resulting in added network load and CPU load. The user is recommended to use the default value to configure the HelloTime of the bridge, 2 seconds by default.

RSTP Bridge MaxAge: Maxage feature of the bridge refers to the maximum lifetime of the configuration message. The parameter is used to judge whether the configuration message gets expired and discarded. The user can configure it according to the actual situation. If it is configured too short, the calculation of the spanning tree will be repeated. Network congestion may be wrongly regarded as the link fault. If the parameter is configured too long, it cannot timely discover the link fault and lower the network auto-sensing. The user is recommended to use the default value to configure the MaxAge of the bridge, 20 seconds by default.

RSTP RootBridgeAddress: it cannot be configured according to MAC address of the root bridge.

The user can modify some parameters based on his requirement. Then, click <Configure>. If <Refresh> is clicked, the system will re-read RSTP information from the device and update the display in the dialog box.

8.2 Port RSTP Management

The function can be used to browse and partially configure RSTP and STP information of S8016 device port.

Double-click [RSTP Management/Port RSTP Management] in the function tree of the function pane, and enable the [Port RSTP Management] dialog box as shown in Figure 8-2.


8-4

Figure 8-2 Port RSTP Management dialog box

To configure a certain port, select one port in the port list and click <Config…>. The [Port RSTP Configuration] dialog box pops up as shown in Figure 8-3.


8-5

Figure 8-3 Port RSTP Configuration dialog box

Each parameter is described as follows:

Port Description: port name.

Port Priority: Setting Ethernet port priority specifies the specific Ethernet port in the spanning tree. Generally, the smaller the configured value is, the higher the port priority is, and the more possible is the Ethernet port in the spanning tree. If all Ethernet ports of the bridge adopt the same priority parameter, the priority level of the Ethernet port is determined by the index of the Ethernet port. It ranges 0 to 255, and by default it is 128.

Port RSTP Status: Port RSTP status, including disabled, blocking, listening, learning, forwarding, broken, discarding.

Port RSTP Spanning Tree: Whether to enable the port RSTP.

Port PathCost: The path cost of Ethernet port is related to the link rate of the port. The higher the link rate is, the smaller the parameter is configured. When the parameter is configured to the default value, RSTP can automatically detect the link rate of the current Ethernet port and converge it into the corresponding path cost. The user is recommended to use the default value so that RSTP can calculate the path cost of the current Ethernet port by itself.

Port Designated Root: Root bridge ID, the first 16 bits are the priority of the root, while the last 48 bits are MAC address of the root bridge.

Port Designated Cost: path designated cost to root bridge.


8-6

Port Trans Limit: Ethernet port Trans limit refers to the maximum number of configuration messages in HelloTime interval. The parameter is related to the physical state and network structure of the port. If the parameter is configured too large, it occupies more network resources. The user is recommended to adopt the default value to configure the parameter. By default, it is 3.

Port EdgePort: Ethernet port EdgePort attribute shows whether the port is directly or indirectly connected to other bridge. If the port is not connected to any Ethernet port of the bridge, the port shall be configured as edge port. In this way, the network bridge operates in RSTP mode, and the port can directly switch to Forwarding state and reduces the unnecessary migrating time. If a certain port is configured as the edge port and it is connected to other port of the network bridge, RSTP can automatically detect and reset it as the non-edge port.

Port Point to Point: If the network bridge operates in RSTP mode, the two ports connected by point-to-point link can switch to Forwarding state by transmitting the synchronous packet, which reduces the unnecessary forwarding delay. If the parameter is configured to auto, RSTP can automatically detect whether Ethernet port is connected to point-to-point link. The user can manually configure whether Ethernet port is connected to point-to-point link, but it is recommended that the user set it to auto mode.

Port mCheck: Port mCheck attribute is used to detect whether the port in STP compatible mode can be switched to RSTP mode. Setting mCheck checks whether there are other bridges running STP in the network segment connected to the current Ethernet port. If so, RSTP will switch the protocol operation mode to STP compatible mode. In the case of relatively stable network, RSTP will also operate in STP compatible mode although the bridge operating STP in the network segment is disconnected. Setting mCheck variable may force it to switch to RSTP mode. When the command is enabled on the port, if the port still operates in STP compatible mode, it means that STP bridge exist in the network segment connected to the port. Otherwise, the port returns to RSTP mode, which means that no STP bridge exists on the network segment connected to the port. It must be noted that the configuration mode of mCheck variable is somehow special; when mCheck variable is set to True, the command is validated in the process of the configuration, but the variable resumes to False after configuration; when mCheck variable is set to False, it is not validated. Besides, only when mCheck command operates in RSTP mode, detecting STP bridge function can be implemented.

The user can modify some parameters based on his requirement. Then, click <OK> for the configuration. If <Refresh> is clicked, the system will re-read RSTP information from the device and update the display in the dialog box.

User Manual Volume I Quidview Device Manager Chapter 9 Routing Protocol Management

9-1

Chapter 9 Routing Protocol Management

9.1 Overview

Routing information protocol (RIP), open shortest path first (OSPF) and border gateway protocol (BGP) are three kinds of dynamic routing protocol widely applied to routers. The user can learn the configuration condition of routing protocol through browsing and viewing routing protocol information.

The routing protocol management mainly includes RIP information browsing, OSPF information browsing and BGP information browsing and route protocol enable configuration.

Note:

S8016 does not support OSPF/BGP information browsing, but provide routing table browsing function.

Browsing of RIP information

Including interface configuration information, interface statistic information, and peer router information.

Browsing of OSPF information

Including OSPF attribute, OSPF area information, connection state database information, OSPF interface information, peer information, and virtual connection information.

Browsing of BGP information

Including BGP attribute, peer information, and BGP4 path information.

Routing table browsing

Including the browsing of static routing table and dynamic routing table. Such function is provided by S8016 device.

Routing protocol management can be done through the following two methods:

1) Function tree

The function menu of routing protocol management is shown in following figure:


9-2

Figure 9-1 Function tree of routing protocol management (not including S8016 device)

Figure 9-2 Function tree of routing protocol management (S8016 device)

Double-click related nodes on function tree to browse related routing protocol.

2) Device menu

Right click on device panel and the device menu shown in Figure 9-3 and Figure 9-4 will pop up. So the user can browse related routing protocol.


9-3

Figure 9-3 Device menu (not including S8016 device)

Figure 9-4 Device menu (S8016)

The functions of two methods are same. The function tree is described as an example in this chapter.

9.2 Browsing of RIP Information

RIP is a relatively simple dynamic routing protocol but is widely used in actual applications. RIP is based on Distance-Vector algorithm and it switches routing information through user datagram protocol (UDP) packet. It sends out update packet once every 30 seconds. If the routing update packets are not received from the opposite for 180 seconds, all the routing information from this opposite will be identified as unreachable. If update packets are not received yet for 120 seconds after this, the above routing will be deleted from the routing table.

If RIP is configured on the device, select [Routing Protocol Management/RIP Browsing] on the function tree, and the right display area will show the RIP related information, including interface configuration information, interface statistic information, peer router information, etc.


9-4

9.2.1 Interface Configuration

Click the [Interface Config] tab in the [RIP Browsing] window and the content in interface configuration table of RIP can be browsed, shown as the following figure:

Figure 9-5 RIP Browsing – Interface Configuration

The description of various parameters in interface configuration information browsing is shown in following table:

Table 9-1 Description of RIP interface configuration information

Content Description

Interface Address Interface address of specified sub-network

Authentication Type

Interface authentication type: noAuthentication: none authentication simplePassword: plain text authentication is needed. md5: MD5 authentication is needed

Key Authentication password when the authentication type is simplePassword or md5

Version of Sent Packets

RIP sends the packets of the following kinds of versions: doNotSend: forbid the interface to send RIP packet outside. ripVersion1: default value. The interface RIP version is RIP-1 and only RIP-1 broadcast packet is sent. rip1Compatible: the interface runs in RIP-2 broadcast mode and only RIP-1 and RIP-2 broadcast packets are sent. ripVersion2: specify the interface to run in RIP-2 multicast mode and only RIP-2 multicast packet is sent.


9-5

Content Description

Version of Received Packets

Version of received RIP packet: rip1: default value. The interface RIP version is RIP-1 and only RIP-1 and RIP-2 broadcast packets are received. RIP-2 multicast packet is not received. rip2: specify interface to run in RIP-2 multicast mode and only RIP-2 multicast packet is received. RIP-1 and RIP-2 broadcast packets are not received. rip1OrRip2: the interface runs in RIP-2 broadcast mode and only RIP-1 and RIP-2 broadcast packets are received. RIP-2 multicast packet is not received. doNotReceive: any RIP packet is not received.

Default Metric Default metric is used in route import. If no Metric is specified in route import, the value of default-metric is used by default.

9.2.2 Interface Statistics

Click the [Interface Statistics] tab in the [RIP Browsing] window and the content in interface statistic table of RIP can be browsed, shown as the following figure:

Figure 9-6 RIP Browsing- Interface Statistics

The description of various parameters in interface statistic information browsing is shown in following table:

Table 9-2 Parameter description of RIP statistic information table

Name Description

Interface Address Interface address of specified sub-network

Received Error Packets Received bad response packets on this interface

Discarded Routes Discarded routes in received valid RIP packets


9-6

Name Description

Triggered RIP Updates Triggered RIP update packets sent out on this interface, not including the update packets sent at interval

9.2.3 Peer Information

Click the [Peer Information] tab in the [RIP Browsing] window, the content in peer router information table of RIP can be browsed, shown as the following figure:

Figure 9-7 RIP browsing-Peer Information

The description of various parameters in peer router information browsing is shown in following table:

Table 9-3 Parameter description of RIP peer router interface table

Name Description

Peer Address Interface address of peer router (Peer)

Last Update The system operation time when the update packet from peer router is received last time.

RIP Version Version of RIP packet received last time

Received Invalid Response Packets Received invalid response packets from the peer router

Discarded Routes Discarded routes for wrong route information format in the received valid packets from peer router

9.3 Browsing of OSPF Information

OSPF is an interior GW protocol developed by IETF on the basis of link state. At present, version 2 (RFC2328) is applied.


9-7

In OSPF protocol, the whole network can be regarded as multiple autonomous systems (AS). The information synchronization from route to AS is dynamically discovered and broadcasted through collecting and transmitting AS link state. Each AS can be divided into different areas. If a port of router is distributed to multiple areas, the router is just called area border router (ABR). It lies in the area border and connects with multiple areas. All ABRs and routers between ABRs constitute backbone area that is identified with 0.0.0.0. Because all areas must keep logical connection with backbone area and virtual concept is introduced, the areas divided physically can keep logical connection. The router connecting with AS is called autonomous system boundary router (ASBR).

If OSPF protocol is configured on device, select [Routing Protocol Management/OSPF Browsing] on the function tree, the right display area will display OSPF protocol related information, including OSPF Attribute, OSPF Area Information, LSDB Information, OSPF Interface, Peer Information, Virtual Link Information, etc.

9.3.1 OSPF Attribute

Click the [OSPF Attribute] tab in the [OSPF Browsing] window, and the OSPF protocol attribute can be browsed, shown as following figure:

Figure 9-8 OSPF Browsing-OSPF Attribute

Various parameters in OSPF protocol attribute information browsing are described in following table:


9-8

Table 9-4 OSPF protocol attribute

Name Description

Router ID Unique ID of router in AS

OSPF Status OSPF protocol management status

OSPF Version Version of current OSPF protocol

Is Area Border Router Is this router area border router

Is AS Border Router Is this router AS border router

ASE-LSA Count Amount of ASE-LSA in LSDB

Sum of The ASE-LSA Checksums Sum of ASE-LSA checksums in LSDB

TOS Support Does the router support TOS route

New LSA Originated Amount of new LSA originated by this router

New LSA Received Amount of received new LSA

Note:

LSDB: Link State Database ASE-LSA: AS-external-LSA, type 5 LSA, the routing that is generated by ASBR and reaches to other AS. It will be broadcasted to the whole AS (not including Stub area).

9.3.2 OSPF Area Information

Click the [OSPF Area Information] tab in the [OSPF Browsing] window, the OSPF area information can be browsed. The information includes area information and Stub area information.

Area information

Click the [Area Information] tab, and the content of area information can be displayed, shown as following figure:


9-9

Figure 9-9 OSPF Browsing- Area Information

Various parameters in area information browsing are described in following table:

Table 9-5 OSPF Browsing-Area Information

Name Description

Area 32-byte integer identifying area uniquely

Auth Type

Specify authentication type of area: None(0): none authentication Simple(1): plain text authentication MD5(2): MD5 authentication

Import As Extern LSA

Does the area support the import of connection status broadcast outside of AS

Spf calculation Times that the area link status is used to calculate routing table in area

ABR Number of reachable ABR in this area

ASBR Number of reachable ASBR in this area

LSA Number of reachable LSA in link status database of this area

Sum of LSA Checksum Sum of LSA checksum in link status database in this area

Stub Area Information

Click the [Stub Area Information] tab, and the content of Stub area information will be displayed, shown as following figure:


9-10

Figure 9-10 OSPF Browsing-Stub Area Information

Various parameters in Stub area information browsing are described in following table:

Table 9-6 OSPF Browsing-Stub Area Information

Name Description

Area Area number of Stub area

TOS Type Which TOS does the next metric belong to

Default Route Metric Default metric of imported Stub area

Status Status of this line

9.3.3 LSDB Information

Click the [LSDB Information] tab in the [OSPF Browsing] window, and the information of OSPF LSDB information can be browsed, shown as following figure:

Figure 9-11 OSPF Browsing- LSDB Information


9-11

Various parameters in OSPF LSDB information are described in following table:

Table 9-7 OSPF Browsing-LSDB Information

Name Description

Area Number of Area to which LSA belongs

Type LSA type: routerLink, networkLink, summaryLink, asSummaryLink, asExternalLink.

LS ID LS_ID of LSA

Originating Router ID of router originating LSA

Serial Number LSA serial number

Age(S) Time generating LSA

Checksum Checksum of LSA

9.3.4 OSPF Interface

Click the [OSPF Interface] tab in the [OSPF Browsing] window, and the content of OSPF protocol interface information can be browsed. The information includes Interface Information and Interface TOS Metric.

Interface Information

Click the [Interface Information] tab, and the content of interface information can be displayed, shown as the following figure:

Figure 9-12 OSPF Browsing-Interface Information


9-12

Various parameters of interface information browsing are described in following table:

Table 9-8 OSPF Browsing-Interface Information

Name Description

Interface Address IP address of OSPF interface

Area Area where the interface lies

Type

Interface network type: broadcast: when link layer protocol is Ethernet, FDDI, OSPF regard the network type as Broadcast by default. nbma: when link layer protocol is ATM, frame-relay, HDLC or X.25, OSPF regards the network type as NBMA (Non Broadcast MultiAccess) by default. pointToPoint: when link layer protocol is PPP, LAPB or POS, OSPF regards the network type as Point-to-Point by default. pointToMultiPoint: no link layer protocol will be regarded as Point-to-Multipoint by default. It is formed through manual modifying NBMA if NBMA network is not connected completely.

Available Status Indicate whether the interface is available

Priority Priority of router

Transit Delay Link status transit delay

Retrans Interval Link status retransmit interval

Hello Interval Sending interval of interface hello packet

Dead Time Interval Dead time interval of interface peer

Poll Interval Polling interval of dead peer

Status Interface status: down, loopback, waiting, pointToPoint, designatedRouter, backupDesignatedRouter, otherDesignatedRouter.

DR IP address of specified router

BDR IP address of backup specified router

Events Times of interface status change or error occurrence

Authentication Key Plain text authentication key of interface

Interface TOS Metric

Click the [Interface TOS Metric] tab, and the related content of interface TOS metric can be displayed, shown as following figure:


9-13

Figure 9-13 OSPF Browsing-Interface TOS Metric

Various parameters in interface TOS metric information browsing are described in following table:

Table 9-9 OSPF Browsing-Interface TOS Metric

Name Description

Interface IP address of OSPF interface (interface index when OSPF interface has no IP address)

Interface TOS Type TOS type of OSPF interface

Route Metric Route metric value of OSPF interface


Click the [Peer Information] tab in the [OSPF Browsing] window, and the content of OSPF peer information can be browsed, shown as following figure:


9-14

Figure 9-14 OSPF Browsing-Peer Information

Various parameters in peer information browsing are described in following table:

Table 9-10 OSPF Browsing-Peer Information

Name Description

Peer Address IP address of peer (index of interface without IP address)

Router ID Router ID of peer

Priority Priority of peer

Status Status of relationship with peer: down, attempt, init, twoWay, exchangeStart, exchange, loading, full

Events Times of status change of relationship with peer or error occurrence

Length of The Retransmission Queue Length of current retransmission queue

9.3.6 Virtual Link Information

Click the [Virtual Link Information] tab in the [OSPF Browsing] window and the content of OSPF virtual link information can be browsed. The information includes Virtual Link Interface and Virtual Link Peer.

Virtual Link Interface

Click the [Virtual Link Interface] tab, and the information of virtual link interface can be displayed, shown as following figure:


9-15

Figure 9-15 OSPF Browsing- Virtual Link Interface

Various parameters in virtual link interface browsing are described in following table:

Table 9-11 OSPF Browsing-Virtual Link Interface

Name Description

Transit Area Transit area of virtual link

Peer Router ID Router ID of virtual link peer

Transit Delay Link status transit delay

Retrans Interval Link status retransmit interval

Hello Interval Sending interval of interface hello packet

Dead Time Interval Dead time interval of interface peer

Status Interface status of virtual link

Events Times of interface status change of virtual link or error occurrence

Authentication Key Plain text authentication key of virtual link interface

Virtual Link Peer

Click the [Virtual Link Peer] tab, and the information of virtual link peer can be displayed, shown as following figure:


9-16

Figure 9-16 OSPF Browsing-Virtual Link Peer

Various parameters in virtual link peer browsing are described in following table:

Table 9-12 OSPF Browsing-Virtual Link Peer

Name Description

Transit Area Transit area number

Peer Router ID ID of virtual link peer router

Peer Address IP address of virtual link peer

Status Status of virtual link peer: Down, Attempt, Init, TwoWay, ExchangeStart, Exchange, Loading, full

Events Times of status change of relationship with peer or error occurrence

Authentication Key Plain text authentication key

9.4 Browsing of BGP Information

For the convenience of management, the Internet is divided into some autonomous systems (AS). One AS refers to one group of routers running under the management of the same technical management department. These routers run the same routing protocols generally and use the same routing strategies. Each AS has one unique ID represented with integer (1 to 65535). The ID of AS is distributed by InterNIC uniformly.

The routing protocols running in the same AS are called interior gateway protocol (IGP). And the protocols running between AS are called exterior gateway protocol (EGP).


9-17

Border gateway protocol (BGP) is a kind of EGP. The basic function of BGP is to switch routing information without loop. The information switched by BGP carry abundant attribute that can be used to construct topology of AS and execute routing strategy based on AS level. T path reachable information with sequence attribute of AS number can cancel routing loop. BGP is often used between ISP.

BGP was started to use from 1989. Its three earliest released versions are RFC1105 (BGP-1), RFC1163 (BGP-2) and RFC1267 (BGP-3) respectively. At present, RFC1771 (BGP-4) is applied. It is applicable to distributed structure and supports Classless InterDomain Routing (CIDR). BGP-4 has been the actual Internet EGP standard.

If BDP is configured on the device, select [Routing Protocol Management/BGP Browsing] on the function tree, and the right display area will display BGP related information.

9.4.1 BGP Attribute

Click the [BGP Attribute] tab in the [BGP Browsing] window, and the basic attribute of BGP can be browsed, shown as following figure:

Figure 9-17 BGP Browsing-BGP Attribute

Various parameters in information browsing are described in following table:

Table 9-13 BGP Browsing-BGP Attribute

Name Description

BGP Local ID BGP ID of local system

Local AS Number Local AS number


9-18


Click the [Peer Information] tab in the [BGP Browsing] window, and the BGP peer information can be browsed. The information includes Basic Information, Statistic Information and Time Attribute.

Basic Information

Click the [Basic Information] tab, and the basic information of BGP peer can be displayed, shown as following figure:

Figure 9-18 BGP Browsing-Peer Information

Various parameters in peer information browsing are described in following table:

Table 9-14 BGP Browsing-Peer Information

Name Description

Peer ID BGP peer ID

Status Connection status of BGP peer: idle, connect, active, opensent, openconfirm, established.

Negotiated Version BGP negotiation version run between two peers

Local IP Address Local IP address of BGP connection

Local Port Local port of TCP connection between BGP peers

Remote IP Address Remote IP address of BGP peer

Remote Port Remote port of TCP connection between BGP peer

Remote AS Remote AS number

Statistic Information

Click the [Statistic Information] tab, and the statistic information of BGP peer can be displayed, shown as following figure:


9-19

Figure 9-19 BGP Browsing-Peer Statistic Information

Various parameters in peer statistic information browsing are described in following table:

Table 9-15 BGP Browsing-Peer Statistic Information

Name Description

Peer IP Address BGP peer IP address

Updates Received Received BGP update messages in this connection

Updates Transmitted Transmitted BGP update packets in this connection

Total Messages Received Total messages received from remote peer in this connection

Total Messages Transmitted

Total messages transmitted to remote peer in this connection

Last Error Last error code and sub-code seen by peer in this connection

Fsm Established Transitions Times of BGP FSM transiting to Established status

Fsm Established Time(s) Duration when the peer is in Established status

Time Attribute

Click the [Time Attribute] tab, and the content of BGP time parameters can be displayed, shown as following figure:


9-20

Figure 9-20 BGP Browsing-Peer Time Attribute

Various parameters in peer time parameter browsing are described in following table:

Table 9-16 BGP Browsing-Peer Time Parameter

Name Description

Peer IP Address BGP peer IP address

Connection Retry Interval(S) Interval (s) of establishing connection timer

HoldTime(S) Same as the interval (s) of holding timer established by peer

KeepAlive(S) Same as the interval (s) of KeepAlive timer established by peer

HoldTime Configured(S) Holding timer interval (s) configured for BGP addresser and peer

KeepAlive Configured(S) KeepAlive timer interval (s) configured for BGP addresser and peer

Route Advertisement Interval(S) Interval of transmitting routing information

Update Elapsed Time(S) Interval from the last time of receiving update packet to now

9.4.3 BGP4 Path Information

Click the [BGP4 Path Information] tab in the [BGP Browsing] window, and the content of BGP4 path information can be browsed, shown as following figure:


9-21

Figure 9-21 BGP Browsing-BGP4 Path Information

Various parameters in BGP4 path information browsing are described in following table:

Table 9-17 BGP4 Path Information

Name Description

Peer IP Address Peer IP address

IP Address Prefix Len IP address prefix length of NLRI domain

IP Address Prefix IP address prefix of NLRI domain

Origin Path information origin: igp, egp, incomplete

AS Path Segment AS path segment sequence

Next Hop Address Next hop address of destination network

Multi Exit Metric The value is used to distinguish multiple exits of adjacent AS

Priority Priority of origin BGP4 addresser advertisement route

Aggregate Route Selection

Local system selects non-specific route or the specific route: LessSpecificRouteNotSelected: non-specific route lessSpecificRouteSelected: specific route

Aggregator AS AS number of BGP4 addresser executing route aggregation

Aggregator IP Address IP address of BGP4 addresser executing route aggregation

Local Priority Calculated

Priority calculated by BGP4 addresser receiving route for advertisement route


9-22

Name Description

IsBest Is the local route selected as best route?

Unknown Attributes One or more attributes unknown for BGP4 addresser. If it is 0, it indicates that there is no this attribute.

9.5 Routing Protocol Enable Configuration

This function is used to enable or disable some protocols. Select [Routing Protocol Management/Route Protocol Enable Configuration] on the function tree to open the [Route Protocol Enable Configuration] dialog box, as shown in Figure 9-22.

Figure 9-22 Route Protocol Enable Configuration

Click the enable or disable option buttons corresponding to various protocols and click <Config> to finish the configuration. If you enable the BGP, you must further specify the local AS number in the range of 1 to 65535.

Note:

If you fail to enable the routing protocol, the Telnet parameters of the device may have not been configured properly.

9.6 Browsing of Routing Table

S8016 device provides browsing for device routing table including Static Routing and Dynamic Routing.


9-23

The key function of device forwarding packet is to route through routing table. The routing table demonstrates which physical port of the router is used to send the packet to a sub-network or a host. And then, the packet can be sent to next router of this path, or be sent to the directly connected destination host in network not passing through other routers.

The user can both manually configure static routing to a specific destination and configure dynamic routing protocol to interact with other routers in network and to find routing through routing calculation.

The routing table includes the following key items: destination address, network mask, output interface, next hop IP address, priority of local routing joining in IP route table.

Double-click [Route Protocol Management/Route Table Browsing] on S8016 function tree and the right information display area will display the content of device routing table, including static routing table and dynamic routing table.

9.6.1 Static Routing Information

The static routing table reflects the information not converted when static routing is configured, i.e., only when the egress is configured, can the valid interface index be seen in device MIB. If the next hop is configured, the egress index cannot be seen in MIB yet even this route takes effect, which is different from dynamic routing.

Click the [Static Routing] tab in the [Route Table Browsing] dialog box, and the content of static routing can be browsed, shown in following figure:

Figure 9-23 Routing Table Browsing-Static Routing

The static routing includes the following contents:


9-24

Table 9-18 Static Routing table

Content Description

Serial Index number of this route

Destination IP Destination address or destination network identifying IP packet

Destination Mask

Identifying, together with destination address, the address of network segment where the destination host or router is located. Perform “AND” operation to destination address and network mask to obtain the address of network segment where the destination host or router is located. For example, the address of network segment where the host or router whose destination address is 129.102.8.10 and mask is 255.255.0.0 is 129.102.0.0.

Next Hop Next router that IP packet passes through

Interface Description Which interface of this router is the IP packet forwarded from?

Priority Priority of this static routing. The priority of each static routing can be different, ranging from 0 to 255. And the default priority of static routing is 60.

Tag

There are following route tags: reject: destination unreachable route. When the static routing to a destination has "reject" attribute, any IP packet to this destination will be discarded and the source host is notified that the destination is unreachable. blackhole: route whose destination is blackhole. When the static routing to a destination has "blackhole" attribute, any IP packet to this destination will be discarded and the source host is not notified. noflag: reachable route. The normal routes are such routes, i.e., IP packet is sent to the next hop according to the route identified by destination, which is the common use of static routing.

9.6.2 Dynamic Routing Information

The dynamic routing table reflects the routes that are valid and can be forwarded. The information, such as next hop and egress, are the converted information, which is different from the static routing table.

Click the [Dynamic Routing] tab in the [Route Table Browsing] dialog box, and the content of dynamic routing can be browsed, shown in following figure:


9-25

Figure 9-24 Routing Table Browsing-Dynamic Routing

The dynamic routing includes the following contents:

Table 9-19 Dynamic Routing Table

Content Description

Serial Index number of this route

Destination IP Destination address or destination network identifying IP packet

Destination Mask

Identifying, together with destination address, the address of network segment where the destination host or router is located. Perform “AND” operation to destination address and network mask to obtain the address of network segment where the destination host or router is located. For example, the address of network segment where the host or router whose destination address is 129.102.8.10 and mask is 255.255.0.0 is 129.102.0.0.

Next Hop Next router that IP packet passes through

Interface Description Which interface of this router is the IP packet forwarded from?

Highest Priority

The highest priority indicates that, actually, a dynamic route may be a result after the routes learned by multiple different protocols are integrated. These protocols have different priority and the highest one of them is the highest priority.

Protocol

Indicate which protocol generates this route: RIP, ISIS, IGRP, OSPF, BGP and DIRECT (direct route),--other cases (static route or other routes learned by other routing protocol)

Metric Metric generated by various protocols. Different protocols have different meanings. For example, the metric is just the hops for RIP and the metric is the cost sum of all paths for OSPF protocol.


9-26

Content Description

Tag

Protocol related data filled by various protocols. For example, the route tag field is the User ID when configuring command for configured static route and the route tag field is 0 for the command input from COM command line. The route tag field is 99 for the command restored from configuration file.

There may be some routes for different next hop. These different routes may be discovered by different route protocols or may be static route configured manually. The route with highest priority (the value is small) will be the best route currently. The user can configure many routes to the same destination but with different priority and the system selects a unique route to forward IP packet according to priority sequence.

User Manual Volume I Quidview Device Manager Chapter 10 S8016 NAT Management

10-1

Chapter 10 S8016 NAT Management

With the fast development of the Internet, data traffic on it doubles every 100 days and the number of online users soars. The theoretic space for IP addresses is 4.2 billion, considering wasting and spending however, the number of Internet users tends to break through this limit. The IPv6 is one of the ideal solutions to the address resource problem but, for some reasons, there is still a long way to go before it becomes developed and is put into real application. Currently, the NAT (Network Address Translation) technology is the unique applicable solution that can ease the network address resource problem.

NAT implements conversion between private and public network addresses. Private addresses are used on a private network, and a NAT device is used at the network egress to implement address conversion. Similar to a proxy server, only the NAT device needs a private address, which drives down the need for public addresses to a great extent.

According to the Internet Assigned Number Authority, the following network address segments are reserved for private addresses:

10.0.0.0 - 10.255.255.255

172.16.0.0 - 172.31.255.255

192.168.0.0 - 192.168.255.255

This is to say, these address segments will not be assigned on the Internet, but can be used on Intranets or MANs. Based on the estimate to the number of hosts in the predictable future, you can select a proper private network segment for an Intranet or a MAN. Different Intranets or MANs can share the same private address segment. If an enterprise selects a public network segment as its internal network address segment, routing table confusion may occur on the Internet.

Address conversion falls into two types, basic address conversion and network address-port conversion. In the former case, certain number of public addresses (may be less than the number of internal hosts) are allocated to a private network. The internal network adopts private addresses, and a NAT device is engaged in dynamically mapping an internal address to a valid public IP address when a host needs to communicate externally. The number of hosts that have external access depends on the number of public IP addresses. The later case implements mapping from the mix of a private address and port to the mix of a public address and port. As a TCP/UDP port is 16 bits long and occupies 64K coding space, the number of simultaneous ports used on a computer is usually small and hence the combination of a public address and port can be mapped to several combinations of private address and port. This expands the number of addresses.


10-2

NAT management function applies to S8016. S8016 routing switch supports network address-port conversion and mixed networking of public and private addresses (that is, you can configure either private addresses or public addresses on the private network). NAT processing provides conversion from any address to any address, that is, supports conversion from private addresses to public addresses, public addresses to public addresses and public addresses to private addresses.

Note:

Not any application can pass through a NAT device smoothly. For example, the FTP negotiates data channel IP address and port through the control channel, and attaches the IP address and port to packets for transmission over the channel. Therefore, it is necessary to track the packets through the control channel and convert the attached IP address and port. This function is implemented by the application layer gateway (ALG).

10.1 NAT Board Attribute and Monitor

10.1.1 Querying NAT Board Attribute

In the function pane, double-click [NAT/NAT Board Attribute And Monitor] node on the function tree to open the [NAT Board Attribute And Monitor] dialog box, as shown in Figure 10-1.

Figure 10-1 NAT Board Attribute And Monitor

Here you can query the attributes of all the NAT boards on the device. These attributes include status (usable/unusable), blacklist function (stopped/started), packet fragment function (enable/disable) and available ports. This interface provides attribute


10-3

configuration, flow monitor and dynamic information clearance operations for NAT boards.

10.1.2 Configuring NAT Board Attribute

In the [NAT Board Attribute And Monitor] dialog box, select a line and click <Config…> to open the [NAT Board Attribute] dialog box, as shown in Figure 10-2.

Figure 10-2 NAT Board Attribute

Here you can modify the attributes of a NAT board, such as enabling/disabling the blacklist and packet fragment functions on the board. After modification, click <OK> to finish the attribute configuration.

Blacklist: To prevent a NAT board from been affected by such attacks as DOS attack, the board supports to control the maximum number of user connections and the maximum speed at which links are established. You can enable/disable the blacklist function and control over connection speed and total connections on each NAT board. When the blacklist function is enabled, a user will be blacklisted and its connection be disabled or the packet sending speed of the newly established links be limited if the total connections or connection speed exceed the preset thresholds. When the threshold-crossing recovers, the user will be cleared from the blacklist for reestablishing connections.

If you enable the blacklist function on a NAT board without selecting any blacklist attribute, the device will not conduct any control but send an alarm when a user is appropriate to be blacklisted.


10-4

Note:

The initiator of DOS (Denial Of Service) attack aims to deny legal users from accessing certain resource, for instance, by sending a large amount of packets to use up network bandwidth resource.

10.1.3 NAT Board Flow Monitor

In the [NAT Board Attribute And Monitor] dialog box, select a line and click <Flow Monitor…> to open the [NAT Board Flow Monitor] dialog box. The monitor items are listed in Table 10-1.

Table 10-1 Traffic monitor items for NAT boards

Group name Monitor item Description

Packets Received Number of packets received on the NAT board in a polling interval

Packets Packets Discarded Number of packets discarded on the NAT board

in a polling interval

NAT Connection Sum Total connections involved in the NAT board

Tcp Connections Common TCP connections involved in the NAT board

Udp Connections Common UDP connections involved in the NAT board

Ftp ALG Connections

Common FTP ALG connections involved in the NAT board

Connects

Icmp ALG Connections

ICMP ALG connections involved in the NAT board

NAT Insert Fails Number of failed NAT table inserting operations on the NAT board in a polling interval

NAT Delete Fails Number of failed NAT table deletion operations on the NAT board in a polling interval

ACL Insert Fails Number of failed ACL table inserting operations on the NAT board in a polling interval

Operation Fails

ACL Delete Fails Number of failed ACL table deletion operations on the NAT board in a polling interval


10-5

Group name Monitor item Description

Speed NAT Connect Speed Every Second

Speed (per second) at which NAT connections are established on the NAT board

Port Number Port Used Number of ports in use on the NAT board

10.1.4 Clearing Dynamic Entries on a NAT Board

In the [NAT Board Attribute And Monitor] dialog box, select a line (with the status as USABLE) and click <Clear Dynamic Information> to clear the dynamically generated NAT entries on the selected NAT board.

10.2 Address Group and ACL Management

To use NAT on a board, you need to configure a public address group (a collection of public addresses for NAT processing) on the board and a NAT ACL (Access Control List) including the IP addresses for NAT processing.

After defining NAT address group and ACL, you can correlate them by configuring the bind between them. This correlation specifies to perform NAT processing on "the IP packets matching certain ACL" using "the addresses in the specified public address group". This correlation serves as the basis for address conversion. For example, when sending a packet externally from a private network, the system checks the packet against the NAT ACL. If match, the system will find the corresponding address group according to the correlation and then convert the source address to a certain one in the address group.

10.2.1 Querying NAT Address Group Information

In the function pane, double-click on [NAT/Address Group and ACL Management] node on the function tree to open the [Address Group and ACL Management] dialog box. Click the [Address Group] tab, and the interface as shown in Figure 10-3 appears:


10-6

Figure 10-3 NAT Address Group Management

Here you can view the information of all the NAT address groups on the device, including the NAT Board Number, Address Group Name, Active NAT Board Number, Start IP and End IP of each address group.

10.2.2 Creating a NAT Address Group

In above interface, click <Add…> to open the [NAT Address Group Creation] dialog box, as shown in Figure 10-4.

Figure 10-4 NAT Address Group Creation


10-7

Here select a NAT board, type the group name, start IP and end IP, and click <OK> to create an address group.

10.2.3 Deleting a NAT Address Group

In the NAT address group management interface, select one or more NAT address groups from the address group list and click <Delete> to delete them.

10.2.4 Querying NAT ACL Information

In the function pane, double-click on [NAT/Address Group and ACL Management] node on the function tree to open the [Address Group and ACL Management] dialog box. Click the [NAT ACL] tab, and the interface as shown in Figure 10-5 appears:

Figure 10-5 NAT ACL Management

Here you can view the information of all the NAT ACLs on the device, including ACL number, source IP and wildcard of source IP.

10.2.5 Creating a NAT ACL

In the NAT ACL management interface, click <Add…> to open the [NAT ACL Creation] dialog box, as shown in Figure 10-6.


10-8

Figure 10-6 NAT ACL Creation

Here select an ACL number, type the source IP and wildcard, and click <OK> to create a NAT ACL.

Caution:

Source IP address and wildcard are the reverses of the mask. For example, the mask is 255.255.255.0 and hence the wildcard should be 0.0.0.255.

10.2.6 Deleting a NAT ACL

In the NAT ACL management interface, select one or more ACLs from the ACL list and click <Delete> to delete them.

10.2.7 Querying NAT Bind Information

NAT bind refers to the correlation between NAT ACL and address group.

In the function pane, double-click on [NAT/Address Group and ACL Management] node on the function tree to open the [Address Group and ACL Management] dialog box. Click the [NAT Bind] tab, and the interface as shown in Figure 10-7 appears:


10-9

Figure 10-7 NAT bind management

Here you can view the information of all the NAT binds on the device, including the interface description, NAT ACL and NAT address group of each bind.

10.2.8 Creating a NAT Bind

In the NAT bind management interface, click <Add…> to open the [NAT Bind Creation] dialog box, as shown in Figure 10-8.

Figure 10-8 NAT Bind Creation

Here select a port description (since NAT bind is configured on a VLAN interface or a POS interface), an ACL number and an address group (bracketed are the start address


10-10

and the number of addresses included in the address group), and click <OK> to create a NAT bind.

10.2.9 Deleting a NAT Bind

In the NAT bind management interface, select one or more binds from the bind list, and click <Delete> to delete them.

10.3 Server Management

Internal server is the one residing on a private network and providing access for both public and private network users. Since public network users can only access the public address of an internal server (hereinafter referred to as server), S8016 publicizes the public address of the server and maps it to a private address so as to provide access for both public and private network users. A NAT board can support 256 servers.

10.3.1 Querying NAT Server Information

Select [NAT/Server Management] to open the [Server Management] dialog box, as shown in Figure 10-9.

Figure 10-9 NAT Server Management

The information shown in the interface is described in Table 10-2.


10-11

Table 10-2 Parameters for NAT Server Management

Name Description

Port Interface of the server

Protocol Type of IP packets used to access the server, including tcp and udp.

Global IP Public IP address used by the server

Global Port

Destination port used by public network users to access the server. It ranges from 1 to 65535. For some special services (currently including FTP, Telnet, www, DNS and TFTP) provided by the server, you can directly enter the keywords of their English descriptions.

Inside IP Private IP address of the server

Inside Port

Port on which the server provides services. It ranges from 1 to 65535. For some special services (currently including FTP, Telnet, www, DNS and TFTP) provided by the server, you can directly enter the keywords of their English descriptions.

NAT Board NAT board number of the server

Using NAT Board NAT board in use

This interface provides service adding and deletion operations.

10.3.2 Creating a NAT Server

In the [NAT Server Management] dialog box, click <Add…> to open the [Add NAT Server] dialog box, as shown in Figure 10-10.


10-12

Figure 10-10 Add NAT Server

The meaning of various parameters in the interface is described in Table 10-2. Set the parameters properly and click <OK> to finish the configuration.

Error information will be prompted under the following conditions:

The mix of public address and port of the new server is identical with that of an existent one.

The public address of the new server is same as that of an existent one, but their NAT board numbers are different.

The mix of private address and port of the new server is identical with that of an existent one.

The private address of the new server is same (the port is different) as that of a server configured on the same interface, but their NAT board numbers are different.

There may be two reasons that cause failure information to be returned: The public address is included in a NAT address group with the NAT board number different from that of the server, or a NAT ACL including a single private address exists, which is exactly the one you have input.

10.3.3 Deleting a NAT Server

In the [NAT Server Management] dialog box, select one or more lines and click <Delete> to delete the corresponding servers.


10-13

10.4 Aging Time Management

The aging time here refers to that of the connection entries of various protocols. In the function pane, double-click on [NAT/Aging Time Management] node on the function tree to open the [Aging Time Management] dialog box, as shown in Figure 10-11.

Figure 10-11 Aging Time Management

Here you can browse and configure the aging time of the connection entries of the TCP, UDP, ICMP and FTP. By default, the valid time for the TCP, UDP, ICMP and FTP are 300 seconds, 120 seconds, 60 seconds and 3600 seconds respectively.

10.5 NAT Enable Attribute Management

When both public and private addresses are used for networking, you must configure the NAT enable attribute on the interface connecting to the public network addresses. Configuring the NAT enable attribute on an interface will enable NAT processing on the interface for the outgoing packets. If a packet through the interface matches the conversion condition, it will be allowed to access the public network after NAT processing. If you configure the NAT enable attribute on an interface, you can further specify not to process the packets heading for some public network addresses. An interface not configured with this attribute will not perform NAT processing on the passing packets. This attribute is available only for the interfaces that can be configured with an IP address, such as VLAN and POS interfaces.

10.5.1 Querying the NAT Enable Attribute of an Interface

In the function pane, double-click on [NAT/NAT Enable Attribute Management] node on the function tree to open the [NAT Enable Attribute Management] dialog box, as shown in Figure 10-12.


10-14

Figure 10-12 NAT Enable Attribute Management

Here you can browse the NAT enable status of various interfaces on the device. Click on an interface with the status as enable in the left list, you can also view the destination segments configured on the interface with the NAT function disabled.

10.5.2 Changing the NAT Enable Status of an Interface

In the [NAT Enable Attribute Management] dialog box, select an interface from the left list and click <Change Status> to change the NAT enable status of the interface.

10.5.3 Creating a NAT-enabled Destination Segment

In the [NAT Enable Attribute Management] dialog box, select an interface with the status as enable from the left list and click <Add Segment…> to open the [Denied Segment Creation] window, as shown in Figure 10-13.

Figure 10-13 Creating a denied segment


10-15

Here type an IP address and a mask and click <OK> to create a destination segment with the NAT function disabled.

10.5.4 Deleting a NAT-enabled Destination Segment

In the [NAT Enable Attribute Management] dialog box, select an interface with the status as enable from the left list and select a segment from the right list, and then click <Delete Segment> to delete the segment.

10.6 Blacklist Management

The upper and lower thresholds of total connections and link establishing speed define the ranges of the related attributes of a user. If you enable the control function for total connections, a user will be blacklisted once its total number of connections exceeds the upper threshold. The user will then be prohibited from creating any connection until the number of connections reduces to under the lower threshold and hence the user is removed from the blacklist. If you enable the control function for link establishing speed, a user will be blacklisted when the speed crosses the related upper threshold. The user will then be restricted in its establishing of new connections until its connection establishing speed returns to under the related lower threshold and hence the user is removed from the blacklist.

The blacklist management function is used to management blacklist information and connection limitation parameters. For the enabling/disabling of the blacklist function on a NAT board, refer to section 13.1.

10.6.1 Querying Blacklist Information

In the function pane, double-click on [NAT/Blacklist Management] node on the function tree to open the [Blacklist Management] dialog box. Click the [Blacklist Information] tab and the interface as shown in Figure 10-14 appears:


10-16

Figure 10-14 NAT Blacklist Information

Here you can view the blacklist information on the device, including the IP address, NAT board, total number of connections, connection establishing speed and reason for being blacklisted (such as "Too large connection number", "Too fast connection-establishing speed" and "Unknown") of each blacklist user.

10.6.2 Deleting Blacklist Information

In the NAT blacklist information interface, select one or more lines and click <Delete> to delete the related blacklist information.

Caution:

Some versions of the S8016 device do not support blacklist information deletion and hence the <Delete> button is not available in the related NAT blacklist information interfaces.

10.6.3 Querying and Configuring Blacklist Connection Limitation Parameters

In the function pane, double-click [NAT/Blacklist Management] node on the function tree to open the [Blacklist Management] dialog box. Click the [Connection Limitation] tab and the interface as shown in Figure 10-15 appears:


10-17

Figure 10-15 NAT blacklist - Connection limitation

Here you can view and configure the status of the limitation function for total connections, upper threshold and lower threshold. If the limitation function is disabled, the device will not conduct any control but send an alarm when the total number of connections of a user exceeds the preset threshold.

In this interface, you can also browse and configure the status of the limitation function for link establishing speed, upper threshold and lower threshold. If the limitation function is disabled, the device will not conduct any control but send an alarm when the speed of a user exceeds the preset threshold.

Theoretically, the link establishing speed set in the NMS limits the number of connections established per second, but in practice this parameter is something different from the actual link establishing speed of a user and the two values are not in linear relation. The reason is that this value is related to the number of packets sent consecutively by a user. Figure 10-16 shows the specific relation between the speed set in the NMS (represented by Y-axis) and the actual speed (represented by X-axis). Various fold-lines show the cases of different number of packets sent consecutively.


10-18

Figure 10-16 Relation between the speed set in the NMS and the actual speed

10.6.4 Querying Blacklist Connection Limitation Parameters on Special IPs

In the function pane, double-click on [NAT/Blacklist Management] node on the function tree to open the [Blacklist Management] dialog box. Click the [Connection Limitation on Special IPs] tab and the interface as shown in Figure 10-17 appears:

Figure 10-17 NAT blacklist - Connection limitation on special IPs


10-19

Here you can view the all the connection limitations configured for special IPs, including the corresponding IP address, upper threshold of total connection number, lower threshold of total connection number, upper threshold of connection-establishing speed and lower threshold of connection-establishing speed of each limitation.

Caution:

After you configure the upper and lower thresholds of total connection number for a special IP, the general thresholds set in the [Connection Limitation] tab become ineffective for the address.

10.6.5 Creating Blacklist Connection Limitation Parameters on Special IPs

In the connection limitation interface for special IPs, click <Add…> to open the [Special IP’s Parameters Creation] dialog box, as shown in Figure 10-18.

Figure 10-18 NAT blacklist - Creating parameters for a special IP

Here type the IP address, upper threshold of total connection number, lower threshold of total connection number, upper threshold of connection-establishing speed and lower threshold of connection-establishing speed, and click <OK> to create the connection limitation for a special IP.


10-20

10.6.6 Deleting Blacklist Connection Limitation Parameters on Special IPs

In the connection limitation interface for special IPs, select one or more lines and click <Delete> to delete the related connection limitations.

10.6.7 Configuring Blacklist Connection Limitation Parameters on Special IPs

This operation is similar to the creation operation, see section 13.6.5 for more detail.

User Manual Volume I Quidview Device Manager Chapter 11 Ethernet Interface Configuration

11-1

Chapter 11 Ethernet Interface Configuration

11.1 Overview

The router supports two types of Ethernet interfaces: Fast Ethernet interface (FE) and Gigabit Ethernet interface (GE).

FE and GE supports the following frame formats:

Ethernet_II (ARPA) Ethernet_SNAP Ethernet_SAP

Ethernet_II and Ethernet_SNAP are used to support IP protocol. FE and GE can identify the received frame format, but they can only send one format of frame at one time.

Ethernet interface configuration includes: interface parameter configuration, interface information query, real-time flow statistics, real-time collision statistics, and real-time error statistics. In addition, NE80 and NE40 also provide the sub-interface configuration management function.

Ethernet interface can be configured via the following methods:

1) Function tree

The function menu of the Ethernet interface configuration is shown in the following figure:


11-2

Figure 11-1 Ethernet Interface function tree (NE80 and NE40)

Figure 11-2 Ethernet interface function tree (S8016)

Double-click relevant nodes in the function tree, and configure the related parameters on the Ethernet interface.


11-3

2) Device menu

Select a certain Ethernet interface on the device panel, and right-click the mouse. The device menu shown in the following figure pops up. Select and configure the related parameters on the menu.

Figure 11-3 Device menu (NE80 and NE40)

Figure 11-4 Device menu (S8016)

The two kinds of operation methods have the same function. The chapter is described with the example of the function tree.

11.2 Ethernet Interface Configuration

Double-click [ETH Interface Management/Interface Parameter Configuration] on the function tree. The information display area in the right side shows the main port of Ethernet interface parameter configuration, including: Interface Status Configuration, Interface Parameter Configuration, and Reset Counter.


11-4

With "Interface Configuration" function, you may select different Ethernet interfaces from the device panel to browse their parameter information.

11.2.1 Ethernet Port Status Configuration

Click the [Interface Status Configuration] tab on the interface parameter configuration window, and configure the Administration Status of the selected interface, while Operation Status is not configurable. See the following figure.

Figure 11-5 Interface status configuration

The user select up or down administration status from the pull-down list. Click <Config>. The user configures the management status of the Ethernet interface according to the setting of the user device. If it is configured successfully, the interface status configuration window is refreshed and the interface status has changed. Refreshing the panel can see the change of the interface color.

If the configuration fails or SNMP operation expires, the system prompts the user of the failed configuration or expired SNMP operation.

11.2.2 Interface Parameter Configuration

Click the [Interface Parameter Configuration] tab on the main interface of Ethernet interface parameter configuration, and configure the parameter for the selected interface. See the following figure:


11-5

Figure 11-6 Interface parameter configuration

The parameter description of the configured interface parameter is shown in the following table:

Table 11-1 Interface parameter configuration description

Contents Description

Interface Description Interface name, not configurable

Frame Type Three kinds of link layer frame formats: Ethernet_II, Ethernet_SAP, Ethernet_SNAP

Negotiation Mode Two kinds of negotiation modes: Self-Negotiation, No Self-Negotiation

Interface Operating Mode

Two kinds of interface operation modes: full duplex, half duplex

Interface Transmission Speed

Three kinds of interface transmission rate: 10M, 100M, 1000M

Loopback Mode Three kinds of loopback modes: none, interior, exterior

Max Transport Unit Ranges from 328 to 1500 bytes (The maximum value of the GE interface of NE80 and NE40 routers is 8000 bytes and that for S8016 is 1548.)


11-6

Frame format: Three kinds of frame formats are available for Ethernet: Ethernet_II, Ethernet_SNAP, and Ethernet_SAP. Both Ethernet interface and subinterface can receive the frame of any format at the same time, but they can only send one kind of frame format at one time.

Negotiation mode: For FE electrical interface, if the two parties are connected in auto negotiation mode, they will determine the operating speed and mode by negotiation. If one party is not in auto negotiation mode, the negotiated result can not be guaranteed. By default, FE electrical interface is in auto negotiation mode, while FE optical interface and GE interface are not in auto negotiation modes, because the operating speed and mode of the optical interface are fixedly configured.

Interface Operating Mode: Full duplex and half duplex are available for FE electrical interface, while GE and GE optical interface can only operate in full duplex mode and cannot be configured.

Interface Transmission Speed: FE electrical interface supports 10Mbit/s and 100Mbit/s, while FE optical interface only supports 100Mbit/s and GE optical interface only supports 1000Mbit/s and cannot be configured. By default, the speed of Ethernet FE electrical interface is 10Mbit/s. If the auto negotiation state is enabled, it will determine the operating speed with the peer interface by negotiation (10Mbit/s or 100Mbit/s). Upon configuration, the peer device must be configured to the same speed.

Loopback mode: In Ethernet interface configuration mode, the loopback test can be configured. Loopback is mainly applied in some special cases. Normally, the loopback shall be disabled. By default, loopback of any form shall be disabled. When the loopback function is configured, the interface must be configured to full duplex mode.

Maximum Transmission Unit: The maximum transmission unit MTU (Maximum Transmission Unit) affects the fragment and restructure of IP packet. By default, it is 1500.

The following must be configured upon configuration:

When the interface is the electrical interface, "Interface Transmission Speed" can only be configured as 10M and 100M.

When "Interface Operating Mode" is "Half Duplex", "Loopback Mode" can only be "None".

Maximum transmission unit can only be 328 to 1500 bytes; otherwise, it prompts error upon configuration.

If the interface is the optical interface, "Interface Operating Mode" and "Interface Transmission Speed" cannot be compiled.

If the interface is the electrical interface and the negotiation mode is configured as "Self-Negotiation", "Interface Operating Mode" and "Interface Transmission Speed" are not compiled.


11-7

Click <Config>. The system configures the various parameters of Ethernet interface according to the user setting. If it is configured successfully, the interface status configuration window is refreshed. The interface parameter has changed.

If the configuration fails or SNMP operation expires, the system prompts the user of the failed configuration or expired SNMP operation.

11.2.3 Reset Counter

Click the [Reset Counter] tab in the main port of Ethernet interface parameter configuration, and reset the selected Ethernet interface counter. See the following figure:

Figure 11-7 Reset Counter

The user can select whether to reset the interface counter in the pull-down list. When the status of the reset counter is YES, click <Config>. Click <OK> in the pop-up window, and the system resets the counter of the interface. If it is operated successfully, the system prompts the user that resetting counter succeeded.

If the operation fails or SNMP operation expires, the system prompts the user that resetting counter failed.


11-8

11.3 Ethernet Interface Information Query

In the function pane, double-click [ETH Interface Management /Interface Information Query] on the function tree, you will see the main interface of Ethernet interface information query on the right, in which you can find Browse Basic Information, Browse Received Information, Browse Sent Information, Browse Invalid VLAN ID and Browse E4GC Information.

Select "Interface Information Query" and then you can select an Ethernet interface to view.

11.3.1 Browse Basic Information

In the Interface Information Query interface, select the "Browse Basic Information" tab to view the basic information about the Ethernet interface, shown as the following figure:

Figure 11-8 Browse Basic Information

The following table describes the available common interface information:


11-9

Table 11-2 Browse basic information description


Interface Description Name of the interface

AlignmentErrors Number of the processed frames with intact octet and checksum error

FCSErrors Number of the processed frames with tact octet but checksum error

SingleCollisionFrames Number of the processed frames successfully transmitted by the single collision interface.

MultipleCollisionFrames Number of the processed frames successfully transmitted by the multiple collision interface.

DeferredTransmissions Number of the deferred frames due to lack of free medium

LateCollisions Number of the processed late frames

InternalMacTransmitErrors Number of transmission errors on the MAC sub-layer

FrameTooLongs Number of the processed too-long frames

InternalMacReceiveErrors Number of receiving errors on the MAC sub-layer

DuplexStatus Operation modes include: 1.Unknown, 2.Half Duplex, 3.Full Duplex

11.3.2 Browse Received Information

In the Interface Information Query interface, select the [Browse Received Information View] tab to view the information about data receiving via a specified Ethernet interface, shown as the following figure:


11-10

Figure 11-9 Browse Received Information

The following table describes the Browse Received Information View:

Table 11-3 Browse received information view description



Received Short Frames Number of short frames (less than 64 bytes) received via the interface

Received Frames (64Bytes) Number of 64-byte frames received via the interface

Received Frames (65~127Bytes) Number of 65~127-byte frames received via the interface




Received Frames (1024~1518Bytes)

Number of 1024~1518-byte frames received via the interface

Received Frames (1519~9018Bytes)



11-11


Received Too-Long Frames of Correct Check

Number of long frames with correct checksum received via the interface

Received Too-Long Frames of Check Errors

Number of long frames with checksum error received via the interface

Received Non-Too-Long Frames (Check Errors)

Number of common frames with checksum error received via the interface

Successfully Received Broadcast Frames

Number of broadcast frames successfully received via the interface

Successfully Received Multicast Frames

Number of multicast frames successfully received via the interface

Received Total Frames(Check Error/Correctness)

All frames (with correct/wrong checksum) received via the interface

Received Frames of Physical Layer Errors

Number of frames with physical layer error received via the interface

Frames Failed in Receiving due to Full Queue

Number of failed frames due to lack of queue space on the interface

Received Deferred Frames Number of pausing frames received via the interface

Total Receive-Delay Total pause time on the interface

11.3.3 Browse Sent Information

In the Interface Information Query interface select the [Browse Sent Information] tab to view the information about data transmission from the specified Ethernet interface, shown as the following figure:


11-12

Figure 11-10 Browse Sent Information

The following table describes the Browse Sent Information:

Table 11-4 Browse sent information description



Sent Short Frames(Correct Check)

Number of short frames (of less than 64 bytes) sent from the interface

Sent Short Frames(Check Errors) Number of short frames with checksum error sent from the interface

Sent Frames (64Bytes) Number of 64-byte frames sent from the interface

Sent Frames (65~127Bytes) Number of 65~127-byte frames sent from the interface






11-13



Sent Too-Long Frames of Correct Check

Number of long frames with correct checksum sent from the interface

Sent Too-Long Frames of Check Errors

Number of long frames with checksum error sent from the interface

Total Sent Conflicted Frames Number of collision frames sent from the interface

Abnormally Sent Frames Aborted by PMM Out-Interface

Number of abnormal frames aborted by PMM egress

All Check Error Frames Number of frames with checksum error sent from the interface

Successfully Sent Broadcast Frames

Number of frames successfully broadcast from the interface

Successfully Sent Multicast Frames

Number of frames successfully multicast from the interface

11.3.4 Browse Invalid VLAN ID

Note:

S8016 does not provide the [Invalid VLAN ID View] tab.

In the Interface Information Query interface select the [Browse Invalid VLAN ID] tab to view the information with invalid VLAN ID received/sent by/from a specified Ethernet interface, shown as the following figure:


11-14

Figure 11-11 Browse Invalid VLAN ID

The following table describes the Browse Invalid VLAN ID:

Table 11-5 Browse invalid VLAN ID description



Sent Invalid Frames Number of frames with invalid VLAN ID sent by the master port

Received Invalid Frames

Number of frames with invalid VLAN ID received via the master port

Sent Invalid Octets Number of octets with invalid VLAN ID sent by the master port

Received Invalid Octets

Number of octets with invalid VLAN ID received via the master port

11.3.5 Browse E4GC Information

In the Interface Information Query interface select the [Browse E4GC Information] tab to view the information about E4GC optical module, shown as the following figure:


11-15

Figure 11-12 Browse E4GC Information

The following table describes Browse E4GC Information:

Table 11-6 Browse E4GC information description



Status Online or Offline

Vendor Name Vendor name of the optical module

Compliance Attributes of the optical module

Part Number Model of the optical module

Length9u (Km/n) The maximum transmission distance supported by the 9u optical fiber (Km/n)

Length50u (Km/n)

The maximum transmission distance supported by the 50u optical fiber (Km/n)

Length62u (Km/n)

The maximum transmission distance supported by the 62u optical fiber (Km/n)

WaveLength Wavelength


11-16

Caution:

If you select a interface other than E4GC, the information window prompts “The selected port doesn’t support this function."; if the E4GC port is not online, it prompts "E4GC module isn't online".

11.4 Real-time Statistics of Ethernet Interface

11.4.1 Real-Time Flow Statistics

Double-click [ETH Interface Management/Real-Time Flow Statistics] node on the function tree in the function pane. The system will read and show the real-time flow information about the selected interface in the information display box with a diagram or table. This real-time statistics interface has similar layouts as those previously introduced in this manual. For the functional operations, refer to the proceeding text. Here we just focus on the objects to be monitored in this interface, shown as the following figure:

Figure 11-13 Real-time flow statistics monitor items

The following table describes the traffic statistics items:


11-17

Table 11-7 Real-time flow statistics monitor items


Sent Frame(64Bytes) Number of 64-byte frames sent from the interface

Sent Frame(65~127Bytes) Number of 65~127-byte frames sent from the interface

Sent Frame (128~255Bytes) Number of 128~255-byte frames sent from the interface

Sent Frame (256~511Bytes) Number of 256~511-byte frames sent from the interface

Sent Frame (512~1023Bytes)

Number of 512~1023-byte frames sent from the interface

Sent Frame (1024~1518Bytes)

Number of 1024~1518-byte frames sent from the interface

Received Frame (64Bytes) Number of 64-byte frames received via the interface

Received Frame (65~127Bytes)



Number of 128~255-byte received via the interface 1

Received Frame (256~511Bytes) Number of 256~511-byte received via the interface




Number of 1024~1518-byte frames received via the interface 1024~1518

In the [Real-Time Flow Statistics] interface, you can select and view an Ethernet interface.

11.4.2 Real-Time Collision Statistics

Double-click [ETH Interface Management/Real-Time Collision Statistics] node on the function tree in the function pane. The system will read and show the real-time collision information about the selected interface in the information display box with a diagram or table. This real-time statistics interface has similar layouts as those previously introduced in this manual. For the functional operations, refer to the proceeding text.

Here we just focus on the objects to be monitored in this interface, shown as the following figure:


11-18

Figure 11-14 Real-time collision statistics monitor items

The following table describes the real-time collision statistics items:

Table 11-8 Real-time collision statistics monitor items


Single Collision Frames (frames/s)

Number of single collision frames successfully sent per second

Multiple Collision Frames (frames/s)

Number of multiple collision frames successfully sent per second

Excessive Collisions (frames/s)

Number of cancelled frames per second due to excessive collisions

Sent Total Collisions (frames/s) Total collision frames sent per second

In the "Real-time Collision Statistics" interface, you can select and view an Ethernet interface.

11.4.3 Real-Time Error Statistics

Double-click [ETH Interface Management/Real-Time Error Statistics] node on the function tree in the function pane. The system will read and show the real-time error information about the selected port in the information display box with a diagram or table. This real-time statistics interface has similar layouts as those previously introduced in this manual. For the functional operations, refer to the proceeding text. Here we just focus on the objects to be monitored in this interface, shown as the following figure:


11-19

Figure 11-15 Real-time error statistics monitor items

The following table describes the real-time error statistics items:

Table 11-9 Real-time error statistics monitor items


AlignmentErrors (frames/s) Number of received frames with intact octet and FCS error per second

FCSErrors (frames/s) Number of received frames with tact octet and FCS error per second

Deferred Transmissions (frames/s)

Number of deferred frames to be transmitted due to lack of medium

In the [Real-Time Error Statistics] interface, you can select and view an Ethernet interface.

11.5 Subinterface Management

A physical port is logically divided into several subinterfaces, which share the physical configuration parameters of the interface yet have respective link layer and network layer configuration parameters.

The Ethernet interface of NE80 core router supports the subinterface concept. A physical interface allows you to configure multiple subinterfaces, which makes the networking much more flexible.

Both the FE and GE port LPUs provide subinterfaces. An FE/GE interface supports up to 4095 subinterfaces, numbered as 1 to 4095.

Note that a subinterface can be configured with the parameters such as IP address only if it has been encapsulated with VLAN. Besides, a sub port will always stay administratively down and turn up only after the interface is physically up.


11-20

11.5.1 Subinterface Management

In the NE80 core router function pane, double-click the [ETH Interface Management/Subinterface Management/Subinterface Management] node on the function tree, and the Ethernet subinterface management interface will display and list all the subinterfaces of the interface, shown as the following figure:

Figure 11-16 Subinterface Management

You can perform the following operations of sub port in the above interface: Add, Delete, Config, and Refresh. They will be introduced respectively in the following sections.

In the [Subinterface Management] interface, you can select and view an Ethernet interface.

I. Adding a subinterface

Click <Add> on the Subinterface Management interface and the Add Subinterface will pop up, shown as the following figure:


11-21

Figure 11-17 Add SubInterface

You need input the subinterface ID, which ranges from 1 to 4095.

Click <OK> and add a subinterface. If successful, the system will refresh the Subinterface Management interface and you will see the new subinterface on the list. The VLAN ID of the new subinterface is 0 and the encapsulation format is dot1q(1).

You can use the "Config" function to set the VLAN ID of the subinterface. For details, refer to the contents in the later part of this chapter.

If the system fails to add a subinterface or SNMP operation timeouts, the system will prompt accordingly.

II. Configuring subinterface

Select an entry from the Subinterface Management and click <Config>. Set the "Encapsulation Type" and "VLAN ID" in the [Config Sub Interface] window, shown as the following figure:

Figure 11-18 Config SubInterface


11-22

The following table describes the subinterface configuration parameters.

Table 11-10 Configuring subinterface parameters


Sub Interface ID Composed by and fixed as "Ethernet interface name""+"."+ "Subinterface ID input by a user".

Encapsulation Type dot1q, while NE80 only supports 802.1Q encapsulation only.

VLAN ID The VLAN ID with the value range of 0~4094. 0 means to cancel the VLAN ID.

A subinterface can be configured with a VLAN ID. The VLAN of NE80 core router does not support L2 switching, but support L3 switching.

Note:

In an NE80 core router, a VLAN domain is identified with physical interfaces and VLAN ID together. The subinterfaces of a physical interface should have different VLAN IDs. The subinterfaces of different interfaces may have the same VLAN ID, yet they belong to different VLAN domains.

A subinterface can be configured with such parameters as IP address and MTU only after it have been configured with VLAN encapsulation.

III. Deleting a subinterface

In the Subinterface Management interface, select one or more subinterfaces to be deleted, click <Delete> and click <OK> in the confirmation window. The system will delete the selected interface(s). If successfully, the system will refresh the Subinterface Management and you can find the selected interface(s) has/have been removed from the list.

If the system fails to delete the interface(s) or SNMP operation timeouts, the system will prompt accordingly.

11.5.2 Subinterface MultiCast Query

In the function pane, double-click the [ETH Interface Management/Subinterface Management/Subinterface MultiCast Query] node, you will see the multicast information about the Ethernet subinterfaces, shown as the following figure:


11-23

Figure 11-19 Subinterface MultiCast Query

The following table describes the Subinterface MultiCast Query.

Table 11-11 Subinterface multicast query parameters


Subinterface Description Subinterface ID, composed by "Ethernet interface name"+"."+"Subinterface ID input by a user".

Sent Multicast Packets Number of multicast packets sent from a subinterface.

Received Multicast Packets Number of multicast packets received by a subinterface

Sent Multicast Bytes Number of multicast bytes sent from a subinterface.

Received Multicast Bytes Number of multicast bytes received by a subinterface.

In the "Subinterface MultiCast Query" interface, you can select and view the specified Ethernet interface.

11.5.3 Subinterface Flow Query

In the function pane, double-click the [ETH Interface Management/Subinterface Management/Subinterface Flow Query] node and you will find the flow information about the Ethernet subinterfaces, shown as the following figure:


11-24

Figure 11-20 Subinterface Flow Query

The following table describers the Subinterface Flow Query.

Table 11-12 Subinterface flow query parameters


Subinterface Description Subinterface ID, composed by "Ethernet interface name"+"."+"Subinterface ID input by a user".

Input Octets Number of octets received by a subinterface.

Input Unicast Frames Number of unicast frames received by a subinterface.

Input Non-Unicast Frames Number of non-unicast frames received by a subinterface.

Discarded input Frames Number of the discarded frames received by a subinterface

Output Octets Number of octets sent from a subinterface.

Output Unicast Frames Number of unicast frames sent from a subinterface.

Output Non-Unicast Frames Number of non-unicast frames sent from a subinterface.

Discarded Output Frames Number of the discarded frames sent from a subinterface

In the [Subinterface Flow Query] window, you can select and view the specified Ethernet interface.

User Manual Volume I Quidview Device Manager Chapter 12 Ethernet Trunk Management

12-1

Chapter 12 Ethernet Trunk Management

12.1 Overview

Interface trunking (Link Aggregation or Port Trunking) is a technology capable of bundling multiple physical interfaces as one independent logic link, using the Link Aggregation Control Protocol (LACP).

The Ethernet trunk employs the interface trunking technology to bundle multiple Ethernet physical interfaces as one Eth-Trunk interface to provide greater bandwidths. The NE80/NE40 series router subinterfaces the Eth-Trunk feature, bundling up to 16 Ethernet physical interfaces. Same as an ordinary Ethernet interface, the bundling-formed Eth-trunk interface subinterfaces various services, most of which can be directly configured on this bundling-formed Eth-trunk interface.

The Ethernet trunk can be configured with the following two methods:

1) Function tree

The function menus for the Ethernet trunk configuration are shown in the following figure:

Figure 12-1 Ethernet Trunk Function Tree

Double-click the relevant node on the function tree to configure the Ethernet trunk.

2) Device menu

Right click the device panel to pop up the device menu, as shown in the following figure, where you can configure relevant parameters of the Ethernet trunk.


12-2

Figure 12-2 Device menu

The two operation methods have the same functions. This chapter takes the function tree operations as an example.

Double-click the function node [ETH Trunk Management/ETH Trunk Management] on the function tree in the function pane, and the Eth Trunk Management window will display in the information display area at the right, as shown in the following figure:

Figure 12-3 Eth Trunk Management window

Operations of Add, Delete, Config, View, Monitor and Refresh, etc. can be performed for the Eth Trunk in this window, and they are respectively described as follows.

12.2 Adding an Eth Trunk

Click <Add> in the Eth Trunk Management window and the system will pop up the Add Trunk window, as shown in the following figure:


12-3

Figure 12-4 Add Trunk window

The user is required to input the ID of the Trunk to be added in the Add Trunk window, and the Trunk ID is an integer within 0 ~ 15.

Click <OK> and the system will add an Eth Trunk interface. If the interface is added successfully, the system will refresh the main Eth Trunk Management interface, where the user can find the added Eth Trunk. The parameters of the Eth Trunk employ the default values, as shown in the following table:

Table 12-1 Default Eth Trunk parameters

Content Description

Trunk Description Description of the Trunk, consisting of "Eth-Trunk" and "Trunk ID" input by the user. This parameter can not be modified.

Trunk ID ID of the corresponding Eth Trunk interface, input by the user.

Trunk Name

Name of the corresponding Eth Trunk, automatically generated by the system, consisting of "HUAWEI, Quidway Series, Eth-Trunk", "Trunk ID" and " Interface". This parameter can be modified..

MTU MTU value of the corresponding Eth Trunk, "1500" by default. This parameter can be modified.

Encapsulation Type

Link encapsulation type of the corresponding Eth Trunk, "Ethernet_II" by default. This parameter can be modified.

Reset Counter The flag indicating whether to clear the statistical data, YES by default. This parameter can be modified.

Administration Status

Administration status, up by default. This parameter can be modified.

Operation Status Operation status, down by default. This parameter can not be modified.


12-4

The user can set the Trunk Name, MTU, Encapsulation Type, Reset Counter and Administration Status, etc. of the Eth Trunk via the "Config" function. For details, see the following relevant contents of this chapter.

If the Add operation fails or the SNMP operation times out, the system will prompt the user accordingly.

12.3 Deleting an Eth Trunk

Select one or multiple lines of the contents to be deleted on the main Eth Trunk Management interface, then click <Delete> on this interface, and the system will pop up a deletion confirmation window. Click <OK> in this window, and the system will delete the selected contents. If the contents are deleted successfully, the system will refresh and display the main Eth Trunk Management interface, where the user can find that the Eth Trunk has been deleted as expected.

If the Delete operation fails or the SNMP operation times out, the system will prompt the user accordingly.

12.4 Eth Trunk Configuration

Select a line on the main Eth Trunk Management interface, then click <Config> to configure relevant attributes of the Eth Trunk in the Eth Trunk configuration window, including Status Configuration, Parameter Configuration, Counter Configuration and Port Configuration, as described below.

12.4.1 Eth Trunk Status Configuration

Click the [Status Configuration] tab in the Eth Trunk configuration interface to configure the administration status of this interface, as shown in Figure 12-5.


12-5

Figure 12-5 Eth Trunk Status Configuration window

The description of the Eth Trunk Status Configuration window is shown in Table 12-2.

Table 12-2 Eth Trunk status configuration

Content Description

Trunk ID ID of the corresponding Eth Trunk interface, which can not be configured.

Trunk Name Name of the corresponding Eth Trunk, which can not be configured.

Trunk Description Trunk description information, which can not be configured.

Administration Status Administration status, including up and down.

Operation Status Operation status, which can not be configured.

Click <Config> and the system will configure the administration status of the Eth Trunk as set by the user. If the configuration is successful, the system will refresh and display the result after configuration.

If the configuration operation fails or the SNMP operation times out, the system will prompt the user accordingly.


12-6

12.4.2 Eth Trunk Parameter Configuration

Click the [Parameter Configuration] tab in the Eth Trunk configuration interface to configure the Trunk Name, MTU and Encapsulation Type of this interface, as shown in Figure 12-6.

Figure 12-6 Eth Trunk Parameter Configuration window

The description of the Eth Trunk Parameter Configuration window is shown in Table 12-3.

Table 12-3 Eth Trunk Parameter Configuration

Content Description

Trunk ID ID of the corresponding Eth Trunk interface, which can not be configured.

Trunk Name Name of the corresponding Eth Trunk, with the value range of 1 to 47 characters.

Trunk Description Trunk description information, which cannot be configured.

MTU MTU value of the corresponding Eth Trunk, with the value range of 328~1500.

Encapsulation Type

Link encapsulation type of the corresponding Eth Trunk. Three types are available: Ethernet_II, Ethernet_SAP, and ethernet_SNAP.


12-7

Click <Config> and the system will configure the parameters of the Eth Trunk as set by the user. If the configuration is successful, the system will refresh and display the result after the configuration.


12.4.3 Eth Trunk Counter Reset

Click the [Counter Reset] tab in the [Trunk configuration] dialog box to configure whether to reset the statistics counter of this interface, as shown in Figure 12-7.

Figure 12-7 Eth Trunk Counter Reset window

Select yes, and the system will clear the statistical data flag. Otherwise, it will not clear this flag.

Click <Config>, and the system will configure the reset status of the operation statistic counter as set by the user. If the configuration is successful, the system will refresh and display the result after the configuration.


12.4.4 Port Configuration

Click the [Port Configuration] tab in the Eth Trunk configuration interface to configure the ports included in this Eth Trunk, as shown in Figure 12-8.


12-8

Figure 12-8 Eth Trunk Port Configuration window

This interface includes two lists: [Available Ports] and [This Trunk's Ports]. The [Available Ports] lists all the fast Ethernet interfaces (FE) and gigabit Ethernet interfaces (GE) included in this device, but it does not include the sub-interfaces. "This Trunk's Ports" lists the Ethernet interfaces included in the currently selected Eth Trunk.

Select one or more interfaces in [Available Ports], then click <>>> in the figure, and the selected interface(s) will be added to [This Trunk's Ports]. Similarly, select one or more interfaces in [This Trunk's Ports], then click <<<> in the figure, and the selected interface(s) will be deleted from [This Trunk's Ports].

To configure the Eth Trunk member interface, the following conditions must be available:

The administration status of the interface is UP. The physical port added to the Trunk must be in the full duplex mode, and no other

configurations can be made before it is added (For FE, the interface can only be configured as negotiation auto and no shutdown. For GE, the interface can only be configured as no negotiation auto and no shutdown.)

There should be not any sub-interface.


12-9

One Eth Trunk interface can be configured with up to 16 member interfaces, which must be of the same type. That is, all of them must be FE or GE, with the same bandwidth, and moreover, FE and GE can not be bound together.

Click <Config> and the system will configure the member interfaces of this Eth Trunk as set by the user. If the configuration is successful, the system will refresh and display the result after the configuration.


12.5 Eth Trunk Information Query

Select a line in the main Eth Trunk Management interface, and click <View> to query relevant information of the Eth Trunk, including [Trunk Information] and [Trunk Port Information], as described below.

12.5.1 Trunk Information

Click the [Trunk Information] tab in the Eth Trunk View interface to display relevant parameters of the Trunk interface, as shown in Figure 12-9.

Figure 12-9 Eth Trunk Information query window


12-10

The description of query information is shown in Table 12-4.

Table 12-4 Default Eth Trunk parameters

Content Description

Trunk ID ID of the corresponding Eth Trunk interface.

Trunk Name Name of the corresponding Eth Trunk

Trunk Description Description information of this Trunk

Administration Status Administration status of this Trunk

Operation Status Operation status of this Eth Trunk

MTU MTU value of the corresponding Eth Trunk.

Encapsulation Type Link encapsulation type of the corresponding Eth Trunk.

Reset Counter The flag indicating whether to clear the statistical data.

12.5.2 Trunk Port Information

Click the [Trunk Port Information] tab in the [Trunk View] dialog box to display relevant parameters of the Trunk member interfaces, as shown in Figure 12-10.

Figure 12-10 Eth Trunk Port Information query window

The description of query information is shown in Table 12-5.


12-11

Table 12-5 Eth Trunk Port Information query

Content Description

Trunk ID ID of the corresponding Eth Trunk interface

Port Description Description information of the Eth Trunk member interface

Lacp Success Whether the Trunk member starts the LACP protocol successfully

12.6 Eth Trunk Statistic Information Query

Select a line in the main Eth Trunk Management interface, and then click <Monitor> to view the flow statistic information of the selected Eth Trunk, as shown in Figure 12-11.

Figure 12-11 Eth Trunk real-time statistics interface

See the previous chapters for operations of different functions in this real-time statistics interface. This chapter will focus on the data items that can be monitored in this real-time statistics interface.

The data items that can be monitored in the Eth Trunk real-time statistics interface fall into four groups. The user can select Receive Monitor, Send Monitor, Error Monitor or LACP Monitor for the selected Eth Trunk. The detailed description can be found in Table 12-6.


12-12

Table 12-6 Eth Trunk statistic information query

Statistics category Statistics item

Received Short Frames (less than 64 bytes)

Received Frames (64 bytes)

Received Frames (65 to 127 bytes)





Received Frames (1519 to 9018 bytes, or 1519 to 9022 bytes when VLAN is supported).

Long Frames Received

Broadcast Frames

Multicast Frames

Receive Monitor

Total Number of Frames (including check errors, multicast, broadcast and ultra long frames)

Sent Short Frames (less than 64 bytes)

Sent Run Frames

Sent Frames (64 bytes)

Sent Frames (65 to 127 bytes)





Sent Frames (1519 to 9018 bytes, or 1519 to 9022 bytes when vlan is supported)

Sent Long Frames Received

Broadcast Frames

Send Monitor

Multicast Frames


12-13

Statistics category Statistics item

RevJabber

RevNumberofFrameswithBadCRC

RevReceiveErrors

RevOverrun

RevNumberofPause

SentJabber

SentTotalCollisions

SentAbort

Error Monitor

SentCRCError

12.7 Eth Trunk Subinterface Management

Similar to an Ethernet interface, VLAN configuration is not available right after the creation of a Trunk interface until a Trunk subinterface is created.

An Ethernet Trunk supports up to 255 subinterfaces with the sequence number ranging from 1 to 255.

12.7.1 Eth Trunk Subinterface Management

In the function pane of an NE80 core router, double-click on [ETH Trunk Management/Trunk Subinterface Management/Trunk Subinterface Management] node on the function tree to open the [Trunk Subinterface Management] dialog box. Select a Trunk interface from the left Trunk interface list, and all the subinterfaces of the interface are displayed in the right list, as shown in Figure 12-12.


12-14

Figure 12-12 ETH Trunk Subinterface Management

Here you can add, delete, configure, refresh and browse Trunk subinterfaces. The specific operation procedures are as follows:

I. Adding a Trunk subinterface

In the Trunk subinterface management interface, click <Add…>to open the "Add Subinterface" interface, as shown in Figure 12-13.

Figure 12-13 Adding a Trunk subinterface

Type the subinterface ID in the range of 1 to 255.

Click <OK> to add a Trunk subinterface. If succeed, the system will refresh the Trunk subinterface management interface where you can browse the new Trunk subinterface with the VLAN ID as 0 and encapsulation format as dot1q(1).


12-15

Here can set the VLAN ID of the subinterface with the "Config" function (see the subsequent sections for more detail).

If adding subinterface fails or SNMP operation times out, you will be prompted accordingly.

II. Configuring a Trunk subinterface

In the Trunk subinterface management interface, select a line and click <Config…> to open the [Config Subinterface] dialog box. Here configure the [Encapsulation Type] and [VLAN ID] of the subinterface, as shown in Figure 12-14.

Figure 12-14 Configuring a Trunk subinterface

Various parameters in the interface are described in the following table:

Table 12-7 Subinterface configuration parameters

Content Description

Subinterface ID Name of the Ethernet Trunk interface plus the subinterface ID specified by the user. This parameter is not configurable.

Encapsulation Type Currently NE80 only supports dot1q (802.1Q) encapsulation.

VLAN ID The value range varies according to different Ethernet interfaces, where 0 refers to canceling VLAN ID.

A Trunk subinterface can only be configured with a single VLAN ID ranging from 1 to 4094. A Trunk supports up to 255 subinterfaces connecting to 255 VLANs. The VLANs of an NE80 core router support not L2 switching but L3 switching.


12-16

Note:

On an NE80 core router, a VLAN domain is jointly identified by a physical port and a VLAN ID. On a physical port, the VLAN IDs of various subinterfaces should be different, while the subinterfaces of different physical ports may have the same VLAN ID through they belong to different VLAN domains.

You must configure VLAN encapsulation for a Trunk subinterface, and then the IP address, MTU and other parameters.

III. Deleting a Trunk subinterface

In the Trunk subinterface management interface, select one or more Trunk subinterfaces to be deleted and click <Delete>. In the popup confirmation dialog box, click <OK> to delete the selected subinterfaces. If the deletion succeeds, the system will refresh the Trunk subinterface management interface to remove the deleted Trunk subinterfaces.

If the deletion fails or SNMP operation times out, you will be prompted accordingly.

12.7.2 Trunk Subinterface MultiCast Query

In the function pane, double-click on [ETH Trunk Management/Trunk Subinterface Management/Trunk Subinterface MultiCast Query] node on the function tree to open the [Trunk Subinterface MultiCast Query] dialog box. Select a Trunk interface from the left Trunk list and the multicast information of all the subinterfaces will be displayed in the right Trunk subinterface list, as shown in Figure 12-15.


12-17

Figure 12-15 Trunk subinterface multicast query

The multicast parameters of a Trunk subinterface are described in Table 12-8.

Table 12-8 Multicast parameters of a Trunk subinterface

Content Description

Subinterface Description

ID of the subinterface, that is, the Ethernet Trunk interface name plus the subinterface ID entered by the user

Sent Multicast Packets Number of multicast packets sent by the subinterface

Received Multicast Packets Number of multicast packets receive by the subinterface

Sent Multicast Bytes Number of multicast octets sent by the subinterface

Received Multicast Bytes Number of multicast octets received by the subinterface

In above interface, you can select a Trunk interface from the left Trunk interface list to access the Ethernet Trunk interface you want to manage.

12.7.3 Trunk Subinterface Flow Query

In the function pane, double-click the [ETH Trunk Management/Trunk Subinterface Management/Trunk Subinterface Flow Query] node on the function tree to open the [Trunk Subinterface Flow Query] dialog box. Select a Trunk interface from the left Trunk


12-18

interface list and the flow information of all the subinterfaces is displayed in the right Trunk subinterface list, as shown in Figure 12-16.

Figure 12-16 Trunk Subinterface Flow Query

The flow parameters of a Trunk subinterface are described in the following table:

Table 12-9 Flow parameters of a subinterface

Content Description

Subinterface Description

ID of the subinterface, that is, the Ethernet Trunk interface name plus the subinterface ID entered by the user

Input Octets Number of input octets of the subinterface

Input Unicast Frames Number of input unicast frames of the subinterface

Input Non-Unicast Frames Number of input non-unicast frames of the subinterface

Discarded Input Frames Number of discarded input frames of the subinterface

Output Octets Number of output octets of the subinterface

Output Unicast Frames Number of output unicast frames of the subinterface

Output Non-Unicast Frames Number of output non-unicast frames of the subinterface

Discarded Output Frames Number of discarded output frames of the subinterface

In above interface, you can select a Trunk interface from the left Trunk interface list to access the Ethernet Trunk interface you want to manage.

User Manual Volume I Quidview Device Manager Chapter 13 IP Trunk Management

13-1

Chapter 13 IP Trunk Management

13.1 Brief Introduction to the IP Trunk

IP Trunk technology is to bundle multiple POS physical ports and provide the total bandwidths of the bound POS interfaces for one IP Trunk interface. For one IP Trunk interface, up to 16 POS interfaces can be bound, and 16 IP Trunk interfaces are supported in the whole device. If the POS interface is added to the IP Trunk, neither the interface administration status nor the link encapsulation protocol can be configured. Instead, they are configured via the IP Trunk.

If it is necessary to assign the bandwidths more flexibly in some special networking, employ the IP Trunk technology to bundle multiple POS physical ports and provide the total bandwidths of the bound ports for one Trunk interface.

The NE80/NE40 series router supports the IP Trunk feature, bundling multiple POS physical ports as one IP Trunk interface to provide greater bandwidth. One device supports 16 IP Trunk interfaces.

The IP Trunk can be configured with the following two methods:

1) Function tree

The function menus for the IP Trunk configuration are shown in the following figure:

Figure 13-1 IP Trunk Function Tree

Double-click the relevant node on the function tree to configure the IP Trunk.

2) Device menu

Right click the device panel to pop up the device menu shown in the following figure, where you can configure relevant parameters of the IP Trunk.


13-2

Figure 13-2 IP Trunk device menu


Double-click the function node [IP Trunk Management/IP Trunk Management] on the function tree in the function pane, and the IP Trunk Management window will display in the information display area at the right, as shown in Figure 13-3.

Figure 13-3 IP Trunk Management window

Operations of Add, Delete, Config, View and Refresh, etc. can be performed in this window for the IP Trunk, as described below.

13.2 Adding an IP Trunk

Click <Add> in the IP Trunk Management window and the system will pop up the Add IP Trunk window, as shown in the following figure:


13-3

Figure 13-4 Add IP Trunk window

The user is required to input the ID of the Trunk to be added in the [Add IP Trunk] dialog box. The value range of the Trunk ID is an integer within 0 to 15.

Click <OK> and the system will add an IP Trunk interface. If it is added successfully, the system will refresh the main IP Trunk Management interface, and the user can find the added IP Trunk, whose parameters use the default values, as shown in the following table:

Table 13-1 Default IP Trunk parameters

Content Description

IP Trunk ID ID of the corresponding IP Trunk interface, input by the user.

IP Trunk Description

IP Trunk description, consisting of Ip-Trunk and IP Trunk ID input by the user, read-only.

Administration Status Administration status, up by default, readable and writable.

Operation Status Operation status, down by default, read-only.

MTU MTU value of the corresponding IP Trunk, 1500 by default, read-only.

Encapsulation Type

Link encapsulation type of the corresponding IP Trunk, PPP by default, readable and writable.

The user can set the Encapsulation Type, Administration Status, and Member Ports, etc. of the IP Trunk via the "Config" function. For details, see the following contents of this chapter.

If the adding operation fails or the SNMP operation times out, the system will prompt the user accordingly.


13-4

13.3 Deleting an IP Trunk Interface

Select one or more IP Trunks to be deleted in the interface, and click <Delete> in the main IP Trunk Management interface to pop up a deletion confirmation window, then click <OK>, and the system will delete the selected content. If the deletion operation is successful, the system will refresh and display the main IP Trunk Management interface, where the user can find that the IP Trunk interface has been deleted as expected.

If the deletion operation fails or the SNMP operation times out, the system will prompt the user accordingly.

13.4 Configuring the IP Trunk

Select a line in the main IP Trunk Management interface, and click <Config> to configure relevant attributes of the IP Trunk in the IP Trunk configuration window, including status configuration, link encapsulation protocol configuration and member interface configuration, as described below.

13.4.1 IP Trunk Status Configuration

Click the [Trunk Status Configuration] tab in the [Config IP Trunk] dialog box to configure the administration status of this interface, as shown in the following figure:

Figure 13-5 IP Trunk Status Configuration

The description of the [IP Trunk Status Configuration] tab is shown in the following table:


13-5

Table 13-2 IPTrunk Status Configuration

Content Description

Trunk ID ID of the corresponding IP Trunk interface, read-only.

Trunk Description Trunk description, read-only.


Administration status, including "up" and "down", which can be configured by the user.

Operation Status Operation status, including "up" and "down", read-only.

The user can select an IP Trunk in this interface and configure the administration status as up or down.

Click <Config> and the system will configure the administration status of the IP Trunk as set by the user. If the configuration is successful, the system will refresh and display the result after the configuration.


13.4.2 IP Trunk Parameter Configuration

Click the [Parameter Configuration] tab in the [Config IP Trunk] dialog box to configure the Encapsulation Type of this interface, as shown in Figure 13-6.

Figure 13-6 IP Trunk Parameter Configuration

The link encapsulation protocol of IP Trunk supports PPP and HDLC, "PPP" by default. When the user clicks <Config> after configuring the link encapsulation protocol, the system will configure the link encapsulation protocol as set by the user. If the


13-6

configuration is successful, the system will refresh and display the result after the configuration.


13.4.3 Add/Delete IP Trunk Member Port

Click the [Trunk Member Configuration] tab in the [Config IP Trunk] dialog box to configure the POS interfaces included in this IP Trunk, as shown in Figure 13-7.

Figure 13-7 IP Trunk Member Configuration

Up to 16 POS interfaces can be bound for the IP Trunk, and one POS interface can be added to one IP Trunk at most.

Before the POS interface is added to IP Trunk, neither the interface administration status nor the link encapsulation status can be configured. Instead, they are configured via the IP Trunk. See the contents of the previous chapters.

If the user selects an IP Trunk to be configured in the IP Trunk interface, the member interfaces of this IP Trunk will be listed in the [Ports to be configured] list box of the interface shown above, and the POS interfaces available on the device (the non-channelized POS interfaces, not including those added to the APS group) will be listed in the [Available Ports] list box.


13-7

Select one or more POS interfaces in the [Available Ports] list box, then click <>>> to add the selected interface(s) to the list box "Ports to be configured". Select one or more POS interfaces in the list box "Ports to be configured", then click <<<> to delete the selected interface(s) from the [Ports to be configured] list box and move it to the [Available Ports].

Click <Config> and the system will configure the member interface of this IP Trunk as set by the user. If the configuration is successful, it can be found on this interface that the member interfaces of this IP Trunk has been set as required by the user.


13.5 IP Trunk View

Select a line in the main interface of IP Trunk Management, and then click <View> to query relevant information of the IP Trunk, including [Member Port Information] and [Flow Information], as described below.

13.5.1 IP Trunk Member Port Information

Click the [Member Port Information] tab in the [IP Trunk View] dialog box to query the member ports of the IP Trunk as well as the running status of the member interface, as shown in Figure 13-8.

Figure 13-8 IP Trunk Member Port query

The query information is shown in Table 13-3.


13-8

Table 13-3 IP Trunk member interface query

Content Description

IP Trunk ID ID of the corresponding IP Trunk interface.

Member Port Description Name of the corresponding member interface.

Running Status Status of the corresponding member interface, including "up" and "down".

13.5.2 IP Trunk Flow Statistics Query

Click the [Flow Information] tab in the [IP Trunk View] dialog box, where the user can query the flow statistics information of the IP Trunk, as shown in Figure 13-9.

Figure 13-9 IP Trunk Flow Information query

The statistics information that can be queried includes: number of the received bytes, number of the received unicast packets, number of the multicast packets, number of the received broadcast packets, number of the received error packets, number of the received packets discarded, number of the sent bytes, number of the sent unicast packets, number of the sent multicast packets, number of the sent broadcast packets, number of the sent error packets and number of the sent packets discarded, etc.

Click <Refresh> and the system will refresh the flow statistics information of this interface.

User Manual Volume I Quidview Device Manager Chapter 14 POS Interface Management

14-1

Chapter 14 POS Interface Management

14.1 Overview

The TDM technology of SDH was once deemed mainly for optimization of the voice transmission. However, SDH and optical fiber have become the important technology for construction of the IP-based large-scale and high-speed networks. This is because in the Internet and large enterprise data networks, the POS interface can effectively transmit data via SDH and provide great bandwidths for data transmission, thus playing an important role in the rapidly increasing Internet. The NE80 product intends to provide the ISPs or the value-added networks with a cost-effective POS solution.

The POS interface is very common in GSR, with flexible solutions for different transmission applications. The known applications include the network backbone application and the data aggregation and distribution application for the network edge. The POS interface of the router is usually connected to ADM, point-to-point SDH link, or directly connected via the optical fiber and DWDM.

With the SDH network as the physical transmission network of the IP data network, IP over SDH encapsulates the IP data packets via link adaptation and framing protocol, then maps the encapsulated IP data packets to the synchronous payload encapsulation SPE of SDH in the byte synchronization mode.

The PPP protocol that is being extensively used encapsulates the IP data packets, and employs the HDLC frame format, i.e. IP/PPP/HDLC/SDH. The PPP protocol provides such functions as multi-protocol encapsulation, error control and link initialization control, while the HDLC frame format delimitates the encapsulated IP data frame of PPP on the synchronous transmission link.

This chapter mainly describes the management functions of the POS interface such as interface configuration, path configuration, link configuration and query of relevant parameters.

The following two methods are available for POS interface management:

1) Function tree

The function menus of POS interface management are shown in the following figure:


14-2

Figure 14-1 POS Interface Management Function Tree

Select a POS interface in the panel and double-click the relevant node on the function tree to configure relevant functions of the POS interface.

2) Device menu

Select a POS interface in the panel, and right click to pop up the interface-level menu, then select the lower-level menu in <POS Interface Management> to configure relevant functions of the POS interface.


Caution:

Only after a POS interface is selected in the panel, can operations related with POS interface management be performed.

14.2 POS Interface Configuration

Select a POS interface in the device panel and double-click the function node [POS Interface Management/Interface Configuration] on the function tree, and the system will pop up the Interface Configuration window shown in Figure 14-2.


14-3

Figure 14-2 POS Interface Management (Status) window

There are two tabs in the figure: [Status Configuration] and [Parameter Configuration]. When switching to the [Parameter Configuration] tab, the configuration dialog box is shown in Figure 14-3.

Figure 14-3 POS Interface Management (Parameter) window

The meanings of interface configuration parameters are shown in Table 14-1.


14-4

Table 14-1 Description of the Interface Status Configuration parameters

Name Description

Interface Description Description of the selected interface, read-only.

Administration Status Administration status of the interface, including the values of up and down, readable and writable.

Operation Status Operation status of the interface, including the values of up and down, read-only.

Table 14-2 Description of the Interface Parameter Configuration parameters

Name Description

Interface Description Description of the selected interface, read-only.

Medium Type For setting the medium type, including the optional values of Sonet and SDH, readable and writable.

Transfer Model For setting the interconnected device type, including the optional values of Sonet and SDH, readable and writable.

J0

For the receiving end to set continuity with the transmitting end. The value range is the number within 0 to 255 when the transmission mode is Sonet, and it is a string of 1 to 15 characters when the transmission mode is SDH; read-only.

loopback For the loopback test, including the optional values of NoLoop, FacilityLoop and TerminalLoop, readable and writable.

Clock Source For configuration of the synchronous timing parameters, including the optional values of Inside (internal clock) and Line (line recovery clock), readable and writable.

Modify relevant parameters and click <Config> to complete the interface configuration operation.

14.3 Path Configuration

Select a POS interface in the device panel and double-click the function node [POS Interface Management/Path Configuration] on the function tree, and the system will pop up the Path Configuration window shown in Figure 14-4.


14-5

Figure 14-4 POS Path Configuration (Path Parameter) window

There are two tabs in the figure: [Path Parameter Configuration] and [Link Configuration]. When switching to the [Link Configuration] tab, the configuration dialog box is shown in Figure 14-5.


14-6

Figure 14-5 POS Path Configuration (Link Configuration) window

The meanings of path configuration parameters are shown in Table 14-3.

Table 14-3 Description of the POS path configuration parameters

Name Description

Interface Description Description of the selected interface; read-only.

Scramble Setting whether to scramble, including the optional values of Scramble (enable scrambling) and UnScramble (disable scrambling).

C2 Setting the multiplex structure of the VC frame and the nature of the information payload, with the value range of 0 to 255.

J1 Setting continuity of the transmitting/receiving end of the path layer, with the value range being a string of 1~15 characters.


14-7

Note:

If the [Scramble] of the POS interface is configured as enable, the “C2” should be configured as 22 (0x16). Otherwise (if the [Scramble] is configured as disable), the [C2] should be configured as 207 (0xCF).

Table 14-4 Description of the POS link configuration parameters

Name Description

Interface Description Description of the selected interface.

Encapsulation Setting the encapsulation protocol type of the link layer, including the optional values of ppp and hdlc.

KeepAlive Timeout

Setting the timeout interval of the KeepAlive message, with the value range of 0 to 32767s.

PPP Authentication

Setting the PPP authentication protocol, including the optional values of pap, chap, chappap, and noauthentication. The parameter is effective only when the encapsulation protocol type of the link layer is set as PPP.

PPP Negotiate Timeout

Setting the timeout interval of the PPP protocol negotiation, with the value range of 1 to 10s. This parameter is effective only when the encapsulation protocol type of the link layer is set as PPP.

Chap Host

Setting the host name of the Chap authentication protocol, with the value range being a string of 1~32 characters. This parameter is effective only when the encapsulation protocol type of the link layer is set as PPP.

Pap Username

Set the user name of the Pap authentication protocol, with the value range being a string of 1~32 characters. This parameter is effective only when the encapsulation protocol type of the link layer is set as "ppp".

Pap PasswdEncrypt

Setting the password display mode of the Pap authentication protocol: noEncrypt or Encrypt. This parameter is effective only when the encapsulation protocol type of the link layer is set as PPP.

Pap Password

Setting the password of the Pap authentication protocol, with the value range being a string of 1 to 16 characters. This parameter is effective only when the encapsulation protocol type of the link layer is set as PPP.

The following corresponding relationships are available for the parameters in the PPP protocol parameter configuration:


14-8

1) When the PPP authentication protocol is pap, the timeout interval of the ppp protocol negotiation, the user name, the password display mode and the password of the pap authentication protocol are effective.

2) When the PPP authentication protocol is chap, the timeout interval of the ppp protocol negotiation and the host name of the chap authentication protocol are effective.

3) When the PPP authentication protocol is chappap, all parameters will be effective, and they are verified in sequence from chap to pap.

Modify the relevant parameters and click <Config> to complete the path configuration operation.

14.4 SDH Interface Query

I. Current Status

Select a POS interface in the device panel and double-click the [POS Interface Management/SDH Interface Query/Current Status] node on the function tree, and the system will pop up the query dialog box shown in Figure 14-6.

Figure 14-6 SDH Interface Current Status (Physical Medium Layer) query window

There are four tabs in the figure: "Physical Medium Layer", "Section Layer", "Line Layer", and "Farend Line Layer". The other tabs are similar to the above figure. For the specific parameter description, see the following tables:


14-9

Table 14-5 Description of the SDH Interface Current Status (Physical Medium Layer) query parameters

Name Description


Medium Type Sonet, SDH

Line Coding sonetMediumOther, sonetMediumB3ZS, sonetMediumCMI, sonetMediumNRZ, sonetMediumRZ

Line Type singleMode1300of15km, multiMode1300of200mOr2km, singleMode1300of2km, singleMode1300ofOver40km, singleMode1550, coaxOrUTP, other

Transfer Model Sonet or SDH

J0

The value is a number within 0~255 when the transmission mode is Sonet. The value is a character string within 1~15 when the transmission mode is SDH.

loopback NoLoop (no loopback), FacilityLoop (internal loopback), TerminalLoop (remote loopback)

Clock Source Inside, Line

Time Elapsed 1 ~ 900 s

Valid Intervals 0 ~ 96

Invalid Intervals 0 ~ 96

Table 14-6 Description of the SDH Interface Current Status (Section Layer) query parameters

Name Description


CurrentStatus NoDefect; LOS; LOF; LOS, LOF.

CurrentESs Error seconds of the current statistic interval (15 minutes).

CurrentSESs Severely error seconds of the current statistic interval (15 minutes).

CurrentSEFSs Severely error frame seconds of the current statistic interval (15 minutes).

CurrentCVs Code violations of the current statistic interval (15 minutes).


14-10

Table 14-7 Description of the SDH Interface Current Status (Line Layer) query parameters

Name Description


CurrentStatus NoDefect; AIS; RDI; AIS, RDI.

CurrentESs Error seconds of the current statistic interval (15 minutes), 0~900.

CurrentSESs Severe error seconds of the current statistic interval (15 minutes), 0~900.

CurrentCVs Code violations of the current statistic interval (15 minutes), 0~232-1.

CurrentUASs Unavailable seconds of the current statistic interval (15 minutes), 0~900.

Table 14-8 Description of the SDH Interface Current Status (Farend Line Layer) query parameters

Name Description






II. Interval Status

Select a POS interface in the device panel and double-click the function node [POS Interface Management/SDH Interface Query/Interval Status] on the function tree, and the system will pop up the query window shown in Figure 14-7.


14-11

Figure 14-7 SDH Interface Interval Status (Section Layer) query window

The relevant history data are listed via the history status query. There are three tabs in the figure: "Section Layer", "Line Layer", and "Farend Line Layer". Other tabs are similar to the above figure. For the specific parameter description, see the following tables:

Table 14-9 Description of the SDH Interface Interval Status (Section Layer) query parameters

Name Description

Interval Number

Sequence number of the reported statistic data, with the value range of 1~32.

ES Error seconds of the interval .

SESs Severe error seconds of the interval .

SEFSs Severe error frame seconds of the interval.

CVs Code violations of the interval.

ValidData Indicating if the data at this time interval is valid.


14-12

Table 14-10 Description of the SDH Interface Interval Status (Line Layer, Farend Line Layer) query parameters

Name Description

Interval Number Sequence number of the statistic data, with the value range of 1 ~ 32.

ES Error seconds of the interval.

SESs Severe error seconds of the interval.

CVs Code violations of the interval.

UASs Unavailable seconds of the interval.

ValidData Indicating if the data at this time interval is valid.

14.5 SDH Path Query

I. Current Status

Select a POS interface in the device panel and double-click the function node [POS Interface Management/SDH Path Query/Current Status] on the function tree to pop up the query window, as shown in the following figure:


14-13

Figure 14-8 SDH Path Current Status (Path Layer) query window

The [Farend Path Layer] tab in this figure is similar to the above one. For the specific parameter description, see the two tables as follows:

Table 14-11 Description of SDH Path Current Status (Path Layer) query parameters

Name Description


CRC crc16 (16-bit check), crc32 (32-bit check)

C2 Setting the multiplex structure of the VC frame and the nature of the information payload, with the value range of 0~255.

S1 unknown, prc, tnc, lnc, sets, dnu

Scramble Scramble (enable scrambling), UnScramble (disable scrambling)

J1 A string of les than 16 characters


14-14

Name Description

CurrentWidth sts1, sts3cSTM1, sts12cSTM4, sts24c, sts48cSTM16

CurrentStatus NoDefect, LOP, PAIS, PRDI, PUNEQ, PSLM





Table 14-12 Description of the SDH Path Current Status (Farend Path Layer) query parameters

Name Description






II. Interval Status

Select a POS interface in the device panel and double-click the function node [POS Interface Management/SDH Path Query/Interval Status] on the function tree, and the system will pop up the query window, as shown in Figure 14-9.


14-15

Figure 14-9 SDH Path Interval Status (Path Layer) query window

The relevant history data are listed via the history status query. The [Farend Path Layer] tab in this figure is similar to the above one. For the specific parameter description, see the contents in Table 14-2.

User Manual Volume I Quidview Device Manager Chapter 15 RPR Interface Management

15-1

Chapter 15 RPR Interface Management

In the current Metropolitan Area Network (MAN), the Sonet/SDH equipment is widely used. However, this technology is tailored for voice transmission, and cannot meet very well the requirements of the data network. The Resilient Packet Ring (RPR) technology is a new technology optimized specifically for the special requirements of the MAN. It adopts the packet-based optical transport technology, defines the Medium Access Control (MAC) protocol for the MAN, Local Area Network (LAN) and Wide Area Network (WAN), and provides multi-service access capability. Meanwhile, this technology can provide low-cost, high-speed, secure and reliable data links based on the existing optical fiber infrastructures of the operators.

RPR interface management function applies to high-end routers, which can be implemented in the following two ways:

I. Function tree

The RPR function menus are shown in the figure below:

Figure 15-1 Function tree of RPR interface management

After selecting a RPR interface in the panel, double-click the related node in the function tree to configure the related functions of the RPR interface.

II. Device menu

Select the RPR interface in the panel, and then right click to pop up an interface-level right-click menu, as shown in Figure 15-2. To configure the related functions of the RPR interface, select the menu items of <RPR Interface Management>.


15-2

Figure 15-2 Device menu

The functions of these two operations are completely the same. This chapter takes the function tree operations as an example.

Caution:

Only after a RPR interface is selected from the panel, can you implemented the relevant operations of RPR interface management.

15.1 Logical and Physical Interfaces of RPR

On the NE80 router, two RPR physical interfaces form one logical interface. Figure 15-3 shows the RPR physical interfaces in the NE80 equipment panel. Of them, the RPR service board on the slot with an odd No. is called side A of the RPR logical interface and the RPR service board on the slot with an even No. is called side B of the RPR logical interface. Meanwhile, the interface description of the side A physical interface is taken as the interface description of the logical interface.

Figure 15-3 RPR physical interfaces


15-3

Caution:

When the NE80 router only has two physical interfaces, no matter which interface the customer selects, the current logical interface will not change. This is because they belong to the same logical interface. As shown in Figure 15-3, no matter whether Rpr7/0/0 or Rpr8/0/0 is selected, the function interface later opened always shows the logical interface description is Rpr7/0/0.

15.2 Interface Management

The interface management function can help us query and configure the information like the interface state, parameters, etc.

After selecting a RPR interface from the panel, double-click the [RPR Interface Management/Interface Management] function node in the function tree. Then, an Interface Management window will appear in the right information display area, as shown in Figure 15-4.

Figure 15-4 The interface management window

The interface management window contains three tabs: MAC Parameter, Interface Status, and Interface Parameter.


15-4

15.2.1 MAC Parameter

This tab is used to config/query the related parameters of the MAC layer of interface sides A and B. As shown in Figure 15-4, the MAC Parameter tab includes three parts below:

Interface Description: Displays the interface description of the currently selected logical interface.

Interface Side: Used to select a side. Side Parameters: Displays the MAC layer parameters of side A or B.

I. Side selection

To query the MAC layer parameters of side A or B, you can check the option button in the Interface Side section. To query the MAC layer parameters of side A, check "Side A". To query the MAC layer parameters of side B, check "Side B".

II. Parameter configuration

To modify the parameters of "Side A" or "Side B", click <Config> in Figure 15-4.

The meanings of parameters are given in the table below:

Table 15-1 MAC layer parameter description

Name Description

Topology Timer Readable and writable, used to set the interval of sending the topology discovery request, ranging between 1~600s.

WTR Timer Readable and writable, used to set the duration of being in the wrap state, ranging between 10~600s.

IPS Timer Readable and writable, used to set the frequency at which the IPS messages are sent, ranging between 10~600s.

Operator Request Readable and writable, used to set the switching request, value range: NoRequest, NoManualSwitch, ManualSwitch, NoForceSwitch, ForcedSwitch

Clock Source Readable and writable, acting as the source of the interface board clock, value range: Internal, Line

HighPriority Rate Readable and writable, used to set the rate limit of the high priority queue, ranging between 0~1000M

LowPriority Rate Readable and writable, used to set the rate limit of the low priority queue, ranging between 0~2500M

Neighbor MAC Address

Read-only, the MAC address of the neighbor node over the RPR ring

Neighbor IP Address

Read-only, the IP address of the neighbor node over the RPR ring


15-5

Name Description

Automatic Request

Read-only, the auto IPS protection request type of the current interface, value range: nonStatus, waitToRestore, signalDegrade, signalFail

Request Path Indicator

Read-only, the identifier of the path used by the interface to send the IPS requests, value range: shortPath, longPath, localRequest, mateSourced, mateForwarded, mateUpdateNeighbor, mateSourcedBySelf

Wrap Counter Read-only, the Wrap times after the interface board is started

Last Wrap Time Read-only, the system time of the last Wrap

Note:

When configuring the operation request parameters, if the operation request is ManualSwitch, you can cancel it by configuring NoManualSwitch. Similarly, to cancel the ForcedSwitch request, configure the NoForceSwitch operation request.

15.2.2 Interface Status

This tab is used to configure and query the logical interface status, as shown in Figure 15-5.

Figure 15-5 The Interface Status tab


15-6

To modify the value of the interface administration status, click <Config> in Figure 15-5.

The parameters are described in Table 15-2.

Table 15-2 Description of the interface state parameters

Name Description

Interface Description Read-only, the interface description of the logical interface

Interface Administration status

Readable and writable, the current administration state of the interface, value range: up, down

Interface Operation status Readable and writable, the current running state of the interface, value range: up, down

15.2.3 Interface Parameter

This tab is used to query the parameters of the RPR logical interface, as shown in Figure 15-6.

Figure 15-6 The Interface Parameter tab



15-7

Table 15-3 Description of interface parameters

Name Description

Interface Description Description of a logical interface

IP Address The IP address of an interface

Priority Threshold

The priority threshold; used to determine what type of a queue (two types, i.e. high priority, and low priority) the packets will be placed in according to the packet type. E.g. if the priority is 5, then 0~5 indicates the low priority while 6~7 indicates the high priority.

Nodes On Ring Number of nodes on the RPR

IPS status The IPS state of a node, value range: idle, passthrough, wrapped

Time Elapsed Time from the last statistics report in seconds.

Valid Intervals Number of intervals during which the statistical data is reported effectively; each interval is 15 minutes.

15.3 Counter Configuration

The counter configuration implements the configuration of the RPR statistical counter and the traffic monitoring function for the statistical data.

After selecting a RPR interface in the panel, double-click the [RPR Interface Management/Counter Configuration] function node in the function tree. Then, in the information display area on the right, the Counter Configuration window will pop up, as shown in Figure 15-7.


15-8

Figure 15-7 The Counter Configuration window

The Counter Configuration window includes three tabs: Source Counter Configuration, Destination Counter Configuration, and Source Reject Counter Configuration.

15.3.1 Source Counter Configuration

The source address counter of the RPR interface can take statistics according to the source MAC address of the packets received by the node, so as to monitor the traffic from a node over the RPR network. The Source Counter Configuration tab can implement the functions of add/delete/reset the source address match counter and the function of monitoring the traffic of statistical data, as shown in Figure 15-7. The parameters are described in Table 15-4.

Table 15-4 Description of the source counter parameters

Name Description

Source MAC address The MAC address of the source address counter

Time Stamp-D,H:M:S.00th The time interval from the last counting

Source Packet Count Number of packets counted by the source address counter

Clear Count Flag The counter clear flag, value range: true, false. The value of this flag bit is True at the moment when the counter is restarted and becomes False immediately after counting.


15-9

I. Adding a source counter

Click <Add…> in Figure 15-7. Then, the "Add Source Counter" window will pop up, as shown in Figure 15-8.

Figure 15-8 The window for adding a source counter

The [Add Source Counter] window includes two list boxes. The "Available Node" list on the left lists the nodes that can be added. You can select one line or more according to actual needs and then click <>>> to add the selected nodes to the [Selected Node] list, as shown in Figure 15-9.


15-10

Figure 15-9 The window for adding a source counter

Also, you can select one line or more from the [Selected Node] list on the right, and then click <<<> to remove the nodes from the [Selected Node] list.

Click <OK> to add the nodes from the [Selected Node] list to the source counter.

Note:

The same node cannot be added to the source address counter repeatedly. That is, the nodes added to the source address counter will be filtered out in the [Available Node] list.

II. Deleting a source counter

In Figure 15-7, select one or more lines of data according to the actual needs and then click <Delete> to delete the selected source counter.

III. Reset the source counter

In Figure 15-7, select one or more lines of data according to the actual needs and then click <Reset> to restart the selected source counter.

IV. Traffic monitoring

In Figure 15-7, select one or more lines of data according to the actual needs and click <Monitor…>. Then, the [Source Counter Statistics] window will pop up, as shown in


15-11

Figure 15-10, which can help you monitor the variation trend of values in a graphical way.

For details about using the [Source Counter Statistics] window, refer to Chapter 5 “Performance Monitoring”.

Figure 15-10 The window for the source counter monitor

15.3.2 Destination Counter Configuration

The destination counter of the RPR interface can take statistics based on the destination MAC address of the packets received by the node, so as to monitor the traffic sent from the local node of the RPR network to a specified node. The Destination Counter Configuration tab can implement the functions of add/delete/reset the destination address match counter and the function of monitoring the statistical data in real time, as shown in Figure 15-11.


15-12

Figure 15-11 The window for configuring the destination counter

The operations of add/delete/reset the destination counter and the operation of taking statistics are completely the same as those of the source address counter. Please refer to the contents of section 15.3.1 “Source Counter Configuration”.

15.3.3 Source Reject Counter Configuration

The refusing source address counter of the RPR interface can refuse the packets from a MAC address, so as to filter the traffic toward the local node. The Source Reject Counter Configuration implements the functions of add/delete the source reject counter, as shown in Figure 15-12.


15-13

Figure 15-12 The window for configuring the source reject counter

The operations of add/delete the source reject counter are completely the same as those of the source counter. Please refer to the contents of section 15.4.2 “Querying the Topology Information”.

Note:

One node cannot be added to different counters simultaneously. That is, the nodes already added to the source address counter will be filtered out of the “Available Node” list of the destination address counter or refusing source address counter.

15.4 Topology Management

The topology management implements the management on the RPR static ring selection, topology information, etc.

After selecting a RPR interface in the panel, double-click the [RPR Interface Management/Topology Management] function node in the function tree. Then, the Topology Management window will pop up in the information display area on the right, as shown in Figure 15-13.


15-14

Figure 15-13 The window for topology management

The topology management window includes two tabs: Static Ring Selection, and Topology Info.

15.4.1 Static Ring Selection

The static ring selection configuration can designate the packet direction toward a node inside the ring as inloop or outloop. The Static Ring Selection implements the functions of add/delete the static ring selection.

As shown in Figure 15-13, the parameters are described in Table 15-5.

Table 15-5 Description of the parameters of static ring selection

Name Description

Remote IP Address The IP address of the node for which ring selection shall be configured.

Ring Identifier Identifying the inloop or outloop

I. Adding the static ring selection

Click <Add…> in Figure 15-13. Then the [Add Static Ring Selection] window will pop up, as shown in Figure 15-14.


15-15

Figure 15-14 The window for adding the static ring selection

The [Add Static Ring Selection] window includes two list boxes. The "Available Node" list on the left lists the nodes that can be added. You can select one or more lines according to needs and then click <>>> to add the selected nodes to the [Selected Node] list, as shown in Figure 15-15.

Figure 15-15 The window for adding the static ring selection

Select one or more lines in "Selected Node" on the right, and then click <<<> to remove the nodes from the [Selected Node] list.


15-16

After selecting "Ring Identifier" from the [Selected Node] list, click <OK> to finish the operation of adding the static ring selection.

II. Deleting the static ring selection

In Figure 15-13, select one or more lines of data. Then, click <Delete> to delete the selected RPR static ring.

Note:

The parameters of a configured RPR static ring cannot be modified. If it is necessary to do so, you must first delete it and then add it anew.

15.4.2 Querying the Topology Information

The topology information query interface can query and display the RPR topology information, as shown in Figure 15-16.

Figure 15-16 The window for querying the topology information



15-17

Table 15-6 Description of the topology information parameters

Name Description

Node Hops Number The hop count between the ring node and the current node

Node MAC Address The MAC address of the ring node

Node IP Address The IP address of the ring node

Node Name The name of the ring node

Node Wrap Status The Wrap status of the ring node

15.5 Querying the SDH Interface

For the use description of this part, please see SDH Interface Query of POS Interface Management.

Taking "Query SDH Interface Current State" for example, the only difference from SDH Interface Query in POS Interface Management is shown in Figure 15-17.

Figure 15-17 The window for querying the SDH interface current status


15-18

In this window, you can select "Side A" or "Side B" from the "Side" area to switch between the display of the SDH interface information of different physical interfaces.

15.6 SDH Path Query

For the use description of this part, please refer to SDH Path Query of POS Interface Management.

Taking "Query SDH Path Current State" for example, the only difference from SDH Path Query in POS Interface Management is shown in Figure 15-18.

Figure 15-18 The window for querying the SDH path current status

In this window, you can select "Side A" or "Side B" from the "Side" area to switch between the display of the SDH path information of different physical interfaces.

15.7 Ring Monitoring

The ring monitoring implements the traffic monitoring for the RPR topology ring statistic items.

After selecting a RPR interface in the panel, double-click the [RPR Interface Management/Ring Monitoring] function node in the function tree. Then, the window for the ring monitoring will pop up in the information display area on the right, as shown in Figure 15-19.


15-19

Figure 15-19 The window for the ring monitoring

In this window, click <Select Items>. Then, the [Select Monitor Item] window will pop up, as shown in Figure 15-20.

Figure 15-20 The window for select monitor item

The "Select Monitor Item" window includes two parts:


15-20

Group of monitored items: divided into two groups, side A and side B. Monitor item: available statistical items, which are the same for side A and side B.

Description of each statistical item can be found in Table 15-7.

Table 15-7 Description of the statistical items of ring monitoring

Name Description

RingCurrentUcastLowPriPktsIn/s The number of received low priority unicast packets within unit time

RingCurrentUcastLowPriOctetsIn/s The number of received low priority unicast bytes within unit time

RingCurrentMcastLowPriPktsIn/s The number of received low priority multicast packets within unit time

RingCurrentUcastLowPriOctetsIn/s The number of received low priority multicast bytes within unit time

RingCurrentUcastHighPriPktsIn/s The number of received high priority unicast packets within unit time

RingCurrentUcastHighPriOctetsIn/s The number of received high priority unicast bytes within unit time

RingCurrentMcastHighPriPktsIn/s The number of received high priority multicast packets within unit time

RingCurrentUcastHighPriOctetsIn/s The number of received high priority multicast bytes within unit time

RingCurrentUcastLowPriPktsOut/s The number of transmitted low priority unicast packets within unit time

RingCurrentUcastLowPriOctetsOut/s The number of transmitted low priority unicast bytes within unit time

RingCurrentMcastLowPriPktsOut/s The number of transmitted low priority multicast packets within unit time

RingCurrentUcastLowPriOctetsOut/s The number of transmitted low priority multicast bytes within unit time

RingCurrentUcastHighPriPktsOut/s The number of transmitted high priority unicast packets within unit time

RingCurrentUcastHighPriOctetsOut/s The number of transmitted high priority unicast bytes within unit time

RingCurrentMcastHighPriPktsOut/s The number of transmitted high priority multicast packets within unit time

RingCurrentUcastHighPriOctetsOut/s The number of transmitted high priority multicast bytes within unit time

Select the group of monitored items. Then, according to actual needs, select one or more statistical items from the [Monitor Item] list. After that, click <OK> to finish the selection of statistical items.


15-21

For detailed use of the window for the ring monitoring, refer to Chapter 5 “Performance Monitoring”.

15.8 Host Monitoring

The Host Monitoring window implements the traffic monitoring for the RPR host statistical items.

After selecting a RPR interface in the panel, double-click the [RPR Interface Management/Host Monitoring] function node in the function tree. Then, the window for the host monitoring will pop up in the information display area on the right, as shown in Figure 15-21.

Figure 15-21 The window for the host monitoring

Here, the operations of selecting statistical items are totally the same as those for the statistics of topology ring counting. For details, see section 17.8.The description of each statistical item is shown in Table 15-8.

Table 15-8 Description of the statistical items of host monitoring

Name Description

HostCurrentUcastLowPriPktsIn/s The number of low priority unicast packets received by the host within unit time

HostCurrentUcastLowPriOctetsIn/s The number of low priority unicast bytes received by the host within unit time


15-22

Name Description

HostCurrentMcastLowPriPktsIn/s The number of low priority multicast packets received by the host within unit time

HostCurrentMcastLowPriOctetsIn/s The number of low priority multicast bytes received by the host within unit time

HostCurrentUcastHighPriPktsIn/s The number of high priority unicast packets received by the host within unit time

HostCurrentUcastHighPriOctetsIn/s The number of high priority unicast bytes received by the host within unit time

HostCurrentMcastHighPriPktsIn/s The number of high priority multicast packets received by the host within unit time

HostCurrentMcastHighPriOctetsIn/s The number of high priority multicast bytes received by the host within unit time

HostCurrentUcastLowPriPktsOut/s The number of low priority unicast packets transmitted by the host within unit time

HostCurrentUcastLowPriOctetsOut/s The number of low priority unicast bytes transmitted by the host within unit time

HostCurrentMcastLowPriPktsOut/s The number of low priority multicast packets transmitted by the host within unit time

HostCurrentMcastLowPriOctetsOut/s The number of low priority multicast bytes transmitted by the host within unit time

HostCurrentUcastHighPriPktsOut/s The number of high priority unicast packets transmitted by the host within unit time

HostCurrentUcastHighPriOctetsOut/s The number of high priority unicast bytes transmitted by the host within unit time

HostCurrentMcastHighPriPktsOut/s The number of high priority multicast packets transmitted by the host within unit time

HostCurrentMcastHighPriOctetsOut/s The number of high priority multicast bytes transmitted by the host within unit time

For detailed use of the window for the host monitoring, refer to Chapter 5 “Performance Monitoring”.

15.9 Error Monitoring

The Error Monitoring window implements the traffic monitoring for the RPR error statistical items.

After selecting a RPR interface in the panel, double-click the [RPR Interface Management/Error Monitoring] function node in the function tree. Then, the window for


15-23

the error monitoring will pop up in the information display area on the right, as shown in Figure 15-22.

Figure 15-22 The window for the error monitoring

Here, the operations of selecting statistical items are totally the same as those for the statistics of topology ring counting. For details, see section 17.8. The description of each statistical item is shown in Table 15-9.

Table 15-9 Description of the statistical items of error monitoring

Name Description

RingCurrentRxErrorsDataParity/sThe number of packets with the parity check error received by the topology ring within unit time

RingCurrentRxErrorsShortPackets/s

The number of packets with less than 16 bytes received by the topology ring within unit time

RingCurrentRxErrorsGiantPackets/s

The number of packets with more than 9216 bytes received by the topology ring within unit time

RingCurrentRxErrorsSideBadPackets/s

The number of bad packets received by the topology ring within unit time

RingCurrentRxErrorsCRC/s The number of packets with the CRC check error received by the topology ring within unit time

RingCurrentTxErrorsDataParity/s The number of packets with the parity check error transmitted by the host within unit time


15-24

Name Description

RingCurrentTxErrorsShortPackets/s

The number of packets with less than 16 bytes transmitted by the host within unit time

RingCurrentTxErrorsGiantPackets/s

The number of packets with more than 9216 bytes transmitted by the host within unit time

RingCurrentTxErrorsSideBadPackets/s

The number of bad packets transmitted by the host within unit time

RingCurrentTxErrorsCRC/s The number of first in first out packets transmitted by the host within unit time

For detailed use of the window for the error monitoring, refer to Chapter 5 “Performance Monitoring”.

15.10 Display Topology Ring

The Display Topology window implements the function of browsing the topology information of the RPR where the current node lies. After selecting a RPR interface in the panel, double-click the [RPR Interface Management/Display Topology] function node in the function tree. Then, the Display Topology window will pop up in the information display area on the right, as shown in Figure 15-23.

Figure 15-23 The display topology window

The Topology Ring Display window is divided into two parts:

1) Functional buttons

These buttons are located on the left of the window. From the top downward they are:

<Pan>: used to drag the topology ring; <Select>: used to select a node inside the ring and drag the node freely; <Zoom in rect>: used to magnify part of the topology ring; <Zoom in>: used to magnify the topology ring;


15-25

<Zoom out>: used to reduce the topology ring; <Fit to view>: used to adjust the size of the topology ring to fit the current view; <Layout>: used to arrange the view again.

2) Topology ring display area

This area is on the right of the window, used to display the RPR topology ring where the current node lies. The viewable information includes:

IP address of the node: displayed below the node icon. Node name: once the cursor is placed in the node area, the prompt information of

the node name will be displayed. Wrap or not: for the node where Wrap occurs, the topological view will disconnect

the connection among nodes. As shown in Figure 15-24, Wrap occurs on node 201.1.1.1 and node 201.1.1.2:

Figure 15-24 The display topology window

Note:

The topology ring view polls and refreshes the topology view display based on the time interval set by the parameter of "Browse polling interval".

Select any other node except this node in the topology ring. Then right click and select the [Open Device…] menu, to open this node device.

User Manual Volume I Quidview Device Manager Chapter 16 CPOS Port Management

16-1

Chapter 16 CPOS Port Management

16.1 Overview

This chapter introduces CPOS interface management function, including Port Configuration, Higher-Order Path Management, Lower-Order Path Management, Multilink Management and query of related parameters.

CPOS interface management can be performed by the following means:

I. Function tree

The function menu of CPOS interface management is shown in the following figure:

Figure 16-1 Function tree for CPOS interface management

Select a CPOS interface from the panel and double-click on different nodes on the function tree to configure the related functions of the CPOS interface.

II. Device menu

Select a CPOS interface from the panel and right click on it to access the short-cut menu of interface level, as shown in Figure 16-2. Select the sub-items of [CPOS Port Management] to perform the related configuration on the CPOS interface.


16-2

Figure 16-2 Device menu for CPOS interface

Figure 16-3 Device menu for CPOS interface board

The two operations function the same, and this chapter takes the function tree operation as an example.

Caution:

Only when you select a CPOS interface from the panel, can you perform the related operations of CPOS interface management. Multilink management addresses CPOS interface boards.

16.2 CPOS Interface Configuration

Select a CPOS interface from the panel and double-click on [CPOS Port Management/Port Config] node on the function tree to open the "Port Config" interface, as shown in Figure 16-4.


16-3

Figure 16-4 CPOS Port Config (Status)

This interface includes two tabbed pages, "Port Status Configuration" and "Port Parameter Configuration". The "Port Parameter Configuration" page is shown in Figure 16-5.

Figure 16-5 CPOS Port Config (Parameter)

Parameters in the interface are described in Table 16-1 and Table 16-2.

Table 16-1 Configuration parameters of interface status

Name Description

Interface Description Description of the interface, read-only

Admin Status Administration status of the interface, including up and down, read-write


16-4

Name Description

Oper Status Operation status of the interface, including up and down, read-write

Table 16-2 Interface configuration parameters

Name Description


Transfer Mode Type the remote device, including byte-1 and byte-16, read-write

J0 It is a string including 1 to 15 characters, which is used by the receiving end to check the connectivity with the sending end. Read-write

Clock Source

Synchronous timing parameter, including Inside (internal clock) and Line (line recovery clock), read-write

Loopback For loopback test, including SonetNoLoop (no loopback), SonetFacilityLoop (internal loopback) and SonetTerminalLoop (remote loopback), read-write

Modify the parameters on your demand and then click <Config> to finish the configuration operation.

16.3 Higher-Order Path Management

Select a CPOS interface from the device panel and double-click on [CPOS Port Management/Higher-Order Path Management] node from the function tree to open the "Higher-Order Path Management" interface, as shown in Figure 16-6.

Figure 16-6 CPOS Higher-Order Path Management


16-5

16.3.1 Higher-Order Path Configuration

In the higher-order path management interface, select a line and click <Config> to open the configuration window, as shown in Figure 16-7.

Figure 16-7 CPOS Higher-Order Path Parameter Configuration

The configuration parameters of a higher-order path are described in Table 16-3.

Table 16-3 Configuration parameters of a CPOS higher-order path

Name Description

Higher-Order Path Description

Description of the path, real-only

J1 It is a string including 1 to 15 characters, which is used to check the connectivity between the receiving and sending ends over the path.

C2 It ranges from 0 to 255, which sets the property of VC frame multiplexing structure and information payload.

S1S0 Load pointer byte, ranging from 0 to 3

16.3.2 Higher-Order Path Current View

In the higher-order path management interface, select a line and click <Current View> to open the current view interface, as shown in Figure 16-8 and Figure 16-9.


16-6

Figure 16-8 Current view of CPOS higher-order path

Figure 16-9 Current view of CPOS farend higher-order path


16-7

Parameters of higher-order path current view are described in Table 16-4 and Table 16-5.

Table 16-4 Parameters of higher-order path current view

Name Description

Interface Description Description of the path, read-only

C2 Sets the property of VC frame multiplexing structure and information payload

J1 Checks the connectivity between the receiving and sending ends over the path

Current Width Includes sts1, sts3cSTM1, sts12cSTM4, sts24c and sts48cSTM16

Current Status Includes NoDefect, LOS, LOF, LOS and LOF.

Current ESs The number of error seconds in current statistical interval (15 minutes)

Current SESs The number of severe error seconds in current statistical interval (15 minutes)

Current CVs Times of code violation in current statistical interval (15 minutes)

Current UASs The number of invalid seconds in current statistical interval (15 minutes), ranging from 0 to 900

Table 16-5 Parameters of farend higher-order path current view

Name Description

Interface Description Description of the path

Current ESs The number of error seconds in current statistical interval (15 minutes), ranging from 0 to 900

Current SESs The number of severe error seconds in current statistical interval (15 minutes), ranging from 0 to 900

Current CVs Times of code violation in current statistical interval (15 minutes), ranging from 0 to 232-1


16.3.3 Higher-Order Path History View

In the higher-order path management interface, select a line and click <History View> to open the history view interface, as shown in Figure 16-10 and Figure 16-11.


16-8

Figure 16-10 History view of CPOS higher-order path

Figure 16-11 History view of CPOS farend higher-order path


16-9

Parameters of higher-order path history view are described in Table 16-6.

Table 16-6 Parameters of higher-order path/farend higher-order path history view

Name Description

Interval Number Serial number for statistics report, ranging from 1 to 32

ESs The number of error seconds in the interval

SESs The number of severe error seconds in the interval

CVs Times of code violation in the interval

UASs The number of invalid seconds in the interval

Valid Data Specifies whether the data collected in the interval is valid

16.4 Lower-Order Path Management

In the device panel, select a CPOS interface and double-click on [CPOS Port Management/Lower-Order Path Management] node on the function tree to open the "Lower-Order Path Management" window, as shown in Figure 16-12.

Figure 16-12 CPOS lower-order path management

16.4.1 Adding a Lower-Order Path

In the lower-order path management interface, click <Add> to open the "Create Lower-Order Path" window, as shown in Figure 16-13.


16-10

Figure 16-13 Creating a lower-order path

Here you need to type the path number in the range of 1 to 63 (for an E1 path) or 1 to 84 (for a T1 path).

Click <OK> to add a lower-order path. If succeed, the system will refresh the lower-order path management interface, where you can browse the new lower-order path. Various parameters of the lower-order path use the default values, as described in the following table:

Table 16-7 Default parameters of a lower-order path

Content Description

Lower-Order Path Number The number of the lower-order path

Lower-Order Path Description Description of the lower-order path

Admin Status By default, the administration status is up. This parameter can be modified.

Oper Status By default, the operation status is down. This parameter cannot be modified.

MTU(byte) MTU of the lower-order path. It is defaulted to 1500 and is configurable.

You can configure the MTU and administration status of the lower-order path with the "Config" function (see the subsequent sections of this chapter).

If the adding fails or in the case of SNMP operation timeout, you will be prompted accordingly.


16-11

16.4.2 Deleting a Lower-Order Path

In the lower-order path management interface, select one or more lines to be deleted and click <Delete> to open the confirmation dialog box. Click <OK> in the dialog box to delete the selected contents. If succeed, the system will refresh the lower-order path management interface to remove the deleted lower-order paths.

If the deletion fails or in the case of SNMP operation timeout, you will be prompted accordingly.

16.4.3 Lower-Order Path Configuration

In the lower-order path management interface, select a line and click <Config> to open the configuration window where to configure the attributes of lower-order path. The configuration includes status configuration, parameter configuration and link configuration, whose interfaces are shown in Figure 16-14, Figure 16-15 and Figure 16-16.

Figure 16-14 Status configuration for a CPOS lower-order path


16-12

Figure 16-15 Parameter configuration for a CPOS lower-order path


16-13

Figure 16-16 Link configuration for a CPOS lower-order path

Various configuration parameters are described in Table 16-8, Table 16-9 and Table 16-10.

Table 16-8 Status configuration parameters of a lower-order path

Name Description

Lower-Order Path Description Description of the lower-order path, read-only

Admin Status Administration status of the lower-order path, including up and down, read-write

Oper Status Operation status of the lower-order path, including up and down, read-only


16-14

Table 16-9 Parameter configuration parameters of a lower-order path

Name Description

Path Description Description of the lower-order path, read-only

LC2 Signal label byte of the lower-order path, ranging from 0 to 7

Clock Source Synchronous timing parameter, including Inside (internal clock) and Line (line recovery clock), read-write

Loopback For loopback test, including noloopback (no loopback), internal (internal loopback) and line (remote loopback), read-write

Table 16-10 Link configuration parameters of a lower-order path

Name Description

Path Description Description of the lower-order path, read-only

Encapsulation Link layer encapsulation type, including ppp and hdlc

KeepAlive Timeout

Timeout of the KeepAlive packets, ranging from 0 to 32767 seconds

PPP Authentication

PPP authentication, including pap, chap, chappap and noauthentication. This parameter is effective only when link layer encapsulation type is set to PPP.

PPP Negotiate Timeout

Timeout for PPP negotiation, ranging from 1 to 10 seconds. This parameter is effective only when link layer encapsulation type is set to PPP.

Chap Host It is a string including 1 to 32 characters, setting the host name for chap authentication. This parameter is effective only when link layer encapsulation type is set to PPP.

Pap User Name It is a string including 1 to 32 characters, setting the user name for pap authentication. This parameter is effective only when link layer encapsulation type is set to PPP.

Pap Password Encrypt

Password display mode for pap authentication, including noEncrypt and Encrypt. This parameter is effective only when link layer encapsulation type is set to PPP.

Pap Password It is a string including 1 to 16 characters, setting the password for pap authentication. This parameter is effective only when link layer encapsulation type is set to PPP.

The corresponding relations between the authentication protocols and parameters are as follows:

For pap authentication, PPP Negotiate Timeout, Pap User Name, Pap Password Encrypt and Pap Password are effective.


16-15

For chap authentication, PPP Negotiate Timeout and Chap Host are effective.

For Chappap authentication, all the parameters are effective, and the authentication proceeds chap authentication to pap authentication.

Modify the parameters on your demand and click <Config> to finish the configuration operation.

16.4.4 Lower-Order Path Traffic Monitor

In the lower-order path management interface, select a line and click <Monitor> to open the "Flow Monitor" window, as shown in Figure 16-17.

Figure 16-17 Traffic monitor for a lower-order path

Click <Select Items> to open the "Select Monitor Item" window, as shown in Figure 16-18.


16-16

Figure 16-18 Selecting monitor items

Various items are described in the following table:

Table 16-11 Traffic monitor items

Monitor item Description

ifHCInOctets/s The number of octets received on the port

ifHCInUcastPkts/s The number of unicast packets received on the port

ifHCInMulticastPkts/s The number of multicast packets received on the port

ifHCInBroadcastPkts/s The number of broadcast packets received on the port

ifInErrors/s The number of error packets received on the port

ifInDiscards/s The number of discarded input packets sent on the port

ifHCOutOctets/s The number of octets sent on the port

ifHCOutUcastPkts/s The number of unicast packets sent on the port

ifHCOutMulticastPkts/s The number of multicast packets sent on the port

ifHCOutBroadcastPkts/s The number of broadcast packets sent on the port

ifOutErrors/s The number of error packets sent on the port

ifOutDiscards/s The number of discarded output packets sent on the port


16-17

16.4.5 Lower-Order Path Current View

In the lower-order path management interface, select a line and click <Current View> to open the current view window, as shown in Figure 16-19 and Figure 16-20.

Figure 16-19 Current view of CPOS lower-order path


16-18

Figure 16-20 Current view of CPOS farend lower-order path

Parameters of lower-order path current view are described in Table 16-12 and Table 16-13.

Table 16-12 Parameters of CPOS lower-order path current view

Name Description

Interface Description Description of the path, read-only

Current Width Includes sts1, sts3cSTM1, sts12cSTM4, sts24c and sts48cSTM16

Current Status Includes NoDefect, LOS, LOF, LOS and LOF






16-19

Table 16-13 Parameters of CPOS farend lower-order path current view

Name Description

Interface Description Description of the interface





16.4.6 Lower-Order Path History View

In the lower-order path management interface, select a line and click <History View> to open the history view window, as shown in Figure 16-21 and Figure 16-22.

Figure 16-21 History view of CPOS lower-order path


16-20

Figure 16-22 History view of CPOS farend lower-order path

Parameters of lower-order path history view are described in Table 16-14.

Table 16-14 Parameters of lower-order path/farend lower-order path history view

Name Description







16.5 Multilink Management

Select a board with a CPOS interface from the device panel and double-click on [CPOS Port Management/Multilink Management] node on the function tree to open the "Multilink Management" window, as shown in Figure 16-23.


16-21

Figure 16-23 CPOS multilink management

16.5.1 Adding a Multilink

In the multilink management interface, click <Add> to open the "Add Multilink" window, as shown in Figure 16-24.

Figure 16-24 Adding a multilink

Here you need to type a multilink number in the range of 1 to 168.

Click <OK> to add a multilink. If succeed, the system will refresh the multilink management interface, where you can view the new multilink. The parameters of the multilink use default values, as described in the following table:


16-22

Table 16-15 Default multilink parameters

Content Description

Multilink Number The number of the multilink

Multilink Description Description of the multilink

Admin Status By default, the administration status is up and can be modified.

Oper Status By default, the operation status is down and cannot be modified.

MTU(byte) The MTU of the multilink. It is defaulted to 1500 and is configurable.

You can configure such parameter as administration status of the multilink with the "Config" function (see the subsequent sections for more detail).

If the adding fails or in the case of SNMP operation timeout, you will be prompted accordingly.

16.5.2 Deleting a Multilink

In the multilink management interface, select one or more lines to be deleted and click <Delete> to open the confirmation dialog box. Click <OK> in the dialog box to delete the selected contents. If succeed, the system will refresh the multilink management interface to remove the deleted multilinks.

If the deletion fails or in the case of SNMP operation timeout, you will be prompted accordingly.

16.5.3 Configuring a Multilink

In the multilink management interface, select a line and click <Config> to open the configuration window where to configure the attributes of the multilink. The configuration includes status configuration, parameter configuration and adding/deleting lower-order path, as shown in Figure 16-25, Figure 16-26 and Figure 16-27:

I. Configuring multilink status

In the multilink configuration interface, click the "Multilink Status Configuration" tab to configure the administration status of the multilink, as shown in the following figure:


16-23

Figure 16-25 Multilink Status Configuration

Parameters in the interface are described in the following table:

Table 16-16 Parameters of multilink status configuration

Content Description

Multilink Description Description of the multilink, not configurable

Admin Status Administration status includes up and down

Oper Status Operation status is not configurable

Click <Config> to configure the administration status of the multilink. If succeed, you can refresh the interface and view the result.

If the configuration fails or in the case of SNMP operation timeout, you will be prompted accordingly.

II. Configuring multilink parameters

In the multilink configuration interface, click the "Multilink Parameter Configuration" tab to configure the MRRU (Max-Receive-Reconstructed Unit), fragment timeout and fragment size of the multilink, as shown in the following figure:


16-24

Figure 16-26 Multilink Parameter Configuration

Parameters of multilink parameter configuration are described in the following table:

Table 16-17 Parameters of multilink parameter configuration

Content Description

Multilink Description Description of the multilink, not configurable

Mrru

MRRU (Max-Receive-Reconstructed Unit) is the necessary parameter for MP negotiation. The peer end reconstructs the received fragments to packets. This parameter is used to set the maximum size (ranging from 4 to 470) of the reconstructed packets so as to facilitate the fragmentation of IP packets.

Drop timeout The timeout of an MP fragment ranges from 10ms to 100ms and is defaulted to 100ms.

Short-sequence Enables/Disables short-sequence MP packet header negotiation

Discriminator Enables/Disables terminal authentication key

Fragment-Threshold MP packets can be divided into fragments of 128 bytes, 256 bytes or 512 bytes, or not be fragmented.

Click <Config> to configure the parameters of the multilink. If succeed, you can refresh the interface and view the result.


16-25


III. Add/delete Lower-Order Path

In the multilink configuration interface, click the "Add/delete Lower-Order Path" tab to configure the lower-order paths included in the multilink, as shown in the following figure:

Figure 16-27 Add/delete Lower-Order Path

This interface includes two lists, "Available Path" and "Select Path". The former lists the currently available lower-order paths, and the latter lists the lower-order paths to be included in the multilink.

Select one or more lower-order paths from the "Available Path" list and click “>>” to add them to the "Select Path" list. Likewise, you can select one or more lower-order paths from the "Select Path" list and click “<<” to remove them.

A multilink can be bound with 12 paths, while a path can only belong to a single multilink at any time. To add a path to a new multilink, you must remove it from the former multilink first.

The physical status of a multilink is UP when the physical status any of its paths is UP, and physical status of a multilink is DOWN when that of all the paths is DOWN.


16-26

When a path joints a multilink, some of its interface attributes and configurations (such as IP, MPLS, peer and ISIS) that are related to network layer configuration are disabled and will be recovered when the path is removed from the multilink interface.

Click <Config> to configure the lower-order paths of the multilink. If succeed, you can refresh the interface and view the result.


Note:

You cannot bind paths of different service boards to a multilink. A service board does not provide E1 and T1 at the same time, but can be channelized to E1 or T1 according to the factory defaults (not changeable).

16.5.4 Multilink Statistics

This function is similar to the traffic statistics function for lower-order paths.


I. Current status

Select a CPOS interface from the device panel and double-click on [CPOS Port Management/SDH Interface Query/Current Status] node on the function tree to open the current status window, as shown in Figure 16-28.


16-27

Figure 16-28 Current status of an SDH interface - Section Layer

This interface includes four tabbed pages, "Section Layer", "Line Layer", "Farend Line Layer" and "E4GC Information", with the contents similar to those shown in above figure. The parameters of each tabbed page are described in the following tables:

Table 16-18 Current status (Section Layer) parameters of an SDH interface

Name Description


Current Status Includes NoDefect, LOS, LOF, LOS and LOF



Current SEFSs The number of serious error frame seconds in current statistical interval (15 minutes)



16-28

Table 16-19 Current status (Line Layer) parameters of an SDH interface

Name Description


Current Status Includes NoDefect, AIS, RDI, AIS and RDI





Table 16-20 Current status (Farend Line Layer) parameters of an SDH interface

Name Description






Table 16-21 Current status (E4GC Information) parameters of an SDH interface

Name Description


Status Includes Online (optical module in service), Offline (optical module not in service)

Vendor Name Vendor the optical module

Compliance Attribute of the optical module

Part Number Model of the optical module

Length9u (Km/n) Length in Km/n supported by 9u fibers


16-29

Name Description

Length50u (Km/n) Length in Km/n supported by 50u fibers

Length62.5u (Km/n) Length in Km/n supported by 62.5u fibers

Wave Len Wave length

Caution:

If the selected interface is not an optical module, the following information will appear in the message window: "The selected port doesn’t support this function". If the optical module is not in service, you will be prompted "E4GC module isn't online".

II. History Status

Select a CPOS interface from the device panel and double-click on [CPOS Port Management/SDH Interface Query/History Status] node on the function tree to open the history status window, as shown in Figure 16-29.

Figure 16-29 History status of an SDH interface - Section Layer

This interface lists the related history data in three tabbed pages, that is, "Section Layer", "Line Layer" and "Farend Line Layer". The contents of various pages are similar


16-30

to those shown in above figure and the specific parameters included in each page are described in the following tables:

Table 16-22 History status (Section Layer) parameters of an SDH interface

Name Description




SEFSs The number of serious frame error seconds in the interval



Table 16-23 History status (Line Layer and Farend Line Layer) parameters of an SDH interface

Name Description







User Manual Volume I Quidview Device Manager Chapter 17 ATM Interface Management

17-1

Chapter 17 ATM Interface Management

17.1 Overview

The ATM (Asynchronous Transfer Mode) is a transmission and switching mode of broadband ISDN and, for its flexibility and support for multimedia services, is considered as the core technology that implements broadband communication.

The ATM is a connection-oriented switching technology based on VC (Virtual Circuit), each of which is identified by a VPI (Virtual Path Identifier) and a VCI (Virtual Channel Identifier).

For the IP, ATM networks and the existent physical subnets such as Ethernet and token ring networks are the same. With the IPoA (IP over ATM), users can directly run the existent IP-based network protocols and applications on an ATM network. The NetEngine core router supports the IPoA based on PVC (Permanent Virtual Circuit).

On a GSR, the physical layer of an ATM interface is implemented based on SDH, so the configuration of the ATM interface includes the configuration of the SDH layer parameters.

This chapter introduces the management functions of ATM interfaces, including interface configuration, PVC configuration and parameter query and performance statistics.

ATM interface management can be performed by any of the following means:

1) Function tree

The function menu of ATM interface management is shown in the following figure:

Figure 17-1 Function menu of ATM interface management

Select an ATM interface from the device panel and double-click on different nodes on the function tree, and you can configure various functions of the ATM interface.

2) Device menu


17-2

Select an ATM interface from the device panel and right click on it to access the short-cut menu of interface level, as shown in Figure 17-2. Select various sub-items of [ATM Interface Management], and you can configure the related ATM interface functions.

Figure 17-2 Device menu of ATM interface

The two operations function the same, and this chapter takes the function tree operation as an example.

Caution:

Before performing any interface-related operation (such as configuration, query and statistics), you must select an interface first.

17.2 Interface Configuration

Select an ATM interface from the device panel, double-click on [ATM Interface Management/Interface Configuration] node on the function tree to open the "Interface Configuration" window, as shown in Figure 17-3.


17-3

Figure 17-3 ATM Interface Configuration (Interface Maintenance)

This interface includes two tabbed pages, Interface Maintenance and SDH Parameter Configuration.

17.2.1 Interface Maintenance

ATM interface supports subinterface. The interface maintenance page implements ATM subinterface adding and deletion, ATM interface reset, ATM interface disabling and interface parameter configuration.

The interface maintenance page shows the currently selected main interface and all its subinterfaces, each of which occupies a line. Various parameters are described in Table 17-1.

Table 17-1 Interface maintenance parameters

Name Description


Administration Status Administration status of the interface, including up and down, read-write

Operation Status Operation status of the interface, including up and down, read-only

Max VCC Integer, read-only

Current VCC Integer, read-only

Max VPI Bit Ranges from 0 to 7, read-write

Max VCI Bit Integer, read-only


17-4

Name Description

Current Max VPI Bit Integer, read-only

Current Max VCI Bit Integer, read-only

I. Adding an ATM subinterface

In Figure 17-3, click <Add…> to open the "Add Subport" window, as shown in Figure 17-4. Here type the subinterface number and click <OK> to add an ATM subinterface.

Figure 17-4 Adding an ATM subinterface

II. Deleting an ATM subinterface

In Figure 17-3, select one or more lines on your demand and click <Delete> to delete the subinterfaces.

III. Resetting an interface

In Figure 17-3, select one or more lines on your demand and click <Active> to set the administration status of the selected interfaces to up.

IV. Disabling an interface

In Figure 17-3, select one or more lines on your demand and click <Deactive> to set the administration status of the selected interfaces to down.

V. Configuring interface parameters

In Figure 17-3, select a line and click <Config…> to open the "Interface Parameter Configuration" window, as shown in Figure 17-5. Here only the "MAX VPI Bit" entry is configurable. Modify the entry and click <OK> to finish the operation.


17-5

Figure 17-5 Interface Parameter Configuration

Note:

To configure "MAX VPI Bit" successfully, make sure that none of the interfaces is configured with PVC and all the configured interfaces are down.

17.2.2 SDH Parameter Configuration

The SDH parameter configuration page implements SDH parameter configuration, as shown in Figure 17-6.


17-6

Figure 17-6 ATM Interface Configuration (SDH Parameter Configuration)

Various parameters are described in Table 17-2.

Table 17-2 Parameters of SDH parameter configuration

Name Description


Medium Type Type of medium, including Sonet and SDH, read-write

Transfer Model Type of the remote device, including Sonet and SDH, read-write

J0

It is used by the receiving end to check the connectivity with the sending end. It is a number ranging from 0 to 255 when the transfer model is set to "Sonet", and is a string including 1 to 15 characters when the transfer model is set to "SDH". Read-write

LoopBack For loopback test, NoLoop (no loopback), FacilityLoop (internal loopback) and TerminalLoop (remote loopback), read-write

Clock Source Synchronous timing parameter, including master (internal clock) and slave (line recovery clock), read-write

Scramble Sets whether to enable scramble, including Scramble (enable) and UnScramble (disable), read-write

C2 Sets the property of VC frame multiplexing structure and payload information, ranging from 0 to 255, read-write

J1 It is a string including 1 to 15 characters and is used to check the connectivity between the receiving and sending ends on the path layer. Read-write


17-7

17.3 PVC Management

Select an ATM interface from the device panel and double-click on [ATM Interface Management/PVC Management] node on the function tree to open the "PVC Management" window, as shown in Figure 17-7.

Figure 17-7 PVC Management (PVC Configuration)

The "Port Selection" list on the left lists the currently selected main interface and its subinterfaces, and the right page shows the related PVC information. Select different interfaces from the "Port Selection" list, and the tabbed pages on the right are refreshed automatically.

The PVC management window includes such two tabbed pages as PVC Configuration and OAM Test Configuration.

17.3.1 PVC Configuration

You can configure PVCs on an ATM main interface and its subinterfaces. PVC configuration implements PVC adding, deletion, enabling, disabling, parameter configuration and performance statistics.

Various parameters in the page are described in Table 17-3.

Table 17-3 PVC configuration parameters

Name Description

Link VPI VPI of current PVC, ranging from 0 to 255, read-only

Link VCI

VCI of current PVC. The value of this parameter depends on the VCI bits configured on the interface. For example, if the VCI is 5bit long, this value ranges from 0 to 31. In addition, this item should not be set to 3 or 4, and VPI and VCI cannot be 0 at a time. Read-only


17-8

Name Description


Administration status of the PVC, including up and down, read-write

Operation Status Operation status of the PVC, including up and down, read-only

AAL Type AAL5, read-only

AAL5 Encaps Type Includes AAL5_SNAP and AAL5_MUX_IP, read-write

Service Category

Includes CBR, UBR and NRT-VBR. If it is set to "CBR", only the PCR is effective; if it is set to "UBR", none of the following three items is effective; if it is set to "NRT-VBR, the following three items are effective. read-write

PCR(kbps) Ranges from 100 to 149760 and is no less than the minimum cell rate, read-write

SCR(kbps) Ranges from 100 to 149760, read-write

MBS Ranges from 1 to 255, read-write

TransSDU Size Integer, read-only

RedvSDU Size Integer, read-only

I. Adding a PVC

In Figure 17-7, click <Add…> to open the "Add PVC" window, as shown in Figure 17-8. Here type the required PVC parameters and click <OK> to add a PVC.


17-9

Figure 17-8 Adding a PVC

II. Deleting a PVC

In Figure 17-7, select one or more lines on your demand and click <Delete> to delete the selected PVCs.

Note:

You cannot delete an enabled PVC, so make sure that the administration status of the PVC to be deleted is down.

III. Enabling a PVC

In Figure 17-7, select one or more lines on your demand and click <Enable> to set the administration status of the selected PVCs to up.


17-10

IV. Disabling a PVC

In Figure 17-7, select one or more lines on your demand and click <Disable> to set the administration status of the selected PVCs to down.

V. Configuring PVC parameters

In Figure 17-7, select a line and click <Config…> to open the "PVC Configuration" window, as shown in Figure 17-9. Here modify the related parameters and click <OK> to finish the operation.

Figure 17-9 PVC Configuration

Note:

You cannot configure the parameters of an enabled PVC, so make sure that the administration status of the PVC is down before configuration.


17-11

VI. Performance statistics

In Figure 17-7, select a line and click <Monitor…> to open the performance statistics window of the PVC, as shown in Figure 17-10.

Figure 17-10 Performance statistics

There three PVC performance statistics items, InArp Statistics Item, OAM Statistics Item and AAL5 Statistics Item.

Various items are described in Table 17-4, Table 17-5 and Table 17-6.

Table 17-4 InArp statistics item

Name Description

Received InArp requests/s The number of request packets received in a time unit

Sent InArp requests/s The number of request packets sent in a time unit

Received InArp replies/s The number of response packets received in a time unit

Sent InArp replies/s The number of response packets sent in a time unit

Received Invalid InArp requests/s

The number of invalid requests received in a time unit

Sent Invalid InArp requests/s The number of invalid requests sent in a time unit


17-12

Table 17-5 OAM statistics item

Name Description

Received End to End F5 OAM Loop Cells/s

The number of end-to-end F5OAM loopback cells received in a time unit

Sent End to End F5 OAM Loop Cells/s

The number of end-to-end F5OAM loopback cells sent in a time unit

Received F5 AIS Cells/s The number of F5AIS cells received in a time unit

Sent F5 AIS Cells/s The number of F5AIS cells sent in a time unit

Received RDI Cells/s The number of RDI cells received in a time unit

Sent RDI Cells/s The number of RDI cells sent in a time unit

Table 17-6 AAL5 statistics item

Name Description

AAL5CRC Errors/s The number of AAL5CRC errors encountered in a time unit

For the detailed operation of the window, refer to Chapter 5 “Performance Monitoring”.

17.3.2 OAM Test Configuration

OAM test is used to enable the sending of the OAM F5 Loopback cells so as to check the status of a PVC. OAM test configuration configures the OAM test attributes of a PVC.

Figure 17-11 PVC Management (OAM Test Configuration)



17-13

Table 17-7 Configuration parameters of OAM test

Name Description

Link VPI VPI of current PVC, ranging from 0 to 255, read-only

Link VCI

VCI of current PVC. The value of this parameter depends on the VCI bits configured on the interface. For example, if the VCI is 5bit long, this value ranges from 0 to 31. In addition, this item should not be set to 3 or 4, and VPI and VCI cannot be 0 at a time. Read-only

Test Status Includes enable and disable, read-write

Link Status Includes up and down, read-only

OamFrequency(s) Ranges from 1 second to 600 seconds, read-write


For the detailed operation, refer to SDH Interface Query in POS Interface Management.

17.5 SDH Path Query

For the detailed operation, refer to SDH Path Query in POS Interface Management.

User Manual Volume I Quidview Device Manager Chapter 18 Portal Configuration

18-1

Chapter 18 Portal Configuration

18.1 Portal Protocol Overview

Portal service is a value-added service based on the existent Internet services. It provides users with individual services, better QoS assurance and higher network security. The NE16E/08E/05 router, jointly with a NAS (Network Access Server) and iTELLIN, provides narrowband Portal service for users.

With the Portal service, a login user can only access the contents on the specified site server through which the operator provides various kinds of information and services for the users and decides whether to enable them to access the external network resources according to the authentication and service selection results.

In a narrowband Portal solution, a NE16E/08E/05 router resides in the middle of a NAS, a content server (Portal Server) provided by the ICP and the other sites the users are authorized to access.

Figure 18-1 Location of NE16E/08E/05 on a network

The NE16E/08E/05 router is engaged in controlling the access rights of the Portal users.

When a Portal user dials on the NAS, the NAS may communicate with the NE16E/08E/05 router in two modes. In the first mode, the NAS is A8010 that sends a Portal user login message to the NE16E/08E/05 router. Upon receiving the message, the latter reassembles it and sends the packet to the iTELLIN. In the other mode, the NAS is not A8010 but a third-party access server, and the NE16E/08E/05 router will check whether the login user is a Portal user. If it is, the router will send a Portal user login message to the iTELLIN. Otherwise, the router will forward the packet according to common procedure.


18-2

When receiving the HTTP packets of a Portal user, if not being informed by the iTELLIN that the user can access any other site, the NE16E/08E/05 router will redistribute the packets to the Portal Server.

When the iTELLIN allows the user to access the other sites, it informs the NE16E/08E/05 router. After receiving the message, the NE16E/08E/05 router will no longer redistribute the packets of the user.

A user may log out initiatively or be forced to logout. After logout, the NE16E/08E/05 router will clear the related data items of the Portal user.

18.2 Portal Configuration

18.2.1 Portal Function List

Enable Portal Portal ID Configuration Address Pool Configuration NAS Configuration iTELLIN Server Key Configuration Browse Portal user information Browse Portal status information

18.2.2 Enabling Portal

The "Port Enable" interface is shown in Figure 18-2. When you enter the interface, all the ports supporting Portal function and their status will be displayed automatically. You can select a status for a port from the drop-down list and click <Config> to validate your configuration.


18-3

Figure 18-2 Enabling Portal

Only when an interface is set to "portal server" status, could it process the Portal-related packets from the Portal Server and iTELLIN. Likewise, only when an interface is set to "portal user" status, could it process the Portal-related packets from the NAS. Therefore, before launching the Portal service, you must set the related interface to a proper status for communication. The status of a Portal port is described in Table 18-1.

Table 18-1 Portal interface status

Status Description

disable portal Disables the Portal function on the interface

only enable portal server

Enables the interface to conduct Portal service communicate with the iTELLIN and the Portal Server

only enable portal user Enables the interface to conduct Portal service communicate with the NAS

enable both portal server and portal user

Enables the interface to conduct Portal service communicate with the NAS, iTELLIN and Portal Server simultaneously

By default, none of interfaces will process Portal-related packets.


18-4

18.2.3 Configuring Portal ID

Before launching a Portal service, you must configure the Portal ID and such attributes as the IP addresses of the iTELLIN and the Portal Server.

Portal ID configuration includes creation, deletion and configuration. The interface is shown in Figure 18-3.

Figure 18-3 Configuring Portal ID

This interface displays all the configured Portal IDs and their attributes.

I. Creating a Portal ID

Click <New…> to open the [Create Portal ID] dialog box, as shown in Figure 18-4.


18-5

Figure 18-4 Creating a Portal ID

Set various attributes and click <OK> to validate your configuration. If the settings are correct, the Portal ID will be set to "active" status automatically. Otherwise, the configuration will fail. The meaning of various attributes is described in Table 18-2.

Table 18-2 Portal ID attributes

Attribute Description

Portal ID The unique identifier of a Portal configuration, once configured, not editable

Portal ID Description A custom description of the Portal ID. If not specified, the system default value will be used.

Server IP Address The IP address of the Portal server

iTELLIN IP Address The IP address of the iTELLIN server

ITELLIN Timeout iTELLIN packet response timeout in second

ITELLIN Retry Times The times of retries on the iTELLIN when the communication with it fails

Hold Time Hole time in second


18-6


DestIPMaxcymometer Update frequency of the destination IP

ITELLIN Aging Time User update timeout on the iTELLIN. If a user is not updated for the specified time, it will log out automatically.

hwNBPortalEnableRedirect

Specifies whether to force a user to enter the Portal status after successful authentication, yes by default

Max Idle Time

The maximum idle time is not 0 and is effective for all the users logging in from a non-A8010 access server. If there is not packet received from a user for the specified time, the user will log out automatically.

Nas Secret Key The key used to communicate with the NAS

II. Deleting a Portal ID

Select a Portal ID and click <Delete> to delete it.

III. Configuring a Portal ID

Select a Portal ID and click <Config…> to enter the configuration dialog box that is similar to the creation dialog box.

18.2.4 Address Pool Configuration

As shown in Figure 18-5, address pool configuration includes creation, deletion and configuration. When you enter the interface, all the configured address pools are displayed automatically.

Figure 18-5 Address Pool Configuration


18-7

I. Creating an address pool

Click <New…> to open the "Create Address Pool" window, as shown in Figure 18-6:

Figure 18-6 Creating an address pool

Set various attributes and click <OK> to validate your configuration. The meaning of various attributes is described in Table 18-3.

Table 18-3 Address pool attributes


Portal ID Select a Portal ID from the existent ones

Pool Number Identifier of the address pool

First Address Start address of the address pool

Last Address End address of the address pool

II. Deleting an address pool

Select an existent address pool and click <Delete> to delete it.

III. Configuring an address pool

Select an existent address pool and click <Config…> to open the configuration dialog box that is similar to the creation dialog box.

18.2.5 NAS Configuration

The NAS configuration interface is shown in Figure 18-7.


18-8

Figure 18-7 NAS Configuration


Table 18-4 NAS configuration parameters


Nas TimeOut User update message timeout in second on the NAS. If there is no update message received from a user for the specified time, the user will log out automatically.

Nas Retry Times Times of retries on the NAS when the communication with it fails

Nas Aging Time NAS communication timeout

18.2.6 iTELLIN Key Configuration

The iTELLIN key management interface is shown in Figure 18-8.


18-9

Figure 18-8 iTELLIN Key Configuration

This interface lists all the iTELLIN server addresses specified when configuring the Portal ID. Select a line and click <Config…> to enter the configuration interface, as shown in Figure 18-9.

Figure 18-9 iTELLIN key configuration


Table 18-5 iTELLIN server configuration parameters


Server IP The IP address of the iTELLIN server

Key The key of the iTELLIN server


18-10

18.2.7 Browsing Portal User Information

The Portal user information browsing interface is shown in Figure 18-10.

Figure 18-10 Portal user information browsing


Table 18-6 User information


Portal ID The unique identifier of a Portal configuration

Registing User Number The number of registering users

UnRegisting User Number The number of users that are logging out

Holding User Number The number of users in holding status

Redirect User Number The number of users to be redirected

URL Filter User Number The number of users whose packets are to be filtered

Common User Number The number of users that can normally access the network and do not require redirection and packets filtering

18.2.8 Browsing Portal Status Information

The Portal status information browsing interface is shown in Figure 18-11:


18-11

Figure 18-11 Portal status information browsing


Table 18-7 Portal status information


User IP A valid IP address

User Status Current status of a user

User Nas IP NAS address of a user

User Portal ID Portal ID used by a user

User Type Narrowband user that is registered by the NAS Narrowband user that is automatically identified

User Online Time Online duration of a user

User Manual Volume I Quidview Device Manager Chapter 19 Voice Management

19-1

Chapter 19 Voice Management

Voice service is typically applied to IP phone. The application of the VOIP to routers makes it possible for voice services to be borne by IP networks, just like traditional telephone service. At present, an IP phone gateway is used in most cases to interwork between PSTN and Internet. At the same time, as the technology of voice transmission from PC to telephone, and from telephone to telephone is becoming mature and the voice quality is improved greatly, VOIP fully meets the requirement of commercial use. This chapter introduces configuration methods of Quidview Voice service.

Voice service is configured in the following two ways:

I. Function tree

Voice management function menus are shown in the following figure:

Figure 19-1 Voice Management Function Tree

Double-click the relevant node in the function tree to configure related functions of Voice service.


19-2

II. Device menu

Right click the device panel and a device menu will pop up as shown in the figure below. Select relevant menus to configure the functions related to Voice service.

Figure 19-2 Device Menu

The functions of these two operations are completely the same. This chapter takes the function tree operations as an example for illustration.

19.1 Voice Common Information

Double-click the function node [Voice Management/Voice Common Information] and the "Voice Common Information" configuration window will pop up as shown in the following figure:

Figure 19-3 "Voice Common Information" configuration window


19-3

The meaning of each parameter in the figure is shown in the table below:

Table 19-1 Description of parameters in “Voice Common Information”

Name Description

Call History Number As the longest history record, its value ranges from 0 to 500.

Match Policy Designate the diversified number match policy for a user’s dialing scheme and its value is optional: shortest, longest.

JitterBuffer Designate the length of buffer in an incoming voice packet, whose value range is 0~10.

Sending Voice Data Flow Mode Optional: normal, fast.

Receiving Voice Data Flow Mode Optional: normal, fast.

Select or modify the parameter in the figure, and click <Config> to finish configuration.

19.2 Voice Port Information

19.2.1 Analog Port Configuration

Double-click the function node [Voice Management/Voice Port Information] in the function tree and the "Voice Port Information" window as shown in the following figure will pop up:

Figure 19-4 Voice Port Information (Analog Port) configuration window


19-4

"Analog Port" tab in the figure is divided into the upper and lower parts. The upper part shows the list of analog voice ports on the device, which specifies several voice point parameters such as "Port No", "Type", "Description" and "Status".

The lower part is "Current Calling Information", which lists the ongoing call information about the selected port.

Select a line of data in the port list. Click <Config…>, and the "Voice Port Details" window will pop up. It is allowed to configure parameters related to voice ports in this window. Depending on different port types, the configuration interface differs. Analog voice port is of three types: FXS, FXO and E&M. Specific configuration parameters will be described below one by one.

I. FXS Port Configuration

Select a FXS port, click <Config…> and a configuration window as shown in the figure below will pop up:

Figure 19-5 FXS Port Details (Analog Port Attribute) configuration window

There are two tabs in the window: Analog Port Attribute and Common Information. Common Information tab is illustrated in the figure below:


19-5

Figure 19-6 FXS Port Details (Common Information) configuration window

The meaning of each parameter in the figure is given in the table below:

Table 19-2 Description of FXS port parameters

Name Description

Port Number As the sequence number of this port in the interface board, it is read-only.

Port Type It refers to port type: fxs, fxo or E&M. This parameter is read-only.

Port Description Descriptive character string for this port.

Port Status Two states are available: up, down; read-only.

Initial Timeout Used to set timeout time for port initialization, which ranges from 0 to 120s, 10s by default.

Analog Port Attribute

Interdigit Timeout

Used to set key timeout, which ranges from 0 to 120s, 10s by default.


19-6

Name Description

Enable Noise Whether to insert comfortable noise mode to disable auditory stimulation caused to users.

Input Gain Used to set the size of gain at the receiving end of voice interface, ranging from -14 to 14 dbs and 0 db by default.

Output Gain Used to set the size of gain at the transmitting end of voice interface, ranging from -14 to 14 dbs and 0 db by default.

Enable Echo Cancelled

Used to set whether to enable echo cancellation; enabled by default.

Echo Cancel Depth

Used to set echo cancellation depth of a voice port, Options: 16ms, 24ms, 32ms. The default value is 16ms. This parameter is valid only when echo cancellation is enabled,

Echo Cancel Delay

Used to set echo cancellation delay of a voice port, ranging from 0 to 64ms, and 32ms by default.

Private Line Number Used to specify private line number.

Common Information

Nation Used to specify the nation.

Modify the parameters to be configured, and then click <OK> to complete the port parameter configuration.

II. FXO Port Config5uration

If FXO port is selected, the configuration window as shown in the following figure will pop up:


19-7

Figure 19-7 FXS Port Details configuration window

As the tabs "Analog Port Attribute" and "Common" in the figure are common to analogy voice port and their parameters are also identical, no more detail will be given here.

The meanings of FXO port parameters are described in the table below:

Table 19-3 Description of FXO port parameters

Name Description

Area

Used to set busy tone type at FXO port. Options: Europe, custom, north-America; Europe by default. This item is configurable for the first FXO port of a voice card, and is read-only for the others.

DTMF Digit Duration

Used to set DTMF digit duration output from the voice port, it ranges from 50 to 500ms and is 120ms by default.

DTMF inter-digit Duration

Used to set the DTMF inter-digit duration output from the voice port, it ranges from 50 to 500ms and is 120ms by default.



19-8

III. E&M Port Configuration

If E&M port is selected, the configuration window as shown in the figure below will pop up:

Figure 19-8 Analog Port E&M Attribute configuration window

When you switch to the tab "Interface Timing Parameter", the configuration window is shown in the following figure:


19-9

Figure 19-9 Interface Timing Parameter configuration window

The meanings of parameters in the figure are given in the table below:


19-10

Table 19-4 Description of E&M port parameters

Name Description

E&M Signaling Type

Used to set the signaling type of E&M voice port, it has the following options: delay-dial (designate delay start mode in digital E&M signaling, immediate (designate immediate start mode in digital E&M signaling), wink-start (designate wink start mode in digital E&M signaling). The default value is "immediate".

Signal Operation

Used to set the type of line used by analog E&M signal, it has the following options: twoWires (one pair of receiving and sending wires), fourWires (two pairs of receiving and sending wires). The default value is fourWires.

Type Used to specify the type of trunk used in analog E&M signals, it has the following options: typeI, typeII, typeIII, typeV. The default value is typeV.

Ringing no answer Timeout

Used to decide whether to time out in case of ringing no answer from E&M voice port.

Timeout Used to specify timeout for ringing no answer from analog E&M voice port, it ranges from 5 to 600s, and is 60s by default.

Wait Cancelled Number Timeout

Used to decide whether to time out when analog E&M voice port is waiting for called number.

Analog Port E&M Attribute

Timeout Used to specify the timeout value for analog E&M voice port waiting called number, its value ranges from 3 to 600s and is 5s by default.


19-11

Name Description

DTMF Digit Duration

Used to set DTMF digit duration output from the voice port, it ranges from 50 to 500ms and is 120ms by default.

DTMF Inter-digit Duration

Used to set DTMF inter-digit duration output from the voice port, it ranges from 50 to 500ms and is 120ms by default.

Time of Cleaning Call

Used to set time interval of clearing call, it ranges from 200 to 2000ms; 200ms by default.

Waiting Time Before Sending Wink Signal

Used to set the waiting time before the called sends wind signal, it ranges from 100 to 5000ms; 500ms by default. This parameter is valid only when "E&M start type" is set as "wink-start".

Max Time To Wait For Wink Signal

Used to set the timeout value for the caller to wait for wink signal, it ranges from 100 to 5000ms; 2000ms by default. This parameter is valid only when "E&M start type" is set as "wink-start".

Max Wink Duration

Used to set the wink delay, this parameter ranges from 100 to 3000ms; 500ms by default. This parameter is valid only when "E&M start type" is set as "wink-start".

Timing of Generation of Delay Start Signal

Used to set timing of generation of delay start signal, this parameter ranges from 20 to 2000ms; 300ms by default. This parameter is valid only when "E&M start type" is set as "delay-dial".

Max Delay Signal Duration

Used to set the maximum delay signal duration, it ranges from 100 to 5000ms; 300ms by default. This parameter is valid only when "E&M start type" is set as "delay-dial".

Interface Timing Parameter

Delay Before Sending Out Called Digit

Used to set the delay before sending out the called number, it ranges from 50 to 5000ms; 300ms by default. This parameter is valid only when "E&M start type" is set as "immediate".


19.2.2 Digital Port Configuration

Choose "Digital Port" tab from the "Voice Port Information" configuration window as shown in Figure 19-4, and the configuration window shown in the following figure will pop up:


19-12

Figure 19-10 Voice Port Information (Digital Port) configuration window

The "Digital Port" tab in the figure consists of the upper part and lower part. The upper part shows the list of digital voice ports, which specifies the values of several voice port parameters including "Port No", "Group No", "Board Type", "Signaling Type", "Port Description" and "Port Status".

The lower part is "Current TimeSlot Calling Information", which lists the time slot status of current port.

Select a line of data in the port list. Click <Config…>, and the "Voice Port Details" window will pop up. You may configure the parameters related to the voice port in this window. Depending on different port types, the configuration windows differ from each other. The digit port is of three signaling types in all: R2, E&M and DSS1, as described below.

I. R2 Port Configuration

If the device is configured with R2 type, a configuration window as shown in the figure below will pop up:


19-13

Figure 19-11 R2 Digital Port Details (Digital Port Attribute) configuration window

As the parameters under the "Common" tab in the figure are identical to those in the voice port, no more detail will be given here.

The meanings of Digital Port Attribute parameters are given in the table below:

Table 19-5 Description of Digital Port Attribute parameters

Name Description

Port Number As the sequence number of this port in the interface board, it is read-only.

Group Number As ds0 or pri group number, it ranges from 0 to 30, and is read-only.

Port Type The port is of two types: e1vi and t1vi. This parameter is read-only.

Signal Type There are three types of port signaling: r2, dss1 and E&M. This parameter is read-only.

Port Description Descriptive character string for this port.

Port Status Two states are available: up, down; this parameter is read-only .


19-14

When you switch to the "R2 Signal Information" tab, the configuration window is shown in the following figure:

Figure 19-12 R2 Digital Port Details (R2 Signal Information)configuration window

The meanings of R2 signaling information parameters are shown in the following table:

Table 19-6 Description of R2 digit port parameters

Name Description

Number of Bits Needed

Used to specify the number of bits required for calling number, this parameter ranges from 1 to 10; 1 by default.

Line Signal Effect Time

Used to set the line signaling effect time, this parameter ranges from 10 to 40ms; 40ms by default.

KA Signal Encode Used to set KA signal code, this parameter ranges from 1 to 15; 1 by default.

KD Signal Encode Used to set KD signal code, this parameter ranges from 1 to 15; 3 by default.

Waiting Time of Sending Holding Confirm Signal

Used to set waiting time of sending holding confirmation signal, this parameter ranges from 200 to 3000ms; 1000ms by default.

R2 Relay Route Mode

Used to set R2 relay routing mode, this parameter has several options: max, maxpoll, min and minpoll; min by default.


19-15

Name Description

Timeout of Waiting Receive KB Signal

Used to set the timeout of waiting to receive KB signal, this parameter ranges from 1000 to 50000ms; 5000ms by default.

Timeout of Waiting Receive KD Signal

Used to set the timeout of waiting to receive KD signal, this parameter ranges from 1000 to 50000ms; 5000ms by default.

Timeout of Waiting Next Calling Number

Used to set the timeout of waiting for next called number, this parameter ranges from 1000 to 50000ms; 5000ms by default.

Timeout of Waiting Releasing Monitor

Used to set the timeout value of waiting to release monitoring, this parameter ranges from 200 to 3000ms; 1000ms by default.

Waiting Time of End of Ringing

Used to set the time of waiting for the end of ringing, this parameter ranges from 1000 to 240000ms; 30000ms by default.

Interval of Waiting Sending Response Signal

Used to set the interval of waiting to send response, this parameter ranges from 50 to 1000ms; 500ms by default.

Line Signal Reverse Mode

Used to set whether to reverse signal, each bit can be any of the two possible values: 0 (disable) and 1 (enable); 0000 by default (i.e. all four bits are set to "disable").

Value of C,D Signal Used to set the signal bit, which needs to be sent but is not sent yet; 1111 by default.


II. E&M Port Configuration

If a device is configured with E&M type, the configuration window as shown in the figure below will pop up:


19-16

Figure 19-13 E&M Digital Port Details (E&M Attribute) configuration window

The parameters under the tab "Interface Timing Parameter" are identical to relevant attributes of E&M port. For details, see Table 19-4.

The meanings of E&M attribute parameters are given in the table below:

Table 19-7 Description of Digital E&M Port parameters

Name Description

Interdigit Timeout Used to set the inter-digit timeout, this parameter ranges from 0 to 120ms;10ms by default.

Ringing no answer Timeout Used to set whether to time out when ringing gets no answer.

Timeout Used to set the timeout value of "ringing no answer", this parameter ranges from 5 to 600s; 60s by default.

Wait Cancelled Number Timeout

Used to set whether to time out while waiting for called number.

Timeout Used to set the timeout value of waiting for the called number, this parameter ranges from 3 to 600s; 5s by default.

ABCD Bit Value of Receiving Idle Signaling

Used to set ABCD bit value of receiving idle signaling, each bit of this parameter can be two possible values: 0 (disable) and 1 (enable); 1101 by default.


19-17

Name Description

ABCD Bit Value of Receiving Busy Signaling

Used to set ABCD bit value of receiving busy signaling, each bit of this parameter can be two possible values: 0 (disable) and 1 (enable); 0101 by default.

ABCD Bit Value of Sending Idle Signaling

Used to set ABCD bit value of sending idle signaling, each bit of this parameter can be two possible values: 0 (disable) and 1 (enable); 1101 by default.

ABCD Bit Value of Sending Busy Signaling

Used to set ABCD bit value of sending busy signaling, each bit of this parameter can be two possible values: 0 (disable) and 1 (enable); 0101 by default.


III. DSS1 Port Configuration

If the device is configured with DSS1 type, the configuration window only contains two tabs: "Digital Port Attribute" and "Common". Please refer to Table 19-2 and Table 19-5 for the meanings of their parameters.

19.3 Voice Entity Information

Double-click the function node [Voice Management/Voice Entity Information] in the function tree, and the "Voice Entity Information" configuration window will pop up, as shown in the following figure:

Figure 19-14 Voice Entity Information (POTS) configuration window


19-18

This window contains two tabs: "POTS Voice Entity" and "VOIP Voice Entity", which will be described in detail one by one as follows.

19.3.1 POTS Voice Entity Configuration

POTS refers to ordinary pone service. To configure POTS voice entity is to relate physical voice port with local telephone equipment.

I. Adding voice entity

Click <Add…> in Figure 19-14, and the [Add a Voice Entity] dialog will pop up, as shown in the figure below:

Figure 19-15 "Add POTS Voice Entity (Common)" window

The figure lists basic information required for POTS voice entity to be added. The meanings of the parameters in the figure are shown in the table below:

Table 19-8 Description of POTS Voice Entity (Common) parameters

Name Description

Voice Entity ID

As the unique expression of the set entity, its value range is 1~231-1.

Telephone Number This parameter indicates the telephone number of local entity.


19-19

Name Description

Prefix Used to set dialing prefix, which can either be any digit of the numbers from 0 to 9 or ",".

Voice Port Voice port on the device.

Cancel Truncate Used to set whether to disable truncating the called number.

When you switch to the [Advanced] and [IP FAX] tabs, the configuration dialog box is illustrated in the following two figures. For parameter meanings, please refer to Table 19-9 and Table 19-10.

Figure 19-16 Add POTS Voice Entity (Advanced) window


19-20

Figure 19-17 Add POTS Voice Entity (IP FAX) window

Table 19-9 Description of POTS Voice Entity (Advanced) parameters

Name Description

Shutdown Used to set whether to disable this entity.

Voice Activity Detect Used to set whether to enable mute compression.

IP Precedence Used to set IP packet parameters, this parameter ranges from 0 to 7; 0 by default.

DTMF Relay Used to specify DTMF transmission mode, this parameter can be either voice or h245Alphanumeric; voice by default.

Encode/Decode Type

Used to specify the encode/decode mode, the value of this parameter can be any of the following: G.711 A Law 64000 bps,G.711 U Law 64000 bps,G.723.1 5300bps,G.723.1 6300bps,G.729 8000bps,G.729 A and Default; Default by default.


19-21

Table 19-10 Description of POTS Voice Entity (IP FAX) parameters

Name Description

Fax Rate Used to specify the fax rate, the value of this parameter is optional: r14400, r2400, r4800, r9600, disable and voice; voice by default.

Train Mode Used to set fax training mode for the dialing terminal, the value of this parameter can either be ppp or local; ppp by default.

Local Train Threshold

Used to specify local training threshold, the parameter ranges from 0 to 100; 10 by default.

Fax Level Used to set the transmitting energy level of gateway carrier wave, its value ranges from 3 to 60db; 15db by default.

Fax Relay(ECM) Used to set whether to use ECM in fax.

Send Nsf Used to set whether to enable nonstandard capacity.

Fax Protocol Used to set supported fax protocols, the value of this parameter can be any of the followings: Nonstandard-compatible,T38, and its default value is T38.

High Speed Redundancy

Used to specify the number of T38 high speed redundancy packets, its value ranges from 0 to 2; 0 by default.

Low Speed Redundancy

Used to set the number of T38 low speed redundancy packets, its value ranges from 2 to 5; 0 by default.

Support Mode

Used to set the mode of interworking with other devices, the value of this parameter can either be rtp or vt; rtp by default.

Fill in or choose relevant parameter values in the three tabs, and click <OK> to complete POTS voice entity operation.

II. Deleting POTS voice entity

Choose a line of data from Figure 19-14, and click <Delete> to delete POTS voice entity upon confirmation.

III. Configuring POTS voice entity

Select a line of data from Figure 19-14 and click <Config…>. The [Config Voice Entity] dialog box will pop up, which is similar to the [Add a Voice Entity] dialog box. For the parameter meanings, please refer to Table 19-8, Table 19-9 and Table 19-10

Modify the relevant parameters, and then click <OK> to complete the POTS voice entity configuration.

19.3.2 VOIP Voice Entity Configuration

When you switch to the [VOIP Voice Entity] tab, the configuration window is shown in the following figure:


19-22

Figure 19-18 Voice Entity Information (VOIP) configuration window

To configure VOIP voice entity is to relate telephone numbers with IP addresses.

I. Adding VOIP voice entity

Click <Add…> in Figure 19-18 to pop up the [Add a Voice Entity] dialog box, as shown in the figure below:


19-23

Figure 19-19 Add VOIP Voice Entity (Common) window

The figure lists the basic information required for the VOIP voice entity to be added. The parameter meanings are given in the following table:

Table 19-11 Description of VOIP Voice Entity (Common) parameters

Name Description

Voice Entity ID

As the unique expression of the set entity, its value range is 1~231-1.

Telephone Number Used to indicate remote telephone numbers.

Technology Prefix

Used to technology prefix, the value of this parameter can either be any of the numbers 0 to 9 or "#".

Session Target

Used to set routing type, the value of this parameter can be any of the following: IPV4,RAS and Unknown; Unknown by default.

Fast Connect Used to set whether to enable fast connection.

Tunnel Used to set whether to enable tunnel, which is valid only when fast connection is enabled.


19-24

The [Advanced] and [IP FAX] tabs are totally the same as POTS voice entity. For relevant parameter meanings, please refer to Table 19-9 and Table 19-10.

Fill in or choose relevant parameter values in the three tabs, and click <OK> to add POTS voice entity.

II. Deleting VOIP voice entity

Choose a line of data from Figure 19-18, and click <Delete> to delete POTS voice entity upon confirmation.

III. Configuring VOIP voice entity

Select a line of data from Figure 19-14 and click <Config…>. The [Config Voice Entity] dialog will pop up, which is similar to the [Add a Voice Entity] dialog box. For the parameter meanings, please see Table 19-9, Table 19-10 and Table 19-11.

Modify the relevant parameters, and then click <OK> to complete the POTS voice entity configuration.

19.4 Voice AAA Information

Double-click the function code [Voice Management/Voice AAA Information] in the function tree, and the [Voice AAA Information] dialog box will pop up, as shown in Figure 19-20

Figure 19-20 Voice AAA Information (AAA Attribute)

19.4.1 AAA Attribute Configuration

AAA Attribute Configuration window is shown in Figure 19-20 with the meaning of its parameters in the following table:


19-25

Table 19-12 Description of AAA att7ribute

Name Description

AAA Enable Used to set whether to enable AAA function.

Client Type

Used to set client type, the value of this parameter can be any of the followings: huawei, nonstandard-compatible-vsa, nonstandard-compatible-overload and ietf-rfc; huawei by default.

Enable VoIP Authentication

Used to set whether to enable one-stage dialing voice authentication.

Enable VoIP Authorization

Used to set whether to enable one-stage dialing voice authorization. Valid only when VoIP Authentication is enabled

Enable VoIP Accounting Used to whether to enable voice accounting.

AAA information configured here is all related to voice function. Modify the parameter to be configured, and click <Config> to complete AAA attribute configuration.

19.4.2 Local User Configuration

When you switch to the [Local User] tab, the configuration dialog box is shown in Figure 19-21

Figure 19-21 "Voice AAA Information (Local User)" configuration window

The above configuration window lists the information about configured local users. The three buttons at the bottom of this window <Add…>, <Delete> and <Modify Password...> are used for relevant configurations.


19-26

I. Adding a user

Click <Add…> and enter the username and password to be added in the popup "Add a Local User" window. Click <OK> in the window to add the user.

II. Deleting a user

Select a line of data in Figure 19-21. Click <Delete> to delete the user upon confirmation.

III. Changing user password

Select a line of data in Figure 19-21. Click <Modify Password…>, and enter a new password in the popup window "Modify User Password". Click <OK> to modify the user password.

19.4.3 Access Number Configuration

When you switch to the [Access Number] tab, the configuration window is shown in the following figure:

Figure 19-22 Voice AAA Information (Access Number)

The above configuration window lists the information about configured access numbers. The three buttons <Add…>, <Delete> and <Modify Password...> at the bottom of this window are used for relevant configurations.

I. Adding an access number

Click <Add…> to pop up the [Add a access number] dialog box, as shown in the figure below:


19-27

Figure 19-23 Add Access Number window

The meanings of parameters in the window are given in the table below:

Table 19-13 Description of Access Number parameters

Name Description

Access Number Used to set access number for AAA client, this parameter can be any character from 0 to 9.

Dial-two Authentication Used to set whether to enable dial-two voice authentication.

Dial-two Authorization

Used to set whether to enable dial-two voice authorization. When dial-two voice authentication is not enabled, this option cannot be started either.

Dial-two Process

Used to choose dial-two process, the value of this parameter can be either Card Number or Caller Number; Card Number by default.

Card Digit Used to set the number of card digits, this parameter ranges from 1 to 31; 12 by default. This option is valid only when "Card Number" is selected.

Password Digit Used to set the number of password digits, the value range of this parameter is 1~16; 6 by default. This option is valid only when "Card Number" is selected.

Redial Times Used to specify redialing times, the value of this parameter ranges from 1 to 10; 3 by default. This option is valid only when "Card Number" is selected.


19-28

Fill in or select relevant parameter values, and then click <OK> to add the access number.

II. Deleting an access number

Select a line of data in Figure 19-22. Click <Delete> to delete the access number upon configuration.

III. Configuring access number

Select a line of data in Figure 19-22. Click <Config…>, and modify the relevant parameters in the popup "Config access number" window (all parameters except the access number can be modified). Click <OK> to finish configuring the access number.

19.5 GK Client Information

GateKeeper (GK) is a H.323 entity, which provides functions like address translation, access grant, bandwidth control and management, area management, security check, call control signaling and call management to LAN or WAN H.323 terminal, GW or some multipoint control units (MCU). Sometimes, it also provides functions such as route control and charging. For the calls in a GK-managed area, GK not only controls call service but also serves as a central control point.

Depending on the composition of an entity that implements all GK functions, there are Client and Server. Normally, GK Client entity takes a router as its hardware carrier, so that GK Server can provide services such as address translation, access grant, bandwidth management and management of router’s IP voice gateway to the router’s IP voice gateway by interacting with GK Server via RAS (Registration Admission and Status) message. At present, H3C series routers only provide GK Client functions.

Double-click the [Voice Management/GK Client Information] node on the function tree, and the [GK Client Information] dialog box will pop up, as shown in the figure below:


19-29

Figure 19-24 GK Client Information configuration window

The meanings of parameters in the figure are given in the table below:

Table 19-14 Description of GK Client parameters

Name Description

GK Client Status Used to set whether to enable GK, the value of this parameter can either be Enable or Disable; Disable by default.

Interface Used to set a gateway interface used to connect GK.

IP Address Used to display the interface IP address

Gateway ID Used to set gateway ID.

Gateway

Technology Prefix

Used to set technology prefix of the gateway, the value of this parameter can be a character within the range of 0~9, #,; with this technology prefix, GK identifies gateway types. A gateway can be configured with 30 prefixes, separated by ";". The prefix may contain a maximum of 31 characters.


19-30

Name Description

Gatekeeper ID Used to set GK’s ID.

IP Address Used to set IP address of GK. Gatekeeper

TCP Port Used to set GK’s port number.

Modify the parameters to be configured, and then click <Config> to complete GK Client configuration.

19.6 Voice Call Information

Voice Call Information lists the current information and history information relating to the ongoing call.

Double-click the [Voice Management/Voice Call Information] node on the function tree, and the [Voice Call Information] dialog box will pop up, as shown in Figure 19-25.

Figure 19-25 Voice Call Information (Active Calling Information

Choose a line of data from the figure. Click <Detail…>, and the [Active Calling Details] dialog box will pop up, as shown in Figure 19-26.


19-31

Figure 19-26 Active Calling Details dialog box

When you switch to the [Call History Information] tab, the dialog box is shown in Figure 19-27.


19-32

Figure 19-27 Voice Call Information (Call History Information) dialog box

Choose a line of data from the figure. Click <Detail…>, the [Call History Details] dialog box will pop up, as shown in Figure 19-28.

Figure 19-28 Call History Details (Common Information) dialog box


19-33

The [Call History Details] dialog box contains three tabs: "Common Information", "VOIP Information" and "PSTN Information". When you switch to the last two tabs, a window will appear, as shown in the following figure:

Figure 19-29 Call History Details (VOIP Information) window

Figure 19-30 Call History Details (PSTN Information) window


19-34

19.7 H.323 Call Statistics

This function is used to count IPP H225 messages, IPP H245 messages and IPP RAS contained in H.323 calls in real time.

Double-click the function node [Voice Management/H.323 Call Statistics] in the function tree, and the "H.323 Call Statistics" window will pop up, as shown in the following figure:

Figure 19-31 H.323 Call Statistics window

The buttons on the left side are <Select Items>, <Bar>, <Plot>, <Exporting Data>, <Importing Data>, <Properties> respectively from top down.

I. Selecting monitor item

Click <Select Items>, and the "Select Monitor Item" window will pop up, as shown in the following figure:


19-35

Figure 19-32 Select Monitor Item window

As shown in the above figure, choose a message group from the "Group" drop box, and then choose the item to be monitored from the list of monitor items. Click <OK> and return to the "H.323 Call Statistics" window to see data curves, which vary with time, and the corresponding legend lists.

The monitor items available for choice are shown in the following table:


19-36

Table 19-15 List of H.323 Call Statistics monitor items

Monitor item group Monitor item

Sent Setups

Sent CallProceedings

Sent Alertings

Sent Connects

Sent ReleaseCompletes

Sent FacilityUserInputs

Sent FacilityTCSRequests

Sent FacilityTCSAcks

Sent FacilityTCSRejects

Sent FacilityOLCRequests

Sent FacilityOLCAcks

Sent FacilityOLCRejects

Sent FacilityMSDRequests

Sent FacilityMSDAcks

Sent FacilityMSDRejects

Sent FacilityCLCRequests

Sent FacilityCLCAcks

Sent FacilityStartH245s

Sent ErrorH225Msgs

Received Setups

Received CallProceedings

Received Alertings

Received Connects

Received ReleaseCompletes

Received Progresses

Received FacilityTCSRequests

Received FacilityTCSAcks

Received FacilityTCSRejects

Received FacilityOLCRequersts

Received FacilityOLCAcks

H225 Statistics

Received FacilityOLCRejects


19-37


Received FacilityMSDRequests

Received FacilityMSDAcks

Received FacilityMSDRejects

Received FacilityCLCRequests

Received FacilityCLCAcks

Received UnknownH225Msgs

Sent TCSRequests

Sent TCSAcks

Sent TCSRejects

Sent MSDRequests

Sent MSDAcks

Sent MSDRejects

Sent OLCRequests

Sent OLCAcks

Sent OLCRejects

Sent CLCRequests

Sent CLCAcks

Sent UserInputs

Sent ErrorH245Msgs

Received TCSRequests

Received TCSAcks

Received TCSRejects

Received MSDRequests

Received MSDAcks

Received MSDRejects

Received OLCRequests

Received OLCAcks

Received OLCRejects

Received CLCRequests

Received CLCAcks

Received UserInputs

H245 Statistics

Received UnknownH245Msgs


19-38


Sent GRQs

Sent RRQs

Sent ARQs

Sent BRQs

Sent DRQs

Sent URQs

Sent UCFs

Sent IRRs

Sent ErrorRASMsgs

Received GCFS

Received RCFS

Received ACFS

Received BCFS

Received DCFS

Received GRJS

Received RRJS

Received ARJS

Received BRJS

Received DRJS

Received URJS

Received UCFs

Received URJs

Received IRQs

RAS Statistics

Received UnknownRASMsgs

II. Graphical display switching

Click the buttons <Bar> and <Plot> to switch the graphical display. By default, the graphical display mode is "Plot".

III. Data export and import

Statistical data can be exported as disk files, while exported data files can be imported, shown in the form of graphics. Click <Exporting Data> or <Importing Data> to export or import data.


19-39

IV. Modifying real-time statistics properties

Click <Properties>, and select the values of parameters to be modified "Interval" and "Max Samples" in the pop up "Properties" window. Click <OK> to modify properties.

User Manual Volume I Quidview Device Manager Chapter 20 POS Access Management

20-1

Chapter 20 POS Access Management

POS (Point of Sale) refers to the card-punching service, which is widely used in such places as supermarket and gas station. This service is used to access POS terminals (at supermarkets, gas stations etc.) to a bank’s card accounting system, so that the user can pay for goods or service through his/her bank card.

As the society gets more and more information-oriented, POS terminal equipment is widely used in the sectors ranging from business, finance to tax, and developed rapidly. Earlier POS terminal equipment was unique to each bank, so a card of one bank cannot be used on POS terminals of other banks. The access service technology based on shared POS has solved this problem effectively, so that several types of bank cards can be used on the same POS. Based on a powerful processing platform equipped with professional router, Huawei’s POS access solution provides a series of IP solutions, featuring high density, manageability and maintainability with multiple access modes and multiple applications/hosts. Such POS supports dialup access, RS232 point-to-point access, and master POS access over RS485. It supports serial port stream and TCP/IP for communication with the front end processor.

Quidview NM system implements POS Access Management functions for medium and low end routers, including POS Access Common Information, POS Access Port Management, POS App Port Management, POS Application Management, POS Map Management and FCM Port Management. These parts will be described in detail below.

20.1 POS Access Common Information

This function is used to browse and configure POS access common information on medium and low end routers, and reset statistical information on POS access port and POS applications.

Double-click the function node [POS Access Management/POS Access Management] on the function tree in the function pane. Open the window "POS Access Management", as shown in Figure 20-1:


20-2

Figure 20-1 "POS Access Management" browse and configuration window

The meaning of each parameter is described in Table 20-1:

Table 20-1 POS access comm. information

Content Description

Enable POS Enable POS access server.

Enable POS Trap

Used to send SNMP alarms related to POS access to the NM system when the equipment is running. By default, no such a alarm is sent.

Open Access POS Debug Switch

Open Debug switch for all POS access ports. By default, Debug switch is disabled.

Open App Debug Switch

Open Debug switch for all POS applications. By default, Debug switch is disabled.

FCM Answer Time

As answer time of dialing via FCM port, its value ranges from 500 to 2000ms; 500ms by default.

FCM Trade Time

As timeout value of a single POS transaction, it ranges from 30000 to 1200000ms; 60000ms by default.

FCM Packet Interval

As timeout value of POS response packet, its value ranges from 3500 to 10000ms; 5000ms by default.

Users may modify part of the parameters according to needs, and then click <Config> to make configurations. If the user clicks <Refresh>, the system will read POS access common information from the device again and update information displayed in the window.


20-3

The <Reset Statistics> button is used to reset statistical information counters for the current device’s POS access port and POS applications, so as to count corresponding packets again starting from zero. After such click, conformation information will pop up. Upon confirmation, statistical information will be reset.

20.2 POS Access Port Management

Before used as POS access port, router interfaces must be configured as POS access ports. At present, the following interfaces on H3C series routers can be configured as POS access ports: asynchronous interface, AUX interface, synchronous/asynchronous interface (in asynchronous working mode) and FCM (Fast Connect Modem) board interface.

This function can be used to browse, add or delete information at the POS access ports of medium and low end routers, and configure part of the information.

20.2.1 Browse POS Access Port

Choose the function tree’s function node [POS Access Management/POS Access Management] in the function pane. Open the "POS Access Management" window, and select "POS Access Port" tab, as shown in Figure 20-2.

Figure 20-2 Window for browsing POS access port information



20-4

Table 20-2 Description of parameters for browsing POS access port information

Name Description

ID A unique ID must be allocated to each POS access port. While adding a POS access port, the user may specify its ID, which ranges from 0 to 127.

Access Port Name of this POS access port.

Connect Status

The physical status of this POS access port. There are four types in all: noset, down, up and ok.

Debug Switch The debug information switch of POS access port.

In the "POS Access Management" window, click <Refresh>, and the system will read POS access port data and refresh the display information.

20.2.2 Add POS Access Port

In the "POS Access Management" window, click <Add...>, and the "Add POS Access Port" window will pop up, as shown in Figure 20-3.

Figure 20-3 Add POS Access Port window

Enter POS access port number in this window. The "Access Port" drop box lists all device interfaces, which can be configured as POS access ports. Users may select an appropriate port according to needs. Finally, choose Debug switch status and click <OK> to add a new POS port. If your click <Cancel>, the system will do nothing but return to the "POS Access Port" window.


20-5

Caution:

POS access port number ranges from 0 to 127. The number you enter cannot be an existing POS access port number. It is allowed to add a maximum of 128 such access ports.

The port selected in the list of POS access ports must work in asynchronous mode and does not stay in other application modes, such as POS application port and terminal access port. Otherwise, a message will appear indicating the configuration has failed.

20.2.3 Delete POS Access Port

In the "POS Access Management" window, select one or more lines in the table, and click <Delete> in the window to delete the selected POS access port(s). When the port fails to be deleted, the system will give a message indicating deletion failure.

20.2.4 Config POS Access Port

In the window "POS Access Management", select one line of the table, click <Config...> in the window, and the "Config POS Access Port" will pop up, as shown in Figure 20-4.

Figure 20-4 Config POS Access Port window

A user is only allowed to modify the Debug switch status of the current POS access port in the "Config POS Access Port" window. After modification, click <OK> to finish configuration. If your click <Cancel>, the system will do nothing but return to the "POS Access Management" window.


20-6

20.2.5 Monitoring Statistical Information of POS Access Port

Select one line of the table in the "POS Access Management" window, and click <Monitor...>, the "POS Access Port Monitor" window will pop up, as shown in Figure 20-5.

Figure 20-5 Window for monitoring statistical information of POS access port

The monitoring items are described in Table 20-3.

Table 20-3 Description of POS access port items to be monitored

Name Description

Received Packets The total number of packets received from this access port.

Received Error Packets

The switching packet data that cannot be identified as complete, such as check sum error or incomplete packet.

POS Map Error Packets

The number of packets whose correspondence cannot be found.

Buffed Packets The number of packets in the buffer to be allocated to this POS access port.

Discarded Packets

The number of packets that cannot be sent out and thus are discarded after the application packets the router receives are distributed to this POS access port for such reasons as link disconnection, full buffer or failure to set the interface.


20-7

20.3 POS App Port Management

When POS access router and UNIX front end processor are connected in asynchronous mode, the interface must be configured to work in POS application mode. At present, the following interfaces on H3C series routers can be configured as POS interface ports: asynchronous interface, AUX interface, synchronous/asynchronous interface (working in asynchronous mode).

This function is used to view, add or delete information of POS application ports on medium and low end routers.

Select the function node [POS Access Management/POS Access Management] of the function tree in the function pane. Open the [POS Access Management] dialog box, and select the "POS App Port" tab, as shown in Figure 20-6.

Figure 20-6 POS App Port information dialog box

The "Port Available" list in the left part shows the ports available for the current device, while the "Port Selected" list in the right part shows the POS application ports available on the current device. Choose a port from the Port Selected list, and click <>>> to move this port to the "Port Selected" list, i.e. add a POS application port. Likewise, click "<<" and you may move a port in the "Port Selected" list to the "Port Available" list, that is, delete a POS application port. After that, click <Config> to make configurations. If you fail to configure a port, a message will appear indicating the configuration has failed. If you click <Refresh>, the system will read information on POS application port again from the device, and update the information in the dialog box.


20-8

Caution:

It is allowed to configure 128 POS application ports at most. The interface to be configured as a POS application port must work in asynchronous

mode and does not stay in any other application mode, such as POS application port and terminal access port. Otherwise, a message will appear indicating the configuration has failed.

20.4 POS Application Management

POS access router and UNIX front end processor are connected in two ways: streaming mode and TCP/IP mode. The commands used to configure POS application in these two ways are different. The connection with UNIX front end processor via Ethernet is called TCP/IP connection, while the connection with UNIX front end processor via asynchronous serial port is known as streaming mode. In whatever connection mode, it is required to configure POS application connected to UNIX front end processor for the terminal.

This function can be used to browse, add, delete or configure POS application information on medium and low end routers, and monitor statistical information about an application.

20.4.1 Browse POS Applications

Select the function node [POS Access Management/POS Access Management] from the function tree in the function pane. Open the [POS Access Management] dialog box, and select the [POS Application] tab, as shown in Figure 20-7:


20-9

Figure 20-7 Dialog box for browsing POS Application


Table 20-4 Description of parameter for browsing POS application

Name Description

Application ID

A unique ID should be allocated to each POS application. While adding a POS application, the user can specify such ID, which ranges from 0 to 31.

Mode

POS access router is connected to UNIX front end processor in two ways: streaming mode and TCP mode. Streaming mode requires no IP address or port number but asynchronous port configuration; TCP application requires IP address and port number but no asynchronous port configuration.

Status

Application connection is in the following 7 states: noset: TCP application not configured; down: asynchronous application "down"; up: asynchronous application "up"; ok: synchronous application "ok", indicating "up" state of successful authentication; kept: TCP application not connected. linking: connecting TCP application. linked: connected TCP application.

App Port Physical port of POS application in streaming mode


20-10

Name Description

IP Address Application IP address in TCP mode

TCP Port Application port number in TCP mode, ranging from 1 to 65535

Source IP Address

Source IP address of TCP application: when several terminals use a single TCP connection via terminal access server to communicate with host application, it is sometimes necessary to hide the real IP address for uplink TCP connection of the terminal access server for the sake of security or other considerations, and set another IP address as required; at the same time, in order for link backup, the terminal access server enables the function of TCP source address binding. TCP source address binding works in this way: first configure an IP address at a router interface not in use, and use that IP address as the IP for uplink TCP connection of the terminal server.

Debug Switch Debug information switch of current POS application.

If you click <Refresh> in the [POS Access Management] dialog box, the system will read POS application data from the device and refresh its display information.

20.4.2 Add POS Application

Click <Add> in the [POS Access Management] dialog box, and the [Add POS Application] dialog box will pop up, as shown in Figure 20-8.


20-11

Figure 20-8 Add POS Application dialog box

Enter POS application ID in this dialog box and select an application mode. If you select TCP/IP Mode, you need to enter application IP address and TCP port ID; if you select "Flow Mode", you need to choose a port from the "App Port" drop box, which lists the interfaces that are configured as POS application ports. A user may select an appropriate port according to his needs; source address of TCP application is only configured in case of TCP application mode but it can also be null. During configuration, click the button on the right of TCP application source address edit box, and the [Set Source IP Address for Application] dialog box will pop up. The list in this dialog box shows the current IP addresses configured with the device. Choose one of them and click <OK>; finally, choose Debug switch status and click <OK> to add a new POS application. If you click <Cancel>, the system will do nothing but return to the [POS Access Management] dialog box.


20-12

Caution:

POS application ID ranges from 0 to 31. It is not allowed to enter any number beyond the above range in the edit box and the number you enter cannot be the same as an existing POS application ID. A maximum of 32 POS applications can be added.

When you select TCP mode, you need to enter the application IP address and TCP port ID; when you choose streaming mode, you need to select an application port; otherwise, it is impossible to add an application.

When you select TCP mode, the combination of IP address and TCP port ID cannot be identical to an existing POS application. Otherwise, a message will appear indicating a failure.

Binding TCP connection source IP is configured only when the state of this application is without TCP connection. Otherwise, the system will give a message indicating the configuration has failed.

20.4.3 Delete POS Application

Select one or more lines of the table in the [POS Access Management] dialog box, and click <Delete> to delete the selected POS application. When the application is not deleted, the system will give a message indicating the deletion failure.

20.4.4 Config POS Application

Select a line of the table in the [POS application] dialog box, click <Config...>, and the [Configure POS application] dialog box will pop up.

To configure a POS application is similar to add an application, but it is not allowed to edit or modify POS application ID in the configuration dialog box. After modifying each parameter, click <OK> to complete configuration. If you click <Cancel>, the system will do nothing but return to the [POS Access Management] dialog box.

20.4.5 Monitoring Statistical Information of POS Application

Select one line of the table in the [POS Access Management] dialog box, click <Monitor...>, and the [POS Application Monitor] dialog box will pop up, as shown in Figure 20-9.


20-13

Figure 20-9 POS Application Monitor dialog box

The monitoring items are described in Table 20-5.

Table 20-5 Description of POS monitor items

Name Description

Received Packets Total number of packets this application receives.

Received Error Packets

The switching packet data that cannot be identified as complete, such as check sum error or incomplete packet.

Received Packets can not be sent to port

The number of packets whose access port correspondence cannot be found with distribution processing errors.

Buffed Packets

The number of packets that are sent to the front end processor via this application, but cannot be sent out and thus are discarded for such reasons as link disconnection, full buffer or failure to set this application.

Discarded Packets The number of packets that exist in this application’s sending cache.

20.5 POS Map Management

POS multi-application refers to POS access function, by which the packets on one POS equipment can be sent to different POS applications depending on the destination address. For TCP/IP connection, an application ID is made up of two parts: IP address


20-14

and port ID. In other words, different applications can either be ones with different IP addresses or those with identical IP address but different port IDs. Such a packet can be sent to an application depending on the exchange packet’s destination address number and the mapping table configured. If a packet’s destination address number corresponds to an item in the mapping table, the packet will be sent to the corresponding application; if such matched item is not found, the packet will be sent to the default application.

This function is used to browse, add, delete or configure POS multi-application mapping information on a medium or low end router.

20.5.1 Browsing POS Map

Select the function node [POS Access Management/POS Access Management] on the function tree of the function pane, open the [POS Access Management] dialog box and select the [POS Map] tab, as shown in Figure 20-10.

Figure 20-10 POS Map browsing dialog box


Table 20-6 Description of parameters used to browse POS multi-application mapping

Name Description

Destination Code

Packets sent from a POS all contain a package destination address. These packets are sent to different POS applications via destination code. While adding POS multi-application map, a user may specify such code, which ranges from 0 to 65535.

Application ID The ID of destination POS application, which ranges from 0 to 31.


20-15

If you click <Refresh> in the [POS Access Management] dialog box, the system will read POS multi-application mapping data from the device again and refresh its display information.

20.5.2 Add POS Map

Click <Add...> in the [POS Access Management] dialog box, and the [Add POS Map Item] dialog box will pop up, as shown in Figure 20-11.

Figure 20-11 Add POS Map Item dialog box

If you select "Default", you need not enter the destination code. Otherwise, you need to enter a number and then the POS application ID, and click <OK> to add a new POS map. If you click <Cancel>, the system will do nothing but return the [POS Access Management] dialog box.

Caution:

In case the current device has no default application, the “Add” window will display "Default" check box. Otherwise, such box will not appear.

It is allowed to add 32 POS multi-application maps at most. The application ID can either be an existent one or not created.

20.5.3 Delete POS Map

Choose one or more lines of the table in the [POS Access Management] dialog box, and click <Delete> in the window to delete the selected POS multi-application map. When you fail to delete the map, the system will give a message indicating the deletion failure.


20-16

20.5.4 Config POS Map

Select one line of the table in the [POS Access Management] dialog box, click <Config...> and the [Config POS Map Item] dialog box will pop up.

To configure POS multi-application map is similar to add one such map, but it is not allowed to edit or modify the destination code in the configuration window but you can only edit the application ID. After modification, click <OK> to complete the configuration. If you click <Cancel>, the system will do nothing but return to the [POS Access Management] dialog box.

20.6 FCM Port Management

During actual card punching, after responding to the operation, the POS equipment will dial up to fast connection Modem (FCM) on a H3C router in a synchronous or asynchronous way using its built-in Modem. After a communication link is set up between the POS equipment and the router, the router will be connected to the bank’s front end processor and background host via WAN or in a direct way, so that the POS unit at the business end is connected to the bank’s card accounting system.

As POS access service is unique, which requires the interface board to enable fast dialup connection, but an ordinary PC Modem at present cannot meet this requirement (its response takes 10 to 20 seconds). FCM (Fast Connect Modem) board developed for H3C series routers is a Modem capable of fast handshake tailor-made for POS dialup access. This board is able to dial a number and create a link in synchronous/asynchronous mode in a very short time.

This function is designed to browse data information on FCM port of medium and low end routers and clear the data information on FCM port through configuration.

Select the function node [POS Access Management/POS Access Management] on the function tree in the function pane, open the [POS Access Management] dialog box and select the [FCM Port] tab, as shown in Figure 20-12.


20-17

Figure 20-12 FCM Port information dialog box

The table is designed for the user to browse the times of disconnection due to timeout and the times of failed handshake negotiation that occur to all FCM ports of the current device.

Click <Reset> to reset the statistical information counter for FCM ports of the current device, and restart counting over again.

User Manual Volume I Quidview Device Manager Chapter 21 NDEC Management

21-1

Chapter 21 NDEC Management

H3C series modularized routers can implement hardware data encryption/decryption operations using NDECs (Network Data Encryption Cards, modularized hardware cards). This eliminates the effect on a router's performance by the VRP principal software's processing on the IPSec and hence improves the working efficiency of the router.

The encryption/decryption procedure with the participation of an NDEC is as follows: The router sends the data to be encrypted or decrypted to the NDEC that will then perform encryption/decryption operation on the data and add/remove encrypted frame headers to/from the data. After data encryption/decryption, the NDEC sends the data to the router for forwarding.

User data processing by multiple NDECs: Each H3C modularized router supports several NDECs. In the mode of polling, the host software sends user data to several normal NDECs for processing, thus implementing synchronous processing of user data on several NDECs and accelerating data encryption/decryption.

When you apply the IPSec on NDECs, if all the NDECs on a router are abnormal, IPSec processing will abort. In this case, if host backup has been enabled and the IPSec module of the VRP principal software supports the encryption/authentication algorism used by the NDECs, the IPSec module will replace the NDECs for IPSec processing, thus implementing NDEC backup.

21.1 NDEC Management

The NDEC management page displays the number of activated IPSec connections on a router and provides host backup function management. In the function pane, double-click on [NDEC/NDEC] node on the function tree to open the "NDEC" window, as shown in Figure 21-1.


21-2

Figure 21-1 NDEC Management

Various parameters are described in Table 21-1:

Table 21-1 NDEC management parameters

Content Description

NDEC Connection The number of currently activated IPSec connections

Backup Specified whether to enable host backup function, including 0 (disable) and 1 (enable)

Click <Enable Backup> to enable the function.

21.2 NDEC Information

As shown in Figure 21-2, the NDEC information page provides such functions as clearing statistics, resetting NDEC, synchronizing clock and NDEC logging.


21-3

Figure 21-2 NDEC information


Table 21-2 NDEC information parameters

Content Description

Card Slot Slot number of the NDEC

InPac The number of received packets

OutPac The number of sent packets

InByte The number of received octets

OutByte The number of sent octets

DropPac The number of discarded packets

Status Current status of the NDEC

Hardware Version Hardware version of the NDEC

Software Version Software version of the NDEC

CPLD Version CPLD version of the NDEC

Discarded Packets In Unit Time The number of packets discarded in a time unit

21.2.1 Clearing Statistics

This function is used to clear the related statistics in Figure 21-2, including InPac, OutPac, InByte, OutByte and DropPac.

Select a line of NDEC data from the interface and click <ClearStatic>. After confirmation, you can clear the related data.


21-4

21.2.2 Resetting NDEC

If finding an NDEC work abnormally, you can reset it so that it can recover. Resetting an NDEC will return its configuration to the initial values and have the host resend the configuration and SA (Security Association) information to the NDEC.

In Figure 21-2, select a line and click <Reset>. After confirmation, you can reset the NDEC.

21.2.3 Synchronizing Clock

Each NDEC has a clock. To synchronize an NDEC clock with the host clock, the host sends clock synchronization command to each NDEC periodically. This function enables you to synchronize an NDEC's clock manually.

In Figure 21-2, select a line and click <SynTime>. After confirmation, you can synchronize the NDEC clock.

21.2.4 NDEC Logging

By default, NDEC logging function is disabled, and you can use the functions provided in Figure 21-2 to enable or disable the logging function or to clear NDEC logs.

Select a line and click <OpenLog>. After confirmation, you will enable the NDEC logging function. Click <CloseLog> and confirm to disable the NDEC logging function. Click <ClearLog> and confirm to clear the existent NDEC logs.

21.3 Router SA Information

This function displays the SA information configured on a router, as show in Figure 21-3:


21-5

Figure 21-3 SA information


Table 21-3 SA information parameters

Content Description

Peer IP The IP address of the peer end

Security Protocol The security protocol used by the NDEC

SPI Security policy identifier

Encrypt The encryption algorism adopted by the NDEC

Auth The authentication algorism adopted by the NDEC

Local IP Local IP address

Life(KByte) Current life cycle in KByte of the SA

Life(Second) Current life cycle in second of the SA

ByCard Whether to use NDEC

Negotiate SA Mode Includes manual negotiation (Manual) and IKE negotiation (isakmp)

Exp_bytes Hard timeout in KByte

Soft_bytes Soft timeout in KByte

Exp_timeout Hard timeout in second

Soft_timeout Soft timeout in second


21-6

21.4 NDEC IKE SA Information

This function displays the IKE SA information of an NDEC on a router, as shown in Figure 21-4.

Figure 21-4 NDEC IKE SA information


Table 21-4 NDEC IKE SA information parameters

Content Description

Conn-ID The identifier of the security path

Peer IP The peer IP address of the SA

Phase

The status of the SA: NONE: The SA is being established. READY: The SA has been successfully established. STAYALIVE: The initiator of the SA, which will reinitiate a negotiation in the case of soft timeout (a new negotiation is initiated before the end of the SA's life). REPLACED: The SA has been replaced by a new one, is not in use currently and will be deleted 10 seconds later. FADING: Though soft timeout occurs, the SA is still in use till a new SA is negotiated or hard timeout (the SA live through its whole life till timeout), when it will be deleted.

Flag The phase of the SA, including unknown, phase1 and phase2

Domain The explanation domain of SA, including unknown and ipsec

Select a line and click <Delete>. After confirmation, you can delete the information.


21-7

21.5 Router IKE Policy Information

This function displays the IKE policy information of a router, as shown in Figure 21-5.

Figure 21-5 IKE policy information


Table 21-5 IKE policy information parameters

Content Description

Priority IKE policy priority of the router

Encrypt IKE policy encryption algorism of the router

Hash IKE policy authentication algorism of the router

Auth Whether to use pre-share-key authentication

DH Group The group identifier of the DH

Lifetime The life cycle in second of the IKE SA

21.6 Router Security Policy Information

This function displays the security policy information of a router, as shown in Figure 21-6.


21-8

Figure 21-6 Security policy information


Table 21-6 Security policy information parameters

Content Description

Name The name of the security policy

Priority The priority of the security policy

NegMode The negotiation mode of the security policy

ACL ID ACL ID matching the policy

Peer IP Peer IP address corresponding to the policy

Transfer Name Policy transference mode name

Lifetime Life cycle in second of the security connection

Lifesize Life cycle in KByte of the security connection


Name Used The name of the interface applying the policy

In AH SPI SPI of the packet stream received by the AH

In ESP SPI SPI of the packet stream received by the ESP

Out AH SPI SPI of the packet stream sent by the AH

Out ESP SPI SPI of the packet stream sent by the ESP

In AH Hex Key String Key of the packet stream received by the hexadecimal AH

In ESP Hex Key String Key of the packet stream received by the hexadecimal ESP


21-9

Content Description

In ESP AuthenHexKeyString Authentication key of the packet stream received by the hexadecimal ESP

In AH StringKeyString Key of the packet stream received by the AH in character string mode

In ESP StringKeyString Key of the packet stream received by the ESP in character string mode

Out AH HexKeyString Key of the packet stream sent by the hexadecimal AH

Out ESP CipherHexKeyString Key of the packet stream sent by the hexadecimal ESP

Out ESP AuthenHexKeyString Authentication key of the packet stream sent by the hexadecimal ESP

Out AH StringKeyString Key of the packet stream sent by the AH in character string mode

Out ESP StringKeyString Key of the packet stream sent by the ESP in character string mode

21.7 Transform Mode Security Information

This function displays the transform mode security information of a router, as shown in Figure 21-7:

Figure 21-7 Transform mode security information



21-10

Table 21-7 Transform mode security information parameters

Content Description

Transform Name Name of transform

Transform Mode Includes transport and tunnel

Transform Protocol Protocol used for authentication/encryption

AH AH protocol (AH authentication algorism)

ESP-Encrypt ESP (encryption algorism)

ESP-Auth ESP (authentication algorism)

IsCardTransform Whether to use NDEC

User Manual Volume I Quidview Device Manager Chapter 22 Terminal Server Management

22-1

Chapter 22 Terminal Server Management

Terminal access servers are primarily applied to the systems operating in host-terminal mode, such as banking service system. It accesses the terminals residing at different business sites to the host in the central equipment room over IP networks. Using virtual terminal, it implements smooth transition from multiplexer access to IP network access. As this transition is transparence to customers, they do not need to change the existent applications.

22.1 Terminal Access Server Management

Terminal access server management includes the setting of general and debugging information of terminal applications. In the function pane, double-click on [Terminal Server/Terminal Server] node on the function tree to open the "Terminal Server" window, as shown in Figure 22-1.

Figure 22-1 Terminal application management

Information in this window falls into two types, general information and debugging information. Various parameters are described in Table 22-1.


22-2

Table 22-1 Terminal application management parameters

Content Description

Enable Tty Server

Enables or disables the terminal access server function on the router

Enable Trap Sets whether to send Trap information from the server

Clear Statics Info Clears the related statistics

Debug Tty Error Sets whether to display the error information of the terminal applications

Debug Tty Manager

Sets whether to display the management path information of the terminal applications

22.2 Terminal Access Application Management

Terminal access application management interface lists the configured terminal applications and the related statistics, as shown in Figure 22-2.

Figure 22-2 Terminal access application management



22-3

Table 22-2 Terminal access application management parameters

Content Description

App ID

The application ID of the terminal server. Its value depends on the number of asynchronous serial interfaces on the device. If there are two available interfaces, it ranges from 0 to 7. If there is one available interface, it ranges from 0 to 3.

App IP The IP address of the UNIX host where the terminal server application resides

App Port TCP port of the UNIX host where the terminal server application resides, ranging from 1025 to 65535

App Type Includes normal and special

App Name The name of the terminal server application

Source IP The source IP address bound to the application

Local Port Local port

Unix ID The index of the management path information

Server Status Displays the connection status between the UNIX host and the router, including kept, linked and linking

Socket Received Buffer Socket Sent Buffer Socket Received Bytes Socket Sent Bytes Last Received Time Last Sent Time

Related statistics of the terminal access application

I. Adding a terminal server application

In Figure 22-2, click <Add…> to open the [Add App] window, as shown in Figure 22-3.


22-4

Figure 22-3 Adding a terminal server application

Various parameters are described in Table 22-2. Click <…> following the "Source IP" edit box, and you will open the [Set Source IP Address for Application] window, as shown in Figure 22-4.

Figure 22-4 Selecting a source IP address

Select a line and click <OK> to finish the selection of source IP address.

In Figure 22-3, click <OK> to finish the adding operation.


22-5

II. Deleting a terminal server application

In Figure 22-2, select one or more terminal server applications and click <Delete>. After confirmation, you will delete the related data.

III. Configuring a terminal server application

In Figure 22-2, select a terminal server application and click <Config…> to open the [Modify App] window, as shown in Figure 22-5:

Figure 22-5 Modifying a terminal server application

All the parameters except App ID are configurable. The meaning of various parameters is the same as that in the adding window.

IV. Clearing statistics

In Figure 22-2, select one or more terminal server applications and click <Clear Statistics>. After confirmation, you will clear the related statistics.

22.3 Physical Terminal and Virtual Terminal Management

On a terminal access server, a physical terminal (terminal) corresponds to an asynchronous port of a router. Each asynchronous port, when being properly configured, can be connected to a terminal over asynchronous cable or Modem. The terminal access server numbers all the connected physical terminals following the same rule. Currently, a router can support up to 32 terminals.

On a terminal access server, you can configure up to 4 virtual terminals, each of which corresponds to a host application, for a single physical terminals. If there are several host applications specified on the terminal access server and you want to correlate a terminal with several applications and switch between different applications using


22-6

hotkeys, you can configure several virtual terminals for the physical terminal and correlate them with the applications.

The physical terminal and virtual terminal management interface is shown in Figure 22-6.

Figure 22-6 Physical terminal and virtual terminal management


Table 22-3 Physical terminal and virtual terminal management parameters

Content Description

Tty ID ID of the physical terminal. Its value depends on the number of interfaces supporting terminal access on the device. For example, if the number of such interfaces is 2, it ranges from 0 to 1.

Vty ID Virtual terminal ID ranging from 0 to 3

Interface The interface supported by the device

App ID Application ID that subjects to the configuration of terminal access application management

Status Current status of the physical terminal and its virtual terminal

Flow Control Flow control setting of the physical terminal and its virtual terminal

I. Adding a physical terminal and its virtual terminal

Click <Add…> to open the [Add TTY&VTY] window, as shown in Figure 22-7.


22-7

Figure 22-7 Adding a physical terminal and its virtual terminal

Various parameters are described in Table 22-3. Enter various parameters and click <OK> to add a physical terminal and a virtual terminal.

Caution:

If the adding fails and you are prompted "Config failed, please confirm the port selected is in async mode instead of pos access port, pos app port or any other ports", please run the "async mode protocol" command on the device in the proper interface mode.

II. Deleting a physical terminal and its virtual terminal

In Figure 22-6, select one or more lines and click <Delete>. After confirmation, you can delete the related information.

III. Configuring a physical terminal and its virtual terminal

In Figure 22-6, select a line and click <Config…> to open the physical terminal and virtual terminal modification window. The Tty ID and Vty ID are not configurable, so you only need to modify the App ID.

IV. Disconnecting a connection

This function is used disconnect the connections of a selected virtual terminal. In Figure 22-6, select a line and click <Disconnect>. After confirmation, you will disconnect the connections.


22-8

22.4 Physical Terminal Information

The physical terminal information interface displays the information of the physical terminals and its virtual terminals configured on a router, as shown in Figure 22-8.

Figure 22-8 Physical terminal information


Table 22-4 Physical terminal information parameters

Content Description

TTY ID Physical terminal ID that depends on the number of interfaces supporting terminal access. For example, if the number of such interfaces is 2, it ranges from 0 to 1.

Buffer Size Buffer size ranging from 4096 to 204800

Auto Link Connection auto creation time ranging from 5 seconds to 3600 seconds

Auto Close Link Connection auto closing time ranging from 5 seconds to 3600 seconds

ConnPrint Includes English, Chinese and none

Delay Ranges from 0 to 1200 seconds

Logo Print Whether to display terminal server Logo

MenuKey1/2/3 Hotkey for menu

Read Block Reads the blocking mode of physical terminal data, including Set and noSet

RedrawKey1/2/3 Hotkey for redrawing screen

ResetKey1/2/3 Hotkey for reset


22-9

Content Description

TCP No Delay Sets whether to enable TCP delay

RecvBufferSize Size of receiving buffer ranging from 512 to 16384

SendBufferSize Size of sending buffer ranging from 512 to 16384

TestKey1/2/3 Hotkey for test

Buffer Rate Utilization rate of the buffer

TtyRecvBytes The number of octets received by the physical terminal

TtySendBytes The number of octets sent by the physical terminal

TtyLastRecvTime Time when the physical terminal receives data the last time

TtyLastSendTime Time when the physical terminal sends data the last time

CurrentVty Current virtual terminal ID

CurrentVtyRecv The number of octets received by current virtual terminal

CurrentVtySend The number of octets sent by current virtual terminal

CurrentApp Current application ID

CurrentAppRecv The number of octets received by current application

CurrentAppSend The number of octets sent by current application

Debug tty all Sets whether to enable debugging

Debug tty brief Sets whether to enable brief information to be received/sent

Debug tty socket Sets whether to enable socket information to be received/sent

Debug tty timestamp Sets whether to log timestamp access information

Debug tty tty Sets whether to enable the physical terminal information to be received/sent

I. Configuring physical terminal information

In Figure 22-8, select a line and click <Config…> to open the physical terminal information modification window, as shown in Figure 22-9:


22-10

Figure 22-9 Modifying physical terminal information

Various parameters are described in Table 22-4. Enter the parameters, click <OK> and confirm to finish the operation.

II. Setting hotkeys

In Figure 22-8, select a line and click <Set HotKey> to open the [Set Hotkey] window, as shown in Figure 22-10.


22-11

Figure 22-10 Setting hotkey

Set the related hotkeys in the window.

III. Clearing statistics

In Figure 22-8, select a line and click <Clear Statistics>. After confirmation, you will clear the related statistics, including TtyRecvBytes, TtySendBytes, TtyLastRecvTime, TtyLastSendTime, CurrentVtyRecv, CurrentVtySend, CurrentAppRecv and CurrentAppSend.

22.5 Management Path Information

The management path information interface lists the information of the management paths configured on a router, as shown in Figure 22-11.

Figure 22-11 Management path information


22-12


Table 22-5 Management path information parameters

Content Description

Unix Index Management path index

Unix Socket ID Socket ID


Managed Apps The number of applications covered by the management path

User Manual Volume I Quidview Device Manager Chapter 23 DLSW Service Management

23-1

Chapter 23 DLSW Service Management

Data link switch (DLSW) is an implementation of SNA (a network protocol family promoted by IBM in 1970's, which completely corresponds to the OSI reference model) over TCP/IP. The DLSW technology is one of the solutions to SNA transmission cross WAN.

The working principal of DLSW is illustrated in Figure 23-1:

Figure 23-1 Working principal of DLSW

As shown, the router running DLSW converts the LLC2 frames from a local SNA device to SSP frames that can be encapsulated in TCP packets and sends them to a remote device cross WAN over a TCP channel. The remote device converts the SSP frames to LLC2 frames again and sends them to the peer SNA device. In this case, the local terminal device thinks that the remote device resides on the same network. Different from transparent bridge, DLSW does not transparently transmit LLC2 frames to the peer end directly, but converts them to SSP frames so that they can be encapsulated in TCP packets. DLSW uses local response mechanism to reduce unnecessary data traffic (ACK and Keepalive frames) and to solve the problem of data link control timeout.

With the DLSW technology, you can also implement SDLC transmission over TCP/IP in the following way: Convert packets of SDLC format to those of LLC2 format and communicate with the peer end via DLSW. In this way, DLSW also supports the interconnection between LAN and SDLC over different mediums.

23.1 DLSW Configuration

DLSW configuration includes general parameter configuration of the DLSW service. In the function pane, select [DLSW Service Management/DLSW Service Management] to open the [DLSW Service Management] window, as shown in Figure 23-2.


23-2

Figure 23-2 DLSW Configuration


Table 23-1 DLSW configuration parameters

Content Description

Status Sets the status of the DLSW service to active or inactive

Connection Timeout Sets connection hole time in the range of 60 ms to 60000 ms

Local Pend Timeout Sets local timeout in the range of 1 ms to 60000 ms

Remote Pend Timeout Sets remote timeout in the range of 1 ms to 60000 ms

Sna Cache Timeout

Sets address storage timeout of the buffer in the range of 1ms to 60000 ms

Enter various parameters and click <Config> to finish the operation.

23.2 Local Peer

Caution:

Before configuring local peer, you must set the status of DLSW to active.


23-3

This function configures the related parameters of local peer, and the interface is shown in Figure 23-3:

Figure 23-3 Local Peer


Table 23-2 Local peer configuration parameters

Content Description

Local Address Sets the IP address of DLSW local peer

Promiscuous Sets whether to enable an un-configured remote peer to establish a connection, including permit, forbid and unknown

Keepalive Interval Sets DLSW life cycle in the range of 1ms to 2000ms

Virtual Segment LF-Size

Sets the maximum frame length of local peer, including 516, 1470, 1500, 2052, 4472, 8144, 11407, 11454, 17800 and 65535

Init Pacing Window Size Initial window size in the range of 1 to 2000

Max Pacing Window Size Maximum window size in the range of 1 to 2000

Cost Cost value in the range of 1 to 5

Enter various parameters and click <Config> to finish the operation.


23-4

23.3 Remote Peer

This function is used to browse and configure the related parameters of the remote peer, and the interface is shown in Figure 23-4:

Figure 23-4 Remote Peer

This interface includes the parameters and statistics of the remote peer. Various parameters are described in Table 23-3:

Table 23-3 Remote peer configuration parameters

Content Description

Address Sets the IP address of the DLSW remote peer

Pack Window Init Initial window size

IsConfig Whether the peer is a static peer

Cost Cost value ranging from 1 to 5

KeepAlive Life cycle ranging from 0 to 1200ms

Virtual Segment LF-Size

Maximum frame length, including 516, 1470, 1500, 2052, 4472, 8144, 11407, 11454 and 17800

TcpQueueMax Maximum length of a TCP queue, ranging from 50 to 2000

HaveBackup Whether the peer is a primary peer

IsBackup Whether the peer is a backup peer

PrimaryEntityAddr Address of the primary peer

Peer Linger Hold time of the backup peer

Link Status Connection status


23-5

Content Description

Received Packets The number of received packets

Sent Packets The number of sent packets

Drops Disconnection times

Uptime Connection hole time

DLSW Version DLSW version number and release number

DLSW OUI The OUI of DLSW

OS Version Operating system version number

I. Creating a remote peer

In Figure 23-4, click <Add…> to open the [Create Remote Peer] window, as shown in Figure 23-5.

Figure 23-5 Creating a remote peer

Various parameters are described in Table 23-3. Select or modify the parameters and click <OK> to finish the operation.

II. Deleting a remote peer

In Figure 23-4, select a line and click <Delete>. After confirmation, you will delete the selected remote peer.


23-6

III. Configuring a remote peer

In Figure 23-4, select a line and click <Config…> to open the remote peer configuration window that is similar to the creation window. All the parameters in the interface except the remote peer IP address are configurable.

23.4 Bridge Group

The DLSW technology is developed based on the bridge technology. Bridge group is the forwarding unit of a bridge, and you can configure several Ethernet interfaces to a bridge group to enable packet forwarding among them.

The bridge group window is shown in Figure 23-6.

Figure 23-6 Bridge Group

On the left of the window is a bridge group list and the interfaces included in each bridge group are displayed in the right list.

I. Creating a bridge group

To forward the packets from the specified bridge group over a TCP connection, you need to connect the local bridge group to the DLSW so that packets from the bridge group can be sent to remote over a TCP channel. You can create several bridge groups and connect them with the DLSW so that they can forward packets over a TCP channel.

In Figure 23-6, click <Add…> to open the "Create Bridge Group" window, as shown in Figure 23-7.


23-7

Figure 23-7 Create Bridge Group

Type the bridge group ID (in the range of 1 to 63) and click <OK> to create a bridge group.

II. Deleting a bridge group

In Figure 23-6, select a bridge group ID from the bridge group list and click <Delete>. After confirmation, you will delete the selected bridge group.

III. Configuring a bridge group

In Figure 23-6, select a bridge group ID from the bridge group list and click <Config…> to open the configuration window, as shown in Figure 23-8.

Figure 23-8 Bridge group configuration


23-8

This window lists the selected interfaces of the bridge group and those available for selection. You can click <>>> or <<<> to move interfaces to or form the bridge group, and then click <OK> to finish the operation.

23.5 SDLC Interface

The SDLC is a link layer protocol relative to the SNA, and its working principal is similar to the HDLC. To have the DLSW work normally, you need to change the link layer encapsulation protocol of the synchronous interface to the SDLC.

The SDLC interface configuration window is shown in Figure 23-9.

Figure 23-9 SDLC Interface


Table 23-4 SDLC interface configuration parameters

Content Description

Serial Port Name The name of the SDLC port

Encapsulating SDLC Sets to encapsulation protocol of the synchronous interface to the SDLC, including SDLC, PPP and OTHER

Role Includes primary, secondary and norole

Virtual MAC The MAC address of the SDLC virtual circuit

Hold Queue Size The length of sending queue ranging from 20 to 255

Sending Window Size The size of sending window ranging from 1 to 7

Modulus Includes m8 and m128

Max Receivable Frame Length

Maximum receivable frame length ranging from 1 to 17680

Retry Retry times in the case of timeout ranging from 1 to 255


23-9

Content Description

Poll Pause Interval Interval at which each secondary site is polled, ranging from 1 ms to 10000 ms

Simultaneous Enable Sets whether to enable SDLC bi-directional transmission

Calling Waiting Interval The timeout of the response to the primary site, ranging from 1 ms to 60000 ms

Called Waiting Interval The timeout of the response to the secondary site, ranging from 1 ms to 60000 ms

23.5.1 SDLC Interface Configuration

In Figure 23-6, select a line and click <Config…> to open the "SDLC Port Config" window, as shown in Figure 23-10:

Figure 23-10 SDLC port configuration - SDLC port attribute

This interface includes two tabbed pages, SDLC Port Attribute and SDLC Port Remote Peer. Various parameters in the "SDLC Port Attribute" page are described in Table 23-4.

23.5.2 SDLC Prot Remote Peer Configuration

The SDLC port remote peer interface is shown in Figure 23-11.


23-10

Figure 23-11 SDLC port configuration - SDLC port remote peer

This interface provides adding, deletion and modification of SDLC port remote peers.

I. Creating an SDLC port peer

Click <Add…> to open the "Create SDLC Port Peer" window, as shown in Figure 23-12.

Figure 23-12 Creating an SDLC port peer



23-11

Table 23-5 SDLC port remote peer parameters

Content Description

SDLC Address Ranges from 1 to 254

XID The XID of SDLC, ranging from 0 to 2147483647

Remote Peer MAC The MAC address of the remote peer

Peer Source SAP The source SAP address of the peer end, ranging from 1 to 254

Peer Destination SAP The destination SAP address of the peer end, ranging from 1 to 254

Enter the parameters and click <OK> to create an SDLC port remote peer.

II. Deleting an SDLC port peer

In Figure 23-11, select a line and click <Delete> to delete the SDLC port remote peer.

III. Modifying an SDLC port peer

In Figure 23-11, select a line and click <Modify…> to open the SDLC port remote peer modification window that is similar to the creation window. All the parameters in the window are editable.

After configuring SDLC port attributes and remote peer, click <OK> in the configuration window and confirm to validate your configuration.

23.6 LLC2 Parameter Configuration

This function is used to configure the related parameters of LLC2 packets, and the interface is shown in Figure 23-13:

Figure 23-13 LLC2 parameter configuration


23-12

Select a line and click <Config…> to open the "LLC2 Parameter Configuration" window, as shown in Figure 23-14.

Figure 23-14 LLC2 parameter configuration


Table 23-6 LLC2 parameters

Content Description

Acknowledge Delay Time

Delay of information frame acknowledgement, ranging from 1 ms to 60000 ms

Acknowledge Max Frame

The maximum number of information frames that can be received before an acknowledgement frame is sent, ranging from 1 to 127

Local Window Size

The maximum number of information frames that can be sent before an acknowledgement frame is received, ranging from 1 to 127

Modulus LLC2 modulus, including m8 and m128

Retry Times of retries, ranging from 1 to 255

Wait Time for Acknowledge Acknowledgement timeout, ranging from 1 ms to 60000 ms

Busy Time Polling interval for a busy site, ranging from 1 ms to 60000 ms

Wait Time of P/F

Duration from the sending of a P frame to the reception of a correct information frame, ranging from 1 ms to 60000 ms


23-13

Content Description

Reject Status Time

Duration from the sending of a rejection frame to the reception of a correct information frame, ranging from 1 ms to 60000 ms

Send Queue Size

Length of the LLC2 information frame output queue, ranging from 20 to 200

Select or modify the related parameters, click <OK> and confirm to finish the configuration operation.

23.7 DLSW View

This function is used to browse the DLSW-related information. The interface includes three tabbed pages: DLSW Static Information, DLSW Virtual Circuit, and DLSW MAC Cache.

Various parameters are described in Table 23-7, Table 23-8 and Table 23-9 respectively.

Table 23-7 DLSW static information parameters

Content Description

DLSW Version Standard DLSW version

DLSW OUI The OUI of the DLSW

DLSW Product Information Information of the product applying the DLSW

Circuit Pacing Type Type of circuit pacing

Table 23-8 DLSW virtual circuit parameters

Content Description

S1 Circuit ID Circuit ID allocated by local DLSW node, ranging from 0 to 2147483647

S1 MAC MAC address of terminal1 of the circuit

S1 SAP SAP address of S1

S2 MAC MAC address of terminal2 of the circuit

S2 SAP SAP address of S2

S1 Interface Index

Index of the interface connected with S1, ranging from 0 to 2147483647

S1 Interface Name Name of the interface connected with S1

S1 Ic Type DLC type between the DLSW device and S1


23-14

Content Description

S2 Location Location of terminal2

S2 Address Remote DLSW's IP address when terminal2 is not a local terminal

S2 Circuit ID Circuit ID allocated by remote DLSW node, ranging from 0 to 2147483647

Origin Originator of the circuit, including s1(1), s2(2)

Entry Time Creation time of the entry

Status Time Time when the circuit entered current status

Status

Current status of the circuit, including disconnected(1), circuitStart(2), resolvePending(3), circuitPending(4), circuitEstablished(5), connectPending(6), contactPending(7), connected(8), disconnectPending(9), haltPending(10), haltPendingNoack(11), circuitRestart(12) and restartPending(13)

Priority Includes unsupported(1), low (2), medium (3), high (4) and highest (5)

Send Granted Units

The number of SSP messages that can be sent by the DLSW over the circuit according to the pacing window size, ranging from 0 to 65535

Send Current Window

Current window length of the DLSW as a sender, ranging from 0 to 65535

Table 23-9 DLSW MAC catch parameters

Content Description

MAC MAC address


User Manual Volume I Quidview Device Manager Chapter 24 DHCP Management

24-1

Chapter 24 DHCP Management

This function can be used on core routers and S8016 LAN switches. For the details of DHCP management function on switches, refer to Quidview Device Manager User Manual Volume II.

DHCP is short for Dynamic Host Configuration Protocol. Users can be assigned IP addresses dynamically using DHCP compare to manual configuration.

Core routers and S8016 support both built-in DHCP server and external DHCP server function. For external DHCP servers, it needs the DHCP Relay support on the equipment. By modifying users’ properties, it can also be configured for the user to obtain IP address from the built-in DHCP server or from the external DHCP servers via DHCP Relay.

Built-in DHCP server means the IP address pool is configured within the equipment and when user goes online, if he was configured to obtain IP address from the built-in address pool, the built-in DHCP server will assign an address to the user according to his address pool properties. If there was no external DHCP server or there’s problem communicating with external DHCP servers, built-in DHCP server can also be used for IP address allocation.

The built-in DHCP server normally service 2 types of users: one is VLAN user that initiate DHCP request directly to the equipment and called VLAN address pool users; the other’s request passes through DHCP relay equipment such as MA5200 before reaching the core routers or S8016 and is called global address pool users.

24.1 DHCP Server Group Management

Core routers and S8016 can support 20 DHCP server groups. Each server group can support 2 IP addresses. The config of DHCP server groups can support different user groups to request IP addresses from different DHCP servers such as some of the VLANs request IP addresses from one server group and the other VLANs request from another server group. This can fulfill different user requirements and to provide special DHCP policies to some specific users. This also can reduce the risk of DHCP server from attacks. You can configure 2 IP addresses for each group to enable the backup of servers.

24.1.1 Browsing DHCP Server Group Information

In the function menu double-click the [DHCP Management/DHCP Server Group Management] on the function tree, open "DHCP Server Group Management" windows as shown in Figure 24-1.


24-2

Figure 24-1 DHCP Server Group Management

Parameters in the window are described as in Table 24-1.

Table 24-1 Description of parameters of DHCP Server Group Management

Name Description

Group ID DHCP server group’s unique ID

DHCP Server IP Address1 First DHCP server address in the group

DHCP Server IP Address2 Second DHCP server address in the group

The information viewable including all DHCP server groups list on the same equipment and the according 2 IP address for each group.

24.1.2 Configuring DHCP Server Group

In the [DHCP Server Group Management] dialog box click any group data, then click <Config…> to pop up the [DHCP Server Group Configuration] dialog box as shown in Figure 24-2.


24-3

Figure 24-2 DHCP Server Group Configuration

Input the DHCP server IP addresses in the window for this server group and click <OK> to finish the configuration.

24.2 DHCP Relay Management

This function is used to query and config the associating relationship between VLAN and DHCP server group.

24.2.1 Querying VLAN and DHCP Server Group Association

In the function pane double-click [DHCP Management/DHCP Relay Management] on the function tree to open "DHCP Relay Management" window as shown in Figure 24-3.


24-4

Figure 24-3 DHCP Relay Management


Table 24-2 Description of parameters of DHCP Relay

Name Description

VLAN ID An integer for unique VLAN identification

DHCP Server Group ID DHCP server group’s unique ID

DHCP Server IP Address1 First DHCP server address in the group

DHCP Server IP Address2 Second DHCP server address in the group

The associating VLAN and DHCP server group on the equipment can be seen including VLAN ID, associating DHCP server group ID and the IP addresses of the servers in the group.

24.2.2 Creating VLAN and DHCP Server Group Association

In the "DHCP Relay Management" window click <Add…> to pop up the "DHCP Relay Creation" window as shown in Figure 24-4.


24-5

Figure 24-4 DHCP Relay Creation

This window provides example of the input. User can input the VLAN ID list like the example and choose DHCP server group then click <OK> to finish this operation.

24.2.3 Deleting VLAN and DHCP Server Group Association

In the "DHCP Relay Management" window choose one or more associations and click <Delete> to delete them.

24.2.4 Configuring VLAN and DHCP Server Group Association

In the "DHCP Relay Management" window, choose a line of associations and click <Config…> to pop up "DHCP Relay Configuration" window as shown in Figure 24-5.

Figure 24-5 DHCP Relay Configuration

In this window choose the DHCP server group again and click <OK> to finish.


24-6

24.3 VLAN Address Pool Management

24.3.1 Querying VLAN Address Pool Information

In the function pane double-click the [DHCP Management/VLAN Address Pool Management] on the function tree to open the "VLAN Address Pool Management" window as shown in Figure 24-6.

Figure 24-6 VLAN Address Pool Management


Table 24-3 Description of parameters of VLAN Address Pool

Name Description

VLAN ID DHCP server group’s unique ID

Address Allocation Mode

User address allocation mode in current VLAN. When address allocation mode is local, it become VLAN address pool

L3 Interface Address VLAN address pool Layer 3 interface IP address

Mask VLAN address pool’s subnet mask

Primary DNS Primary DNS server IP address

Secondary DNS Secondary DNS server IP address

Primary WINS Primary WINS server IP address

Secondary WINS Secondary WINS server IP address


24-7

Information viewable including associating address allocation method of each VLAN on the equipment. When the method is local, it is the VLAN address pool and the Layer 3 interface IP address, subnet mask, primary/secondary DNS/WINS server addresses and reserved address range in the pool can be seen.

24.3.2 Changing VLAN Address Allocation Mode

In "VLAN Address Pool Management" window choose a line of data from the "VLAN Address Pool List" and click <Change Allocation Mode> to change the allocation mode. If previously is local, then changed to extern; if previously is extern, then changed to local.

24.3.3 Configuring VLAN Address Pool

In "VLAN Address Pool Management" window choose an address pool and click <Config…> to pop up "VLAN Address Pool Configuration" window as shown in Figure 24-7.

Figure 24-7 VLAN Address Pool Configuration

In the window, Primary/Secondary DNS/WINS addresses can be configured. After modification, click <OK> to finish the operation.

24.3.4 Querying Statistics Information

In "VLAN Address Pool Management" window, choose an address pool and click <Statistics…> to pop up VLAN Address Pool Statistics window as shown in Figure 24-8.


24-8

Figure 24-8 VLAN Address Pool Statistics


Table 24-4 Description of parameters of VLAN Address Pool Statistics

Name Description

Used Addresses Number of addresses being used in the pool

Unused Addresses Number of free addresses in the pool

Disabled Addresses Number of disabled addresses in the pool

Total Addresses Number of all addresses in the pool

This window displays pool information including Used Addresses, Unused Addresses, Disabled Addresses and Total Addresses.

24.3.5 Appending Disabled IP Segment

In "VLAN Address Pool Management" window choose an IP address pool, click <Append Disabled IP Segment…> to pop up "Disabled IP Segment Creation" window as shown in Figure 24-9.


24-9

Figure 24-9 Disabled IP Segment Creation


Table 24-5 Description of parameters of Disabled IP Segment Creation

Name Description

VLAN ID VLAN address pool VLAN ID

Low Address Start address of the disabled address segment

High Address Last address of the disabled address segment

Input the disabled segment’s Low Address and High Address in the window then click <OK> to finish the operation. Now new disabled segment can be seen in the window shown as in Figure 24-6.

24.3.6 Canceling Disabled IP Segment

Choose an address pool in "VLAN Address Pool Management" window then click <Cancel Disabled IP Segment…> to pop up "Disabled IP Segment Cancellation" window as shown in Figure 24-10.


24-10

Figure 24-10 Disabled IP Segment Cancellation

The length in the window means the length of the segment needs cancellation. The value is between 1 to actual length of the segment. Input length and click <OK> to finish the cancellation operation.

Note:

The first and the last address value in the disabled segment (the low and high address of “Disabled IP Segments”) cannot be cancelled.

24.4 Global Address Pool Management

24.4.1 Querying Global Address Pool Information

In the function pane, double-click the [DHCP Management/Global Address Pool Management] on the functions tree to open "Global Address Pool Management" window as shown in Figure 24-11.


24-11

Figure 24-11 Global Address Pool Management

Information viewable including Name, Gateway, Mask, Router IP, Primary/Secondary DNS/WINS addresses and disabled address segment in the pool.

24.4.2 Creating Global Address Pool

In "Global Address Pool Management" window click <Add…> to pop up "Global Address Pool Creation" window as shown in Figure 24-12.


24-12

Figure 24-12 Global Address Pool Creation


Table 24-6 Description of parameters of Global Address Pool

Name Description

Name Global address pool unique ID

Gateway Global address pool Gateway address

Mask Global address pool subnet mask, with address pool gateway address, defines ip address range with in the pool

Router IP Router IP address for this pool

Primary DNS Primary DNS Server IP address

Secondary DNS Secondary DNS Server IP address

Primary WINS Primary WINS Server IP address

Secondary WINS Secondary WINS Server IP address


24-13

In the window, input parameters of Name, Gateway, Mask, Router IP, Primary/Secondary DNS/WINS address and click <OK> to finish operation.

24.4.3 Deleting Global Address Pool

Choose one or more global address pool to be deleted in the "Global Address Pool Management" window, then click <Delete> and click <OK> to confirm the deletion in the pop up warning window.

24.4.4 Configuring Global Address Pool

Choose an address pool in the "Global Address Pool Management" window and click <Config…> to pop up the [Global Address Pool Configuration] window as shown in Figure 24-13.

Figure 24-13 Global Address Pool Configuration

In the window the configurable parameters including Router IP, Primary/Secondary DNS/WINS address. After modification, click <OK> to finish the operation.

24.4.5 Querying Statistics Information

Choose an address pool in the [Global Address Pool Management] window then click <Statistics…> to enter the [Global Address Pool Statistics] window as shown in Figure 24-14.


24-14

Figure 24-14 Global Address Pool Statistics


Table 24-7 Description of parameters of Global Address Pool Statistics

Name Description

Used Addresses Number of addresses being used in the pool

Unused Addresses Number of free addresses in the pool

Disabled Addresses Number of disabled addresses in the pool

Total Addresses Number of all addresses in the pool

24.4.6 Appending Disabled IP Segment

Choose an address pool in the [Global Address Pool Management] window and click <Append Disabled IP Segment…> to pop up "Disabled IP Segment Creation" window as shown in Figure 24-15.


24-15

Figure 24-15 Disabled IP Segment Creation


Table 24-8 Description of parameters of Disabled IP Segment Creation

Name Description

Pool Name Name of the pool to create a disabled segment

Low Address Start address of the disabled address segment

High Address Last address of the disabled address segment

Input the Low Address and the High Address in the window and click <OK> to finish the operation. Now new disabled segment can be seen in the window shown as in Figure 24-11.

24.4.7 Canceling Disabled IP Segment

Choose an address pool in the [Global Address Pool Management] then choose a disabled segment and click <Cancel Disabled IP Segment…> to enter the [Disabled IP Segment Cancellation] window as show in Figure 24-16.


24-16

Figure 24-16 Disabled IP Segment Cancellation

In the window, the length means the address range length to be cancelled, ranging from 1 to actual segment length. Input length value click <OK> to finish operation.

Note:

The first and the last address value in the disabled segment (the low and high address of “Disabled IP Segments”) cannot be cancelled.

24.5 DHCP Traffic Monitoring

This function uses graphical view to monitor all types of DHCP packet flow. The types of packets including: DISCOVER Messages, REQUEST Messages, RELEASE Messages, DECLINE Messages, INFORM Messages, Invalid Messages, OFFER Messages, ACK Messages, NACKS Messages and Discarded Messages.

In the function pane, double-click the [DHCP Management/DHCP Traffic Monitoring] on the function tree to open the [DHCP Traffic Monitoring] window as shown in Figure 24-17.


24-17

Figure 24-17 DHCP Traffic Monitoring

For detail operation procedures of DHCP Traffic Monitoring window, refer to Chapter 5 “Performance Monitoring”.

User Manual Volume I Quidview Device Manager Chapter 25 Frame Relay Management

25-1

Chapter 25 Frame Relay Management

25.1 Overview

Frame relay protocol is a simplified X.25 protocol. Frame relay networks enable data communication between data terminal equipment (DTE) and data circuit-terminal equipment (DCE). Frame relay networks can be public networks or the private networks of enterprises, or networks of directly-connected data devices.

Frame relay protocol is a statistical-multiplexing protocol; it provides multiple virtual circuits on a single physical channel. Each virtual circuit is identified by a data link connection identifier (DLCI). DLCI is only significant on local interfaces and the peer interface connected to it, in other words, the same DLCI on different interfaces does not necessarily identify the same virtual circuit. FR (frame relay) network interfaces support up to 1,024 virtual circuits and DLCI 16-1007 are open to users. As frame relay virtual circuits are connection-oriented and locally different DLCIs are connected to different peer devices, we may take the local DLCI as the peer device’s FR address.

Virtual circuits can be divided into two types based on how they are established: permanent virtual circuit (PVC) and switching virtual circuit (SVC). PVCs are manually established, while SVCs are automatically created and deleted by the protocol. Currently PVCs are more common.

25.2 Frame Relay DTE Management

25.2.1 DLCM Management

In the [DLCM (Data Link Connection Management) Management] tab, you can browse and configure the LMI (local management interface) protocol and protocol parameters for FR interfaces.

Start NMS of the router, choose the [Device/Start Device…] menu or click on on

the toolbar to open the panel view of a router. Double-click [Frame Relay Management/Frame Relay DTE Management] in the navigation window and the dialog box as shown in the following figure pops up.


25-2

Figure 25-1 DLCM Management dialog box

The dialog box displays the LMI protocol for frame relay interfaces and MFR (multilink frame relay) interfaces, and the corresponding protocol parameters.

For PVC mode, it is required to test if the virtual circuit is already available. LMI protocol is right for this purpose. The system supports three types of LMI protocols: ITU-T Q.933 Annex A, ANSI T1.617 Annex D and nonstandard compatibility protocol.

Their fundamental principle is like this:

The DTE sends a status-request message, which can be link integrity check message or link status query message, after a fixed interval (which is defined by T391). Upon receiving the request message, the DCE returns a status response message. If receiving no response within the defined time limit, the DTE records it as an error. If the number of this error type exceeds the defined threshold, the DTE reckons the physical channel (including all virtual circuits) is unavailable.

The following table summarizes the parameters in the DLCM Management dialog box.

Table 25-1 Parameter description for DLCM management


Interface Interface description

DLCM state

It refers to LMI type and can be q933a: ITU-T Q.933 Annex A ansi: ANSI T1.617 Annex D nostandard: Nonstandard compatibility protocol nonset: No LMI configured


25-3


Address format

It can be q921 q922March90 q922November90 q922

Address length

It can be two-octets three-octets four-octets

T391 (second) DTE sends a status-request message after an interval which is decided by T391.

N391 It defines the proportion for sending two status-request message types, which is number of link integrity check messages:number of link status query messages = N391-1:1.

N392 The defined error threshold

N393 Total number of the monitored events

Max. virtual circuits Maximum virtual circuits supported on the interface

Multicast service If multicast is supported

Choose a record in the dialog box and click <Config…> to configure LMI type and protocol parameters for the interface. Specifically, they include LMI type, status query interval, all status query interval, error threshold, monitored events. Click <OK> to end your configuration.

Figure 25-2 DLCM Configuration dialog box


25-4

25.2.2 Circuit Management


the toolbar to open the panel view of a router. Double-click the [Frame Relay Management/Frame Relay DTE Management] in the navigation window and the Frame Relay DTE Management dialog box pops up. Choose the Circuit Management tab and the corresponding dialog box pops up, in which you can browse, monitor in real time information about virtual circuits.

Figure 25-3 Circuit Management dialog box

This dialog box displays relatively detailed information about all virtual circuits, including interface, DLCI index, circuit state, creation time, last-time change, committed burst, burst size, and committed access rate.

Choose a record in the dialog box and click <Monitor…> to monitor in real time information of the target virtual circuit, including received FEC (forward error correction) messages, received BEC (backward error correction) messages, transmitted frames and received bytes.

25.2.3 Error Information


the toolbar to open the panel view of a router. Double-click the [Frame Relay Management/Frame Relay DTE Management] in the navigation window and the Frame


25-5

Relay DTE Management dialog box pops up. Choose the Error Information tab and corresponding dialog box pops up, in which you can browse error information of FR interfaces.

Figure 25-4 Error Information dialog box

The dialog box displays interface, error type, error data and error time. The error type can be unknownError, receiveShort, receiveLong, illegalDLCI, unknownDLCI, dlcmiProtoErr, dlcmiUnknownIE, dlcmiSequenceErr, dlcmiUnknownRpt and noErrorSinceReset.

25.2.4 Trap State Management


the toolbar to open the panel view of a router. Double-click the [Frame Relay Management/Frame Relay DTE Management] in the navigation window and the Frame Relay DTE Management dialog box pops up. Choose the Trap Stage Management tab and the corresponding dialog box pops up.


25-6

Figure 25-5 Trap State Management dialog box

In the dialog box, you can specify if to enable the device to send Trap messages to the specific destination address for network management when the PVC status changes.

25.3 Frame Relay Service Management

25.3.1 Logical Port Management


the toolbar to open the panel view of a router. Double-click the [Frame Relay Management/Frame Relay Service Management] in the navigation window and the Logical Port Management dialog box as shown in the following figure pops up.


25-7

Figure 25-6 Logical Port Management dialog box

This dialog box displays information about all FR interfaces and MFR interfaces.

An MFR (Multilink Frame Relay) interface is created by binding multiple FR physical links, to provide a higher-rate and higher-bandwidth link over the FR network.

The following table summarizes the fields in the dialog box.

Table 25-2 Parameter description for logical port management

Item Description

Interface Interface index

Logical port address length and DLCI length

Q.922 address length and DLCI length of the logical port

Logical port VC signaling protocol

It can be q933a: ITU-T Q.933 Annex A ansiT1-617-D: ANSI T1.617 Annex D nonstandard: Nonstandard compatibility protocol

Logical port type

It can be uni: Means the interface runs in frame relay mode. In frame relay mode, communication participants falls into user end (called DTE) and net end (called DCE). nni: Means the interface runs in FR network mode. In the FR network, switches use NNI interfaces for communication, so the interface type must be NNI.


25-8

Choose a record in the dialog box and click <Config…>, and then the Lport Parameter Configuration dialog box pops up, as shown in the following figure.

Figure 25-7 Logical Port Parameter Configuration dialog box

In this dialog box you can define port type and LMI type. Click <OK> to end your configuration.

25.3.2 LMI Parameter Management

LMI protocol is used to test if the virtual circuit is available, as well as to maintain the PVC table for frame relay protocol. It is required for PVC mode.


the toolbar to open the panel view of a router. Double-click the [Frame Relay Management/Frame Relay Service Management] in the navigation window and choose the LMI Parameter Management tab to enter the corresponding dialog box. In it you can browse and configure LMI parameters for the FR interfaces.


25-9

Figure 25-8 LMI Parameter Management dialog box

Choose a record in the dialog box and click <Monitor…>, and then you can monitor the numbers of LMI messages discarded at the user end and net end.

More details about the parameter in the dialog box are given in the following:

LMI signaling approach means different parameters are used for different interface types: u2nnet indicates the interface serves as DCE, and the available parameters include NetN392, NetN393 and NetT392. bidirect means the interface can serve both as DCE or DTE. u2nuser specifies the interface is as DTE, and the available parameters include UserN391, UserN392, UserN393 and UserT391.

The parameters related to DTE interface:

N391: The DTE sends a status-request message, which can be link integrity check message or link status query message, after a fixed interval (which is defined by T391). It defines the proportion for sending two status-request message types, which is number of link integrity check messages:number of link status query messages = N391-1:1.

N392: Defined error threshold N393: Total number of the monitored events

The DTE sends a status-request message, which can be link integrity check message or link status query message, after a fixed interval (which is defined by T391). Upon receiving the request message, the DCE returns a status response message. If receiving no response within the defined time limit, the DTE records it as an error. If the number of this error type exceeds the defined threshold, the DTE reckons the physical channel (including all virtual circuits) is unavailable. The parameters N392 and N393 jointly define the error threshold: if the error number reaches N392 among the N393


25-10

status-request messages sent by DTE, DTE reckons that the error threshold is reached and that the physical channel (all virtual circuits) are unavailable.

T391: A time variable, defining the time interval when the DTE originates a status-request message.

The parameters related to DCE interface:

The parameters N392 and N393 here are similar to those for DTE interface. The difference lies in that at DCE the interval for DTE to originate a status-request message is defined by T392, versus it is determined by T391 for DTE. If receiving no status-request messages within the time limit defined by T392 from the DTE, the DCE records it as an error.

T392: A time variable, defining maximum time period for the DCE to wait for a status-request message. It is greater than T391.

Choose a record in the dialog box and click <Config…>, and then the VC Signaling Parameter Configuration dialog box pops up, as shown in the following figure.

Figure 25-9 VC Signaling Parameter Configuration dialog box

In this dialog box, you can configure LMI protocol parameters for the interface. Click <OK> to end your configuration.

25.3.3 PVC End-points Management


the toolbar to open the panel view of a router. Double-click the [Frame Relay


25-11

Management/Frame Relay Service Management] in the navigation window and choose the PVC End-points Management tab to enter the corresponding dialog box. In it you can browse and configure information for PVC end points.

Figure 25-10 PVC End-points Management dialog box

Choose a record in the dialog box and click <Monitor…>, and then you can monitor these information types: counts of PVC-received frames, PVC-sent frames, PVC-received frames which exceed BC (committed burst), PVC-discarded frames, PVC-sent bytes and PVC-received bytes.

The dialog box displays information about the established PVCs, including interface, CLCI index and PVC status of the received peer LMI reports. The last field is only available for the DTE, since only for the DTE, its PVC status is decided by DCE. For NNI interfaces, their PVC status is determined jointly by the peer LMI reports received at both ends.

Click <Add…> in the dialog box and the PVC End-point Creating dialog box (see the following figure) appears, in which you can add a new PVC.


25-12

Figure 25-11 PVC End-point Creating dialog box

Click <OK> to end your PV6C adding.

25.3.4 PVC Connection Management


the toolbar to open the panel view of a router. Double-click the [Frame Relay Management/Frame Relay Service Management] in the navigation window and choose the [PVC Connection Management] tab to enter the corresponding dialog box. In it you can browse and configure information for PVC connections.

Figure 25-12 PVC Connection Management dialog box


25-13

This dialog box displays information about PVC connections for FR switching, including low interface, low DLCI, high interface, high DLCI, administrative status, low-to-high operation status, high-to-low operation status user name, connection provider.

I. Adding a PVC

Click <Add…> in the dialog box and the [PVC Connection] dialog box (see the following figure) appears, in which you can add a new PVC connection for FR switching.

Figure 25-13 PVC Connection Creating dialog box

After setting parameters for the new PVC connection, you can click <OK> to end your configuration.

Note:

You cannot choose the same port both as low interface and as high interface.

II. Deleting a PVC

Choose one or more records in the [PVC Connection Management] dialog box and click <Delete> to delete the target PVC connections.

III. Configuring a PVC

Choose a record in the [PVC Connection Management] dialog box and click <Config…> to configure user name and provider for this connection.

En Quidview Adoc Device Manager UM I V3.11(20060809)

Documents

Transcript of En Quidview Adoc Device Manager UM I V3.11(20060809)