Vivotek VivoCam AW-GEV-104B-130, VivoCam AW-GEV-184B-250, VivoCam AW-GEV-264B-370 User Manual

Download

AW-GEV-104B-130 AW-GEV-184B-250 AW-GEV-264B-370

VivoCam Web Smart Managed PoE Switch

User Manual

Rev. 2.0

For firmware version 0003

About This Manual

Copyright © 2017 VIVOTEK Inc. All rights reserved. The products and programs described in this User Guide are licensed products of VIVOTEK Inc., This User Guide contains proprietary information protected by copyright, and this User Guide and all accompanying hardware, software and documentation are copyrighted. No parts of this User Guide may be copied, photocopied, reproduced, translated or reduced to any electronic medium or machine-readable from by any means by electronic or mechanical. Including photocopying, recording, or information storage and retrieval systems, for any purpose other than the purchaser’s personal use, and without the prior express written permission of VIVOTEK Inc.

Purpose

This GUI user guide gives specific information on how to operate and use the management functions of the AW-GEV series switch via HTTP/HTTPs web browser

Audience

The Manual is intended for use by network administrators who are responsible for operating and maintaining network equipment; consequently, it assumes a basic working knowledge of general switch functions, the Internet Protocol (IP), and Hypertext Transfer Protocol (HTTP).

CONVENTIONS

The following conventions are used throughout this manual to show information.

WARRANTY

See the Customer Support/ Warranty booklet included with the product. A copy of the specific warranty terms applicable to your VIVOTEK products and replacement parts can be obtained from your VIVOTEK Sales and Service Office authorized dealer.

Disclaimer

VIVOTEK does not warrant that the hardware will work properly in all environments and applications, and marks no warranty and representation, either implied or expressed, with respect to the quality, performance, merchantability, or fitness for a particular purpose. VIVOTEK disclaims liability for any inaccuracies or omissions that may have occurred. Information in this User Guide is subject to change without notice and does not represent a commitment on the part of VIVOTEK. VIVOTEK assumes no responsibility for any inaccuracies that may be contained in this User Guide. VIVOTEK makes no commitment to update or keep current the information in this User Guide, and reserves the righter to make improvements to this User Guide and /or to the products described in this User Guide, at any time without notice.

NOTE:

For users who use this switch in a surveillance application, you can go directly to Chapter 13 for information directly related to surveillance deployments.

Table of Contents

ABOUT THIS MANUAL ................................................................................................................................ II

Revision History ......................................................................................................................................... vii

INTRODUCTION ........................................................................................................................................... 1

CHAPTER 1 OPERATION OF WEB-BASED MANAGEMENT ............................................................ 3

CHAPTER 2 SYSTEM ............................................................................................................................ 7

2-1 SYSTEM INFORMATION ................................................................................................................................... 7

2-2 IP ADVANCE .................................................................................................................................................. 9

2-2.1 IP Configuration ................................................................................................................................ 9

2-2.2 IP Status ............................................................................................................................................ 13

2-3 SYSTEM TIME ............................................................................................................................................... 15

2-4 LOG ............................................................................................................................................................ 19

2-4.1 Syslog Configuration ....................................................................................................................... 19

2-4.2 View Log ........................................................................................................................................... 21

2-5 LLDP .......................................................................................................................................................... 23

2-5.1 LLDP Configuration ......................................................................................................................... 23

2-5.2 LLDP-MED Configuration ............................................................................................................... 26

2-5.3 LLDP Neighbour .............................................................................................................................. 33

2-5.4 LLDP-MED Neighbour ..................................................................................................................... 35

2-5.5 LLDP Statistics .................................................................................................................................. 39

2-6 UPNP ......................................................................................................................................................... 41

CHAPTER 3 PORT MANAGEMENT .................................................................................................. 43

3-1 PORT CONFIGURATION ................................................................................................................................. 43

3-2 PORT STATISTICS .......................................................................................................................................... 46

3-3 SFP PORT INFO ........................................................................................................................................... 50

3-4 ENERGY EFFICIENT ETHERNET ....................................................................................................................... 52

3-5 LINK AGGREGATION ..................................................................................................................................... 53

3-5.1 Port ................................................................................................................................................... 53

3-5.2 Aggregator View .............................................................................................................................. 55

3-5.3 Aggregation Hash Mode ................................................................................................................. 57

3-5.4 LACP System Priority ....................................................................................................................... 59

3-6 LOOP PROTECTION ...................................................................................................................................... 60

3-6.1 Configuration ................................................................................................................................... 60

3-6.2 Status ................................................................................................................................................ 62

CHAPTER 4 POE MANAGEMENT ..................................................................................................... 64

4-1 POE CONFIGURATION .................................................................................................................................. 64

4-2 POE STATUS ................................................................................................................................................ 66

CHAPTER 5 VLAN MANAGEMENT .................................................................................................. 68

5-1 VLAN CONFIGURATION ............................................................................................................................... 68

5-2 VLAN MEMBERSHIP .................................................................................................................................... 72

5-3 VLAN PORT STATUS .................................................................................................................................... 74

CHAPTER 6 QUALITY OF SERVICE ................................................................................................... 76

6-1 GLOBAL SETTINGS........................................................................................................................................ 76

6-2 PORT SETTINGS ........................................................................................................................................... 78

6-3 PORT POLICING ........................................................................................................................................... 80

6-4 PORT SHAPER .............................................................................................................................................. 81

6-5 STORM CONTROL ........................................................................................................................................ 83

6-6 PORT SCHEDULER ........................................................................................................................................ 85

6-7 COS/802.1P MAPPING ............................................................................................................................... 86

6-8 COS/802.1P REMARKING ............................................................................................................................ 87

6-9 IP PRECEDENCE MAPPING ............................................................................................................................ 88

6-10 IP PRECEDENCE REMARKING ...................................................................................................................... 89

6-11 DSCP MAPPING ....................................................................................................................................... 90

6-12 DSCP REMARKING .................................................................................................................................... 91

CHAPTER 7 SPANNING TREE ........................................................................................................... 92

7-1 STATE .......................................................................................................................................................... 92

7-2 REGION CONFIG .......................................................................................................................................... 94

7-3 INSTANCE VIEW ........................................................................................................................................... 95

CHAPTER 8 MAC ADDRESS TABLES ............................................................................................. 102

8-1CONFIGURATION ........................................................................................................................................ 102

8-2 INFORMATION ........................................................................................................................................... 105

CHAPTER 9 MULTICAST ................................................................................................................. 107

9-1 IGMP SNOOPING ...................................................................................................................................... 107

9-1.1 Basic Configuration ....................................................................................................................... 107

9-1.2 VLAN Configuration ...................................................................................................................... 110

9-1.3 Status .............................................................................................................................................. 112

9-1.4 Group Information......................................................................................................................... 114

9-1.5 IGMP SFM Information .................................................................................................................. 116

CHAPTER 10 SECURITY ................................................................................................................... 118

10-1 MANAGEMENT ........................................................................................................................................ 118

10-2 IEEE 802.1X ........................................................................................................................................... 122

10-2.1 Configuration ............................................................................................................................... 122

10-2.2 Status ............................................................................................................................................ 125

10-3 PORT SECURITY ....................................................................................................................................... 127

10-3.1 Configuration ............................................................................................................................... 127

10-3.2 Status ............................................................................................................................................ 130

10-4 RADIUS ................................................................................................................................................. 132

10-4.1 Configuration ............................................................................................................................... 132

10-4.2 Status ............................................................................................................................................ 135

CHAPTER 11 DIAGNOSTICS ........................................................................................................... 140

11-1 PING ....................................................................................................................................................... 140

11-2 CABLE DIAGNOSTICS ................................................................................................................................ 142

11-3 TRACEROUTE ........................................................................................................................................... 143

11-4 MIRROR .................................................................................................................................................. 144

CHAPTER 12 MAINTENANCE ......................................................................................................... 146

12-1 CONFIGURATION ..................................................................................................................................... 146

12-1.1 Save startup-config ..................................................................................................................... 146

12-1.2 Backup config .............................................................................................................................. 148

12-1.3 Restore config .............................................................................................................................. 149

12-1.4 Activate config ............................................................................................................................. 150

12-1.5 Delete config ................................................................................................................................ 151

12-2 RESTART DEVICE ...................................................................................................................................... 152

12-3 FACTORY DEFAULTS .................................................................................................................................. 153

12-4 FIRMWARE .............................................................................................................................................. 154

12-4.1 Firmware Upgrade ...................................................................................................................... 154

CHAPTER 13 SURVEILLANCE - GRAPHICAL MONITORING ......................................................... 155

13-1 OVERVIEW ................................................................................................................................................. 155

GRAPHICAL MONITORING ...................................................................................................................................... 157

TOPOLOGY VIEW .............................................................................................................................................. 157

FLOOR VIEW .................................................................................................................................................... 165

MAP VIEW ....................................................................................................................................................... 167

MANAGEMENT………………………………………………………………………………………………………………………………………… 168

DEVICE LIST ..................................................................................................................................................... 168

VVTK CAMERA & ENCODER……………………………………………………………………………………………………………………….169 CAMERA CONFIGURE………………………………………………………………………………………………………………………………..170

MAINTENANCE ............................................................................................................................................ 171

vii

Revision History

Hardware Reset / Mode Button

The reset button is used to reboot the PoE switch or to restore the factory default settings. Sometimes resetting the system can return the PoE switch to normal operation. If the system problems remain after reset, restore the factory settings and try again.

Reboot: Press 3~10 seconds and release the recessed reset button. Wait for the PoE Switch to reboot. Reset to factory default: Press longer than 10 seconds and release the recessed reset button. Wait for the PoE

Switch to reset to factory default & Reboot. The mode button is use to switch LED indicator’s mode. Link / ACT/ Speed: Press shorter than 3 seconds and release the recessed mode button. The Link / ACT/ Speed

LED will on. Green when displaying Link/ACT/Speed status of Ethernet ports.

PoE : Press shorter than 3 seconds and release the recessed mode button. The PoE LED will turn on. Green when displaying the PoE link status with powered devices.

Release

Date

Revision

Initial Release

2016/08/25

1.0

FW0003 Release

2017/09/05

2.0

Publication date: Jun., 2016

Revision A1

INTRODUCTION

Overview

In this User Guide, it will not only tell you how to install and connect your network system but configure and monitor the AW-GEV-104B-130, AW-GEV-184B-250, or AW-GEV-264B-370 through the web by (RJ-45) serial interface and Ethernet ports step-by-step. Many explanations in detail of hardware and software functions are shown as well as the examples of the operation for web-based interface.

The AW-GEV series switches are the next generation web smart+ managed switch from VIVOTEK, is a portfolio of affordable managed switches that provides a reliable infrastructure for your business network. These switches deliver more intelligent features you need to improve the availability of your critical business applications, protect your sensitive information, and optimize your network bandwidth to deliver information and applications more effectively. It provides the ideal combination of affordability and capabilities for entry level networking includes small business or enterprise application and helps you create a more efficient, better-connected workforce.

The AW-GEV series Web Smart+ Managed Switches provide 10/18/26 ports in a single device; the specification is highlighted as follows.

 DHCP Server & Client & Relay & Snooping  QoS Hardware Queues, Classification, Rate Limiting, Priority Queue Scheduling  Tag-Based VLAN, Port-Based VLAN, Protocol-Based VLAN, IP Subnet-Based VLAN,

MAC-Based VLAN

 Private VLAN Edge (PVE), Voice VLAN, Q-in-Q VLAN, GVRP VLAN  Multicast VLAN Registration (MVR)  802.1d (STP), 802.1w (RSTP), 802.1s (MSTP) & Loop Protection  IEEE802.3ad LACP and Static Link Aggregation  IGMP Snooping v1/v2 & Querer & Proxy  SNMP v1/v2c/v3 User-Based Security Model (USM)  IEEE802.1x RADIUS & TACACS+ Authentication  SSH/SSL Secured Management  IP Source Guard  IEEE802.3az Energy-Efficient Ethernet

Overview of this User Guide

 Chapter 1 “Operation of Web-based Management”

 Chapter 2 “System”

 Chapter 3 “Port Management”

 Chapter 4 “PoE Management”

 Chapter 5 “VLAN Management”

 Chapter 6 “Quality of Service”

 Chapter 7 “Spanning tree”

 Chapter 8 “MAC Address Tables”

 Chapter 9 “Multicast”

 Chapter 10 “Security”

 Chapter 11 “Diagnostics”

 Chapter 12 “Maintenance”

 Chapter 13 "Surveillance"

Publication date: Jul., 2016

Revision A1

Chapter 1 Operation of Web-based Management

Initial Configuration

IMPORTANT:

1. It is recommended to use IE10 or IE11 to open a web console with the

PoE switch.

2. This PoE switch is specifically designed for surveillance applications. It

comes with an integrated Surveillance interface for ease of configuration. The interface is accessed through a tabbed menu, and the configuration changes made in its window have a higher priority than those in the Switch configuration menus.

This chapter instructs you how to configure and manage the switch through the web user interface. With this facility, you can easily access and monitor through any one port of the switch all the status of the switch, including MIBs status, each port activity, Spanning tree status, port aggregation status, multicast traffic, VLAN and priority status, even illegal access record and so on.

The default values of the AW-GEV series switches are listed in the table

below:

IP Address

DHCP client

Subnet Mask

255.255.255.0

Default Gateway

N/A

Username

admin

Password

admin

You can find the PoE switch using VIVOTEK’s IW2 utility. If network address conflicts occur, use this utility to locate the PoE switch.

If you enabled the onboard DHCP server on the PoE switch, you can browse it. For instance, type http://192.168.1.1 in the address row in a browser, it will display the following screen and ask you to enter a username and password in order to login and access authentication.

The default username is “admin” and password is admin. For the first time to use, please enter the default username and password, and then click the

<Login> button. The login process now is completed. In this login menu,

you have to input the complete username and password respectively, the AW-GEV switch will not give you a shortcut to username automatically. This

looks inconvenient, but safer.

The AW-GEV switch allows two or more users to manage the switch using the administrator’s identity. The configuration changes made will take effect depending on who made the last configuration change.

This chapter instructs you how to configure and manage the AW-GEV switch through the web user interface. With this facility, you can easily access and monitor through any one port of the switch all the status of the switch, including MIBs status, each port activity, Spanning tree status, port aggregation status, multicast traffic, VLAN and priority status, even illegal access record and so on.

After the AW-GEV switch has been finished configuration it interface, you can browse it. For instance, type http://192.168.1.1 in the address row in a browser, it will display the following screen and ask you inputting username and password in order to login and access authentication.

If you double-click on the entry found on the IW2 utility, an IE console will be opened. If you prefer using Firefox or Google Chrome, you can manually enter the IP address in your browser’s URL field.

A startup wizard page will prompt the first time you access the switch. The first step is to configure a password for access security.

If necessary, configure a static IP for the switch. Click Next to proceed.

You can then configuration the data and time setting for the switch either by assigning a network time server or manually enter the values using the calendar.

You should enter additional information such as system contact and system location. When done, click the Apply button.

The default username is “admin” and password is empty. For the first time to use, please enter the default username and password, and then click the <Login> button. The login process now is completed. In this login menu, you have to input the complete username and password respectively, the AW-GEV switch will not give you a

shortcut to username automatically. This looks inconvenient, but safer.

The AW-GEV switch allows two or more users using administrator’s identity to manage this switch, which administrator to do the last setting, it will be an available configuration to effect the system.

NOTE:

When you login the Switch WEB page to manage. You must first type the Username of the admin. Password was blank, so when you type after the end Username, please press enter. Management page to enter WEB.

When you login AW-GEV series switch Web UI management, you can use both ipv4 ipv6 login to manage

To optimize the display effect, we recommend you use Microsoft IE 6.0 above, Netscape V7.1 above or Firefox V1.00 above and have the resolution 1024x768. The switch supported neutral web browser interface

NOTE:

AS AW-GEV switch the function enable dhcp, so If you do not have DHCP server to provide ip addresses to the switch, the Switch default ip

192.168.1.1

Figure 1: The login page

Chapter 2 System

This chapter describes the entire basic configuration tasks which includes the System Information and any management parameters of the Switch (e.g. Time, Account, IP, Syslog, and NTP.)

2-1 System Information

You can identify the system by configuring system name, location and the contact of the switch.

The switch system’s contact information is provided here.

Web interface

To configure System Information in the web interface:

1. Click System and System Information.

2. Write System Name, Location, Contact information in this page.

3. Click Apply

Figure 2-1: System Information

Parameter description:  System name :

An administratively assigned name for this managed node. By convention, this is the node's fully-qualified domain name. A domain name is a text string drawn from the alphabet (A-Z, a-z), digits (0-9), minus sign (-). No space characters are permitted as part of a name. The first character must be an alpha character. And the first or last character must not be a minus sign. The allowed string length is 0 to 128.

 Location :

The physical location of this node(e.g., telephone closet, 3rd floor). The allowed string length is 0 to 128, and the allowed content is the ASCII characters from 32 to 1.

 Contact :

The textual identification of the contact person for this managed node, together with information on how to contact this person. The allowed string length is 0 to 128, and the allowed content is the ASCII characters from 32 to 126.

Publication date: Jul., 2016

Revision A1

2-2 IP Address 2-2.1 IP Settings

IPv4 DHCP Enable:

Enables the DHCP client mode setting for listening to a DHCP server in the local network.

IPv4 Address:

The IPv4 address of the interface VLAN1.

Subnet mask:

The IPv4 network mask of the interface VLAN1.

DNS Server:

Select the source of DNS service.

1. No DNS server.

2. Configured: User defined.

3. From any DHCP interfaces: as provided by a router offering the DHCP service

4. From this DHCP interface: If a router exists in a specific VLAN configuration, listen to the particular router for the DNS service.

Figure 2-2.1: IP Settings

2-2.2 Advanced IP Settings

The IPv4 address for the switch could be obtained via DHCP Server for VLAN 1. To manually configure an address, you need to change the switch's default settings to values that are compatible with your network. You may also need to establish a default gateway between the switch and management stations that exist on another network segment.

Configure the switch-managed IP information on this page

Configure IP basic settings, control IP interfaces and IP routes.

The maximum number of interfaces supported is 8 and the maximum number of routes is 8.

Web Interface

To configure an IP configuration in the web interface:

1. Click System, IP Advance and IP Configuration.

2. Click Add Interface then you can create new Interface on the switch.

3. Click Add Route then you can create new Route on the switch

4. Click Apply

Figure 2-2.2: The IP configuration

Parameter description:

IP Configuration  DNS Server :

This setting controls the DNS name resolution done by the switch. The following modes are supported:

 No DNS server

No DNS server will be used.

 Configured

Explicitly provide the IP address of the DNS Server in dotted decimal notation.

 From this DHCP interface

Specify from which DHCP-enabled interface a provided DNS server should be preferred.

 From any DHCP interfaces

The first DNS server offered from a DHCP lease to a DHCP-enabled interface will be used.

IP Interfaces

 Delete :

Select this option to delete an existing IP interface.

 VLAN :

The VLAN associated with the IP interface. Only ports in this VLAN will be able to access the IP interface. This field is only available for input when creating an new interface.

 IPv4 DHCP Enabled :

Enable the DHCP client by checking this box. If this option is enabled, the system will configure the IPv4 address and mask of the interface using the DHCP protocol. The DHCP client will announce the configured System Name as hostname to provide DNS lookup.

 IPv4 DHCP Fallback Timeout :

The number of seconds for trying to obtain a DHCP lease. After this period expires, a configured IPv4 address will be used as IPv4 interface address. A value of zero disables the

fallback mechanism, such that DHCP will keep retrying until a valid lease is obtained. Legal values are 0 to 4294967295 seconds.

 IPv4 DHCP Current Lease :

For DHCP interfaces with an active lease, this column show the current interface address, as provided by the DHCP server.

 IPv4 Address :

The IPv4 address of the interface in dotted decimal notation. If DHCP is enabled, this field is not used. The field may also be left blank if IPv4 operation on the interface is not desired.

 IPv4 Mask :

The IPv4 network mask, in number of bits (prefix length). Valid values are between 0 and 30 bits for a IPv4 address. If DHCP is enabled, this field is not used. The field may also be left blank if IPv4 operation on the interface is not desired.

 IPv6 Address :

The IPv6 address of the interface. A IPv6 address is in 128-bit records represented as eight fields of up to four hexadecimal digits with a colon separating each field (:). For example, fe80::215:c5ff:fe03:4dc7. The symbol :: is a special syntax that can be used as a shorthand way of representing multiple 16-bit groups of contiguous zeros; but it can appear only once. It can also represent a legally valid IPv4 address. For example, ::192.1.2.34. The field may be left blank if IPv6 operation on the interface is not desired.

 IPv6 Mask :

The IPv6 network mask, in number of bits (prefix length). Valid values are between 1 and 128 bits for a IPv6 address. The field may be left blank if IPv6 operation on the interface is not desired.

IP Routes

 Delete :

Select this option to delete an existing IP route.

 Network :

The destination IP network or host address of this route. Valid format is dotted decimal notationor a valid IPv6 notation. A default route can use the value 0.0.0.0or IPv6 :: notation.

 Mask Length :

The destination IP network or host mask, in number of bits (prefix length). It defines how much of a network address that must match, in order to qualify for this route. Valid values are between 0 and 32 bits respectively 128 for IPv6 routes. Only a default route will have a mask length of 0 (as it will match anything).

 Gateway :

The IP address of the IP gateway. Valid format is dotted decimal notationor a valid IPv6 notation. Gateway and Network must be of the same type.

 Next Hop VLAN (Only for IPv6) :

The VLAN ID (VID) of the specific IPv6 interface associated with the gateway. The given VID ranges from 1 to 4094 and will be effective only when the corresponding IPv6 interface is valid. If the IPv6 gateway address is link-local, it must specify the next hop VLAN for the gateway. If the IPv6 gateway address is not link-local, system ignores the next hop VLAN for the gateway.

Buttons

 Add Interface :

Click to add a new IP interface. A maximum of 8 interfaces is supported.

 Add Route :

Click to add a new IP route. A maximum of 8 routes is supported.

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

NOTE: If you configure switches and IP cameras to be using static IPs, make sure to

configure the same gateway value and subnet settings for IP cameras under IP routers for all switches to work properly on the Topology view.

2-2.2 IP Status

This page displays the status of the IP protocol layer. The status is defined by the IP interfaces, the IP routes and the neighbour cache (ARP cache) status.

Web Interface

To display the log configuration in the web interface:

1. Click System, IP Advance and IP Status.

2. Display the IP Configuration information.

Figure 2-2.2: The IP Status

Parameter description:

IP Interfaces

 Interface :

Show the name of the interface.

 Type :

Show the address type of the entry. This may be LINK or IPv4.

 Address :

Show the current address of the interface (of the given type).

 Status :

Show the status flags of the interface (and/or address).

IP Routes

 Network :

Show the destination IP network or host address of this route.

 Gateway :

Show the gateway address of this route.

 Status :

Show the status flags of the route.

 Interface:

Show the name of the interface.

Neighbour cache

 IP Address :

Show the IP address of the entry.

 Link Address :

Show the Link (MAC) address for which a binding to the IP address given exist.

Buttons

Figure 2-2.2: The IP Status buttons

 Auto-refresh :

Check this box to refresh the page automatically. Automatic refresh occurs every 3 seconds.

 Refresh :

Click to refresh the page immediately.

2-3 System Time

The switch provides manual and automatic ways to set the system time via NTP. Manual setting is simple and you just input “Year”, “Month”, “Day”, “Hour” and “Minute” within the valid value range indicated in each item.

Web Interface

To configure Time in the web interface:

1. Click System and System Time

2. Specify the Time parameter.

3. Click Apply.

Figure 2-3: The time configuration

Parameter description:

Time Configuration

 Clock Source :

There are two modes for configuring how the Clock Source from. Select "Local Settings" : Clock Source from Local Time. Select "NTP Server" : Clock Source from NTP Server.

 System Date :

Show the current time of the system. The year of system date limits between 2001 and 2037.

Time Zone Configuration

 Time Zone :

Lists various Time Zones worldwide. Select appropriate Time Zone from the drop down and click Apply to set.

 Acronym :

User can set the acronym of the time zone. This is a User configurable acronym to identify the time zone. (Range: Up to 16 characters)

Daylight Saving Time Configuration

 Daylight Saving Time :

This is used to set the clock forward or backward according to the configurations set below for a defined Daylight Saving Time duration. Select 'Disable' to disable the Daylight Saving Time configuration. Select 'Recurring' and configure the Daylight Saving Time duration to repeat the configuration every year. Select 'Non-Recurring' and configure the Daylight Saving Time duration for single time configuration. (Default: Disabled).

Recurring Configuration

 Start time settings :

Week - Select the starting week number.

Day - Select the starting day.

Month - Select the starting month.

Hours - Select the starting hour.

 End time settings :

Week - Select the ending week number.

Day - Select the ending day.

Month - Select the ending month.

Hours - Select the ending hour.

 Offset settings :

Offset - Enter the number of minutes to add during Daylight Saving Time. (Range: 1 to 1440)

NOTE: The under “Start Time Settings” and “End Time Settings” was

displayed what you set on the “Start Time Settings” and “End Time Settings” field information.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

Figure 4-4: The Configure NTP Server button

 Configure NTP Server :

Click to configure NTP server, When Clock Source select from NTP Server.

Figure 4-4: The SNTP configuration

NTP is Network Time Protocol and is used to sync the network time based Greenwich Mean Time (GMT). If use the NTP mode and select a built-in NTP time server or manually specify an user-defined NTP server as well as Time Zone, the switch will sync the time in a short after pressing <Apply> button. Though it synchronizes the time automatically, NTP does not update the time periodically without user’s processing.

Time Zone is an offset time off GMT. You have to select the time zone first and then perform time sync via NTP because the switch will combine this time zone offset and updated NTP time to come out the local time, otherwise, you will not able to get the correct time. The switch supports configurable time zone from –12 to +13 step 1 hour.

Default Time zone: +8 Hrs.

Parameter description :  Server 1 to 6:

Provide the NTP IPv4 or IPv6 address of this switch. IPv6 address is in 128-bit records represented as eight fields of up to four hexadecimal digits with a colon separating each field (:). For example, 'fe80::215:c5ff:fe03:4dc7'. The symbol '::' is a special syntax that can be used as a shorthand way of representing multiple 16-bit groups of contiguous zeros; but it can only appear once. It can also represent a legally valid IPv4 address. For example, '::192.1.2.34'.

 Interval

You can specify the time interval in seconds after which a time check and, in case of deviation, a resynchronization of the internal device clock against the specified timeserver via Network Time Protocol(NTP) should be performed.

Buttons

These buttons are displayed on the SNTP page:

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

2-4 Log

2-4.1 Syslog Configuration

The Syslog Configuration is a standard for logging program messages . It allows separation of the software that generates messages from the system that stores them and the software that reports and analyzes them. It can be used as well a generalized informational, analysis and debugging messages. It is supported by a wide variety of devices and receivers across multiple platforms.

Web Interface

To configure Syslog Configuration in the web interface:

1. Click System, Log and Syslog Configuration.

2. Specify the syslog parameters include IP Address of Syslog server and Port number.

3. Evoke the Syslog to enable it.

4. Click Apply.

Figure 2-4.1: The System Log configuration

Parameter description:  Mode :

Indicate the server mode operation. When the mode operation is enabled, the syslog message will send out to syslog server. The syslog protocol is based on UDP communication and received on UDP port 514 and the syslog server will not send acknowledgments back sender since UDP is a connectionless protocol and it does not provide acknowledgments. The syslog packet will always send out even if the syslog server does not exist. Possible modes are:

On: Enable server mode operation.

Off: Disable server mode operation.

 Server 1 to 6 :

Indicates the IPv4 hosts address of syslog server. If the switch provide DNS feature, it also can be a host name.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

2-4.2 View Log

This section describes that display the system log information of the switch

Web Interface

To display the log configuration in the web interface:

1. Click System, Log and View Log.

2. Display the log information.

Figure 2-4.2: The System Log Information

Parameter description:  ID :

ID (>= 1) of the system log entry.

 Level :

level of the system log entry. The following level types are supported:

Debug : debug level message.

Info : informational message.

Notice : normal, but significant, condition.

Warning : warning condition.

Error : error condition.

Crit : critical conditions.

Alert : action must be taken immediately.

Emerg : system is unusable.

 Time :

It will display the log record by device time. The time of the system log entry.

 Message :

It will display the log detail message. The message of the system log entry.

 Search :

You can search for the information that you want to see.

 Show entries :

You can choose how many items you want to show off.

Buttons

 Refresh :

Updates the system log entries, starting from the current entry ID.

 Clear Logs :

Clear all the system log entries.

 Next :

Updates the system log entries, turn to the next page.

 Previous :

Updates the system log entries, turn to the previous page.

2-5 LLDP

The switch supports the LLDP. For current information on your switch model, The Link Layer Discovery Protocol (LLDP) provides a standards-based method for enabling switches to advertise themselves to adjacent devices and to learn about adjacent LLDP devices. The Link Layer Discovery Protocol (LLDP) is a vendor-neutral Link Layer protocol in the Internet Protocol Suite used by network devices for advertising their identity, capabilities, and neighbors on a IEEE 802 local area network, principally wired Ethernet. The protocol is formally referred to by the IEEE as Station and Media Access Control Connectivity Discovery specified in standards document IEEE 802.1AB.

2-5.1 LLDP Configuration

You can per port to do the LLDP configuration and the detail parameters, the settings will take effect immediately. This page allows the user to inspect and configure the current LLDP port settings.

Web Interface

To configure LLDP:

1. Click System, LLDP and LLDP configuration.

2. Modify LLDP timing parameters

3. Set the required mode for transmitting or receiving LLDP messages

4. Specify the information to include in the TLV field of advertised messages

5. Click Apply

Figure 2-5.1: The LLDP Configuration

Parameter description:

LLDP Parameters

 Tx Interval :

The switch periodically transmits LLDP frames to its neighbours for having the network discovery information up-to-date. The interval between each LLDP frame is determined by the Tx Interval value. Valid values are restricted to 5 - 32768 seconds.

 Tx Hold :

Each LLDP frame contains information about how long the information in the LLDP frame shall be considered valid. The LLDP information valid period is set to Tx Hold multiplied by Tx Interval seconds. Valid values are restricted to 2 - 10 times.

 Tx Delay :

If some configuration is changed (e.g. the IP address) a new LLDP frame is transmitted, but the time between the LLDP frames will always be at least the value of Tx Delay seconds. Tx Delay cannot be larger than 1/4 of the Tx Interval value. Valid values are restricted to 1 8192 seconds.

 Tx Reinit :

When a port is disabled, LLDP is disabled or the switch is rebooted, an LLDP shutdown frame is transmitted to the neighboring units, signaling that the LLDP information isn't valid anymore. Tx Reinit controls the amount of seconds between the shutdown frame and a new LLDP initialization. Valid values are restricted to 1 - 10 seconds.

LLDP Port Configuration

The LLDP port settings relate to the currently selected, as reflected by the page header.

 Port :

The switch port number of the logical LLDP port.

 Mode :

Select LLDP mode.

Rx only The switch will not send out LLDP information, but LLDP information from neighbor units is analyzed.

Tx only The switch will drop LLDP information received from neighbors, but will send out LLDP information.

Disabled The switch will not send out LLDP information, and will drop LLDP information received from neighbors.

Enabled the switch will send out LLDP information, and will analyze LLDP information received from neighbors.

 CDP Aware :

Select CDP awareness.

The CDP operation is restricted to decoding incoming CDP frames (The switch doesn't transmit CDP frames). CDP frames are only decoded if LLDP on the port is enabled.

Only CDP TLVs that can be mapped to a corresponding field in the LLDP neighbors’ table are decoded. All other TLVs are discarded (Unrecognized CDP TLVs and discarded CDP frames are not shown in the LLDP statistics.). CDP TLVs are mapped onto LLDP neighbors’ table as shown below.

CDP TLV "Device ID" is mapped to the LLDP "Chassis ID" field.

CDP TLV "Address" is mapped to the LLDP "Management Address" field. The CDP address TLV can contain multiple addresses, but only the first address is shown in the LLDP neighbors’ table.

CDP TLV "Port ID" is mapped to the LLDP "Port ID" field.

CDP TLV "Version and Platform" is mapped to the LLDP "System Description" field.

Both the CDP and LLDP support "system capabilities", but the CDP capabilities cover capabilities that are not part of the LLDP. These capabilities are shown as "others" in the LLDP neighbors’ table.

If all ports have CDP awareness disabled the switch forwards CDP frames received from neighbor devices. If at least one port has CDP awareness enabled all CDP frames are terminated by the switch.

NOTE: When CDP awareness on a port is disabled the CDP

information isn't removed immediately, but gets when the hold time is exceeded.

 Port Descr :

Optional TLV: When checked the "port description" is included in LLDP information transmitted.

 Sys Name :

Optional TLV: When checked the "system name" is included in LLDP information transmitted.

 Sys Descr :

Optional TLV: When checked the "system description" is included in LLDP information transmitted.

 Sys Capa :

Optional TLV: When checked the "system capability" is included in LLDP information transmitted.

 Mgmt Addr :

Optional TLV: When checked the "management address" is included in LLDP information transmitted.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

2-5.2 LLDP-MED Configuration

Media Endpoint Discovery is an enhancement of LLDP, known as LLDP-MED that provides the following facilities:

Auto-discovery of LAN policies (such as VLAN, Layer 2 Priority and Differentiated services (Diffserv) settings) enabling plug and play networking.

Device location discovery to allow creation of location databases and, in the case of Voice over Internet Protocol (VoIP), Enhanced 911 services.

Extended and automated power management of Power over Ethernet (PoE) end points.

Inventory management, allowing network administrators to track their network devices, and determine their characteristics (manufacturer, software and hardware versions, and serial or asset number).

This page allows you to configure the LLDP-MED. This function applies to VoIP devices which support LLDP-MED.

Web Interface

To configure LLDP-MED:

1. Click System, LLDP and LLDP-MED Configuration

2. Modify Fast start repeat count parameter, default is 4

3. Modify Coordinates Location parameters

4. Fill Civic Address Location parameters

5. Add new policy

6. Click Apply, will show following Policy Port Configuration

7. Select Policy ID for each port

8. Click Apply.

Figure 2-5.2: The LLDP-MED Configuration

Parameter description :

Fast start repeat count

Rapid startup and Emergency Call Service Location Identification Discovery of endpoints is a critically important aspect of VoIP systems in general. In addition, it is best to advertise only those pieces of information which are specifically relevant to particular endpoint types (for example only advertise the voice network policy to permitted voice-capable devices), both in order to conserve the limited LLDPU space and to reduce security and system integrity issues

that can come with inappropriate knowledge of the network policy.

With this in mind LLDP-MED defines an LLDP-MED Fast Start interaction between the protocol and the application layers on top of the protocol, in order to achieve these related properties. Initially, a Network Connectivity Device will only transmit LLDP TLVs in an LLDPDU. Only after an LLDP-MED Endpoint Device is detected, will an LLDP-MED capable Network Connectivity Device start to advertise LLDP-MED TLVs in outgoing LLDPDUs on the associated port. The LLDP-MED application will temporarily speed up the transmission of the LLDPDU to start within a second, when a new LLDP-MED neighbour has been detected in order share LLDP-MED information as fast as possible to new neighbours.

Because there is a risk of an LLDP frame being lost during transmission between neighbours, it is recommended to repeat the fast start transmission multiple times to increase the possibility of the neighbours receiving the LLDP frame. With Fast start repeat count it is possible to specify the number of times the fast start transmission would be repeated. The recommended value is 4 times, given that 4 LLDP frames with a 1 second interval will be transmitted, when an LLDP frame with new information is received.

It should be noted that LLDP-MED and the LLDP-MED Fast Start mechanism is only intended to run on links between LLDP-MED Network Connectivity Devices and Endpoint Devices, and as such does not apply to links between LAN infrastructure elements, including Network Connectivity Devices, or other types of links.

Coordinates Location

 Latitude :

Latitude SHOULD be normalized to within 0-90 degrees with a maximum of 4 digits.

It is possible to specify the direction to either North of the equator or South of the equator.

 Longitude :

Longitude SHOULD be normalized to within 0-180 degrees with a maximum of 4 digits.

It is possible to specify the direction to either East of the prime meridian or West of the prime meridian.

 Altitude :

Altitude SHOULD be normalized to within -32767 to 32767 with a maximum of 4 digits.

It is possible to select between two altitude types (floors or meters).

Meters: Representing meters of Altitude defined by the vertical datum specified.

Floors: Representing altitude in a form more relevant in buildings which have different floor-to-floor dimensions. An altitude = 0.0 is meaningful even outside a building, and represents ground level at the given latitude and longitude. Inside a building, 0.0 represents the floor level associated with ground level at the main entrance.

 Map Datum :

The Map Datum is used for the coordinates given in these options:

WGS84: (Geographical 3D) - World Geodesic System 1984, CRS Code 4327, and Prime Meridian Name: Greenwich.

NAD83/NAVD88: North American Datum 1983, CRS Code 4269, Prime Meridian Name: Greenwich; the associated vertical datum is the North American Vertical Datum of 1988 (NAVD88). This datum pair is to be used when referencing locations on land, not near tidal water (which would use Datum = NAD83/MLLW).

NAD83/MLLW: North American Datum 1983, CRS Code 4269, Prime Meridian Name: Greenwich; the associated vertical datum is Mean Lower Low Water (MLLW). This datum pair is to be used when referencing locations on water/sea/ocean.

Civic Address Location

IETF Geopriv Civic Address based Location Configuration Information (Civic Address LCI).

 Country code :

The two-letter ISO 3166 country code in capital ASCII letters - Example: DK, DE or US.

 State :

National subdivisions (state, canton, region, province, prefecture).

 County :

County, parish, gun (Japan), district.

 City :

City, township, shi (Japan) - Example: Copenhagen.

 City district :

City division, borough, city district, ward, chou (Japan).

 Block (Neighbourhood) :

Neighbourhood, block.

 Street :

Street - Example: Poppelvej.

 Leading street direction :

Leading street direction - Example: N.

 Trailing street suffix :

Trailing street suffix - Example: SW.

 Street suffix :

Street suffix - Example: Ave, Platz.

 House no. :

House number - Example: 21.

 House no. suffix :

House number suffix - Example: A, 1/2.

 Landmark :

Landmark or vanity address - Example: Columbia University.

 Additional location info :

Additional location info - Example: South Wing.

 Name :

Name (residence and office occupant) - Example: Flemming Jahn.

 Zip code :

Postal/zip code - Example: 2791.

 Building :

Building (structure) - Example: Low Library.

 Apartment :

Unit (Apartment, suite) - Example: Apt 42.

 Floor :

Floor - Example: 4.

 Room no. :

Room number - Example: 450F.

 Place type :

Place type - Example: Office.

 Postal community name :

Postal community name - Example: Leonia.

 P.O. Box :

Post office box (P.O. BOX) - Example: 12345.

 Additional code :

Additional code - Example: 1320300003.

 Emergency Call Service:

Emergency Call Service (e.g. E911 and others), such as defined by TIA or NENA.

 Emergency Call Service :

Emergency Call Service ELIN identifier data format is defined to carry the ELIN identifier as used during emergency call setup to a traditional CAMA or ISDN trunk-based PSAP. This format consists of a numerical digit string, corresponding to the ELIN to be used for emergency calling.

Policies

Network Policy Discovery enables the efficient discovery and diagnosis of mismatch issues with the VLAN configuration, along with the associated Layer 2 and Layer 3 attributes, which apply for a set of specific protocol applications on that port. Improper network policy configurations are a very significant issue in VoIP environments that frequently result in voice quality degradation or loss of service.

Policies are only intended for use with applications that have specific 'real-time' network policy requirements, such as interactive voice and/or video services.

The network policy attributes advertised are:

1. Layer 2 VLAN ID (IEEE 802.1Q-2003)

2. Layer 2 priority value (IEEE 802.1D-2004)

3. Layer 3 Diffserv code point (DSCP) value (IETF RFC 2474)

This network policy is potentially advertised and associated with multiple sets of application types supported on a given port. The application types specifically addressed are:

1. Voice

2. Guest Voice

3. Softphone Voice

4. Video Conferencing

5. Streaming Video

6. Control / Signalling (conditionally support a separate network policy for the media types above)

A large network may support multiple VoIP policies across the entire organization, and different policies per application type. LLDP-MED allows multiple policies to be advertised per port, each corresponding to a different application type. Different ports on the same Network

Connectivity Device may advertise different sets of policies, based on the authenticated user identity or port configuration.

It should be noted that LLDP-MED is not intended to run on links other than between Network Connectivity Devices and Endpoints, and therefore does not need to advertise the multitude of network policies that frequently run on an aggregated link interior to the LAN.

 Delete :

Check to delete the policy. It will be deleted during the next save.

 Policy ID :

ID for the policy. This is auto generated and shall be used when selecting the polices that shall be mapped to the specific ports.

 Application Type :

Intended use of the application types:

1. Voice - for use by dedicated IP Telephony handsets and other similar appliances supporting interactive voice services. These devices are typically deployed on a separate VLAN for ease of deployment and enhanced security by isolation from data applications.

2. Voice Signalling (conditional) - for use in network topologies that require a different policy for the voice signalling than for the voice media. This application type should not be advertised if all the same network policies apply as those advertised in the Voice application policy.

3. Guest Voice - support a separate 'limited feature-set' voice service for guest users and visitors with their own IP Telephony handsets and other similar appliances supporting interactive voice services.

4. Guest Voice Signalling (conditional) - for use in network topologies that require a different policy for the guest voice signalling than for the guest voice media. This application type should not be advertised if all the same network policies apply as those advertised in the Guest Voice application policy.

5. Softphone Voice - for use by softphone applications on typical data centric devices, such as PCs or laptops. This class of endpoints frequently does not support multiple VLANs, if at all, and are typically configured to use an 'untagged' VLAN or a single 'tagged' data specific VLAN. When a network policy is defined for use with an 'untagged' VLAN (see Tagged flag below), then the L2 priority field is ignored and only the DSCP value has relevance.

6. Video Conferencing - for use by dedicated Video Conferencing equipment and other similar appliances supporting real-time interactive video/audio services.

7. Streaming Video - for use by broadcast or multicast based video content distribution and other similar applications supporting streaming video services that require specific network policy treatment. Video applications relying on TCP with buffering would not be an intended use of this application type.

8. Video Signalling (conditional) - for use in network topologies that require a separate policy for the video signalling than for the video media. This application type should not be advertised if all the same network policies apply as those advertised in the Video Conferencing application policy.

 Tag :

Tag indicating whether the specified application type is using a 'tagged' or an 'untagged' VLAN.

Untagged indicates that the device is using an untagged frame format and as such does not include a tag header as defined by IEEE 802.1Q-2003. In this case, both the VLAN ID and the

Layer 2 priority fields are ignored and only the DSCP value has relevance.

Tagged indicates that the device is using the IEEE 802.1Q tagged frame format, and that both the VLAN ID and the Layer 2 priority values are being used, as well as the DSCP value. The tagged format includes an additional field, known as the tag header. The tagged frame format also includes priority tagged frames as defined by IEEE 802.1Q-2003.

 VLAN ID :

VLAN identifier (VID) for the port as defined in IEEE 802.1Q-2003.

 L2 Priority :

L2 Priority is the Layer 2 priority to be used for the specified application type. L2 Priority may specify one of eight priority levels (0 through 7), as defined by IEEE 802.1D-2004. A value of 0 represents use of the default priority as defined in IEEE 802.1D-2004.

 DSCP :

DSCP value to be used to provide Diffserv node behaviour for the specified application type as defined in IETF RFC 2474. DSCP may contain one of 64 code point values (0 through 63). A value of 0 represents use of the default DSCP value as defined in RFC 2475.

 Port Policies Configuration :

Every port may advertise a unique set of network policies or different attributes for the same network policies, based on the authenticated user identity or port configuration.

 Port :

The port number to which the configuration applies.

 Policy Id :

The set of policies that shall apply to a given port. The set of policies is selected by check marking the checkboxes that corresponds to the policies.

Buttons

 Adding a new policy :

Click to add a new policy. Specify the Application type, Tag, VLAN ID, L2 Priority and DSCP for the new policy. Click "Apply".

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

2-5.3 LLDP Neighbour

This page provides a status overview for all LLDP neighbours. The displayed table contains a row for each port on which an LLDP neighbour is detected. The columns hold the following information:

Web Interface

To show LLDP neighbours:

1. Click System, LLDP and LLDP Neighbour.

2. Click Refresh for manual update web screen

3. Click Auto-refresh for auto-update web screen

Figure 2-5.3: The LLDP Neighbour information

NOTE: If your network without any device supports LLDP then the

table will show “No LLDP neighbour information found”.

Parameter description:  Local Port :

The port on which the LLDP frame was received.

 Chassis ID :

The Chassis ID is the identification of the neighbour's LLDP frames.

 Port ID :

The Remote Port ID is the identification of the neighbour port.

 Port Description :

Port Description is the port description advertised by the neighbour unit.

 System Name :

System Name is the name advertised by the neighbour unit.

 System Capabilities :

System Capabilities describes the neighbour unit's capabilities. The possible capabilities are:

1. Other

2. Repeater

3. Bridge

4. WLAN Access Point

5. Router

6. Telephone

7. DOCSIS cable device

8. Station only

9. Reserved

When a capability is enabled, the capability is followed by (+). If the capability is disabled, the capability is followed by (-).

 System Description

Displays the system description.

 Management Address :

Management Address is the neighbour unit's address that is used for higher layer entities to assist discovery by the network management. This could for instance hold the neighbour's IP address.

Buttons

Figure 2-5.3: The LLDP Neighbor buttons

 Auto-refresh :

Check this box to refresh the page automatically. Automatic refresh occurs every 3 seconds.

 Refresh :

Click to refresh the page immediately.

2-5.4 LLDP-MED Neighbour

This page provides a status overview of all LLDP-MED neighbours. The displayed table contains a row for each port on which an LLDP neighbour is detected. This function applies to VoIP devices which support LLDP-MED. The columns hold the following information:

Web Interface

To show LLDP-MED neighbor:

1. Click System, LLDP and LLDP-MED Neighbour.

2. Click Refresh for manual update web screen

3. Click Auto-refresh for auto-update web screen

Figure 2-5.4: The LLDP-MED Neighbour information

NOTE: If your network without any device supports LLDP-MED

then the table will show “No LLDP-MED neighbour information found”.

Parameter description  Port :

The port on which the LLDP frame was received.

 Device Type :

LLDP-MED Devices are comprised of two primary Device Types: Network Connectivity Devices and Endpoint Devices.

 LLDP-MED Network Connectivity Device Definition

LLDP-MED Network Connectivity Devices, as defined in TIA-1057, provide access to the IEEE 802 based LAN infrastructure for LLDP-MED Endpoint Devices. An LLDP-MED Network Connectivity Device is a LAN access device based on any of the following technologies:

1. LAN Switch/Router

2. IEEE 802.1 Bridge

3. IEEE 802.3 Repeater (included for historical reasons)

4. IEEE 802.11 Wireless Access Point

5. Any device that supports the IEEE 802.1AB and MED extensions defined by TIA-1057 and can relay IEEE 802 frames via any method.

 LLDP-MED Endpoint Device Definition :

LLDP-MED Endpoint Devices, as defined in TIA-1057, are located at the IEEE 802 LAN network edge, and participate in IP communication service using the LLDP-MED framework.

Within the LLDP-MED Endpoint Device category, the LLDP-MED scheme is broken into further Endpoint Device Classes, as defined in the following.

Each LLDP-MED Endpoint Device Class is defined to build upon the capabilities defined for the previous Endpoint Device Class. For-example will any LLDP-MED Endpoint Device claiming compliance as a Media Endpoint (Class II) also support all aspects of TIA-1057 applicable to Generic Endpoints (Class I), and any LLDP-MED Endpoint Device claiming compliance as a Communication Device (Class III) will also support all aspects of TIA-1057 applicable to both Media Endpoints (Class II) and Generic Endpoints (Class I).

 LLDP-MED Generic Endpoint (Class I) :

The LLDP-MED Generic Endpoint (Class I) definition is applicable to all endpoint products that require the base LLDP discovery services defined in TIA-1057, however do not support IP media or act as an end-user communication appliance. Such devices may include (but are not limited to) IP Communication Controllers, other communication related servers, or any device requiring basic services as defined in TIA-1057.

Discovery services defined in this class include LAN configuration, device location, network policy, power management, and inventory management.

 LLDP-MED Media Endpoint (Class II) :

The LLDP-MED Media Endpoint (Class II) definition is applicable to all endpoint products that have IP media capabilities however may or may not be associated with a particular end user. Capabilities include all of the capabilities defined for the previous Generic Endpoint Class (Class I), and are extended to include aspects related to media streaming. Example product categories expected to adhere to this class include (but are not limited to) Voice / Media Gateways, Conference Bridges, Media Servers, and similar.

Discovery services defined in this class include media-type-specific network layer policy discovery.

 LLDP-MED Communication Endpoint (Class III) :

The LLDP-MED Communication Endpoint (Class III) definition is applicable to all endpoint products that act as end user communication appliances supporting IP media. Capabilities include all of the capabilities defined for the previous Generic Endpoint (Class I) and Media Endpoint (Class II) classes, and are extended to include aspects related to end user devices. Example product categories expected to adhere to this class include (but are not limited to) end user communication appliances, such as IP Phones, PC-based softphones, or other communication appliances that directly support the end user.

Discovery services defined in this class include provision of location identifier (including ECS / E911 information), embedded L2 switch support, inventory management.

 LLDP-MED Capabilities :

LLDP-MED Capabilities describes the neighborhood unit's LLDP-MED capabilities. The possible capabilities are:

1. LLDP-MED capabilities

2. Network Policy

3. Location Identification

4. Extended Power via MDI - PSE

5. Extended Power via MDI - PD

6. Inventory

7. Reserved

 Application Type :

Application Type indicating the primary function of the application(s) defined for this network policy, advertised by an Endpoint or Network Connectivity Device. The possible application types are shown below.

2. Voice Signalling - for use in network topologies that require a different policy for the voice signalling than for the voice media.

3. Guest Voice - to support a separate limited feature-set voice service for guest users and visitors with their own IP Telephony handsets and other similar appliances supporting interactive voice services.

4. Guest Voice Signalling - for use in network topologies that require a different policy for the guest voice signalling than for the guest voice media.

5. Softphone Voice - for use by softphone applications on typical data centric devices, such as PCs or laptops.

6. Video Conferencing - for use by dedicated Video Conferencing equipment and other similar appliances supporting real-time interactive video/audio services.

8. Video Signalling - for use in network topologies that require a separate policy for the video signalling than for the video media.

 Policy :

Policy indicates that an Endpoint Device wants to explicitly advertise that the policy is required by the device. Can be either Defined or Unknown

Unknown: The network policy for the specified application type is currently unknown.

Defined: The network policy is defined.

 TAG :

TAG is indicative of whether the specified application type is using a tagged or an untagged VLAN. Can be Tagged or Untagged.

Untagged: The device is using an untagged frame format and as such does not include a tag header as defined by IEEE 802.1Q-2003.

Tagged: The device is using the IEEE 802.1Q tagged frame format.

 VLAN ID :

VLAN ID is the VLAN identifier (VID) for the port as defined in IEEE 802.1Q-2003. A value of 1 through 4094 is used to define a valid VLAN ID. A value of 0 (Priority Tagged) is used if the

device is using priority tagged frames as defined by IEEE 802.1Q-2003, meaning that only the IEEE 802.1D priority level is significant and the default PVID of the ingress port is used instead.

 Priority :

Priority is the Layer 2 priority to be used for the specified application type. One of the eight priority levels (0 through 7).

 DSCP :

DSCP is the DSCP value to be used to provide Diffserv node behavior for the specified application type as defined in IETF RFC 2474. Contain one of 64 code point values (0 through 63).

 Auto-negotiation

Auto-negotiation identifies if MAC/PHY auto-negotiation is supported by the link partner.

 Auto-negotiation status

Auto-negotiation status identifies if auto-negotiation is currently enabled at the link

partner. If Auto-negotiation is supported and Auto-negotiation status is disabled, the

802.3 PMD operating mode will be determined the operational MAU type field value rather than by auto-negotiation.

 Auto-negotiation Capabilities

Auto-negotiation Capabilities shows the link partners MAC/PHY capabilities.

Buttons

Figure 2-5.4: The LLDP Neighbor buttons

 Auto-refresh :

Check this box to refresh the page automatically. Automatic refresh occurs every 3 seconds.

 Refresh :

Click to refresh the page immediately.

2-5.5 LLDP Statistics

Two types of counters are shown. Global counters are counters that refer to the whole switch, while local counters refer to per port counters for the currently selected switch.

Web Interface

To show LLDP Statistics:

1. Click System ,LLDP and LLDP Statistics.

2. Click Refresh for manual update web screen.

3. Click Auto-refresh for auto-update web screen.

4. Click Clear to clear all counters.

Figure 2-5.5: The LLDP Statistics information

Parameter description:

Global Counters

 Neighbour entries were last changed at :

It also shows the time when the last entry was last deleted or added. It also shows the time elapsed since the last change was detected.

 Total Neighbours Entries Added :

Shows the number of new entries added since switch reboot.

 Total Neighbours Entries Deleted :

Shows the number of new entries deleted since switch reboot.

 Total Neighbours Entries Dropped :

Shows the number of LLDP frames dropped due to the entry table being full.

 Total Neighbours Entries Aged Out :

Shows the number of entries deleted due to Time-To -Live expiring.

Local Counters

The displayed table contains a row for each port. The columns hold the following information:

 Local Port :

The port on which LLDP frames are received or transmitted.

 Tx Frames :

The number of LLDP frames transmitted on the port.

 Rx Frames :

The number of LLDP frames received on the port.

 Rx Errors :

The number of received LLDP frames containing some kind of error.

 Frames Discarded :

If an LLDP frame is received on a port, and the switch's internal table has run full, the LLDP frame is counted and discarded. This situation is known as "Too Many Neighbours" in the LLDP standard. LLDP frames require a new entry in the table when the Chassis ID or Remote Port ID is not already contained within the table. Entries are removed from the table when a given port's link is down, an LLDP shutdown frame is received, or when the entry ages out.

 TLVs Discarded :

Each LLDP frame can contain multiple pieces of information, known as TLVs (TLV is short for "Type Length Value"). If a TLV is malformed, it is counted and discarded.

 TLVs Unrecognized :

The number of well-formed TLVs, but with an unknown type value.

 Org. Discarded :

The number of organizationally received TLVs.

 Age-Outs :

Each LLDP frame contains information about how long time the LLDP information is valid (age-out time). If no new LLDP frame is received within the age out time, the LLDP information is removed, and the Age-Out counter is incremented.

Buttons

Figure 2-5.5: The LLDP Statistics information buttons

 Auto-refresh :

Check this box to refresh the page automatically. Automatic refresh occurs every 3 seconds.

 Refresh :

Click to refresh the page.

 Clear :

Clears the counters for the selected port.

2-6 UPnP

UPnP is an acronym for Universal Plug and Play. The goals of UPnP are to allow devices to connect seamlessly and to simplify the implementation of networks in the home (data sharing, communications, and entertainment) and in corporate environments for simplified installation of computer components

Web Interface

To configure the UPnP Configuration in the web interface:

1. Click System and UPnP.

2. Scroll to select the mode to enable or disable.

3. Specify the parameters in each blank field.

4. Click the Apply to save the setting.

5. If you want to cancel the setting then you need to click the Reset button.

6. It will revert to previously saved values.

Figure 2-6: The UPnP Configuration

Parameter description:

These parameters are displayed on the UPnP Configuration page:

 Mode :

Indicates the UPnP operation mode. Possible modes are:

Enabled: Enable UPnP mode operation.

Disabled: Disable UPnP mode operation.

When the mode is enabled, two ACEs are added automatically to trap UPNP related packets to CPU. The ACEs are automatically removed when the mode is disabled. .

 TTL :

The TTL value is used by UPnP to send SSDP advertisement messages. Valid values are in the range 1 to 255.

 Advertising Duration :

The duration, carried in SSDP packets, is used to inform a control point or control points how often it or they should receive an SSDP advertisement message from this switch. If a control point does not receive any message within the duration, it will think that the switch no longer exists. Due to the unreliable nature of UDP, in the standard it is recommended that such refreshing of advertisements to be done at less than one-half of the advertising duration. In the implementation, the switch sends SSDP messages periodically at the interval one-half of the advertising duration minus 30 seconds. Valid values are in the range 100 to

86400.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

Chapter 3 Port Management

The section describes to configure the Port detail parameters of the switch. Others you could using the Port configure to enable or disable the Port of the switch. Monitor the ports content or status in the function.

3-1 Port Configuration

This page displays current port configurations. Ports can also be configured here.

Web Interface

To configure a Current Port Configuration in the web interface:

1. Click Port Management and Port Configuration.

2. Specify the Speed Configured, Flow Control.

3. Specify the detail Port alias or description an alphanumeric string describing the full name

and version identification for the system’s hardware type, software version, and

networking application.

4. Click Apply.

Figure 3-1: The Port Configuration

Parameter description:  Port :

This is the logical port number for this row.

 Link :

The current link state is displayed graphically. Green indicates the link is up and red that it is down.

 Current Link Speed :

Provides the current link speed of the port.

 Configured Link Speed :

Selects any available link speed for the given switch port. Only speeds supported by the specific port is shown. Possible speeds are:

Disabled - Disables the switch port operation.

Auto - Port auto negotiating speed with the link partner and selects the highest speed that is compatible with the link partner.

10Mbps HDX - Forces the cu port in 10Mbps half-duplex mode.

10Mbps FDX - Forces the cu port in 10Mbps full duplex mode.

100Mbps HDX - Forces the cu port in 100Mbps half-duplex mode.

100Mbps FDX - Forces the cu port in 100Mbps full duplex mode.

1Gbps FDX - Forces the port in 1Gbps full duplex.

2.5Gbps FDX - Forces the Serdes port in 2.5Gbps full duplex mode.

SFP_Auto_AMS - Automatically determines the speed of the SFP. Note: There is no standardized way to do SFP auto detect, so here it is done by reading the SFP rom. Due to the missing standardized way of doing SFP auto detect some SFPs might not be detectable. The port is set in AMS mode. Cu port is set in Auto mode.

100-FX - SFP port in 100-FX speed. Cu port disabled.

100-FX_AMS - Port in AMS mode. SFP port in 100-FX speed. Cu port in Auto mode.

1000-X - SFP port in 1000-X speed. Cu port disabled.

1000-X_AMS - Port in AMS mode. SFP port in 1000-X speed. Cu port in Auto mode. Ports in AMS mode with 1000-X speed has Cu port preferred. Ports in AMS mode with 100-FX speed has fiber port preferred.

 Flow Control :

When Auto Speed is selected on a port, this section indicates the flow control capability that is advertised to the link partner. When a fixed-speed setting is selected, that is what is used. The Current Rx column indicates whether pause frames on the port are obeyed, and the Current Tx column indicates whether pause frames on the port are transmitted. The Rx and Tx settings are determined by the result of the last Auto-Negotiation.

Check the configured column to use flow control. This setting is related to the setting for Configured Link Speed.

 Description :

Enter up to 47 characters to be descriptive name for identifies this port.

Buttons

 Refresh :

You can click them for refresh the Port link Status manually.

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

3-2 Port Statistics

The section describes to the Port statistics information and provides overview of general traffic statistics for all switch ports.

Web Interface

To Display the Port Statistics Overview in the web interface:

1. Click Port Management and Port Statistics.

2. If you want to auto-refresh then you need to evoke the “Auto-refresh”.

3. Click “ Refresh“ to refresh the port statistics or clear all information when you click

“ Clear”.

4. If you want to see the detailed of port statistic then you need to click that port.

Figure 3-2: The Port Statistics Overview

Parameter description:  Port :

The logical port for the settings contained in the same row.

 Packets :

The number of received and transmitted packets per port.

 Bytes :

The number of received and transmitted bytes per port.

 Errors :

The number of frames received in error and the number of incomplete transmissions per port.

 Drops :

The number of frames discarded due to ingress or egress congestion.

Buttons

Figure 3-2: The Port Statistics Overview buttons

 Auto-refresh :

Check this box to refresh the page automatically. Automatic refresh occurs every 3 seconds.

 Refresh :

Click to refresh the page.

 Clear :

Clears the counters for all ports.

If you want to see the detailed of port statistic then you need to click that port. The displayed counters are the totals for receive and transmit, the size counters for receive and transmit, and the error counters for receive and transmit.

Figure 3-2: The Detailed Port Statistics

Parameter description:  Upper left scroll bar:

To scroll which port to display the Port statistics with “Port-1”, “Port-2”, ...

Receive Total and Transmit Total

 Rx and Tx Packets :

The number of received and transmitted (good and bad) packets.

 Rx and Tx Octets :

The number of received and transmitted (good and bad) bytes. Includes FCS, but excludes framing bits.

 Rx and Tx Unicast :

The number of received and transmitted (good and bad) unicast packets.

 Rx and Tx Multicast :

The number of received and transmitted (good and bad) multicast packets.

 Rx and Tx Broadcast :

The number of received and transmitted (good and bad) broadcast packets.

 Rx and Tx Pause :

A count of the MAC Control frames received or transmitted on this port that have an opcode indicating a PAUSE operation.

Receive and Transmit Size Counters

The number of received and transmitted (good and bad) packets split into categories based on their respective frame sizes.

Receive Error Counters

 Rx Drops :

The number of frames dropped due to lack of receive buffers or egress congestion.

 Rx CRC/Alignment :

The number of frames received with CRC or alignment errors.

 Rx Undersize :

The number of short 1 frames received with valid CRC.

 Rx Oversize :

The number of long 2 frames received with valid CRC.

 Rx Fragments :

The number of short 1 frames received with invalid CRC.

 Rx Jabber :

The number of long 2 frames received with invalid CRC.

 Rx Filtered :

The number of received frames filtered by the forwarding process.

Short frames are frames that are smaller than 64 bytes.

Long frames are frames that are longer than the configured maximum frame length for this port.

Transmit Error Counters

 Tx Drops :

The number of frames dropped due to output buffer congestion.

 Tx Late/Exc. Coll. :

The number of frames dropped due to excessive or late collisions.

Buttons

Figure 3-2: The Detailed Port Statistics buttons

 Auto-refresh :

Check this box to refresh the page automatically. Automatic refresh occurs every 3 seconds.

 Refresh :

Click to refresh the page.

 Clear :

Clears the counters for the selected port.

3-3 SFP Port Info

The section describes that switch could display the SFP module detail information which you connect it to the switch. The information includes: Connector type, Fiber type, wavelength, bit rate and Vendor OUI etc.

Web Interface

To Display the SFP information in the web interface:

1. Click Port Management and SFP Port Info.

2. To display the SFP Information.

Figure 3-3: The SFP Port Information

Parameter description:  Upper left scroll bar:

To scroll which port to display the Port statistics with “Port-9”, “Port-10”.

 Connector Type:

Display the connector type, for instance, UTP, SC, ST, LC and so on.

 Fiber Type:

Display the fiber mode, for instance, Multi-Mode, Single-Mode.

 Tx Central Wavelength:

Display the fiber optical transmitting central wavelength, for instance, 850nm, 1310nm, 1550nm and so on.

 Bit Rate:

Displays the nominal bit rate of the transceiver.

 Vendor OUI:

Display the OUI code which is assigned by IEEE.

 Vendor Name:

Display the company name of the module manufacturer.

 Vendor P/N:

Display the product name of the naming by module manufacturer.

 Vendor Rev (Revision):

Display the module revision.

 Vendor SN (Serial Number):

Show the serial number assigned by the manufacturer.

 Date Code:

Show the date this SFP module was made.

 Temperature:

Show the current temperature of SFP module.

 Vcc:

Show the working DC voltage of SFP module.

 Mon1(Bias) mA:

Show the Bias current of SFP module.

 Mon2(TX PWR):

Show the transmit power of SFP module.

 Mon3(RX PWR):

Show the receiver power of SFP module.

Buttons

Figure 3-3: The SFP Port Information buttons

 Auto-refresh :

Check this box to refresh the page automatically. Automatic refresh occurs every 3 seconds.

 Refresh :

Click to refresh the page.

3-4 Energy Efficient Ethernet

EEE is an abbreviation for Energy Efficient Ethernet defined in IEEE 802.3az.

This page allows the user to inspect and configure the current EEE port settings.

EEE is a power saving option that reduces the power usage when there is very low traffic utilization (or no traffic).

EEE works by powering down circuits when there is no traffic. When a port gets data to be transmitted all circuits are powered up. The time it takes to power up the circuits is named wakeup time. The default wakeup time is 17 us for 1Gbit links and 30 us for other link speeds. EEE devices must agree upon the value of the wakeup time in order to make sure that both the receiving and transmitting device has all circuits powered up when traffic is transmitted. The devices can exchange information about the devices wakeup time using the LLDP protocol.

Web Interface

To configure an Energy Efficient Ethernet in the web interface:

1. Click Port Management and Energy Efficient Ethernet..

2. The port to select enable or disable Energy Efficient Ethernet

3. Click the apply to save the setting.

4. If you want to cancel the setting then you need to click the Reset button. It will revert to

previously saved values.

Figure 3-4: The Energy Efficient Ethernet Configuration

Parameter description:  Port :

The switch port number of the logical EEE port.

 Configure :

Controls whether EEE is enabled for this switch port.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

3-5 Link Aggregation

3-5.1 Port

This section describes that Port setting/status is used to configure the trunk property of each and every port in the switch system.

Web Interface

To configure the trunk property of each and every port in the web interface:

1. Click Port Management, Link Aggregation and port.

2. Specify the Method, Group, LACP Role and LACP Timeout.

3. Click the apply to save the setting.

4. If you want to cancel the setting then you need to click the Reset button. It will revert to

previously saved values.

Figure 3-5.1: The trunk port setting/status

Parameter description :  Port :

The logical port for the settings contained in the same row.

 Method :

This determines the method a port uses to aggregate with other ports.

 None :

A port does not want to aggregate with any other port should choose this default setting.

 LACP :

A port use LACP as its trunk method to get aggregated with other ports also using LACP.

 Static :

A port use Static Trunk as its trunk method to get aggregated with other ports also using Static Trunk.

 Group :

Ports choosing the same trunking method other than “None” must be assigned a unique Group number (i.e. Group ID, valid value is from 1 to 5) in order to declare that they wish to aggregate with each other.

 LACP Role:

This field is only referenced when a port’s trunking method is LACP.

 Active :

An Active LACP port begins to send LACPDU to its link partner right after the LACP protocol entity started to take control of this port.

 Passive :

A Passive LACP port will not actively send LACPDU out before it receives an LACPDU from its link partner.

 LACP Timeout :

The Timeout controls the period between BPDU transmissions.

 Fast :

It will transmit LACP packets each second,

 Slow :

It will wait for 30 seconds before sending a LACP packet.

 Aggtr :

Aggtr is an abbreviation of “aggregator”. Every port is also an aggregator, and its own aggregator ID is the same as its own Port No. We can regard an aggregator as a representative of a trunking group. Ports with same Group ID and using same trunking method will have the opportunity to aggregate to a particular aggregator port. This aggregator port is usually the port with the smallest Port No. within the trunking group.

 Status :

This field represents the trunking status of a port which uses a trunking method other than “None”. It also represents the management link status of a port which uses the “None” trunking method. “---“ means “not ready”

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

3-5.2 Aggregator View

To display the current port trunking information from the aggregator point of view.

Web Interface

To see the LACP detail in the web interface:

1. Click Port Management, Link Aggregation and Aggregator View.

2. Click the LACP Detail.

Figure 3-5.2: The Aggregator View

Parameter description:  Aggregator :

It shows the aggregator ID of every port. In fact, every port is also an aggregator, and its own aggregator ID is the same as its own Port No..

 Method :

Show the method a port uses to aggregate with other ports.

 Member Ports :

Show all member ports of an aggregator (port).

 Ready Ports :

Show only the ready member ports within an aggregator (port).

 Lacp Detail :

You can select the port that you want to see the LACP Detail.

Buttons

 Lacp Detail :

Click this button then you will see the aggregator information, Details will be described in the below.

Figure 3-5.2: The Lacp Detail

Parameter description:

Actor

 System Priority :

Show the System Priority part of the aggregation Actor. (1-65535)

 Mac Address :

The system ID of the aggregation Actor.

 Actor Port :

The actor's port number connected to this port.

 Actor Key :

The Key that the actor has assigned to this aggregation ID.

Partner

 System Priority :

Show the System Priority part of the aggregation partner. (1-65535).

 Mac Address :

The system ID of the aggregation partner.

 Partner Port :

The partner's port number connected to this port.

 Partner Key :

The Key that the partner has assigned to this aggregation ID.

 Trunk Status :

Button

 Back :

Click to undo any changes made locally and return to the Users.

3-5.3 Aggregation Hash Mode

Web Interface

To configure the Aggregation hash mode in the web interface:

1. Click Port Management, Link Aggregation and Aggregator Hash Mode.

2. Click Hash Code Contributors to select the mode.

3. Click the apply to save the setting.

4. If you want to cancel the setting then you need to click the Reset button. It will revert to

previously saved values.

Figure 3-5.3: Aggregation Hash Mode

Parameter description:

Hash Code Contributors

 src-mac :

Source MAC Address

The Source MAC address can be used to calculate the destination port for the frame. Check to enable the use of the Source MAC address, or uncheck to disable. By default, Source MAC Address is enabled.

 dst-mac :

Destination MAC Address

The Destination MAC Address can be used to calculate the destination port for the frame. Check to enable the use of the Destination MAC Address, or uncheck to disable. By default, Destination MAC Address is disabled.

 ip :

IP Address

The IP address can be used to calculate the destination port for the frame. Check to enable the use of the IP Address, or uncheck to disable. By default, IP Address is enabled.

 src-dst-mac :

Source MAC Address + Destination MAC Address.

 src-ip :

Source MAC Address + IP Address.

 dst-ip :

Destination MAC Address + IP Address.

 src-dst-ip :

Source MAC Address + Destination MAC Address + IP Address.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

3-5.4 LACP System Priority

It is used to set the priority part of the LACP system ID. LACP will only aggregate together the ports whose peer link partners are all on a single system. Each system supports LACP will be assigned a globally unique System Identifier for this purpose. A system ID is a 64-bit field comprising a 48-bit MAC Address and 16-bit priority value. The System Priority can be set by the user. Its range is from 1 to 65535. Default: 32768.

Web Interface

To configure the LACP System Priority in the web interface:

1. Click Port Management, Link Aggregation and LACP System Priority.

2. Specify the LACP System Priority.

3. Click the apply to save the setting.

4. If you want to cancel the setting then you need to click the Reset button. It will revert to

previously saved values.

Figure 3-5.4: The Lacp System Priority

Parameter description:  System Priority:

1-65535.

Show the System Priority part of a system ID.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

3-6 Loop Protection

3-6.1 Configuration

The loop Protection is used to detect the presence of traffic. When switch receives packet’s

(looping detection frame) MAC address the same as oneself from port, show Loop Protection happens. The port will be locked when it received the looping Protection frames. If you want to resume the locked port, please find out the looping path and take off the looping path, then select the resume the locked port and click on “Resume” to turn on the locked ports.

Web Interface

To configure the Loop Protection parameters in the web interface:

1. Click Port Management, Loop Protection and Configuration.

2. Evoke to select enable or disable the port loop Protection.

3. Click the apply to save the setting.

4. If you want to cancel the setting then you need to click the Reset button. It will revert to

previously saved values.

Figure 3-6.1: The Loop Protection Configuration

Parameter description :

Global Configuration

 Enable Loop Protection :

Controls whether loop protections is enabled (as a whole).

 Transmission Time :

The interval between each loop protection PDU sent on each port. Valid values are 1 to 10 seconds.

 Shutdown Time :

The period (in seconds) for which a port will be kept disabled in the event of a loop is detected (and the port action shuts down the port). Valid values are 0 to 604800 seconds (7 days). A value of zero will keep a port disabled (until next device restart).

Port Configuration

 Port :

The switch port number of the port.

 Enable :

Controls whether loop protection is enabled on this switch port

 Action:

Configures the action performed when a loop is detected on a port. Valid values are Shutdown Port, Shutdown Port and Log or Log Only.

 Tx Mode :

Controls whether the port is actively generating loop protection PDU's, or whether it is just passively looking for looped PDU's.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

3-6.2 Status

This section displays the loop protection port status the ports of the currently selected switch.

Web Interface

To display the Loop Protection status in the web interface:

1. Click Port Management, Loop Protection and Status.

2. If you want to auto-refresh the information then you need to evoke the “Auto refresh”.

3. Click “Refresh” to refresh the Loop Protection Status.

Figure 3-6.2: Loop Protection Status

Parameter description:  Port

The switch port number of the logical port.

 Action

The currently configured port action.

 Transmit

The currently configured port transmit mode.

 Loops

The number of loops detected on this port.

 Status

The current loop protection status of the port.

 Loop

Whether a loop is currently detected on the port.

 Time of Last Loop

The time of the last loop event detected.

Buttons

Figure 3-6.2: Loop Protection Status buttons

 Auto-refresh :

Check this box to refresh the page automatically. Automatic refresh occurs every 3 seconds.

 Refresh :

Click to refresh the page immediately.

Chapter 4 PoE Management

PoE is an acronym for Power over Ethernet. Power over Ethernet is used to transmit electrical power, to remote devices over standard Ethernet cable. It could for example be used for powering IP telephones, wireless LAN access points and other equipment, where it would be difficult or expensive to connect the equipment to main power supply.

4-1 PoE Configuration

This page allows the user to inspect and configure the current PoE port settings and show all PoE Supply W.

Web Interface

To configure Power over Ethernet in the web interface:

1. Click PoE Management and PoE Configuration.

2. Specify the PoE or PoE+ Mode, Priority and Maximum Power(W).

3. Click Apply to save the configuration.

4. If you want to cancel the setting then you need to click the Reset button. It will revert to

previously saved values.

Figure 4-1: PoE Configuration

Parameter description:

PoE Power Supply Configuration

 Primary Power Supply [W] :

To display watts for the primary power supply.

 Capacitor Detection :

Click to enable or disable the capacitor configuration.

PoE Port Configuration

 Port :

This is the logical port number for this row.

 PoE Mode :

The PoE Mode represents the PoE operating mode for the port. Enable or Disable PoE.

 Priority :

The Priority represents the ports priority. There are three levels of power priority named Low, High and Critical.

The priority is used in the case where the remote devices requires more power than the power supply can deliver. In this case the port with the lowest priority will be turn off starting from the port with the highest port number.

 Maximum Power [W] :

The Maximum Power value contains a numerical value that indicates the maximum power in watts that can be delivered to a remote device.

The maximum allowed value is 30 W.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

4-2 PoE Status

This page allows the user to inspect the current status for all PoE ports.

Web Interface

To Display PoE Status in the web interface:

1. Click PoE Management and PoE Status

2. Scroll “Auto-refresh” to on/off.

3. Click “Refresh” to refresh the port detailed statistics.

Figure 4-2: The PoE Status

Parameter description:  Local Port :

This is the logical port number for this row.

 PD Class :

Each PD is classified according to a class that defines the maximum power the PD will use. The PD Class shows the PDs class.

Five Classes are defined:

Class 0: Max. power 15.4 W

Class 1: Max. power 4.0 W

Class 2: Max. power 7.0 W

Class 3: Max. power 15.4 W

Class 4: Max. power 30.0 W

 Power Requested :

The Power Requested shows the requested amount of power the PD wants to be reserved.

 Power Allocated :

The Power Allocated shows the amount of power the switch has allocated for the PD.

 Power Used :

The Power Used shows how much power the PD currently is using.

 Current Used :

The Power Used shows how much current the PD currently is using.

 Priority :

The Priority shows the port's priority configured by the user.

 Port Status :

The Port Status shows the port's status. The status can be one of the following values:

PoE not available - No PoE chip found - PoE not supported for the port.

PoE turned OFF - PoE disabled : PoE is disabled by user.

PoE turned OFF - Power budget exceeded - The total requested or used power by the PDs exceeds the maximum power the Power Supply can deliver, and port(s) with the lowest priority is/are powered down.

No PD detected - No PD detected for the port.

PoE turned OFF - PD overload - The PD has requested or used more power than the port can deliver, and is powered down.

PoE turned OFF - PD is off.

Invalid PD - PD detected, but is not working correctly.

Buttons

Figure 4-2: The PoE Status buttons

 Auto-refresh :

Check this box to refresh the page automatically. Automatic refresh occurs every 3 seconds.

 Refresh :

Click to refresh the page immediately.

Chapter 5 VLAN Management

5-1 VLAN Configuration

To assign a specific VLAN for management purpose. The management VLAN is used to establish an IP connection to the switch from a workstation connected to a port in the VLAN. This connection supports a VSM, SNMP, and Telnet session. By default, the active management VLAN is VLAN 1, but you can designate any VLAN as the management VLAN using the Management VLAN window. Only one management VLAN can be active at a time.

When you specify a new management VLAN, your HTTP connection to the old management VLAN is lost. For this reason, you should have a connection between your management station and a port in the new management VLAN or connect to the new management VLAN through a multi-VLAN route.

Web Interface

To configure VLAN membership configuration in the web interface:

1. Click VLAN Management and VLAN Configuration.

2. Specify Existing VLANs, Ether type for Custom S-ports.

3. Click Apply.

Figure 5-1: The VLAN Configuration

Parameter description:

Global VLAN Configuration

 Allowed Access VLANs :

This field shows the VLANs that are created on the switch.

By default, only VLAN 1 exists. More VLANs may be created by using a list syntax where the

individual elements are separated by commas. Ranges are specified with a dash separating the lower and upper bound.

The following example will create VLANs 1, 10, 11, 12, 13, 200, and 300: 1,10-13,200,300. Spaces are allowed in between the delimiters.

 Ethertype for Custom S-ports :

This field specifies the ethertype/TPID (specified in hexadecimal) used for Custom S-ports. The setting is in force for all ports whose Port Type is set to S-Custom-Port.

Port VLAN Configuration

 Port :

This is the logical port number of this row.

 Mode :

The port mode (default is Access) determines the fundamental behavior of the port in question. A port can be in one of three modes as described below. Whenever a particular mode is selected, the remaining fields in that row will be either grayed out or made changeable depending on the mode in question. Grayed out fields show the value that the port will get when the mode is applied.

Access: Access ports are normally used to connect to end stations. Dynamic features like Voice VLAN may add the port to more VLANs behind the scenes. Access ports have the following characteristics:

• Member of exactly one VLAN, the Port VLAN (a.k.a. Access VLAN), which by default is 1,

• accepts untagged frames and C-tagged frames,

• discards all frames that are not classified to the Access VLAN,

• on egress all frames are transmitted untagged.

Trunk: Trunk ports can carry traffic on multiple VLANs simultaneously, and are normally used to connect to other switches. Trunk ports have the following characteristics:

• By default, a trunk port is member of all existing VLANs. This may be limited by the use of Allowed VLANs,

• unless VLAN Trunking is enabled on the port, frames classified to a VLAN that the port is not a member of will be discarded,

• by default, all frames but frames classified to the Port VLAN (a.k.a. Native VLAN) get tagged on egress. Frames classified to the Port VLAN do not get C-tagged on egress,

• egress tagging can be changed to tag all frames, in which case only tagged frames are accepted on ingress,

• VLAN trunking may be enabled.

Hybrid: Hybrid ports resemble trunk ports in many ways, but adds additional port configuration features. In addition to the characteristics described for trunk ports, hybrid ports have these abilities:

• Can be configured to be VLAN tag unaware, C-tag aware, S-tag aware, or S-custom-tag aware,

• ingress filtering can be controlled,

• ingress acceptance of frames and configuration of egress tagging can be configured independently.

 Port VLAN :

Determines the port's VLAN ID (a.k.a. PVID). Allowed VLANs are in the range 1 through 4095, default being 1. On ingress, frames get classified to the Port VLAN if the port is configured as VLAN unaware, the frame is untagged, or VLAN awareness is enabled on the port, but the frame is priority tagged (VLAN ID = 0). On egress, frames classified to the Port VLAN do not get tagged if Egress Tagging configuration is set to untag Port VLAN. The Port VLAN is called an "Access VLAN" for ports in Access mode and Native VLAN for ports in Trunk or Hybrid mode.

 Port Type :

Ports in hybrid mode allow for changing the port type, that is, whether a frame's VLAN tag is used to classify the frame on ingress to a particular VLAN, and if so, which TPID it reacts on. Likewise, on egress, the Port Type determines the TPID of the tag, if a tag is required.

Unaware: On ingress, all frames, whether carrying a VLAN tag or not, get classified to the Port VLAN, and possible tags are not removed on egress.

C-Port: On ingress, frames with a VLAN tag with TPID = 0x8100 get classified to the VLAN ID embedded in the tag. If a frame is untagged or priority tagged, the frame gets classified to the Port VLAN. If frames must be tagged on egress, they will be tagged with a C-tag.

S-Port: On ingress, frames with a VLAN tag with TPID = 0x8100 or 0x88A8 get classified to the VLAN ID embedded in the tag. If a frame is untagged or priority tagged, the frame gets classified to the Port VLAN. If frames must be tagged on egress, they will be tagged with an S-tag.

S-Custom-Port: On ingress, frames with a VLAN tag with a TPID = 0x8100 or equal to the Ethertype configured for Custom-S ports get classified to the VLAN ID embedded in the tag. If a frame is untagged or priority tagged, the frame gets classified to the Port VLAN. If frames must be tagged on egress, they will be tagged with the custom S-tag.

 Ingress Filtering :

Hybrid ports allow for changing ingress filtering. Access and Trunk ports always have ingress filtering enabled. If ingress filtering is enabled (checkbox is checked), frames classified to a VLAN that the port is not a member of get discarded. If ingress filtering is disabled, frames classified to a VLAN that the port is not a member of are accepted and forwarded to the switch engine. However, the port will never transmit frames classified to VLANs that it is not a member of.

 VLAN Trunking :

Trunk and Hybrid ports allow for enabling VLAN trunking. When VLAN trunking is enabled, frames classified to unknown VLANs are accepted on the port whether ingress filtering is enabled or not. This is useful in scenarios where a cloud of intermediary switches must bridge VLANs that haven't been created. By configuring the ports that connect the cloud of switches as trunking ports, they can seemlessly carry those VLANs from one end to the other.

 Ingress Acceptance :

Hybrid ports allow for changing the type of frames that are accepted on ingress.

Tagged and untagged both tagged and untagged frames are accepted.

Tagged Only Only tagged frames are accepted on ingress. Untagged frames are discarded.

Untagged Only Only untagged frames are accepted on ingress. Tagged frames are discarded.

 Egress Tagging :

Ports in Trunk and Hybrid mode may control the tagging of frames on egress.

Untag Port VLAN Frames classified to the Port VLAN are transmitted untagged. Other frames are transmitted with the relevant tag.

Tag All All frames, whether classified to the Port VLAN or not, are transmitted with a tag.

Untag All All frames, whether classified to the Port VLAN or not, are transmitted without a tag. This option is only available for ports in Hybrid mode.

 Allowed VLANs :

Ports in Trunk and Hybrid mode may control which VLANs they are allowed to become members of. Access ports can only be member of one VLAN, the Access VLAN. The field's syntax is identical to the syntax used in the Existing VLANs field. By default, a port may become member of all possible VLANs, and is therefore set to 1-4095. The field may be left empty, which means that the port will not be member of any of the existing

VLANs, but if it is configured for VLAN Trunking it will still be able to carry all unknown VLANs.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

5-2 VLAN Membership

This page provides an overview of membership status of VLAN users.

The ports belong to the currently selected stack unit, as reflected by the page header.

Web Interface

To configure VLAN membership configuration in the web interface:

1. Click VLAN Management and VLAN membership.

2. Scroll the bar to choice which VLANs would like to show up.

3. Click Refresh to update the state.

Figure 7-2: The VLAN Membership

Parameter description:  VLAN USER :

VLAN User module uses services of the VLAN management functionality to configure VLAN memberships and VLAN port configurations such as PVID and UVID. Currently we support the following VLAN user types:

CLI/Web/SNMP : These are referred to as static.

NAS : NAS provides port-based authentication, which involves communications between a

Supplicant, Authenticator, and an Authentication Server.

MVRP : Multiple VLAN Registration Protocol (MVRP) allows dynamic registration and deregistration of VLANs on ports on a VLAN bridged network.

Voice VLAN : Voice VLAN is a VLAN configured specially for voice traffic typically originating from IP phones.

MVR : MVR is used to eliminate the need to duplicate multicast traffic for subscribers in each VLAN. Multicast traffic for all channels is sent only on a single (multicast) VLAN.

MSTP : The 802.1s Multiple Spanning Tree protocol (MSTP) uses VLANs to create multiple spanning trees in a network, which significantly improves network resource utilization while maintaining a loop-free environment.

 VLAN ID :

VLAN ID for which the Port members are displayed.

 Port Members (VLAN Configuration 功能不同要做修改)

A row of check boxes for each port is displayed for each VLAN ID. If a port is included in a VLAN, an image will be displayed.

If a port is included in a Forbidden port list, an image will be displayed.

If a port is included in a Forbidden port list and dynamic VLAN user register VLAN on same Forbidden port, then conflict port will be displayed as .

 Untagged port Members :

The interface is an untagged member of the VLAN. Frames of the VLAN are sent untagged to the interface VLAN.

 VLAN Membership :

The VLAN Membership Status Page shall show the current VLAN port members for all VLANs configured by a selected VLAN User (selection shall be allowed by a Combo Box). When ALL VLAN Users are selected, it shall show this information for all the VLAN Users, and this is by default. VLAN membership allows the frames classified to the VLAN ID to be forwarded on the respective VLAN member ports.

 Show entries :

You can choose how many items you want to show off.

 Search :

You can search for the information that you want to see.

Buttons

Figure 5-2: The VLAN Membership buttons

 Auto-refresh :

Check this box to refresh the page automatically. Automatic refresh occurs every 3 seconds.

 Refresh :

Click to refresh the page.

 Clear :

Click to clear the page.

 Next :

Updates the system log entries, turn to the next page.

 Previous :

Updates the system log entries, turn to the previous page.

5-3 VLAN Port Status

The function Port Status gathers the information of all VLAN status and reports it by the order of Static NAS MVRP MVP Voice VLAN MSTP GVRP Combined.

Web Interface

To Display VLAN Port Status in the web interface:

1. Click VLAN Management and VLAN Port Status.

2. Specify the Static NAS MVRP MVP Voice VLAN MSTP GVRP Combined.

3. Display Port Status information.

Figure 5-3: The VLAN Port Status

Parameter description:

VLAN USER

VLAN User module uses services of the VLAN management functionality to configure VLAN memberships and VLAN port configuration such as PVID, UVID. Currently we support following VLAN User types:

CLI/Web/SNMP : These are referred to as static.

NAS : NAS provides port-based authentication, which involves communications between a

Supplicant, Authenticator, and an Authentication Server.

Voice VLAN : Voice VLAN is a VLAN configured specially for voice traffic typically originating from IP phones.

MVR : MVR is used to eliminate the need to duplicate multicast traffic for subscribers in each VLAN. Multicast traffic for all channels is sent only on a single (multicast) VLAN.

 Port :

The logical port for the settings contained in the same row.

 Port Type :

Shows the Port Type. Port type can be any of Unaware, C-port, S-port, Custom S-port.

If Port Type is Unaware, all frames are classified to the Port VLAN ID and tags are not removed. C-port is Customer Port. S-port is Service port. Custom S-port is S-port with Custom TPID.

 Ingress Filtering :

Shows the ingress filtering on a port. This parameter affects VLAN ingress processing. If ingress filtering is enabled and the ingress port is not a member of the classified VLAN, the frame is discarded.

 Frame Type :

Shows whether the port accepts all frames or only tagged frames. This parameter affects VLAN ingress processing. If the port only accepts tagged frames, untagged frames received on that port are discarded.

 Port VLAN ID :

Shows the Port VLAN ID (PVID) that a given user wants the port to have.

The field is empty if not overridden by the selected user.

 Tx Tag :

Shows egress filtering frame status whether tagged or untagged.

Buttons

Figure 5-3: The VLAN Port Status buttons

 Auto-refresh :

Check this box to refresh the page automatically. Automatic refresh occurs every 3 seconds.

 Refresh :

Click to refresh the page.

 Clear :

Click to clear the page.

Chapter 6 Quality of Service

6-1 Global Settings

Use the Global Settings page to set the trust behavior for QoS basic mode. This configuration is active when the switch is in QoS basic mode. Packets entering a QoS domain are classified at the edge of the QoS domain.

Web Interface

To configure the Global Settings in the web interface:

1. Click Quality of Service and Global Settings.

2. Select the trust mode when the switch is in QoS basic mode. If a packet CoS level and

DSCP tag are mapped to separate queues, the trust mode determines the queue to which the packet is assigned.

3. Click Apply to save the configuration.

4. If you want to cancel the setting then you need to click the Reset button. It will revert

to previously saved values.

Figure 6-1: The QoS Global Settings

Parameter description:

Trust Mode

 CoS/802.1p :

Traffic is mapped to queues based on the VPT field in the VLAN tag, or based on the per-port default CoS/802.1p value (if there is no VLAN tag on the incoming packet), the actual mapping of the VPT to queue can be configured on the CoS/802.1p to Queue page.

 DSCP :

All IP traffic is mapped to queues based on the DSCP field in the IP header. The actual mapping of the DSCP to queue can be configured on the DSCP to Queue page. If traffic is not IP traffic, it is mapped to the best effort queue.

 IP Precedence :

Traffic is mapped to queues based on the IP precedence. The actual mapping of the IP precedence to queue can be configured on the IP Precedence to Queue page.

 CoS/802.1p-DSCP :

Uses the trust CoS mode for non-IP traffic and trust DSCP mode for IP traffic.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

6-2 Port Settings

Web Interface

To configure the QoS Port Setting in the web interface:

1. Click Quality of Service and Port Settings.

2. Select Mode, Default CoS, Source CoS, Remark CoS to each port.

3. Click which port need to enable the Remark Cos, Remark DSCP, Remark IP Precedence

4. Click Apply to save the configuration.

5. If you want to cancel the setting then you need to click the Reset button. It will revert

to previously saved values.

Figure 6-2: The QoS Port Settings

Parameter description:  Port :

The logical port for the settings contained in the same row.

 Mode :

 Untrust :

All ingress traffic on the port is mapped to the best effort queue and no classification/prioritization takes place.

 Trust :

Port prioritize ingress traffic is based on the system wide configured trusted mode, which is either CoS/802.1p trusted mode, IP Precedence trusted mode or DSCP trusted mode.

 Default CoS :

Select the default CoS value to be assigned for incoming untagged packets. The range is 0 to 7.

 Source CoS :

The CoS value is determined based on C-Tag or S-Tag for incoming tagged packets.

 Remark CoS :

Click the checkbox to remark the CoS/802.1p priority for egress traffic on this port.

 Remark DSCP :

Click the checkbox to remark the DSCP value for egress traffic on this port.

 Remark IP Precedence

Click the checkbox to remark the IP precedence for egress traffic on this port.

Note: The CoS/802.1p priority and IP Precedence, or the CoS/802.1p priority and DSCP value can be remarked simultaneously for egress traffic on a port, but the DSCP value and IP Precedence cannot be remarked simultaneously.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

6-3 Port Policing

This section provides an overview of QoS Ingress Port Policers for all switch ports The Port Policing is useful in constraining traffic flows and marking frames above specific rates. Policing is primarily useful for data flows and voice or video flows because voice and video usually maintains a steady rate of traffic

Web Interface

To configure the QoS Port Policers in the web interface:

1. Click Quality of Service and Port Policing.

2. Click which port need to enable the QoS Ingress Port Policers, and configure the Rate

limit condition.

3. Click Apply to save the configuration.

4. If you want to cancel the setting then you need to click the Reset button. It will revert

to previously saved values.

Figure 6-3: The QoS Ingress Port Policers Configuration

Parameter description:  Port :

The logical port for the settings contained in the same row. Click on the port number in order to configure the schedulers.

 Enabled :

To evoke which Port you need to enable the QoS Ingress Port Policers function.

 Rate :

To set the Rate limit value for this port, the default is 1000000.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

6-4 Port Shaper

This section provides an overview of QoS Egress Port Shapers for all switch ports. Others the user could get all detail information of the ports belong to the currently selected stack unit, as reflected by the page header.

Web Interface

To configure the QoS Port Shapers in the web interface:

1. Click Quality of Service and Port Shaper.

2. Select which port need to configure QoS Egress Port Shaper.

3. Click which port need to enable, and configure the Rate limit condition.

4. Click Apply to save the configuration.

5. If you want to cancel the setting then you need to click the Reset button. It will revert

to previously saved values.

Figure 6-4: The QoS Egress Port Shaper

Parameter description:  Port :

The logical port for the settings contained in the same row. Click on the port number in order to configure the shapers.

Queue Shaper

 Queue :

The queue number of the queue shaper on this switch port.

 Enable :

Controls whether the queue shaper is enabled for this queue on this switch port.

 Rate(kbps) :

Controls the rate for the queue shaper. The default value is 1000000.

Port Shaper

 Enable :

Controls whether the port shaper is enabled for this switch port.

 Rate(kbps) :

Controls the rate for the port shaper. The default value is 1000000.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

6-5 Storm Control

The section allows user to configure the Storm control for the switch. There is a destination lookup failure storm rate control, multicast storm rate control, and a broadcast storm rate control. These only affect flooded frames, i.e. frames with a (VLAN ID, DMAC) pair not present on the MAC Address table. The configuration indicates the permitted packet rate for unicast, multicast, or broadcast traffic across the switch.

Web Interface

To configure the Storm Control Configuration parameters in the web interface:

1. Click Quality of Service and Storm Control.

2. Click which port need to enable, and configure the Rate limit condition.

4. Click the Apply to save the setting.

5. If you want to cancel the setting then you need to click the Reset button. It will revert to previously saved values.

Figure 6-5: The Storm Control Configuration

Parameter description:  Port :

The logical port for the settings contained in the same row. Click on the port number in order to configure the storm control.

 Frame Type :

The settings in a particular row apply to the frame type listed here: Broadcast, Multicast or DLF(destination lookup failure).

 Enable :

Enable or disable the storm control status for the given frame type.

 Rate :

The rate unit is packets per second (pps). Valid values are: 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1K, 2K, 4K, 8K, 16K, 32K, 64K, 128K, 256K, 512K or 1024K. , 1024K, 2048K, 4096K, 8192K, 16384K or 32768K. , 1024K, 2048K, 4096K, 8192K, 16384K or 32768K.

The 1 kpps is actually 1002.1 pps.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

6-6 Port Scheduler

This section provides an overview of QoS Egress Port Scheduler for all switch ports. and the ports belong to the currently selected stack unit, as reflected by the page header.

Web Interface

To configure the QoS Port Schedulers in the web interface:

1. Click Quality of Service and Port Scheduler.

2. Select Scheduler Mode for each port.

3. If you select WRR or WFQ, you can configure weight.

4. Click the Apply to save the setting.

5. If you want to cancel the setting then you need to click the Reset button. It will revert

to previously saved values.

Figure 6-6: The QoS Egress Port Schedules

Parameter description:  Port :

The logical port for the settings contained in the same row.

 Scheduler Mode :

Controls whether the scheduler mode is "Strict Priority", "WRR" or "WFQ" on this switch port.

 Weight :

Controls the weight for this queue. The default value is "0". This value is restricted to 1-100. This parameter is only shown if "Scheduler Mode" is set to "Weighted".

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

6-7 CoS/802.1p Mapping

Use the CoS/802.1p to Queue page to map 802.1p priorities to egress queues. The CoS/802.1p to Queue table determines the egress queues of the incoming packets based on the 802.1p priority in their VLAN tags. For incoming untagged packets, the 802.1p priority will be the default CoS/802.1p priority assigned to the ingress ports.

Web Interface

To configure the Cos/802.1p Mapping in the web interface:

1. Click Quality of Service and Cos/802.1p Mapping.

2. Select Queue ID.

3. Click the Apply to save the setting.

4. If you want to cancel the setting then you need to click the Reset button. It will revert

to previously saved values.

Figure 6-7: The QoS Ingress CoS/802.1p to Queue Mapping

Parameter description:  CoS/802.1p :

Displays the 802.1p priority tag values to be assigned to an egress queue, where 0 is the lowest and 7 is the highest priority.

 Queue ID :

Select the egress queue to which the 802.1p priority is mapped. Eight egress queues are supported, where Queue 8 is the highest priority egress queue and Queue 1 is the lowest priority egress queue.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

6-8 CoS/802.1p Remarking

Use the Queues to CoS/802.1p page to remark the CoS/802.1p priority for egress traffic from each queue.

Web Interface

To configure the Cos/802.1p Remarking in the web interface:

1. Click Quality of Service and Cos/802.1p Remarking.

2. Select CoS/802.1p.

3. Click the Apply to save the setting.

4. If you want to cancel the setting then you need to click the Reset button. It will revert

to previously saved values.

Figure 6-8: The QoS Egress Queue to CoS/802.1p Remarking

Parameter description:  Queue ID :

Displays the Queue ID, where Queue 8 is the highest priority egress queue and Queue 1 is the lowest priority egress queue.

 CoS/802.1p :

For each output queue, select the CoS/802.1p priority to which egress traffic from the queue is remarked.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

6-9 IP Precedence Mapping

To map IP precedence to egress queue.

Web Interface

To configure the IP Precedence Mapping in the web interface:

1. Click Quality of Service and IP Precedence Mapping.

2. Select Queue ID.

3. Click the Apply to save the setting.

4. If you want to cancel the setting then you need to click the Reset button. It will revert

to previously saved values.

Figure 6-9: The QoS Ingress IP Precedence to Queue Mapping

Parameter description:  IP Precedence :

Displays the IP Precedence priority tag values to be assigned to an egress queue, where 0 is the lowest and 7 is the highest priority.

 Queue ID :

Select the egress queue to which the IP precedence priority is mapped. Eight egress queues are supported, where Queue 8 is the highest priority egress queue and Queue 1 is the lowest priority egress queue.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

6-10 IP Precedence Remarking

To map egress queue to IP precedence.

Web Interface

To configure the IP Precedence Remarking in the web interface:

1. Click Quality of Service and IP Precedence Remarking.

2. Select IP Precedence.

3. Click the Apply to save the setting.

4. If you want to cancel the setting then you need to click the Reset button. It will revert

to previously saved values.

Figure 6-10: The QoS Egress Queue to IP Precedence Remarking

Parameter description:  Queue ID :

Displays the Queue ID, where Queue 8 is the highest priority egress queue and Queue 1 is the lowest priority egress queue.

 IP Precedence :

For each output queue, select the IP Precedence priority to which egress traffic from the queue is remarked.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

6-11 DSCP Mapping

Use the DSCP to Queue page to map IP DSCP to egress queues. The DSCP to Queue table determines the egress queues of the incoming IP packets based on their DSCP values. The original VLAN Priority Tag (VPT) of the packet is unchanged.

It is possible to achieve the desired QoS in a network by simply changing the DSCP to Queue mapping, the queue schedule method, and bandwidth allocation.

Web Interface

To configure the DSCP Mapping in the web interface:

1. Click Quality of Service and DSCP Mapping.

2. Select Queue ID.

3. Click the Apply to save the setting.

4. If you want to cancel the setting then you need to click the Reset button. It will revert

to previously saved values.

Figure 6-11: The QoS Ingress DSCP to Queue Mapping

Parameter description:  DSCP :

Displays the DSCP value in the incoming packet and its associated class.

 Queue ID :

Select the traffic forwarding queue from the Output Queue drop-down menu to which the DSCP value is mapped.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

6-12 DSCP Remarking

Use the Queues to DSCP page to remark DSCP value for egress traffic from each queue.

Web Interface

To configure the DSCP Remarking in the web interface:

1. Click Quality of Service and DSCP Remarking.

2. Select DSCP.

3. Click the apply to save the setting.

4. If you want to cancel the setting then you need to click the Reset button. It will revert

to previously saved values.

Figure 6-12: The QoS Egress Queue to DSCP Remarking

Parameter description:  Queue ID :

Displays the Queue ID, where Queue 8 is the highest priority egress queue and Queue 1 is the lowest priority egress queue.

 DSCP :

For each output queue, select the DSCP priority to which egress traffic from the queue is remarked.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

Chapter 7 Spanning tree

The Spanning Tree Protocol (STP) can be used to detect and disable network loops, and to provide backup links between switches, bridges or routers. This allows the switch to interact with other bridging devices (that is, an STP-compliant switch, bridge or router) in your network to ensure that only one route exists between any two stations on the network, and provide backup links which automatically take over when a primary link goes down.

STP - STP uses a distributed algorithm to select a bridging device (STP- compliant switch, bridge or router) that serves as the root of the spanning tree network. It selects a root port on each bridging device (except for the root device) which incurs the lowest path cost when forwarding a packet from that device to the root device. Then it selects a designated bridging device from each LAN which incurs the lowest path cost when forwarding a packet from that LAN to the root device. All ports connected to designated bridging devices are assigned as designated ports. After determining the lowest cost spanning tree, it enables all root ports and designated ports, and disables all other ports. Network packets are therefore only forwarded between root ports and designated ports, eliminating any possible network loops.

Figure 9: The Spanning Tree Protocol

Once a stable network topology has been established, all bridges listen for Hello BPDUs (Bridge Protocol Data Units) transmitted from the Root Bridge. If a bridge does not get a Hello BPDU after a predefined interval (Maximum Age), the bridge assumes that the link to the Root Bridge is down. This bridge will then initiate negotiations with other bridges to reconfigure the network to reestablish a valid network topology.

7-1 State

The section describes that you can select enable spanning tree protocol or not, and you can select what protocol version you want.

Web Interface

To configure the Spanning Tree Protocol version in the web interface:

1. Click Spanning Tree and state.

2. Evoke to enable or disable the Spanning Tree Protocol.

3. Select the Spanning Tree Protocol version.

4. Click the apply to save the setting.

5. If you want to cancel the setting then you need to click the Reset button. It will revert to

previously saved values.

Figure 7-1: The Spanning Tree state

Parameter description:  Multiple Spanning Tree Protocol :

You can select enable spanning tree protocol or not.

 Force Version :

The STP protocol version setting. Valid values are STP, RSTP and MSTP.

Buttons

 Apply :

Click to save changes.

 Reset :

Click to undo any changes made locally and revert to previously saved values.

Vivotek VivoCam AW-GEV-104B-130, VivoCam AW-GEV-184B-250, VivoCam AW-GEV-264B-370 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual